Bug 657465 – gnome-settings-daemon crashed with SIGSEGV in idle_is_session_inhibited()

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 657465 - gnome-settings-daemon crashed with SIGSEGV in idle_is_session_inhibited()


Summary:	gnome-settings-daemon crashed with SIGSEGV in idle_is_session_inhibited()


Status:	RESOLVED INCOMPLETE

Product:	gnome-settings-daemon
Classification:	Core
Component:	power
Version:	2.29.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Richard Hughes
QA Contact:	gnome-settings-daemon-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-08-26 18:31 UTC by Pedro Villavicencio
Modified:	2011-10-21 05:51 UTC

See Also:
GNOME target:	---
GNOME version:	3.1/3.2

Description Pedro Villavicencio 2011-08-26 18:31:57 UTC

this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/834234

".

+ Trace 228235

Thread 1 (Thread 0xb76fe840 (LWP 1277))

#0 idle_is_session_inhibited
at gsd-power-manager.c line 2665
#1 idle_evaluate
at gsd-power-manager.c line 2704
#2 idle_evaluate
at gsd-power-manager.c line 2679
#3 g_cclosure_marshal_VOID__UINT
at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c line 259
#4 g_closure_invoke
at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c line 773
#5 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3271
#6 g_signal_emit_valist
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3002
#7 g_signal_emit
at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c line 3059
#8 gpm_idletime_event_filter_cb
at gpm-idletime.c line 271
#9 gpm_idletime_event_filter_cb
at gpm-idletime.c line 244
#10 gdk_event_apply_filters
at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 83
#11 gdk_event_source_translate_event
at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 197
#12 _gdk_x11_display_queue_events
at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 334
#13 gdk_display_get_event
at /build/buildd/gtk+3.0-3.1.12/./gdk/gdkdisplay.c line 311
#14 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.1.12/./gdk/x11/gdkeventsource.c line 356
#15 g_main_dispatch
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 2439
#16 g_main_context_dispatch
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3008
#17 g_main_context_iterate
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3086
#18 g_main_loop_run
at /build/buildd/glib2.0-2.29.16/./glib/gmain.c line 3294
#19 gtk_main
at /build/buildd/gtk+3.0-3.1.12/./gtk/gtkmain.c line 1367
#20 main
at main.c line 451

Comment 1 Bastien Nocera 2011-08-31 10:11:41 UTC

This is where it crashes:
http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/power/gsd-power-manager.c?id=a9756f7e5ef5777fbdca302919bfbeb35e76f6b3#n2656

This means that the error is NULL, but error is not set. So a bug in GDBus.

glib is at 2.29.16

Comment 2 David Zeuthen (not reading bugmail) 2011-09-01 18:15:51 UTC

(In reply to comment #1)
> This is where it crashes:
> http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/power/gsd-power-manager.c?id=a9756f7e5ef5777fbdca302919bfbeb35e76f6b3#n2656
> 
> This means that the error is NULL, but error is not set. So a bug in GDBus.
> 
> glib is at 2.29.16

I'm not sure how you infer this - at least it's not clear to me after spending 5+ minutes reading through the traces - for all we know, this could just as well be memory corruption. Please don't reassign bugs without more explanation, thanks! (I'm happy to help debugging)

Comment 3 Richard Hughes 2011-09-07 16:13:15 UTC

Pedro, does this happen with gnome-settings-daemon 3.1.90 or 3.1.91? Have you tried running gnome-settings-daemon under valgrind to see if it's indeed memory corruption? Thanks.

Comment 4 Pedro Villavicencio 2011-09-07 16:52:26 UTC

Richard last dupe we have is with 3.1.90, I'm asking the users to try to reproduce it with 3.1.91 and provide the valgrind log, will come back with info shorly, thanks!.

Comment 5 Akhil Laddha 2011-10-21 05:51:01 UTC

downstream bug report has been closed.