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 706971 - SIGSEGV in gnome-settings-daemon
SIGSEGV in gnome-settings-daemon
Status: RESOLVED DUPLICATE of bug 706511
Product: gnome-settings-daemon
Classification: Core
Component: general
3.9.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2013-08-28 12:49 UTC by Dominique Leuenberger
Modified: 2013-09-05 18:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2013-08-28 12:49:10 UTC 
forwarded from https://bugzilla.novell.com/show_bug.cgi?id=837274

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/31.0.1612.1 Safari/537.36

I am testing openSUSE 13.1 Milestone 4 x86_64 with GNOME desktop in VirtualBox
4.2.16 r86992 on Windows 7 SP1 64 bit .
Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt .

2 times, /usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon crashed with
Segmentation fault in g_object_unref() at gobject.c:3086 .

> LANG=C ls -l /var/crash/core.gnome-settings-.1000.13775*
-rw------- 1 mitsutoshi users 60092416 Aug 26 17:52
/var/crash/core.gnome-settings-.1000.1377507164
-rw------- 1 mitsutoshi users 60104704 Aug 27 17:44
/var/crash/core.gnome-settings-.1000.1377593053

gnome-settings-daemon-3.9.3-2.2.x86_64.rpm
libnotify4-0.7.5-7.4.x86_64.rpm
libXtst6-1.2.2-1.2.x86_64.rpm
gnome-disk-utility-3.8.2-2.2.x86_64.rpm
libudisks2-0-2.1.0-1.5.x86_64.rpm
libwacom2-0.7.1-1.3.x86_64.rpm
libcolord1-1.0.2-1.2.x86_64.rpm
cups-libs-1.5.4-11.2.x86_64.rpm
krb5-1.11.3-2.2.x86_64.rpm
libcom_err2-1.42.8-1.3.x86_64.rpm
libkeyutils1-1.5.5-5.2.x86_64.rpm
libpackagekit-glib2-16-0.8.9-1.4.x86_64.rpm
libarchive13-3.1.1-2.2.x86_64.rpm
libattr1-2.4.47-1.3.x86_64.rpm



Reproducible: Sometimes

Steps to Reproduce:
1. Use openSUSE 13.1 Milestone 4 x86_64 with GNOME desktop .
Sorry, I do not understand how to reproduce this issue .

Actual Results:  
2 times, /usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon crashed with
Segmentation fault in g_object_unref() at gobject.c:3086 .


Expected Results:  
The gnome-settings-daemon should not crash .


the stack trace:
GNU gdb (GDB; openSUSE Factory) 7.5.50.20130215
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>...
Reading symbols from /usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon...Reading symbols from /usr/lib/debug/usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon.debug...done.
done.

warning: core file may not match specified executable file.
[New LWP 3301]
[New LWP 3313]
[New LWP 3319]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/lib/gnome-settings-daemon-3.0/gnome-settings-daemon'.
Program terminated with signal 11, Segmentation fault.

+ Trace 232426

Thread 1 (Thread 0x7f33d2298980 (LWP 3301))

  • #0 g_object_unref
    at gobject.c line 3086
  • #1 do_call
    at gdbusnameowning.c line 215
  • #2 ffi_call_unix64
    at ../../../libffi/src/x86/unix64.S line 75
  • #3 ffi_call
    at ../../../libffi/src/x86/ffi64.c line 492
  • #4 g_cclosure_marshal_generic
    at gclosure.c line 1454
  • #5 g_closure_invoke
    at gclosure.c line 777
  • #6 signal_emit_unlocked_R
    at gsignal.c line 3582
  • #7 g_signal_emit_valist
    at gsignal.c line 3326
  • #8 g_signal_emit
    at gsignal.c line 3382
  • #9 emit_closed_in_idle
    at gdbusconnection.c line 1389
  • #10 g_main_dispatch
    at gmain.c line 3064
  • #11 g_main_context_dispatch
    at gmain.c line 3640
  • #12 g_main_context_iterate
    at gmain.c line 3711
  • #13 g_main_loop_run
    at gmain.c line 3905
  • #14 gtk_main
    at gtkmain.c line 1157
  • #15 main
    at main.c line 479 
(gdb) quit
Comment 1 Rui Matos 2013-09-04 15:17:36 UTC 
This trace doesn't look good. It seems like it was generated from a core dump. Is there any chance of getting a better one?
Comment 2 Dominique Leuenberger 2013-09-05 18:31:49 UTC 
You mean from another / better crash? Or what are you missing?
Comment 3 Dominique Leuenberger 2013-09-05 18:42:33 UTC 
I see a segfault on gnome-settings-daemon on my system; trace looks different though:

Program terminated with signal 11, Segmentation fault.

+ Trace 232453

Thread 1 (Thread 0x7faccc9bc980 (LWP 18830))

  • #0 g_variant_ref_sink
    at gvariant-core.c line 705
  • #1 g_variant_new_variant
    at gvariant.c line 726
  • #2 g_variant_valist_new_leaf
    at gvariant.c line 4387
  • #3 g_variant_valist_new
    at gvariant.c line 4569
  • #4 g_variant_valist_new
    at gvariant.c line 4621
  • #5 g_variant_new_va
    at gvariant.c line 4778
  • #6 g_variant_builder_add
    at gvariant.c line 4930
  • #7 engine_properties_changed
    at gsd-rfkill-manager.c line 139
  • #8 rfkill_changed
    at gsd-rfkill-manager.c line 182
  • #9 g_cclosure_marshal_VOID__POINTERv
    at gmarshal.c line 1236
  • #10 _g_closure_invoke_va
    at gclosure.c line 840
  • #11 g_signal_emit_valist
    at gsignal.c line 3234
  • #12 g_signal_emit
    at gsignal.c line 3382
  • #13 emit_changed_signal_and_free
    at rfkill-glib.c line 172
  • #14 event_cb
    at rfkill-glib.c line 218
  • #15 g_main_dispatch
    at gmain.c line 3065
  • #16 g_main_context_dispatch
    at gmain.c line 3641
  • #17 g_main_context_iterate
    at gmain.c line 3712
  • #18 g_main_loop_run
    at gmain.c line 3906
  • #19 gtk_main
    at gtkmain.c line 1157
  • #20 main
    at main.c line 471 






Comment 4


Bastien Nocera





          2013-09-05 18:47:07 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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