Nautilus often doesn't start the first (or second, or third) time

[andrewdavidwong]

Qubes OS version (e.g., R3.1):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

fedora-24 (possibly others)

---

Expected behavior:

Nautilus starts the first time the shortcut is clicked in the app menu.

Actual behavior:

Often (~70% of the time) it only starts on the second, third, or fourth try.

[andrewdavidwong]

This also affects opening certain attachments in Thunderbird with the thunderbird-qubes extension. For example, if you double click on an attached .zip file, a new DispVM will start (and presumably the .zip file will be transferred to it), but no window from the new DispVM will open.

Usually it's Archive Manager, so maybe there's some dependency on Nautilus, or maybe this affects more than Nautilus.

[andrewdavidwong]

This also affects opening certain attachments in Thunderbird with the thunderbird-qubes extension. For example, if you double click on an attached .zip file, a new DispVM will start (and presumably the .zip file will be transferred to it), but no window from the new DispVM will open.

Usually it's Archive Manager, so maybe there's some dependency on Nautilus, or maybe this affects more than Nautilus.

[andrewdavidwong]

@marmarek: Any idea what might be causing this? Any logs I should look at?

[andrewdavidwong]

@marmarek: Any idea what might be causing this? Any logs I should look at?

[entr0py]

What does it say when you try to launch Nautilus from the terminal? Only Nautilus or other Gnome apps as well? I had a dbus-related issue in Whonix-12 that produced same symptoms, but for gnomish-apps across the board.

[entr0py]

What does it say when you try to launch Nautilus from the terminal? Only Nautilus or other Gnome apps as well? I had a dbus-related issue in Whonix-12 that produced same symptoms, but for gnomish-apps across the board.

[andrewdavidwong]

What does it say when you try to launch Nautilus from the terminal?

Good idea:

$ nautilus

(nautilus:17938): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.

(nautilus:17938): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist

Only Nautilus or other Gnome apps as well?

Seems to be only Nautilus and things that directly use Nautilus (e.g., Archive Manager).

[andrewdavidwong]

What does it say when you try to launch Nautilus from the terminal?

Good idea:

$ nautilus

(nautilus:17938): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.

(nautilus:17938): Gtk-WARNING **: Theme parsing error: <broken file>:1:0: Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' does not exist

Only Nautilus or other Gnome apps as well?

Seems to be only Nautilus and things that directly use Nautilus (e.g., Archive Manager).

[marmarek]

Does it start after issuing those warnings?

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[marmarek]

Does it start after issuing those warnings?

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[entr0py]

Sounded familiar. Related to these?

https://groups.google.com/d/msg/qubes-users/veefnCdXHhs/2A-5IqEQZFYJ
https://groups.google.com/d/msg/qubes-users/ki-m5el9yUQ/X99qrODEX4cJ
https://groups.google.com/d/msg/qubes-users/Vpw8VOPvUEU/_0a4ywPpBwAJ

I don't remember the solution though... dbus activatable = false? Or was that a bandaid?

[entr0py]

Sounded familiar. Related to these?

https://groups.google.com/d/msg/qubes-users/veefnCdXHhs/2A-5IqEQZFYJ
https://groups.google.com/d/msg/qubes-users/ki-m5el9yUQ/X99qrODEX4cJ
https://groups.google.com/d/msg/qubes-users/Vpw8VOPvUEU/_0a4ywPpBwAJ

I don't remember the solution though... dbus activatable = false? Or was that a bandaid?

[andrewdavidwong]

Does it start after issuing those warnings?

Yes, when started from the command-line, it starts after those warnings. (When started from the Application menu, though, it usually doesn't.)

[andrewdavidwong]

Does it start after issuing those warnings?

Yes, when started from the command-line, it starts after those warnings. (When started from the Application menu, though, it usually doesn't.)

[andrewdavidwong]

Some anecdotal evidence: I've noticed that clicking the menu link twice in quick succession usually works, whereas waiting a few seconds between clicks does not.

Why this is extremely annoying and kills productivity:

Since I don't know whether a single click will work (because of this bug), my choice -- every time I need to open Nautilus in a Fedora VM (which is a lot) -- is between taking my chances (in which case I may ultimately have to navigate to and click the menu link 2+ times in the event that the first time doesn't work) or navigating to and clicking the link twice in quick succession (i.e., before I have a chance to find out whether the first click worked, in which case I have to navigate to the menu link twice). Either way means a lot of extra navigation and clicking through a very long menu.

I already have five groups of Xfce launchers, including 18 distinct Nautilus entries. This remains extremely problematic even after that degree of mitigation. I sometimes give up, open a dom0 terminal, and do qvm-run <vm-name> nautilus from the command-line, which is cumbersome but at least reliable.

[andrewdavidwong]

Some anecdotal evidence: I've noticed that clicking the menu link twice in quick succession usually works, whereas waiting a few seconds between clicks does not.

Why this is extremely annoying and kills productivity:

Since I don't know whether a single click will work (because of this bug), my choice -- every time I need to open Nautilus in a Fedora VM (which is a lot) -- is between taking my chances (in which case I may ultimately have to navigate to and click the menu link 2+ times in the event that the first time doesn't work) or navigating to and clicking the link twice in quick succession (i.e., before I have a chance to find out whether the first click worked, in which case I have to navigate to the menu link twice). Either way means a lot of extra navigation and clicking through a very long menu.

