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 360177 - Crash when print poscritp to file.
Crash when print poscritp to file.
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-10-06 14:20 UTC by Alexander Blazej
Modified: 2006-10-06 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Alexander Blazej 2006-10-06 14:19:47 UTC
Distribution: Debian 3.1 (sarge)
Package: epiphany
Severity: Normal
Version: GNOME2.14.2 2.14.x
Gnome-Distributor: Debian
Synopsis: Crash when print poscritp to file.
Bugzilla-Product: epiphany
Bugzilla-Component: Printing
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:


Steps to reproduce the crash:
1. Select print
2. Select generic postcript
3. Select to file
4. Click print, then it crashes.

How often does this happen?
This is the firt time I tired to print to file.



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 -1240975680 (LWP 6845)]
[New Thread -1325577296 (LWP 7193)]
[New Thread -1262101584 (LWP 6859)]
[New Thread -1244279888 (LWP 6850)]
(no debugging symbols found)
0xb7061221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1240975680 (LWP 6845))

  • #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-10-06 14:20 -------

Comment 1 Karsten Bräckelmann 2006-10-06 14:51:46 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 ***