lock screen doesn't work

[ASDFASDF]

Binary package hint: indicator-session

lock screen option from the indicator-session doesn't work, it used to work before the latest updates.

ProblemType: Bug
Architecture: i386
Date: Fri Sep 25 18:29:11 2009
DistroRelease: Ubuntu 9.10
Package: indicator-session 0.1.5-0ubuntu1
ProcEnviron:
 LANGUAGE=hr_HR.UTF-8
 PATH=(custom, user)
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SourcePackage: indicator-session
Uname: Linux 2.6.31-10-generic i686

[Ted Gould (ted)]

On Fri, 2009-09-25 at 16:31 +0000, Igor Vatavuk wrote:
> lock screen option from the indicator-session doesn't work, it used to
> work before the latest updates.

Hmm, it seems we were too aggressive with the lock screen protection.
It won't lock if you have autologin enabled.

It would seem like if you specifically ask it to lock, it should. On
the other hand, if you accidentally hit the menu item and you've got no
clue of your password, that's no good as well.

Thoughts? I'm leaning towards disabling the menu item with autologin.

  affects indicator-session
  priority medium
  milestone ubuntu-9.10
  status confirmed
  subscribe dbarth
  subscribe ivanka
  subscribe mpt

[Vish (vish)]

Why does this have to be done.

My system runs 24/7, so often i lock the screen and leave.
But since i have selected auto-login , this option is not available.

At the cost of simplifying things for new users , things are made harder for the regular users :/

The question of security issue for auto-login might be asked , "Oh , anyone might hard shutdown the system and can easily boot back in and view your data"...
If a stranger or someone is walking and having access to my system , then i have more serious concerns than my system being hacked!
Well... people i am surrounded by maintain their boundaries and dont use the system when its locked or use a different session!
Pls dont do this on the basis of security.

Ted gould said this was done because the netbook users forget the password and lock screen and get locked out!

If it is the issue that user are forgetting the password , a solution could be:
By default , if the user selects auto-login during install, greyout the option in the menu [or do not display the option , the menu is getting huge as is!]
Now present the option to display the lock-screen in the System Administration > Login screen.
[/] show lock screen option in the indicator session.

This would be a better solution. As this is the place where the user selects the auto-login feature.

Not all users have nosy people around them nor does everyone forget their password. Why does the solution to a problem always have to mean the removal of the option!

[Matthew Paul Thomas (mpt)]

I suggest that if someone sets themselves up to log in automatically, the "Lock Screen" command is insensitive by default.

Then, if it is possible to get a User Interface Freeze exception for this, I suggest that in the "Users and Groups" settings, the bottom of the "Password" section for your user account should have a checkbox, "Allow locking the screen (requires password to unlock)". If you are using automatic login, the checkbox should be unchecked by default, otherwise it should be checked by default. If it is checked, the "Lock Screen" item should be sensitive.

In the long term, the various security settings should be consolidated into a single Security control panel.

[Ted Gould (ted)]

On Tue, 2009-09-29 at 10:49 +0000, Matthew Paul Thomas wrote:
> I suggest that if someone sets themselves up to log in automatically,
> the "Lock Screen" command is insensitive by default.

Makes sense to me.

> Then, if it is possible to get a User Interface Freeze exception for
> this, I suggest that in the "Users and Groups" settings, the bottom of
> the "Password" section for your user account should have a checkbox,
> "Allow locking the screen (requires password to unlock)". If you are
> using automatic login, the checkbox should be unchecked by default,
> otherwise it should be checked by default. If it is checked, the "Lock
> Screen" item should be sensitive.

I understand this from the user perspective, but from the technical one
I'm not sure how this should be stored. It would be tricky to set a
setting in another user's gconf repository. It would also doesn't seem
like it would be a system level setting.

Anyway, I think we should open another bug for this, as I don't believe
it can be done for 9.10.

[Ted Gould (ted)]

  affects indicator-session
  assign ted

[Vish (vish)]

Ted , If the option to re-enable lock screen option is not possible for 9.10 , how is this bug going to be fixed?
If its not possible to implement it as mpt has suggested , its better to not implement new feature and reverting to previous behavior.

As most users autologin and a constant greyed out lock screen option would not be ideal. ;)

[Ted Gould (ted)]

On Tue, 2009-09-29 at 15:46 +0000, mac_v wrote:
> As most users autologin and a constant greyed out lock screen option
> would not be ideal. ;)

