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

[Richard Mote]

Binary package hint: gnome-settings-daemon

Crashed upon resetting screen resolution to correct error in screen size (screen edges display past actual edge of screen, shifting to allow display when mouse reaches actual screen edge).

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: nvidia
Package: gnome-settings-daemon 2.23.6-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCwd: /
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 xkl_process_error () from /usr/lib/libxklavier.so.12
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:_gdk_region_get_xrectangles (region=0x9407100, x_offset=-1074568408, y_offset=200, rects=0xb6337fe0,
xkl_process_error (dpy=0x9407100, evt=0xbff36328) at xklavier_evt.c:513
_XError (dpy=0x9407100, rep=0x9557060) at ../../src/XlibInt.c:2912
process_responses (dpy=0x9407100, wait_for_first_event=0, current_error=0xbff36428, current_request=1201)
_XReply (dpy=0x9407100, rep=0xbff3645c, extra=0, discard=0) at ../../src/xcb_io.c:370

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=546760

[Martin Pitt (pitti)]

Confirmed, apport just reported the same on my system.

[Mahesh Asolkar (asolkar)]

Apport just reported this for me for the first time. Although I have seen similar symptoms before, without apport detecting any thing.

Sometimes after logging in, my appearance settings are all messed up - theme, decoration etc. When I open the Appearance preferences, they come back to normal. HTH.

[Jamie Strandboge (jdstrand)]

apport just reported the same on my system.

[Jamie Strandboge (jdstrand)]

Upstream bug report mentioned it might be X related, so I'll mention I saw this on Intrepid with an ATI Radeon Mobility M7 LW [Radeon Mobility 7500].

[Haico van Roeden (brainball)]

I got the same report, also on Intrepid but with an Nvidia Geforce 6800

[Marco R. (smandrake93)]

I'd got the same report, i'm using Intrepid with ATI Mobility Radeon X700.

[KIAaze (zohn-joidberg)]

I have the same bug as Mahesh Asolkar: theme completely messed up sometimes. Opening appearance preferences brings things back to normal.
Apport reported the same message as here.

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 330M/340M/350M
        Subsystem: Hewlett-Packard Company Device 0850
        Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 10
        Memory at d8000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 9000 [size=256]
        Memory at d0300000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at d0320000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel modules: radeonfb

lsb_release -a
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:cxx-3.0-ia32:cxx-3.0-noarch:cxx-3.1-ia32:cxx-3.1-noarch:cxx-3.2-ia32:cxx-3.2-noarch:desktop-3.1-ia32:desktop-3.1-noarch:desktop-3.2-ia32:desktop-3.2-noarch:graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch:graphics-3.1-ia32:graphics-3.1-noarch:graphics-3.2-ia32:graphics-3.2-noarch:languages-3.2-ia32:languages-3.2-noarch:multimedia-3.2-ia32:multimedia-3.2-noarch:printing-3.2-ia32:printing-3.2-noarch:qt4-3.1-ia32:qt4-3.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid

[tuxidermiste (tuxidermiste)]

Got the same on an nVidia 5600.

When the bug occur, the theme crash and is replaced by a default windows-like theme (really special I have'nt seen it before).

[nicksk (nicksk-deactivatedaccount)]

I got the same bug on Intrepid Alpha 3. Theme changes to some default type.

[wilbur.harvey (wilbur-harvey)]

Running today's latest update as of an hour ago.
Same crash when re-starting X.
I have seen the same problem with defaulting to another window manager than Gnome, but rebooting the computer seems to get around that.
I am using a MacBook Pro, V2 with the ATI graphics.
One other problem is that objects can only be dragged part way across the second screen connected to the DVI port.

[Andrew (keen101)]

Running Ibex off my external hard drive. Things keep crashing. This is one of them. It asked if i wanted to report it, so i said yes. Aug/16/2008

[aschuring (aelschuring)]

can this possibly be a duplicate of #254671 ?

The backtrace listed above is incomplete, but it seems to be following the same codepath as the aforementioned bug. The only difference I can see is that this bug is not triggered automatically on login, is that correct?

[Excentrik (excentrik)]

I got the same report using Intrepid Alpha 4 with ATI Mobility Radeon X700.
It occured when trying to change theme in the Appearance window.

[John Vivirito (gnomefreak)]

I got this crash during gnome loading. I see users are seeing this when opening an appearance app (sreensavers, anything that gnome appearance settings is in control of).
Excentrik, they should be marked as dupes (this bug and bug #254671, they both are same upstream bug. , but im not real sure since Sebastien looked at both and didnt mark them as dupes.

[John Vivirito (gnomefreak)]

after restarting GDM it works, restarted using /etc/init.d/gdm restart.

[Antono Vasiljev (antono)]

after upgrade to Interpid I got the same bug on MacBook2,1 (version 1.0) with Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller