GNOME Bugzilla – Bug 618086
Crash in IA__g_type_check_instance, set_pending_icon_to_reveal at nautilus-icon-container.c line 622
Last modified: 2010-05-10 20:26:30 UTC
Version: 2.28.3 What were you doing when the application crashed? Browsing a folder of videos in Nautilus. The CD/DVD Creator application was not intentionally invoked and was never seen. Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-3-powerpc64 #1 SMP Thu Feb 25 08:18:03 UTC 2010 ppc64 X Vendor: The X.Org Foundation X Vendor Release: 10706901 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 215179264 vsize: 215179264 resident: 88625152 share: 27684864 rss: 88625152 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273304630 rtime: 3078 utime: 2752 stime: 326 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xef921400 (LWP 20168)] 0x0fe5d4f0 in waitpid () from /lib/libpthread.so.0
+ Trace 221812
Thread 1 (Thread 0xf7b40000 (LWP 18425))
Inferior 1 [process 18425] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- Minor opcode of failed request: 47 () Serial number of failed request: 15 Current serial number in output stream: 15 Failure: Module initalization failed MCS->Xfconf settings migration complete (gnome-panel:18424): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -13 and height 24 Initializing nautilus-gdu extension (gnome-panel:18424): Gdk-WARNING **: /build/buildd-gtk+2.0_2.20.0-3-powerpc-fDfgMi/gtk+2.0-2.20.0/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window App startup ** (deja-dup-monitor:18433): DEBUG: monitor.vala:263: Invalid next run date. Not scheduling a backup. Cannot access memory at address 0x8 --------------------------------------------------
could be related to bug 452894
Yes, brasero or its libraries did not seem to appear in the stack trace and the last 4 functions that appear before the crash are exactly similar to the bug you mentioned. Thanks for pointing this out. Setting this bug as a duplicate of the aforementioned bug. 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 bug 452894 ***