Your message dated Mon, 24 Jun 2019 17:49:40 +0200 with message-id <[email protected]> and subject line Re: [Pkg-libvirt-maintainers] Bug#931014: Solved has caused the Debian Bug report #931014, regarding virt-manager: Virt-manager crashed when attempting to create new VM. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 931014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931014 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: virt-manager Version: 1:2.0.0-3 Severity: important Dear Maintainer, * What led up to the situation? Attempted to create a new VM * What exactly did you do (or not do) that was effective (or ineffective)? Clicked the new VM button * What was the outcome of this action? Virt-manager crashed * What outcome did you expect instead? VM creation wizard comes up and works. Here's the output of the console during the crash: [Mon, 24 Jun 2019 10:39:53 virt-manager 21406] DEBUG (create:200) Showing new vm wizard [Mon, 24 Jun 2019 10:39:53 virt-manager 21406] DEBUG (create:695) Guest type set to os_type=hvm, arch=x86_64, dom_type=kvm (virt-manager:21406): GLib-GIO-ERROR **: 10:39:53.289: Settings schema 'org.virt-manager.virt-manager.urls' does not contain a key named 'containers' There is not further output past this point. My system is an upgrade from Debian Stretch to Debian Buster. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/24 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-gtk-vnc-2.0 0.9.0-1.1 ii gir1.2-libosinfo-1.0 1.2.0-1 ii gir1.2-libvirt-glib-1.0 1.0.0-1 ii gir1.2-vte-2.91 0.54.2-2 ii librsvg2-common 2.44.10-2.1 ii python-requests 2.21.0-1 ii python3 3.7.3-1 ii python3-dbus 1.2.8-3 ii python3-gi 3.30.4-1 ii python3-gi-cairo 3.30.4-1 ii python3-libvirt 5.0.0-1 ii virtinst 1:2.0.0-3 Versions of packages virt-manager recommends: ii gir1.2-spiceclientglib-2.0 0.35-2 ii gir1.2-spiceclientgtk-3.0 0.35-2 ii libvirt-daemon-system 5.0.0-3 Versions of packages virt-manager suggests: ii gir1.2-secret-1 0.18.7-1 ii gnome-keyring 3.28.2-5 ii ksshaskpass [ssh-askpass] 4:5.14.5-1 pn python3-guestfs <none> ii virt-viewer 7.0-2 -- no debconf information
--- End Message ---
--- Begin Message ---Hi, On Mon, Jun 24, 2019 at 03:39:07PM +0000, Joe McEntire wrote: > This was solved by: > > apt autoremove virt-manager --purge > > apt install virt-manager > > I do not see this issue on my laptop. I think it was a fluke issue. Closing although it'd be nice to know how that happened. -- Guido > > Please disregard! > > Thanks for your time, > > Joe > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Pkg-libvirt-maintainers mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers
--- End Message ---
