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 428961 - crash in Keyboard: I clicked on System->Pre...
crash in Keyboard: I clicked on System->Pre...
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-04-12 10:50 UTC by jd.junk1+gbug
Modified: 2007-04-13 18:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jd.junk1+gbug 2007-04-12 10:50:31 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I clicked on System->Preferences->Keyboard.  I was trying to change my keyboard settings


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

Memory status: size: 20955136 vsize: 0 resident: 20955136 share: 0 rss: 10936320 rss_rlim: 0
CPU usage: start_time: 1176374987 rtime: 0 utime: 30 stime: 0 cutime:26 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 -1225558352 (LWP 29023)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 127142

Thread 1 (Thread -1225558352 (LWP 29023))

  • #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 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #0 __kernel_vsyscall 






Comment 1


Jens Granseuer





          2007-04-13 18:12:09 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 ***