A Locked session can not be unlocked

[Carlos Sevcik]

When I lock a session my password is useless to unlock it

[Sebastien Bacher (seb128)]

Thanks for your bug. What version of Ubuntu do you use. Do you use xscreensaver or gnome-screensaver? Are you sure you type your password correctly?

[Carlos Sevcik (carlos-sevcik-s)]

Hi Sebastian,

    I am using Ubuntu 5.10, both the KDE and xscreensavers are installed
I mostly use the Open GL ones, Antinspect is my favorite. Yes, I am an
sure I type the password OK. I have been using Linux for over 5 years
(Red Hat or Fedora with Gnome before switching to Ubuntu and KDE) and
used Solaris since 1987 before switching to linux.

Many thatnks for your interest and fine job with KDE

Carlos

Sebastien Bacher wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/32074
>
> Task: ubuntu
> Status: Unconfirmed => Needs Info
>
> Comment:
> Thanks for your bug. What version of Ubuntu do you use. Do you use
> xscreensaver or gnome-screensaver? Are you sure you type your password
> correctly?
>
>

[nanoyow (denommees)]

Whenever xscreensaver starts, X freezes. Only thing that works is reset. This is all straight out of the box. I did not modify any settings from the fresh install. I was able to disable the screesaver in the less than 2 seconds before it freezes using the dialog window to select which theme to use. This is reproducible 100% of the time. System is rock solid without screensaver.

I am using Ubuntu 5.10
AMD Athlon 2200
ATI Radeon R200 QM (Radeon 9100)

System has been updated to latest for all packages using synaptic

[mexlinux (mcanedo)]

Hi:
I have kubuntu 3.5 I have the same problem.
I only notices afeter installing xscreen saver, the first time I suspended when resuming xscreensaver askd for password, and it was impossible to unlock. I had to kill X.

Then I don't use xscreensaver anymore, but If I lock the session from kde I can not log back in.

[Carlos Sevcik (carlos-sevcik-s)]

Hi,

Thanks for your message. If the bug is associated with the screensaver
it is not xscreensaver specific. I uninstalled the all xscreensaver
packages (my favourits) and left only the KDE ones and the bug persists
:-( . When I reported the bug I had KDE 3.4 (the original one with
Kubuntu), yesterday I updated to 3.5 (as indicated in the Kubuntu site)
and it makes no difference :-( .

mexlinux wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/32074
>
> Comment:
> Hi:
> I have kubuntu 3.5 I have the same problem.
> I only notices afeter installing xscreen saver, the first time I suspended when resuming xscreensaver askd for password, and it was impossible to unlock. I had to kill X.
>
> Then I don't use xscreensaver anymore, but If I lock the session from
> kde I can not log back in.
>
>

[Luka Renko (lure)]

This might be a duplicate of bug 26175.

Please check your /etc/shadow file bt doing the following command:
ls -l /etc/shadow

You should get something like this:
-rw-r----- 1 root shadow 811 Mar 1 21:50 /etc/shadow

If it is not owned by root:shadow, you should fix it manually (sudo chown root:shadow /etc/shadow).
If you are runing KDE and have used Users config in System Settings, then it was most probably caused by that bug in kde-guidance.

[Carlos Sevcik (carlos-sevcik-s)]

If I don't change /etc/shadow it should not change, in any case here it is:

*ls -ls /etc/shadow
4 -rw-r----- 1 root root 846 2006-02-14 21:39 /etc/shadow
*
so its root:root. Changing it to root:shadow makes no difference in my case.

I just checked another machine with Fedora Core 4 and /etc/shadow is
also root:root. Since my times (more than 10 years ago) working under
Solaris /etc/shadow only belongs to root. My security handbook says
/etc/shadow should belong to root and *only* to root.

The problem started after the upgrade from the original KDE in Kubuntu
to 3.5.1. Also it started in both my office workstation and my laptop at
the same time (after upgrading Kubuntu to 3.5.1). The bug you mention
relates to being unable to unlock a locked session, this happened to me
from the very moment I installed of Kubuntu (see my report 32074) so I
don't think there is a connection with any of this two previous bugs.

regards

Carlos

Luka Renko wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/32074
>
> Comment:
> This might be a duplicate of bug 26175.
>
> Please check your /etc/shadow file bt doing the following command:
> ls -l /etc/shadow
>
> You should get something like this:
> -rw-r----- 1 root shadow 811 Mar 1 21:50 /etc/shadow
>
> If it is not owned by root:shadow, you should fix it manually (sudo chown root:shadow /etc/shadow).
> If you are runing KDE and have used Users config in System Settings, then it was most probably caused by that bug in kde-guidance.
>
>

[mexlinux (mcanedo)]

Thanks
sudo chown root:shadow /etc/shadow
worked for me.
and yes, I have used Users config in System Settings KDE

[Carlos Sevcik (carlos-sevcik-s)]

I agree sudo chown root:shadow /etc/shadow solves the session lock
problem. In my earalier post was thinking in the crash of konkeror while
renaming files which I just reported. I wonder however if the
root:shadow ownership of /etc/shadows creates any wulnerabilities since
/etc/shadows is very critical for security.

carlos

mexlinux wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/32074
>
> Comment:
> Thanks
> sudo chown root:shadow /etc/shadow
> worked for me.
> and yes, I have used Users config in System Settings KDE
>
>

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]