Version-Release number of selected component: gnome-boxes-3.19.92-1.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 2151 kernel: 4.5.0-0.rc7.git0.2.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 boxes_app_setup_default_source_co at /home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430 #5 g_simple_async_result_complete at gsimpleasyncresult.c:801 #6 boxes_app_add_collection_source_co at /home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:351 #7 g_simple_async_result_complete at gsimpleasyncresult.c:801 #8 boxes_libvirt_broker_real_add_source_co at /home/zeenix/checkout/gnome/gnome-boxes/src/libvirt-broker.vala:105 #9 g_task_return_now at gtask.c:1107 #10 complete_in_idle_cb at gtask.c:1121 #14 g_main_context_iteration at gmain.c:3901 #15 g_application_run at gapplication.c:2381 #16 _vala_main at /home/zeenix/checkout/gnome/gnome-boxes/src/main.vala:84
Created attachment 1139215 [details] File: backtrace
Created attachment 1139216 [details] File: cgroup
Created attachment 1139217 [details] File: core_backtrace
Created attachment 1139218 [details] File: dso_list
Created attachment 1139219 [details] File: environ
Created attachment 1139220 [details] File: limits
Created attachment 1139221 [details] File: maps
Created attachment 1139222 [details] File: mountinfo
Created attachment 1139223 [details] File: namespaces
Created attachment 1139224 [details] File: open_fds
Created attachment 1139225 [details] File: proc_pid_status
Created attachment 1139226 [details] File: var_log_messages
Similar problem has been detected: just run gnome-boxes after boot reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 3612 kernel: 4.5.0-302.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 reason: gnome-boxes killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: just launch gnome-boxes reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 4188 kernel: 4.5.0-302.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 reason: gnome-boxes killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just run gnome-boxes after computer reboot reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 2975 kernel: 4.5.0-302.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 reason: gnome-boxes killed by SIGABRT runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: just launch gnome-boxes immediately after system boot reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 2836 kernel: 4.5.1-300.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: launch gnome-boxes after reboot $ gnome-boxes (gnome-boxes:2845): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:2845): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:2845): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 2845 kernel: 4.5.1-300.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 1000
(In reply to Mikhail from comment #17) > Similar problem has been detected: > > launch gnome-boxes after reboot > > $ gnome-boxes > > Error setting up default broker: Unable to open qemu+unix:///session: Failed > to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or > directory > ** > Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430: > boxes_app_setup_default_source_co: assertion failed: (default_connection != > null) > Aborted (core dumped) Is this working fine if you try to run it several times? Or always crashing?
> Is this working fine if you try to run it several times? Yes.
On Fedora 23 I have another issue: https://bugzilla.redhat.com/show_bug.cgi?id=1318713 which seems fixed here. P.S. /home partition placed on btrfs partition.
Your issue from comment #17 might be https://bugzilla.gnome.org/show_bug.cgi?id=751696 then. Corresponding fedora bug is https://bugzilla.redhat.com/show_bug.cgi?id=1271183 , but if it's this bug, it's supposed to be fixed in libvirt-1.3.3-1.fc24
Similar problem has been detected: [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:2956): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:2956): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:2956): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3158): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3158): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3158): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3368): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3368): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3368): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 2956 kernel: 4.5.2-300.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3198): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3198): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3198): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3462): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3462): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3462): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3501): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3501): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3501): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:430:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3670): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3670): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3670): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 3198 kernel: 4.5.2-302.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Created attachment 1154131 [details] screencast
Ah ok, so it actually crashes every time you try to run it, not just the first time after startup. Have you tried running virsh -c qemu:///session list --all ? Is this working or throwing the same error?
Similar problem has been detected: Just trying to open the Boxes app on Fedora 24 Beta. Nothing more, nothing less. reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 10404 kernel: 4.5.2-302.fc24.x86_64 package: gnome-boxes-3.20.0-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3598): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3598): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3598): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:433:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3830): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3830): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3830): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:433:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:3921): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:3921): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:3921): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:433:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:4120): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:4120): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:4120): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:433:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:4198): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:4198): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:4198): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:/home/zeenix/checkout/gnome/gnome-boxes/src/app.vala:433:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:4435): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:4435): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:4435): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead (gnome-boxes:4435): Boxes-WARNING **: vm-creator.vala:117: Failed to start 'Microsoft Windows 7 Professional': Unable to start domain: operation failed: job: unexpectedly failed reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: gnome-boxes crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 3511 kernel: 4.5.6-300.fc24.x86_64+debug package: gnome-boxes-3.20.2-2.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: The problem is reproducible runlevel: unknown type: CCpp uid: 1000
Answering the questions in https://bugzilla.redhat.com/show_bug.cgi?id=1320317#c25 would be nice rather than just adding the same information to the bug report... Additional questions would be whether ps aux |grep libvirtd shows one or 2 libvirtd running and whether /run/user/1000/libvirt/libvirt-sock exists
[mikhail@localhost ~]$ ps aux |grep libvirtd root 1165 0.5 0.1 894060 35272 ? Ssl 13:35 0:00 /usr/sbin/libvirtd mikhail 3552 0.0 0.0 117140 1004 pts/7 S+ 13:37 0:00 grep --color=auto libvirtd [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:4392): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:4392): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:4392): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead Error setting up default broker: Unable to open qemu+unix:///session: Failed to connect socket to '/run/user/1000/libvirt/libvirt-sock': No such file or directory ** Boxes:ERROR:app.c:3350:boxes_app_setup_default_source_co: assertion failed: (default_connection != null) Aborted (core dumped) [mikhail@localhost ~]$ ps aux |grep libvirtd root 1165 0.3 0.1 1221856 35280 ? Ssl 13:35 0:00 /usr/sbin/libvirtd mikhail 4490 1.3 0.0 783456 27212 ? Sl 13:38 0:00 /usr/sbin/libvirtd --timeout=30 mikhail 4748 0.0 0.0 117140 948 pts/7 S+ 13:38 0:00 grep --color=auto libvirtd [mikhail@localhost ~]$ gnome-boxes (gnome-boxes:5230): Gtk-WARNING **: Theme parsing error: gtk-style.css:76:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' (gnome-boxes:5230): Gtk-WARNING **: Theme parsing error: gtk-style.css:87:18: The 'outline-radius' property has been renamed to '-gtk-outline-radius' ** (gnome-boxes:5230): WARNING **: Using a file (/usr/share/gnome-boxes/gnome-boxes-logos-db.xml) as a database location is deprecated, use a directory instead (gnome-boxes:5230): Boxes-WARNING **: vm-creator.vala:117: Failed to start 'Microsoft Windows 7 Professional': Unable to start domain: operation failed: job: unexpectedly failed (gnome-boxes:5230): Libvirt.GLib-CRITICAL **: cannot finish stream: this function is not supported by the connection driver: virStreamFinish
$ ps aux |grep libvirtd root 1165 0.0 0.1 1418464 35280 ? Ssl 13:35 0:00 /usr/sbin/libvirtd mikhail 4490 0.1 0.1 1441516 35204 ? Sl 13:38 0:00 /usr/sbin/libvirtd --timeout=30 mikhail 11398 0.0 0.0 117140 972 pts/9 S+ 13:45 0:00 grep --color=auto libvirtd
Ok, so it looks like the second time libvirtd is running, is that correct? This really should be fixed by libvirt-1.3.3-1.fc24 , please add the version of the libvirt package that you are using
(In reply to Christophe Fergeau from comment #31) > Ok, so it looks like the second time libvirtd is running, is that correct? You ask me? I am don't know how many libvirtd processes should be launched. As you see I tried several attempts to run gnome-boxes. Before each run I checked how many `libvirtd` is launched. > This really should be fixed by libvirt-1.3.3-1.fc24 , please add the version > of the libvirt package that you are using $ rpm -qa | grep libvirt libvirt-client-1.3.3.1-3.fc24.x86_64 libvirt-daemon-driver-qemu-1.3.3.1-3.fc24.x86_64 libvirt-daemon-driver-storage-1.3.3.1-3.fc24.x86_64 libvirt-daemon-config-network-1.3.3.1-3.fc24.x86_64 libvirt-gconfig-0.2.3-2.fc24.x86_64 libvirt-gobject-0.2.3-2.fc24.x86_64 libvirt-daemon-driver-nodedev-1.3.3.1-3.fc24.x86_64 libvirt-daemon-driver-nwfilter-1.3.3.1-3.fc24.x86_64 libvirt-daemon-1.3.3.1-3.fc24.x86_64 libvirt-daemon-driver-interface-1.3.3.1-3.fc24.x86_64 libvirt-daemon-kvm-1.3.3.1-3.fc24.x86_64 libvirt-daemon-driver-network-1.3.3.1-3.fc24.x86_64 libvirt-glib-0.2.3-2.fc24.x86_64 libvirt-daemon-driver-secret-1.3.3.1-3.fc24.x86_64
(In reply to Mikhail from comment #32) > (In reply to Christophe Fergeau from comment #31) > > Ok, so it looks like the second time libvirtd is running, is that correct? > > You ask me? I am don't know how many libvirtd processes should be launched. > As you see I tried several attempts to run gnome-boxes. Before each run I > checked how many `libvirtd` is launched. > Sorry, this is not what I wanted to ask /o\ I meant that the second time libvirtd is running, and so starting up gnome-boxes should be working fine, it's just the first time that it dies and crash, is that correct? > > > This really should be fixed by libvirt-1.3.3-1.fc24 , please add the version > > of the libvirt package that you are using > > $ rpm -qa | grep libvirt > libvirt-client-1.3.3.1-3.fc24.x86_64 Ok, this should be new enough, so something weird is going on :((
> I meant that the second time > libvirtd is running, and so starting up gnome-boxes should be working fine, > it's just the first time that it dies and crash, is that correct? Yes, exactly. When gnome-boxes crashed we se only one process root 1165 0.5 0.1 894060 35272 ? Ssl 13:35 0:00 /usr/sbin/libvirtd When gnome-boxes launched fine we see two process root 1165 0.3 0.1 1221856 35280 ? Ssl 13:35 0:00 /usr/sbin/libvirtd mikhail 4490 1.3 0.0 783456 27212 ? Sl 13:38 0:00 /usr/sbin/libvirtd --timeout=30
Hmm this makes it really similar to https://bugzilla.redhat.com/show_bug.cgi?id=1271183 then, not sure why it's not fixed for you :(
You can get additional debugging by creating ~/.config/libvirt/libvirtd.conf as described here: http://libguestfs.org/guestfs-faq.1.html#debugging-libvirt Then when reproducing, run LIBVIRT_DEBUG=1 gnome-boxes, and attach both the /tmp/libvirtd.log and boxes DEBUG output. Though once this bug is resolved make sure you turn off the libvirtd.conf debugging since it's very noisy
Created attachment 1169477 [details] libvirtd.log
Created attachment 1169478 [details] boxes DEBUG output
Created attachment 1172184 [details] libvirtd.log
Created attachment 1172185 [details] boxes DEBUG output
Similar problem has been detected: I tried to start gnome-boxes, and it crashed a few seconds after it opened and before I could do anything. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 5305 kernel: 4.5.7-300.fc24.x86_64 package: gnome-boxes-3.20.2-3.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
I see lots of this in the libvirtd.log: 2016-06-25 07:55:42.600+0000: 3845: error : virPidFileAcquirePath:422 : Failed to acquire pid file '/run/user/1000/libvirt/libvirtd.pid': Resource temporarily unavailable But the times don't match up with the gnome-boxes attempt, at the libvirtd.log is confusing because there's multiple conflicting timestamps. I don't really know what's going on
Created attachment 1175456 [details] libvirtd.log
Created attachment 1175457 [details] boxes DEBUG output
Similar problem has been detected: Tried to start Boxes right after the login on Desktop reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 1971 kernel: 4.6.3-300.fc24.x86_64 package: gnome-boxes-3.20.2-4.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: The application shows a spinner for a while, then crashes. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: boxes_app_setup_default_source_co executable: /usr/bin/gnome-boxes global_pid: 4062 kernel: 4.6.3-300.fc24.x86_64 package: gnome-boxes-3.20.2-4.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-boxes killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
Created attachment 1180758 [details] Boxes running but not showing
After starting a VM you can see in the gnome-boxes window that it is running, but .. the vm window is not displayed. Output as requested in comment #31: [root@carbide ~] # ps aux |grep libvirtd root 2576 0.0 0.2 1424144 34648 ? Ssl 15:10 0:00 /usr/sbin/libvirtd leo 4858 0.2 0.2 1446360 36796 ? Sl 15:11 0:00 /usr/sbin/libvirtd --timeout=30 root 11738 0.0 0.0 118496 972 pts/2 S+ 15:14 0:00 grep --color=auto libvirtd [root@carbide ~] # ls /run/user/1000/libvirt/libvirt-sock /run/user/1000/libvirt/libvirt-sock see also attachment [Boxes running but not showing]
I saw this issue too after renaming the storage pool 'gnome-boxes' into 'default'. Renaming it back, solved the issue for me. Figured that out after using: $ gnome-boxes --checks • The CPU is capable of virtualization: yes • The KVM module is loaded: yes • Libvirt KVM guest available: yes • Boxes storage pool available: no Could not get 'gnome-boxes' storage pool information from libvirt. Make sure 'virsh -c qemu:///session pool-dumpxml gnome-boxes' is working. ...
*** Bug 1377813 has been marked as a duplicate of this bug. ***
*** Bug 1395367 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.