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 425228 - crash in Keyboard: adding layout
crash in Keyboard: adding layout
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.18.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-01 17:36 UTC by Nicolas Mailhot
Modified: 2007-05-02 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Nicolas Mailhot 2007-04-01 17:36:56 UTC
Version: 2.18.0

What were you doing when the application crashed?
adding layout


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3038.fc7 #1 SMP Sat Mar 31 19:23:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299903
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Bluecurve

Memory status: size: 314634240 vsize: 314634240 resident: 20430848 share: 11964416 rss: 20430848 rss_rlim: 18446744073709551615
CPU usage: start_time: 1175448962 rtime: 118 utime: 98 stime: 20 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 46912500656864 (LWP 7672)]
0x000000347060d805 in __libc_waitpid (pid=7678, stat_loc=0x7fffd66ef31c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
32	      return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 1 (Thread 46912500656864 (LWP 7672))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 32
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 g_free
    at gmem.c line 184
  • #4 IA__g_list_foreach
    at glist.c line 495
  • #5 g_free
    at gmem.c line 184
  • #6 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #7 g_main_context_iterate
    at gmain.c line 2677
  • #8 IA__g_main_loop_run
    at gmain.c line 2881
  • #9 IA__gtk_dialog_run
    at gtkdialog.c line 996
  • #10 xkb_layout_choose
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gtk_real_button_released
    at gtkbutton.c line 1484
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #19 IA__g_signal_emit
    at gsignal.c line 2243
  • #20 gtk_button_button_release
    at gtkbutton.c line 1377
  • #21 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #22 IA__g_closure_invoke
    at gclosure.c line 490
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #24 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #25 IA__g_signal_emit
    at gsignal.c line 2243
  • #26 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #27 IA__gtk_propagate_event
    at gtkmain.c line 2341
  • #28 IA__gtk_main_do_event
    at gtkmain.c line 1575
  • #29 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #30 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #31 g_main_context_iterate
    at gmain.c line 2677
  • #32 IA__g_main_loop_run
    at gmain.c line 2881
  • #33 IA__gtk_main
    at gtkmain.c line 1154
  • #34 main
0x000000347060d805	32	      return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (46 sec old) ---------------------
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__
    _dbus_bindings.UInt32(0))
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
** Message: Error: Resource not found.
gstfilesrc.c(976): gst_file_src_start (): /play/source:
No such file "/dev/video0"
GTK Accessibility Module initialized
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Avertissement du gestionnaire de fenêtres : last_user_time (32) is greater than comparison timestamp (2922883808).  This most likely represents a buggy client sending inaccurate timestamps in messag
Avertissement du gestionnaire de fenêtres : 0x1600003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
--------------------------------------------------
Comment 1 Jens Granseuer 2007-04-01 18:32:23 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 control-center debugging symbols as well?
Comment 2 Bruno Boaventura 2007-05-02 16:58:49 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!