This is an issue with the upstream project that must be appropriately relayed to them and resolved
Wed, May 20
Thanks for the updates!
Tue, May 19
Sorry. I was 99% sure v2 was required by 245 when I wrote that. Had completely forgotten about EFI changes.
No, this has nothing to do with systemd 245. The reason we reverted from 245 was due to EFI changes for default boot loaders (see here, not anything related to cgroup heirarchy. That already exists and is something we set to legacy already via the kernel's cmdline. This has to do with the fact that multiple pieces of software do not support cgroups v2, as highlighted by T8609. None of the mentioned issues referenced in T8609 have been resolved and as such, we cannot drop our use of legacy cgroups v2 without imposing unnecessary and undesired breakage and requirements of configuration for users.
There is no workaround. Newer versions of Snap require the newer versions of systemd. Until we are able to update systemd to 245, it's a moot point.
Sorry to dig up closed tickets, but thought it was worth mentioning as I have also come up against this bug.
As per the discussion on github, it appears that this issue isn't caused by bad AppArmor profiles within the snaps, but rather a change in snapd itself, as is described in the following PR:
@JoshStrobl I can confirm that the latest patch in the unstable repository fixed the issue for me. Also I did not have budgie-desktop-branding-livecd installed on my system.
Mon, May 18
Okay, for whatever reason I have budgie-desktop-branding-livecd still installed on my laptop, just not on my desktop. I'm guessing my issue was just caused by testing a bunch of stuff during prior GNOME stack upgrades and not doing proper cleanup on that system. That had a lock-enabled set to false which rightfully preventing it from locking. After uninstalling it, the issue is resolved. I'd double check that you also don't have this installed (you shouldn't but you never know). Marking this as resolved since I can now properly lock while suspending and there are no crashes.
Okay so I did a sync with git, added a VT1 patch to GDM, and disabled all extensions. Still doesn't actually lock on suspend. I'm not getting anything related to segfaults anymore but it does make me question whether or not they're even calling to lock before suspending in the first place.
Seems it may be an issue upstream. Even though we don't use gTile at all, I'm able to reproduce it however not able to reproduce any "fix" by disabling specific extensions, or all extensions. I'm going to see about merging https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d3934bd6854aa0b655437d443e59396dfb0c0945, which isn't in any of the latest releases, to see if that resolves the issue.
Sun, May 17
This seems to be an issue with Electron 8: https://dev.getsol.us/D8774#141938
Thu, May 14
Not sure if "acpi=off" is the same as "acpi=noirq" but it also allows the system to boot, discovered that via MX Linux.
Just tested it and it is working fine now.
Okay after further testing, the PR referenced that the dev claims fixes it doesn't in fact do so. Additional details should be provided once telepathy-mission-control and new polari are synced into stable (or if the individual that tested this against Solus 4.1 P.S. it isn't Solus 4). Going to add the patch in regardless, but marking this as an upstream issue.
This was an upstream bug with telepathy-mission-control that broke it:
Thu, May 7
Well this is a surprise, while adding "noapic" or "nomodeset" to the Kernel line in Grub does not work and "apic=debug" does nothing, it turns out using "acpi=noirq" does allow the system to boot the current Solus 4.1 iso.
Tue, May 5
This should be filed with the GNOME developers: https://gitlab.gnome.org/GNOME/gnome-control-center
Apr 20 2020
We don't provide the AppArmor profiles used by Snaps. If there is something wrong with them, you'll need to take it up with folks packaging them.
Apr 15 2020
So i guess it's related to trying to connect to a roku box for me.
@moore-bryan I just tested this with GNOME Shell, which is what supports vino (Budgie doesn't reliably support the integrated screen sharing / VNC mechanisms) by running the binary directly on my laptop, which runs GNOME Shell, then VNCing into it from a different machine after setting a password.
Thanks, @JoshStrobl; that upstream bug suggests running the vino-server from cli works, but on my system it does not.
This is an upstream issue: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/937
Apr 4 2020
In the future, please report these errors on the Github issues for help-center-docs. Closing since @sethfl has reported it there.
Mar 29 2020
This link can help you for color keywords:
I have been able to switch back to Plata-Noir-Compact after editing the file you pointed out (~/.Texworks/configuration/syntax-patterns.txt) to use lighter colous. (Basically I replaced darkred with salmon, darkblue with dodgerblue and darkgreen with green).
Mar 25 2020
Mar 19 2020
This is an upstream issue in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/1113
Mar 18 2020
Not to mention our Nautilus is currently held back, so it may not be reflective of Nautilus in newer releases. This will be resolved hopefully within next few weeks.
Probably just Nautilus hogging the render thread. Nothing we can do about this without an upstream fix.
Mar 17 2020
Mar 15 2020
Mar 3 2020
I would suggest filing your issue with the nouveau developers, since they're the ones that support your card (seeing as NVIDIA no longer does).
Feb 29 2020
Feb 28 2020
File this with the Plata developers: https://gitlab.com/tista500/plata-theme
Feb 21 2020
Feb 14 2020
This got solved for me with the last update to kernel 5.5.3
Feb 13 2020
I thought this is the latest kernel. After sudo eopkg check, this turned up:
`Checking integrity of udisks Broken
Corrupted file: /usr/lib/tmpfiles.d/udisks2.conf`
I doubt this is related but to be sure, how would I fix this?
I ran a full update. The kernel according to hostnamectl | grep -i kernel is Linux 5.4.12-144.current.
@feuerstein That kernel is from early January. Update your system...
My wifi is also broken.
Device-2: Intel Wireless 8260 driver: iwlwifi
Feb 11 2020
The package in the repo is not a Flatpak though.
Not a Solus issue, been an issue since at least April 2019 for the flatpak: https://github.com/bleakgrey/tootle/issues/140
Feb 10 2020
Jan 29 2020
@Juankz Please use this task for your wifi related issues rather than creating another one. Thanks.