Well, I don't think that there is a basis to say that most users
autologin :) But, I think that for 9.10 the safest option is to just
disable the menu item. Then in 10.04 we can continue to refine it.
I've opened bug 438936 to ensure this gets fixed for Lucid.

[Omegamormegil (omegamormegil)]

Lock screen does not work for me either, and I never use auto-login. To reiterate, I am prompted for a password when my system boots, and using the Indicator Applet Session applet to lock the screen does absolutely nothing.

[Ted Gould (ted)]

On Tue, 2009-09-29 at 23:43 +0000, Omegamormegil wrote:
> Lock screen does not work for me either, and I never use auto-login. To
> reiterate, I am prompted for a password when my system boots, and using
> the Indicator Applet Session applet to lock the screen does absolutely
> nothing.

Try this:

  $ dbus-send --print-reply --reply-timeout=100
--dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock

That is the same thing that the session menu is doing.

[Vish (vish)]

Ted Gould wrote :
> Well, I don't think that there is a basis to say that most users autologin

This feature is being done for auto login users , So they must be considered a significant population ;)

If providing option to enable lock screen , in "Users and Groups" settings , is not possible.

Why not provide a gconf setting? atleast those who want it back will have a way to enable it.. Why does this have to be hardcoded for the next 6 moths? Pls provide a gconf setting :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-session - 0.1.6-0ubuntu1

