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 405339 - crash in Keyboard: keyboard repeat has stop...
crash in Keyboard: keyboard repeat has stop...
Status: RESOLVED DUPLICATE of bug 374923
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 12:35 UTC by Kaare Schou
Modified: 2007-02-07 16:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Kaare Schou 2007-02-07 12:35:17 UTC
Version: 2.16.0

What were you doing when the application crashed?
keyboard repeat has stopped functioning. I open system -> preferences -> keyboard. Then crash


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 25493504 vsize: 0 resident: 25493504 share: 0 rss: 9760768 rss_rlim: 0
CPU usage: start_time: 1170851565 rtime: 0 utime: 32 stime: 0 cutime:27 cstime: 0 timeout: 5 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208936224 (LWP 5458)]
(no debugging symbols found)
0x00a12402 in __kernel_vsyscall ()

Thread 1 (Thread -1208936224 (LWP 5458))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_ascii_strcasecmp
  • #5 g_ascii_strcasecmp
  • #6 g_ascii_strcasecmp
  • #7 g_ascii_strcasecmp
  • #8 __libc_start_main
    from /lib/libc.so.6
  • #9 g_ascii_strcasecmp
  • #0 __kernel_vsyscall


----------- .xsession-errors (1141 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
Running tvtime 1.0.1.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /root/.tvtime/tvtime.xml
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400001 (tvtime)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Thank you for using tvtime.
Running tvtime 1.0.1.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /root/.tvtime/tvtime.xml
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400001 (tvtime)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Thank you for using tvtime.
--------------------------------------------------
Comment 1 Jens Granseuer 2007-02-07 16:40:37 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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