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 368863 - crash in Keyboard: I was trying to start up...
crash in Keyboard: I was trying to start up...
Status: RESOLVED DUPLICATE of bug 374923
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: 2006-11-01 14:23 UTC by svpastime
Modified: 2006-11-14 11:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description svpastime 2006-11-01 14:23:28 UTC
Version: 2.16.0

What were you doing when the application crashed?
I was trying to start up the preferences/keyboard program


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

Memory status: size: 25751552 vsize: 0 resident: 25751552 share: 0 rss: 11411456 rss_rlim: 0
CPU usage: start_time: 1162394465 rtime: 0 utime: 28 stime: 0 cutime:24 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208338736 (LWP 2836)]
(no debugging symbols found)
0x00185402 in __kernel_vsyscall ()

Thread 1 (Thread -1208338736 (LWP 2836))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_ascii_strcasecmp
  • #5 g_ascii_strcasecmp
  • #6 g_ascii_strcasecmp
  • #7 g_ascii_strcasecmp
  • #8 __libc_start_main
    from /lib/libc.so.6
  • #9 g_ascii_strcasecmp
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-14 11:46:17 UTC
marking as a duplicate of bug 374923, as we have the .xseesion-errors output there

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