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 409382 - crash in Keyboard: updating clean install o...
crash in Keyboard: updating clean install o...
Status: RESOLVED INCOMPLETE
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-18 19:51 UTC by Thomas van der Burgt
Modified: 2007-03-21 03:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Thomas van der Burgt 2007-02-18 19:51:51 UTC 
Version: 2.16.1

What were you doing when the application crashed?
updating clean install of 6.10, Gnome control centre opened, filebrowser opened


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

Memory status: size: 20852736 vsize: 0 resident: 20852736 share: 0 rss: 10874880 rss_rlim: 0
CPU usage: start_time: 1171828234 rtime: 0 utime: 15 stime: 0 cutime:13 cstime: 0 timeout: 2 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 -1224902464 (LWP 13477)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111820

Thread 1 (Thread -1224902464 (LWP 13477))

  • #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 ??
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-02-18 23:03:25 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


Bruno Boaventura





          2007-03-21 03:51:00 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!