Bug 376567 – crash in Help: Nothing, I just tried to...

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 376567 - crash in Help: Nothing, I just tried to...


Summary:	crash in Help: Nothing, I just tried to...


Status:	RESOLVED DUPLICATE of bug 377079

Product:	yelp
Classification:	Applications
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Yelp maintainers
QA Contact:	Yelp maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-18 06:08 UTC by Duncan Lithgow
Modified:	2006-11-21 18:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Duncan Lithgow 2006-11-18 06:08:43 UTC

Version: 2.16.1

What were you doing when the application crashed?
Nothing, I just tried to open it. The window opened and the left-hand cursor was blinking. The Bug Reporting Tool came up and moving it around shows that the windows of Yelp is not being refreshed,


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.2 2006-11-14 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 118276096 vsize: 0 resident: 118276096 share: 0 rss: 34021376 rss_rlim: 0
CPU usage: start_time: 1163829991 rtime: 0 utime: 136 stime: 0 cutime:114 cstime: 0 timeout: 22 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227823408 (LWP 4945)]
[New Thread -1303737456 (LWP 4958)]
[New Thread -1295344752 (LWP 4957)]
[New Thread -1286952048 (LWP 4956)]
[New Thread -1278559344 (LWP 4955)]
[New Thread -1270039664 (LWP 4949)]
[New Thread -1247433840 (LWP 4948)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87396

Thread 1 (Thread -1227823408 (LWP 4945))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#10 ??
#0 __kernel_vsyscall

Comment 1 Duncan Lithgow 2006-11-18 08:01:12 UTC

I should also mention that was the first time I tried to run the app on a machine recently upgraded from ubuntu 6.1 to 7.4.

Comment 2 André Klapper 2006-11-18 13:14:04 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 3 Don Scorgie 2006-11-21 18:43:57 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 377079 ***