Has anyone else noticed that in F19 GNOME, even with Screen Lock turned off, lately the screen will lock anyway? Is there an existing bug, and if not, which component should it be filed under?
Andre Robatino <robatino <at> fedoraproject.org> writes:
Has anyone else noticed that in F19 GNOME, even with Screen Lock turned off, lately the screen will lock anyway? Is there an existing bug, and if not, which component should it be filed under?
The problem is worse than I thought. My screen just locked, and I was unable to get focus in the Password window to enter my password, though I could click on the "Unlock" button (giving an error about wrong password). So I couldn't unlock the screen, and had to restart X. I'm pretty sure this started just in the last few days.
On 10/15/2013 11:03 AM, Andre Robatino wrote:
Andre Robatino <robatino <at> fedoraproject.org> writes:
Has anyone else noticed that in F19 GNOME, even with Screen Lock turned off, lately the screen will lock anyway? Is there an existing bug, and if not, which component should it be filed under?
The problem is worse than I thought. My screen just locked, and I was unable to get focus in the Password window to enter my password, though I could click on the "Unlock" button (giving an error about wrong password). So I couldn't unlock the screen, and had to restart X. I'm pretty sure this started just in the last few days.
Andre,
I had this problem after having updated the cinnamon pkgs, though I see no releationship.
On 10/15/2013 11:21 AM, Andre Robatino wrote:
Joachim Backes <joachim.backes <at> rhrk.uni-kl.de> writes:
I had this problem after having updated the cinnamon pkgs, though I see no releationship.
I currently have 5 DEs installed (GNOME/KDE/MATE/Cinnamon/Basic), but was using GNOME at the time.
I'm running gnome3 too as my DE, but the update of the cinnamon screen locker disturbed the gnome screen locker totally (no input focus,...). I got rid of this by (at least) uninstalling the cinnamon screen locker.
Joachim Backes
Am 15.10.2013 12:17, schrieb Joachim Backes:
On 10/15/2013 11:21 AM, Andre Robatino wrote:
Joachim Backes <joachim.backes <at> rhrk.uni-kl.de> writes:
I had this problem after having updated the cinnamon pkgs, though I see no releationship.
I currently have 5 DEs installed (GNOME/KDE/MATE/Cinnamon/Basic), but was using GNOME at the time.
I'm running gnome3 too as my DE, but the update of the cinnamon screen locker disturbed the gnome screen locker totally (no input focus,...). I got rid of this by (at least) uninstalling the cinnamon screen locker.
Same here.
If you're locked out: Change to a virtual terminal (ctrl f2), login there and run "killall cinnamon-screensaver".
Zaptac
zaptac <mp-001 <at> ponschab.de> writes:
Same here.
If you're locked out: Change to a virtual terminal (ctrl f2), login there and run "killall cinnamon-screensaver".
Thanks for this, I'll try it next time it happens, and file a bug if it works. (BTW, I don't always have the problem - the last time I was locked out, I was able to enter password.) I currently have cinnamon-screensaver-2.0.0-1.fc19 installed from just over a day ago, which is probably when the problem started.
On Tue, Oct 15, 2013 at 11:25:13AM +0000, Andre Robatino wrote:
Thanks for this, I'll try it next time it happens, and file a bug if it works. (BTW, I don't always have the problem - the last time I was locked out, I was able to enter password.) I currently have cinnamon-screensaver-2.0.0-1.fc19 installed from just over a day ago, which is probably when the problem started.
Cinnamon bug. It seems cinnamon-screensaver was forked from gnome-screensaver, but they didn't adjust the autostart file. So currently it is configured to start under GNOME and Unity. Breaking things under GNOME.
Please file a bug. Note: the bug is in Cinnamon, because I see the same in Mageia.
On Tue, Oct 15, 2013 at 03:09:32PM +0200, Olav Vitters wrote:
Please file a bug. Note: the bug is in Cinnamon, because I see the same in Mageia.
Checking more, it seems that almost all of the Cinnamon 2.0 packages have similar bugs. Causing Cinnamon bits to start under GNOME. Plus Cinnamon specific programs to show up under GNOME (and not under Cinnamon).
Pretty much all the .desktop files in Cinnamon packages are wrong.
Olav Vitters <olav <at> vitters.nl> writes:
Cinnamon bug. It seems cinnamon-screensaver was forked from gnome-screensaver, but they didn't adjust the autostart file. So currently it is configured to start under GNOME and Unity. Breaking things under GNOME.
Please file a bug. Note: the bug is in Cinnamon, because I see the same in Mageia.
I was locked out and was able to get back in by going to a VT and killing the cinnamon-screensaver process.
Andre Robatino <robatino <at> fedoraproject.org> writes:
Olav Vitters <olav <at> vitters.nl> writes:
Cinnamon bug. It seems cinnamon-screensaver was forked from gnome-screensaver, but they didn't adjust the autostart file. So currently it is configured to start under GNOME and Unity. Breaking things under GNOME.
Please file a bug. Note: the bug is in Cinnamon, because I see the same in Mageia.
I was locked out and was able to get back in by going to a VT and killing the cinnamon-screensaver process.
The bug was just closed as NOTABUG with the comment "Get the gnome devs to blacklist it." Since you obviously understand this stuff much better than me, does that sound like a reasonable response?
On Tue, Oct 15, 2013 at 05:51:53PM +0000, Andre Robatino wrote:
The bug was just closed as NOTABUG with the comment "Get the gnome devs to blacklist it." Since you obviously understand this stuff much better than me, does that sound like a reasonable response?
To explain this in a bit more detail. Packages can configure to automatically start programs. This is done by placing files in /etc/xdg/autostart. Obviously you sometimes only want to start an application under a certain desktop environment. Or maybe multiple. To do that, you can have a header like: OnlyShowIn=GNOME;Unity;
Which tells GNOME it should be started. This header is currently in cinnamon-screensaver.desktop. What's wrong is that Cinnamon has GNOME there. They should specify Cinnamon and listen to that.
His answer is basically: - instead of Cinnamon just listening to: OnlyShowIn=Cinnamon - GNOME should be patched to specifically ignore cinnamon-screensaver.desktop and then patched again whenever Cinnamon adds more desktop files.
In any case, that is not a solution at all. It just works around things, badly.
Note that a lot of Cinnamon components will now start in GNOME due to this bug. I've added a more brief comment to Bugzilla.
Andre Robatino <robatino <at> fedoraproject.org> writes:
I was locked out and was able to get back in by going to a VT and killing the cinnamon-screensaver process.
The updates-testing packages from https://admin.fedoraproject.org/updates/FEDORA-2013-19499 seem to fix the problem for me. But it needs another +2 karma to go to stable, so more testing would be welcome.
| From: Joachim Backes joachim.backes@rhrk.uni-kl.de
| On 10/15/2013 11:03 AM, Andre Robatino wrote: | > Andre Robatino <robatino <at> fedoraproject.org> writes: | > | >> Has anyone else noticed that in F19 GNOME, even with Screen Lock turned off, | >> lately the screen will lock anyway? Is there an existing bug, and if not, | >> which component should it be filed under? | > | > The problem is worse than I thought. My screen just locked, and I was unable | > to get focus in the Password window to enter my password, though I could | > click on the "Unlock" button (giving an error about wrong password). So I | > couldn't unlock the screen, and had to restart X. I'm pretty sure this | > started just in the last few days.
| I had this problem after having updated the cinnamon pkgs, though I see | no releationship.
Thanks very much for this thread. It's great to have mysteries revealed.
My desktop too got into the weird state where I could not type in my password to lock the screen (as describe by Andre).
I also had a few crash-on-resume problems.
And the screen saver no longer honoured my request to go all-black: it left a clock on the screen.
I've also had these problems on my notebook (but have not used it much).
I thought that the problem might be the very recent kernel update to kernel-3.11.4-201.fc19.x86_64.
I booted with the last-but-one kernel, kernel-3.11.3-201.fc19.x86_64. Since then (yesterday), I've not had trouble. But the screen-saver screen is still different.
Since I don't use Cinnamon, I'll just remove all its packages, reboot the old kernel, and see if life goes back to normal.
Trial and error got me this command to remove Cinnamon: sudo rpm -e `rpm -qa | grep -i cinnamon` muffin nemo nemo-extensions nemo-open-terminal
I forgot to mention another symptom. Sometimes a warning box would pop up near the bottom of my screen, and then go away. I think it popped up when a screen-save was about to fire, so I didn't see it very often. It said: Unable to Lock: lock was blocked by an application
Stupidly, the message doesn't say what program is generating this. Grrr.
I guess it is one of the two competing screen locking facilities (ordinary Gnome and Cinnamon).
-
Andre Robatino -
D. Hugh Redelmeier -
Joachim Backes -
Olav Vitters -
zaptac