Bug 564358 – crash in Keyboard Indicator:

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 564358 - crash in Keyboard Indicator:


Summary:	crash in Keyboard Indicator:


Status:	RESOLVED DUPLICATE of bug 529773

Product:	gnome-applets
Classification:	Other
Component:	keyboard indicator (gswitchit)
Version:	2.22.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-12-13 06:30 UTC by racos_lm
Modified:	2009-01-08 14:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description racos_lm 2008-12-13 06:30:14 UTC

Version: 2.22.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Parsix)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-parsix-22 #1 SMP PREEMPT Wed May 14 07:47:28 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-Midnight
Icon Theme: Human

Memory status: size: 24174592 vsize: 24174592 resident: 9551872 share: 7548928 rss: 9551872 rss_rlim: 4294967295
CPU usage: start_time: 1229128001 rtime: 12 utime: 6 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/gnome-keyboard-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dc0aa0 (LWP 2911)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 210753

Thread 1 (Thread 0xb6dc0aa0 (LWP 2911))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 g_markup_escape_text
from /usr/lib/libglib-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
#9 ??
#10 ??
#11 g_value_transform
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_set
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_set_tooltip_text
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgnomekbdui.so.2
#16 ??
#17 ??
#18 ??
#19 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2009-01-08 14:56:28 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 529773 ***