Update of my Plasma laptop went well, however, an update of my Plasma VM did not. I suspect that there is, or was, an upstream issue at Oracle, and if it's not already fixed, I hope for a resolution from them soon. There is a workaround, though, so all my VMs are usable for illustrating answers to forum questions. And that's really their only raison d'etre.

I'll explain. After I update each VM, I typically just shut it down instead of rebooting. That's because I usually have no reason to restart it at that time ... I just want to make sure it's up-to-date the next time I use it. It will load all the new packages if/when I start it again. If I do a shutdown now after an update has finished, the VM now enters an error state so serious that I need to use a long press on the power switch to recover. This doesn't happen just for Plasma, but for all of the VMs.

After restarting the host, and launching the VM to load all the new packages, if I execute another shutdown now command, it all works as expected. The end result of this adventure, for each VM, is that the update works, but it makes an update pretty painful. The workaround I mentioned: if I do execute a reboot after each update, then I can execute shutdown now without any problems. So, I'm convinced that the root cause of the problem is in the current VirtualBox, and as soon as the upgraded packages have been loaded, everything seems to work okay.

Since there is a workaround, and my four Solus VMs are quite usable now, I'm happy to wait for the next sync to see whether my idea is correct - that it's an issue that Oracle has already fixed.

oops bug, merkuro calendar no longer working

QQmlApplicationEngine failed to load component
qrc:/main.qml:344:26: Type IncidenceInfoDrawer unavailable
qrc:/IncidenceInfoDrawer.qml:111:13: Type IncidenceInfoContents unavailable
qrc:/IncidenceInfoContents.qml:8:1: module "QtLocation" is not installed

    ReillyBrogan hi, yes but only after a reboot.
    it does spawn a trillion lines like this though

    qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x563d665ee990) to a QML list of QQuickAbstractButton*

    x 100000

        Another new package that missed getting a mention is snippetexpander, it lets you save your often used text snippets and then auto expand them whenever you type their abbreviation. It also has a handy search and paste window that you can open with a global shortcut (I use it that way the most).

        Snippet Expander's website: https://snippetexpander.org/

        As well as the package maintainer, I'm the author, and happy to answer any questions if you ping me on a new forum thread.

          Fine on my two physical Plasma Desktops and Weather Report Widget has been fixed so it doesn't crash plasmashell when loaded anymore. Will update the VM on Tuesday when I boot into Win 11 for patches.

          Thank you for the hut CLI add!

          I usually build it myself, but having it as a package makes it even more convenient.

          ianmjones Sorry about that. Right now, I have no way to get a summary of added and removed packages, so I have to go through all the commits in the cycle looking for particular commit messages. I've made an issue to hopefully improve this in the future.

              Lucien_Lachance I checked and I get those errors with the previous version, so I don't think that's a new bug. I'll add qt6-location as a rundep so it's pulled in automatically

                No issues to report. All went well

                  Axios was out of town a few days. my update went great as well.

                    EbonJaeger Pisi and eopkg have been updated to add versioned FilesDB and LazyDB instances, which are used to speed up eopkg searches for locally installed packages and their files. These databases will now be regenerated automatically as necessary. For the full details, check out this Pull Request.

                    After running the update, I immediately rerun eopkg to install a package prior to a reboot. This lead to a rebuild of FilesDB. Is this expected behaviour? Does the updated eopkg need to rebuild FilesDB on first run?

                        Sebastian It only happens if you switch between py2 and py3 version of eopkg. Do you use the py3 version before? If you tried packaging, our build pipeline is all py3 by default. You might not realized, you used py3 eopkg there. It is also quite harmless, it just takes time.

                          Cherry-picked discord 0.0.74

                          I think it also does this for the first package operation after installing the new eopkg version, when it initializes the new FilesDB format (and sets it to version 3). After that it should only do rebuilds when you switch between Python 2 and Python 3 eopkg (the latter uses version 4).