KDE 3.5.3 build for Solaris 10

Hi,


great - this is perfect! Thanks a lot.		

However, this kwin issue with the windows positioned fix at
the top border 
still remains unsolved...

I have yet another question to the KDE-solaris community: I
have 3 kinds of 
KDE running under Solaris 10:
 - an old 3.2.3 that I've built myself using SunStudio 8 2
yeard ago
 - Stefan Teleman's 3.4.3
 - and my gccfss build of 3.5.3

Under all these KDEs, I have problems when locking the
screen with the KDE 
screensavers. When trying to unlock the screen, I simply get
the following 
error message:

  "Cannot unlock the session because the
authentication system failed to work;
   you must kill kdesktop_lock (pid ....) manually."

When invoking 'kdesktop_lock --forcelock' manually from
konsole, I see the 
following additional error messages after having killed it:

X Error: Bad Access (attempt to access private resource
denied) 10
  Major opcode: 2
  Minor opcode: 0
  Resource id: 0x98000c
WARNING: DCOPReply<>: cast to 'QStringList' error
WARNING: DCOPReply<>: cast to 'QString' error.

Since
 a) this behavior occurs under all my KDEs, and
 b) the same good old KDE 3.2.3 works fine under Solaris 9,
I don't think that this is a KDE bug. Instead, it's likely
that I have 
something misconfigured under Solaris 10. PAM?

Do you have any ideas?

Greetings from Dortmund

  Heiko


On Friday 07 July 2006 15:42, Bernd Kuhls wrote:
> Heiko Falk wrote:
> > a) The time displayed by e.g. kicker's clock or
korganizer etc. doesn't
> >    treat my timezone correctly. My box is
configured for MEST, but the
> >    KDE tools all use GMT/UTC so that I have an
offset of 2 hours.
> >    Does anybody know how to correct this?
>
> Hi,
>
> have a look at this bug report for the patches needed
on Solaris:
> http:/
/bugs.kde.org/show_bug.cgi?id=114771#c29
>
> Greetings, Bernd
>
> ___________________________________________________
> This message is from the kde-solaris mailing list.
> Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.h
tml.


____________________________________________________________
___________

Dr. Heiko Falk

University of Dortmund
Department of Computer Science 12 (Embedded Systems Group)
Otto-Hahn-Strasse 16, Room E-19

44221 Dortmund
Germany


Phone:  +49 231 755 6124
Fax:    +49 231 755 6116
Mail:   Heiko.Falkudo.edu
WWW:    http://ls12-
www.cs.uni-dortmund.de/~falk
____________________________________________________________
___________
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

Hi,


> Under all these KDEs, I have problems when locking the
screen with the
> KDE screensavers. When trying to unlock the screen, I
simply get the
> following error message:
>
>   "Cannot unlock the session because the
authentication system failed
> to work; you must kill kdesktop_lock (pid ....)
manually."

Do you run kcheckpass as normal user? You usually have to
set the suid bit 
to get this working.

Btw you can check the authentification system more simply by
running
kcheckpass; echo $?
instead of locking the desktop 


Regards
Chris
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

Hi Christopher,


On Thursday 13 July 2006 11:16, Christopher Dietz wrote:
> Hi,
>
> > Under all these KDEs, I have problems when locking
the screen with the
> > KDE screensavers. When trying to unlock the
screen, I simply get the
> > following error message:
> >
> >   "Cannot unlock the session because the
authentication system failed
> > to work; you must kill kdesktop_lock (pid ....)
manually."
>
> Do you run kcheckpass as normal user? You usually have
to set the suid bit
> to get this working.

I think, the permissions of kcheckpass are OK:

-rwsr-xr-x    1 root     bin         28924 Nov  8  2004
kcheckpass*

> Btw you can check the authentification system more
simply by running
> kcheckpass; echo $?
> instead of locking the desktop 

That's cool - that simplifies testing a lot...!			

On my Solaris 10 box, the above line leads to a return value
2 (AuthError):

kcheckpass; echo $?
Password: 
2

On a Solaris 9 machine, I get a return value 0.

I built kcheckpass/kdebase with these options for configure:
--with-shadow --with-rpcauth --with-pam=yes

When installing my KDEs under Solaris 10, I used the
template 
for /etc/pam.conf provided by Stefan Teleman 
(ftp://ftp.kde.org/pub/kde/stable/3.4.3/contrib/Solaris/SUNS
TUDIO10/INSTALLATION/PAM.INSTALL/etc.pam.conf.diff). 
Here, I don't see any entry for kcheckpass. Is this OK?

/etc/rpc and /etc/services also contain entries just for
dcopserver and dcop.

  Heiko

____________________________________________________________
___________

Dr. Heiko Falk

University of Dortmund
Department of Computer Science 12 (Embedded Systems Group)
Otto-Hahn-Strasse 16, Room E-19

44221 Dortmund
Germany


Phone:  +49 231 755 6124
Fax:    +49 231 755 6116
Mail:   Heiko.Falkudo.edu
WWW:    http://ls12-
www.cs.uni-dortmund.de/~falk
____________________________________________________________
___________
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.

Hi,


> I think, the permissions of kcheckpass are OK:
> -rwsr-xr-x    1 root     bin         28924 Nov  8  2004
kcheckpass*

Looks fine to me...


> I built kcheckpass/kdebase with these options for
configure:
> --with-shadow --with-rpcauth --with-pam=yes

I haven't specified those flags at all 


> When installing my KDEs under Solaris 10, I used the
template
> for /etc/pam.conf provided by Stefan Teleman
>
(ftp://ftp.kde.org/pub/kde/stable/3.4.3/contrib/Solaris/SUNS
TUDIO10/INS
>TALLATION/PAM.INSTALL/etc.pam.conf.diff). Here, I don't
see any entry
> for kcheckpass. Is this OK?

The default entry should take care of that, I think. But
again, no kde 
specific changes were necessary for PAM authentification to
work for me. 
Just the usual modifications to get it running with ldap.


Regards
Chris
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  ht
tps://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.h
tml.