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 357222 - Crash whilst printing selection from web page
Crash whilst printing selection from web page
Status: RESOLVED DUPLICATE of bug 356632
Product: epiphany
Classification: Core
Component: Printing
2.14.x
Other other
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-09-22 17:20 UTC by andy
Modified: 2006-09-22 18:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description andy 2006-09-22 17:20:01 UTC 
Distribution: Debian testing/unstable
Package: epiphany
Severity: Normal
Version: GNOME2.14.3 2.14.x
Gnome-Distributor: Debian
Synopsis: Crash whilst printing selection from web page
Bugzilla-Product: epiphany
Bugzilla-Component: Printing
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Open web page
2.  Select text
3.  Select print, get print dialog.
4. Crashes when close print dialog.

Expected Results: Printed selection. 

How often does this happen? Always.

Printer is hosted on Windows, accessed through CUPS as an SMB printer.

Additional Information:



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 -1508464960 (LWP 8353)]
[New Thread -1569281104 (LWP 8368)]
[New Thread -1560892496 (LWP 8367)]
[New Thread -1552503888 (LWP 8366)]
[New Thread -1535710288 (LWP 8365)]
[New Thread -1544098896 (LWP 8364)]
[New Thread -1527211088 (LWP 8360)]
[New Thread -1516254288 (LWP 8354)]
(no debugging symbols found)
0xa7081201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 73002

Thread 1 (Thread -1508464960 (LWP 8353))

  • #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 2006-09-22 17:20 -------
Comment 1 Karsten Bräckelmann 2006-09-22 18:25: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.


Matches the stacktrace in bug 357163, which is a duplicate of bug 356544, which in turn is a duplicate of bug 356632. Yay. ;)


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