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 405402 - crash in Keyboard: installed kde desktop at...
crash in Keyboard: installed kde desktop at...
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-07 15:55 UTC by martin.olof.andersson
Modified: 2007-02-07 18:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description martin.olof.andersson 2007-02-07 15:55:31 UTC 
Version: 2.16.1

What were you doing when the application crashed?
installed kde desktop at the same time


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 20234240 vsize: 0 resident: 20234240 share: 0 rss: 10510336 rss_rlim: 0
CPU usage: start_time: 1170863688 rtime: 0 utime: 33 stime: 0 cutime:29 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225963856 (LWP 10405)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 108763

Thread 1 (Thread -1225963856 (LWP 10405))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 xkl_config_rec_dump
    from /usr/lib/libxklavier.so.11
  • #5 xkl_config_rec_dump
    from /usr/lib/libxklavier.so.11
  • #6 gconf_property_editor_marshal_VOID__STRING_POINTER
  • #7 gconf_property_editor_marshal_VOID__STRING_POINTER
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 






Comment 1


Kjartan Maraas





          2007-02-07 18:15: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-02-07 18:18:04 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 ***

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