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 439238 - crash in Yelp: Reviewing help search re...
crash in Yelp: Reviewing help search re...
Status: RESOLVED DUPLICATE of bug 356632
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-17 17:47 UTC by richard.marshall
Modified: 2007-05-17 19:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description richard.marshall 2007-05-17 17:47:53 UTC
Version: 2.16.1

What were you doing when the application crashed?
Reviewing help search results regarding telnet, sent to print to file


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

Memory status: size: 492900352 vsize: 492900352 resident: 47607808 share: 33320960 rss: 80928768 rss_rlim: 873533440
CPU usage: start_time: 1179423861 rtime: 493 utime: 439 stime: 54 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 47195780900640 (LWP 5658)]
[New Thread 1098918208 (LWP 5663)]
[New Thread 1090525504 (LWP 5660)]
[New Thread 1082132800 (LWP 5659)]
(no debugging symbols found)
0x00002aec9c2d4c5f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47195780900640 (LWP 5658))

  • #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 Pedro Villavicencio 2007-05-17 19:49:44 UTC
Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!


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