Qt-interest Archive, August 2006
4.2 startup authentication failed
Message 1 in thread
Anyone know why this message comes up in 4.2 and how to fix it
or if it means anything?
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Running Qt4.2 8-26 release Fedora Core 5
Jeff
--
[ signature omitted ]
Message 2 in thread
Hi,
> Anyone know why this message comes up in 4.2 and how to fix it or if
> it means anything?
>
> Qt: Session management error: Authentication Rejected, reason : None
> of the authentication protocols specified are supported and
> host-based authentication failed
>
> Running Qt4.2 8-26 release Fedora Core 5
Are you displaying the application locally, on the very same box it runs
on? Are you running the application as a different user? This error has
to do with session management (libSM library) but nothing related to
libSL has changed recently as far as I can see.
I have no problem running the current Qt 4.2 branch on Fedora core 5.
--
[ signature omitted ]
Message 3 in thread
> Are you displaying the application locally, on the very same box it runs
> on?
Yes, same box, same user as I compiled it as, myself.
snapshot was compiled as root, which is normal, correct?
Jeff
--
[ signature omitted ]
Message 4 in thread
Hi,
> Yes, same box, same user as I compiled it as, myself.
Actually I was not asking if it's the same box/account used to compile
the application. What I was asking for is whether you're displaying the
application locally or remotely. What the output of:
echo $DISPLAY
uname -n
Have you tried to log out, then log in, then run the application again?
> snapshot was compiled as root, which is normal, correct?
The root account is normally used for administration tasks only.
--
[ signature omitted ]
Message 5 in thread
> echo $DISPLAY
> uname -n
:0.0
fedora
Im running it on the local machine its on, nothing remote.
> Have you tried to log out, then log in, then run the application again?
No I havent, too many screens and windows in use today. Ill
try it another day. It doesnt appear to be affecting anything,
it all works, just wondered about the message.
If logging out/in doesnt clear it up, Ill let you know later.
Thanks,
Jeff
--
[ signature omitted ]
Message 6 in thread
Hi,
>> Have you tried to log out, then log in, then run the application again?
>
> No I havent, too many screens and windows in use today. Ill
> try it another day. It doesnt appear to be affecting anything,
> it all works, just wondered about the message.
Ah, that could be the problem. I've already seen Fedora workstations
(with Nvidia drivers installed) "forget" about the current session,
apprently after a few days without logging out or after launching too
many applications (but not with similar error messages as far as I can
recall). I never bothered to investigate, logging out/in fixed the
problem for me.
> If logging out/in doesnt clear it up, Ill let you know later.
--
[ signature omitted ]
Message 7 in thread
Ok thanks Dimitri...as long as it isnt affecting the
app Im ok with it.
Jeff
--
[ signature omitted ]
