However, it takes several minutes before the panels will display and the application menu and system tray become active. http://i.imgur.com/8Huraeu.png
What can I do to make the desktop load more quickly? In researching this problem, I believe I saw something about using modprobe to change when the display manager loads from run level 1 to run level 3. Is this accurate? or relevant?
Any and all help gratefully accepted. Thanks in advance.
As far as I can tell, except for the slow desktop load time, the installation was successful. KInfoCenter reports the correct card and video resolution. Display has been rock solid, with no more “tearing” (or whatever it is called when there is like static on the display), quicker response times, sharper images and better color depth.
However, if I’ve been working in openSUSE for a time (1 hour? 2 hours?), then, when I logout of one user’s session and login as the other user, there is no significant delay to render the desktop completely.
What does this mean? Can you explain me what’s going on? Is there some sort of cache that’s created?
I still have the problem of slow desktop rendering if I cold boot. Is there a way to fix this?
Thanks for your continued support. I appreciate it.
I ran systemd-analyze blame and here’s the output (I didn’t include services further down in the output where the time drops to ms). It doesn’t mean much to me but can you take a look at it and give me your feedback?
Note the difference in userspace time. From the critical chain listing it seems* that your computer is waiting 20s or more for the network. Is it wireless? AFAIK the desktop would keep on loading regardless. Perhaps you have a start-up application that blocks the desktop** until it gets a connection?
*disclaimer: I’m using systemd-analyze only for the second time today, never needed it, so I’m not sure I know what I’m talking about. Besides, your total time is less than mine.
**wildly speculative. You may want to wait for someone more knowledgeable in this subject.
My mini-desktop is a Sony Vaio model VGC-RA840G. Over 10 years old but I forget exactly when I got it. It is liquid cooled - totally silent - which I really like. It’s been upgraded some over the years.
Hi, just a different hint since I occasionally see something similar on my test laptop, 2007 vintage, dual core, 800 MHz FSB, spinning disk.
When using BTRFS, these boxes just have slow access to disk when dealing with highly fragmented journal files, or when dealing with a nearly full /root partition filled up with snapshots.
My guess is that 30-60 s boot times are normal for such machines, but I witnessed as high as 3-5 minutes occasionally, like the original post suggests, when the journal file in active use was big (say, more that 30MB before rollover to a new file) or when snapshots nearly filled the /root partition.
The update to the Nvidia driver might just have triggered a number of snapshots and/or growing journal files.
Look for system.journal or user-1000.journal (or whatever user number experiences delays) files in /var/log/journal/<some numbers>/
Look also for free space on /root and possibly clean up unneeded snapshots.
BTW, nobody booting from an SSD is likely to witness such things.
Your system’s boot time according to your ‘systemd-analyze’-results look pretty reasonable, comparable to those of my system.
Just my guess:
You could try another wallpaper for your desktop and change your system settings concerning desktop and workspace appearance to default values,
since you told about problems with rendering the desktop background right after booting.
System settings -> hardware -> screen /monitor has settings for the compositor, that could also have an effect.
If a kernel update happens then the boot can take a while since the kernels need to be sorted out. Sometimes a long boot happens. Also if a corrupted or improper closed file system is detected fsck is run to correct problems and that can take time. But these things happen before the desktop.
If you have auto-login set turn it off since it can hide problems