GNOME Bugzilla – Bug 169722
nautilus crashes after moving image files and then right-click on the destination folder
Last modified: 2005-03-09 16:47:10 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: nautilus crashes after moving image files and then right-click on the destination folder Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: i moved some files from one dir to a sub dir, then right-clicked on the sub dir and then in crashed. i think it only happens with omage files. i tried some others too and it didn't crash. secondly, it seems only to happen when i have the "view as list" option on. maybe it's similar to crash # 146483? but i think it's not the same. Steps to reproduce the crash: first i have to say that this way of reproducing the crash doesn't always work. so try several times if it doesn't crash. 1. create a dir (let's call it pictures) somewhere (i created mine in the home directory, also tried it on the desktop). 2. copy/move/... some image files (i took two of them) to the pictures dir. 3. create a subdir (let's call it pictures_sub) in the pictures dir. okay, this was the first part which works fine. just the second part caused a crash. 4. open the pictures directory 5. in this window, drag your image files from pictures to pictures_sub 6. right-klick on pictures_sub 7. crash :-( if it doesn't work, move your files back to the pictures dir, close all nautilus windows and try again from point 4 on. Expected Results: i hope i could help you by solving nautilus problems. How often did this happen? about each 2nd or 3rd time i tried points 4 to 6 above. Additional Information: Nautilus 2.8.1 (german) on Ubuntu Linux (didn't find any version but it's quite new. german, too) greets, maxli when you have questions, email me. maxli_@hotmail.com Debugging Information: 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4125)] [New Thread 1102613424 (LWP 4145)] [Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4125)] [New Thread 1102613424 (LWP 4145)] [Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 4125)] [New Thread 1102613424 (LWP 4145)] (no debugging symbols found)...[New Thread 1101675440 (LWP 4135)] (no debugging symbols found)...[New Thread 1101409200 (LWP 4134)] (no debugging symbols found)...[New Thread 1101142960 (LWP 4133)] (no debugging symbols found)...[New Thread 1100860336 (LWP 4130)] (no debugging symbols found)...[New Thread 1100200880 (LWP 4129)] (no debugging symbols found)...[New Thread 1099893680 (LWP 4126)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 56631
Thread 8 (Thread 1099893680 (LWP 4126))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-09 11:23 ------- Unknown version 2.8.1 in product nautilus. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was maxli_@hotmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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. Matches the stack trace in bug 166556, which has been marked as a duplicate of 146483. *** This bug has been marked as a duplicate of 146483 ***