Dev1 Galaxy Forum / Devuan Chimaera LXQT is slow to respond once desktop is fully present

Re: Devuan Chimaera LXQT is slow to respond once desktop is fully present

dummy@example.com (Mike-thinky) — Sat, 03 Dec 2022 18:42:18 +0000

Ogis1975 wrote:

Hello. Just check
.xsession-errors
file (in /home/yourusername/ dir). If I'm not mistaken, the problem lies with the default keyboard keys...and more specifically to keybinding to show desktop. Just delete it, or assign to another one.

Bingo, and thanks.

BatteryChanged discharging: false chargeLevel: 100 actionTime: QTime(Invalid)
Starting idlenesswatcher
"PowerButton" "" ""
"SuspendButton" "" ""
"HibenateButton" "" ""
[Notice] Started
[Notice] X11 error: type: 0, serial: 367, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 369, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 371, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 373, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Warning] Cannot grab shortcut 'Alt+F2'
[Notice] X11 error: type: 0, serial: 695, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 697, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 699, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 701, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Warning] Cannot grab shortcut 'Alt+F1'
[Notice] X11 error: type: 0, serial: 711, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 713, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 715, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Notice] X11 error: type: 0, serial: 717, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 380
[Warning] Cannot grab shortcut 'Control+Alt+D'
Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
These settings cannot work with your current window manager (Metacity (Marco))
These settings cannot work with your current window manager (Metacity (Marco))
Listener adapter polkit_qt_listener_initiate_authentication
GSimpleAsyncResult: 0x55aecb4ab600
polkit_qt_listener_initiate_authentication callback for  0x55aecb449200
REQUEST
COMPLETED
Listener adapter polkit_qt_listener_initiate_authentication_finish

Now I will be looking up which files set these keybindings.

I renamed the .xsession-errors file and rebooted, it does take about 20 secs to wake up, and generates an 8k file and the first errors are about dbus and wanting to start systemd!!!

dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument                 
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge                                   
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument                 
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1                                                  
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument                       
dbus-update-activation-environment: setting SHELL=/bin/bash                                                           
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1                                                        
dbus-update-activation-environment: setting LANGUAGE=en_GB:en                                                             
dbus-update-activation-environment: setting LIBOVERLAY_SCROLLBAR=0                                                            
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge

the next bit of going wrong seems to be:

Output:  "Virtual6"
Output:  "Virtual7"
Output:  "Virtual8"
New PolkitAgentListener  0x5572435cf000
Adding new listener  PolkitQt1::Agent::Listener(0x7fffc5d6adb0) for  0x5572435cf000
lxqt-config-monitor: Settings applied.
isPrimaryInstance

** (xiccd:3341): WARNING **: 18:57:39.708: EDID is empty

** (xiccd:3341): WARNING **: 18:57:39.725: EDID is empty
size of cached file QSize(1153, 768) , requiredSize: QSize(1153, 768)
origin "/usr/share/lxqt/themes/ambiance/Butterfly-Kenneth-Wimer.jpg"
QDBusMarshaller: cannot add an invalid QVariant
QDBusConnection: error: could not send message to service "org.freedesktop.login1" path "/org/freedesktop/login1" interface "org.freedesktop.login1.Manager" member "CanHibernate": Marshalling failed: Variant containing QVariant::Invalid passed in arguments
** Dbus error **************************

So that is the next things to google for.

Re: Devuan Chimaera LXQT is slow to respond once desktop is fully present

dummy@example.com (Ogis1975) — Sat, 03 Dec 2022 12:08:44 +0000

Hello. Just check

.xsession-errors

file (in /home/yourusername/ dir). If I'm not mistaken, the problem lies with the default keyboard keys...and more specifically to keybinding to show desktop. Just delete it, or assign to another one.

Devuan Chimaera LXQT is slow to respond once desktop is fully present

dummy@example.com (Mike-thinky) — Fri, 02 Dec 2022 17:25:56 +0000

I have had enough of my current Linux install, so I have spun up a collection of VM's to see which ones I could use long term.

So I have Chimaera nstalled as Cinnamon, Mate, LXQT, Ghost BSD, Trisquel, and some others. They all have 1 core, 8Gb of Ram, 80Mb of Video to emulate a similar fairly heavy workload.

The LXQT version takes about 4 secs to come up according to the dmesg logs:

[    3.680341] ext2 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[    3.706336] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[    3.719381] Adding 999420k swap on /dev/mapper/devuanC--vg-swap_1.  Priority:-2 extents:1 across:999420k SSFS
[    3.807282] audit: type=1400 audit(1669999101.792:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1013 comm="apparmor_parser"
[    3.814743] audit: type=1400 audit(1669999101.800:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=1022 comm="apparmor_parser"
[    3.833185] audit: type=1400 audit(1669999101.820:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1026 comm="apparmor_parser"
[    3.833188] audit: type=1400 audit(1669999101.820:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1026 comm="apparmor_parser"
[    3.833189] audit: type=1400 audit(1669999101.820:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=1026 comm="apparmor_parser"
[    3.947562] audit: type=1400 audit(1669999101.932:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice" pid=1035 comm="apparmor_parser"
[    3.947564] audit: type=1400 audit(1669999101.932:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" pid=1035 comm="apparmor_parser"
[    3.962661] audit: type=1400 audit(1669999101.948:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1042 comm="apparmor_parser"
[    3.962666] audit: type=1400 audit(1669999101.948:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1042 comm="apparmor_parser"
root@devuanC:~# dmesg | grep -i "error||warning|fail|segfault|fatal"

That is fine, and comparable to the other VM's

The desktop comes up and is fully decorated at about that time, BUT it takes at least another 10-20 secs before the mouse is able to select anything, eg start menu.

Any ideas what or where I should be looking for that delay just in the LXQT version?

Once that initial delay is over it is then quite snappy, faster than cinnamon for sure.