Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56075 - [lxqt] new lxqt-themes replacing lxqt-common and the upgrade that came with it break lxqt

Attached to Project: Community Packages
Opened by Javier (jevv) - Sunday, 22 October 2017, 06:50 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 22 October 2017, 07:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Recently after fixing dependency on libqtxdg, lxqt got an additional update, which ended up not able to startlxqt again. The following upgrades happened:

[2017-10-21 22:51] [ALPM] running 'systemd-update.hook'...
[2017-10-21 23:49] [PACMAN] Running 'pacman -Syu'
[2017-10-21 23:49] [PACMAN] synchronizing package lists
[2017-10-21 23:49] [PACMAN] starting full system upgrade
[2017-10-21 23:49] [ALPM] transaction started
[2017-10-21 23:49] [ALPM] removed lxqt-common (0.11.2-1)
[2017-10-21 23:49] [ALPM] installed lxqt-themes (0.12.0-2)
[2017-10-21 23:49] [ALPM] upgraded lximage-qt (0.5.1-2 -> 0.6.0-1)
[2017-10-21 23:49] [ALPM] upgraded lxqt-config (0.12.0-1 -> 0.12.0-2)

Notice how the package lxqt-themes replaces lxqt-common... So this new upgrade got lxqt broken once again. Please also notice the prior fix requiring recompilation for libqtxdg did work actually... This new upgrade is the one that broke everything again...
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 22 October 2017, 07:21 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Sunday, 22 October 2017, 06:58 GMT
Broke what, exactly? Without errors, logs, etc, this is totally useless.

I can only guess that you used --force with the previous updates, since they included all kinds of conflicts with lxqt-common. If that's the case, that's what's caused your problem.
Comment by Javier (jevv) - Sunday, 22 October 2017, 07:15 GMT
Well, lxqt session doesn't start anymore... And, thanks to your question:

/home/general/.xinitrc: line 98: startlxqt: command not found

Somehow "startlxqt" is lost. And as far as I can read from the wiki:

https://wiki.archlinux.org/index.php/LXQt#Using_xinit

"startlxqt" still is the way to start the lxqt session, as well as from the lxqt-session man page:

SEE ALSO
startlxqt.1 LXQt session initialization and launch script (e.g. in .xinitrc)
Comment by Doug Newgard (Scimmia) - Sunday, 22 October 2017, 07:21 GMT
So yeah, this was caused by your previous use of --force. You ended up with a bunch of files owned by 2 packages, so when one of those packages got removed, it broke everything.

Loading...