I already have five groups of Xfce launchers, including 18 distinct Nautilus entries. This remains extremely problematic even after that degree of mitigation. I sometimes give up, open a dom0 terminal, and do qvm-run <vm-name> nautilus from the command-line, which is cumbersome but at least reliable.

[evadogstar]

Maybe additional shortcut for nautilus like for terminal will be useful?
#2706
I am also notices that qvm-run VM nautilus always start nautilus. It's application menu problem. Maybe lets add two utils to run terminal and to run nautilus by shortcuts?

[evadogstar]

Maybe additional shortcut for nautilus like for terminal will be useful?
#2706
I am also notices that qvm-run VM nautilus always start nautilus. It's application menu problem. Maybe lets add two utils to run terminal and to run nautilus by shortcuts?

[jpouellet]

It's application menu problem.

I'm inclined to believe the opposite.

Does it start after issuing those warnings?

Yes, when started from the command-line, it starts after those warnings. (When started from the Application menu, though, it usually doesn't.)

I have observed it still refusing to start after issuing the same warnings, also when started from the command line (both via qubes-desktop-run, and directly nautilus (with and without --gapplication-service)). Qubes seems not to be at fault. Looks more like a bug from something in the gnome/gtk/dbus/etc. world to me.

[jpouellet]

It's application menu problem.

I'm inclined to believe the opposite.

Does it start after issuing those warnings?

Yes, when started from the command-line, it starts after those warnings. (When started from the Application menu, though, it usually doesn't.)

I have observed it still refusing to start after issuing the same warnings, also when started from the command line (both via qubes-desktop-run, and directly nautilus (with and without --gapplication-service)). Qubes seems not to be at fault. Looks more like a bug from something in the gnome/gtk/dbus/etc. world to me.

[jpouellet]

Also, I've had cases where it happens repeatably 100% of the time (at least for the 50+ times in a row while I was investigating). Killing all nautilus processes would make it work (file manager window opens, no warnings) the first time afterwards, but would immediately go back to never working and always warning. Restarting the VM usually causes it to resume working each time.

[jpouellet]

Also, I've had cases where it happens repeatably 100% of the time (at least for the 50+ times in a row while I was investigating). Killing all nautilus processes would make it work (file manager window opens, no warnings) the first time afterwards, but would immediately go back to never working and always warning. Restarting the VM usually causes it to resume working each time.

[jpouellet]

@evadogstar wrote:

Maybe additional shortcut for nautilus like for terminal will be useful? #2706

Here: qvm-filemanager

It is curious that the above linked script (essentially qvm-run $vm 'exec nautilus --new-window --no-desktop </dev/null >/dev/null') has yet to fail to open Nautilus even when it reproducably fails consistently via the Qubes menu.

The thing which makes it work seems to be the inclusion of --new-window flag, also confirmed by trying to start nautilus from a terminal in the affected VM. I still haven't dug into source to determine root cause. In the mean time, --new-window appears to be a reliable workaround.

[jpouellet]

@evadogstar wrote:

Maybe additional shortcut for nautilus like for terminal will be useful? #2706

Here: qvm-filemanager

It is curious that the above linked script (essentially qvm-run $vm 'exec nautilus --new-window --no-desktop </dev/null >/dev/null') has yet to fail to open Nautilus even when it reproducably fails consistently via the Qubes menu.

The thing which makes it work seems to be the inclusion of --new-window flag, also confirmed by trying to start nautilus from a terminal in the affected VM. I still haven't dug into source to determine root cause. In the mean time, --new-window appears to be a reliable workaround.

[jpouellet]

Err sorry, the above is incorrect.

Desktop entry already passes this:

% grep Exec= /usr/share/applications/org.gnome.Nautilus.desktop 
Exec=nautilus --new-window %U
Exec=nautilus --new-window

Perhaps --no-desktop flag is differentiating factor? Idk. Needs more investigation.

[jpouellet]

Err sorry, the above is incorrect.

Desktop entry already passes this:

% grep Exec= /usr/share/applications/org.gnome.Nautilus.desktop 
Exec=nautilus --new-window %U
Exec=nautilus --new-window

Perhaps --no-desktop flag is differentiating factor? Idk. Needs more investigation.

[marmarek]

`/usr/share/applications/org.gnome.Nautilus.desktop` have `DBusActivatable=true` which affect how the application is started. Especially, `Exec=` key is ignored in a such case: https://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[marmarek]

`/usr/share/applications/org.gnome.Nautilus.desktop` have `DBusActivatable=true` which affect how the application is started. Especially, `Exec=` key is ignored in a such case: https://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html

…

-- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

[evadogstar]

@jpouellet Nice :) What shortcut you suggest for qvm-filemanager? Your Ctrl+Enter for qvm-terminal iis fine at 99% situations. 1% - the same shortcut used at pidgin for new line/send message and on some sites and other messengers.

[evadogstar]

@jpouellet Nice :) What shortcut you suggest for qvm-filemanager? Your Ctrl+Enter for qvm-terminal iis fine at 99% situations. 1% - the same shortcut used at pidgin for new line/send message and on some sites and other messengers.

