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 410382 - crash in Keyboard: Starting the gnome-keybo...
crash in Keyboard: Starting the gnome-keybo...
Status: RESOLVED DUPLICATE of bug 370038
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-02-21 14:04 UTC by mark.evenson
Modified: 2007-02-21 15:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
full backtrace with all symbols resolved (4.43 KB, text/plain)
2007-02-21 14:58 UTC, mark.evenson
Details

Description mark.evenson 2007-02-21 14:04:22 UTC
Version: 2.16.3

What were you doing when the application crashed?
Starting the gnome-keyboard-properties application


Distribution: Unknown
Gnome Release: 2.16.3 2007-01-31 (FreeBSD GNOME Project)
BugBuddy Version: 2.16.1

System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #2: Mon Jan 15 12:22:07 CET 2007     evenson@elvis.intern.etel.at:/usr/obj/usr/src/sys/ELVIS i386
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled

Memory status: size: 4743168 vsize: 0 resident: 4743168 share: 0 rss: 16412672 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 457113 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

[New LWP 100173]
[Switching to LWP 100173]
0x2909d6cd in wait4 () from /lib/libc.so.6

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 gswitchit_kbd_config_get_lv_descriptions
    at gswitchit-config.c line 116
  • #14 gswitchit_kbd_config_get_descriptions
    at gswitchit-config.c line 1003
  • #15 xkb_layouts_fill_selected_tree
    at gnome-keyboard-properties-xkblt.c line 347
  • #16 setup_xkb_tabs
    at gnome-keyboard-properties-xkb.c line 183
  • #17 setup_dialog
    at gnome-keyboard-properties.c line 172
  • #18 main
    at gnome-keyboard-properties.c line 252


----------- .xsession-errors (2996 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1b284aa specified for 0x1b284c9 (Styles and).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1b284aa (Untitled1 )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1b2f519 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1b360a0 specified for 0x1b360bf (Styles and).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1b360a0 (Untitled1 )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
CalDAV Eplugin starting up ...
** (evolution-2.8:28143): DEBUG: mailto URL command: evolution %s
** (evolution-2.8:28143): DEBUG: mailto URL program: evolution
camel-Message: --
Window manager warning: 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-02-21 14:39:02 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 mark.evenson 2007-02-21 14:58:00 UTC
Created attachment 83042 [details]
full backtrace with all symbols resolved
Comment 3 mark.evenson 2007-02-21 15:07:06 UTC
The backtrace was generated by running 'gnome-keyboard-properties' directly under gdb after recompiling the necessary gnome ports.  This backtrace is a little different than the one generated via 'bug-buddy', but I think this is due to platform differences especially with respect to FreeBSD threading model.  

Since I am running GNOME on FreeBSD, I cannot just install GNOME debug binaries.

Please let me know what else I can do to provide information.
  
Comment 4 Jens Granseuer 2007-02-21 15:38:01 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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