Nautilus hangs on opening Trash

Bug #544859 reported by JanHolbo
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I cannot be 100% sure that the bug is in nautilus, it may be in related packages. When opening Trash, Nautilus "hangs" with high CPU usage. There is no crash and seem to be no extra memory usage.

All further interaction with nautilus is futile. This bug has been experienced on kernels 2.6.32-14. -16 and -17. This report is generated on -17.

Install is an Ubuntu 10.04 lucid lynx Alpha 3 updated with apt-get update/upgrade today (23/3-2010, 8am CET).

ProblemType: Bug
Architecture: i386
Date: Tue Mar 23 09:11:58 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
Package: nautilus 1:2.29.92.1-0ubuntu4
ProcEnviron:
 LANG=en_DK.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: nautilus
Uname: Linux 2.6.32-17-generic i686

Revision history for this message
JanHolbo (janholbo) wrote :
Revision history for this message
JanHolbo (janholbo) wrote :
Revision history for this message
JanHolbo (janholbo) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, please try to obtain a backtrace of that hang manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. Thanks in advance.

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
JanHolbo (janholbo) wrote :

I had to deviate from the course set out by the web page https://wiki.ubuntu.com/Backtrace.

When I start nautilus from gdb it starts threads and I cannot control it through gdb any longer. Only way out is to force quite nautilus and then gdb crashes.

So I elected to attach gdb to the running thread of nautilus (up to now still following instructions).

Here is where I had to deviate:

When I attach gdb to the running process and continue gdb, same as above happens and I loose control over gdb. So I did the backtrace _without_ continue. I figure it is probably in its infinite loop or dead lock anyway, so I hope the data is usable.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

It seems to be a memory allocation problem, could you please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Revision history for this message
JanHolbo (janholbo) wrote : Re: [Bug 544859] Re: Nautilus hangs on opening Trash

I updated to lucid lynx beta 1 yesterday and the problem seems persistent. I
will post the Valgrind log when I can.

2010/3/23 Pedro Villavicencio <email address hidden>

> It seems to be a memory allocation problem, could you please try to
> obtain a valgrind log following the instructions at
> https://wiki.ubuntu.com/Valgrind and attach the file to the bug report.
> This will greatly help us in tracking down your problem.
>
> --
> Nautilus hangs on opening Trash
> https://bugs.launchpad.net/bugs/544859
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nautilus” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: nautilus
>
> I cannot be 100% sure that the bug is in nautilus, it may be in related
> packages. When opening Trash, Nautilus "hangs" with high CPU usage. There is
> no crash and seem to be no extra memory usage.
>
> All further interaction with nautilus is futile. This bug has been
> experienced on kernels 2.6.32-14. -16 and -17. This report is generated on
> -17.
>
> Install is an Ubuntu 10.04 lucid lynx Alpha 3 updated with apt-get
> update/upgrade today (23/3-2010, 8am CET).
>
> ProblemType: Bug
> Architecture: i386
> Date: Tue Mar 23 09:11:58 2010
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
> Package: nautilus 1:2.29.92.1-0ubuntu4
> ProcEnviron:
> LANG=en_DK.utf8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
> SourcePackage: nautilus
> Uname: Linux 2.6.32-17-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/544859/+subscribe
>

--
Jan Holbo Rasmussen
http://www.kaddu.dk - Familiens Web site | The Family Web Site
http://janholbodk.blogspot.com - Min danske blog | My Danish (and primary
blog)
http://twitter.com/JanHolbo - Mit twitter feed | My Twitter feed
http://kaddulinux.blogspot.dk - Min Linux blog (på engelsk) - My Linux Blog

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Ok, Thank you Jan. Please keep us posted.

Revision history for this message
Rune K. Svendsen (runeks) wrote :

Could this be a duplicate of Bug #553082?
Please try emptying your trash, then open it up to see if it still hangs. If it doesn't hang, try deleting some random files and test if it still hangs.
If it still doesn't hang, then try creating a new folder and setting the folder to use an emblem (right click folder -> Properties -> Emblems -> Draft (for example)), then delete this folder.
Now open the trash again, if it hangs this time it's a duplicate of Bug #553082.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
Revision history for this message
effell (effell) wrote :

In case anyone else is having similar problems:

Nautilus 3.10.1 on Ubuntu 14.04 started hanging both on "Delete File" and "Empty Trash".

Rebooting in safe mode and running disk checks fixed it for me.

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.