Indeed, this need better UI (although that custom theme you are using makes it worse imho).

Carlos, just to be clear: this is not a custom theme but the default theme that Solus Budgie comes with. Thus this is not the experience of a "hacker" using his own modified theme but a new user installing a distro that comes with Nautilus to see this default experience.

(In reply to Robert Orzanna from comment #2)
> Carlos, just to be clear: this is not a custom theme but the default theme
> that Solus Budgie comes with. Thus this is not the experience of a "hacker"
> using his own modified theme but a new user installing a distro that comes
> with Nautilus to see this default experience.

I understand.

However we don't support neither recommend any other theme than Adwaita which is the theme we do, test and design against, and that one is not Adwaita :)

I understand Solus use a different one, but that's something you would need to discuss with them. Note that this doesn't change the fact that that dialog needs work on our side, just that a different theme than Adwaita makes it worse imho.

I agree, Carlos.

Let's improve your side first and then I am taking back whatever else is missing or needed to Solus.

One thing is the appearance of the dialog, another thing is a question, why it is empty. GVfs udisks2 volume monitor should return a list of pids from "lsof" command to the client if umount failed with UDISKS_ERROR_DEVICE_BUSY. The client side should resolve application names and list them in the dialog. Is the dialog always empty for you? Can you please try to run "lsof -t [mountpoint]" manually in such case to see if it contains something, or not? We have to find in what cases may be empty and show some reasonable error messages instead of the empty list...

"lsof" is not preinstalled by default on Solus. Can this dialog work at all without lsof? If not, Solus needs to add lsof as a dependency for Nautilus, I guess.

> orschiro@x230 ~ $ lsof
> bash: lsof: command not found

Ah, that's the issue, the output will be always empty and you should see "Error launching lsof(1)" in logs. GVfs (not Nautilus) needs lsof dependency to see blocking processes... and then you should not see the empty dialog in majority cases.

Let me report this to Solus and try to get their response!

For further reference: https://dev.solus-project.com/T4076

Thanks Carlos and Ondrej on the quick response. Resolving downstream right now.

Resolved downstream. Added rundep to gvfs.

(In reply to Joshua Strobl from comment #11)
> Resolved downstream. Added rundep to gvfs.

Thanks!