GNOME Bugzilla – Bug 369579
[2x nautilus_file_is_hidden_file] renaming a folder
Last modified: 2007-10-19 01:12:01 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 116092928 vsize: 0 resident: 116092928 share: 0 rss: 46071808 rss_rlim: 0 CPU usage: start_time: 1162469375 rtime: 0 utime: 5466 stime: 0 cutime:5011 cstime: 0 timeout: 455 it_real_value: 0 frequency: 1233 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226479952 (LWP 4816)] [New Thread -1278227552 (LWP 5886)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 82004
Thread 1 (Thread -1226479952 (LWP 4816))
*** Bug 370872 has been marked as a duplicate of this bug. ***
*** Bug 371616 has been marked as a duplicate of this bug. ***
*** Bug 371740 has been marked as a duplicate of this bug. ***
*** Bug 373681 has been marked as a duplicate of this bug. ***
confirming as per duplicate
*** Bug 379034 has been marked as a duplicate of this bug. ***
*** Bug 376219 has been marked as a duplicate of this bug. ***
*** Bug 377300 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
*** Bug 379695 has been marked as a duplicate of this bug. ***
*** Bug 381133 has been marked as a duplicate of this bug. ***
*** Bug 381565 has been marked as a duplicate of this bug. ***
Can anybody of the reporters please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1\] debugging packages for nautilus, glib, gtk, gnome-vfs and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 391270 has been marked as a duplicate of this bug. ***
*** Bug 392216 has been marked as a duplicate of this bug. ***
*** Bug 392454 has been marked as a duplicate of this bug. ***
*** Bug 392544 has been marked as a duplicate of this bug. ***
*** Bug 395489 has been marked as a duplicate of this bug. ***
*** Bug 396451 has been marked as a duplicate of this bug. ***
*** Bug 397545 has been marked as a duplicate of this bug. ***
*** Bug 397850 has been marked as a duplicate of this bug. ***
*** Bug 398123 has been marked as a duplicate of this bug. ***
*** Bug 399035 has been marked as a duplicate of this bug. ***
*** Bug 401601 has been marked as a duplicate of this bug. ***
*** Bug 402683 has been marked as a duplicate of this bug. ***
*** Bug 402855 has been marked as a duplicate of this bug. ***
*** Bug 404029 has been marked as a duplicate of this bug. ***
*** Bug 404758 has been marked as a duplicate of this bug. ***
*** Bug 405606 has been marked as a duplicate of this bug. ***
*** Bug 405703 has been marked as a duplicate of this bug. ***
*** Bug 406964 has been marked as a duplicate of this bug. ***
*** Bug 408176 has been marked as a duplicate of this bug. ***
*** Bug 408496 has been marked as a duplicate of this bug. ***
*** Bug 408257 has been marked as a duplicate of this bug. ***
*** Bug 409862 has been marked as a duplicate of this bug. ***
*** Bug 410786 has been marked as a duplicate of this bug. ***
Dear reporters, could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, libgnome2-0-dbgsym, and libgnomeui-0-dbg. Fedora Core 6 and OpenSuSE 10.2: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. SuSE provides a debuginfo package repository, that users can add to their installation sources, under http://download.opensuse.org/distribution/10.2/repo/debug/suse/ . More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 412625 has been marked as a duplicate of this bug. ***
*** Bug 413047 has been marked as a duplicate of this bug. ***
*** Bug 413458 has been marked as a duplicate of this bug. ***
*** Bug 413460 has been marked as a duplicate of this bug. ***
*** Bug 414273 has been marked as a duplicate of this bug. ***
This bug happened during my first struggles with linux and mythtv. I ran into a logon problem with the mythtv account. I found out that the mythtv home folder was owned by the mysql account and I decided to uninstall both mysql-server and mythtv. During uninstall i decided to delete the mythtv folder and I believe that triggered the bug
*** Bug 418499 has been marked as a duplicate of this bug. ***
*** Bug 420236 has been marked as a duplicate of this bug. ***
*** Bug 423744 has been marked as a duplicate of this bug. ***
*** Bug 423347 has been marked as a duplicate of this bug. ***
Ce bug est apparu lorsque je renommait un dossier. Le nom du dossier était en caractère majuscule et je voulait le renommer en minuscule. Nautilus ne l'a pas renommer, et ensuite la fenêtre de bug est apparu. J'ai remarqué par la suite que ce bug est apparu plusieurs fois lorsque le dossier que je renommait était situé sur un disque formaté en FAT32. Depuis que le disque est au format EXT3 le bug a disparu.
vinssounou: thanks for your comment and the explanation how to reproduce, but we really need a better stacktrace, as described in comment 38.
*** Bug 425193 has been marked as a duplicate of this bug. ***
*** Bug 425192 has been marked as a duplicate of this bug. ***
*** Bug 425144 has been marked as a duplicate of this bug. ***
*** Bug 427278 has been marked as a duplicate of this bug. ***
*** Bug 438608 has been marked as a duplicate of this bug. ***
*** Bug 441329 has been marked as a duplicate of this bug. ***
*** Bug 441346 has been marked as a duplicate of this bug. ***
*** Bug 443817 has been marked as a duplicate of this bug. ***
*** Bug 444767 has been marked as a duplicate of this bug. ***
*** Bug 447729 has been marked as a duplicate of this bug. ***
*** Bug 447626 has been marked as a duplicate of this bug. ***
*** Bug 452532 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!