Arch Linux

Woolie Wool

Member

Registered: 2019-02-10

Posts: 14

[RESOLVED] Files left behind after uninstalling LXQt

A while back I was having problems with KDE (turned out to be a configuration that didn't agree with a new KDE update so I just had to nuke my config and rebuild it), and installed LXQt as a temporary alternative. Soon thereafter, I removed all the LXQt packages and ever since then these messages have appeared during the post-transaction hooks of every pacman session:

ldconfig: File /usr/lib/libfm-qt6.so.16.0.0 is empty, not checked.
ldconfig: File /usr/lib/libfm-extra.so.4.2.0 is empty, not checked.
ldconfig: File /usr/lib/libQt6Xdg.so.4 is empty, not checked.
ldconfig: File /usr/lib/libmenu-cache.so is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys.so.2.2.0 is empty, not checked.
ldconfig: File /usr/lib/libQt6XdgIconLoader.so is empty, not checked.
ldconfig: File /usr/lib/libobt.so.2.0.2 is empty, not checked.
ldconfig: File /usr/lib/libfm-extra.so.4 is empty, not checked.
ldconfig: File /usr/lib/liblxqt.so is empty, not checked.
ldconfig: File /usr/lib/libdbusmenu-lxqt.so.0.3.0 is empty, not checked.
ldconfig: File /usr/lib/libqtermwidget6.so.2.2.0 is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys-ui.so.2 is empty, not checked.
ldconfig: File /usr/lib/libqtermwidget6.so is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys-ui.so is empty, not checked.
ldconfig: File /usr/lib/libqtermwidget6.so.2 is empty, not checked.
ldconfig: File /usr/lib/libmuparser.so is empty, not checked.
ldconfig: File /usr/lib/libmenu-cache.so.3 is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys.so.2 is empty, not checked.
ldconfig: File /usr/lib/libobt.so is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys.so is empty, not checked.
ldconfig: File /usr/lib/libfm-extra.so is empty, not checked.
ldconfig: File /usr/lib/libQt6Xdg.so is empty, not checked.
ldconfig: File /usr/lib/libmuparser.so.2.3.5 is empty, not checked.
ldconfig: File /usr/lib/libdbusmenu-lxqt.so is empty, not checked.
ldconfig: File /usr/lib/libfm-qt6.so is empty, not checked.
ldconfig: File /usr/lib/libobt.so.2 is empty, not checked.
ldconfig: File /usr/lib/liblxqt.so.2 is empty, not checked.
ldconfig: File /usr/lib/liblxqt.so.2.2.0 is empty, not checked.
ldconfig: File /usr/lib/libmuparser.so.2 is empty, not checked.
ldconfig: File /usr/lib/libobrender.so.32.0.0 is empty, not checked.
ldconfig: File /usr/lib/libfm-qt6.so.16 is empty, not checked.
ldconfig: File /usr/lib/libQt6Xdg.so.4.2.0 is empty, not checked.
ldconfig: File /usr/lib/libobrender.so is empty, not checked.
ldconfig: File /usr/lib/libdbusmenu-lxqt.so.0 is empty, not checked.
ldconfig: File /usr/lib/libmenu-cache.so.3.2.1 is empty, not checked.
ldconfig: File /usr/lib/liblxqt-globalkeys-ui.so.2.2.0 is empty, not checked.
ldconfig: File /usr/lib/libQt6XdgIconLoader.so.4 is empty, not checked.
ldconfig: File /usr/lib/libQt6XdgIconLoader.so.4.2.0 is empty, not checked.
ldconfig: File /usr/lib/libobrender.so.32 is empty, not checked.

This appears to have no practical effect on my system, no instability or usability issues, but they are annoying and ugly and I don't want to look at them. I sometimes briefly see references to other deleted LXQt elements when logging into KDE from my display manager (I use ly so it's in text mode until KDE takes over the display and thus will display system messages). How would I go about cleaning up the traces of LXQt to silence these messages?

Last edited by Woolie Wool (2025-08-18 05:20:25)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,315

Re: [RESOLVED] Files left behind after uninstalling LXQt

Either something went very wrong during the removal process or this is just a symptom of bigger problems.

Please run (as root/with root rights)

# pacman -Qkk | grep -v '0 altered files'

and post the output

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Woolie Wool

Member

Registered: 2019-02-10

Posts: 14

Re: [RESOLVED] Files left behind after uninstalling LXQt

Either something went very wrong during the removal process or this is just a symptom of bigger problems.

Please run (as root/with root rights)

# pacman -Qkk | grep -v '0 altered files'

and post the output

This gave me a lot of unrelated files (mostly packages I had changed the configurations of to suit my needs, and one whose AUR-supplied PKGBUILD broke and I built by hand), but a second grep for lxqt yields:

libdbusmenu-lxqt: no mtree file
liblxqt: no mtree file
lxqt-menu-data: no mtree file

I then grepped the file I piped that pacman command to again for "no mtree file" and got:

libdbusmenu-lxqt: no mtree file
libfm-extra: no mtree file
libfm-qt: no mtree file
liblxqt: no mtree file
libqtxdg: no mtree file
lxqt-menu-data: no mtree file
menu-cache: no mtree file
muparser: no mtree file
qtermwidget: no mtree file
qtxdg-tools: no mtree file
screengrab: no mtree file

Last edited by Woolie Wool (2025-08-14 04:16:42)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,173

Re: [RESOLVED] Files left behind after uninstalling LXQt

Either

something went very wrong during the removal process

or bigger issues are hidden behind

grep for lxqt … I then grepped

The output there means the package is still installed but broken and so are apparently the files it left behind.
Overall feels like a filesystem / SSD trimming related issue.
To clean this up, re-install the packages "pacman -S--dbonly …" then remove them.
Pay attention to the output (the first run will likely still get you the linker errors because it doesn't do anything about the files on disk, it's only to allow proper removal in the second step)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Woolie Wool

Member

Registered: 2019-02-10

Posts: 14

Re: [RESOLVED] Files left behind after uninstalling LXQt

Either

something went very wrong during the removal process

or bigger issues are hidden behind

grep for lxqt … I then grepped

The output there means the package is still installed but broken and so are apparently the files it left behind.
Overall feels like a filesystem / SSD trimming related issue.
To clean this up, re-install the packages "pacman -S--dbonly …" then remove them.
Pay attention to the output (the first run will likely still get you the linker errors because it doesn't do anything about the files on disk, it's only to allow proper removal in the second step)

That worked, thanks! I have no idea why it didn't actually delete the files when I uninstalled the packages the first time.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,173

Re: [RESOLVED] Files left behind after uninstalling LXQt

Overall feels like a filesystem / SSD trimming related issue.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
You'll probably have to shorten the original title.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc