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 370126 - trying to print any page crashes while in progress dialog
trying to print any page crashes while in progress dialog
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-11-03 17:59 UTC by oa
Modified: 2006-11-04 15:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description oa 2006-11-03 17:59:47 UTC
Version: 2.16.0

What were you doing when the application crashed?
trying to print from epiphany, any page at all, crashes the browser. Printing does work in Firefox and Evolution


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798_1.fc6.cubbi_suspend2 #1 SMP Fri Oct 20 22:53:53 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (76 sec old) ---------------------
Traceback (most recent call last):
  File "/usr/lib/gedit-2/plugins/modelines.py", line 25, in ?
    class ModelinePlugin(gedit.Plugin):
AttributeError: 'module' object has no attribute 'Plugin'
** (gedit:8031): WARNING **: Could not load python module modelines
** (gedit:8031): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed
** (gedit:8031): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed
** (gedit:8031): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed
** (gedit:8031): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed
--------------------------------------------------

Memory status: size: 246505472 vsize: 0 resident: 246505472 share: 0 rss: 42119168 rss_rlim: 0
CPU usage: start_time: 1162576697 rtime: 0 utime: 245 stime: 0 cutime:228 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/epiphany'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208624896 (LWP 8365)]
[New Thread -1403954288 (LWP 8409)]
[New Thread -1340056688 (LWP 8399)]
[New Thread -1329566832 (LWP 8398)]
[New Thread -1319076976 (LWP 8397)]
[New Thread -1298097264 (LWP 8396)]
[New Thread -1308587120 (LWP 8392)]
[New Thread -1287607408 (LWP 8390)]
[New Thread -1210868848 (LWP 8374)]
0x00caf402 in __kernel_vsyscall ()

Thread 1 (Thread -1208624896 (LWP 8365))

  • #0 __kernel_vsyscall
  • #1 __cxa_pure_virtual
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 210
  • #4 <signal handler called>
  • #5 IA__FcCharSetDestroy
    at fccharset.c line 57
  • #6 ~nsFontMetricsPS
    at nsFontMetricsPS.cpp line 111
  • #7 nsFontMetricsPS::Release
    at nsFontMetricsPS.cpp line 135
  • #8 nsFontCache::Flush
    at nsDeviceContext.cpp line 715
  • #9 ~nsFontCache
    at nsDeviceContext.cpp line 580
  • #10 ~nsFontCachePS
    at nsDeviceContextPS.cpp line 550
  • #11 ~DeviceContextImpl
    at nsDeviceContext.cpp line 88
  • #12 ~nsDeviceContextPS
    at nsDeviceContextPS.cpp line 137
  • #13 DeviceContextImpl::Release
    at nsDeviceContext.cpp line 54
  • #14 nsDeviceContextPS::Release
    at nsDeviceContextPS.cpp line 182
  • #15 ~nsCOMPtr_base
    at nsCOMPtr.cpp line 81
  • #16 ~nsCOMPtr
    at dist/include/xpcom/nsCOMPtr.h line 542
  • #17 ~nsPrintData
    at nsPrintData.cpp line 159
  • #18 nsPrintEngine::Destroy
    at nsPrintEngine.cpp line 283
  • #19 DocumentViewerImpl::OnDonePrinting
    at nsDocumentViewer.cpp line 4141
  • #20 HandlePLEvent
    at nsPrintEngine.cpp line 4549
  • #21 PL_HandleEvent
    at plevent.c line 688
  • #22 PL_ProcessPendingEvents
    at plevent.c line 623
  • #23 nsEventQueueImpl::ProcessPendingEvents
    at nsEventQueue.cpp line 417
  • #24 event_processor_callback
    at nsAppShell.cpp line 67
  • #25 g_io_unix_dispatch
    at giounix.c line 162
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #27 g_main_context_iterate
    at gmain.c line 2677
  • #28 IA__g_main_loop_run
    at gmain.c line 2881
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main
    at ephy-main.c line 705
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-03 18:02:30 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 ***
Comment 2 oa 2006-11-04 05:05:13 UTC
Sorry for reopening this, but is it certain this is a dup? 356632 is against FF 2.0, and so is the upstream. I'm on FC6, with latest 1.5 update RPM, and printing from FF does work. Furthermore, the upstream bug says "print to file" manages to create the file before crash - my Epiphany does not.
Comment 3 Christian Persch 2006-11-04 10:33:59 UTC
The trace from comment 0 says that it's a dup. If FC6 has the fix in its firefox (it's not just 2.0, all earlier versions were buggy too), and you still crash in epiphany, can you get an updated trace and file a new bug if it's different from comment 0?
Comment 4 Christian Persch 2006-11-04 10:48:28 UTC
FC6 has ff 1.5.7 and not added the patch, as far as I can see at http://cvs.fedora.redhat.com/viewcvs/rpms/firefox/FC-6/?sortby=date#dirlist ; the upstream fix is fixed1.8.0.8 which means that it's not released yet. You should probably file a bug against fedora.
Comment 5 oa 2006-11-04 15:36:08 UTC
Filed https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214015

Reinstalled Epiphany built against Firefox 2.0 from http://remi.collet.free.fr/rpms/fc6.i386, and the crash is now gone, so it does appear indeed to be caused by Fedora's Firefox build.