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 496260 - crash in Epiphany Web Browser: Login with nession resto...
crash in Epiphany Web Browser: Login with nession resto...
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-12 20:54 UTC by jam
Modified: 2007-11-12 21:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description jam 2007-11-12 20:54:23 UTC 
Version: 2.20.1

What were you doing when the application crashed?
Login with nession restore


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

System: Linux 2.6.22-3-k7 #1 SMP Mon Oct 22 22:51:54 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 71581696 vsize: 71581696 resident: 25149440 share: 17350656 rss: 25149440 rss_rlim: 4294967295
CPU usage: start_time: 1194900755 rtime: 106 utime: 96 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/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb60626c0 (LWP 14785)]
[New Thread 0xb4a39b90 (LWP 15075)]
[New Thread 0xb533eb90 (LWP 15048)]
[New Thread 0xb5ca5b90 (LWP 15030)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 177280

Thread 1 (Thread 0xb60626c0 (LWP 14785))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 210
  • #6 <signal handler called>
  • #7 ??
    from /lib/i686/cmov/libc.so.6
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (68 sec old) ---------------------
program instead. For further details, see:
    http://www.gtk.org/setuid.html
Refusing to initialize GTK+.
/etc/gdm/Xsession: Beginning session setup...
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
** Message: Another GPG agent already running
SESSION_MANAGER=local/athene:/tmp/.ICE-unix/14618
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
seahorse nautilus module initialized
Initializing gnome-mount extension
** Message: failed to load session from /home/jam/.nautilus/saved-session-NBRXTT
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-11-12 21:07:57 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.


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