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 418145 - crash in Keyboard: Pressed the button Add i...
crash in Keyboard: Pressed the button Add i...
Status: RESOLVED DUPLICATE of bug 404107
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-14 08:05 UTC by Quentin Brandon
Modified: 2007-03-14 20:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Quentin Brandon 2007-03-14 08:05:08 UTC
Version: 2.16.3

What were you doing when the application crashed?
Pressed the button Add in the Layout tab of the keyboard properties.
Happens systematically...


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:05:34 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 284479488 vsize: 284479488 resident: 15773696 share: 9580544 rss: 15773696 rss_rlim: -1
CPU usage: start_time: 1173859433 rtime: 55 utime: 51 stime: 4 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 46912496377776 (LWP 11053)]
(no debugging symbols found)
0x0000003dfb60d935 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496377776 (LWP 11053))

  • #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


----------- .xsession-errors (16825 sec old) ---------------------
Selected video codec: [mpeg12] vfm: libmpeg2 (MPEG-1 or 2 (libmpeg2))
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 44100 Hz, 2 ch, s16le, 224.0 kbit/15.87% (ratio: 28000->176400)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 352 x 240 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.30:1 - prescaling to correct movie aspect.
VO: [xv] 352x240 => 352x270 Planar YV12 
A:   0.4 V:   0.0 A-V:  0.321 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.4 V:   0.3 A-V:  0.058 ct:  0.003   2/  2 ??% ??% ??,?% 0 0              
A:   0.4 V:   0.4 A-V:  0.046 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jens Granseuer 2007-03-14 20:09:12 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 404107 ***