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 540599 - crash in Epiphany Web Browser (Gecko): I think I just closed Ep...
crash in Epiphany Web Browser (Gecko): I think I just closed Ep...
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-28 12:06 UTC by yulomon
Modified: 2008-06-28 13:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description yulomon 2008-06-28 12:06:50 UTC 
Version: 2.22.2

What were you doing when the application crashed?
I think I just closed Epiphany.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-powerpc #1 Thu Jun 12 17:54:44 UTC 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 154447872 vsize: 154447872 resident: 80994304 share: 33013760 rss: 80994304 rss_rlim: 4294967295
CPU usage: start_time: 1214652002 rtime: 10485 utime: 9848 stime: 637 cutime:50 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany-gecko'

[Thread debugging using libthread_db enabled]
[New Thread 0x4804ed20 (LWP 2887)]
0x0e8ab290 in waitpid () from /lib/libpthread.so.0

+ Trace 201593

Thread 1 (Thread 0x4804ed20 (LWP 2887))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #5 <signal handler called>
  • #6 ??
  • #7 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 207
  • #8 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #9 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #10 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #11 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #12 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #13 g_io_unix_dispatch
  • #14 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #15 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #16 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #17 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.10/gtk/gtkmain.c line 1163
  • #18 main
    at /build/buildd/epiphany-browser-2.22.2/src/ephy-main.c line 744
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (35 sec old) ---------------------
** Message: GetValue variable 2 (2)
** (epiphany-gecko:2887): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (epiphany-gecko:2887): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (epiphany-gecko:2887): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
(evince:7434): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed
Shutting down
Child process exited with status 15
plugin instance destruction
shutting down input chan 0x10d85138
** (epiphany-gecko:7549): WARNING **: An error occured while calling remote method: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus secur
--------------------------------------------------
Comment 1 Susana 2008-06-28 13:45:03 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 509083 ***