[KLUG Members] Re: Suse thread-local support error after update

[John Pesce]

On Mon, 2004-05-17 at 17:04, Jeremy Leonard wrote:
> I see in YOU it allows you to re-apply all patches. Have you tried this?
> Maybe something became corrupt during the download.
> 

I starting thinking yesterday afternoon that somehow the Suse updates
went wacko on my system. It seemed to be permission problems dealing
with X apps. I then thought of the NVIDIA drivers. I reinstalled them
after the kernel update and it still didn't work. I reinstalled the
kernel and the NVIDIA drivers and still nothing. 
I then dis-reguarded the warnings and manually installed the NVIDIA
drivers and everything worked again.
Go figure.

Thanks all.   


> On Mon, 2004-05-17 at 13:56, John Pesce wrote: 
> > On Sat, 2004-05-15 at 00:31, somercet@core.com wrote:
> > > <boggle> Wow, fascinating set of symptoms.
> > 
> > Truly. logging in as root produces no errors.
> > Only users get errors.
> > 
> > > > Dumb question, but did you reboot after the update?
> > 
> > For sanity I reboot once more with the same effects.
> > 
> > 
> > > > > This is weird. I just ran Yast2 under Suse 9.0 and it included a
> > > > > kernel update.
> > > 
> > > I'm guessing this all worked previously. Do you have more updates to
> > > install?
> > 
> > Suse 9.0 is now fully updated. Everything worked prior to this last
> > update set.
> > 
> > > > > I can login as root just fine under KDM.
> > > > > 
> > > > > If I try to login as a user now under KDM I get a dialog that
> > > > > kdeinit could not start. Check your configuration.
> > > 
> > > class tree.) Try:
> > > 
> > > ls -l `which kdeinit`
> > > 
> > > and try:
> > > 
> > > ldd `which kdeinit`
> > > 
> > > as root and as a user, and see if they differ.
> > > 
> > 
> > No differences.
> > 
> > > > > If I login as a user remotely and try and run an X app like yast2 I
> > > > > get the error:
> > > > > 
> > > > > cannot set up thread-local storage: kernel too old for thread-local
> > > > > storage support
> > > 
> > > Does remote login as a generic user work until you run something like
> > > yast2?
> > 
> > Yes generic user logins work fine on console or remotely. I only get the
> > error when I try to login to KDM now. I can now remote login as a
> > generic user and run an X app, though I thought I couldn't before...
> > Interesting note: I logged into KDM as root just now and then su - user
> > and I was able to open an X app without an error.
> > 
> > > 2.6 has thread-local storage. Is your kernel a heavily patched 2.4 with
> > > NPTL, or 2.6? I didn't see these errors with 2.6 and Debian KDE 3.x.
> > 
> > This is not patched by me. I installed the latest Suse kernel update,
> > which is kernel-2.4.21-215-smp4G. I have another computer that was
> > updated the same, but it doesn't have a problem.
> >  
> > 
> > > Also read /var/log/XFree86.?.log and ~/.xsession-errors.
> > 
> > I don't see any errors in XFree86.0.log when a user logs in.
> > 
> > 
> > ~generic/.xsession-errors contains the errors
> > 
> > cannot set up thread-local storage: kernel too old for thread-local
> > storage support.
> > 
> > startkde: Could not start kdeinit. Check your installation.
> > 
> > 
> > 
> > > As root, log into KDM and open a terminal:
> > > 
> > > cat .Xauthority > /home/$USER/.Xauthority
> > > 
> > > then `su - $USER` and try running apps from there.
> > 
> > see. above I could run Xapps sued to a generic user before cating
> > .Xauthority.
> > 
> > 
> > It is weird.  It is like a permission problem prevents a user from
> > logging into KDM to do something.
> > 
> > 
> > _______________________________________________
> > Members mailing list
> > Members@kalamazoolinux.org
> > 
> > 
> 
> _______________________________________________
> Members mailing list
> Members@kalamazoolinux.org
>