gnome-settings-daemon crashed with signal 5 in gdk_x_error()

Bug #510629 reported by Atanas Atanasov
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

Crashed while using firefox.

ProblemType: Crash
Architecture: amd64
Date: Thu Jan 21 07:50:17 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Package: gnome-settings-daemon 2.29.5-0ubuntu1
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_US.UTF-8:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 gdk_x_error (display=<value optimized out>,
 xkl_process_error () from /usr/lib/libxklavier.so.16
 _XError () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XQueryTree () from /usr/lib/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.32-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev plugdev powerdev sambashare scanner video

Revision history for this message
Atanas Atanasov (thenasko) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_x_error (display=<value optimized out>,
 xkl_process_error (dpy=0xe2cc30, evt=0x7fff0a503d50)
 _XError (dpy=0xe2cc30, rep=0x1122600)
 _XReply (dpy=0xe2cc30, rep=<value optimized out>,
 XQueryTree (dpy=0xe2cc30, w=81789145,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
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.