I'm still seeing this bug, and others commenting below seem to be too,
so I'll reopen the bug.
** Changed in: gnome-screensaver (Ubuntu)
Status: Fix Released = Confirmed
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
It doesn't work at me too. When I try to log after screen locking, in auth.log
there is:
Feb 19 10:26:08 urzenia unix_chkpwd[22395]: check pass; user unknown
Feb 19 10:26:08 urzenia gnome-screensaver-dialog: (pam_unix) authentication
failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=
Hi MySZ,
I know you said your system is upto date, but just to check what package
is actually installed.
dpkg -l | grep gnome-screensaver
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Jamie, I think your variant is what's referred to above as gnome-
screensaver is not supposed to hang because of this.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Hello daviey,
dpkg return as follow:
ii gnome-screensaver 2.17.7-0ubuntu2
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Martin, if I understand right that means the problem I'm seeing is fixed
upstream now, and will get to the Ubuntu version soon?
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Jamie: It has been fixed upstream in December 2006... I'm pretty sure
that fixed version is already in Ubuntu, but still broken.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I am seeing this bug again with a fresh installed Herd4 fully updated as
of Feb 19th.
gnome-screensaver 2.17.7-0ubuntu3
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Killing off gnome-screensaver, then making this symlink fixed it. I
think there is an error in the last update.
* debian/patches/05_gdm_varrun_fix.patch:
- look for the gdm socket to /tmp/.gdm_socket and then /var/run/gdm_socket
This should be /var/run/.gdm_socket and not
That symlink may well work if you're using GDM. If you start Gnome
without using GDM, though, it still locks up.
Aside: Shouldn't the name of the GDM socket be an environment variable,
passed down from GDM to gnome-screensaver just like all the other
sockets, D-BUS, SSH agent etc...
--
screen
I can confirm it as well. How I solved the problem was I went into
gconf-editor (alt-f2 and enter gconf-editor), the go to apps, then to
gnome-power-manager, and then I disabled lock_on_blank_screen,
lock_on_hibernate, and lock_on_suspend. This disables screen lock, which
is only a shoddy,
** Changed in: gnome-screensaver (upstream)
Status: Unknown = Fix Released
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Confirmed, fix works :D
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Talking to William (upstream developer), i guess he found - and fixed -
the problem. Although gdm socket has changed its place, gnome-
screensaver is not supposed to hang because of this.
The history is here: http://bugzilla.gnome.org/show_bug.cgi?id=407524
--
screen does not unlock after
I'm afraid it is not properly fixed in 2.17.7-0ubuntu2.
When the X session is started from GDM, it probably works. (I've seen
it lockup, but I suspect that was before I picked up 2.17.7-0ubuntu2).
However, when the X session is started using 'startx' (which starts the
X server then runs
gdm changed the location of the socket file, apparently it's hardcoded
in gnome-screensaver, a fix is uploaded and should get into herd4
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Changed status based on comment by Oliver Grawert.
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed = In Progress
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
gnome-screensaver (2.17.7-0ubuntu2) feisty; urgency=low
.
* make sure we look in /var/run for the .gdm_socket file
** Changed in: gnome-screensaver (Ubuntu)
Status: In Progress = Fix Released
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs
2.17.7-0ubuntu2 just posted to the repos; confirmed, the new version
works! Thanks so much for the quick turnaround :)
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Description changed:
Binary package hint: gnome-screensaver
If I lock my screen, then try to unlock it, the dialog hangs at
checking password. I honestly have not waited around long enough to
see if it will eventually unlock. I have waited a few minutes, nothing
- happens, just
** Changed in: gnome-screensaver (upstream)
Bugwatch: GNOME Bug Tracker #388642 = GNOME Bug Tracker
#http://bugzilla.gnome.org/show_bug.cgi?id=387572
Status: Rejected = Unknown
** Bug watch removed: GNOME Bug Tracker
#http://bugzilla.gnome.org/show_bug.cgi?id=387572
Oh no; it looks like its back; I just upgraded to 2.17.7-0ubuntu1 and
its doing it again. Let's hope this gets fixed before Herd 4 is
released.
** Changed in: gnome-screensaver (Ubuntu)
Status: Fix Released = Confirmed
--
screen does not unlock after locking
Confirmed here
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Confirmed here too, with 2.17.7-0ubuntu1. I got an strace of gnome-
screensaver-dialog for you
close(16) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1171411287, 862237}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
Problem is back in 2.17.7-0ubuntu1.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I can reproduce it after a fresh reboot, so I don't think it was related
to upgrading/restarting gdm.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: gnome-screensaver (Ubuntu)
Status: In Progress = Fix Released
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Hello,
Sorry, my previous comment was a case of cutpaste gone very wrong.
I can confirm that the problem persists. However, installing Feisty from
SCRATCH, and doing all of the updates at once, the problem is _not_
there. I think this is an important piece of information - could it be
that the
I have no idea why, but after today's updates, the problem doesn't
persist anymore. I can unlock the screensaver just fine.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Oh, I just saw gnome-screensaver got updated to -ubuntu2... for me, it's
working alright. No need to reinstall. If others can confirm this, I
guess we should close; merc's problem seems to be something else.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
I can confirm that 2.17.4-0ubuntu2 fixes the problem for me
(feisty/amd64)
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
raising importance, and I think this bug can be closed. Merc: it is
critical that you relogin (or better, reboot to be sure) after the
upgrade. Then this particular bug should be fixed. Can you confirm?
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = High
--
screen does not
Great! I can confirm that, after upgrading to gnome-screensaver
2.17.4-0ubuntu2 _and_ rebooting, the problem was solved for me. Thanks a
lot.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Hi,
I feel like a party-spoiler. But... I have 2.17.40-ubuntu2, and the problem is
still there :-/
What is worse, I am about to kill the laptop with the problem (the one
installed from scratch doesn't have the problem, and that's actually my
laptop - the other one I just had from Lenovo for a
Works after upgrading to 2.17.40-ubuntu2.
what I did:
killall gnome-screensaver
gnome-screensaver
and now it works back again
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I just tried it today. Seems it is fixed somehow, but I don't know why
it is fixed now ;)
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: gnome-screensaver (upstream)
Status: Unconfirmed = Rejected
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Still the same problem here with gnome-screensaver updated to
2.17.4-0ubuntu2
Regards
Pochu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Same here, still having the same problem. Attached latest debug output.
Package: gnome-screensaver
Priority: optional
Section: gnome
Installed-Size: 4052
Maintainer: Ubuntu Core Developers [EMAIL PROTECTED]
Architecture: i386
Version: 2.17.4-0ubuntu2
Depends: libart-2.0-2 (= 2.3.16), libatk1.0-0
** Bug watch added: GNOME Bug Tracker #388642
http://bugzilla.gnome.org/show_bug.cgi?id=388642
** Also affects: gnome-screensaver (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=388642
Importance: Unknown
Status: Unknown
--
screen does not unlock after locking
Still the same problem here with gnome-screensaver updated to
2.17.4-0ubuntu2
I can confirm that the problem persists.
Merc.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gnome-screensaver (upstream)
Status: Unknown = Unconfirmed
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Goodness... There has been a lot of action on this bug since I posted
it. : ) I love our community!
To confirm, yes, I am on feisty, and it hardly seems like it matters
now... But my gnome-screensaver is version
gnome-screensaver:
Installed: 2.17.4-0ubuntu1
Thanks for working on this...
Assigning to me.
** Changed in: gnome-screensaver (Ubuntu)
Assignee: (unassigned) = Pappan
Status: Unconfirmed = Needs Info
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Can you please confirm whether you are on feisty ? Also provide the
gnome-screensaver package version you are using ?
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I have the same problem.
Here is my aptitude show gnome-screensaver :
Package: gnome-screensaver
State: installed
Automatically installed: no
Version: 2.17.4-0ubuntu1
Priority: optional
Section: gnome
Maintainer: Ubuntu Core Developers [EMAIL PROTECTED]
Uncompressed Size: 4149k
Depends:
Is your password expired ? Can you try changing your password and see
whether you are able to unlock with the new password ?
If you still see the problem can you post /var/log/auth.log after
trying to unlock the screen.
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
Yeah, I'm having the same problem. Gotta do a CTRL + ALT + Backspace to
get back to the login.
[EMAIL PROTECTED]:~$ cat /etc/pam.d/gnome-screensaver
@include common-auth
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
desktop-bugs mailing list
48 matches
Mail list logo
