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 496638 - crash in Epiphany Web Browser: close the program
crash in Epiphany Web Browser: close the program
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-14 04:02 UTC by burak.demirtas
Modified: 2007-11-14 07:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description burak.demirtas 2007-11-14 04:02:31 UTC
Version: 2.20.1

What were you doing when the application crashed?
close the program


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 Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 374054912 vsize: 374054912 resident: 36941824 share: 22167552 rss: 36941824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195055891 rtime: 92 utime: 76 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2add2ddb6e50 (LWP 3704)]
[New Thread 0x42003950 (LWP 3712)]
[New Thread 0x41001950 (LWP 3710)]
[New Thread 0x40800950 (LWP 3707)]
(no debugging symbols found)
0x00002add28e5ac7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2add2ddb6e50 (LWP 3704))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/libgtkembedmoz.so.0d
  • #5 <signal handler called>
  • #6 ??
    from /lib/libc.so.6
  • #7 ??
  • #8 ephy_session_load
  • #9 ??
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (104 sec old) ---------------------
Refusing to initialize GTK+.
(process:3446): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
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
SESSION_MANAGER=local/omega:/tmp/.ICE-unix/3439
Window manager warning: Failed to read saved session file /home/burak/.metacity/sessions/default0.ms: Failed to open file '/home/burak/.metacity/sessions/default0.ms': No such file or directory
seahorse nautilus module initialized
Initializing gnome-mount extension
--------------------------------------------------
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2007-11-14 07:37:11 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 ***