Arch Linux User Repository

I'm not really using this package anymore, as I migrated to use https://gitlab.com/aar642/shadow-repackaged directly, but I don't want to change the upstream AppImage to shadow-repackaged as this may disrupt other users of this repo. I will continue to update the PKGBUILD until someone else wants to take over.

Finally got my issue resolved. None of the packages that got pinned after I unsubscribed helped. (although they motivated me to resubscribed and try again) I reached out to shadow support and said that they officially support Ubuntu but I couldn't get that working in a VM. (which was true) The person who responded directed me to a repo that helped a lot. https://gitlab.com/aar642/shadow-repackaged

In my case my issue was you can't run plex and shadow at the same time and once I stopped the plex service it worked like a charm. (Note: the Stable version over there didn't work for me but the Beta and Alpha work fine as well the package in this repo. @tionis I highly recommend pinning the link to that gitlab as it has a bunch of possible issues listed with workarounds for a lot of the popular branches. (Arch among others)

Some notes:

Some dependencies may be required and were reported by other users. They are not in PKGBUILD because I personally haven't had any issue running Shadow without these packages. I need more users' reports to confirm they are really required before putting them into PKGBUILD. So please try the following dependencies if you encounter errors, and please report here if these dependencies do resolve your errors.

1. libldap24 from AUR
2. net-tools
3. xdg-utils
4. flatpak

@peshane, it works! After installing "libldap24" from AUR, shadow runs without any problems. Thank you very much!

@whyrhd, I was also stuck with this error, first I try to install net-tools package because strace shown sh exit 127 on "netstat" call. But that was not enough, in the end, the solution looks like to install "libldap24" from AUR.

Hi everyone, I was running shadow on my Arch for quite some time with the original AppImage provided by shadow. Recently, whenever I start the AppImage and press "Start", after some time I get the error code R-0x7F - Unknown Error. I feel like there are some dependencies missing but I cannot figure out which. Anyone having some advice? Thanks!

PS.: Some further information: I'm running Gnome and X11 (not Wayland). Besides the prepacked AppImage, I've now installed this shadow-tech package from AUR and get the same error. As mentioned before, shadow worked fine for some time but at some point it just stopped working. Presumably because of some update although I don't know if the problem is caused by a new shadow version or some other system update. I'm using a GeForce GT1030 and I'm using Arnouds patch (https://gitlab.com/aar642/libva-vdpau-driver). I would be really happy for any advice! Thanks!

Hello everyones,

I do have a minimalist arch install on Wayland with swaywm. Shadow app run fine (using the appImage directly or this aur package). The only thing is when I click on "Log In With Browser", nothing happens. I tried to look of any environment missing variable and created BROWSER=/usr/bin/firefox with no changes. Any ideas?

Thanks anyway

EDIT: Answering myself, looks like xdg-utils package installation corrected the problem. I was able to login after.

@pychuang I use the traditional X11 backend due to issues with my Nvidia card and Wayland. And you’re right Xfce4 works fine out of the box without Flatpak. (Can’t have anything to do with the Nvidia driver as those where not installed in my vms when testing)

I found out that flatpak fixes it for kde by testing with Manjaro in a vm. Manjaro KDE worked fine; Manjaro kde minimal had the issue. So I compared packages and tracked it down to flatpak. (I reallly didn’t want to install Manjaro on my pc just to be able to use shadow)

I did a quick clean arch install in a vm too (SDDM plasma kde-applications) so I don’t have those Manjaro repos. Same Login error as with my main machine. I installed kfce4 in the same vm and the login works. Once logged in shadow also works in kde. Even with kfce4 installed tho login isn’t possible in kde.

Hope that helps for you to reproduce it :) And thanks for maintaining that package :)

@kskudlik Thanks for looking into the issue. I think I wasn't able to reproduce the error probably because I use i3-WM when using shadow. Just to get more information, is your KDE using Wayland backend or the traditional X11 backend? And using Xfce4 did not give you any errors, right? I'll try to reproduce the error and dig into it.

In the meantime, I'll pin your solution at the top so that other users can follow it for now. Thanks!

@pychuang TLDR: seems like flatpak + reboot is needed for base kde/plasma to login (YMMV)

It has been a hell of a ride to get shadow working on my arch install, but i (kinda) figured out why. I had a similar issue as @LinuxLoverForeve and could not login. After some testing I figured out that the problem didn´t exist in xfce4 but it didn´t work even on the same machine when using plasma.

yadi yadi yada hours, tears, frustration and over 9000 VMs later i found out that a simple install of flatpak with a reboot afterwards made it work without any issues so far.

So maybe include flatpak to the dependencies?
PS: i don´t know why i had to reboot after installing flatpak and a this point i am afraid to ask :) so if you know let me know^^

Edit: It's probably (maybe) just a dependency of flatpak and not flatpak itself that does the trick, but i can't be bothered to figure out which one atm

@pychuang

I haven't tried deleting the config dirs you mentioned but I did try the direct download and run method you mentioned. No luck I got the localhost error in chrome. This was the output in the terminal /bin/sh: line 1: hostname: command not found Checking for update Update for version 5.0.1020 is not available (latest version: 5.0.1020, downgrade is disallowed).

Update: Due to this issue I decided to cancel my subscription since it was going to renew in two days. Plus I've been waiting for additional storage to not be sold out. @pychuang

If you are able to reproduce my issue and find a solution please post it here.

@LinuxLoverForeve You can also try using the official AppImage directly without installing it to Arch Linux. In terminal:

curl -LO https://storage.googleapis.com/shadow-update/launcher/prod/linux/ubuntu_18.04/Shadow.AppImage

then

chmod +x Shadow.AppImage

finally

./Shadow.AppImage

If using the AppImage directly without installation works, please let me know.

@LinuxLoverForeve I couldn't reproduce the error. I could log in as usual. Not sure if this matters, but I use Firefox when logging in through the browser. I didn't have oidc-agent.

Though I don't think this is relevant, one thing you can try is to delete old Shadow configurations. Try deleting ~/.cache/blade, ~/.cache/shadow. and ~/.config/shadow. And if you used to have auto-login in the previous version (through either keepassxc, gnome-keyring, pass-secrets, or kwallet), also try deleting the data from blade or shadow if you see them.

Do you have a firewall? Is it possible the firewall blocks the redirection to localhost?