I'm running Kubuntu but have seen the black screen thing once or twice about a month ago. It hasn't returned for awhile.
The problem I see about 1 out of every 3 days is ksplashqml crashes when first logging in. It doesn't seem to cause any long=term problems but it's frustrating. That's been going on for about a month, maybe a bit longer but it corresponded to a full upgrade awhile back. On Wed, Mar 4, 2020 at 8:49 AM Jack <[email protected]> wrote: > On 3/4/20 8:41 AM, Dale wrote: > > All the timing of the above problems are very similar. I believe they > > have the same cause. When I finished my updates, I logged out, went to > > boot runlevel, used checkrestart to make sure everything that needed to > > be restarted was clean, restarted any that weren't and then when back to > > default runlevel. In the past this has always worked fine. Thing is, > > elogind is in the boot runlevel. I'm going to have to get used to > > restarting it manually I guess. Could elogind be the cause of all > > this? Would it be safe to put elogind in the default runlevel? That > > would solve the problem of me forgetting to restart it after upgrades. > > Or would some other service in the boot runlevel start it as a > > dependency anyway?? > > > > When I get to a point where I can logout and back in, I'll test > > restarting elogind to see if it helps. Thing is, I'm not really sure > > what all elogind does but from what little I know, it sounds like a good > > place to start. Thing that confuses me, checkrestart not showing it > > needed to be restarted. It's never failed me before. > > I was recently in a similar position (but not such serious effects) but > discovered that elogind refused to restart. The message was that it > wouldn't start because it was already started, but that implies that it > simply failed to stop, without producing any error message. I didn't > want to fight it any further, so I just rebooted. > > Jack > > >
