Opened 2 years ago

Last modified 12 months ago

#13132 reopened bug

Updating the system may require immediate restart

Reported by: axeld Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Kits/Package Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

It looks like the package management already moves packages around on an update. Since it doesn't keep the packages used open, it can happen that it won't be able to access a currently activated package anymore afterwards.

For example, the binutils package had been updated. "as" from that package could not be run anymore until a restart.

That could be improved by telling the packagefs whenever the location of an activated package changes during runtime.

Attachments (2)

package_daemon-677-debug-29-04-2017-19-29-16.report (24.9 KB) - added by vidrep 2 years ago.
package_daemon-677-syslog (1.7 KB) - added by vidrep 2 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 2 years ago by waddlesplash

Related bug that I never got around to reporting: After a "pkgman update", if you try to do anything else with pkgman (install/uninstall/etc.), package_daemon crashes.

comment:2 Changed 2 years ago by vidrep

hrev51135 x86_64 SoftwareUpdater->update 7 packages to hrev51137 Launching HaikuDepot before a reboot will cause package_daemon to crash Debug report and syslog attached

comment:3 Changed 2 years ago by vidrep

Has a Patch: set

Changed 2 years ago by vidrep

Attachment: package_daemon-677-syslog added

comment:4 Changed 2 years ago by pulkomandy

Has a Patch: unset

comment:5 Changed 2 years ago by jessicah

I wonder if some of this could be alleviated by using node refs to the activated packages, such as when their entry refs change, the package kit doesn't need to worry, and can still work with the nodes themselves no matter where they moved to.

I suppose the only downside to that is that it would hold file descriptors open, if I'm understanding the BNode documentation correctly... I guess the package kit doesn't hold files open currently, hence leading to the behaviour we currently have?

comment:6 Changed 2 years ago by diver

Owner: changed from nobody to bonefish
Status: newassigned

package_daemon crash in being tracked at #10898.

comment:7 Changed 12 months ago by cocobean

Tested with hrev52014. This bug seems fixed as of #10898..

comment:8 Changed 12 months ago by waddlesplash

Resolution: fixed
Status: assignedclosed

comment:9 Changed 12 months ago by diver

I don't think this one is fixed at all.

comment:10 Changed 12 months ago by pulkomandy

Resolution: fixed
Status: closedreopened
Note: See TracTickets for help on using tickets.