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