Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Plasma startup very slow after update
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Thu Aug 16, 2018 2:24 pm    Post subject: Plasma startup very slow after update Reply with quote

I updated my system yesterday and now the startup of plasma has become very slow.
It takes more than 40 seconds between the login in SDDM and a fully loaded KDE
environment. Before, it was like 5 seconds (SSD drive). Same problem with a new
user with minimal configuration. However, after a logout, a new login is really fast.

Anybody with the same problem?

I haven't found anything in the log files I can relate to this behavior. Any help is appreciated.

Spacebug


Here is my xorg-session.log:

Code:

kcm_input: Using X11 backend
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Initializing  "kcm_style" :  "kcminit_style"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ktimezoned.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/baloosearchmodule.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/freespacenotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/filenamesearchmodule.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/desktopnotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/solidautoeject.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkwatcher.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/soliduiserver.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/keyboard.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/remotenotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/device_automounter.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/colorcorrectlocationupdater.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/statusnotifierwatcher.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ksysguard.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/khotkeys.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/proxyscout.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkstatus.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/bluedevil.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/recentdocumentsnotifier.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/appmenu.so"
Initializing  "kcm_access" :  "kcminit_access"
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/disable_kmix.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/fonts_akregator.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/fonts_global.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/fonts_global_toolbar.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/fonts_kate.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/kde4breeze.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/kile.upd' for new updates
"Missing \"Version=5\", file '/usr/share/kconf_update/kile.upd' will be skipped."
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/krdb_libpathwipe.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/krunnerplugins.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates
2018-08-15T17:58:43 Checking update-file '/usr/share/kconf_update/okular.upd' for new updates
"Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."
Initializing  "kcm_input" :  "kcminit_mouse"
kcm_input: Using X11 backend
Xlib XKB extension major= 1  minor= 0
X server XKB extension major= 1  minor= 0
Qt: Session management error: networkIdsList argument is NULL
Configuring Lock Action
ksmserver: "/var/run/user/1001/KSMserver"
ksmserver: KSMServer: SetAProc_loc: conn  0 , prot= local , file= @/tmp/.ICE-unix/3981
ksmserver: KSMServer: SetAProc_loc: conn  1 , prot= unix , file= /tmp/.ICE-unix/3981
ksmserver: KSMServer::restoreSession  "saved at previous logout"
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.10'
ksmserver: Starting autostart service  "/etc/xdg/autostart/baloo_file.desktop" ("/usr/bin/baloo_file")
ksmserver: Starting autostart service  "/etc/xdg/autostart/krunner.desktop" ("/usr/bin/krunner")
ksmserver: Starting autostart service  "/etc/xdg/autostart/org.kde.plasmashell.desktop" ("/usr/bin/plasmashell")
ksmserver: Starting autostart service  "/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop" ("/usr/lib64/libexec/polkit-kde-authentication-agent-1")
ksmserver: Starting autostart service  "/etc/xdg/autostart/xembedsniproxy.desktop" ("/usr/bin/xembedsniproxy")
ksmserver: Autostart 0 done
Session path: "/org/freedesktop/ConsoleKit/Session4"
kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
Initializing  "kded_touchpad" :  "kcminit_touchpad"
kcm_touchpad: Using X11 backend
Width:  2851  height:  1891
Approx. resX:  31  resY:  37
Touchpad resolution: x:  31  y:  32
Final resolution x: 31  y: 32
ksmserver: completeShutdownOrCheckpoint called
ksmserver: Kcminit phase 1 done
ksmserver: Starting autostart service  "/etc/xdg/autostart/pulseaudio.desktop" ("/usr/bin/start-pulseaudio-x11")
ksmserver: Autostart 1 done
New PolkitAgentListener  0x5603247d42e0
Adding new listener  PolkitQt1::Agent::Listener(0x5603247e4070) for  0x5603247d42e0
Listener online
Authentication agent result: true
ksmserver: completeShutdownOrCheckpoint called
ksmserver: Starting autostart service  "/etc/xdg/autostart/powerdevil.desktop" ("/usr/lib64/libexec/org_kde_powerdevil")
ksmserver: Autostart 2 done
ksmserver: Kcminit phase 2 done
Installing the delayed initialization callback.
"\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
bluedevil: Created
kf5.kded: found kded module "touchpad" by prepending 'kded_' to the library path, please fix your metadata.
kcm_touchpad: Using X11 backend
Width:  2851  height:  1891
Approx. resX:  31  resY:  37
Touchpad resolution: x:  31  y:  32
Final resolution x: 31  y: 32
Delayed initialization.
ksmserver: Starting notification thread
Reloading the khotkeys configuration
Version 2 File!
true
Imported file "/usr/share/khotkeys/konqueror_gestures_kde321.khotkeys"
Imported file "/usr/share/khotkeys/defaults.khotkeys"
Imported file "/usr/share/khotkeys/kde32b1.khotkeys"
org.kde.plasmaquick: Applet preload policy set to 1
bluedevil: ObexManager operational changed false
bluedevil: Bluetooth operational changed true
bluedevil: Agent registered
bluedevil: Requested default Agent
powerdevil: Backend loaded, loading core
powerdevil: Core loaded, initializing backend
powerdevil: Using XRandR
powerdevil: Screen brightness value:  937
powerdevil: Screen brightness value max:  937
powerdevil: current screen brightness value:  937
powerdevil: Backend is ready, KDE Power Management system initialized
powerdevil: Battery with UDI "/org/freedesktop/UPower/devices/battery_BAT0" was detected
powerdevil: Current session is now active
powerdevil: fd passing available: true
powerdevil: systemd powersave events handling inhibited, descriptor: 18
powerdevil: ConsoleKit support initialized
powerdevil: Got a valid offer for  "DPMSControl"
ksmserver: completeShutdownOrCheckpoint called
powerdevil: Core is ready, registering various services on the bus...
powerdevil: Can't contact systemd
powerdevil: We are now into activity  "fb9d9acb-eae4-4edf-a3ff-9231ac30e70e"
powerdevil: () ()
powerdevil: () ()
powerdevil: Loading profile for plugged AC
powerdevil: Activity is not forcing a profile
powerdevil: Handle button events action could not check for screen configuration
powerdevil:
powerdevil: Loading timeouts with  300000
powerdevil: Can't contact systemd
OpenGL vendor string:                   Intel Open Source Technology Center
OpenGL renderer string:                 Mesa DRI Intel(R) HD Graphics 5300 (Broadwell GT2)
OpenGL version string:                  3.0 Mesa 17.3.9
OpenGL shading language version string: 1.30
Driver:                                 Intel
GPU class:                              Unknown
OpenGL version:                         3.0
GLSL version:                           1.30
Mesa version:                           17.3.9
X server version:                       1.19.5
Linux kernel version:                   4.9.95
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop"
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
bluedevil: ObexManager operational changed true
bluedevil: ObexAgent registered
trying to show an empty dialog
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
trying to show an empty dialog
Registering "org.kde.StatusNotifierHost-4005" as system tray
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
Plasma Shell startup completed
org.kde.plasmaquick: New Applet  "Application Launcher" with a weight of 81
org.kde.plasmaquick: New Applet  "Digital Clock" with a weight of 26
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/code/logic.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/logic.js")
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1856, resource id: 10485780, major code: 18 (ChangeProperty), minor code: 0
powerdevil: Screen brightness value:  937
powerdevil: Screen brightness value max:  937
powerdevil: Screen brightness value:  937
powerdevil: Screen brightness value max:  937
Both point size and pixel size set. Using pixel size.
Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/code/logic.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js")
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Audio Volume" with a weight of 26
org.kde.plasmaquick: New Applet  "Clipboard" with a weight of 26
org.kde.plasmaquick: New Applet  "Device Notifier" with a weight of 26
org.kde.plasmaquick: New Applet  "Notifications" with a weight of 26
org.kde.plasmaquick: New Applet  "Battery and Brightness" with a weight of 26
org.kde.plasmaquick: New Applet  "Bluetooth" with a weight of 26
org.kde.plasmaquick: Delayed preload of  "Application Launcher" after 0.806 seconds
KAStatsFavoritesModel::setFavorites is ignored
KActivities: Database connection:  "kactivities_db_resources_139653176612864_readonly"
    query_only:          QVariant(qlonglong, 1)
    journal_mode:        QVariant(QString, "wal")
    wal_autocheckpoint:  QVariant(qlonglong, 100)
    synchronous:         QVariant(qlonglong, 0)
