Control: severity -1 important [ The severity might deserve to be even lower though, depending on the analysis of the bug. ]
Hi! On Wed, 2018-01-24 at 06:05:14 +0100, Christoph Anton Mitterer wrote: > Package: dpkg > Version: 1.19.0.5 > Severity: serious > Not sure if the following is expected to happen, but I think > dpkg doesn't notice when some packages aren't actually fully upgraded. Are you sure they are not fully upgraded? What makes you think so? Just the dpkg.log below? > Here's the situation: > Since a while I see sporadic freezes of my system (quite often actually > while I do upgrades via aptitude and dpkg runs through the packages). > > Until know I thought it would be my new notebook, but I just went back to > my old one (swapped the SSD) and there it hapened as well, so it must be > something else in Debian (kernel, GPU drivers whatever). Intel microcode? > Once it's frozen, only power off helps (no magic sysrq), after reboot, when > I check the logs, then apt's termlog, doesn't show the end message, and > it seems also that dpkg's log shows that packages haven't completely installed > /configured, etc. > (see attached log) That might well be because the log file is not fsync()ed to disk, so the operations might hae finished but the log not been written. > And I noticed that my locales where broken, because of the recent new libc > packages in sid... and "locales" wasn't configured. > > > Normally dpkg -C would show this then, but it doesn't. > Neither does dpkg --configure -a do anything. And there are no packages in the status file with Status less than installed. And no lingering files under «/var/lib/dpkg/updates»? > This happened alrready quite some times now, an probably my system has > many packages in a state not fully installed, while dpkg thinks everything > would be fine. dpkg is very careful about how it handles its database. If it think they are installed, and there are no update journal entries on the above directory. Then this might indicate something more severe like a very broken filesystem on-disk or implementation or hardware failure or similar. > Interestingly: debsums -asc doesn't find problems. That to me would indicate that the packages are either the old versions or the new ones, but thay match. > I have no idea how to debug this any further... please tell me if you need > anything. > btw: this is on btrfs That alone seems very suspect IMO. Thanks, Guillem
