I updated my two machines with Solus KDE, and Solus xfce, and so far so good. 
Solus Updates for Week 49, 2024
all good, had to make a minor change in my dunst config though
- Edited
Aw, fsck. When I restored from hibernation this morning, things didn't look so good. The panel that works as a dock has gone the other way from the condition it's been lately. Instead of squeezing everything into a tiny square, it now displays full-size, but showing only the two left icons.
Strangely enough, when I clicked on the location where my Terminology icon used to display (far right), Terminology is what started, so I was able to get things started there.
So, I clicked where Vivaldi should be, but just got the tired old error message about "No internet..." At that point, I did the screencap you see above, getting Spectacle from the menu instead of the dock. Also, the hibernation problem that I thought was solved by changing Vivaldi's setting to save a week of browsing data instead of the 3 months it defaulted to was back.
C'mon KDE. 222 packages updated, and this is what I get? Gonna try one more reboot, and see if it sorts itself out once more.
EDIT: I did a full shutdown instead of a reboot, as I wanted to make sure I didn't leave any debris anywhere. Here's the dock now, so I'm hopeful that things are once again working as they should. So far, so good.
Next, I'll populate the workspaces in the upper panel, and do a brief hibernation, to see if the Internet is still connected when the laptop wakes up. I suspect it will be fine.
WetGeek 222 packages updated
Most were rebuilt for Qt 6.8.1, not updated in the sense you are thinking.
Brace for rant.
ACPI (Advanced Configuration and Power Interface) is the standard that defines these power states. Every single piece of hardware in your computer needs to support these states properly.
In 2003, Linus Torvald said:
Modern PCs are horrible. ACPI is a complete design disaster in every way. But we're kind of stuck with it. If any Intel people are listening to this and you had anything to do with ACPI, shoot yourself now, before you reproduce.
Source: https://www.linuxjournal.com/article/7279
For context Intel helped develop this standard and he is not only talking about ACPI for sleep states.
I stopped using these states over a decade ago because they are not reliable. Some hardware will never support it properly and even if you have hardware that does have decent support for it, every driver/kernel update or hardware addition can break it. I have had the simple addition of a usb dongle break it.
This is not a Solus problem. It is not even a Linux problem. Microsoft has a hardware certification program and part of their testing makes sure these states work and its still a cluster fuck (Microsoft share the blame for why ACPI sucks). They can only certify that it works at that point in time with that hardware. If you update the system or add new hardware it can break it.
24th January 1999, Bill Gates
One thing I find myself wondering about is whether we shouldn't try and make "ACPI" extensions somehow Windows specific.
It seems unfortunate if we do all this work and get our partners to do the work and the result is that Linux works great having to do the work.Maybe there is no way to avoid this problem but it does bother me.
Maybe we could define the APIs so that they work well with NT and not the others even if they are open.
Or maybe we could patent something related to this.
Their efforts ensured it sucked for everyone instead.
The only thing about sleep states I can guarantee is on a long enough time line it will break. If you haven't encountered this sort of breakage before with these states you are extremely lucky. You are rolling a d100 every time you try use it and the DC is 80.
Harvey Brace for rant.
Thanks for that summary of the ACPI issue. I guess it's just something we need to put up with, if we want to use sleep states. The last time I fixed everything, it lasted for quite a while, so that's just a decision I need to make. The alternative for me is just to lock my screen at night and unlock in the morning, which is not so terrible. I just hate leaving the computer running for that many hours when I'm not using it.
My computers are all DELLs, so all Intel inside. I imagine things could be worse. Now it's time to forget all about this for now, and watch the Abu Dhabi grand prix - the last one of the F1 season. And the last one for Louis Hamilton to be driving a Mercedes.
To be clear there is a chance we are missing a patch, doing something wrong / a future update will resolve it. But as you may be able to infer from my rant, I've had a long history of issues with sleep states across OSes and highly doubt we can solve it. I just wished to express my own frustration with the underlying issues you have been experiencing.
Enjoy your F1 
- Edited
is this something new in plasma? middle clicking a file in dolphin to open it in the 2nd choice app? - for example images open in gwenview by default, and in gimp via middle click?
edit: which is a good thing i discovered because twice now today the system has crashed HARD when dragging a pic from dolphin into gimp. cant even switch tty, keyboard/mouse not responding to anything
Lucien_Lachance middle clicking a file in dolphin to open it in the 2nd choice app?
Can't say its new because I've never tried this before but just confirming the behaviour. Middle click .mkv file for me is mkvtoolnix gui and for .avi it is mediainfo
Harvey you can configure the order in system settings >default apps> file associations
in case you didnt know
Harvey can you also confirm crashes when dragging image from dolphin into gimp?
- Edited
Negative. I tried drag & dropping into gimp for png, jpg, webp, and gif (it worked fine).
Harvey okay
i guess it doesent happen all the time, first time i think i did it several times without issue first, 2nd time it happened right away
I can confirm that this problem has indeed been solved, thank you for stepping in.
It's not directly relate to this update, but my issue is fixed from the hint about Nvidia beta driver. I got 4060 recently and run into "known issue" with black screen after wake up. I tried different versions of this driver. The beta helped, it shows login screen, then just black screen with cursor after logged in (I use Xfce). Then I tried nvidia-developer-driver-current and it works 
. At least I could hold this until they release the fix. Thanks for the hint @EbonJaeger
minh so nvidia-developer-driver-current is not the "beta" driver, it's actually a driver specifically for game developers and other developers working with opengl/vulkan directly that exposes more debug information to help them develop effectively. You want nvidia-beta-driver-current to be on the beta driver specifically.
ReillyBrogan It's not fully working with nvidia-beta-driver-current, I know I'm on the edge when install developer version but no other choice to avoid this black screen.
minh The beta helped, it shows login screen, then just black screen with cursor after logged in (I use Xfce)
Harvey fascinating context for the sleep state governor (acpi). I wonder if Torvalds or Stallman ever envisioned a foss solution to this? It can't though, I suppose, because acpi is industry standard...
...Gates, man, what a quote, I've never seen a man so committed to his own bottom line (hence this is why he's a trillionaire)..cold..I can just hearing him saying after the patent part "Embrace, extend, extinguish."
minh hmmm that's probably because the developer driver is based on an older driver branch (the 550 driver) and not the newer 565 branch.
