busy mouse pointer

[Golddouble]

Describe the bug FSearch supports the possibility for double clicking on a folder and then thunar opens with the content of that folder. -> When I use this function I have a "busy mouse pointer" for about half a minute. When I remember correctly: This was not an issue with FSearch 0.1

To Reproduce Gif-Animaion:

Expected behavior The mouse pointer is busy for about half a second or less.

Desktop (please complete the following information):

• OS:MX-Linux 19.4 Xfce (Debian 10 based)
• How you installed FSearch MX package installer
• Version 0.2.2
• Output of localectl status: System has not been booted with systemd as init system (PID 1). Can't operate. Failed to create bus connection: Der Rechner ist nicht aktiv

[cboxdoerfer]

I can't reproduce this on my system (Fedora, GNOME), but I'll try MX Linux in a VM this weekend.

I'm not a hundred percent sure about how the system implements the busy cursor, but afaik it uses the StartupNotify entry in the applications desktop file. So maybe Thunar doesn't support those notifications (so never sends a startup finished notification) but the flag is set in desktop entry in your distro.

[Golddouble]

Since you said that this does not occur in your system, I have now done the following: Shut down the PC and restarted it. Now the problem no longer occurs.

Sorry for the confusion.

[Golddouble]

OK I had this issue again.

How to reproduce:

0. Boot the PC
1. open FSearch
2. type into the search field *
3. choose picture filter
4. double click on a folder in the folder Column to open the folder in thunar
5. Result: All is as expected. No busy mouse pointer
6. go back to the FSearch window
7. repeat 4) but with another folder in the folder Column to open in thunar
8. the mouse pointer is busy now. (Maybe you need to repeate step 4) more than one)

[cboxdoerfer]

Thx for the information, I'll try to reproduce it. Can you also show the output of the following command:

grep folder_open_cmd ~/.config/fsearch/fsearch.conf

[Golddouble]

No output with this command:

$ grep folder_open_cmd ~/.config/fsearch/fsearch.conf
Golddouble@mx:~
$ 

(?)

[cboxdoerfer]

No output with this command:

That's fine, this just means you didn't override the folder open command manually.

But I still can't reproduce the issue — I tried MX 21 with Xfce. I'll try MX 19 again tomorrow.

[Golddouble]

More Info: I have now uninstalled version Version 0.2.2 . After I have installed the old version 0.1-1 .

So I was able to test the same with the old version. And yes: I have not this issue with the old version.

After I have uninstalled version 0.1-1 and installed again version 0.2.2: Now I have again this issue.

[cboxdoerfer]

I've now tried to reproduce it with MX 19 (Xfce + Thunar), but no busy mouse pointer there either.

[Golddouble]

Thank you. Strange.

[cboxdoerfer]

Ah, now I can reproduce it. Do you by any chance have Thunar configured to open new instances as tabs? Because once I enable this feature, the busy mouse pointer shows up.

But this also seems to happen with other applications on my system which open the file manager. For example when I click on the "Open folder" button in the Firefox download menu, Thunar also shows the busy mouse pointer. So this seems like the issue is somewhere else. Maybe in Thunar, because it somehow doesn't notify the system that it successfully opened?

[cboxdoerfer]

The reason why this doesn't happen with 0.1 is because this version didn't use the startup notification system at all, when opening files or folders.

[cboxdoerfer]

Another application I can use to trigger this bug is mate-search-tool from the mate-utils package, by just opening one or two found folders.

[cboxdoerfer]

Had a quick look at Thunar's code and it's indeed a Thunar bug. Here the code returns early when Thunar opens a new tab instead of a window, without handling the startup id. Hence the system doesn't know that Thunar startup was successful and thinks it's still loading, i.e. showing the busy mouse cursor.

[Golddouble]

Yes, I use tabs as new instances in thunar.

... and it's indeed a Thunar bug.

I see.

The reason why this doesn't happen with 0.1 is because this version didn't use the startup notification system at all, when opening files or folders.

It's interesting.

Thank you for having a look at it. :-)

[cboxdoerfer]

No problem. One workaround you could use, until this bug gets fixed in Thunar, is to set StartupNotify in the thunar.desktop file to false.

You should also report it to the Thunar developers, so they become aware of the issue.