Bug 635494 - Double click on the removable media icon don't open nautilus first time
Double click on the removable media icon don't open nautilus first time
Status: NEW
Product: nautilus
Classification: Core
Component: Desktop
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-11-22 07:28 UTC by Artiom MOLCHANOV
Modified: 2016-06-19 16:02 UTC (History)
3 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Artiom MOLCHANOV 2010-11-22 07:28:03 UTC
1. After login plug in a USB key.
2. Icon created on the desktop
3. Double click this icon => nothing
4. Double click this icon => nautilus window opened.
Any successive plug out/plug in acts like expected (nautilus window opened with the first double click). To reproduce the problem I need to logout than login again.
Comment 1 André Klapper 2010-11-27 14:23:36 UTC
Which exact distribution is this about?
Comment 2 Artiom MOLCHANOV 2010-11-28 16:05:58 UTC
Archlinux
Comment 3 Sébastien Wilmet 2015-02-24 09:22:22 UTC
I sometimes still have this bug with GNOME Classic. It can happen with the Home folder too, or I guess any icon on the desktop that should open a Nautilus window.

I have this bug with CentOS 7.0 (GNOME 3.8) and Fedora 21 (GNOME 3.14).
Comment 4 Carlos Soriano 2015-02-24 09:56:39 UTC
Can you reproduce on master?
Comment 5 Sébastien Wilmet 2015-02-24 18:38:45 UTC
I don't plan to install a jhbuild gnome session. Nautilus 3.14 is the latest stable version, it's enough for a bug report, no?

Have you tried to reproduce the bug? The bug is a bit hard to reproduce, but this month I had it maybe 5 times, on different computers. Maybe a reboot is needed to reproduce it, I've tested a logout/login but the bug doesn't reappear, or it's maybe not exactly the same conditions.
Comment 6 Sébastien Wilmet 2016-06-19 16:02:37 UTC
(In reply to Carlos Soriano from comment #4)
> Can you reproduce on master?

I can still reproduce with 3.20. It's a long-standing bug (since at least 3.8).

Note You need to log in before you can comment on or make changes to this bug.