Hi everyone, I ran apt full-upgrade last month and accidentally deleted a couple packages that weren’t supposed to be removed, due to me not paying enough attention. I could recover most of the system just fine, since most of the missing features and related packages were obvious to me. However, I still couldn’t figure out why transparency is not working on KDE, both in Wayland and X. I suspected it could be a missing compositor, but libwayland and libqt6waylandcompositor6 (and related packages) are all installed (and that wouldn’t explain why it isn’t also working on X).
I have attached a screenshot to illustrate what I mean.
I would appreciate if anyone could help me figure out what package might be missing that is causing this issue. Thanks in advance!
EDIT: Thank you so much everyone! I finally solved my problem. I just had to replace libqt5quick5-gles by libqt5quick5 (non gles version).
Commandline: apt install libqt5quick5
Install: libqt5quick5:amd64 (5.15.10+dfsg-2+b2)
Remove: libqt5quick5-gles:amd64 (5.15.10+dfsg-2+b2)
That was actually my first attempt, but unfortunately I removed 484 packages during that process, so checking the log didn’t help me much. Some packages that were removed had many dependencies that I could quickly recover, like Dolphin and Okular, but in the end I was left with ~100 packages that I don’t know what they do.
While I could technically reinstall all of them manually, it would be less than ideal since many are indeed not needed and supposed to be removed during that update (apt complains about conflicts).
~$ awk '$1 == "2024-03-13" && $3 == "remove" {gsub(":amd64",""); print $4}' /var/log/dpkg.log | wc -w 484I am open to suggestions if you know how I could recover from this or improve my awk filter to make things easier.
100 isn’t that many really. If you’re really curious I would try reinstalling them in steps of 10 to narrow it down. And when/if you identified the pack of 10 with the culprit, uninistall those 10 and install 1 by 1: max number of reinstalls/uninstalls = 20
You are right. Breaking it down in steps of 10 followed by a reboot is actually great advice. I will get to it soon to see if I can find out what is wrong with the system (I am indeed curious).