From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.cendio.se/pipermail/thinlinc-technical/attachments/20120202/ff9db09b/attachment.html From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Shilpa.Shilpa at shell.com Thu Feb 2 09:19:06 2012 From: Shilpa.Shilpa at shell.com (Shilpa.Shilpa at shell.com) Date: Thu, 2 Feb 2012 16:19:06 +0800 Subject: [Thinlinc-technical] problem with gnomedesktop Message-ID: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> I am using thinlinc server on a linux machine(redhat 5.7). Once I login to it using thinlinc client in windows,everything goes fine. But if I do "lock screen",and when trying to unlock,its not able to login. It will always asks the password,but unlocking is not happening. Below is the content of /var/log/secure Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) Feb 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password Please help me in this regard. Thanks & Regards Shilpa -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Thu Feb 2 09:45:57 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 09:45:57 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> Message-ID: Hi! The 3 lines you sent looks quite OK, I think. The first one basically tells you that the user is not found in the local account db, but then it moves on to Winbind (ie AD). Can you provide a few more lines of output? Also, does it work on the console, ie have you verified that the problem only occurs in TL sessions? There's a similar report here: https://bugzilla.samba.org/show_bug.cgi?id=6103 But apparently that only happens when the network goes down. Another thing to try is to disable SELinux. This can be done with "setenforce 0". Btw, I assume that you really want to run a screensaver in the TL session? In that case, make sure you use a "blank" one, to avoid consuming CPU power in disconnected sessions. The typical recommendation however is to disable screensavers in thin sessions. Instead, you can configured ThinLinc to disconnect inactive sessions. Best regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > > I am using thinlinc server on a linux machine(redhat 5.7). > > Once I login to it using thinlinc client in windows,everything goes fine. > > But if I do ?lock screen?,and when trying to unlock,its not able to login. > > It will always asks the password,but unlocking is not happening. > > ? > > Below is the content of /var/log/secure > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; > logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password > (0x00000390) > > Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a > password > > ? > > ? > > Please help me in this regard. > > ? > > Thanks & Regards > > Shilpa > > ? > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 10:42:26 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 10:42:26 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: The log entries doesn't really indicate why the unlock is not successful, strange. To configure TL to disconnect inactive sessions, you can use the IdleTimeout option for Xvnc: IdleTimeout - The number of seconds after which an idle VNC connection will be dropped (zero means no timeout) (default=0) So for example, you can add -IdleTimeout=120 to the xserver_args parameter in vsmagent.hconf. Then, restart the vsmagent service and login again. Regards, Peter On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > Selinux status is disabled only for us . > /var/log/secure looks like this > > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:52:51 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:52:58 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost= user=ASIA-PAC\girish.vasu-b > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390) > Feb 2 03:53:33 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password > Feb 2 03:53:37 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'ASIA-PAC\girish.vasu-b' granted access > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session opened for user root by (uid=0) > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26692]: pam_unix(crond:session): session closed for user root > Feb 2 03:55:01 ZEU-V-913BC0D9 crond[26694]: pam_unix(crond:session): session closed for user root > > Can you please let us know how we can configure thinlinc to disconnect inactive sessions? > > -----Original Message----- > From: Peter ?strand [mailto:astrand at cendio.se] > Sent: Thursday, February 02, 2012 2:16 PM > To: Shilpa, Shilpa SHLOFF-WIPRO > Cc: thinlinc-technical at lists.cendio.se > Subject: Re: [Thinlinc-technical] problem with gnomedesktop > > > Hi! The 3 lines you sent looks quite OK, I think. The first one basically > tells you that the user is not found in the local account db, but then it > moves on to Winbind (ie AD). Can you provide a few more lines of output? > > Also, does it work on the console, ie have you verified that the problem > only occurs in TL sessions? > > There's a similar report here: > https://bugzilla.samba.org/show_bug.cgi?id=6103 > But apparently that only happens when the network goes down. > > Another thing to try is to disable SELinux. This can be done with > "setenforce 0". > > Btw, I assume that you really want to run a screensaver in the TL session? > In that case, make sure you use a "blank" one, to avoid consuming CPU > power in disconnected sessions. The typical recommendation however is to > disable screensavers in thin sessions. Instead, you can configured > ThinLinc to disconnect inactive sessions. > > > Best regards, > Peter > > On Thu, 2 Feb 2012, Shilpa.Shilpa at shell.com wrote: > >> >> I am using thinlinc server on a linux machine(redhat 5.7). >> >> Once I login to it using thinlinc client in windows,everything goes fine. >> >> But if I do ?lock screen?,and when trying to unlock,its not able to login. >> >> It will always asks the password,but unlocking is not happening. >> >> ? >> >> Below is the content of /var/log/secure >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; >> logname= uid=16777220 euid=16777220 tty=:1.0 ruser= rhost=? user=ASIA-PAC\girish.vasu-b >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password >> (0x00000390) >> >> Feb? 1 06:07:01 ZEU-V-913BC0D9 gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a >> password >> >> ? >> >> ? >> >> Please help me in this regard. >> >> ? >> >> Thanks & Regards >> >> Shilpa >> >> ? >> >> >> > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Thu Feb 2 11:27:36 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Thu, 2 Feb 2012 11:27:36 +0100 (CET) Subject: [Thinlinc-technical] problem with gnomedesktop In-Reply-To: References: <8E072861B112464CA0F10CD98E20FB0103622A1B@cbj-s-02341.asia-pac.shell.com> <8E072861B112464CA0F10CD98E20FB0103622A54@cbj-s-02341.asia-pac.shell.com> Message-ID: I should perhaps add that the -IdleTimeout option is currently not documented in our Administrators Guide. We will fix this in the upcoming release. The documentation can be found in the man page /opt/thinlinc/share/man/man1/Xvnc.1 though. Regards, Peter On Thu, 2 Feb 2012, Peter ?strand wrote: > > The log entries doesn't really indicate why the unlock is not successful, > strange. > > To configure TL to disconnect inactive sessions, you can use the IdleTimeout > option for Xvnc: > > IdleTimeout - The number of seconds after which an idle VNC connection > will be dropped (zero means no timeout) (default=0) > > So for example, you can add -IdleTimeout=120 to the xserver_args parameter in > vsmagent.hconf. Then, restart the vsmagent service and login again. > > Regards, > Peter --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Mon Feb 6 16:30:43 2012 From: astrand at cendio.se (=?ISO-8859-15?Q?Peter_=C5strand?=) Date: Mon, 6 Feb 2012 16:30:43 +0100 (CET) Subject: [Thinlinc-technical] Wish List for Future Fixes and Features Message-ID: Hi all. We are planning the next release of ThinLinc. For the most part, we have already decided what we will focus on: an improved installer, better Ubuntu compatibility, and few bugfixes. This will be a relatively short development cycle, so there is not much room for additional fixes and features. Nevertheless, we would like to ask you what your wish list looks like? Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00