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 460292 - crash in Epiphany Web Bookmarks: non riesco a utilizzare ...
crash in Epiphany Web Bookmarks: non riesco a utilizzare ...
Status: RESOLVED DUPLICATE of bug 349051
Product: epiphany
Classification: Core
Component: General
2.14.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-07-25 16:38 UTC by salvo00365
Modified: 2007-07-25 23:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description salvo00365 2007-07-25 16:38:27 UTC 
Version: 2.14.3

What were you doing when the application crashed?
non riesco a utilizzare gnome-art


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

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: DebianRed
Icon Theme: BlankOn

Memory status: size: 83648512 vsize: 83648512 resident: 31563776 share: 21442560 rss: 31563776 rss_rlim: 4294967295
CPU usage: start_time: 1185395755 rtime: 3081 utime: 3035 stime: 46 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1242052928 (LWP 4747)]
0xb7ef37f2 in ?? () from /lib/ld-linux.so.2

+ Trace 150481

Thread 1 (Thread -1242052928 (LWP 4747))

  • #0 ??
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 gtk_moz_embed_get_title
    from /usr/lib/libgtkembedmoz.so.0d
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 __pthread_mutex_unlock_usercnt
    from /lib/i686/cmov/libpthread.so.0
  • #12 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.10.13/gtk/gtkmain.c line 1154
  • #17 main
  • #0 ??
    from /lib/ld-linux.so.2 


----------- .xsession-errors ---------------------
/usr/lib/ruby/1.8/glib2.rb: line 55
   GLib-GObject-CRITICAL **:g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
/usr/bin/gnome-art: line 22
   Gtk-WARNING **:Impossibile trovare il motore del tema in module_path: «lighthouseblue»,
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
/usr/lib/ruby/1.8/gnome-art/gnome_art.rb:144: warning: GRClosure invoking callback: already destroyed
(epiphany:4747): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed
(bug-buddy:4798): Gtk-WARNING **: Impossibile trovare il motore del tema in module_path: «lighthouseblue»,
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-07-25 23:45:55 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 349051 ***