Hello everybody,

Long time Linux user but a KaOS newbie here! 👋

I just installed KaOS a few days after the jump to Plasma 6 happened, and have had pretty much no issues. There's one "non-trivial" issue however: virtualbox-qt5 doesn't start, because it's missing libQt5Help.so.5. It also appears to be the only one missing:

$ ldd ./usr/lib/virtualbox/VirtualBox | grep "not found"
        libQt5Help.so.5 => not found

After a little detective work, trial and error, both qt5-base and qt5-tools were installed, but that one .so is missing. pacman -F does not return an owner to the file either. So perhaps it's a build config issue in PKGCONFIG or something similar?

I'm not familiar with building Qt5 itself, so I didn't start debugging that now (plus I'm on a potato for a few days, so recompiling big things myself is slow). Meanwhile I'll try to borrowing the missing file from another distribution, perhaps that works in a pinch.

So far KaOS + Plasma 6 has been an absolute joy! Using the computer feels very snappy and responsive, compared with Manjaro Plasma 5. All devices and features work just fine, so currently my plan is to keep using KaOS in (at least) this one laptop and slowly going through my use cases (spoilers: all of them are quite common for Linux power users) to see what works and what doesn't. I like the idea of having a one-arch-only and one-desktop-environment-only distro with a sharp focus and opinions (which I support, obviously) - the result really seems to be a bit different distro that actually stands out from the crowd in its favor. Thank you for all the hard work you've put into it so far!

Without full SysInfo, this is just a guess, but this look like a system not updated prior to installing new applications.
Please post or pastebin the output of Octopi > SysInfo, see https://kaosx.us/docs/

There was indeed three packages which 404'd during install (docker, docker-cli and virtualbox-modules) but they were installed running pacman -Syu right after, so I don't think that's an issue. The Docker image was built and it runs fine, the VirtualBox machine as well.

You left out the most important part for this issue of the SysInfo log, please pastebin the full log, including pacman log & installation log.
Though it will be interesting to see what the output is of pacman -Qi docker-buildx and pacman -Qi openssl-1.1 (last one is in the KaOS repo as openssl1.1, so not installed in any supported way).
I'll add the qt5-tools package to the depends also now for virtualbox (was listed as makedepend only, was never an issue before, since plasma-workspace depended on it, but that one now depends on qt6-tools), but that does not explain why libQt5Help.so.5 was not found on your install after you did install qt5-tools.

Thanks for the dependency fix!

As I wrote above, qt5-tools was not installed at that time. Sorry for the wrong info earlier.

Just to clarify; I can use Pacman directly, right?

This is absolutely not supported, and most of this thread will be deleted.
KaOS is NOT Arch based and installing packages from a repo that is Arch based WILL break your install, not a matter of if, but when, please read:
https://kaosx.us/about/based/
What you do with your install is of course entirely up to you, but please don't come to the forums if you want to use Arch or Arch based packages and run into broken packages/install. (the whole filesystem, base of your install is entirely different here)

Yes, I'm aware that KaOS is not Arch based and that I really should not install pre-built packages from other sources. As I said earlier, I did that because the packages were not currently available in KaOS. All foreign packages are now locally re-built from their PKGBUILD files and all seems to be well.

However, KCP guide https://kaosx.us/docs/kcp/ says that "If you can find working PKGBUILDs elsewhere, use them." so I do have to say I am a bit conflicted, since that's essentially what I did... Anyway, I'll keep any self-caused troubles out of the forum, and they weren't the issue here either.

What do you think about the Octopi SysInfo behavior? Would you like me to reproduce it with a clean install?

    The use of a PKGBUILD is entirely different from installing a build package from the Arch repositories as you did, see why pacman was chosen (especially because of the availability of tens of thousands of PKGBUILDs):
    https://kaosx.us/docs/package/

    The permission issue of SysInfo will be tested/tried to replicate today.

    direc85 However, KCP guide https://kaosx.us/docs/kcp/ says that "If you can find working PKGBUILDs elsewhere, use them." so I do have to say I am a bit conflicted, since that's essentially what I did...

    It should mean working for KaOS, you need to understand packages are named differently, they are packaged not the same way as Arch Linux. If you want to use PKGBUILD from Arch you have to know package to package relation between Arch and KaOS (or find them by yourself, which sometimes not easy)

      Permissions issues is confirmed, and started around the end of September for most installs, looks to be caused by an upgrade of Systemd to 254, it changed permissions for all new files owned by root from rw-r-r to only rw, no answer yet how to fix.

      Thanks for clarification. I'll have to study KaOS packaging before going any further. I think I'll remake a few "missing" packages for myself to get the ball rolling. Let's see how it turns out!

      8 days later

      Same problem here

      ldd /usr/lib/virtualbox/VirtualBox | grep Qt
      libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f6cf8200000)
      libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f6cf7a00000)
      libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f6cf7200000)
      libQt5PrintSupport.so.5 => /usr/lib/libQt5PrintSupport.so.5 (0x00007f6cf8d8d000)
      libQt5X11Extras.so.5 => /usr/lib/libQt5X11Extras.so.5 (0x00007f6cfa987000)
      libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5 (0x00007f6cf8847000)
      libQt5Xml.so.5 => /usr/lib/libQt5Xml.so.5 (0x00007f6cfa943000)
      libQt5Help.so.5 => not found

      
[2024-02-20T16:56:43-0500] [PACMAN] Running '/usr/bin/pacman -S --noconfirm apps/virtualbox-qt5'
[2024-02-20T16:56:43-0500] [ALPM] transaction started
[2024-02-20T16:56:43-0500] [ALPM] installed xf86-input-mouse (1.9.5-1)
[2024-02-20T16:56:43-0500] [ALPM] installed virtualbox-modules (7.0.14-4)
[2024-02-20T16:56:47-0500] [ALPM-SCRIPTLET] Loading modules: vboxnetadp vboxnetflt vboxdrv 
[2024-02-20T16:56:48-0500] [ALPM] installed virtualbox-qt5 (7.0.14-2)
[2024-02-20T16:56:48-0500] [ALPM] transaction completed
[2024-02-20T16:56:48-0500] [ALPM] running 'gtk-update-icon-cache.hook'...
[2024-02-20T16:56:48-0500] [ALPM] running 'update-desktop-database.hook'...
[2024-02-20T16:56:48-0500] [ALPM] running 'update-mime-database.hook'...
[2024-02-20T16:56:51-0500] [PACMAN] Running '/usr/bin/pacman -S --noconfirm --asdeps apps/virtualbox-ext-oracle apps/virtualbox-guest-additions'
[2024-02-20T16:56:51-0500] [ALPM] transaction started
[2024-02-20T16:56:51-0500] [ALPM] installed virtualbox-ext-oracle (7.0.14-1)
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[2024-02-20T16:56:54-0500] [ALPM] installed virtualbox-guest-additions (7.0.14-1)
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] 
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===> virtualbox-guest-additions post install message:
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===>
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===> By using this package you accept
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===> the VirtualBox Personal Use and Evaluation License (PUEL)
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===> which can be found here: http://virtualbox.org/wiki/VirtualBox_PUEL
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===>
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===> If you do not accept this license, you must remove the package immediately.
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] ===>
[2024-02-20T16:56:54-0500] [ALPM-SCRIPTLET] 
[2024-02-20T16:56:54-0500] [ALPM] transaction completed