LXQt desktop not allowing new apps

Hi, I found this on reddit and I’m also experiencing the same issue, used to happen on lubuntu 22.04 shipping 0.17 lxqt, still happens with lxqt 1.1.1.

After some time away from the desktop, the lxqt desktop does not allow me to open any new apps, allows me to logout though (which resolves the issue after login back again).

Checking on htop, there are several (50+ maybe) “/usr/bin/lxt-config-monitor -l” entries, if kill them, the desktop works as expected once again.

I don’t know why is this happening, for some context it’s and i3 6100 with integrated graphics I use as a “homelab”, the monitor is connected through HDMI and it’s shared with another desktop, so basically I switch sources on the monitor while I leave it running. In case it’s relevant, the keyboard and mouse also gets disconnected in that switching. I normally log in and out of lxqt and everything is fine, but when I leave the desktop open this always happens after some time, forcing me to either manually kill those “lxqt-config-monitor -l” processes or login out and back in.

Anyone can give some pointers on where or what to look for in order to fix it?


Just a quick thought (a workaround maybe)

I also use KVM (keyboard/video/mouse) type switches & ignore systems awhile*), I did find some boxes (and software stacks) didn’t respond well with lack of messages from loss of keyboard/mouse (these messages can be box specific), and my workaround was having an old MOUSE connected to a USB port that was permanently connected to that box, it just lived behind the box & was never used (sat out of reach anyway, hidden behind boxes & screens).

The keyboard/mouse I do actually use is controlled by the KVM switches I use (thus connection may vanish from the box on my keystrokes), but by having an old mouse connected to boxes, I had less issues with the systems using KVM switches, and you may find this too.


Thanks a lot for the suggestion, just tried it and the issue is still present.

For more information I did a tail -f /var/log/kern.log before disconnecting everything and there is nothing happening besides logging the hardware being plugged/unplugged:

Aug 23 10:32:10 GHL kernel: [133801.388664] usb 1-1: USB disconnect, device number 24
Aug 23 10:32:10 GHL kernel: [133801.388677] usb 1-1.1: USB disconnect, device number 25
Aug 23 10:32:10 GHL kernel: [133801.568530] usb 1-1.2: USB disconnect, device number 26
Aug 23 10:32:10 GHL kernel: [133801.756650] usb 1-1.3: USB disconnect, device number 27
Aug 23 11:21:26 GHL kernel: [136757.259045] usb 1-8: USB disconnect, device number 20
Aug 23 11:21:39 GHL kernel: [136769.988886] usb 1-1: new high-speed USB device number 28 using xhci_hcd
Aug 23 11:21:39 GHL kernel: [136770.143770] usb 1-1: New USB device found, idVendor=2109, idProduct=2812, bcdDevice=90.90
Aug 23 11:21:39 GHL kernel: [136770.143789] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 23 11:21:39 GHL kernel: [136770.143799] usb 1-1: Product: USB2.0 Hub             
Aug 23 11:21:39 GHL kernel: [136770.143806] usb 1-1: Manufacturer: VIA Labs, Inc.         
Aug 23 11:21:39 GHL kernel: [136770.145183] hub 1-1:1.0: USB hub found
Aug 23 11:21:39 GHL kernel: [136770.145420] hub 1-1:1.0: 4 ports detected
Aug 23 11:21:39 GHL kernel: [136770.456893] usb 1-1.1: new full-speed USB device number 29 using xhci_hcd
Aug 23 11:21:39 GHL kernel: [136770.575016] usb 1-1.1: New USB device found, idVendor=0c45, idProduct=7664, bcdDevice


Any other ideas?

Some more hopefully useful information, I’ve just tested without disconnecting anything, the only thing that happened was the energy saving screen blanking while sort of monitored for the “lxqt-config-monitor -l” processes to spawn, couldn’t see any while the monitor was still on.

I left it for some time and when I checked back there they where, a few dozen of those processes and this time I was monitoring sudo tail -f /var/log/syslog and this showed up syslog

I don’t really understand what’s going on, can’t say if it’s a kscreen bug or a hardware issue, but I think it’s probably safe to say that lxqt is not to blame for it besides maybe how it handles this events which could be related to this lxqt github issue, idk.

Again any help or direction on where to go from here is appreciated.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.