[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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= user=mysz Feb 19 10:26:17 urzenia login[20144]: (pam_unix) session opened for user mysz by (uid=0) Of course my password is correct and not expired. My feisty is up-to- date, I do it 5 minutes ago :) % apt-cache show gnome-screensaver | grep -i version Version: 2.17.7-0ubuntu2 -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Hello daviey, dpkg return as follow: ii gnome-screensaver 2.17.7-0ubuntu2 -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 /var/run/gdm_socket Quick symlink hack to fix the issue: sudo ln -s /var/run/.gdm_socket /var/run/gdm_socket -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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, temporary solution, but hey it works. Hope this helps. - Jai -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** Changed in: gnome-screensaver (upstream) Status: Unknown = Fix Released -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Confirmed, fix works :D -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 'dbus-launch gnome-session'), the screensaver still locks up as described. I guess it's looking for the GDM socket, and still locks up when it can't find it? If so the more sensible fix is not to hang if the socket can't be found. :-) I use 'startx' on my laptop sometimes, because the external monitor requires a different X server command line than the laptop's panel. But anyway, 'startx' should work, and everything else Gnome-ish seems to be fine with it. (Unfortunately, I can't even switch to a console VT and 'killall gnome- screensaver' to unlock when it hangs, because switching back to the X server fails to restore the graphic display. So I have to kill the X server and lose the session. But that's a different bug). -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** 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 hangs, with the password filed grayed out, like it should + happens, just hangs, with the password field grayed out, like it should normally, and checking password, but it never unlocks as far as I can tell. This is different from any bugs I have found. The dialog appears normally, and accepts my typing into the box, however as explained, it inexplicably freezes. I have to kill the session and re-log. I'd be happy to help figure this out, I just don't know how to proceed to get more useful information. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** 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 http://bugzilla.gnome.org/show_bug.cgi?id=http://bugzilla.gnome.org/show_bug.cgi?id=387572 ** Bug watch added: GNOME Bug Tracker #387572 http://bugzilla.gnome.org/show_bug.cgi?id=387572 -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Confirmed here -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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,
events=POLLIN|POLLPRI}, {fd=10, events=POLLIN|POLLPRI}, {fd=11,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN},
{fd=14, events=0}], 8, 0) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1171411287, 862353}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=10, events=POLLIN|POLLPRI}, {fd=11,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN},
{fd=14, events=0}], 8, 0) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 16
fcntl64(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
connect(16, {sa_family=AF_FILE, path=/tmp/.gdm_socket}, 110) = -1 ENOENT (No
such file or directory)
send(16, CLOSE\n, 6, MSG_NOSIGNAL)= -1 ENOTCONN (Transport endpoint is
not connected)
write(2, \n(gnome-screensaver-dialog:16595..., 107) = 107
This repeats continuously until I kill it.
I'd just done an upgrade through software-updates, I don't know if that
is related. It did upgrade gnome-screensaver.
2007-02-14 10:27:44 status unpacked gnome-screensaver 2.17.7-0ubuntu1
2007-02-14 10:27:44 status unpacked gnome-screensaver 2.17.7-0ubuntu1
2007-02-14 10:27:44 status unpacked gnome-screensaver 2.17.7-0ubuntu1
2007-02-14 10:27:44 status half-configured gnome-screensaver 2.17.7-0ubuntu1
2007-02-14 10:27:47 status installed gnome-screensaver 2.17.7-0ubuntu1
It's true there is no /tmp/.gdm_socket, is there meant to be?
(Is tmp really a good location for that anyhow?)
--
screen does not unlock after locking
https://launchpad.net/bugs/76632
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Problem is back in 2.17.7-0ubuntu1. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** Changed in: gnome-screensaver (Ubuntu) Status: In Progress = Fix Released -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 problem only shows for incremental updates? Can anybody else confirm this? Merc. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 product review... If nobody else has this problem, please do close the bug. Otherwise, please let me know which output you'd like... Merc. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** Changed in: gnome-screensaver (upstream) Status: Unconfirmed = Rejected -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
gnome-screensaver (2.17.4-0ubuntu2) feisty; urgency=low . * add 01_fix_pam_cvs20061220 to (hopefully) fix malone #76632 please test this build as soon as its available in the archive -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 76632] Re: screen does not unlock after locking
-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 iD8DBQFFi/3nPHB1VjBTaKERAqYSAKClKFfoA5gNP/xGo46ehp5B3Xn3PACfQw20 klwnhsnFbpO93e2wac8kMn8= =I8Wp -END PGP SIGNATURE- -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 (= 1.12.2), libbonobo2-0 (= 2.15.0), libbonoboui2-0 (= 2.15.1), libc6 (= 2.5-0ubuntu1), libcairo2 (= 1.2.4), libdbus-1-3 (= 0.94), libdbus-glib-1-2 (= 0.72), libexif12, libfontconfig1 (= 2.4.0), libfreetype6 (= 2.2), libgconf2-4 (= 2.13.5), libgl1-mesa-glx | libgl1, libglade2-0 (= 1:2.5.1), libglib2.0-0 (= 2.12.0), libgnome-keyring0 (= 0.7.1), libgnome-menu2 (= 2.15.4), libgnome2-0 (= 2.14.1), libgnomecanvas2-0 (= 2.11.1), libgnomeui-0 (= 2.16.0), libgnomevfs2-0 (= 2.16.0-1), libgtk2.0-0 (= 2.10.3), libice6 (= 1:1.0.0), liborbit2 (= 1:2.14.1), libpam0g (= 0.76), libpango1.0-0 (= 1.15.2), libpng12-0 (= 1.2.13-4), libpopt0 (= 1.10), libsm6, libx11-6, libxau6, libxcursor1 ( 1.1.2), libxext6, libxfixes3 (= 1:4.0.1), libxi6, libxinerama1, libxml2 (= 2.6.27), libxrandr2, libxrender1, libxss1, libxxf86misc1, libxxf86vm1, zlib1g (= 1:1.2.1), gconf2 (= 2.12.1-4ubuntu1) Recommends: xscreensaver-data, xscreensaver-gl, rss-glx Size: 1545896 Description: a screen saver and locker gnome-screensaver is a screen saver and locker that aims to have simple, sane, secure defaults and be well integrated with the desktop. It is designed to support: . * the ability to lock down configuration settings * translation into other languages * user switching Original-Maintainer: Sebastien Bacher [EMAIL PROTECTED] ** Attachment added: debug output http://librarian.launchpad.net/5515299/screensaver_debug.log -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** 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 https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** Changed in: gnome-screensaver (upstream) Status: Unknown = Unconfirmed -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
I've been having the same problems - I've attached my debug log, generated using kill `pidof gnome-screensaver`;gnome-screensaver --no-daemon --debug ~/Desktop/screensaver_debug.log ** Attachment added: screensaver_debug.log http://librarian.launchpad.net/5506526/screensaver_debug.log -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Read at ubuntuforums.org: Logging to virtual terminal and killall gnome-screensaver is workaround Regards Pochu -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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... Pretty frustrating bug. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
confirm here on feisty with gnome-screensaver 2.17.4-0ubuntu1 I tried to run: kill `pidof gnome-screensaver`;gnome-screensaver --no-daemon --debug ~/Desktop/screensaver_debug.log But infortunately, has I had to switch to virtual console and killall gnome-scrennsaver, the logs were empty. by the way, this is /usr/lib/gnome-screensaver/gnome-screensaver-dialog --enable-switch which locks on 'checking' but killing only this process will respawn it. Therefore we need to kill gnome-screensaver. Hope this helps -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
To debug authentication problems you want to use the test-passwd tool in the src directory or the gnome-screensaver sources. This may be fixed by the patch in GNOME bug #387572. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
i'm waving it into the 2.17.4 version (doesnt apply cleanly it seems), lets see if it fixes it, thanks for the pointer. ** Changed in: gnome-screensaver (Ubuntu) Assignee: Pappan = Oliver Grawert Status: Confirmed = In Progress -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
@Oliver Grawert: keep us posted. As soon as you think you have a patch post it, so I (we) can test it ;) @Brendan Martens: Thats Ubuntu :P If you find something it will be fixed soon ... -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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: libart-2.0-2 (= 2.3.16), libatk1.0-0 (= 1.12.2), libbonobo2-0 (= 2.15.0), libbonoboui2-0 (= 2.15.1), libc6 (= 2.5-0ubuntu1), libcairo2 (= 1.2.4), libdbus-1-3 (= 0.94), libdbus-glib-1-2 (= 0.72), libexif12, libfontconfig1 (= 2.4.0), libfreetype6 (= 2.2), libgconf2-4 (= 2.13.5), libgl1-mesa-glx | libgl1, libglade2-0 (= 1:2.5.1), libglib2.0-0 (= 2.12.0), libgnome-keyring0 (= 0.7.1), libgnome-menu2 (= 2.15.4), libgnome2-0 (= 2.14.1), libgnomecanvas2-0 (= 2.11.1), libgnomeui-0 (= 2.16.0), libgnomevfs2-0 (= 2.16.0-1), libgtk2.0-0 (= 2.10.3), libice6 (= 1:1.0.0), liborbit2 (= 1:2.14.1), libpam0g (= 0.76), libpango1.0-0 (= 1.15.1), libpng12-0 (= 1.2.15~beta5), libpopt0 (= 1.10), libsm6, libx11-6, libxau6, libxcursor1 ( 1.1.2), libxext6, libxfixes3, libxi6, libxinerama1, libxml2 (= 2.6.27), libxrandr2, libxrender1, libxss1, libxxf86misc1, libxxf86vm1, zlib1g (= 1:1.2.1), gconf2 (= 2.12.1-4ubuntu1) Recommends: xscreensaver-data, xscreensaver-gl, rss-glx Description: a screen saver and locker gnome-screensaver is a screen saver and locker that aims to have simple, sane, secure defaults and be well integrated with the desktop. It is designed to support: * the ability to lock down configuration settings * translation into other languages * user switching I do have Feisty ;) Thanks for your job. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
same here on feisty. changed password with passwd and still the same problem. also I could not change via system-admin-users/groups because after i enter my password, the app just locks up. could be related to this. posting my auth.log ** Attachment added: auth.log http://librarian.launchpad.net/5498732/auth.log -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Same here on Feisty up-to-date. Thomas, the problem with system-admin-users is with gksudo. You should launch it from a terminal with: sudo dbus-launch application such as sudo dbus-launch gdmsetup Regards Pochu -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
I have this bug also. confirmed. Running also feisty -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
happens after the big update of feisty yesterday ** Changed in: gnome-screensaver (Ubuntu) Assignee: Pappan = Amnon82 Status: Needs Info = Confirmed -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
could you please run: kill `pidof gnome-screensaver`;gnome-screensaver --no-daemon --debug ~/Desktop/screensaver_debug.log lock and try to unlock and attach the log to the bug -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
** Changed in: gnome-screensaver (Ubuntu) Assignee: Amnon82 = Pappan -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Hope this helps: [EMAIL PROTECTED]:~$ sudo kill `pidof gnome-screensaver`;gnome-screensaver --no-daemon --debug ~/Desktop/screensaver_debug.log Password: Usage: kill pid ... Send SIGTERM to every process listed. kill signal pid ... Send a signal to every process listed. kill -s signal pid ...Send a signal to every process listed. kill -l List all signal names. kill -L List all signal names in a nice table. kill -l signalConvert between signal numbers and names. [gs_debug_init] gs-debug.c:106 (23:27:45): Debugging enabled [main] gnome-screensaver.c:87 (23:27:45):initializing gnome-screensaver 2.17.4 [query_session_id] gs-listener-dbus.c:1868 (23:27:45): org.freedesktop.DBus.Error.ServiceUnknown raised: The name org.freedesktop.ConsoleKit was not provided by any .service files [init_session_id] gs-listener-dbus.c:1886 (23:27:45):Got session-id: (null) [gs_fade_init] gs-fade.c:678 (23:27:45): Fade type: 2 [gamma_info_init] gs-fade.c:352 (23:27:45): Initialized gamma ramp fade [initialize_server_extensions] gs-watcher-x11.c:900 (23:27:45): Not using server's MIT-SCREEN-SAVER extension. [gs_watcher_set_active] gs-watcher-x11.c:728 (23:27:45): turning watcher: ON [_gs_watcher_set_active_internal] gs-watcher-x11.c:715 (23:27:45): Starting idle watcher [listener_dbus_handle_system_message] gs-listener-dbus.c:1371 (23:27:45): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.11 [listener_dbus_handle_system_message] gs-listener-dbus.c:1371 (23:27:45): obj_path=(null) interface=(null) method=(null) destination=:1.11 [listener_dbus_handle_system_message] gs-listener-dbus.c:1371 (23:27:45): obj_path=(null) interface=(null) method=(null) destination=:1.11 [listener_dbus_handle_system_message] gs-listener-dbus.c:1371 (23:27:45): obj_path=(null) interface=(null) method=(null) destination=:1.11 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:27:49): Window created: noticing activity on 0xE01CE2 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x100057F [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x1000580 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0xE01D18 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A1 [notice_events_inner] gs-watcher-x11.c:355 (23:28:04): Adding events for 0x2A2 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00025 [notice_events_inner] gs-watcher-x11.c:355 (23:28:04): Adding events for 0x2A00025 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00051 [notice_events_inner] gs-watcher-x11.c:355 (23:28:04): Adding events for 0x2A00051 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0005A [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0005B [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00063 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00064 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00065 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00066 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00067 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00068 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00069 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0006A [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0006B [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0006C [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A0006D [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00072 [_gs_watcher_notice_window_created] gs-watcher-x11.c:565 (23:28:04): Window created: noticing activity on 0x2A00077 [_gs_watcher_notice_window_created]
[Bug 76632] Re: screen does not unlock after locking
I have to restart X with Ctrl+Alt+Backspace so the log is still empty. How can I run your command and save it to a log? When does the log gets saved? -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Some snippes out of auth.log: Dec 20 22:53:01 amsoft gdm[4367]: (pam_unix) session closed for user amnon Dec 20 22:54:05 amsoft gdm[4536]: (pam_unix) session opened for user amnon by (uid=0) Dec 20 23:17:09 amsoft gdm[4536]: (pam_unix) check pass; user unknown Dec 20 23:17:09 amsoft gdm[4536]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= Dec 20 23:17:21 amsoft gdm[4536]: (pam_unix) session opened for user amnon by (uid=0) Dec 20 23:27:45 amsoft sudo:amnon : TTY=pts/0 ; PWD=/home/amnon ; USER=root ; COMMAND=/bin/kill Dec 20 23:34:43 amsoft gdm[4536]: (pam_unix) session closed for user amnon Dec 20 23:34:52 amsoft gdm[5748]: (pam_unix) session opened for user amnon by (uid=0) Dec 20 23:38:29 amsoft gdm[5748]: (pam_unix) session closed for user amnon Dec 20 23:38:58 amsoft gdm[6022]: (pam_unix) session opened for user amnon by (uid=0) -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
@ Amnon82 I do not think you need to use sudo for the steps mentioned by Oliver unless you are locking and unlocking as root. Please try it again without sudo: Also can you try the following along with above ? 1. cat /etc/pam.d/gnome-screensaver Also list the contents of any files mentioned inside /etc/pam.d/gnome- screensaver with @include directive. 2. Can you do the following and see whether unlocking works ? sudo chmod 4755 /usr/bin/gnome-screensaver kill `pidof gnome-screensaver`; gnome-screensaver -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
@pappan: I realy want to post you the log. How do I run the command and getting something into the log. It is still empty. I tried the 1. thing with and without sudo. For the second thing you mentioned: [EMAIL PROTECTED]:~$ sudo chmod 4755 /usr/bin/gnome-screensaver Password: [EMAIL PROTECTED]:~$ kill `pidof gnome-screensaver`; gnome-screensaver (process:6561): Gtk-WARNING **: This process is currently running setuid or setgid. This is not a supported use of GTK+. You must create a helper program instead. For further details, see: http://www.gtk.org/setuid.html Refusing to initialize GTK+. should I reboot my machine and try again? -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Sorry, you can leave the second part of doing chmod. Can you please tell us whether you are using authentication information from a different machine (like ldap, nis etc) Also please post the contents of /etc/pam.d/gnome-screensaver and the include files listed inside /etc/pam.d/gnome-screensaver The @include files can be found in /etc/pam.d itself. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
Can you please tell us whether you are using authentication information from a different machine (like ldap, nis etc) No I don't. I only want to help to fix this bug. I got it form: http://www.ubuntuforums.org/showthread.php?t=322498 Here you go: [EMAIL PROTECTED]:~$ cat /etc/pam.d/gnome-screensaver @include common-auth [EMAIL PROTECTED]:~$ ** Attachment added: @include common-auth http://librarian.launchpad.net/5500508/common-auth -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
I confirmed this bug. I have a normal authentication. -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
... seems there isn't a way to post you the ~/Desktop/screensaver_debug.log? I tried it with a terminal and with ALT+F2 Run Application ... -- screen does not unlock after locking https://launchpad.net/bugs/76632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76632] Re: screen does not unlock after locking
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
