Nautilus crash when attempting to duplicate a folder

Bug #233865 reported by vexorian
4
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: nautilus

The nautilus version I am using is "1:2.22.2-0ubuntu6" in hardy.

Whenever I try to duplicate a folder nautilus crashes and restarts on /home/username/ I tried running nautilus from the terminal and reproducing the bug but no error message seems to appear.

Steps to reproduce:
Go to your home
Select a folder, if there is no folder there, temporarily create one, just make sure to also add a file to it.
Control+C (copy)
Control+V (paste)
The normal behavior is that a copy for the folder is created, but in this setup this procedure crashes nautilus. I have tried the same on files and there is no crash. I have also tried on empty folders, that also seems to prevent the crash.

I am attaching valgrind's output when reproducing the crash.

Revision history for this message
vexorian (vexorian) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, are you using a spanish locale? there is a known translation issue creating this issue, that's fixed in rosetta and waiting for language pack updates

Changed in nautilus:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
barichardson5727 (barichardson5727-gmail) wrote :

I have been having similar problems after updating nautilus to version 1:2.22.2-0ubuntu6. Copying folders is causing nautilus to go non-responsive. If you kill the process it will respawn a new window to of your home directory, the new instance of nautilus that gets created is usually non-responsive upon being created. I have confirmed this problem did not exist with nautilus version 1:2.22.2-0ubuntu5 on the same machine. Also, my system is not using spanish locale so I don't believe this to be a translation issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that's not likely, the valgrind log is similar to the other bug, you likely have not tested correctly

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.