GNOME Bugzilla – Bug 452894
crash in set_pending_icon_to_reveal at nautilus-icon-container.c:569
Last modified: 2015-11-24 11:37:57 UTC
Version: 2.18.1 What were you doing when the application crashed? Crash while creating a new directory. Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Toxig Icon Theme: Iris Memory status: size: 435679232 vsize: 435679232 resident: 71159808 share: 18472960 rss: 71159808 rss_rlim: 18446744073709551615 CPU usage: start_time: 1183285743 rtime: 4325 utime: 3817 stime: 508 cutime:1914 cstime: 183 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47925914649712 (LWP 5165)] 0x00002b96996c0c9f in waitpid () from /lib/libpthread.so.0
+ Trace 145087
Thread 1 (Thread 47925914649712 (LWP 5165))
*** Bug 536612 has been marked as a duplicate of this bug. ***
*** Bug 541160 has been marked as a duplicate of this bug. ***
*** Bug 549806 has been marked as a duplicate of this bug. ***
*** Bug 569969 has been marked as a duplicate of this bug. ***
*** Bug 570514 has been marked as a duplicate of this bug. ***
Last duplicates appear to be with 2.22.2. Can anyone reproduce with 2.26?
we got a similar crash on 2.28.0, here: https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/447459 "#0 0x00007f0729ae2665 in g_type_check_instance () from /usr/lib/libgobject-2.0.so.0 No symbol table info available.
+ Trace 218276
*** Bug 602613 has been marked as a duplicate of this bug. ***
*** Bug 618086 has been marked as a duplicate of this bug. ***
*** Bug 542199 has been marked as a duplicate of this bug. ***
*** Bug 634883 has been marked as a duplicate of this bug. ***
last dupe in 2.30.x
Still actual for 3.1.90.
How can I reproduce this? Does it still happen with 3.14?
Closing this bug report as no further information has been provided and code has change quite a bit in the meantime. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!