Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using Mageia, the startup is fast and smooth. It changes over to the login screen for KDE. There are 5 dots, representing the progress of KDE bootup. It runs through the first 4 dots instantly, and then get stuck on the last dot for about 10-15 seconds. I have recently had my distro installed with KDE, where this last dot took only 2-3 seconds. So the 15 seconds is far longer than expected.
I have tried to analyse the problem using bootchart and "systemd-analyse blame" and "time".
I cannot see any obvious sinners in any of them that should cause KDE to take such an extraordinarily long time.
The tools I have been using is good at analysing system time, xorg and general GUI. But it is not particularily strong at analysing KDE for example.
Is there any way to analyse only KDE?
And why would KDE only hang at the very end of its startup, what does it do at that point?
I am using my "user" data from my previous distro installation. But I have also tried with a new fresh users with almost no Plasma applets, which takes a few seconds less, but still a lot of time.
I have also run through my KDM and xsession.error and xorg.0.log to find any obvious reasons, but there seem to be onl insignificant problems there.
I looked up Plymouth -
It is an intermediate stage that displays a logo--4 dots flash to let you know the system is working and saves the user from seeing any errors occasionally in the background.
It also handels the display settings and this is were the user will find problems (not always related to graphics) I think it is in /dir/var/logs (sysfile)
There is also a stage where Grub and the kernel work together to find the graphics card.
Ensure that you have a driver installed for your card. If your suspicious of your driver try dmesg (demessaging it)
Please explain a little bit more and clarify "using user data"
By this I mean that I am using the same home partition as in a previous installation, and the same username, everything. So the desktop data is old.
But I did try creating a new user.
Quote:
Originally Posted by Ztcoracat
Try looking in the message logs or dmesg-
I can't find anything really telling there. The only problem I find is that pulseaudio tries to start twice. I tried to solve that, but it turned out tricky. But I might give it another go another time, but I am quite sure that is not the problem.
I have a "feeling" that the problem is related to "network-up" somehow, that this is the last thing KDE does before showing the desktop, and that this takes longer than necessary.
I found such a problem with "systemd-analyze blame" and I took the service away from systemd since it is also in the desktop. In systemd it was the one taking by far most time. But when I removed it there was no difference.
My gut feeling still thinks its related to the network somehow, the wireless connection. Not sure though.
Quote:
Originally Posted by Ztcoracat
You could try using the LXDE, XFCE or Gnome envirnment instead and see if the problem persists--
I have enlightenment as well, but I never really use it. I am a huge KDE fan.
I did find a lot of QT errors at one point, but according to searches on the net, none of them were "bad" errors. And I didn't find any ways to get rid of them either.
I looked up Plymouth -
It is an intermediate stage that displays a logo--4 dots flash to let you know the system is working and saves the user from seeing any errors occasionally in the background.
It also handels the display settings and this is were the user will find problems (not always related to graphics) I think it is in /dir/var/logs (sysfile)
There is also a stage where Grub and the kernel work together to find the graphics card.
Ensure that you have a driver installed for your card. If your suspicious of your driver try dmesg (demessaging it)
HTH
Yes. It passed that stage fine. It is the latest stage which is the problem, after KDM takes over from system and X.
My graphics is Intel HD, and it runs quite fine, so that is not the problem. It is in the very last stage. I don't really know what KDE is doing then, but someone said it is doing the plasma applets. But the problem was the same with a new user account, without any plasma applets!
It seems to be something to do with how kde creates its config files on first login and it appears that it will only complete that with a ttf- font package installed.
If you're still having trouble try installing ttf-dejavu and kde should complete the login even with all the config files removed.
It's a Arch Linux 2011 thread but it might work--(page 2 post #43)
Another thing you could try is "Boot Info Script"
It's a bash script which searches all hard drives for into related to booting. Looks good for troubleshooting booting problems.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.