After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 404107 - crash in Keyboard: opening "Choose a Layout...
crash in Keyboard: opening "Choose a Layout...
Status: RESOLVED DUPLICATE of bug 429907
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 410734 413318 418145 429362 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-03 22:48 UTC by blake
Modified: 2007-09-03 17:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description blake 2007-02-03 22:48:28 UTC
Version: 2.16.0

What were you doing when the application crashed?
opening "Choose a Layout" in System>Preferences>Keyboard


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:29:48 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
ALSA lib pcm_hw.c:1357:(_snd_pcm_hw_open) Invalid value for card
** WARNING **: alsa_setup(): Failed to open pcm device (hw:1,0): No such device
ALSA lib pcm_hw.c:1357:(_snd_pcm_hw_open) Invalid value for card
** WARNING **: alsa_setup(): Failed to open pcm device (hw:1,0): No such device
-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink': Resource busy or not available. [gstalsasink.c(636): gst_alsasink_open (): /pipeline0/gconfaudiosink0/bin0/halaudiosink0/bin1/alsasink0:
Device 'default:0' is busy]
-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music': Resource busy or not available. [gstalsasink.c(636): gst_alsasink_open (): /pipeline1/gconfaudiosink1/bin2/halaudiosink1/bin3/alsasink1:
Device 'default:0' is busy]
** (gnome-keyboard-properties:3133): WARNING **: key AE00: keycode = 4294967295; not in range 8..255
** (bug-buddy:3152): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 281374720 vsize: 281374720 resident: 15175680 share: 9138176 rss: 15175680 rss_rlim: -1
CPU usage: start_time: 1170542823 rtime: 119 utime: 110 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-keyboard-properties'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496357248 (LWP 3133)]
(no debugging symbols found)
0x00000037cb40d935 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496357248 (LWP 3133))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_ascii_strcasecmp
  • #4 g_list_foreach
    from /lib64/libglib-2.0.so.0
  • #5 g_ascii_strcasecmp
  • #6 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #11 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gdk_window_is_viewable
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #14 gdk_window_process_all_updates
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #15 gtk_container_check_resize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 gtk_dialog_run
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 g_ascii_strcasecmp
  • #21 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #25 gtk_button_set_alignment
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #27 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #30 gtk_button_released
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #36 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #39 gdk_add_client_message_filter
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #40 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #41 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #43 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #44 g_ascii_strcasecmp
  • #45 __libc_start_main
    from /lib64/libc.so.6
  • #46 g_ascii_strcasecmp
  • #47 ??
  • #48 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Jens Granseuer 2007-02-04 10:33:11 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Can you please install debugging symbols for control-center, gtk+, and glib? Thank you.
Comment 2 Susana 2007-02-22 11:04:40 UTC
*** Bug 410734 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2007-03-01 09:54:59 UTC
*** Bug 413318 has been marked as a duplicate of this bug. ***
Comment 4 Jens Granseuer 2007-03-14 20:09:12 UTC
*** Bug 418145 has been marked as a duplicate of this bug. ***
Comment 5 Jens Granseuer 2007-04-13 18:23:41 UTC
*** Bug 429362 has been marked as a duplicate of this bug. ***
Comment 6 Jens Granseuer 2007-04-13 18:25:26 UTC
Possibly helpful extract from .xsession-errors in bug 429362:

** (gnome-keyboard-properties:5276): WARNING **: key HZTG: keycode =
4294967295; not in range 8..255
Comment 7 Sergey V. Udaltsov 2007-09-03 14:39:39 UTC
First of all, it was a but in xkeyboard-config (fixed). But even with that, the keycode -1 (=not found) should not make the app crash. Anyway, it is already fixed

*** This bug has been marked as a duplicate of 429907 ***
Comment 8 Quentin Brandon 2007-09-03 14:54:46 UTC
Good work and also thank you for the update.
Are both the xkeyboard-config bug and the error handling bug fixed or just the xkeyboard-config and we hope there is no case of error anymore to avoid crashes of the keyboard selection window ?
Comment 9 Sergey V. Udaltsov 2007-09-03 17:31:05 UTC
both hopefully