GNOME Bugzilla – Bug 749814
Crash when troubleshooting device
Last modified: 2018-01-11 10:18:37 UTC
In the last couple of versions of boxes I am not able to redirect any usb device. For some reason when I redirect them, the system is not able to find a proper driver for it. If I go to control panel -> devices, and I trouble shoot the device and apply the proposed fix, boxes will hang and crash at the end. (gnome-boxes:6507): GLib-GObject-WARNING **: The property GtkCellRendererPixbuf:follow-state is deprecated and shouldn't be used anymore. It will be removed in a future version. [New Thread 0x7fffcf9d6700 (LWP 6512)] [Thread 0x7fffcf9d6700 (LWP 6512) exited] Detaching after fork from child process 6677. (gnome-boxes:6507): GSpice-CRITICAL **: usbredirhost: error resetting device: LIBUSB_ERROR_NOT_FOUND (gnome-boxes:6507): GSpice-CRITICAL **: usbredirhost: error resetting device: LIBUSB_ERROR_NOT_FOUND [New Thread 0x7fffcf9d6700 (LWP 6783)] [New Thread 0x7fffcf1d5700 (LWP 6610)] [New Thread 0x7fffb7fff700 (LWP 6609)] [New Thread 0x7fffccec3700 (LWP 6519)] [New Thread 0x7fffcdfc6700 (LWP 6515)] Program received signal SIGPIPE, Broken pipe.
+ Trace 235088
Thread 140736676587264 (LWP 6783)
(In reply to Ignacio Casal Quinteiro (nacho) from comment #0) > In the last couple of versions of boxes I am not able to redirect any usb > device. For some reason when I redirect them, the system is not able to find > a proper driver for it. If I go to control panel -> devices, and I trouble > shoot the device and apply the proposed fix, boxes will hang and crash at > the end. What proposed patch? The usb issue is more of a spice-gtk bug and it has already been fixed. See bug#748797 for details.
"Apply fix" that is what Windows will tell you when you click on troubleshoot a device.
Should we mark this as dup then? See that I am running f22 so I guess it will come the fix for 3.18 or for the next patch release?
(In reply to Ignacio Casal Quinteiro (nacho) from comment #3) > Should we mark this as dup then? Not sure. So doing something from guest crashes Boxes? If so, can you see if qemu is crashed too? > See that I am running f22 so I guess it > will come the fix for 3.18 or for the next patch release? spice-gtk unfortunately do not follwing GNOME release cycle even though they really should (its not like they follow some other release cycle) but that's something I don't have control on. :( I did ping spice devs about release though and I'll ping again if they haven't released still.
(In reply to Zeeshan Ali (Khattak) from comment #4) > (In reply to Ignacio Casal Quinteiro (nacho) from comment #3) > > Should we mark this as dup then? > > > Not sure. So doing something from guest crashes Boxes? If so, can you see if > qemu is crashed too? Also need a more complete backtrace (one that shows the arguments passed to functions).
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/58.