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 493019 - crash in Epiphany Web Browser: Logging into Gnome
crash in Epiphany Web Browser: Logging into Gnome
Status: RESOLVED DUPLICATE of bug 488718
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.20.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-03 12:16 UTC by Matijs van Zuijlen
Modified: 2007-11-05 00:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Matijs van Zuijlen 2007-11-03 12:16:25 UTC 
Version: 2.20.1

What were you doing when the application crashed?
Logging into Gnome


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Thu Oct 11 15:23:23 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: gartoon

Memory status: size: 448663552 vsize: 448663552 resident: 49397760 share: 24305664 rss: 49397760 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194092151 rtime: 110 utime: 100 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b9af3979e50 (LWP 9010)]
[New Thread 0x41802950 (LWP 9182)]
[New Thread 0x41001950 (LWP 9178)]
[New Thread 0x40800950 (LWP 9168)]
0x00002b9aeea1dc7f in waitpid () from /lib/libpthread.so.0

+ Trace 174836

Thread 1 (Thread 0x2b9af3979e50 (LWP 9010))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.14.2/glib/gspawn.c line 369
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.14.2/glib/gspawn.c line 677
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 210
  • #5 <signal handler called>
  • #6 ??
    from /lib/libc.so.6
  • #7 int_from_string
    at /usr/include/stdlib.h line 336
  • #8 ephy_session_load
    at /build/buildd/epiphany-browser-2.20.1/src/ephy-session.c line 1483
  • #9 session_command_dispatch
    at /build/buildd/epiphany-browser-2.20.1/src/ephy-session.c line 729
  • #10 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.2/glib/gmain.c line 2061
  • #11 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.2/glib/gmain.c line 2694
  • #12 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.2/glib/gmain.c line 2898
  • #13 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.1/gtk/gtkmain.c line 1146
  • #14 main
    at /build/buildd/epiphany-browser-2.20.1/src/ephy-main.c line 725
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (20 sec old) ---------------------
(gpilotd:9009): libgpilotdcm-WARNING **: No accessible devices available
(gpilotd:9009): libgpilotdcm-WARNING **: Number of PDAs is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing gnome-mount extension
seahorse nautilus module initialized
** (empathy:9014): DEBUG: check_for_accounts: No enabled accounts
** (empathy:9014): DEBUG: check_for_accounts: No enabled accounts
** (empathy:9014): DEBUG: check_for_accounts: No enabled accounts
(gnome-panel:8985): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-11-05 00:22:53 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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