gnome-settings-daemon crashed with SIGSEGV in xkl_engine_ensure_vtable_inited()

Bug #546927 reported by Jan Hülsbergen
240
This bug affects 42 people
Affects Status Importance Assigned to Milestone
libgnomekbd
Fix Released
Medium
libgnomekbd (Ubuntu)
Fix Released
Medium
Unassigned
Lucid
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

switched the theme in 'Appearance', then came the crash (new theme was visible just a fraction of a second)

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 25 15:22:37 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Package: gnome-settings-daemon 2.29.92-0ubuntu3
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x7fd828a65ea4 <xkl_engine_ensure_vtable_inited+4>: mov 0x18(%rdi),%rax
 PC (0x7fd828a65ea4) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 xkl_engine_ensure_vtable_inited ()
 xkl_engine_get_num_groups ()
 ?? () from /usr/lib/libgnomekbdui.so.4
 gkbd_status_reinit_ui ()
 g_closure_invoke ()
Title: gnome-settings-daemon crashed with SIGSEGV in xkl_engine_ensure_vtable_inited()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jan Hülsbergen (jan-afoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 xkl_engine_ensure_vtable_inited (engine=0x0) at xklavier.c:508
 xkl_engine_get_num_groups (engine=0x0)
 gkbd_status_fill (gki=<value optimized out>)
 gkbd_status_reinit_ui (gki=0x239f650)
 g_closure_invoke ()

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):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Jan Hülsbergen (jan-afoo) wrote :

just wanted to add a note that this keeps happening to me at least a few times a day

visibility: private → public
Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Same for me here on i386 and Kernel 2.6.32-19-generic.

Revision history for this message
Jan Hülsbergen (jan-afoo) wrote :

one of the updates over the last few days seems to have fixed this for me. Don't know about the other 8 people so I'm not closing the bug.

Revision history for this message
Tordj (tord-jansson) wrote :

Got exactly the same crash on April 5, with the exception that I was NOT playing around with themes, I was installing Ubuntu Restricted Extras from Synaptics.

My original bug report is available here: https://bugs.launchpad.net/bugs/555555

Revision history for this message
wilfred_com (wilfredcom) wrote :

I'm doing a simple installation:

sudo aptitude install quanta

affects: gnome-settings-daemon (Ubuntu) → libgnomekbd (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Changed in libgnomekbd (Ubuntu):
status: New → Triaged
Changed in libgnomekbd:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream bug comment

"Would it be possible to run (and crash!) g-s-d with --nodaemon and
XKL_DEBUG=160? Please attach the resulting output here (especially the lines
before the crash)."

Changed in libgnomekbd (Ubuntu):
status: Triaged → Incomplete
Changed in libgnomekbd:
status: New → Incomplete
Revision history for this message
Hansen (moteprime) wrote :

 " "Would it be possible to run (and crash!) g-s-d with --nodaemon and XKL_DEBUG=160? Please attach the resulting output here (especially the lines before the crash)." "

I would be happy to try, but i need at more information about how to do it.

Revision history for this message
Louis Simard (louis-simard-deactivatedaccount) wrote :

@mote: At a terminal, type

XKL_DEBUG=160 gnome-settings-daemon --no-daemon

Revision history for this message
Louis Simard (louis-simard-deactivatedaccount) wrote :

Instructions for reproducing this bug:

1. Boot Ubuntu 10.04 from the LiveCD. Don't change the language; leave it as English. This will make the default keyboard layout "USA" later.
2. Wait for the GNOME desktop to fully load.
3. System > Preferences > Keyboard. Select the Layouts tab, add a random layout, then remove "USA". Click Close. (Not removing the first layout works around this bug.)
4. System > Preferences > Appearance. Change ANYTHING. (Change the theme, or the desktop background, or the font.)
5. Asynchronous crash of gnome-settings-daemon. It takes 5 seconds usually, but after this, the theme changes to something like Redmond in all applications.

I think "XKL_DEBUG=160 gnome-settings-daemon --no-daemon" should be typed before Step 3 above.

Revision history for this message
Louis Simard (louis-simard-deactivatedaccount) wrote :
Changed in libgnomekbd (Ubuntu):
status: Incomplete → Confirmed
Changed in libgnomekbd (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgnomekbd - 2.30.2-0ubuntu1

---------------
libgnomekbd (2.30.2-0ubuntu1) maverick; urgency=low

  * New upstream version:
    A couple of translations updated
    Proper location in NA is provided
    Fixed three crashers (lp: #546927)
  * debian/patches/02_layout_crash.patch:
    - the change is in the new version
 -- Sebastien Bacher <email address hidden> Tue, 22 Jun 2010 23:41:03 +0200

Changed in libgnomekbd (Ubuntu):
status: Fix Committed → Fix Released
Changed in libgnomekbd (Ubuntu Lucid):
importance: Undecided → Low
status: New → Fix Committed
Changed in libgnomekbd:
status: Incomplete → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted libgnomekbd into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Louis Simard (louis-simard-deactivatedaccount) wrote :

Using the instructions from comment 14, I can reproduce this crash in lucid main, but not in lucid proposed.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libgnomekbd - 2.30.2-0ubuntu0.1

---------------
libgnomekbd (2.30.2-0ubuntu0.1) lucid-proposed; urgency=low

  * New upstream version:
    A couple of translations updated
    Proper location in NA is provided
    Fixed three crashers (lp: #546927)
  * debian/patches/02_layout_crash.patch:
    - the change is in the new version
 -- Sebastien Bacher <email address hidden> Tue, 22 Jun 2010 23:41:03 +0200

Changed in libgnomekbd (Ubuntu Lucid):
status: Fix Committed → Fix Released
Changed in libgnomekbd:
importance: Unknown → Medium
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.