Entry is not valid "kontact.desktop" 0x55f30f11b3d0
Entry is not valid "ktp-contactlist.desktop" 0x55f30f11b3d0
Entry is not valid "org.kde.discover.desktop" 0x55f30f11b3d0
Entry is not valid "kontact.desktop" 0x55f30f11b3d0
Entry is not valid "ktp-contactlist.desktop" 0x55f30f11b3d0
Entry is not valid "org.kde.discover.desktop" 0x55f30f11b3d0
Closing SQL connection:  "kactivities_db_resources_139653176612864_readonly"
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 88 msec
org.kde.plasmaquick: Delayed preload of  "Audio Volume" after 2.601 seconds
org.kde.plasmaquick: Applet "Audio Volume" loaded after 81 msec
org.kde.plasmaquick: Delayed preload of  "Device Notifier" after 3.971 seconds
org.kde.plasmaquick: Applet "Device Notifier" loaded after 9 msec
org.kde.plasmaquick: Delayed preload of  "Clipboard" after 4.158 seconds
org.kde.plasmaquick: Applet "Clipboard" loaded after 23 msec
org.kde.plasmaquick: Delayed preload of  "Bluetooth" after 5.783 seconds
Initializing  "kcm_input" :  "kcminit_mouse"
kcm_input: Using X11 backend
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2770, resource id: 10485764, major code: 18 (ChangeProperty), minor code: 0
org.kde.plasmaquick: Applet "Bluetooth" loaded after 61 msec
org.kde.plasmaquick: Delayed preload of  "Notifications" after 6.831 seconds
org.kde.plasmaquick: Applet "Notifications" loaded after 0 msec
org.kde.plasmaquick: Delayed preload of  "Battery and Brightness" after 6.944 seconds
org.kde.plasmaquick: Applet "Battery and Brightness" loaded after 32 msec
org.kde.plasmaquick: Delayed preload of  "Digital Clock" after 7.348 seconds
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: Applet "Digital Clock" loaded after 109 msec
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 0 msec
org.kde.plasmaquick: Increasing score for "Application Launcher" to 86
Back to top
View user's profile Send private message
Keruskerfuerst
Advocate
Advocate


