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 434715 - crash in Yelp: Tring to print.
crash in Yelp: Tring to print.
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-04-30 21:52 UTC by slgallagher
Modified: 2007-05-17 19:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description slgallagher 2007-04-30 21:52:31 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Tring to print.


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

Memory status: size: 209235968 vsize: 0 resident: 209235968 share: 0 rss: 43544576 rss_rlim: 0
CPU usage: start_time: 1177970219 rtime: 0 utime: 753 stime: 0 cutime:697 cstime: 0 timeout: 56 it_real_value: 0 frequency: 0

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

(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 -1244850480 (LWP 5588)]
[New Thread -1364354160 (LWP 5603)]
[New Thread -1355961456 (LWP 5602)]
[New Thread -1347568752 (LWP 5600)]
[New Thread -1248842864 (LWP 5589)]
(no debugging symbols found)
0xb7ef9402 in ?? ()

+ Trace 131534

Thread 1 (Thread -1244850480 (LWP 5588))

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






Comment 1


palfrey





          2007-05-01 10:32:21 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


Pedro Villavicencio





          2007-05-17 19:50:13 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 ***