Menu
▾
▴
#911 lxpanel unresponsive/doesn't work on linux kernel 4.17
lxpanel unresponsive/doesn't work on linux kernel 4.17
Using (L)Ubuntu 16.04.4 LTS (from #lsb_release -a) with Ubuntu kernel 4.17.0-041700-generic (from #uname -r) installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17/
On normal system boot, lxpanel is unresponsive - no tooltips, extremely extended response to choosing panel items, or no response at all, clock is not updated.
On same system using kernel 4.16.13-041613-generic (from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.13/ ) everything works as expected.
Windows work fine once opened. E.g. hot-key combination to get terminal (Ctrl-Alt-T pops up terminal instantly), and running graphical applications from the command line in that terminal works fine (e.g. thunderbird) , so it appears to be something in lxpanel that stops working between kernel 4.16.13 and 4.17 . Similar faulty behaviour also seen in 4.17-rc7 and 4.17-rc6. I do not have the capability to do a full bisection.
Ole Normann
The same faulty behaviour is confirmed to occur in kernel 4.17.1. (4.17.1-041701-generic)
lxpanel is unresponsive, and hangs/stalls. Left-click mouse menu on desktop is fully functional.
Today kernel 4.17.2 hit Fedora and now I've tried it on my "real" machine and it is working as before. Maybe you are using LXDE (or linux) on virtualbox or so?
No, it is Lubuntu on raw metal: no virtualisation of any kind.
lsb_release -cdr
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial
lxpanel -v
lxpanel 0.8.2
It works fine on the above distribution with kernel 4.6.17, and when I last looked, the behaviour on a 4.17 kernel was faulty in the way I described above.
If I get the time, I load up a (L)Ubuntu 18.04 distribution and see if that makes any difference. It might take a while.
I just tried kernels 4.18.3, and 4.18.5 and in both cases lxpanel is now working as expected. The unresponsive behaviour as detailed in the original post has stopped happening. If I get the time, I'll see if I can work out in which kernel revision it started working again. HOWEVER, it may be something to do with a (L)Ubuntu update, as I'm now on 16.04.5 LTS.
$ lsb_release -cdr
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
$ lxpanel -v
lxpanel 0.8.2
$ uname -srvmo
Linux 4.18.5-041805-generic #201808241320 SMP Fri Aug 24 13:22:12 UTC 2018 x86_64 GNU/Linux
Further to the above, as the problem is now resolved via an upgrade, (from (L)ubuntu 16.04.4 LTS to (L)ubuntu 16.04.5 LTS and/or to kernel 4.18.3 or above (and possibly an earlier kernel), this can be marked closed.
Ole Normann