not working correctly when run using sudo

Bug #238668 reported by Waleb
140
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Tested on 2 independent Ubuntu 8.04 systems:

When I open Nautilus with: "sudo nautilus" and then click on "Trash" on the left side nautilus takes all the available RAM until its killed manually.

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

thank you for your bug report, confirming, setting low setting though since nautilus should not be ran using sudo, that should be sent on bugzilla.gnome.org though

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, it looks like http://bugzilla.gnome.org/show_bug.cgi?id=537298 ; which is known upstream already, linking the bug, thanks.

Changed in nautilus:
status: Confirmed → Triaged
Changed in nautilus:
status: Unknown → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

you can use "sudo dbus-launch nautilus" to workaround the issue

Changed in nautilus:
status: Incomplete → New
Revision history for this message
Nanley Chery (nanoman) wrote :

This bug also occurs when you run "gksudo nautilus" or "gksu nautilus." Tested on 8.04.1.
This bug really caught me off guard, maybe we should set this to a higher importance?

Changed in nautilus:
importance: Low → Medium
Revision history for this message
davidr (davaweb) wrote :

Re the comments in #310122 re fixing it in hardy 8.04 / 8.04.1

This is a LTS release specificially so people don't have to upgrade to the most recent version with all the possible 'new' bugs that might entail.

Please tell me what LTS means if your solution is to upgrade to Intrepid which is not LTS? You are putting us on a path of upgrading to every new version instead of getting the support.

David

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

the bug is still open so there is no stable update to consider yet there

Revision history for this message
davidr (davaweb) wrote :

Quote:

"the bug is still open so there is no stable update to consider yet there"

I am not meaning to be offensive, but isn't that saying that the solution if Jaunty (? - the next release) solves the bug then 'to update' will be the suggestion if it isn't fixed by then?

From the comments I referred to, it came across to me and other posters that 'update' may be the suggested solution.

David

Revision history for this message
davidr (davaweb) wrote :

I don't know how to edit my comments ...
please read:
I am not meaning to be offensive, but isn't that saying that if Jaunty (? - the next release) solves the bug, then 'to update' will be the suggestion if it isn't fixed by then?

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

there is no suggestion to be made there before having a change solving the issue, stable updates often depend of the complexity of the change and how it has been tested and applies to the stable version, if the fix is easy enough to be updated to the stable version it will likely be updated there

Changed in nautilus:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue should be fixed in jaunty, closing the bug, you can reopen if you still get the bug after upgrade though

Changed in nautilus (Ubuntu):
status: Triaged → Fix Released
Changed in nautilus:
importance: Unknown → Critical
status: Invalid → Expired
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.