That is a really old thread. If you look at that sway link you should be able to follow those steps to fix it.
Migrating pre-2022.08.21 sway session
This is possible, but quite difficult, and not really supported. Will be easier with a little help from the pacseek [AUR] package.
You need to uninstall the archlabs-nwg-shell package, and then replace all the AUR stuff previously packaged for the ArchLabs repository (they are "local" now) with AUR counterparts:
archlabs-autotiling -> autotiling
archlabs-azote -> azote
archlabs-gopsuinfo -> gopsuinfo
archlabs-nwg-bar -> nwg-bar-bin
archlabs-nwg-dock -> nwg-dock-bin
archlabs-nwg-drawer -> nwg-drawer-bin
archlabs-nwg-menu -> nwg-menu-bin
archlabs-nwg-look -> nwg-look-bin
archlabs-nwg-panel -> nwg-panel
archlabs-nwg-shell-config -> nwg-shell-config
archlabs-nwg-wrapper -> nwg-wrapper
archlabs-nwg-displays -> nwg-displays
archlabs-swaync -> swaync
archlabs-nwg-shell -> nwg-shell
In some cases you may need to uninstall the archlabs- package first. For sure it affects the archlabs-gtklock package.
I would just wait a bit for a dev to come along and see what to do. Since i3 was kept as a session those packages really shouldn’t have broken.
If open box is showing similar issues it is relevant. As this really should have been considered when the packages were removed from the archlabs repo as with i3. At the very least a forum post warning people they need to fix it. So yes both issues (i3 and openbox or any other window manager that was kept are /could be affected). DK does not have the issue more then likely because that is @natemaia 's baby.
If you like to experiment just remove archlabs-autotiling and install the AUR version.
One last thing:
This one is especially troubling because of the way they had things set up previously with xfce laying under the window mangers, and switched to lxappearance.
I’m a bit late to the party but would like to clear a few things up.
Yes, you can get the nwg-* versions from the AUR. I removed the archlabs-* versions at request or I would have left them in the repo longer to ease the transition period (as with other packages we’ve had in the past).
I don’t have any favoritism towards one session or another and was reluctant to even add dk as an option. It just so happens dk requires very few packages to function and I don’t want to complicate it, users can do what they like afterwards.
The skel packages are not required at all after install and xfce4-skel would only be installed if you did select xfce as a session so you wouldn’t lose any configs or packages regardless.
All sessions in the installer have the required packages in our repo and we never installed autotiling for i3 or any session other than sway, so this would be a user installing it themselves.
Arch also removes packages from their repos and the users are left to figure it out and find the package elsewhere if they want to continue using it (think mksh, sakura, qpdfview, etc…).
Update warnings about packages not existing can be safely ignored and treated as a local install. Think of using pacman -U with a package you create yourself, these warnings would also be present there.
The window managers and desktop environments conflicted and were another reason to drop the DEs. For example dunst which all the window managers use conflicts with xfce4-notifyd. We didn’t offer any custom configurations for any other DEs other than xfce4 and it was the main one that conflicted with the WMs. I was maintaining the xfce4-session and honestly felt it was better to drop it and allow a user to use the defaults of it. Another conflict was using xfsettingsd for theming but then the window managers and xfce fought over keybindings. Just some rationale for everyone to think about.
Basically drop the DEs so everyone could have a cleaner experience on either or.
The sway stuff was at @nwg ’s request so he could maintain the frequency of his work better through AUR.
Hi, so I also saw this message when doing system upgrade through pacman and yay. I have one question though, removal of all the said archlabs-* packages resulted in a lot of other dependant packages as “orphaned” and I often just clean up all orphaned packages periodically. I’m afraid some of these (now marked as orphaned) packages are quite crucial for my system like conky, rofi, tint2 and jgmenu and I think this will break my setup badly if I were to remove it in my periodic cleanup. Is there any solution to fix this on my end? I did not find a solution to unmark a package as orphaned on arch wiki or internet. would be immensely appreciate your help if someone can guide me! Thank you for reading.