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 522562 - crash in Epiphany Web Browser: trataba de configurar ep...
crash in Epiphany Web Browser: trataba de configurar ep...
Status: RESOLVED DUPLICATE of bug 419712
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.20.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-15 07:30 UTC by hxtr227
Modified: 2008-03-15 11:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description hxtr227 2008-03-15 07:30:38 UTC 
Version: 2.20.3

What were you doing when the application crashed?
trataba de configurar epilicious


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (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: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 493060096 vsize: 493060096 resident: 59375616 share: 30691328 rss: 59375616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1205566051 rtime: 245 utime: 226 stime: 19 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 0x2b03d604af20 (LWP 7772)]
[New Thread 0x41001950 (LWP 7774)]
[New Thread 0x40800950 (LWP 7773)]
(no debugging symbols found)
0x00002b03d018234f in waitpid () from /lib/libpthread.so.0

+ Trace 192465

Thread 1 (Thread 0x2b03d604af20 (LWP 7772))

  • #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 g_boxed_copy
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #8 ??
  • #9 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #10 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #12 ??
    from /usr/lib/libpython2.4.so.1.0
  • #13 ??
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #15 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #16 ??
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 ??
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 waitpid
    from /lib/libpthread.so.0 



--------------------------------------------------
Comment 1 Gianluca Borello 2008-03-15 11:45:12 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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