---------------
indicator-session (0.1.6-0ubuntu1) karmic; urgency=low

  * Upstream release 0.1.6 (LP: #440216)
    * Making startup of services asynchronous (LP: #436181)
    * Disabling "Lock Screen" item when action is blocked by
      GDM autologin (LP: #436724)
    * Disabling "Lock Screen" in guest session (LP: #439068)

 -- Ted Gould <email address hidden> Thu, 01 Oct 2009 23:33:25 +0200

[Brian Owens (bjo101)]

Where can I download the package to fix this bug in Karmic?

Thanks,

Brian Owens

[Martin Pitt (pitti)]

Brian, it's in karmic. Just update to the latest packages.

[Daniel_Brez (daniel-breznau)]

I agree that the option should be available to those who still have autologin enabled. I'm on a laptop at school and will leave on and in my friends company while I quickly go to use the bathroom, etc. and would prefer that they don't mess with it. I know it's not really "secure" with autologin, but its nice to have to stop the casual temptation.

[Martin Pitt (pitti)]

> I agree that the option should be available to those who still have autologin enabled.

+1. It should be disabled when the password is locked, not when autologin is enabled. Autologin and password locking are different concepts, and I don't see a reason to disable screen locking when having autologin. After autologin you are in a fresh session, but with a locked session you might currently work on sensitive documents, or typing a private mail, or what not.

[Biji (biji)]

this bug reintroduces in beta:
ii indicator-applet-session 0.2.0-0ubuntu1 A clone of the GNOME panel indicator applet.

lock screen not working, no auto login enabled

[Human (humanitas)]

I have the same problem: lock screen not working, no auto login enabled.

Then i run this
"dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock"

i have error:
"Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files"

Karmic, all updates are installed.

[David Barth (dbarth)]

Thanks for your feedback.

@Human: this shows that the issue is with gnome-screensaver not running: can you investigate why?

@Biji: can you confirm that the option is indeed present in the session menu, but that only the action is not performed? In this case, you could use the test that Human just proposed to see whether gnome-screensaver is running or not. I suspect it may not run in your case.

[Chris Coulson (chrisccoulson)]

Human - is the screensaver enabled in System -> Preferences -> Startup Applications?

[Kalana (kalguni)]

@Chris Coulson
 I had the same problem and found out that I had disable the screen saver on startup as you have shown. Thanks. Now it's working as it suppose to work.

[Biji (biji)]

the lock screen menu sometimes work sometime not working.. when not working executing this on terminal would lock the screen:

"dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock"

[Ted Gould (ted)]

On Wed, 2009-10-28 at 10:46 +0000, Biji wrote:
> the lock screen menu sometimes work sometime not working.. when not
> working executing this on terminal would lock the screen:

When it works, does it work for the entire session? So you login once
and it works all the time, then you login again and it never works?

[Omegamormegil (omegamormegil)]

"dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock" does lock my screen, but clicking the Lock Screen option from the Applet dropdown still does absolutely nothing, and I don't use autologin.

[P4man (duvel123)]

Same problem here. Karmic up to date as of now.
Lock Screen from the applet does nothing. Running the command gives:

bob@bob-desktop:~$ dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files

Tried changing some settings regarding screensaver and in gconf-editor, but it makes no difference.

Probably doesnt matter, but Im using 2 monitors.

[P4man (duvel123)]

I probably should have mentioned, Im not using auto login either.

[Brian Owens (bjo101)]

Hi all,

I notice several people are still experiencing this issue for me it was resolved two or so weeks ago, I believe they released a fix that resolved this issue. If you are still having this issue make sure that the proposed updates are checked off i you updates tab under software sources.

[xica (oxx00hj02)]

I'm still having this issue too.

I did a clean install (with forgetting to archive my /etc ) a few days ago. I then updated the installation. Curiously the universe and multiverse never had to be checked, that was already done.

When I'm logged into my single screen, the "Lock Screen" under the upper right dropdown does nothing.

Workaround: Instead, click "Switch User..." and login as guest. When you get back to your PC, you will need to enter in your password when you switch back to yourself.

This (presumably) keeps the files you have protected with permissions safe, but it does still allow access to the machine.

[xica (oxx00hj02)]

also, I'm not using auto login either.

[mealstrom (mischenko-mm)]

ubuntu karmic amd_x64

ctrl + alt + L works, indicator doesnt.

$dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock
works with this error:
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[Wiley (coyotewilee99)]

Exactly the same problem as mealstrom, intel 32 though:

Karmic all updated

ctrl+alt+L works, indicator doesn't. Used to work a few weeks ago though!

$dbus-send works but shows the same error as in mealstrom's post

[JMFTheVCI (jmfthevci)]

lock screen in any of its variants (System>Lock Screen, Ctrl-Alt-L, and the DBUS command listed) do nothing and my system does not lock.
I have a screensaver enabled. I do not use autologin.
I have also just upgraded to Lucid Alpha 1 and the problem is still there.
Getting this fixed would be good as to lock my screen I have to logout!

[JMFTheVCI (jmfthevci)]

BTW. This is the response from the dbus command:
jmf@UbuntuJMF:~$ dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files

[EddieArt (arteleb1)]

I also have the same bug, I have all Karmic updates installed.
My system is a IBM T61.

[sergioroa (s-roa)]

Same problem here. I had to install gnome-screensaver package:
sudo apt-get install gnome-screensaver
Run:
$ gnome-screensaver
and then the indicator and Ctrl-Alt-L work

[ogro (ogromano)]

Same problem here... Clean install to 9.10 from 8.04, 4 weeks ago. Everything up to date. No auto-login. Screen saver and option to lock screen when Screensaver active are both enabled.
(current system: Kernel 2.6.31-17, Gnome 2.28.1)

Indicator : clicked on Lock Screen... Nothing happens
Ctrl+Alt+L: Nothing happens
Lock screen Panel applet: added to panel, clicked, nothing happens. (Note: when selecting this applet's properties the Screen saver options pop-up).
Dbus command suggested above: run with screen saver enabled and lock option checked, not worked, output: [$ dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock
Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files]
Main menu Lock screen option: clicked, nothing happens.

Don't know what else to try...

Thanks in advance for the hardwork...

 - Ogro -

[Kensey (ubuntu-orion-com)]

I started with lock not working at all and partially resolved my issues by creating my own .service file (attached) in /usr/share/dbus-1/services/org.gnome.ScreenSaver.service

Before:

* Ctrl-Alt-L did not lock
* "dbus-send --print-reply --reply-timeout=100 --dest=org.gnome.ScreenSaver / org.gnome.ScreenSaver.Lock" terminated with the error:

"Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files"

* session-menu -> Lock Screen did not work

After:

* Ctrl-Alt-L works
* the dbus command works but also generates the following error:

"Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

* session-menu -> Lock Screen still does not work

There is still another issue -- when I go to unlock by striking a key or moving the mouse, the screensaver freezes but the unlock dialog does not appear. Blindly typing my password successfully unlocks the screen.

[Kensey (ubuntu-orion-com)]

After a reboot, the Lock Screen menu item works, but I still have to type the password blindly.

[Glenn Dimaliwat (guren)]

"Lock Screen" in indicator applet was working great for me until today.

I'm using indicator-applet-session 0.1

1. Ctrl-Alt-L works
2. gnome-screensaver-command --lock works
3. dbus command also works with the following error:

Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[Sebastien Bacher (seb128)]

is there anybody still getting the issue in lucid now with gnome-screensaver installed? (there is a different bug about the option not working when gnome-screensaver is not installed)

[Vish (vish)]

Seems fixed. No problems now.

[Vish (vish)]

Oh ,btw using , indicator-session 0.2.5-0ubuntu1