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 420956 - crash in Keyboard: startup
crash in Keyboard: startup
Status: RESOLVED DUPLICATE of bug 370038
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-03-21 11:28 UTC by vit.shatsillo
Modified: 2007-03-28 19:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description vit.shatsillo 2007-03-21 11:28:35 UTC 
Version: 2.18.0

What were you doing when the application crashed?
startup


Distribution: Unknown
Gnome Release: 2.18.0 2007-03-19 (FreeBSD GNOME Project)
BugBuddy Version: 2.18.0

System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #6: Tue Mar  6 08:23:25 MSK 2007     root@vit.smolny.uts:/usr/obj/usr/src/sys/WK2 i386
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Mist

Memory status: size: 19668 vsize: 19668 resident: 13596 share: 18597525 rss: 13596 rss_rlim: 3399
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

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

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100173]
[Switching to LWP 100173]
0x28f743f9 in wait4 () from /lib/libc.so.6

+ Trace 120719

Thread 1 (LWP 100173)

  • #0 wait4
    from /lib/libc.so.6
  • #1 waitpid
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.2
  • #3 libgnomeui_module_info_get
    from /usr/local/lib/libgnomeui-2.so.0
  • #4 sigaction
    from /lib/libpthread.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 sigaction
    from /lib/libpthread.so.2
  • #11 xkl_config_registry_find_object
    from /usr/local/lib/libxklavier.so.11
  • #12 xkl_config_registry_find_layout
    from /usr/local/lib/libxklavier.so.11
  • #13 gkbd_keyboard_config_get_lv_descriptions
    from /usr/local/lib/libgnomekbd.so.1
  • #14 gkbd_keyboard_config_get_descriptions
    from /usr/local/lib/libgnomekbd.so.1
  • #15 xkb_layouts_fill_selected_tree
  • #16 setup_xkb_tabs
  • #17 main 


----------- .xsession-errors ---------------------
(gnome-terminal:57737): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Fontconfig warning: no <cachedir> elements found. Check configuration.
Fontconfig warning: adding <cachedir>/var/db/fontconfig</cachedir>
Fontconfig warning: adding <cachedir>~/.fontconfig</cachedir>
Fontconfig warning: no <cachedir> elements found. Check configuration.
Fontconfig warning: adding <cachedir>/var/db/fontconfig</cachedir>
Fontconfig warning: adding <cachedir>~/.fontconfig</cachedir>
Fontconfig warning: no <cachedir> elements found. Check configuration.
Fontconfig warning: adding <cachedir>/var/db/fontconfig</cachedir>
Fontconfig warning: adding <cachedir>~/.fontconfig</cachedir>
This libgtop was compiled on FreeBSD 6.2-RELEASE i386
If you see strange problems caused by it,
you should recompile libgtop and dependent applications
warning: Unable to get location for thread creation breakpoint: generic error
--------------------------------------------------
Comment 1 Timm F. Gloger 2007-03-21 16:35:47 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!
Comment 2 Jens Granseuer 2007-03-28 19:52:23 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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