Nautilus gives Could not display "computer:///". error when unmounting a volume for the first time for that login

[Erik B. Andersen]

Binary package hint: nautilus

This bug seems similar to bug 520685 , which is marked as fixed, but has the difference of not needing the extra pane to be open to cause this bug. It does have 'only occurring the first time after you login' in common with the aforementioned bug.

To reproduce:
Login to a user. (I'm using the lucid daily image for 4-3-2010 here)
Open the home folder for the user in nautilus.
Use the sidebar to open a volume. (Doesn't seem to matter if it was previously mounted or not)
Unmount the volume.
Notice Error saying
" Could not display "computer:///".
  Error: Location is already mounted
  Please select another viewer and try again.
"
Notice that if you do this test again, without logging out and then back in the error will not happen a second time.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Sat Apr 3 20:58:43 2010
ExecutablePath: /usr/bin/nautilus
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus
XsessionErrors: (polkit-gnome-authentication-agent-1:2973): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Pedro Villavicencio (pedro)]

any chance to attach the ~/.xsession-error file to the report? Thanks.

[Erik B. Andersen (azendale)]

Here the file is right after I just reproduced the bug.

[Erik B. Andersen (azendale)]

I'm going to set this back to new status since I provided the file. (I'm not sure if that follows protocol or not. If not, just let me know).

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Erik B. Andersen (azendale)]

Ok. I sent it upstream. https://bugzilla.gnome.org/show_bug.cgi?id=615963

[Sebastien Bacher (seb128)]

Thank you for sending the bug GNOME

[Erik B. Andersen (azendale)]

Just checking in.. This still happens with the Maverick Daily image for 6-13-2010.

[Sebastien Bacher (seb128)]

the upstream bug has been closed which is somewhat weird since the code didn't really change

[Dan Andreșan (danyer)]

The bug still exists, exactly as described in Maverick fully updated.

@Sebastien, I saw that people are asked to report bugs directly to Gnome.

Although I understand the reason behind it, is it not better for Ubuntu to have one person responsible for a package and that person to do all the upstream reports?

I mean, the Gnome people might give more attention to a bug reported by "The Official Ubuntu Caretaker for Nautilus" than a bug reported by me, for example.

Thanks.

[Bruno Girin (brunogirin)]

@Dan, people are not asked to report bugs directly to Gnome but if the bug is actually in the upstream code, it needs to be forwarded to Gnome so that they can fix it.

The process works a bit like this:
* You report the bug here,
* A member of the Ubuntu BugSquad (like me) reproduces the bug and marks it as confirmed,
* An Ubuntu maintainer, like Sebastien, checks whether the bug is specific to Ubuntu packaging or is a generic Gnome issue and if generic to Gnome asks for someone to forward it to Gnome,
* Someone who has an account on the Gnome bug tracker (usually someone from BugSquad but it could be anybody) forwards it to Gnome and links back the Gnome bug to the Launchpad bug.

The reason for doing this is that we need to validate first whether the bug is Ubuntu specific or Gnome generic and only forward to Gnome when needed. So in short, you should always report the bug here first so that it can be evaluated. After that, it doesn't matter who the person is who forwards to Gnome as long they link back to the Launchpad bug so that the Gnome developers can be confident that the bug has been evaluated here first. That's what bug triaging is all about: working out who can fix it. And if you want to give a hand, you're welcome to join BugSquad :-)

[Sami Tapio (flexy)]

This affects me too. Running Lucid, update it when ever I get the notification of updates available.

[Erik B. Andersen (azendale)]

>the upstream bug has been closed which is somewhat weird since the code didn't really change
For a while, it seemed like the bug was gone, and so they closed the bug.
However, I still occasionally stumble across this bug.

[Bálint Magyar (balintm)]

This is still a problem for me on Natty.

[Id2ndR (id2ndr)]

As Bálint Magyar, this bug still is present in natty (finale).

[raymulder (raymulder)]

 have 11.04 installed from the release iso and this bug is still there.
It happens with me when I unmount a DVD disk.
The problem seems to be Nautilus which cannot find a new directory to open after you have unmounted the disk.
This does not happen to a USB device or maybe it is only the first time you remove a drive from the computer.
Will try some more permutations.

[Alex Solanos (hakermania)]

Same problem in Natty for me.
It occurs usually when I unmount a Disk or something.

[Sebastien Bacher (seb128)]

The issue is fixed in Oneiric