Bug 84314 - random crash (SIGSEGV)
Summary: random crash (SIGSEGV)
Status: RESOLVED NOTOURBUG
Alias: None
Product: udisks
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: David Zeuthen (not reading bugmail)
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-25 08:21 UTC by Paul Wise
Modified: 2015-06-30 05:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Crash dump (21.50 KB, text/plain)
2014-09-25 08:21 UTC, Paul Wise
Details

Description Paul Wise 2014-09-25 08:21:40 UTC
Created attachment 106835 [details]
Crash dump

I got this random crash using udisks2 2.1.3-3 on Debian jessie. No idea what I was doing at the time though. gdb trace attached.
Comment 1 Ivailo Monev 2014-11-05 15:11:37 UTC
Maybe this is relevant to the issue: https://bugzilla.gnome.org/show_bug.cgi?id=707298. Apparently, there has been a bug in glib-2.40 which is fixed in glib-2.40.1. Does the following work for you:

LD_PRELOAD=/usr/lib/libgobject-2.0.so.0 /usr/lib/udisks2/udisksd

?
Comment 2 Paul Wise 2014-11-05 23:30:00 UTC
The crash was random, no idea what triggered it so it isn't possible to reproduce it. Debian jessie has now moved on to glib 2.42.0-2 so the issue you mentioned is no longer relevant. Checking my mail archives and logs, the last new udisks crash was 2014-09-26 and I upgraded from glib 2.40.0-5 to 2.42.0-1 on 2014-09-29. So I think it is plausible that this is fixed already. If you agree or don't think the backtrace is useful, feel free to close the bug.
Comment 3 Martin Pitt 2015-06-30 05:43:08 UTC
This crashed deep in glib's own signal/thread handling, there's no udisks code in the stack trace. So indeed, let's blame that glib fix as you didn't get further crashes since then. Thanks for checking!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.