GNOME Bugzilla – Bug 756499
Double click on folded open folder in another nautilus window
Last modified: 2015-12-17 10:14:41 UTC
$ rpm -q nautilus nautilus-3.18.0-1.fc23.x86_64 Double click on folded open folder in another nautilus window
Screencast: https://drive.google.com/file/d/0B0nwzlfiB4aQY2hQaUI0U3NZNTg/view?usp=sharing (Please use google-chrome for HD quality)
(In reply to Mikhail from comment #1) > Screencast: > https://drive.google.com/file/d/0B0nwzlfiB4aQY2hQaUI0U3NZNTg/ > view?usp=sharing (Please use google-chrome for HD quality) it's not available, use webm or so and attach it somewhere that allows for all browsers please. Can you provide more info? does it happens always? do you use icons on the desktop? Thanks!
Probably related to this? https://bugzilla.gnome.org/show_bug.cgi?id=756370
*** This bug has been marked as a duplicate of bug 756370 ***
*** Bug 756655 has been marked as a duplicate of this bug. ***
Full screencast with reproduction: https://mega.nz/#!T5sGyTaB!TcZ0v1sHjvKfATBEB3qqBVqP33WvIRP86_G1T9l1AEo But I must be noted immediately that are not always it reproduceable.
Hi, I would like to confirm this bug on Arch Linux, Nautilus 3.18.1 I don't know why it is a duplicate of bug 756370, the symptoms are different. This is to do with existing Nautilus windows suddenly taking control of each other. Please see https://plus.google.com/+MichaelHeyns/posts/WTTTnpJMyqp I have been trying to reproduce this methodically but with no luck. It can happen when changing focus between Nautilus windows or navigating a tree within the same window. This is making it considerably difficult to use the file browser. Also see this screencast: https://vid.me/F8N5
> I don't know why it is a duplicate of bug 756370, the symptoms are > different. This is to do with existing Nautilus windows suddenly taking > control of each other. > The status of the bug report is "REOPENED", that means is no longer a duplicate. I just misunderstood the other bug report, and indeed this is not a duplicate of that one. Talking about the this bug, it has to do with the focus managing, but I couldn't reproduce on my own, code looks "good", and until now nobody got a reproducer (that makes me think there is a race somewhere)
*** Bug 756957 has been marked as a duplicate of this bug. ***
I also have this issue.(In reply to Michael Heyns from comment #7) > Hi, I would like to confirm this bug on Arch Linux, Nautilus 3.18.1 > > I don't know why it is a duplicate of bug 756370, the symptoms are > different. This is to do with existing Nautilus windows suddenly taking > control of each other. > > Please see https://plus.google.com/+MichaelHeyns/posts/WTTTnpJMyqp > > I have been trying to reproduce this methodically but with no luck. It can > happen when changing focus between Nautilus windows or navigating a tree > within the same window. > > This is making it considerably difficult to use the file browser. > > Also see this screencast: https://vid.me/F8N5 I'm having the same issue (as in the screencast), it also happen in earlier version of Nautilus.
(In reply to francoism from comment #10) > I also have this issue.(In reply to Michael Heyns from comment #7) > > Hi, I would like to confirm this bug on Arch Linux, Nautilus 3.18.1 > > > > I don't know why it is a duplicate of bug 756370, the symptoms are > > different. This is to do with existing Nautilus windows suddenly taking > > control of each other. > > > > Please see https://plus.google.com/+MichaelHeyns/posts/WTTTnpJMyqp > > > > I have been trying to reproduce this methodically but with no luck. It can > > happen when changing focus between Nautilus windows or navigating a tree > > within the same window. > > > > This is making it considerably difficult to use the file browser. > > > > Also see this screencast: https://vid.me/F8N5 > > I'm having the same issue (as in the screencast), it also happen in earlier > version of Nautilus. which early version?
3.14 and 3.16, but don't know if earlier versions have the same issue.
(In reply to francoism from comment #12) > 3.14 and 3.16, but don't know if earlier versions have the same issue. That's....surprising. I though this was a regression on 3.18, so seems it was an issue that was present before just that now the code trigers this more often.
(In reply to Carlos Soriano from comment #13) > (In reply to francoism from comment #12) > > 3.14 and 3.16, but don't know if earlier versions have the same issue. > > That's....surprising. I though this was a regression on 3.18, so seems it > was an issue that was present before just that now the code trigers this > more often. Correct, but for me it makes no differences on GTK 3.16/GTK 3.18 (as in trigger-time). Could it be an issue with recent files and/or cache? Are switches available?
This seems to be getting worse. It happens consistently within a few minutes of having two or more windows open.
This issue started for me with 3.18, never happened before the upgrade. Happens often enough that I have no switched to Thunar.
Created attachment 315370 [details] [review] window: explicitily set active window We were relying on getting the current active window from gtk to switch open locations, but what people found is that some times another window change its location instead of the current one. I couldn't figure out the root of the problem, so I'm going to pass explicitly the window on the callers as previous 3.18 we were doing. Would be cool to find the root of the problem though...
Attachment 315370 [details] pushed as cff7857 - window: explicitily set active window
I'm using Arch with nautilus 3.18.2-1 but the bug seems to be still there... Plus, here https://git.gnome.org/browse/nautilus/tree/NEWS?h=gnome-3-18&id=b12df7d7f2c9dab81ee8bd1eb569cae14c8c5e63 it says 3.18.1 twice, is it correct? Sorry but I am a noob here! Thank you!
(In reply to andrea from comment #19) > I'm using Arch with nautilus 3.18.2-1 but the bug seems to be still there... really? This starts to get completely strange... in which case does it happens to you? does it still happens when using the sidebar? > Plus, here > https://git.gnome.org/browse/nautilus/tree/NEWS?h=gnome-3- > 18&id=b12df7d7f2c9dab81ee8bd1eb569cae14c8c5e63 it says 3.18.1 twice, is it > correct? Sorry but I am a noob here! whops, no it's not correct. > Thank you!
Usually I use Nautilus by opening a folder on the desktop (I have activated desktop icons with tweak tool). I can reproduce the bug this way: 1) Double click on Home folder on desktop opens nautilus in window 1 2) Double click again on Home folder on desktop opens nautilus in a new window 2 3) Double click again on Home folder on desktop opens nautilus in a new window 3 4) Close window 2 with the [X] button of the window 5) Now for example if I double click on Trash icon on desktop, Trash is opened in window 3 and not in a new window
(In reply to Carlos Soriano from comment #20) > (In reply to andrea from comment #19) > > I'm using Arch with nautilus 3.18.2-1 but the bug seems to be still there... > > really? This starts to get completely strange... in which case does it > happens to you? does it still happens when using the sidebar? > > > Plus, here > > https://git.gnome.org/browse/nautilus/tree/NEWS?h=gnome-3- > > 18&id=b12df7d7f2c9dab81ee8bd1eb569cae14c8c5e63 it says 3.18.1 twice, is it > > correct? Sorry but I am a noob here! > > whops, no it's not correct. > > > Thank you! I can confirm that the bug still happens, also an Arch Linux user here. Although the comment from @andrea should work to trigger the bug, it happens for me at random. But for some reason the bug get's more triggered on GTK 3.16>. What also surprised me is that Nautilus isn't using an own process for each window. Although it helps reducing resources, it helps with issues like this (and also if crashing). Please correct me if I'm mistaken. :)
-> 3.18 for tracking it
-> reopened, this is not fixed
Cannot reproduce with Andrea's steps :( There's must be something different between us... I still never achieved to reproduce it. Are you using some plugin? All of you use the desktop option? Francoism, you said it happened to you as well in 3.16? Also, no, a thread for each window won't help with this issue, and no, it's not a good idea and it's basically impossible since you have to communicate with the UI which happens in a single thread. Also, Nautilus uses too much threads, we actually need a better threadpool. Anyway, two more patches attempting to fix it comming.
Created attachment 317205 [details] [review] nautilus-application: unset slot if new window created If the new window flag is set, make sure that, whatever the caller pass as target slot, we don't use it.
Created attachment 317206 [details] [review] mime-actions: use explicit slot for opening locations Even if we wanted to always use the active window as the default action to open locations, seems gtk_get_active_windows doesn't work as expected for us. Until we figure out the problem, pass explicitly the target slot that the caller provides so users don't experience the location opening in a different window than the expected.
Reopen if it doesn't work. It will be available in 3.18.3 Attachment 317205 [details] pushed as 755c771 - nautilus-application: unset slot if new window created Attachment 317206 [details] pushed as 81c58a9 - mime-actions: use explicit slot for opening locations
@Calros Soriano: As far as I remember I have activated desktop icons and installed nautilus-dropbox (icons change during sync), seahorse-nautilus (adds "Encrypt..." when right click on file), nautilus-sendto (adds "Send to..." when right click on file). I also have installed few gnome shell extensions but I don't think they could be related to the issue. If I have time during next days I will try to install arch+gnome in a virtual machine from scratch, without any extensions, in order to see if the bug appears in that case. If not I will try to add extensions until the bug appear. @francoism do you have any extension that I have installed?
Hi! I have installed nautilus 3.18.3. Today I have used my notebook only for few minutes and I have not been able to reproduce the bug anymore with my previous steps (with the 3 windows stuff). However I have only used it for few minutes so I can't tell you for sure that the bug is effectively solved, it's better if someone else can confirm with a more intense usage of nautilus.
thanks Andrea