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

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?

@pychuang

Yes I used yay for everything. I deleted the folder in the yay directory and told yay to do a clean build now I get this error in waterfox instead of a blank white screen like before XML Parsing Error: no root element found Location: http://localhost:32600/openidconnect/callback?code=iQFJFY5aNSZo-tgNXPnDAm9wneD40XOVuLVnWGHA01K Line Number 1, Column 1: and trying again via chrome still gives me this error. No webpage was found for the web address: http://localhost:32600/openidconnect/callback?code=KKO3BshDVY9oxOWbh0FLUlnjmW4SkNrPX93HKKSqTXx

I did research on the Open connect id error that I get in chrome and found an aur package for that here https://aur.archlinux.org/packages/oidc-agent/ unfortunately aside from being outdated it fails to install. However I noticed that I can install directly from source because of the github it's referencing. Should I try to do that? I don't know if the maintainer of that repo wrote the pkgscript as a git repo but just didn't put that in the title. I left them a comment asking if they are.

@LinuxLoverForeve

1. Regarding the checksum issue, how did you build/install shadow-tech? Did you use yay? If so, try removing the cached source directory (usually ~/.cache/yay/shadow-tech) and see if you still get the checksum error.

2. As for the clean build and redirection error, I couldn't reproduce it. Did you use yay's clean build? Or did you build it in a clean chroot (as described here: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot)?

@pychuang I had an issue with the checksum matching so I did a clean build but now I'm having the issue that I had with one of the other repos on the aur. When I go to login the browser redirects to a localhost error. No webpage was found for the web address: http://localhost:32600/openidconnect/callback?code=GV8O0TscQXuUiwf3jAraW09NlPtF_2ge8D_lpC65Gfv HTTP ERROR 404

My default browser is waterfox g3 but I even tried with chrome which is what gave me the actual error.