Package: libvirt-clients
Version: 7.10.0-1
Severity: important
X-Debbugs-Cc: d...@vollmann.ch
Dear Maintainer,
* What led up to the situation?
Using virsh to start a VM from fvwm.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I start a VM from fvwm normally with such an entry:
Exec virsh start vm && virt-viewer vm
This stopped working after the last libvirt upgrade.
Using a script and strace I found that it opens /dev/tty shortly before
the end of the output, so I assume there's a problem here.
Running the command from the command line in an xterm works fine.
* What was the outcome of this action?
The virsh process still shows up in 'ps', but doesn't show
any activity, doesn't end and doesn't start the VM.
* What outcome did you expect instead?
That the program returns and starts the VM.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libvirt-clients depends on:
ii libc6 2.33-1
ii libgcc-s1 11.2.0-13
ii libglib2.0-0 2.70.2-1
ii libgnutls30 3.7.2-4
ii libreadline8 8.1-2
ii libvirt0 7.10.0-1
ii libxml2 2.9.12+dfsg-5+b1
ii sensible-utils 0.0.17
libvirt-clients recommends no packages.
Versions of packages libvirt-clients suggests:
ii libvirt-daemon 7.10.0-1
pn libvirt-login-shell <none>
-- no debconf information
