I´m using Lubuntu 20.04 and until now it happened 3 times that lxqt-panel shut down and immediately after that restarted.
In each case xpad (“sticky note application for X”) also terminated its process.
So my guess is that the weird behaviour of lxqt-panel might have something to do with xpad…
Anyhow, I looked at the logs (using lnav) each time and I think it´s best to post them here in case they may help:
Well, as far as the respective dates are concerned I just looked them up (as I tend to make notes of almost everything ).
I performed a fresh/clean install of Lubuntu 20.04 on Jan 20 this year.
So indeed the first occurrence of the phenomenon was on Feb 10. After that Mar 26 and then yesterday when I was in the middle of shutting down the system (but hadn´t initiated the shutdown process yet).
So this lxqt-panel/xpad thing doesn´t happen on a regular basis. Rather seldom and unpredictably.
Yes, that I do. Almost on a daily basis. So my system is up-to-date.
Perhaps you can check out if this is the issue you are experiencing. If it is, you can notify whoever is responsible of this not being fixed. If it is not precisely the same issue, you could open a new bug report, referencing this one.
That being said, a backtrace would be appreciated (consult your distro doc on how to find a meaningful backtrace).
Oh, that´s funny.
I looked up the package and it seems to be the latest version already:
sudo apt update
apt-get -s install liblxqt0
HINWEIS: Dies ist nur eine Simulation!
apt-get benötigt root-Privilegien für die reale Ausführung.
Behalten Sie ebenfalls in Hinterkopf, dass die Sperren deaktiviert
sind, verlassen Sie sich also bezüglich des reellen aktuellen
Status der Sperre nicht darauf!
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
liblxqt0 ist schon die neueste Version (0.14.1-0ubuntu2). # already the latest version
liblxqt0 wurde als manuell installiert festgelegt. # manually installed
I don´t want to mess around with package-management. If Lubuntu says it´s the latest version I really don´t want to force anything newer on it.
There will always be a discrepancy between what the distribution “thinks” is the newest version and what the developer or publisher thinks is the newest version, which is also actually the newest version.
That is certainly not the most bleeding edge distribution, there there are probably a lot of “outdated” packages, that mostly work fine, but are “outdated” according to the software developers who created the software that ultimately ends up as packages in your distribution.
Now if he referred to lxqt itself when saying that
0.14.1 is outdated
then the newest version is, as I assume 0.16.0:
So, you would need to use a distribution that uses this version or you would need to manually upgrade, but this is not so recommended, because it may break other things.
However, the point is, nobody at Github will care about this issue, as long as it is not confirmed to be an issue on the newest version. They first have to know if it is still an issue in the newest version. Only then, it is an issue that should be taken into account.
That is because there is no reason to fix an older version, if there is already a newer version that has the issue fixed. The only time that might seem reasonable is when developers need to backport fixes to older major versions, like it is the case with OpenVPN 2 or it was the case with Python 2.7, however usually one should just use the newest stable version.
Thank you @Akito for taking out so much the time of your day in order to provide such detailed information. It´s highly appreciated.
Thanks to your link I see now there´s a newer version of lxqt.
It seems to be provided by “tsujan”, the very person who responded to my query at github.
O.K., I see.
Since I don´t want to change distributions (as my Lubuntu installation is relatively new and in general I´m very satisfied with it) and I don´t want to manually upgrade either (thanks for your referring to that point ) I think it´s best to leave things as they are at the moment.
Despite all I seem to have learnt quite a few things.
Thanks for your explanation, Akito.