[jpouellet]

@evadogstar Currently Qubes+N, where "Qubes" is my modifier key reserved for exclusive use by all keyboard shortcuts

[jpouellet]

@evadogstar Currently Qubes+N, where "Qubes" is my modifier key reserved for exclusive use by all keyboard shortcuts

[jpouellet]

FWIW I also use Qubes+Enter for new terminals. Ctrl+Enter conflicts with things like posting github comments ;)

In practice my "Qubes" modifier is the key to the left of my space bar, but people should feel free to use whatever they prefer. I intend to send patches for this unified Qubes modifier functionality when I get some more free time.

[jpouellet]

FWIW I also use Qubes+Enter for new terminals. Ctrl+Enter conflicts with things like posting github comments ;)

In practice my "Qubes" modifier is the key to the left of my space bar, but people should feel free to use whatever they prefer. I intend to send patches for this unified Qubes modifier functionality when I get some more free time.

[andrewdavidwong]

This problem has recently gotten worse for some reason. Now, clicking a Nautilus shortcut N times will never open it. I have to launch it from the command line (I do it from dom0), at which point N Nautilus windows will open in the VM.

[andrewdavidwong]

This problem has recently gotten worse for some reason. Now, clicking a Nautilus shortcut N times will never open it. I have to launch it from the command line (I do it from dom0), at which point N Nautilus windows will open in the VM.

[marmarek]

fedora-28 template? Qubes 3.2 or 4.0? Does opening other application (xterm?) also make N Nautilus windows open?

[marmarek]

fedora-28 template? Qubes 3.2 or 4.0? Does opening other application (xterm?) also make N Nautilus windows open?

[andrewdavidwong]

Fedora 28 on Qubes 3.2.

Does opening other application (xterm?) also make N Nautilus windows open?

No, just tried it. Launching xterm in the VM from the dom0 command line resulted in an xterm window but no Nautilus windows. I then launched Nautilus in the VM from the dom0 command line and only then got N Nautilus windows.

[andrewdavidwong]

Fedora 28 on Qubes 3.2.

Does opening other application (xterm?) also make N Nautilus windows open?

No, just tried it. Launching xterm in the VM from the dom0 command line resulted in an xterm window but no Nautilus windows. I then launched Nautilus in the VM from the dom0 command line and only then got N Nautilus windows.

[tasket]

To a lesser degree I'm experiencing this on R4.0, debian-9.

I've started to look at using the KDE apps instead, since they do not exhibit the same startup problems and have better feature sets anyway. On R4.0 however, the Dolphin menu integration exists only in Whonix -- EDIT -- Nevermind, it works in debian-9!

[tasket]

To a lesser degree I'm experiencing this on R4.0, debian-9.

I've started to look at using the KDE apps instead, since they do not exhibit the same startup problems and have better feature sets anyway. On R4.0 however, the Dolphin menu integration exists only in Whonix -- EDIT -- Nevermind, it works in debian-9!