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

Bug #327547 reported by Nizar Kerkeni
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

ubuntu jaunty alpha 4, 64 bits.
Crash after logging in gnome session.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: nvidia
Package: gnome-settings-daemon 2.25.3-0ubuntu2
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.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
 _XReply () from /usr/lib/libX11.so.6
 XGetWindowProperty () from /usr/lib/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Nizar Kerkeni (nizarus) wrote :

I don't know if it's related but at each connection I have this error message :
"Could not apply the stored configuration for monitors
Erreur à la ligne 1, caractère 2 : Texte codé en UTF-8 non valide - «  » est non valide"
a fast translation :
Error on line 1, character 2 : Invalid text coded in UTF-8 - «  » is invalid.

Revision history for this message
Nizar Kerkeni (nizarus) wrote :

This bug is marked as a duplicate of bug #254671, but that bug is marked as fixed.

Revision history for this message
Graziano (graziano-giuliani-gmail) wrote :

Can confirm this still happens on jaunty as of today. Think duplicate status is wrong OR the bug is still not fixed as reported in bug #254671.

Revision history for this message
dmatthys (derek-matthysfamily) wrote :

I would agree for it not being corrected in jaunty yet i read the other one and it says after the update it was corrected i ran an update 10 minutes ago says my system is up to date but it still happened

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.