Control: reassign -1 upgrade-reports On Lu, 20 sep 21, 21:42:24, mYnDstrEAm wrote: > Package: Debian > Version: 11 > > Maybe these should be separate bug reports. However, I'm not sure about that > and this is made more inconvenient and outdated by using emails for > bug-reports. Filing it all under Debian rather than e.g. rkhunter or KDE > Plasma packages is implying or calling for such things to be tested and > solved prior to enabling upgrade by Debian contributors. Please split/link if > needed. > > I upgraded multiple machines from Debian 10/KDE to 11/KDE stable. > > - After the partial upgrade with `sudo apt upgrade --without-new-pkgs` the > console output quit with: > > Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: > /bin/which E: Problem executing scripts DPkg::Post-Invoke 'if [ -x > /usr/bin/rkhunter ] && grep -qiE '^APT_AUTOGEN=.?(true|yes)' > /etc/default/rkhunter; then /usr/share/rkhunter/scripts/rkhupd.sh; fi' E: > Sub-process returned an error code > > I asked about it [here](https://unix.stackexchange.com/q/666356/233262) with > more details. It's related to [#932594](https://bugs.debian.org/932594). If I > just selected keep current version in a prompt during the upgrade this isn't > a bug (even though it may be useful if these prompts showed an indication > that the new conf file is needed/has updated). > > - I also had to remove package aide. Furthermore, unatteneded-upgr was > blocked. I also asked about these two, in my case minor, issues in the > question above. The unatteneded-upgrades had this output:Waiting for cache > lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process > 2705 (unattended-upgr)... 30s > > - Another minor issue: after (fully) upgrading the initial boot screen asking > for the grub password was red and looked a bit strange instead of blue but > quickly changed back to the blue one and didn't look strange and/or red > reboots afterwards or another machine. Could this have occurred because some > /etc / conf file wasn't upgraded or was it a negligible glitch? > > - On one of my Debian10/KDE->11 machines after logging in I only had a black > screen (with some windows on top). This is because plasmashell isn't running > (the only thing that runs is startplasma-x11) so I started it with kstart5 > plasmashell. However, it crashes right after it seems to have fully loaded. I > asked about it [here](https://unix.stackexchange.com/q/666617/233262) and the > solution was to re/move the > /home/username/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar > folder. > > - The cursor was too small and changing it was not possible because the > cursortheme wasn't working. I found the solution > [here](https://forum.siduction.org/index.php?topic=8133.0): it was > (re?)installing package qml-module-org-kde-newstuff. > > - The upgrade can fail if there is not enough disk-space. The upgrade process > should (accurately) check how much disk space is available and needed and if > needed do the upgrades in batches, leaving a bit of disk-space as a buffer, > rather than trying to run the full upgrade and repeatedly failing. The > upgrade should not fail due to lack of disk space. > On one machine this was worked around by rerunning the upgrade and sudo dpkg > --configure -a. > > - On one of my Debian10/KDE->11 machines the sound output wasn't working > anymore before the upgrade, after running sudo apt-get dist-upgrade before > changing the sources.list entries to "bullseye". I asked about it > [here](https://unix.stackexchange.com/questions/669001/audio-missing-after-upgrading-from-debian-10-to-11). > The solution was to (re?)install package plasma-pa.
Reassigning to correct (pseudo-)package. Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages
signature.asc
Description: PGP signature
