Bug 395841 – epiphany frequently crashes when printing from "print" window

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 395841 - epiphany frequently crashes when printing from "print" window


Summary:	epiphany frequently crashes when printing from "print" window


Status:	RESOLVED DUPLICATE of bug 356632

Product:	epiphany
Classification:	Core
Component:	Printing
Version:	2.14.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Marco Pesenti Gritti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-12 17:11 UTC by Richard Lyons
Modified:	2007-01-12 22:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Richard Lyons 2007-01-12 17:09:24 UTC

Distribution: Debian testing/unstable
Package: epiphany
Severity: Normal
Version: GNOME2.14.3 2.14.x
Gnome-Distributor: Debian
Synopsis: epiphany frequently crashes when printing from "print" window
Bugzilla-Product: epiphany
Bugzilla-Component: Printing
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
epiphany frequently crashes when printing from "print" window

Steps to reproduce the crash:
1. open eg googlemaps
2. select "print"
3. click anywhere not on print dialog then click print

Expected Results:
Print sent to printer (LAN)

How often does this happen?
30 - 50% of time

Additional Information:
Debian Etch, kernel 2.6.17-2-686, windowmaker


Debugging Information:

Backtrace was generated from '/usr/libexec/epiphany-browser'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1509267776 (LWP 15926)]
[New Thread -1523835984 (LWP 15929)]
[New Thread -1515263056 (LWP 15928)]
(no debugging symbols found)
0xa6fbe231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 101593

Thread 1 (Thread -1509267776 (LWP 15926))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 gtk_moz_embed_get_title
from /usr/lib/libgtkembedmoz.so.0d
#3 <signal handler called>
#4 FcCharSetDestroy
from /usr/lib/libfontconfig.so.1
#5 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#6 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#7 nsFontCache::Flush
from /usr/lib/libxul.so.0d
#8 nsFontCache::~nsFontCache
from /usr/lib/libxul.so.0d
#9 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#10 DeviceContextImpl::~DeviceContextImpl
from /usr/lib/libxul.so.0d
#11 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#12 DeviceContextImpl::Release
from /usr/lib/libxul.so.0d
#13 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#14 nsCOMPtr_base::~nsCOMPtr_base
from /usr/lib/libxul.so.0d
#15 NS_RegistryGetFactory
from /usr/lib/libxul.so.0d
#16 NS_RegistryGetFactory
from /usr/lib/libxul.so.0d
#17 NS_RegistryGetFactory
from /usr/lib/libxul.so.0d
#18 NS_RegistryGetFactory
from /usr/lib/libxul.so.0d
#19 PL_HandleEvent
from /usr/lib/libxul.so.0d
#20 PL_ProcessPendingEvents
from /usr/lib/libxul.so.0d
#21 nsAutoMonitor::NewMonitor
from /usr/lib/libxul.so.0d
#22 JSD_DebuggerOnForUser
from /usr/lib/libxul.so.0d
#23 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0





------- Bug created by bug-buddy at 2007-01-12 17:11 -------

Comment 1 palfrey 2007-01-12 22:11:03 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 ***