mickoMar 20
@jloc0 noctalia on labwc (at least) has pooped it's pants since the last update. I've filed an issue (https://github.com/noctalia-dev/noctalia-shell/issues/2232) as I do believe it's their problem. Dank still runs fine with qs-noctalia, but the inverse is not so. #noctalia
Show threadmickoMar 20
@jloc0 Yeah, fragmentation reared it's fugly head. Fixed but not really FIXED.
Show threadmicko
@jloc0 so I popped the frag question to lemmy and lysec .. https://github.com/noctalia-dev/noctalia-shell/issues/2232#issuecomment-4097758111
noctalia not starting on labwc/slackware · Issue #2232 · noctalia-dev/noctalia-shell

Description The slackware64-current noctalia package has been updated (3rd party package) and with that upgrade noctalia will not start on labwc-0.9.6. (see https://slackware.lngn.net/#noctalia). I...

GitHub
Mar 20 at 1:12pmWeb
Show threadjloc0Mar 20

@01micko it seems you somehow got the main quickshell package over noctalia-qs somehow. But this is the problem I expected. They didn’t change any install locations or file names or anything. Which creates issues for package managers along the way.

My solution locally is to remove both quickshell and noctalia-qs, blacklist the one I don’t want and reinstall the other so slackpkg+ don’t reinstall it.

Show threadmickoMar 20
@jloc0 my solution is just ditch #noctalia. I use #quickshell for other stuff so I need a stable version that covers all bases. Thanks for backing me up in that issue, but I don't think they care.
Show threadjloc0Mar 20
@01micko yeah it doesn’t really seem like they have any real idea how to really fork a project like that. Its sad as its a promising shell, but now its boxed into its own incompatible world.