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 469093 - crash in Epiphany Web Browser: Attempting to use the de...
crash in Epiphany Web Browser: Attempting to use the de...
Status: RESOLVED DUPLICATE of bug 419712
Product: epiphany
Classification: Core
Component: General
2.18.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-08-22 02:50 UTC by cardinal
Modified: 2007-08-22 08:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description cardinal 2007-08-22 02:50:37 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Attempting to use the del.icio.us syncing extension


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 493314048 vsize: 493314048 resident: 51638272 share: 26226688 rss: 51638272 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187750944 rtime: 176 utime: 152 stime: 24 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 47594575747936 (LWP 16635)]
[New Thread 1090525520 (LWP 16637)]
(no debugging symbols found)
0x00002b4975639c7f in waitpid () from /lib/libpthread.so.0

+ Trace 157028

Thread 1 (Thread 47594575747936 (LWP 16635))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
    from /usr/lib/libgtkembedmoz.so.0d
  • #3 <signal handler called>
  • #4 g_boxed_copy
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #6 ??
  • #7 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #8 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #9 PyEval_EvalFrame
    from /usr/lib/libpython2.4.so.1.0
  • #10 ??
    from /usr/lib/libpython2.4.so.1.0
  • #11 ??
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #14 ??
    from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (97 sec old) ---------------------
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security poli
(epiphany-browser:14423): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
StopIteration
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-08-22 08:52:49 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 419712 ***