Hi -- just upgraded to 15.04 from 14.10. Been painful, but i've tamed most of the issues, and this last thing is proving challenging; if anyone feels like slogging through this with me i would be much obliged! Been banging my head on it all day and am just about at wits' end.
sddm takes a long time for me to log in; meaning, the time from hitting "enter" on the password to when the desktop appears. What used to be a 1-second-or-so operation now takes 15-20 seconds. Tried to google a solution, came up empty. (I thought to try lightdm. Had a ton of trouble getting it to work; long story, gave up on that for now. Seems like it's not being actively developed/fixed.)
I have a script that does a ps every 0.5 seconds and does a diff between the result and the previous ps, so I can watch what processes are starting and stopping. (The processes are logged in between timestamps every 0.5 seconds. It's possible that processes start and exit in less than 0.5 seconds and within a single window, and thus don't appear in the log file.)
There is a clear section of about 17 seconds where nothing is starting or stopping. I was hoping that the processes that start just before this period, or end just after, might offer some clues, but nothing clear. The most common thing is a krunner process/thread starts, then 17 seconds go by, then another krunner process/thread, then plasmashell, then a few seconds, then things progress normally. But i'm not sure if those processes really deserve the blame.
E.g. backlighthelper was running, 10 seconds would go by, then it would exit. I disabled it, and then kdeconnectd appeared to be the cause. Uninstalled KDE Connect, and now this, etc. I wonder if the pause is unrelated to the particular processes, and maybe something to do with a video driver or whatever. During the long period, the screens change once or twice (background image shifts, etc., almost like mode setting is going on.) I have multiple monitors going, incidentally.
I also note that if I switch to vterms while the login is happening, it seems to "pause" it; as if sddm (or whatever is controlling the process) has to wait for me to go back to the graphical vterm to continue it's work and/or waiting.
Anyway, that's what I have so far. Gonna try renaming .kde. If anyone has heard of this or has tips on what to check next, I'd be much obliged. I'd also be happy to try a different display manager, if there is one that works and doesn't require installing an entire desktop with it. :-)
Thanks!
-c
sddm takes a long time for me to log in; meaning, the time from hitting "enter" on the password to when the desktop appears. What used to be a 1-second-or-so operation now takes 15-20 seconds. Tried to google a solution, came up empty. (I thought to try lightdm. Had a ton of trouble getting it to work; long story, gave up on that for now. Seems like it's not being actively developed/fixed.)
I have a script that does a ps every 0.5 seconds and does a diff between the result and the previous ps, so I can watch what processes are starting and stopping. (The processes are logged in between timestamps every 0.5 seconds. It's possible that processes start and exit in less than 0.5 seconds and within a single window, and thus don't appear in the log file.)
There is a clear section of about 17 seconds where nothing is starting or stopping. I was hoping that the processes that start just before this period, or end just after, might offer some clues, but nothing clear. The most common thing is a krunner process/thread starts, then 17 seconds go by, then another krunner process/thread, then plasmashell, then a few seconds, then things progress normally. But i'm not sure if those processes really deserve the blame.
E.g. backlighthelper was running, 10 seconds would go by, then it would exit. I disabled it, and then kdeconnectd appeared to be the cause. Uninstalled KDE Connect, and now this, etc. I wonder if the pause is unrelated to the particular processes, and maybe something to do with a video driver or whatever. During the long period, the screens change once or twice (background image shifts, etc., almost like mode setting is going on.) I have multiple monitors going, incidentally.
I also note that if I switch to vterms while the login is happening, it seems to "pause" it; as if sddm (or whatever is controlling the process) has to wait for me to go back to the graphical vterm to continue it's work and/or waiting.
Anyway, that's what I have so far. Gonna try renaming .kde. If anyone has heard of this or has tips on what to check next, I'd be much obliged. I'd also be happy to try a different display manager, if there is one that works and doesn't require installing an entire desktop with it. :-)
Thanks!
-c
Comment