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 405499 - crash in Epiphany: Trying to print to a Bro...
crash in Epiphany: Trying to print to a Bro...
Status: RESOLVED DUPLICATE of bug 356632
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-02-07 19:58 UTC by dgfreeman
Modified: 2007-02-07 21:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dgfreeman 2007-02-07 19:58:08 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Trying to print to a Brother HL-2040, connected to lpt0, using SuSe 10.2


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

Memory status: size: 447356928 vsize: 447356928 resident: 20058112 share: 32661504 rss: 52719616 rss_rlim: 893987840
CPU usage: start_time: 1170878817 rtime: 817 utime: 752 stime: 65 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 47889928413168 (LWP 14552)]
[New Thread 1132489024 (LWP 14561)]
[New Thread 1124096320 (LWP 14560)]
[New Thread 1115703616 (LWP 14559)]
[New Thread 1107310912 (LWP 14558)]
[New Thread 1098918208 (LWP 14557)]
[New Thread 1090525504 (LWP 14554)]
[New Thread 1082132800 (LWP 14553)]
(no debugging symbols found)
0x00002b8e39417c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 108835

Thread 1 (Thread 47889928413168 (LWP 14552))

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






Comment 1


Reinout van Schouwen





          2007-02-07 21:36:50 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 ***