microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.26k stars 309 forks source link

Nautilus always produces the same error message #805

Open Aaron-Junker opened 2 years ago

Aaron-Junker commented 2 years ago

Environment

Windows build number: 10.0.25174.0
Your Distribution version: Unbuntu 20.04
WSL version: 0.64.0.0
Kernel version: 5.10.102.1
WSLg version: 1.0.40
MSRDC version: 1.2.3213
Direct3D version: 1.601.0
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.25174.101

Steps to reproduce

  1. Open Nautilus
  2. Do one of the following things
    • Right click on a folder/file
    • Exit right click menu
    • Navigate to another folder
    • Show/Hide Sidebar
    • Star a location

Nautilus logs:

Nautilus Logs ``` On start: ** (org.gnome.Nautilus:307): WARNING **: 09:38:58.367: Error on getting connection: Failed to load SPARQL backend: Could not connect: Connection refused (org.gnome.Nautilus:307): libunity-CRITICAL **: 09:38:58.431: unity-launcher.vala:157: Unable to connect to session bus: Could not connect: Connection refused Everytime I do something of the things mentioned above: (org.gnome.Nautilus:307): dconf-WARNING **: 09:39:09.018: failed to commit changes to dconf: Could not connect: Connection refused (org.gnome.Nautilus:307): GLib-GIO-CRITICAL **: 09:39:14.221: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ```

WSL logs:

wslg logs.zip

Expected behavior

It works and shows preferences.

Actual behavior

It can't save preferences and it always shows error messages.

logan9t8 commented 2 years ago

Try dbus-launch nautilus

If that works, make it permanent by putting export $(dbus-launch) in ~/.profile or ~/.zprofile and restart wsl using wsl --shutdown in PS/cmd.

Now simply nautilus or launching from Windows' start menu should work.

daviSR99 commented 10 months ago

Had the same issue and your comment saved me, dude. Thank you very much!!!