Bug 375793 – crash in Help: Nothing. The bug popped ...

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 375793 - crash in Help: Nothing. The bug popped ...


Summary:	crash in Help: Nothing. The bug popped ...


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-16 03:48 UTC by Pradeep Varadarajan
Modified:	2006-11-20 19:28 UTC

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

Description Pradeep Varadarajan 2006-11-16 03:48:16 UTC

Version: 2.16.1

What were you doing when the application crashed?
Nothing. The bug popped up when the system started.


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

Memory status: size: 126328832 vsize: 0 resident: 126328832 share: 0 rss: 42024960 rss_rlim: 0
CPU usage: start_time: 1163648807 rtime: 0 utime: 135 stime: 0 cutime:119 cstime: 0 timeout: 16 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 -1227311408 (LWP 4574)]
[New Thread -1304441968 (LWP 4590)]
[New Thread -1296049264 (LWP 4589)]
[New Thread -1287656560 (LWP 4588)]
[New Thread -1279263856 (LWP 4580)]
[New Thread -1269503088 (LWP 4577)]
[New Thread -1246938224 (LWP 4576)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86848

Thread 1 (Thread -1227311408 (LWP 4574))

#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 André Klapper 2006-11-16 10:20:46 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 Pradeep Varadarajan 2006-11-18 09:58:55 UTC

gnome version is 2.17.2 (is this head?)
yelp version 2.16.1

(gdb) r
<snip>
(no debugging symbols found)
[New Thread -1247212656 (LWP 6950)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1269777520 (LWP 6951)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1278297200 (LWP 6956)]
[New Thread -1286689904 (LWP 6957)]
[New Thread -1295082608 (LWP 6958)]
[New Thread -1303475312 (LWP 6959)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

** (yelp:6945): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.

** (yelp:6945): WARNING **: IOR not set.

** ERROR **: Could not locate registry
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1227585840 (LWP 6945)]
0xffffe410 in __kernel_vsyscall ()

(gdb) thread apply all bt

+ Trace 87412

Comment 3 Don Scorgie 2006-11-20 19:28:54 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 ***