GNOME Bugzilla – Bug 531771
crash in About Me: Attempting to select an ...
Last modified: 2008-05-06 16:54:39 UTC
Version: 2.22.1 What were you doing when the application crashed? Attempting to select an image, the file selector loaded, and then the app crashed. Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.1 2008-04-22 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.24-gentoo-r6-adc1 #1 SMP PREEMPT Wed Apr 23 14:36:24 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76107776 vsize: 76107776 resident: 25509888 share: 12824576 rss: 25509888 rss_rlim: 4294967295 CPU usage: start_time: 1210089440 rtime: 37 utime: 31 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-about-me' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb5f55700 (LWP 21632)] [New Thread 0xb3fffb90 (LWP 21642)] [New Thread 0xb4962b90 (LWP 21641)] [New Thread 0xb4a02b90 (LWP 21636)] [New Thread 0xb5203b90 (LWP 21633)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197043
Thread 3 (Thread 0xb4962b90 (LWP 21641))
----------- .xsession-errors --------------------- (epiphany:8716): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany:8716): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (gnome-about-me:21632): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GThemedIcon' has no property named `names' (gnome-about-me:21632): GLib-GIO-CRITICAL **: g_themed_icon_constructed: assertion `themed->names != NULL && themed->names[0] != NULL' failed (gnome-about-me:21632): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed GLib-GObject-ERROR **: g_type_plugin_*() invalidly modified type `GLocalFileEnumerator' aborting... Cannot access memory at address 0x0 Cannot access memory at address 0x0 --------------------------------------------------
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 526242 ***