Bug 401910 – crash in Yelp: Printing a help page

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 401910 - crash in Yelp: Printing a help page


Summary:	crash in Yelp: Printing a help page


Status:	RESOLVED DUPLICATE of bug 356632

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:	2007-01-28 23:59 UTC by lest19
Modified:	2007-02-07 10:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description lest19 2007-01-28 23:59:28 UTC

Version: 2.16.1

What were you doing when the application crashed?
Printing a help page


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 522854400 vsize: 522854400 resident: 72019968 share: 33947648 rss: 105967616 rss_rlim: 1793459200
CPU usage: start_time: 1170028679 rtime: 624 utime: 600 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47256458045216 (LWP 23166)]
[New Thread 1124096320 (LWP 23202)]
[New Thread 1115703616 (LWP 23201)]
[New Thread 1107310912 (LWP 23200)]
[New Thread 1098918208 (LWP 23169)]
[New Thread 1090525504 (LWP 23168)]
[New Thread 1082132800 (LWP 23167)]
(no debugging symbols found)
0x00002afabcd10c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 106137

Thread 1 (Thread 47256458045216 (LWP 23166))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 FcCharSetDestroy
from /usr/lib64/libfontconfig.so.1
#4 nsFontMetricsPS::~nsFontMetricsPS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#5 nsFontPSAFM::FindFont
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#6 nsFontCache::Flush
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#7 nsFontCache::~nsFontCache
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#8 nsFontCachePS::~nsFontCachePS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#9 DeviceContextImpl::~DeviceContextImpl
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#10 nsDeviceContextPS::~nsDeviceContextPS
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#11 DeviceContextImpl::Release
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#12 nsPrintData::~nsPrintData
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#13 nsPrintEngine::Destroy
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#14 DocumentViewerImpl::OnDonePrinting
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#15 PL_HandleEvent
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#16 PL_ProcessPendingEvents
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#17 nsEventQueueImpl::~nsEventQueueImpl
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#18 nsCOMPtr<nsIWidget>::nsCOMPtr
from /usr/lib64/xulrunner-1.8.1b2/libxul.so
#19 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#20 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#21 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#22 gtk_main
from /opt/gnome/lib64/libgtk-x11-2.0.so.0
#23 nsIPrefService::GetIID
#24 __libc_start_main
from /lib64/libc.so.6
#25 g_cclosure_marshal_VOID__VOID
#26 ??
#27 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Reinout van Schouwen 2007-02-07 10:34: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 356632 ***