gnome-appearance-properties crashed with SIGSEGV

Bug #123207 reported by Jurriaan
10
Affects Status Importance Assigned to Milestone
gtk-qt-engine (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-control-center

Just update to gutsy..
You can reproduce this bug by starting gnome-appearance-properties, it happens every time :(

ProblemType: Crash
Architecture: i386
Date: Sat Jun 30 11:35:16 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-appearance-properties
NonfreeKernelModules: nvidia
Package: gnome-control-center 1:2.19.4-0ubuntu4
PackageArchitecture: i386
ProcCmdline: gnome-appearance-properties
ProcCwd: /home/jurp5
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/var/lib/gems/1.8/bin
 LANG=nl_NL.UTF-8
Signal: 11
SourcePackage: gnome-control-center
Stacktrace:
 #0 0xb68eac00 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libhcengine.so
 #1 0xb78733a1 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
 #2 0xbfae8778 in ?? ()
 #3 0x081cfa88 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libhcengine.so
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: gnome-appearance-properties crashed with SIGSEGV
Uname: Linux jurp5-desktop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: pulse

Tags: apport-crash
Revision history for this message
Jurriaan (jurriaan) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
gdk_event_apply_filters (xevent=0xbfae8778, event=0x81cfa88, filters=0x8474790) at /build/buildd/gtk+2.0-2.11.4/gdk/x11/gdkevents-x11.c:344
gdk_event_translate (display=0x808e020, event=0x81cfa88, xevent=0xbfae8778, return_exposes=0)
_gdk_events_queue (display=0x808e020) at /build/buildd/gtk+2.0-2.11.4/gdk/x11/gdkevents-x11.c:2283
gdk_event_dispatch (source=0x8097fc0, callback=0, user_data=0x0) at /build/buildd/gtk+2.0-2.11.4/gdk/x11/gdkevents-x11.c:2343

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-control-center:
importance: Undecided → Medium
Revision history for this message
Dailos (dfranchy) wrote :

I had the same problem (same backtrace) with a user migrated though several Ubuntu releases. I found that changing ShowIconsOnPushButtons=false to true in config file .kde/share/config/kdeglobals avoids the crash for me. Not a fix, obviously, but maybe a hint.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Do you have gtk-qt-engine installed? Does it happen without it

Changed in gnome-control-center:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Paysen (johannes-paysen) wrote : AW: [Bug 123207] Re: gnome-appearance-properties crashed with SIGSEGV

Hi Sebastien,

yes the gtk-gt-engine is installed!

Bye, Johannes

-----Ursprüngliche Nachricht-----
Von: <email address hidden> [mailto:<email address hidden>] Im Auftrag von
Sebastien Bacher
Gesendet: Freitag, 10. August 2007 17:45
An: <email address hidden>
Betreff: [Bug 123207] Re: gnome-appearance-properties crashed with SIGSEGV

Thank you for your bug. Do you have gtk-qt-engine installed? Does it happen
without it

** Changed in: gnome-control-center (Ubuntu)
     Assignee: (unassigned) => Ubuntu Desktop Bugs
       Status: New => Incomplete

--
gnome-appearance-properties crashed with SIGSEGV
https://bugs.launchpad.net/bugs/123207
You received this bug notification because you are a direct subscriber of
the bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does it happen if you uninstall it?

Revision history for this message
nanog (sorenimpey) wrote :

I had a similar problem after updating a box to gutsy.
Example of apport.log:
apport (pid 15562) Thu Aug 23 16:13:58 2007: called for pid 15414, signal 11
apport (pid 15562) Thu Aug 23 16:13:58 2007: executable: /usr/lib/gnome-control-center/gnome-settings-daemon (command line "/usr/lib/gnome-control-center/gnome-settings-daemon")
apport (pid 15562) Thu Aug 23 16:13:58 2007: apport: report /var/crash/_usr_lib_gnome-control-center_gnome-settings-daemon.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
apport (pid 15623) Thu Aug 23 16:14:00 2007: called for pid 15548, signal 11
apport (pid 15623) Thu Aug 23 16:14:00 2007: executable: /usr/lib/gnome-applets/trashapplet (command line "/usr/lib/gnome-applets/trashapplet --oaf-activate-iid=OAFIID:GNOME_Panel_TrashApplet_Factory --oaf-ior-fd=25")
apport (pid 15623) Thu Aug 23 16:14:00 2007: apport: report /var/crash/_usr_lib_gnome-applets_trashapplet.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
apport (pid 15669) Thu Aug 23 16:14:01 2007: called for pid 15585, signal 11
apport (pid 15669) Thu Aug 23 16:14:01 2007: executable: /usr/lib/gnome-control-center/gnome-settings-daemon (command line "/usr/lib/gnome-control-center/gnome-settings-daemon")

Although its probably unrelated I had noted that this warning came up during the dist-upgrade "X Error: BadDevice, invalid or uninitialized input device 158".
It seems to have been caused by my forgetting to remove Virtualbox.

I removed virtualbox, auto-removed and a large set of gdm-related files were removed.
No more crashing gdm settings daemon and trashcan applet.

I've attached the crash log referenced in apport.

Let me know if I can be of further assistance.

Changed in gnome-control-center:
assignee: desktop-bugs → nobody
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try if that's still an issue on hardy?

Revision history for this message
Jurriaan (jurriaan) wrote :

I'm using Hardy since the beginning and never had a problem with this anymore. I think it's fixed somewhere..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.