Linux Questions

1550 readers

1 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 2 years ago

MODERATORS

[email protected]

Apt package updates take longer than expected - where to look? (lemmy.world)

submitted 1 week ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

I've been daily driving Kubuntu for ages now (currently on 24.10), and I've noticed that updates take a while for seemingly no reason.

The downloads are slower than my internet is capable of, but they happen fast enough. It's just that some packages take longer than I would expect on the "unpacking" step.

For example, anytime there's a new kernel release or new headers, apt downloads the packages fast enough, but the unpacking takes time with seemingly no resource usage. No increased CPU load (for possible inflating of a compressed archive), no IOWAIT warnings, my NVMe disk shows very little throughput (and can handle much faster disk operations, like downloading games via Steam), stuff like that. The system seems to be at idle, and yet the unpacking of some packages just... takes a while.

It's not like it's a huge issue. It's only maybe an extra 30+ seconds, but it's got me wondering if there's anything I could do to improve it.

sudo apt clean hasn't had any effect, and my Google searches are of people complaining of either slow download speeds or 30+ minute delays that end up being failing drives.

Anyone have ideas?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 week ago

The next time packages are unpacking (or just before), run in another terminal/tab: journalctl -f.

That should give you the logs. Try to do this when no/minimum other apps are running as to not pollute the logs.