nice keet it up, i use XFCE edition run smoothly thank you

WetGeek I am not sure I follow what the problems are. It seems you said it is mostly browser related (So Vivaldi?) and a "Shutdown and Restart" solves it (?). So the problem does not occur anymore ? Or it keeps occuring after a Reboot?

If you wan to rolback and update, first check eopkg history to see which point (check the number order) do you want to rollback to. Then run sudo eopkg hs -t ***. "*" being the order number.

      alfisya Or it keeps occuring after a Reboot?

      Thanks for your help. Yes, various assorted problems continue after a reboot. Only a complete shutdown and restart allowed me to restart Vivaldi and continue working with it, after which all worked as it should.

      But after the next wake-up from hibernation, the problem repeated. Again, reboot did nothing to help, but after a complete shutdown and restart, everything worked as expected.

      Although I've never had a need to regress to a previous build, I remembered the first part of the process from reading other posts on the subject. But I'd forgotten what to do after that. That is, the history -t part. I've successfully regressed now, and loaded my virtual desktops with their usual contents. I'll try a hibernate/wake-up now to make sure, but I had no such probems before the update, so I'm confident that it will work.

      Maybe whatever is wrong will be corrected in the next sync.

          WetGeek

          Yes, hibernating and then waking up works perfectly, and everything is exactly where it was originally. So it's definitely something to do with the update - first time this has happened to me. Thanks again, @alfisya.

            WetGeek the problem repeated.

            What problem? I don't think you said in your posts what's actually going on, which makes it impossible to have any ideas.

                EbonJaeger What problem?

                I mentioned several times that the problem first manifested when I tried to wake up my laptop from hibernation. And it mostly affected my browser, Vivaldi. Instead of displaying what was active on the screen before the hibernation, it displayed a black screen.

                Stopping Vivaldi and restarting it didn't help. So I tried a reboot next, which didn't help, either. Then I did a shutdown, and when I restarted, things seemed to be working properly. But the next day, upon waking from hibernation, the same problem occurred. Since I spend most of my day in the browser, it's not a trivial issue here.

                Regressing to the previous update solved it, though. I first tested it with a brief hibernate and wakeup. No problem. Then I thought that timing might be a factor, but when I hibernated and went to a dental appointment, I was gone for about 1.5 hours, and when I returned, I could again awaken my laptop with no problem. I haven't had time to try an overnight hibernation yet, of course, but I'm pretty confident that the issue is somewhere in the update.

                    WetGeek Instead of displaying what was active on the screen before the hibernation, it displayed a black screen.

                    So the issue is that sometimes your laptop couldn't wake from hibernation?

                    That's the key bit of information that wasn't in the above posts. You said that there was a problem, or even various problems, but never said what the problems actually were.

                        WetGeek Oh no! I thought everything had gone well, but after awakening from a night of hibernation, various problems manifested, mostly browser-related. This has happened twice now.

                        @"EbonJaeger: I'm sorry if my message wasn't clearer, but that's the problem. And it's cured by regressing to the last previous update. I'd try to narrow it down to root cause, but right now certain medical issues require me to keep Vivaldi available to schedule appointments. Maybe when some of those issues are sorted, I can update again and try using Firefox and see if it's really just Vivaldi that's affected, or returning from any hibernation is an issue for another browser.

                            EbonJaeger So the issue is that sometimes your laptop couldn't wake from hibernation?

                            WetGeek I'm sorry if my message wasn't clearer, but that's the problem.

                            From my reading of the previous comment it sounds like it's not the waking up your session from hibernation itself that's the issue, but the fact that Vivaldi (specifically Vivaldi, and not other apps or the laptop as a whole) shows a black screen (?). Just to avoid confusion here.

                            And it mostly affected my browser, Vivaldi. Instead of displaying what was active on the screen before the hibernation, it displayed a black screen.

                                  I did the latest sync a few minutes ago and rebootet afterwards, now it won't come up and I got the following error message on my old laptop:

                                  [FAILED] Failed to start light.service - Light Display Manager.

                                  What would be the best thing to fix this?

                                  Thanks in advance!

                                    hunzel I have got the same problem.
                                    The system now no longer boots into the desktop.
                                    I will have to revert to to the previous update until a fix is found.

                                        Staudey

                                        Okay, now I know more, and it's definitely Vivaldi with the problem. After hibernating all night, I woke up my laptop this morning, and did a few normal things in my browser - banking, etc. Eventually things went dark, and unresponsive. So I closed Vivaldi, and another Vivaldi appeared. Closed than, and another one appeared. Altogether, I closed about 20 instances of it, which probably represented the last 20 or so sites I visited yesterday before I hibernated.

                                        I know that it launches a new process for every site that's loaded into a tab, so eventually (together with other apps in the other 11 virtual workspaces) it must have used up all available free memory. And this is NOT with the newesst sync. It's the previous sync that I regressed to yesterday.

                                        I still have some investigating to do, but it appears that Vivaldi isn't doing any garbage-collection, and memory is filling up until there's no more. When this happens, the screen looks like this:

                                        It's possible that it's not Vivaldi that's at fault, but possibly something else that's keeping it from releasing old memory, but right now Vivaldi is sure looking guilty to me. I need to keep an eye on what happens to free RAM when I work with Vivaldi, to verify my suspicions, but I just got up, so that will wait until after breakfast. I'll do a shutdown and restart, do this week's update again, and keep an eye on how much memory is used. I'll let you know more as soon as I've confirmed anything.

                                        Please excuse any typos in this message. I'm using Firefox right now, and I haven't taken the time to figuredout how to scale the text yet. It's extremely tiny on this laptop's full HD screen. Later ...

                                          Now I'm in Vivaldi again, and I can see what I'm typing. And I have another clue. Upon startup, the system tray displays some notifications that I haven't been able to capture before, because they disappear when I try to take a screenshot with one of them open. So I wrote the message on a notepad (the paper kind) so I could share it here:

                                          I'm talking about those six images on the far left. They read:

                                          plasma-browser-integration-host Closed
