[apport] gnome-keyboard-properties crashed with SIGSEGV in draw_key() when trying to add new layout.

This has been tagged 'need-amd64-retrace', however the trace I gave is from an AMD-64 system. How do I generate what is needed? Do I need a special debug version of the packages or something?

There is an automatic service running and retracing bugs tagged, you don't need to do anything

Thanks for your bug report.

StacktraceTop:draw_key (drawing=0x9e78f0, key=<value optimized out>) at gkbd-keyboard-drawing.c:616
IA__g_list_foreach (list=<value optimized out>, func=0x2afd34f035f0 <draw_keyboard_item>, user_data=0x9e78f0) at glist.c:495
idle_redraw (user_data=0xa28bf0) at gkbd-keyboard-drawing.c:993
IA__g_main_context_dispatch (context=0x659190) at gmain.c:2045
g_main_context_iterate (context=0x659190, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2677

Thanks for your bug report. New packages version have been uploaded since you opened it, could you try if you still get the issue and attach a new crash file if that's the case?

Just ran into this problem on a fully updated AMD64 running Feisty myself. Attached is the core dump from gdb (apport didn't catch it), backtrace is coming. Need this functionality to work around a bug when running full-screen games under Cedega (us-intl layout doesn't work right).

To reproduce, open gnome-keyboard-properties, click "Layouts", click "Add". Program dies every time. Following is the output from the terminal, which may also help:

mbt@sage:~$ gnome-keyboard-properties
dpy: 0x63f8f0
evt/error/major/minor: 113/174/1/0

(gnome-keyboard-properties:14444): GnomeKbdIndicator-WARNING **: key AE00: keycode = 4294967295; not in range 8..255

Segmentation fault (core dumped)
mbt@sage:~$

Additional information provided along with how to reproduce, core dump, backtrace. Problem still exists as of 14-Apr-2007 with fully updated Feisty.

I've opened a bug upstream: http://bugzilla.gnome.org/show_bug.cgi?id=429907

Additional information:

Today, I was playing around in this and found that if I changed the keyboard from Microsoft Natural (which is what I have) to a generic 105-key international keyboard, I am able to add the second layout that I need. Paul, is your selected keyboard in this a MS Natural keyboard, or something different? If it is the natural keyboard, does the problem persist if you change it to a generic keyboard?

I actually have the "Microsoft Natural Keyboard Pro USB / Microsoft Internet Keyboard Pro", but I suspect that it is the non-square layout that is causing the problem... Switching to generic did indeed solve the problem.

This is with:
Package: gnome-control-center
Source: control-center
Version: 1:2.18.1-0ubuntu2

I have a similar problem too. I'm using a fresh Feisty Fawn installation (AMD64 release version). Here's the error:

vitor@obiwankenobi:~$ gnome-keyboard-properties
dpy: 0x63f240
evt/error/major/minor: 113/174/1/0

(gnome-keyboard-properties:8000): GnomeKbdIndicator-WARNING **: key HZTG: keycode = 4294967295; not in range 8..255

(gnome-keyboard-properties:8000): GnomeKbdIndicator-WARNING **: key AC12: keycode = 4294967295; not in range 8..255

Falha de segmentação (core dumped)

The bug has been fixed upstream now

libgnomekbd (2.19.91-0ubuntu1) gutsy; urgency=low

  * New upstream version:
    - Fixed a couple of bugs (one crasher), minor build fixes (LP: #101895)
  * debian/patches/80_from_bugzilla_fix_incorrect_free_usage.patch:
    - Dropped as got fixed upstream

 -- Aron Sisak <email address hidden> Mon, 27 Aug 2007 12:29:53 +0200