Anyone had any success in connecting to Wallpaper Engine on Linux, running through Proton?

[Dark Thoughts]

It doesn't seem to be able to find anything and I also tried to manually enter the network address of my desktop, but it doesn't seem to be able to connect / find anything.

[Biohazard]

We have not heard of anyone transferring wallpapers from Linux before, but if you got the UI to run through Proton then maybe it's possible.

What you could do is check the uilog.txt in the wallpaper_engine/bin directory, to check which network addresses have been found and are being broadcasted on. The logs for this will be written the moment you click "connect new device" in the app, so you could click that and check the log right after, that should make it easy to find.

Obviously we don't know how Proton handles this, but this at least allows you to verify what the application is seeing from Proton.

If it says that it started broadcasting on your local network adapter with the right address, you could then use Wireshark and see if the packets are really coming through to your network (I'm assuming you may be familiar with it already).

[Dark Thoughts]

Figured out at least something.
My VPN (Mullvad, using their client on both desktop & mobile) on the desktop prevents the broadcasting. If I disconnect, then I can see my desktop client from within the mobile client. My mobile client is still connected to the VPN in that case and both clients have local network sharing enabled. However, connecting the two is still not possible ("Failed to connect, please try again" after entering the code on mobile). Disabling the VPN on the phone does not make a difference in detecting or connecting.

The uilog starts like this and constantly spams the firewall status message afterwards.

2022-05-18T20:27:06Z, 908: GetLocalAdapterAddresses status: 1
2022-05-18T20:27:06Z, 908: Adapter 0, {00000001-0000-0000-0000-4E6574446576} / lo, status 1, IfType 24, ipv4 0, ipv6 0, NoMulticast 0
2022-05-18T20:27:06Z, 908: Adapter 1, {00000002-0000-0000-0000-4E6574446576} / enp3s0, status 1, IfType 6, ipv4 0, ipv6 0, NoMulticast 0
2022-05-18T20:27:06Z, 908: Starting mobile discovery on ***** for 0 adapters.
2022-05-18T20:27:06Z, 908: Broadcast socket status: 1 @ 0.0.0.0
2022-05-18T20:27:06Z, 908: Failed broadcasting directed packet at 0.0.0.0
2022-05-18T20:27:07Z, 496: Failed checking firewall status 0x80004001
2022-05-18T20:27:07Z, 908: Failed broadcasting directed packet at 0.0.0.0
2022-05-18T20:27:09Z, 908: Failed broadcasting directed packet at 0.0.0.0
2022-05-18T20:27:09Z, 496: Failed checking firewall status 0x80004001
2022-05-18T20:27:10Z, 908: Failed broadcasting directed packet at 0.0.0.0

I believe when I try to connect it spits out this one, but I'm not 100% sure:

2022-05-18T20:36:07Z, 908: Acceptor status: 0
2022-05-18T20:36:07Z, 1484: BCryptDecrypt failed UUID init with c0000002
2022-05-18T20:36:07Z, 1484: Authentication failed, restart with new keys.
2022-05-18T20:36:07Z, 496: Closing client connection in UI.

The UI & subscribing etc. works fine through Proton Experimental, except for performance and some visual oddities. It's enough for the KDE Plugin for now.

[Biohazard]

Unfortunately it looks like something is missing in Proton if I understand this correctly. BCryptDecrypt returns 0xc0000002 which seems to be STATUS_NOT_IMPLEMENTED.

Funnily enough this is not a valid return value for BCryptDecrypt: https://docs.microsoft.com/en-us/windows/win32/api/bcrypt/nf-bcrypt-bcryptdecrypt but semantically it obviously makes sense what is implied anyway.

We're using BCRYPT_RSA_ALGORITHM and BCRYPT_AES_ALGORITHM for the communication, but Proton doesn't seem to return any errors on BCryptOpenAlgorithmProvider which is called earlier. So the issue may be the combination of the BCRYPT_PAD_OAEP flag used in this call to BCryptDecrypt with the BCRYPT_RSA_ALGORITHM provider.

Looks like it's missing in wine specifically here: https://github.com/ValveSoftware/wine/blob/df982e6865c2041ae994ee20ed2a2075ae7ddfb7/dlls/bcrypt/bcrypt_main.c#L2008

[Dark Thoughts]

return STATUS_NOT_IMPLEMENTED

Yeah. Not great. :(
Probably low on peoples priority as well.

Would it be possible to just move the wallpaper folders from the workshop folder over onto the phone, to whatever the Android path would be?

[Tim]

You can attempt the backup solution as explained in the bottom section of this page:

https://help.wallpaperengine.io/en/mobile/pairing-fixes.html#backup-solution-manually-importing-a-wallpaper-file-mpkg