Joined: 01 Feb 2006
Posts: 2288
Location: near Augsburg, Germany

PostPosted: Thu Aug 16, 2018 2:30 pm    Post subject: Reply with quote

How many MB for KDE start is loaded into RAM ?
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21346
Location: here

PostPosted: Thu Aug 16, 2018 3:02 pm    Post subject: Reply with quote

Probably related to this bug.
After downloading haveged package and add it to default runlevel, sddm work again fast
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Thu Aug 16, 2018 3:04 pm    Post subject: Reply with quote

Keruskerfuerst wrote:
How many MB for KDE start is loaded into RAM ?


I don't know exactly what you mean by that. How do I check it?

During the (very long) startup, only 200 MB out of 8 GB RAM are used. CPU usage is also low.
It feels like the system is waiting; maybe getting a timeout after 30 seconds. Can't see any timeouts
in the log files though.

Thanks,

Spacebug
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Thu Aug 16, 2018 3:17 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Probably related to this bug.
After downloading haveged package and add it to default runlevel, sddm work again fast


Did not solve the problem, but thanks for the suggestion.

Actually, sddm starts up very fast. The problem is the period after login in sddm and the
initialization of kde (startkde).

Thanks, Spacebug
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21346
Location: here

PostPosted: Thu Aug 16, 2018 3:21 pm    Post subject: Reply with quote

