Package: upgrade-reports
Severity: important
My previous release is: buster
I am upgrading to: bullseye
Archive date: unknown
Upgrade date: Thu 18 Aug 2022
uname -a before upgrade: didn't save it before upgrade, system was buster, up to date.
uname -a after upgrade: Linux hppro 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux
Method: apt as described in the release notes.
Contents of /etc/apt/sources.list:
---------------
# Bullseye
# Main sources
deb http://deb.debian.org/debian bullseye main contrib non-free
deb-src http://deb.debian.org/debian bullseye main contrib non-free
# Security sources
deb https://deb.debian.org/debian-security bullseye-security main contrib non-free
deb-src https://deb.debian.org/debian-security bullseye-security main contrib non-free
# Updates sources
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
# Backports sources
# deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
# deb-src http://deb.debian.org/debian/ bullseye-backports main contrib non-free
-------------
- Were there any non-Debian packages installed before the upgrade? If
so, what were they?
There where few non debian packages before the upgrade: a self built backport of bluez-alsa from unstable, another package needed to handle some specific smart cards (libbit4xpki-idemia-amd64.1.4.10-622.deb), and another self built backport of "octave-database". They all had been removed before the upgrade.
- Was the system pre-update a pure sarge system? If not, which packages
were not from sarge?
I assume here that "sarge" should be interpreted as "buster". System was a pure debian buster, except from the few removed packages above.
- Did any packages fail to upgrade?
I'm not usre because at a certain point I had no way to check if the update completed or not. Probably no.
- Were there any problems with the system after upgrading?
After some manual intervention everything seems to work properly now.
Further Comments/Problems:
I strictly followed the release notes instructions.
During the full-upgrade stage I had to left the system unattended for some time, while it was downloading packages, so the screen locked automatically by itself. When I got back there was the Gnome unlock screen, already with the "Debian 11" logo, but no textbox to input the password. I'm sure the system didn't reboot by itself, because it's a multi OS system and by default it boots back to Windows, not Linux.
I had no way to unlock the screen, so I switched to a console, where I could log-in as root. The system was still running, but had no way to check at which stage the upgrading process was. The last few lines of the script log were:
----
...
Setting up libreoffice-gnome (1:7.0.4-4+deb11u1) ...
Creating config file /etc/libreoffice/registry/gnome.xcd with new version
Setting up gnome-shell (3.38.6-1~deb11u1) ...
Installing new version of config file /etc/xdg/autostart/gnome-shell-overrides-migration.desktop ...
Setting up libreoffice-impress (1:7.0.4-4+deb11u1) ...
Creating config file /etc/libreoffice/registry/impress.xcd with new version
Creating config file /etc/libreoffice/registry/ogltrans.xcd with new version
Setting up gdm3 (3.38.2.1-1) ...
Installing new version of co
----
Last line was truncated as shown, it isn't a cut and paste error, and the script log was not changing, so I assumed that the upgrade process was stale.
I had no other option but to reboot. After rebooting I was unable to login so I tried restarting the upgrade from a console but apt warned that the package database was corrupted, or something like that, and suggested running:
dpkg --configure -a
After running this command and answering the question it posed, I have been able to complete the update process and now the system seems to work properly.
I have to add that I was abusing a little the standard upgrade procedure because I was running the Gnome Desktop as root (it's a test system with no other user on it).
I don't know if there could be way to fix an uncommon issue like this, but probably it would be wise to add a warn in the documentation about disabling automatic screen locking before running the upgrade.
Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.
Package lists before and after the upgrade provided as attachment. Note that here there are still some of the non debian packages listed before. During the upgrade process they were not present.