trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: April 2015

Re: [trinity-users] TDE and kernel 3.16

From: Baron <baron@...>
Date: Wed, 29 Apr 2015 23:50:24 +0100

On Wednesday 29 April 2015 23:36:19 Nick Koretsky wrote:
> On Wed, 29 Apr 2015 17:36:00 +0100
>
> Baron <baron@...> wrote:
> > > > > Ironically right after writing previous message i
> > > > > encountered this behavior on the first boot into jessie on
> > > > > the next machine i updated. But it was fixed by restarting
> > > > > tdm-trinity.
> > > >
> > > > Unfortunately that hasn't worked for me :-)
> > > >
> > > > What I find interesting is having to wait and then reentering
> > > > my password after which everything works Ok.  Even root
> > > > behaves the same.  There is something that has to complete
> > > > before I / you can login.
> > >
> > > Yep. This machine got stuck in this state few more times while
> > > i was frantically rebooting while making my audio and video
> > > work :) And it does seems like this happens if you try to login
> > > too fast. I dont think it hanged even once if i waited on login
> > > screen for a minute or more, but when i typed password
> > > immediately it has a decent chance to stuck.
> > >
> > > Still, this only happens on one out of four PCs i updated to
> > > jessie since release. And no matter how i look i cant
> > > comprehend whats different in this one.
> >
> > I wonder if its hardware related.  I upgraded a friends machine
> > and he doesn't have this problem.  His machine, mother board wise
> > is AMD based, while mine is intel based.  We both have mother
> > boards with built in graphic cards and both have the same Nvidia
> > external AGP graphic cards.  But I think that there are to many
> > differences to be able to speculate.
>
> It doesnt look like its hardware related. All my machines have AMD
> CPU's. The one which exhibits this have AMD video, but one of
> others have AMD video too. This behavior happens both with radeon
> and fglrx drivers. Also this is not systemd related as someone
> suggested early because i left this one on sysv-init.
>
> Also i tried to monitors what happens when it gets stuck -
> apparently at one point in tde startup process two kdesktop process
> started, one finishes almost instantly and other goes to sleep.
> When it stuck the second process doesnt finish and just sits here.
> If you kill it (the one which is not in Sl state) tde stratup would
> proceeds into half-functioning tde session (kicker related stuff
> works, but desktop is not loaded and background remains from
> startup. Apparently some other services do not start too because
> its complains when you try to logout)

Apart from not discovering the second desktop process, going through 
another tty sometimes let me into this half functioning state.  It 
was completly by accident, being called away after putting in my 
password that I found that the password field was now blank and 
putting my password in again and pressing enter or the login button 
that TDE started normally.


-- 
Best Regards:
            Baron