** Changed in: gnome-screensaver
Importance: Unknown = Critical
--
gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no logout has happened
https://bugs.launchpad.net/bugs/76632
You received this bug notification because you are a member
This is happening for me on Intrepid Ibex (see bug marked duplicate).
This particular machine was upgraded from Hardy Heron, which experienced
the described problem at a greater frequency.
Following a request from William Jon McCann (comment #24 above), I
downloaded the sourcecode and tried to
sbin/unix_chkpwd is setGID shadow, but /etc/shadow was owned by root.root
In my case, /etc/shadow had read permissions only for root, and not for the
group, and so unix_chkpwd could not check the password. This is now working
correctly after I did:
sudo chmod 440 /etc/shadow
--
gdm should add
not a gdm bug
** Changed in: gdm (Ubuntu)
Status: Confirmed = Rejected
--
gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no logout has happened
https://bugs.launchpad.net/bugs/76632
You received this bug notification because you
the gnome-screensaver code has been updated to work with the change
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Fix Released
--
gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no
I am running Feisty up to date and cannot log back in after locking the
screen, although logging in as a new user works. Killing gnome-
screensaver works as a work-around.
/var/log/auth.log says:
Mar 29 22:42:54 new unix_chkpwd[9765]: check pass; user unknown
Mar 29 22:42:54 new
My problem with Feisty was as posted here:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/97569
/sbin/unix_chkpwd is setGID shadow, but /etc/shadow was owned by
root.root
Fixed by
sudo chgrp shadow /etc/shadow
--
gdm should add symlink to /var/run/gdm_socket during ugrades to
Hi,
I have the same problem with a freshly updated Festy.
--
gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no logout has happened
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Problem occured with fresh edgy install after initial update. I could
reproduce the behavior with xlockmore too.
--
gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no logout has happened
https://launchpad.net/bugs/76632
--
desktop-bugs
** Summary changed:
- screen does not unlock after locking
+ gdm should add symlink to /var/run/gdm_socket during ugrades to prevnet the
sceensaver from hanging if no logout has happened
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: gnome-screensaver = gdm
Assignee: Oliver
There is a feisty to feisty upgrade problem which will happen for people
who installed a version using /var/run/.gdm_socket, upgraded and restart
gnome-screensaver without restarting gdm. The upgrade from edgy should
work fine since the packages have been patched to look at the edgy
socket
11 matches
Mail list logo
