Applications not showing up in Deskbar Menu

[begasus]

After installing Qupzilla over HaikuDepot it didn't show up in the DeskbarMenu, I also noticed it when installing hpkg's in /boot/home/config/packages that they didn't show up, I had to reboot to see them and use them.

[waddlesplash]

Pretty sure this is a "clean" occurrence of the bug that ttcoder and I saw in #10959.

[waddlesplash]

Line 2591:

KERN: package_daemon [16808149:   582] Failed to open packages activation file: No such file or directory
KERN: package_daemon [16808516:   582] Failed to get activated packages info from activated packages file. Assuming all package files in package directory are activated.
KERN: package_daemon [16809062:   582] latest volume state:

Bug described in this ticket, line 7048:

KERN: package_daemon [1709725728:   584] KERN: Volume::_PackagesEntryCreated("qtcore_x86-4.8.5.git-4-x86_gcc2.hpkg")
KERN: package_daemon [1709726163:   584] Volume::_PackagesEntryCreated("qupzilla_x86-1.7.x-1-x86_gcc2.hpkg")

..and then 7091:

KERN: package_daemon [2096953595:   584] CommitTransactionHandler::_ChangePackageActivation(): activating 0, deactivating 1 packages
KERN: package_daemon [2097454000:   584] Volume::_PackagesEntryRemoved("qupzilla_x86-1.7.x-1-x86_gcc2.hpkg")
KERN: [ACPI Debug]  String KERN: [0x1A] "_Q80 : Temperature Up/Down"
KERN: [ACPI Debug]  String KERN: [0x1A] "_Q80 : Temperature Up/Down"
KERN: package_daemon [2112720364:   584] CommitTransactionHandler::_ChangePackageActivation(): activating 1, deactivating 0 packages
KERN: package_daemon [2113220825:   584] Volume::_PackagesEntryCreated("qupzilla_x86-1.7.x-1-x86_gcc2.hpkg")

Why is there a "deactivating" for the QupZilla package before an "activating" of it? That seems suspicious to me...

[begasus]

IIRC it deppended on a library that needed to be installed, maybe that explains why there was a deactivation before? (ps HaikuDepot installed the library automaticly - maybe some output could be shown as to what it is doing in the background?)

[waddlesplash]

This is due to running a system upgrade first on a pre-HPKG_COMPRESSION_NONE system as described in #10959. If it occurs in some other case, please reopen. Otherwise, closing as a duplicate.