Bug 357163 – Crash after printing

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 357163 - Crash after printing


Summary:	Crash after printing


Status:	RESOLVED DUPLICATE of bug 356544

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:	2006-09-22 08:53 UTC by Michal Čihař
Modified:	2006-09-22 09:57 UTC

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

Description Michal Čihař 2006-09-22 08:52:49 UTC

Distribution: Debian testing/unstable
Package: epiphany
Severity: Normal
Version: GNOME2.14.3 2.14.x
Gnome-Distributor: Debian
Synopsis: Crash after printing
Bugzilla-Product: epiphany
Bugzilla-Component: Printing
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
I tried to print OBB time table and I got crash.

Steps to reproduce the crash:
1. Go to
http://fahrplan.oebb.at/bin/query.exe/en?ld=oebb&seqnr=14&ident=fg.01576132.1158914224&OK#focus
(I'm not sure if the url will not timeout)
2. Print it
3. You get this crash

Expected Results:
No crash

How often does this happen?
Every time

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1508866368 (LWP 6949)]
[New Thread -1605751888 (LWP 6962)]
[New Thread -1561539664 (LWP 6955)]
[New Thread -1552684112 (LWP 6954)]
[New Thread -1544291408 (LWP 6953)]
[New Thread -1535837264 (LWP 6952)]
[New Thread -1527444560 (LWP 6951)]
[New Thread -1514038352 (LWP 6950)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 72973

Thread 1 (Thread -1508866368 (LWP 6949))

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





------- Bug created by bug-buddy at 2006-09-22 08:53 -------

Comment 1 Reinout van Schouwen 2006-09-22 09:57:12 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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