All;
when I was running Fedora 42 - KDE Spin I could do this:
*open konsole*
*become root*
*# virt-manager &*
then close the konsole and virt-manager would continue to run
I upgraded via the steps on this page: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
Now this happens:
*open konsole*
*become root*
*# virt-manager &*
then close the konsole and virt-manager immediately dies / goes away
Thoughts?
Thanks in advance
On Mon, Jan 12, 2026, 11:22 AM Sbob via kde kde@lists.fedoraproject.org wrote:
All;
when I was running Fedora 42 - KDE Spin I could do this:
*open konsole*
*become root*
*# virt-manager &*
then close the konsole and virt-manager would continue to run
I upgraded via the steps on this page: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
Now this happens:
*open konsole*
*become root*
*# virt-manager &*
then close the konsole and virt-manager immediately dies / goes away
Thoughts?
Thanks in advance
Sounds like virt manager changed to not disconnect from controlling
terminal, try nohup or daemonize (probably the latter)
On 1/12/26 9:29 AM, Neal Becker wrote:
On Mon, Jan 12, 2026, 11:22 AM Sbob via kde kde@lists.fedoraproject.org wrote:
All; when I was running Fedora 42 - KDE Spin I could do this: *open konsole* *become root* *# virt-manager &* then close the konsole and virt-manager would continue to run I upgraded via the steps on this page: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/ Now this happens: *open konsole* *become root* *# virt-manager &* then close the konsole and virt-manager immediately dies / goes away Thoughts? Thanks in advanceSounds like virt manager changed to not disconnect from controlling terminal, try nohup or daemonize (probably the latter)
nohup works, any idea why I did not need nohup on Fedora 42?
On Mon, 2026-01-12 at 22:37 +0000, Barry via kde wrote:
On 12 Jan 2026, at 17:37, Sbob via kde kde@lists.fedoraproject.org wrote:
On 1/12/26 9:29 AM, Neal Becker wrote:
On Mon, Jan 12, 2026, 11:22 AM Sbob via kde kde@lists.fedoraproject.org wrote:
All;
when I was running Fedora 42 - KDE Spin I could do this: open konsole become root # virt-manager & then close the konsole and virt-manager would continue to run
I upgraded via the steps on this page: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora -offline/
Now this happens: open konsole become root # virt-manager & then close the konsole and virt-manager immediately dies / goes away
Thoughts?
You can start virt manager from the plasma menu. Which would avoid the need to involve konsole.
Also if your user is added to the libvirt group you do not need to run virt manager as root.
Was about to say this. Running virt-manager as root is probably not a good idea unless there's some specific need for it, and the launcher menu takes care of backgrounding.
[Please don't post in HTML-only. See the list guidelines linked at the end of every message].
poc