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 374923 - crash in Keyboard: Launching System-config-...
crash in Keyboard: Launching System-config-...
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
: 368863 375785 375792 375811 378489 390113 405339 406146 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-14 00:22 UTC by jim.cornette
Modified: 2007-06-06 00:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
This was on FC6 Fedora (5.13 KB, text/plain)
2006-12-29 00:09 UTC, Jim Cornette
Details

Description jim.cornette 2006-11-14 00:22:31 UTC
Version: 2.16.0

What were you doing when the application crashed?
Launching System-config-keyboard


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.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled
----------- .xsession-errors ---------------------
xscreensaver: 18:38:19: 1: for window 0x1a00006 (xscreensaver)
xscreensaver: 18:39:27: 1: unrecognised ClientMessage "_GTK_LOAD_ICONTHEMES" received
xscreensaver: 18:39:27: 1: for window 0x1a00006 (xscreensaver)
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
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value: /desktop/gnome/peripherals/keyboard/repeat: possibly incomplete setup
(gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value: /desktop/gnome/interface/cursor_blink: possibly incomplete setup
(gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value: /desktop/gnome/typing_break/enabled: possibly incomplete setup
** (bug-buddy:4043): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 25661440 vsize: 0 resident: 25661440 share: 0 rss: 9912320 rss_rlim: 0
CPU usage: start_time: 1163463711 rtime: 0 utime: 15 stime: 0 cutime:11 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208829104 (LWP 4041)]
(no debugging symbols found)
0x005da402 in __kernel_vsyscall ()

Thread 1 (Thread -1208829104 (LWP 4041))

  • #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

Comment 1 Jim Cornette 2006-11-14 00:59:12 UTC
(In reply to comment #0)
> Version: 2.16.0
> 
> What were you doing when the application crashed?
> Launching gnome-keyboard-properties.

Thanks, the bug report itself helped me locate the problematic component. Reinstalling control-center allowed gnome-keyboard-properties to launch without 



> 
> 
> 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.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
> X Vendor: The X.Org Foundation
> X Vendor Release: 70101000
> Selinux: Permissive
> Accessibility: Disabled
> ----------- .xsession-errors ---------------------
> xscreensaver: 18:38:19: 1: for window 0x1a00006 (xscreensaver)
> xscreensaver: 18:39:27: 1: unrecognised ClientMessage "_GTK_LOAD_ICONTHEMES"
> received
> xscreensaver: 18:39:27: 1: for window 0x1a00006 (xscreensaver)
> 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
> ** Message: Could not connect to power manager: Could not get owner of name
> 'org.gnome.PowerManager': no such name
> (gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value:
> /desktop/gnome/peripherals/keyboard/repeat: possibly incomplete setup
> (gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value:
> /desktop/gnome/interface/cursor_blink: possibly incomplete setup
> (gnome-keyboard-properties:4041): capplet-common-WARNING **: NULL GConf value:
> /desktop/gnome/typing_break/enabled: possibly incomplete setup
> ** (bug-buddy:4043): WARNING **: Couldn't load icon for Open Folder
> --------------------------------------------------
> 
> Memory status: size: 25661440 vsize: 0 resident: 25661440 share: 0 rss: 9912320
> rss_rlim: 0
> CPU usage: start_time: 1163463711 rtime: 0 utime: 15 stime: 0 cutime:11 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/libthread_db.so.1".
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1208829104 (LWP 4041)]
> (no debugging symbols found)
> 0x005da402 in __kernel_vsyscall ()
> #0  0x005da402 in __kernel_vsyscall ()
> #1  0x4a352c93 in __waitpid_nocancel () from /lib/libpthread.so.0
> #2  0x00c10cf6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
> #3  <signal handler called>
> #4  0x08050c14 in g_ascii_strcasecmp ()
> #5  0x08051821 in g_ascii_strcasecmp ()
> #6  0x0804fa19 in g_ascii_strcasecmp ()
> #7  0x0804f29e in g_ascii_strcasecmp ()
> #8  0x4a1edf2c in __libc_start_main () from /lib/libc.so.6
> #9  0x0804eb51 in g_ascii_strcasecmp ()
> 
> Thread 1 (Thread -1208829104 (LWP 4041)):
> #0  0x005da402 in __kernel_vsyscall ()
> No symbol table info available.
> #1  0x4a352c93 in __waitpid_nocancel () from /lib/libpthread.so.0
> No symbol table info available.
> #2  0x00c10cf6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
> No symbol table info available.
> #3  <signal handler called>
> No symbol table info available.
> #4  0x08050c14 in g_ascii_strcasecmp ()
> No symbol table info available.
> #5  0x08051821 in g_ascii_strcasecmp ()
> No symbol table info available.
> #6  0x0804fa19 in g_ascii_strcasecmp ()
> No symbol table info available.
> #7  0x0804f29e in g_ascii_strcasecmp ()
> No symbol table info available.
> #8  0x4a1edf2c in __libc_start_main () from /lib/libc.so.6
> No symbol table info available.
> #9  0x0804eb51 in g_ascii_strcasecmp ()
> No symbol table info available.
> #0  0x005da402 in __kernel_vsyscall ()
> 

Comment 2 André Klapper 2006-11-14 11:46:17 UTC
*** Bug 368863 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2006-11-16 08:19:14 UTC
*** Bug 375785 has been marked as a duplicate of this bug. ***
Comment 4 Susana 2006-11-16 08:24:27 UTC
*** Bug 375811 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2006-11-16 10:21:27 UTC
confirming as per duplicates
Comment 6 André Klapper 2006-11-16 10:21:39 UTC
*** Bug 375792 has been marked as a duplicate of this bug. ***
Comment 7 Susana 2006-11-23 20:20:30 UTC
*** Bug 378489 has been marked as a duplicate of this bug. ***
Comment 8 Sebastien Bacher 2006-12-17 22:55:35 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 9 Jim Cornette 2006-12-18 03:43:25 UTC
The bug only happened until I removed control-center followed by reinstalling the package again. If I recall, there were no files installed for the keyboard.

The problem that I was having which made me try the keyboard options was that the terminal was light yellow, I had no settings for shortcuts with either copy or paste. The keyboard would not advance or go backwards when the left or right arrow was pressed, the backspace key only worked if the key was released and pressed down again.
I got the error with this condition when I launched the keyboard settings.
Uninstalling and reinstalling the rpm allowed me to adjust the settings without a crash.
Since reporting this bug, I have maintained the settings which I had to manually enter.
Also the debuginfo package was not installed which most likely is the reason that the info was inadequate for diagnosis.
Sorry I cannot repeat the problem since there are so many bug reports that were marked as duplicates of this bug. Thanks for the link for getting traces, I'll use this for future problem diagnosis.
Comment 10 Susana 2006-12-28 11:40:14 UTC
*** Bug 390113 has been marked as a duplicate of this bug. ***
Comment 11 Jim Cornette 2006-12-29 00:07:42 UTC
I recently had another crash which dumped a file through bug-buddy. I don't know if this attachment will help or not. I will try to install the deguginfo packages for control center and wait until I get any more errors.

Attached will be a no deguginfo file which is not keyboard related but related to fonts I presume.
Comment 12 Jim Cornette 2006-12-29 00:09:50 UTC
Created attachment 79013 [details]
This was on FC6 Fedora

The system slowed down, the mouse was not controllable. This incident only happened once when using an application called seamonkey.
Comment 13 Jens Granseuer 2007-02-07 16:40:37 UTC
*** Bug 405339 has been marked as a duplicate of this bug. ***
Comment 14 Jens Granseuer 2007-02-09 17:13:51 UTC
*** Bug 406146 has been marked as a duplicate of this bug. ***
Comment 15 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 00:21:06 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 and
reopen this bug or report a new one. Thanks in advance!

(Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass
changing all of these. Search for "dieguito-doing-incomplete-spam" to delete
all this from your inbox.)