You tried with a new user to see if the problem are configuration file in home directory?
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Thu Aug 16, 2018 3:37 pm    Post subject: Reply with quote

fedeliallalinea wrote:
You tried with a new user to see if the problem are configuration file in home directory?

Yes. Same problem with a new user.

Thanks, Spacebug
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Thu Aug 16, 2018 4:37 pm    Post subject: Reply with quote

Got the same problem here.
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1635
Location: United Kingdom

PostPosted: Thu Aug 16, 2018 5:08 pm    Post subject: Reply with quote

I don't think the longer delay for the Plasma Desktop to appear is due to SDDM, because I have noticed a longer delay after I login via LightDM on my Clevo W230SS laptop running Gentoo Stable. I have not yet looked into it, but a longer delay was immediately noticeable. I have also just updated my Compal NBLB2 laptop, running Gentoo Testing and SDDM rather than LightDM, but have not yet rebooted, so I'll check that soon to see if there is also a noticeable increase in the time for the Plasma Desktop to appear after logging in.
_________________
Clevo W230SS: amd64 OpenRC elogind nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64 OpenRC elogind xf86-video-ati. Dual boot Win 7 Pro 64-bit.
KDE on both.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
Keruskerfuerst
Advocate
Advocate


Joined: 01 Feb 2006
Posts: 2288
Location: near Augsburg, Germany

PostPosted: Thu Aug 16, 2018 5:23 pm    Post subject: Reply with quote

How many MB for KDE start is loaded into RAM ?

I don't know exactly what you mean by that. How do I check it?

How many program code (measured in Mega Byte) is loaded into RAM?
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Thu Aug 16, 2018 7:31 pm    Post subject: Reply with quote

Keruskerfuerst wrote:
How many MB for KDE start is loaded into RAM ?

I don't know exactly what you mean by that. How do I check it?

How many program code (measured in Mega Byte) is loaded into RAM?


I can monitor the startup interval with top. During the long wait, I see three processes

plasmashell
kwin_x11
krunner

using 90-100% of cpu time and 0.5-0.7 of the memory. I would like to know what they
are doing for 40 odd seconds, but apart from studying the xorg-session.log file (which
doesn't give me enough clues) how can I do that?
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Fri Aug 17, 2018 8:34 am    Post subject: Reply with quote

The slow startup of KDE is a problem on my laptop with SSD drive. I have now updated my
desktop computer so that ts runs the same version of everything as my laptop.
Interestingly, my desktop does not seem to slow down when loading KDE. Of course, with a
HDD it was always much slower to begin with, but now it is actually a bit faster.

What happened in the last update to make my laptop with SSD so slow starting KDE?
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Fri Aug 17, 2018 6:13 pm    Post subject: Reply with quote

Another observation: When I first log in, the splash screen doesn't appear (and it takes forever).
If I afterwards log out, a subsequent login is fast and the splash screen does appear!

I tried to disable the splash screen, but that didn't solve the problem with long initial startup time.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13509

PostPosted: Fri Aug 17, 2018 11:49 pm    Post subject: Reply with quote

What did you change in the update that introduced the problem? What packages were updated to new versions? Were any packages reconfigured? What kernel version were you using when it was fast? What kernel version are you using now that it is slow?
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Sat Aug 18, 2018 5:52 pm    Post subject: Reply with quote

I don't want to switch to Gnome 8O :lol:
Back to top
View user's profile Send private message
saderror256
n00b
n00b


Joined: 26 Jul 2018
Posts: 13
Location: Current Directory

PostPosted: Sun Aug 19, 2018 2:10 am    Post subject: Reply with quote

have you tried something other than sddm, ive had many issues and sddm is commonly the cause

EDIT: or, it might be a bug, by looking at it, the best option if its possible is just roll back temporarily, better cross your fingers and hope its in your cache :lol:
_________________
FreeBSD user, but still uses and loves himself some Gentoo!

I wont judge you based on what you use, newbie or inexperienced, you are still amazing for being here B)
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Sun Aug 19, 2018 3:03 am    Post subject: Reply with quote

