Did the Update right now.

Did it with Discover and not with "Software Center".

Worked well, as expected.
No issues so far.

Bluetooth now works as it should. I no longer need to do anything special to reconnect my mouse and keyboard after I reboot. That wasn't a serious issue, but an annoyance for sure. Thanks!

palto42 As a workaround, I had re-built the perl-xmlsimple package from main branch against stable and installed manually.

Harvey Thanks a lot, works now with package from repo 🙂

      Update went well, but this issue persists (now only works about 10% of the time) - any idea if/when it might get looked at again?

      Cherry-picked curl to fix a crash with other programs.

      this is the unheralded dirty work that will make transitions easier as we turn the corner. A cold one 🍻 for this crew:tm.

      After sync and reboot audio output device is gone on lenovo laptop, so no sound. Added my details to the open gh issue

      Edit: My hp mini 400 g6 (i5-10400T) sync done without issues

      Edit 2: Both are running Plasma

      Are these audio issues on all DEs?
      I have and had No problems on my KDE

      Other than still having to downgrade the kernel for audio everything else appears OK!

      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. A reboot doesn't help, but a shutdown and restart seemed to cure it. There appears to be nothing wrong with Vivaldi, as it works quite well once the laptop was restarted - tab stacks and all. But when I checked for broken packages, I found this:

      I remembered that apparmor has issues, but I don't use it, so I ignored that one. But the broken kernel appears to be more significant. So I tried to eopkg it --reinstall it, and got two more errors, for which I obviously couldn't get a screenshot.

      Does this sound familiar to anyone else? I've never had a reason to regress to an earlier version of a package. I believe I may need to do that here, unless there's a simpler solution, and if so, I'd appreciate a quick review of how to do that.

      I remember eopkg history to locate the previous version, but I'm not sure of what comes next. Also, would that generate problems because of all the KDE updates this week? Are they likely to require the newer kernel? Thanks!

        WetGeek these are false positives and not actually broken. still think they are trying to remedy that message. my current is 'broken' too. it;'s a symlink thing I think

            brent these are false positives and not actually broken

            Thanks for reminding me of that. But that apparently means my beloved Vivaldi might be the source of the problem, despite its appearing to work fine after a restart. So after I find the previous version number of it, whats next? Is eopkg it --reinstall all that's needed, or is there more to it?

              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.