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 528420 - crash in Keyboard Indicator: iniciando sesión en gnom...
crash in Keyboard Indicator: iniciando sesión en gnom...
Status: RESOLVED DUPLICATE of bug 523583
Product: gnome-applets
Classification: Other
Component: keyboard indicator (gswitchit)
2.20.x
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-16 15:13 UTC by bib
Modified: 2008-04-16 18:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description bib 2008-04-16 15:13:25 UTC 
Version: 2.20.1

What were you doing when the application crashed?
iniciando sesión en gnome.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Crux

Memory status: size: 22810624 vsize: 22810624 resident: 10002432 share: 7344128 rss: 10002432 rss_rlim: 4294967295
CPU usage: start_time: 1208358631 rtime: 19 utime: 17 stime: 2 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 0xb6f0e940 (LWP 4454)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 195386

Thread 1 (Thread 0xb6f0e940 (LWP 4454))

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


----------- .xsession-errors (12 sec old) ---------------------
(nautilus:4137): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:4137): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans Bold 0'
(nautilus:4137): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='DejaVu Sans Bold 0', text='img4trainALL'
(nautilus:4137): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans Bold 0'
(nautilus:4137): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
(nautilus:4137): Eel-CRITICAL **: eel_pango_font_description_get_largest_fitting_font_size: assertion `maximum_acceptable_font_size > minimum_acceptable_font_size' failed
get bib pop://bib@mail.alu.ua.es/
Find Items 0
get boyan pop://boyan@luceros.dccia.ua.es/
Find Items 0
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-16 18:27:45 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 523583 ***