Trying LXDM - same problem. So it is probably not related to SDDM.
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Sun Aug 19, 2018 3:20 pm    Post subject: Reply with quote

Lightdm works normally bur I just can't get it to autologin properly.
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Tue Aug 21, 2018 4:51 am    Post subject: Reply with quote

Got the Lightdm autologin working now. But exprerienced a slow Plasma start up again.

Installing sys-apps/haveged like recommended in this thread helped.

https://forums.gentoo.org/viewtopic-t-1083242-highlight-autologin.html?sid=28f55a3340448d35c5352d2e983d2801

Everything back to normal now. Perhaps that is a solution for SDDM as well.
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Wed Aug 22, 2018 4:00 am    Post subject: Reply with quote

Works fine for SDDM too.
Back to top
View user's profile Send private message
Spacebug
n00b
n00b


Joined: 04 Jan 2009
Posts: 18
Location: Germany

PostPosted: Fri Aug 24, 2018 8:45 pm    Post subject: Reply with quote

The problem is gone :)

Sorry to say, I have no idea why. I booted the computer after being away for a week, and now
everything works. No delay anymore.

I did at some point install haveged. Although it didn't help immediately, I can think of no other reason
what could have solved the problem.

From my side, I consider the problem solved.

Thanks everyone!
Back to top
View user's profile Send private message
Tolstoi
l33t
l33t


Joined: 20 May 2004
Posts: 678

PostPosted: Sun Aug 26, 2018 9:05 am    Post subject: Reply with quote

I didn't have haveged installed and I added it to the boot runlevel as the other post suggests. Then everything went on fine.
Back to top
View user's profile Send private message
archenroot
Apprentice
Apprentice


Joined: 13 Dec 2011
Posts: 197
Location: Lake Macha, Czech republic

PostPosted: Wed Jan 23, 2019 5:21 am    Post subject: Reply with quote

Thanks I found this thread :-), facing same issue from October, but used to take coffee every morning during plasma desktop startup (autologin) with SDDM.

Just to describe my observations:
1. SDDM looks as autolog super fast
2. Then for some seconds pure black screen appears
3. For some other period of time plasma loading indicator (white circle circulating) appears

2 and 3 taking around 1-2 minutes....

Going to test installation of haveged.

I am not sure if SDDM requires entropy as LightDM, but this is interesting:
http://lists-archives.com/debian-user/3720747-lightdm-testing-long-waiting-time-after-login.html
_________________
Emperor wants to control outer space Yoda wants to explore inner space that's the fundamental difference between good and bad sides of the Force
Back to top
View user's profile Send private message
archenroot
Apprentice
Apprentice


Joined: 13 Dec 2011
Posts: 197
Location: Lake Macha, Czech republic

PostPosted: Wed Jan 23, 2019 10:53 am    Post subject: Reply with quote

In my case installation of new package haveged and put to autostart didn't solved the issue.
_________________
Emperor wants to control outer space Yoda wants to explore inner space that's the fundamental difference between good and bad sides of the Force
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Wed Jan 23, 2019 10:56 am    Post subject: Reply with quote

If sddm starts up fast, then any entropy related issue is off the table. This delay sounds more like a timeout (like dbus).
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum