After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609902 - Opening "Computer" with nautilus fails 1st time after login when using Extra Pane view (A.K.A "split view mode")
Opening "Computer" with nautilus fails 1st time after login when using Extra ...
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-14 08:39 UTC by Mitch Towner
Modified: 2010-03-07 13:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mitch Towner 2010-02-14 08:39:18 UTC
This bug was originally reported on Ubuntu's Launchpad.

Opening the "Computer" shortcut in the Places menu or running "nautilus computer:///" from a terminal window fails the first time after login if using the "Extra Pane" (F3) view (A.K.A "split view mode").

This issue was reported by the OP on AMD64 Lucid Lynx alpha 2. It has been confirmed on up-to-date Lucid Lynx alpha 2 i386.

$ uname -a
Linux ubuntu 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:24:20 UTC 2010 i686 GNU/Linux

$ sudo apt-cache policy nautilus
nautilus:
  Installed: 1:2.29.90-0ubuntu1
  Candidate: 1:2.29.90-0ubuntu1
  Version table:
 *** 1:2.29.90-0ubuntu1 0
        500 http://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

[TEST CASE]
=============
1. Ensure "Extra Pane" (F3) view (A.K.A "split view mode") is selected in nautilus
2. Ensure you have not opened the location "Computer" since logging in
3. Open "Computer" from the Places menu OR run "nautilus computer:///" from a terminal window

[Current Result]
=============
An error message is displayed advising that the location is already mounted. Nautilus does not open. (See OP's "Screenshot.png" below)
Note that this only occurs the FIRST time nautilus tries to open this location. Upon dismissing this error message, nautilus operates as expected with the "Extra Pane" view (A.K.A "split view mode") enabled.

[Expected Result]
=============
Nautilus should open the location "Computer" without error with the "Extra Pane" view (A.K.A "split view mode") enabled.

[Work Around]
=============
1. Dismiss the error message & re-open the location "Computer" with nautilus. This error is only displayed the first time, all subsequent attempts to open this location will work without error.

OR

2. Disable the "Extra Pane" (F3) view (A.K.A "split view mode").

[Notes]
=============
This issue only occurs when using the "Extra Pane (F3) view (A.K.A "split view mode") in nautilus on Lucid.
This issue only occurs the first time the location "Computer" is opened in nautilus after login
This issue can be reproduced by selecting "Computer" from the Places menu OR by running "nautilus computer:///" from a terminal window

The full report can be found here: https://bugs.edge.launchpad.net/ubuntu/+bug/520685
Comment 1 Holger Berndt 2010-03-06 02:45:30 UTC
I cannot reproduce this. Also, new Nautilus windows now never show the extra pane when they are created, which might be related. Could you try to reproduce with a more recent version (past 95ae539e8)?
Comment 2 Arand 2010-03-06 18:51:00 UTC
95ae539e8d042b04ee9c6817bcc41f551ab207fc is already present in current Lucid and does not fix the issue

When pulling in c8ded383147e0f860f9a206e9f45606bf16effe9 the issue is gone, since obviously there is no way to open nautilus with the two-pane interface present.

However, I'm not sure if the original issue is strictly due to the two-pane interface or if it's some odd bug that is exposed by it. Since possibly if the "remember-two-pane" is re-implemented (I heard mentions of it requested as a pereference option at least), the issue might crop up again.

Anyway, with c8ded383147e0f860f9a206e9f45606bf16effe9 there is no way to reproduce the issue as of now.
Comment 3 Holger Berndt 2010-03-07 13:33:24 UTC
Okay, so appearantly, the issue was fixed by not opening with the extra pane enabled. I'm closing the bug now; if anybody finds a way to still reproduce it with the extra pane opened manually, feel free to re-open.