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 396733 - crash in Epiphany: Closing print preview wi...
crash in Epiphany: Closing print preview wi...
Status: RESOLVED DUPLICATE of bug 390223
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-01-15 03:26 UTC by arnwit
Modified: 2007-01-15 08:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description arnwit 2007-01-15 03:26:39 UTC
Version: 2.16.1

What were you doing when the application crashed?
Closing print preview window


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 537628672 vsize: 537628672 resident: 49836032 share: 33423360 rss: 83259392 rss_rlim: 838369280
CPU usage: start_time: 1168830176 rtime: 3127 utime: 2925 stime: 202 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47271023824880 (LWP 6529)]
[New Thread 1157667136 (LWP 6654)]
[New Thread 1140881728 (LWP 6649)]
[New Thread 1107310912 (LWP 6560)]
[New Thread 1115703616 (LWP 6559)]
[New Thread 1090525504 (LWP 6531)]
[New Thread 1082132800 (LWP 6530)]
(no debugging symbols found)
0x00002afe1faaec5f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 47271023824880 (LWP 6529))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 nsProfileLock::FatalSignalHandler
    from /usr/lib64/xulrunner-1.8.1b2/libgtkembedmoz.so
  • #3 <signal handler called>
  • #4 FcCharSetDestroy
    from /usr/lib64/libfontconfig.so.1
  • #5 nsFontMetricsPS::~nsFontMetricsPS
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #6 nsFontPSAFM::FindFont
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #7 nsFontCache::Flush
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #8 nsFontCache::~nsFontCache
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #9 nsFontCachePS::~nsFontCachePS
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #10 DeviceContextImpl::~DeviceContextImpl
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #11 nsDeviceContextPS::~nsDeviceContextPS
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #12 DeviceContextImpl::Release
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #13 nsCOMPtr<nsIDeviceContext>::operator=
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #14 DeviceContextImpl::SetAltDevice
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #15 DocumentViewerImpl::InitInternal
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #16 DocumentViewerImpl::ReturnToGalleyPresentation
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #17 DocumentViewerImpl::PrepareToStartLoad
    from /usr/lib64/xulrunner-1.8.1b2/libxul.so
  • #18 EphyBrowser::SetPrintPreviewMode
  • #19 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #20 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #23 gtk_widget_get_action
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #25 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #27 g_signal_emit_by_name
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #29 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #31 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #32 gtk_button_set_alignment
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #33 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #34 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #37 gtk_button_released
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #38 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #39 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #40 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #43 gtk_widget_get_default_style
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #44 gtk_propagate_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #45 gtk_main_do_event
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #46 gdk_add_client_message_filter
    from /opt/gnome/lib64/libgdk-x11-2.0.so.0
  • #47 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #48 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #50 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #51 main
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 Reinout van Schouwen 2007-01-15 08:25:47 UTC
Thanks for taking the time to report this bug.
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 in order to help the developers?


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