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 441581 - crash in About GNOME: Things I was doing when ...
crash in About GNOME: Things I was doing when ...
Status: RESOLVED DUPLICATE of bug 431255
Product: gnome-desktop
Classification: Core
Component: gnome-about
2.16.x
Other All
: High critical
: ---
Assigned To: Desktop Maintainers
Desktop Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-27 13:11 UTC by thebillywayne
Modified: 2007-05-28 22:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thebillywayne 2007-05-27 13:11:02 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Things I was doing when "Bug Buddy" lauched:
1.  Emerging "bibletime" package
2.  Mozilla Firefox running in background
3.  Viewing the "About the GNOME desktop" info slideshow 	


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-05-13 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 30486528 vsize: 0 resident: 30486528 share: 0 rss: 11907072 rss_rlim: 0
CPU usage: start_time: 1180295628 rtime: 0 utime: 31 stime: 0 cutime:30 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-about'

(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 -1225582928 (LWP 26410)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 136271

Thread 1 (Thread -1225582928 (LWP 26410))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-05-27 14:31:52 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


thebillywayne





          2007-05-28 20:39:56 UTC
        



Hi Tom.  

I've followed the instructions linked in your comment on getting better backtraces.  Afterward, I re-emerged libgnome and libgnomeui and attempted to re-create the bug.  Below is what Bug Buddy produced in the "Show Details" window.  I see that -some- new info has been added, but I still see a lot of "no debugging symbols found" messages.  Let me know whatever I can do to help with this bug.  

Billy Wayne McCann 



##BEGIN BUG BUDDY REPORT##
Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-05-13 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 31825920 vsize: 0 resident: 31825920 share: 0 rss: 11997184 rss_rlim: 0
CPU usage: start_time: 1180384579 rtime: 0 utime: 31 stime: 0 cutime:29 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-about'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225591120 (LWP 26379)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    136504






Thread 1
          (Thread -1225591120 (LWP 26379))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  870

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
pthread_mutex_lock

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#5
??

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#6
??

    • 

  • 
#7
??

    
                from
                /lib/libc.so.6

    

    • 

  • 
#8
??

    • 

  • 
#9
??

    • 

  • 
#10
malloc

    
                from
                /lib/libc.so.6

    

    • 

  • 
#11
??

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#12
??

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


thebillywayne





          2007-05-28 20:58:54 UTC
        



Was told to recompile cairo, as well.

##BEGIN BUG BUDDY REPORT##
Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-05-13 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 31817728 vsize: 0 resident: 31817728 share: 0 rss: 12005376 rss_rlim: 0
CPU usage: start_time: 1180386211 rtime: 0 utime: 32 stime: 0 cutime:31 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-about'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225718096 (LWP 16879)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    136507






Thread 1
          (Thread -1225718096 (LWP 16879))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  870

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
pthread_mutex_lock

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#5
_cairo_ft_unscaled_font_lock_face

    
                at cairo-ft-font.c
                  line
                  519

    

    • 

  • 
#6
_cairo_ft_ucs4_to_index

    
                at cairo-ft-font.c
                  line
                  2034

    

    • 

  • 
#7
_cairo_scaled_font_text_to_glyphs

    
                at cairo-scaled-font.c
                  line
                  932

    

    • 

  • 
#8
cairo_scaled_font_text_extents

    
                at cairo-scaled-font.c
                  line
                  777

    

    • 

  • 
#9
??

    
                from
                /usr/lib/libpangocairo-1.0.so.0

    

    • 

  • 
#10
??

    
                from
                /usr/lib/libcairo.so.2

    

    • 

  • 
#11
??

    • 

  • 
#12
??

    • 

  • 
#13
pthread_getspecific

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#14
??

    
                from
                /usr/lib/libpangocairo-1.0.so.0

    

    • 

  • 
#15
??

    • 

  • 
#16
??

    • 

  • 
#17
??

    • 

  • 
#18
??

    
                from
                /usr/lib/libpangocairo-1.0.so.0

    

    • 

  • 
#19
??

    
                from
                /lib/libc.so.6

    

    • 

  • 
#20
??

    • 

  • 
#21
??

    
                from
                /usr/lib/libpangocairo-1.0.so.0

    

    • 

  • 
#22
??

    
                from
                /usr/lib/libpangocairo-1.0.so.0

    

    • 

  • 
#23
??

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 4


palfrey





          2007-05-28 22:06:26 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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