this post was submitted on 25 Mar 2024
0 points (NaN% liked)

Linux

47696 readers
787 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
0
Accidentally uninstalled an important package in Debian Sid with KDE, transparency no longer working (lemmy.world)
submitted 6 months ago* (last edited 6 months ago) by buffy@lemmy.world to c/linux@lemmy.ml
7 comments fedilink hide all child comments
 

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)
top 7 comments
sorted by: hot top controversial new old
[–] elmicha@feddit.de 0 points 6 months ago (1 children)

Perhaps you can spot the package that got removed in /var/log/apt/history.log.

[–] buffy@lemmy.world 0 points 6 months ago* (last edited 6 months ago) (1 children)

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
484

I am open to suggestions if you know how I could recover from this or improve my awk filter to make things easier.

[–] ISOmorph@feddit.de 0 points 6 months ago* (last edited 6 months ago)

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

[–] Pantherina@feddit.de 0 points 6 months ago

Just reinstall plasma-desktop or however the metapackage is called

[–] kyoji@lemmy.world 0 points 6 months ago (1 children)

Are you on BTRFS? If so maybe you could restore to a snapshot prior to the apt upgrade?

I'm not very familiar with Debian, but perhaps there are official "groups" of packages that comprise a set of softwares, like KDE. Perhaps you could re-install that group, if it exists?

You could also create a new user, log in as that user, and see if the issue persists. If so then you'll know it's a system wide issue. If not, then maybe you could migrate to the new user?

Good luck!

[–] buffy@lemmy.world 0 points 6 months ago* (last edited 6 months ago) (1 children)

Sadly I am not using BTRFS for my root directory on this specific system. If I end up deciding to reinstall, I will definitely go back to BTRFS to avoid such problems.

Debian actually has a KDE group named kde-full. I reinstalled it but the issue persists, which was honestly surprising to me.

~$ sudo apt install kde-full
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kde-full is already the newest version (5:147).
0 upgraded, 0 newly installed, 0 to remove and 87 not upgraded.

The new user idea was really clever, thanks for the suggestion! I will try that now and see.

Edit: the new user also presents the same problem. Actually, it makes sense, since SDDM is affected as well (I should have mentioned that before).

[–] Pantherina@feddit.de 0 points 6 months ago

You will also need to use snapper before every apt-get upgrade to avoid these issues