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 364665 - Epiphany crashes on printing
Epiphany crashes on printing
Status: RESOLVED DUPLICATE of bug 356632
Product: epiphany
Classification: Core
Component: Printing
2.14.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-10-24 10:15 UTC by Stefan Jenkner
Modified: 2006-10-24 11:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Stefan Jenkner 2006-10-24 10:15:36 UTC
Steps to reproduce:
1. Open a webside
2. Select print
3. Select printer or select generic postscript, save to file
4. Select print

Expected Results:
Epiphany crashes

How often does this happen?
Always


Stack trace:
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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1508488704 (LWP 6410)]
[New Thread -1571124304 (LWP 6418)]
[New Thread -1562731600 (LWP 6417)]
[New Thread -1554338896 (LWP 6416)]
[New Thread -1537279056 (LWP 6415)]
[New Thread -1545671760 (LWP 6414)]
[New Thread -1528775760 (LWP 6412)]
[New Thread -1519715408 (LWP 6411)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1508488704 (LWP 6410))

  • #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



Other information:
Additional Information:
on debian etch, epiphany is build against xulrunner
Comment 1 André Klapper 2006-10-24 11:15:46 UTC
Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!


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