GNOME Bugzilla – Bug 762703
Nautilus crashing when trying to open loopback device
Last modified: 2016-03-07 11:33:47 UTC
When I mount any ISO as loopback device through gnome-disk-utility(equivalent to udisksctl loop-setup -f --file), and trying to open in Nautilus, then it fails. dmesg nautilus[2087]: segfault at ffffffffffffffd0 ip 00007f1421e9a2a9 sp 00007ffef3fe2a90 error 5 in libgtk-3.so.0.1910.0[7f1421d1a000+703000]
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Created attachment 322496 [details] Nautilus stack trace
Also, I can not open my USB flash drive and SD card.
Created attachment 323251 [details] [review] content-bar: move content type handling to nautilus-file All the other content type functions are there, and we will need it anyway in an upcoming patch.
Created attachment 323252 [details] [review] content-bar: move more content type handling And rely on file-utilities to check whether we can should handle those mime types.
Created attachment 323253 [details] [review] window-slot: only create x-content-bar if necessary We were creating the x-content-bar every time, then the content bar was destroying itself (?) if no content type could be handled. Just avoid to create the content bar if no necessary.
Created attachment 323254 [details] [review] content-bar: don't auto destroy the widget We were auto destroying the content bar if the mime type couldn't be handled. This is wrong since the caller is not aware of anything, trying to show or do other things with the destroyed widget. I'm not sure how this even work, if it worked at all. Previously it wasn't crashing because gtk+ was failing gratefully, however, with the gadget rework, this makes gtk+ crash. We fixed this in the previous patch, only creating the content bar if we can handle the myme types. This patch adds a few more guards and, in any case, avoid to destroy the widget inside the widget itself.
Attachment 323251 [details] pushed as 50298ac - content-bar: move content type handling to nautilus-file Attachment 323252 [details] pushed as 9c54dea - content-bar: move more content type handling Attachment 323253 [details] pushed as a974938 - window-slot: only create x-content-bar if necessary Attachment 323254 [details] pushed as afdc6f9 - content-bar: don't auto destroy the widget