Please report this error to help improve the software

                                          So that leads me to believe that it's a flaw in the other KDE updates, that perhaps has nothing to do with Vivaldi. Chances are, if I'd found a way to use Firefox any longer, it might have had the same issues.

                                          I have forgotten the best way to monitor RAM usage, as I've not usually found it to be a concern with this laptop. Anybody have a favorite? I still want to see what changes happen as I use Vivaldi today.

                                            WetGeek

                                            Btop is now on duty.

                                            I've set up Vivaldi as I normally do: 12 virtual desktops, containg Thunderbird, Vivaldi, Aisleriot, kshisen, gnome-mahjongg, Telegram, VMs, VirtualBox, Office, Settings, Dolphin, and Terminology. The Btop image above reflects the system with these all loaded. As I work with Vivaldi today, I plan to watch the memory consumption occasionally, and especially to check it when the Vivaldi screen once again goes dark.

                                              @EbonJaeger

                                              I think KDE really messed up their last update. Now when I wake up from hibernation, Bluetooth is still enabled, but not working. And I can't enable my mouse and keyboard with anything short of a full shutdown and restart.

                                              I just don't have any more time to spend on something that I can't fix, so I'm going to exercise patience and try again after their next update. As a contributor, I have access to the KDE forum, so when I can find the time, I may look there for posts that are anything like what I'm experiencing. But even if that results in finding out what has happened over there, I won't be able to fix it anyway.

                                              I did determine that none of this nonsense happens if I use sleep at night instead of hibernate. That wouldn't normally be my preference, but it's better than nothing.

                                              AlphaElwedritsch Size of your RAM?
                                              Size of your SWAP?
                                              Partition or file (/dev/zram0)?

                                              See my Btop post about 3 before this one. That should answer all.