#14605 closed bug (no change required)
Fail to activate package
Reported by: | msiism | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Kits/Package Kit | Version: | R1/beta1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
I'm running hrev52295+96.
After installing BurnItNow, it doesn't show up in the Applications menu. Also, executing it from the command line doesn't seem to work, though I might have done something wrong there.
Rebooting fixes the problem, however.
Change History (5)
comment:1 by , 6 years ago
comment:3 by , 6 years ago
Component: | Applications/HaikuDepot → Kits/Package Kit |
---|---|
Keywords: | BurnItNow removed |
Owner: | changed from | to
Summary: | BurnItNow not installable → Fail to activate package |
I changed the title of the ticket, as it's not really an issue of a specific package.
I think what's described is a know penomenon, but details on what's causing it are thin. I suggest having a tail -f /var/logs/syslog
running in Terminal when installing something. A successful installation looks like this:
KERN: package_daemon [1963373262: 700] CommitTransactionHandler::_ChangePackageActivation(): activating 1, deactivating 0 packages KERN: unknown [1963373740: 700] Volume::_ChangeActivation(): 1 new packages, 0 old packages KERN: unknown [1963375663: 700] package "burnitnow-1.2-4-x86_gcc2.hpkg" activated KERN: package_daemon [1963881220: 700] Volume::_PackagesEntryCreated("burnitnow-1.2-4-x86_gcc2.hpkg")
Maybe we get some hints from a failed activation, but I kinda doubt it will help much...
comment:4 by , 5 years ago
Resolution: | → no change required |
---|---|
Status: | new → closed |
If it worked after the reboot, that means a system package update is pending. We now display messages when a reboot is required in HaikuDepot, so no more change is required.
comment:5 by , 5 years ago
Remove milestone for tickets with status = closed and resolution != fixed
It works fine in nightly here.