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 385113 - crash when trying to print
crash when trying to print
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-12-12 16:53 UTC by ljlencina
Modified: 2006-12-12 22:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description ljlencina 2006-12-12 16:51:45 UTC 
Distribution: Debian testing/unstable
Package: epiphany
Severity: major
Version: GNOME2.14.3 2.14.x
Gnome-Distributor: Debian
Synopsis: crash when trying to print
Bugzilla-Product: epiphany
Bugzilla-Component: Printing
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

Click on the button print and when i sent to then printer it
automatically crash

Steps to reproduce the crash:
1. open epiphany
2. click on print and select printer
3. click print

Expected Results:


How often does this happen?
every time i click on print

Additional Information:
I use cups 1.2.7 for manage printer


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 -1508411712 (LWP 17913)]
[New Thread -1564283984 (LWP 17985)]
[New Thread -1555895376 (LWP 17984)]
[New Thread -1547506768 (LWP 17983)]
[New Thread -1530729552 (LWP 17982)]
[New Thread -1539118160 (LWP 17955)]
[New Thread -1522230352 (LWP 17953)]
[New Thread -1513657424 (LWP 17952)]
(no debugging symbols found)
0xa708f231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 93588

Thread 1 (Thread -1508411712 (LWP 17913))

  • #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-12-12 16:53 -------
Comment 1 Bruno Boaventura 2006-12-12 21:03:45 UTC 
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Can you get us one with debugging
symbols? Please see http://live.gnome.org/GettingTraces for more information on
how to do so.

Could you also please try to reproduce the problem with Mozilla? This is
possibly the same bug as https://bugzilla.mozilla.org/show_bug.cgi?id=294879.
Comment 2 Christian Persch 2006-12-12 22:19:11 UTC 

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