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

Bug #830264 reported by Sam_
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Did lots of workspace switching due to testing another bug. The last was testing available alt+tab keys. Again switching workspaces freezes workspace switcher, no mouse or shortcut worked. After a while apport dialog opened top left corner under the panel, but buttons to send the report were accessible. (Forgot to make a screenshot there.)

There have been other reports which are either closed, expired or fixed. (screenshot)
The newest Bug #825073 wasn't among them, it was found through searching bug reports.
Since bug triage Wiki says coredump needs to be removed first to make a report public I didn't make it a dupe yet.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sat Aug 20 23:22:09 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110423)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 xkl_process_error () from /usr/lib/libxklavier.so.16
 _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
UpgradeStatus: Upgraded to oneiric on 2011-08-01 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Sam_ (and-sam) wrote :
Revision history for this message
Sam_ (and-sam) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (3.6 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.6.1-7ubuntu1 required, but 1:4.6.1-7ubuntu2 is available
outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libslang2: package version 2.2.4-2ubuntu1 dbgsym version 2.2.2-4ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
outdated debug symbol package for libnih1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for dbus: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
outdated debug symbol package for busybox-initramfs: package version 1:1.18.4-2ubuntu1 dbgsym version 1:1.17.1-10ubuntu1
gnome-settings-daemon version 3.1.4-0ubuntu3 required, but 3.1.5-0ubuntu5 is available
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
libudev0 version 173-0ubuntu2 required, but 173-0ubuntu3 is available
udev version 173-0ubuntu2 required, but 173-0ubuntu3 is available
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
libnotify4 version 0.7.3-1 required, but 0.7.3-2 is available
outdated debug symbol package for x11-xkb-utils: package version 7.6+4 dbgsym version 7.6+2
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
libklibc version 1.5.22-1ubuntu1 required, but 1.5.22-1ubuntu2 is available
outdated debug symbol package for libdbus-1-3: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
libcups2 version 1.5.0-4 required, but 1.5.0-5 is available
libc-bin version 2.13-16ubuntu4 required, but 2.13-17ubuntu2 is available
libffi6 version 3.0.10~rc8-6 required, but 3.0.11~rc1-1 is available
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
gcc-4.6-base version 4.6.1-7ubuntu1 required, but 4.6.1-7ubuntu2 is available
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for procps: package version 1:3.2.8-10ubuntu5 dbgsym version 1:3.2.8-10ubuntu3
ifupdown version 0.7~alpha5.1ubuntu2 required, but 0.7~alpha5.1ubuntu3 is available
outdated debug symbol package for libkrb5support0: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libnih-dbus1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for ncurses-bin: package version 5.9-1 dbgsym version 5.7+20101128-1
multiarch-support version 2.13-16ubuntu4 required, but 2.13-17ubuntu2 is available
libc6 version 2.13-16ubuntu4 requ...

Read more...

tags: removed: need-amd64-retrace
Revision history for this message
Sam_ (and-sam) wrote :

Mmh, actually the system is up-to-date and I've followed suggestion #1 there creating an /etc/apt/sources.list.d/ddebs.list.
https://wiki.ubuntu.com/DebuggingProgramCrash

Sam_ (and-sam)
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.