After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757976 - Segmentation fault with GNOME Disks 3.18.1
Segmentation fault with GNOME Disks 3.18.1
Status: RESOLVED DUPLICATE of bug 787230
Product: gnome-disk-utility
Classification: Core
Component: general
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
Depends on:
Blocks:
 
 
Reported: 2015-11-12 09:37 UTC by John Doe
Modified: 2017-10-10 03:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb backtrace (2.95 KB, text/x-log)
2015-11-12 09:37 UTC, John Doe
Details
screenshot of disks (1.10 MB, image/png)
2015-11-12 09:38 UTC, John Doe
Details
gdb backtrace for gnome-disks (4.48 KB, text/plain)
2016-06-22 15:49 UTC, John Doe
Details

Description John Doe 2015-11-12 09:37:24 UTC
Created attachment 315311 [details]
gdb backtrace

I'm using GNOME 3.18.1 on a Parabola GNU/Linux-libre system.

Today I managed to make GNOME Disks crash while ejecting an USB flash drive. I successfully ejected it with Nautilus, then I went to Disks in order to power off the device. After having selected my device (Lexar USB Flash Drive) I clicked on the poweroff button on the top-right corner. I mean the button in the middle. And it crashed.

I'm going to attach both a screenshot and a backtrace obtained with gdb.
Comment 1 John Doe 2015-11-12 09:38:20 UTC
Created attachment 315312 [details]
screenshot of disks
Comment 2 Michael Catanzaro 2015-11-13 23:55:10 UTC
The backtrace is missing all but the last couple of frames. Please install debuginfo and take the backtrace again!
Comment 3 John Doe 2015-11-14 10:19:49 UTC
I can't find a package called debuginfo for my GNU/Linux distribution.

I simply edited the PKGBUILD file of the relevant packages and recompiled them with debugging information enabled and stripping of debug symbols disabled:

options=(debug !strip)

Unfortunately I also rebooted my computer since when I reported this bug, and I can't reproduce it anymore.
Comment 4 John Doe 2016-06-22 15:49:06 UTC
I experienced this bug again.

I tried to obtain a new backtrace but I still get "No symbol table info available" messages at the end of it. Someone on the #gdb IRC channel said me that it "looks more like a broken stack frame than missing debug info". I have no significant experience at debugging with gdb, so I don't know what I should do to fix this broken stack frame.

I'm going to post the new backtrace anyway.
Comment 5 John Doe 2016-06-22 15:49:41 UTC
Created attachment 330199 [details]
gdb backtrace for gnome-disks
Comment 6 John Doe 2016-06-22 21:47:43 UTC
The new backtrace I posted was produced with the following package versions:

gnome-disk-utility-3.20.1-1
glibc-2.23-1
glib2-2.48.0-1
udisks2-2.1.7-1

In addition to options 'debug' and '!strip' I also rebuilt those packages with the following variables:

export CFLAGS="$CFLAGS -O0 -fbuiltin -g"
export CXXFLAGS="$CXXFLAGS -O0 -fbuiltin -g"
Comment 7 Michael Catanzaro 2016-06-23 01:39:10 UTC
I don't know how to help with this, sorry. In Fedora, gdb will give you a dnf debuginfo-install command you can use to install all relevant debuginfo; it only takes a couple seconds, doesn't require thinking, and doesn't require rebuilding anything.

I searched for udisks_object_get_partition_table on codesearch.debian.net and the only hits were from udisks itself and gnome-disks, so we can be reasonably sure the next frame is gnome-disks. Why it's not appearing in the backtrace, I don't know. Maybe #gdb is right that it's a broken stack; I'm not really sure what that entails or what could cause it, though.

But don't waste too much effort on this; to be perfectly honest, nobody is working on GNOME Disks or udisks right now, so it's not very likely your crash would be fixed even if you did manage to post a useful backtrace. Sorry. :/
Comment 8 Kai Lüke 2017-10-10 03:46:07 UTC
I think this is a variant of this fixed bug.

*** This bug has been marked as a duplicate of bug 787230 ***