Version-Release number of selected component: gnome-boxes-3.14.2-2.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: spice_usb_device_manager_stop_event_listening executable: /usr/bin/gnome-boxes kernel: 3.17.8-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (9 frames) #0 spice_usb_device_manager_stop_event_listening at usb-device-manager.c:1228 #1 spice_usbredir_channel_disconnect_device at channel-usbredir.c:422 #2 spice_usbredir_channel_reset at channel-usbredir.c:121 #3 channel_disconnect at spice-channel.c:2646 #4 spice_channel_coroutine at spice-channel.c:2430 #5 coroutine_trampoline at coroutine_ucontext.c:63 #6 continuation_trampoline at continuation.c:55 #7 ?? at /lib64/libc.so.6 #8 ??
Created attachment 982041 [details] File: backtrace
Created attachment 982042 [details] File: cgroup
Created attachment 982043 [details] File: core_backtrace
Created attachment 982044 [details] File: dso_list
Created attachment 982045 [details] File: environ
Created attachment 982046 [details] File: exploitable
Created attachment 982047 [details] File: limits
Created attachment 982048 [details] File: maps
Created attachment 982049 [details] File: open_fds
Created attachment 982050 [details] File: proc_pid_status
Created attachment 982051 [details] File: var_log_messages
This bug is very likely to occur when I close Boxes.
Another user experienced a similar problem: Ben bezig een Windows Vista te voltooien. Op het punt dat de installatie de eerste keer automatisch wil herstarten valt Gnome-Boxes uit. Na herstarten van Gnome-Boxes kan ik gelukkig gewoon doorgaan met de installatie. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes --gapplication-service crash_function: spice_usb_device_manager_stop_event_listening executable: /usr/bin/gnome-boxes kernel: 3.18.7-200.fc21.x86_64 package: gnome-boxes-3.14.3.1-1.fc21 reason: gnome-boxes killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** This bug has been marked as a duplicate of bug 1182226 ***