trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: May 2015

Re: [trinity-users] Installed R14.0.1 but no desktop

From: Greg Madden <gomadtroll@...>
Date: Sun, 17 May 2015 18:21:19 -0800

On Sunday 17 May 2015 05:11:20 am Lisi Reisz wrote:
> On Sunday 17 May 2015 13:54:02 andre_debian@... wrote:
> > On Saturday 16 May 2015 10:19:10 Rolf Schmidt wrote:
> > > Instead start kdesktop try: /etc/init.d/tde-trinity restart.
> > > It works here
> > > Rolf
> >
> > Hello,
> >
> > "tde-trinity" doesn't exist in "/etc/init.d",
> > but "/etc/init.d/tdm-trinity".
> >
> > > You mean when you killall kdesktop it does not proceed into
> > > half-working session? Then you probably have a different bug...
> > >
> > > Um, no. The bug everyone is having is a deadlock at kdesktop start.
> > > While various methods of restarting tdm may or may not help depending
> > > on unknown factors (Slavek have not yet found why the lock is happening
> > > in the first place), killall -9 kdesktop should work in 100% cases (It
> > > should get you a working kicker without desktop functionality). If in
> > > your case killing kdesktop doesnt work it means it hangs in a
> > > completely different place.
> >
> > My booting bug logging stopping is quite the same as the others.
> > It's not because a solution doesn't work that the bug could be
> > differrent.
> >
> > Do CTRL-ALT-BACKSPACE => back to the tdm-trinity or text console,
> > is an option that I have enabled.
> >
> > 1] CTRL-ALT-BACKSPACE, logging again,
> > or
> > 2] killall Desktop,
> > or
> > 3] waiting the password disappears,
> >
> > doesn't not solve the problem of the logging aborting,
> > or sometimes, about one of ten tentatives,
> > it's not acceptable.
>
> We're probably onto English not first language territory again but...
>
> André, there is a bug.  You have been told which workarounds work for the
> bug. The rest of us are using the workarounds for now and the developers
> are working on finding a solution.  When they find a solution we shall have
> the patch and we shall not have the problem.  Until then we continue to use
> the workarounds.
>
> That is the situation.  If it is not acceptable, don't accept it.  But
> either do something about it  yourself or don't.  There is no point in
> going on and on about it.  We note that you find it unacceptable.  So what
> then??
>
> That is the situation.  Accept it or don't.  Those are the alternatives.
>
> Lisi

One more case to round out solutions, my main install is my workstation, it 
runs all the time. 

I also do not use 'kdesktop_lock', it does not  work with my Nvidia card 
drivers from Nvidia ...maybe video related?

-- 

Greg M