Debian10LXQT: normal that it takes 47 sec to be ready?

Desktop Environments and Multimedia
Post Reply
Message
Author
debcub
Posts: 55
Joined: 2017-01-18 16:12

Debian10LXQT: normal that it takes 47 sec to be ready?

#1 Post by debcub »

Hi,
I am learning to use LXQT with Debian 10. Each time I login (key in my password at the user icon), it takes about 47 seconds before I can use the computer (see below), i.e., before the Debian desktop has opened and the lower panel with the applications, e.g., network applet, is ready. The same takes only about 25 seconds with Debian 10 LXDE (same HD, multiboot). Is it normal that LXQT is that slow?

Thanks, debcub

Here are my computer details:

System Model
SAMSUNG ELECTRONICS CO., LTD. 300E5C-S04DE
RAM 4GB
Processor
Processor a 2,20 gigahertz Intel Core i3-2328M
64 kilobyte primary memory cache
256 kilobyte secondary memory cache
3072 kilobyte tertiary memory cache
64-bit ready
Multi-core (2 total)
Hyper-threaded (4 total)

Controllers
Intel(R) 7 Series Chipset Family SATA AHCI Controller

Display
Intel(R) HD Graphics 3000 [Display adapter]
NVIDIA GeForce GT 620M [Display adapter]
PnP-Monitor (Standard) (15,7"vis, August 2010) Jetzt mein Notebook:
System Model
SAMSUNG ELECTRONICS CO., LTD. 300E5C-S04DE
RAM 4GB
Processor
Processor a 2,20 gigahertz Intel Core i3-2328M
64 kilobyte primary memory cache
256 kilobyte secondary memory cache
3072 kilobyte tertiary memory cache
64-bit ready
Multi-core (2 total)
Hyper-threaded (4 total)

User avatar
sunrat
Global Moderator
Global Moderator
Posts: 3644
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 3 times
Been thanked: 1 time

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#2 Post by sunrat »

You need to check logs to see if there's a holdup. Set up persistent journalling and use journalctl, check log files in /var/log/ , even ~/.xsession-errors may provide a clue.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#3 Post by debcub »

sunrat wrote:You need to check logs to see if there's a holdup. Set up persistent journalling and use journalctl, check log files in /var/log/ , even ~/.xsession-errors may provide a clue.
Thanks, but what is persistent journalling - what is journalling anyway - and how do I set it up?

User avatar
sickpig
Posts: 589
Joined: 2019-01-23 10:34

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#4 Post by sickpig »

https://wiki.archlinux.org/index.php/Systemd/Journal

man journald.conf - to make it peristent

edit https://wiki.archlinux.org/index.php/Im ... md-analyze can help in analyzing slow boot

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#5 Post by debcub »

I will do the "man" thing, but first, maybe this helps?
~/.xsession-errors It is a verrrrry big file, and full of error lines like this:

The beginning of .xsession-errors opened a while ago, 2020-07-28-1:50 pm:

Code: Select all

Xsession: X session started for <my user id> at Mon 27 Jul 16:51:22 CEST 2020
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/<my user id>/.Xauthority
localuser:<my user id> being added to access control listerr
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
(0x7ffc57ba8350) Debug: New PolkitAgentListener  0x56493cf01a80
(0x7ffc57ba8350) Debug: Adding new listener  PolkitQt1::Agent::Listener(0x7ffc57ba8360) for  0x56493cf01a80
[Notice] Started
isPrimaryInstance
no cached wallpaper. generate a new one!
size of original image QSize(1920, 1080)
wallpaper cached saved to  "/home/<my user id>/.cache/pcmanfm-qt/lxqt/wallpaper.cache"
(0x7ffd9b8e2860) Debug: systemd: "CanHibernate" = "yes"
(0x7ffd9b8e2860) Debug: systemd: "CanSuspend" = "yes"
(0x7ffec0b26360) Debug: systemd: "CanReboot" = "yes"
(0x7ffec0b26360) Debug: systemd: "CanPowerOff" = "yes"
(0x7fffa2c5dc60) Debug: ()
(0x7fffa2c5dc60) Debug: WinIdChange 1400008 handle QWidgetWindow(0x55af2f0a1030, name="LXQtPanel panel1Window") QScreen(0x55af2ed47d00, name="LVDS-1")
[Notice] X11 error: type: 0, serial: 203, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 205, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 207, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
And the "error code: 10 'Bad..."-lines continue, just the numbers after "type: 0, serial:" change. Occasionally some other text follows, then those lines again, and they are legion! Unfortunately, I am no expert on this, do not know what to make out of it, and would not know how many lines I should present here?

User avatar
sickpig
Posts: 589
Joined: 2019-01-23 10:34

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#6 Post by sickpig »

debcub wrote:I will do the "man" thing, but first, maybe this helps?
it just indicates that some application is wanting to start as root

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#7 Post by debcub »

*** 1 ***
sickpig wrote:it just indicates that some application is wanting to start as root
Does this info help, then?

*** 2 ***
man journald.conf - to make it peristent
This opens just a help page! "These files configure various parameters of the systemd journal service..." . Wow, this sounds weird. Neither do I know what jounald is all about nor how to make it persistent :(

Maybe you have the impression that I am an expert in Linux and Debian. No way! I know a lot but from each of this lot I know only a little, what a user needs to know to barely survive. So, please, how can the various log-files help me to make my start-up time shorter and what about this journal, please :?:

User avatar
Head_on_a_Stick
Posts: 13450
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#8 Post by Head_on_a_Stick »

debcub wrote:
man journald.conf - to make it peristent
This opens just a help page!
Well read it then. Or ask the interweb how to make the systemd journal persistent.

And for ~/.xsession-errors try deleting the file then starting LXQt again to generate some fresh entries.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#9 Post by debcub »

Head_on_a_Stick wrote:Well read it then.
That's harsh! Like throwing a manual "how to learn to swim" to drowning person and advising him "Read it"!

User avatar
Onsemeliot
Posts: 281
Joined: 2010-12-15 14:43

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#10 Post by Onsemeliot »

Just some thoughts:

I have never used LXQt but maybe it makes sense to look what applications do auto-start (after you finally have reached the desktop). And if you have such an option in grub you could also try to start without extensions. (There is a way to start just a minimal system even if you don't have a dedicated boot entry but I would need to search for it too.)

User avatar
sickpig
Posts: 589
Joined: 2019-01-23 10:34

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#11 Post by sickpig »

debcub wrote:This opens just a help page! "These files configure various parameters of the systemd journal service..." . Wow, this sounds weird. Neither do I know what jounald is all about nor how to make it persistent :(
the first archwiki link shared earlier explains what systemd journal is all about. The conf file is /etc/systemd/journald.conf

Code: Select all

[Journal]
Storage=persistent
You can use the above option to make it persistent, but there are numerous options like size specification which you may want to specify hence the man page.
Also the 2nd arch wiki link shared earlier will give you clues about the delay in the boot process.
And you may want to generate new xsession-errors as suggested by Hoas.

Deb-fan
Posts: 1042
Joined: 2012-08-14 12:27

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#12 Post by Deb-fan »

That's harsh! Like throwing a manual "how to learn to swim" to drowning person and advising him "Read it"!
It's exactly nothing like the ridiculous statement you made there. Am about 200% sure Hoas would dive in or throw whoever a dang innertube, call an ambulance or whatever. It's basically telling someone with a claimed interest in something to employ common sense and demonstrate any amount of effort in learning about it. No ... that big a difference doesn't seem right, would profile the systems boot(with systemd cmds)for one thing, see which services are auto-starting and how long they're taking. See if something is causing the PC to hang-up during startup.

PS, though on reflection, throwing someone a bk on how to swim would be friggin hilarious, so thanks. :) The Hoasinater is clearly big time into studying of the medical field to, would be shocked if he doesn't know stuff like performing CPR etc.
Most powerful FREE tech-support tool on the planet * HERE. *

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#13 Post by debcub »

sickpig wrote:...
the first archwiki link...
Thank you, but presently I cannot see the wood for the trees; but I will get through. Be patient with an oldie ;) I was born 2 years before the end of WWII.

Deb-fan
Posts: 1042
Joined: 2012-08-14 12:27

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#14 Post by Deb-fan »

Woah '43?!? Dayum you are old dude. Lol ... messing around, like your style you've got an apparent eloquent way with words. :)

Google systemd-analyze ... Am sure things have changed a lot from when you were a kid. You'd just hop on the family dinosaur and ride down to the local library, wait did they have books back then? Still kidding around. Teasing older folks I think are cool is a hobby that's near and dear to me. :D
Most powerful FREE tech-support tool on the planet * HERE. *

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#15 Post by debcub »

Deb-fan wrote:Woah '43?!?.. Am sure things have changed a lot from when you were a kid...
You bet! And when I tell you that I did Internet in the 1980s using DOS, Kermit and COM/KOM... Now seriously: I'll attack .xsession-errors first.
P.S. I liked your teasing, honestly :D

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#16 Post by debcub »

Ok, first step:
Head_on_a_Stick wrote:And for ~/.xsession-errors try deleting the file then starting LXQt again to generate some fresh entries.
Deleted and here is the fresh entry (only 195 lines altogether):

Code: Select all

Xsession: X session started for <user-id> at Wed 29 Jul 14:06:25 CEST 2020
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/<user-id>/.Xauthority
localuser:<user-id> being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
(0x7fff6ae2eb80) Debug: Detected "ETPS/2 Elantech Touchpad" on "/dev/input/event6"
(0x7fff6ae2eb80) Debug: Load settings for "ETPS/2 Elantech Touchpad"
(0x7ffd7a64e270) Debug: New PolkitAgentListener  0x555ce2e88080
(0x7ffd7a64e270) Debug: Adding new listener  PolkitQt1::Agent::Listener(0x7ffd7a64e280) for  0x555ce2e88080
[Notice] Started
isPrimaryInstance

[01mHP Linux Imaging and Printing System (ver. 3.18.12)[0m
[01mSystem Tray Status Service ver. 2.0[0m

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

(0x7ffd88c6dae0) Debug: systemd: "CanHibernate" = "yes"
(0x7ffd88c6dae0) Debug: systemd: "CanSuspend" = "yes"
(0x7ffeca438b30) Debug: systemd: "CanReboot" = "yes"
(0x7ffeca438b30) Debug: systemd: "CanPowerOff" = "yes"
(0x7ffc4da2aa80) Debug: ()
(0x7ffc4da2aa80) Debug: WinIdChange 1200008 handle QWidgetWindow(0x558433616350, name="LXQtPanel panel1Window") QScreen(0x5584332a9d00, name="LVDS-1")
(0x7ffc4da2aa80) Debug: Systray started
[Notice] X11 error: type: 0, serial: 475, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 477, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 479, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 481, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F1'
[Notice] X11 error: type: 0, serial: 491, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 493, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 495, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 497, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F2'
[Notice] X11 error: type: 0, serial: 507, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 509, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 511, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 513, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F3'
[Notice] X11 error: type: 0, serial: 523, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 525, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 527, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 529, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F4'
[Notice] X11 error: type: 0, serial: 539, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 541, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 543, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 545, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F5'
[Notice] X11 error: type: 0, serial: 555, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 557, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 559, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 561, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F6'
[Notice] X11 error: type: 0, serial: 571, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 573, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 575, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 577, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F7'
[Notice] X11 error: type: 0, serial: 587, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 589, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 591, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 593, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F8'
[Notice] X11 error: type: 0, serial: 603, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 605, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 607, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 609, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F9'
[Notice] X11 error: type: 0, serial: 619, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 621, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 623, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 625, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F10'
[Notice] X11 error: type: 0, serial: 635, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 637, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 639, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 641, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F11'
[Notice] X11 error: type: 0, serial: 651, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 653, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 655, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Notice] X11 error: type: 0, serial: 657, error_code: 10 'BadAccess (attempt to access private resource denied)', request_code: 33 (GrabKey), minor_code: 0, resourceid: 338
[Warning] Cannot grab shortcut 'Control+F12'
Translator is not loaded "qlipper_en_GB" "/usr/share/qlipper/translations"
(0x7fff9d9dca60) Debug: BatteryChanged discharging: true chargeLevel: 69 actionTime: QTime(Invalid)
(0x7fff9d9dca60) Debug: Inhibit got: 28
(0x7fff9d9dca60) Debug: Starting idlenesswatcher
(0x7ffc4da2aa80) Debug: execAction "/usr/share/applications/pcmanfm-qt.desktop"
This is my part. I am unable to interpret it. Can anybody, please?

debcub
Posts: 55
Joined: 2017-01-18 16:12

Re: Debian10LXQT: normal that it takes 47 sec to be ready?

#17 Post by debcub »

After I had deleted the old "~/.xsession-errors", and rebooted, it took only 29 sec for the Desktop to be ready. Even after a second reboot it was only 29 sec. Is this deemed ok?
Then I will be content.

Post Reply