Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Hi smurfendrek,
Please check jarnos comment #89, you need to use light-locker, using dm-tool
for lock is not recommended.
You could also try with other screen lockers program.
Also this is an old bug, if you are still experiencing the problem, please open
a new bug.
I am unsubscribing the
** Tags added: lightdm lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications about this bug go to:
When trying to circumvent the lock on gnome with lightdm, it seems that
the exploit only works when using gnome on X. The exploit does not seem
to work when using gnome on wayland with lightdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
When using lightdm with gnome, the exploit works in exactly the same
ways as the original bug, just by switching tty's the lock can be
circumvented.
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This bug still exists in 18.04 when using lightdm with gnome, please fix
this, it is a massive vulnerability with shared computers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock
If you have light-locker running, and do the steps in the description,
session will remain locked, but it will show desktop for short time.
This is in Xubuntu 16.04, which does not have lxsession installed. I do
not see how lxsession is affected.
--
You received this bug notification because you
any news ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications about this bug go to:
Looks like this is a duplicate of
https://bugs.launchpad.net/lightdm/+bug/904006
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To
This bug on lxsession (actually lxlock) was fixed sometimes ago, by
removing the use of dm-tools, replaced by light-locker.
** Changed in: lxsession (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still present on 16.10. I'm trying to get custom environment with just
Compiz and no Unity, but this is quite annoying bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be
This bug does not affect Xubuntu 16.04 rnuning XFCE Desktop.
This is consistent with this bug set to affect LXDE not XFCE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be
Has there been any progress with this high priority bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications about
@thezenkitteh : that link is a 404. Looks like the correct link is now:
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1205384/comments/55
Lock screen now gets me xscreensaver which seems to work (but damn it's
ugly).
--
You received this bug notification because you are a member of
To be clear: this is after after adding ppa:lubuntu-dev/staging and upgrading
or installing libjpeg-progs libjpeg-turbo-progs xscreensaver xscreensaver-data
lxappearance lxsession lxsession-data lxsession-default-apps lxsession-logout
as noted in comment 55.
--
You received this bug notification
Solution in this comment fixed this bug for me:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1205384/comments/55
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be
** No longer affects: lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications about this bug go to:
I suggest that the current lxlock script should be replaced by this:
http://bug-attachment.xfce.org/attachment.cgi?id=5295 It does not have
any specific dependency, but adds support for various screen savers and
locker utilities one of which user may install and run according to
his/her
In order to make xfce4-power-manager support lxlock for locking in
general case, you could add certain symbolic link to it:
sudo ln -s -T /usr/bin/lxlock /usr/local/bin/xflock4
This would make Xfce also use lxlock as its locker, if Xfce is installed
in the same system. Please test.
--
You
The behavior described in the previous comment is in use in current xflock4
script for Xfce desktop environment. By the way, I proposed a new xflock4
script that adds light-locker (available in Trusty) as an option for locking:
http://bug-attachment.xfce.org/attachment.cgi?id=5288
It uses
Is the problem, that xscreensaver (or any other locker application) is
not wanted as a dependency? Altrenatively lxlock could exit with an
error, if it can't find an available locking method. Please see bug
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1253046
--
You received this bug
There are no complaints of the fix, so I wonder why the fix is not
released, yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To
@gilir
Great, just the introducing comment should be updated accordingly:
# Try to lock the screen with the following applications (in this order) :
# running xscreensaver, running gnome-screensaver, slock,
# i3lock, and finally, if none of them is available, use xscreensaver.
--
You received
@ibere-fernandes
It does not work, if gnome-screensaver is running.
@gilir
What is a SRU update? The proposed fix in the PPA does not give user any other
option than to use xscreensaver, but still keeps the options hanging there in
lxlock script. If the options are wanted to be preserved,
@jarnos
SRU are update of a stable release :
https://wiki.ubuntu.com/StableReleaseUpdates
Your modified lxlock looks correct, I'll update the package to have a bit more
testing (PPA users should receive an update soon). Thanks for the help on this.
--
You received this bug notification because
one more use case/scenario:
I've just tested hibernate and also suspend (fresh installation) with
the patch described above.
Things are working as expected.
Thank you Julien.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@jarnos
The change was minimal on purpose. The goal is to include it as a SRU update,
so it needs to be as minimal as possible.
However, if you want to propose a patch to improve lxlock more, you can do it
upstream so it can be include for the next release.
--
You received this bug
Julien Lavergne, #29, why is gnome-screensaver out of the question? It
does not delay locking; xscreensaver does and reveals the desktop for a
while when resuming from suspend: Bug #1229486
Marc Deslauriers, #7, I tested that, and indeed the combination seems to
work, but only with
Now I have tested that It works for me also in a system that is
installed via OEM. Thanks at lot for solving the issue :-)
I did as described by ibere fernandes in post #55.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jarno, I new that I could lock my computer with xscreensaver it works
perfect but not with dm-tool lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by
Hmm, added the patch and now 'Lock Screen' no longer has any affect!
I'll have to bite the bullet and do a clean re-install, this system has
had a lot done to it since the alpha1 of 13.10 came out!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Elbennit, the patch does not use dm-tool, but xscreensaver to lock
screen. I am afraid there is no fix available for lightdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can
Jarno,
Thanks for your input and response!!! xscreensaver ctrl+alt+L locks
my system perfectly! I will say that adding the new staging ppa did
solve some reboot / shutdown issues on my machine!!!
Be Blessed!!!
~LuvLinuxOS~
--
You received this bug notification because you are a member of
Yes, the patch from Lubuntu-dev/staging PPA (post #55) is working fine
in OEM install ( and on OBI too). Thanks Iberê.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be
As for the lxlock from https://launchpad.net/~lubuntu-
dev/+archive/staging, xscreensaver-command -lock at line 27 is
redundant.
The script will fail, if gnome-screensaver is running and xscreensaver
is not running, when you run lxlock. Running
which gnome-screensaver-command /dev/null
I installed the patch accordint to #55 instruction on my personal
machine and it did not fix the bug! I do not have gnome-screensaver
installed but This is my production machine thus it is equiped with
quite a bit of additional packages installed.
--
You received this bug notification because
Elbenit, sorry, the second command is
xscreensaver-command -lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
Elbennit, please type
xscreensaver -nosplash
in terminal. Is there some output? If not, try
xscreensaver-command -nosplash
in terminal. Does it lock successfully or does it output some error?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
A fixed package will be available in https://launchpad.net/~lubuntu-
dev/+archive/staging
The fix is based on the script Jarno Suni submitted. It re-install
xscreensaver by default, but only start it when you launch lxlock. It
also removes the lightdm method for locking the screen. Please test it
Fresh install of saucy. System updated.
Bug is still there as expected.
Terminal:
sudo add-apt-repository ppa:lubuntu-dev/staging
Confirmed PPA addition.
sudo apt-get update
sudo apt-get dist-upgrade
The following NEW packages will be installed:
libjpeg-progs libjpeg-turbo-progs miscfiles
@L K (koziollz-v) from comment #52:
the patch will also fix your issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
It works for me in a system that is not installed via OEM. Thanks at lot
for solving the issue :-)
I did as described by ibere fernandes in post #55.
I have no time right now to test it in an OEM install, but will do it
later (I hope within 2-3 days).
--
You received this bug notification
This might be related:
After completing a full Lubuntu 13.10 install on my laptop when I
attempt to lock the screen via shortcuy (Ctrl+Alt+L) I receive the
following error:
Failed to execute child process xscreensaver-command (No such file or
directory)
--
You received this bug notification
From reading the comments and following up with this issue and the whole
process of removing 'xscreensaver' and replace it with whatever suppose
to work to lock the screen but it is not actually working, it appears
that there is/are some package or files or whatever you call it is
'still' somehow
Installing 'xscreensaver' did NOT solve the issue for me.
I will now try this workaround -
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1205384/comments/35
- and will report back :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirmed - Installing 'xscreensaver' alone will NOT fix the issue.
Confirmed - the workaround on this post:
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1205384/comments/35
Has solved the issue for me.
Indeed, NO need for xscreensaver service to start automatically so I can
I can confirm that the bug is there 2013-10-07 in an updated/upgraded
Lubuntu 13.10 i386 system installed into a USB 3 drive in the following
computer.
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-
pro-c850-19w/
I can confirm that installing 'xscreensaver' alone will NOT fix the
I should also mention that I have installed a complete Swedish language
pack, and set the system to use it globally. (I don't know if that would
make any difference, but I don't know of any other particular feature;
Standard Lubuntu updated/upgraded today.)
--
You received this bug notification
I have re-done it in the same computer with the same result, and I have
redone it in another computer (still using the same i386).
IBM Thinkpad T42:
http://www.cnet.com/laptops/lenovo-
thinkpad-t42-2373/4507-3121_7-31155666.html
-o-
But it works if I lock with
xscreensaver-command -lock
or
More details:
1. Typing error in comment #40: 2013-10-07 should be 2013-11-07
2. My systems of Lubuntu13.10 i386 are made via OEM (final installations
but via OEM). Maybe that makes a difference concerning the locking
ability.
--
You received this bug notification because you are a member of
sudodus, you told in #40 that workaround #35 did not work for you. Did
you get any error messages when running the commands in terminal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
If you already have some lxlock file in /usr/local/bin directory before
doing the workaround mentioned in comment #35, it may fail. You may want
to delete the old lxlock in /usr/local/bin/ before trying the
workaround.
--
You received this bug notification because you are a member of Ubuntu
No I saw no error messages. I'll try to delete lxlock and try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
I instructed to download the script to /usr/local/bin/ since you don't
have to overwrite the original lxlock script in /usr/bin/ in that case,
but it will be used instead of the original, if the /usr/local/bin is
before /usr/bin in PATH environment variable (and not full path is used
in the
echo $PATH
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
so /usr/local/bin is before /usr/bin in my user's path.
But what about root's path? Maybe /usr/bin/lxlock will be used that way?
-
/usr/bin/lxlock:
...
# Try to lock
After wiping and downloading /usr/local/bin/lxlock again, I can still
log in without any password via 'ctrl + alt + F1-F6'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be
sudo echo $PATH
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
so /usr/local/bin is before /usr/bin also in root's path. But if
/usr/bin/X11/lxlock has priority ...
--
You received this bug notification because you are a member
sudodus, lxlock and xscreensaver only protects the desktop (case Ctrl +
Alt + F7), not the virtual consoles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by
@Julien: Hi, when should we expect a fix/bypass? This is a pretty bad
bug... Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
is sudo apt-get install xscreensaver a good workaround while ligthdm
implementation is not finished?
i've installed xscreensaver on my Lubuntu 13.10 test machine (fresh
install) and lock was not being circumvented anymore.
--
You received this bug notification because you are a member of Ubuntu
@ibere
Most likely I will try this on my test machine and report back ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
Please note that lxlock between the sudos is a part of the preceding
command's URL option on #35, even if it is wrapped on separate line
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
A workaround is to do this on terminal:
sudo apt-get install xscreensaver
sudo wget --directory-prefix=/usr/local/bin/
https://launchpadlibrarian.net/154739229/lxlock
sudo chmod a+x /usr/local/bin/lxlock
You may also want to start xscreensaver as an automatically started
application, but that
This bug affects me too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications about this bug go to:
In my case:
Lubuntu 13.10 amd64
Menu Logout Lock Screen
ctrl+alt+F1
ctrl+alt+F7
Result: session is unlocked without entering a password
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Actually, xscreensaver does not need to start at startup; the daemon can
be started within lxlock, if needed. But xscreensaver needs to be
installed, of course. I wrote a replacement script for lxlock that tries
to lock by xscreensaver; see the attachement for more details.
Still, there is a
I can confirm this bug on lubuntu 13.10 amd64.
The workaround I chose (following #22) was to:
1) Install suckless-tools: sudo apt-get install suckless-tools
2) edit /usr/bin/lxlock (sudo nano /usr/bin/lxlock). It tries to trigger screen
locking using various tools, one of them is in fact slock,
If you don't want to change the original lxlock script, you can copy the
script to /usr/local/bin/ and change it there. The modified script will
be used, since the local directory is mentioned earlier in the
environment variable called PATH. Upgrading the operating system will
not change the
This bug needs to be forwarded upstream
(https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding_upstream).
** Also affects: lxde
Importance: Undecided
Status: New
** Changed in: lxsession (Ubuntu)
Importance: Undecided = High
** Changed in: lightdm (Ubuntu)
Importance: Undecided =
The lightdm locking facility is an unfinished work, and lack a proper
way to lock the session, it started at the begin of the cycle, and was a
bit forgotten later in the development. It's unfortunate that it went
into the release in this state.
That's said, the less invasive way I can see to fix
Well, #19 describes a workaround, but it requires using a package from a
PPA repository https://launchpad.net/~light-locker/+archive/release .
Another workaround that uses a package from Universe repository of
Ubuntu and works around Bug #1229486, too, is here: Install suckless-
tools, edit
I was trying to tell in the previous comment: Note that slock does not
even display password prompt, but a blank screen you have to type
password in, and there is no way to make a new login by slock. However,
if you run slock and then dm-tool switch-to-greeter in lxlock, you
have that ability.
As for #19, the workaround stopped working in my last session for some
reason, i.e. Ctrl+Alt+F7 bybassed password prompt again. Logging out and
in again made it work again. I would not call light-locker reliable,
yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm this bug on lubuntu 13.10 amd64.
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
Ibere Fernandes, as for #9 can you also bypass the password prompt in
logging in, and not just bypass the prompt when unlocking a running
session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Jarno, when not logged into a session pressing ctrl-alt-f7 goes to a
blank, black screen with a cursor in the upper left corner. Pressing
ctrl-alt-f8 brings back the login screen. It looks like you have to be
logged in for this bug.
--
You received this bug notification because you are a
So far 5 people have told the bug affects them. As for the article
mentioned in #9, it is incorrect: you can not bypass password prompt by
Ctrl + Alt +7, but by Ctrl + Alt + F7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to be clear, this isn't a lightdm issue.
Something needs to lock the user's session before switching to the
greeter.
This can either be gnome-screensaver or xscreensaver, and the lxlock
script has to tell them to lock before switching to the greeter.
** Changed in: lightdm (Ubuntu)
If lightdm is installed, then lxlock will use dm-tool for screen
locking. dm-tool is part of lightdm. It seems to be the same if you use
dm-tool switch-to-greeter or dm-tool lock. Aren't these supposed to
lock user's session? I do not see the point why you would have to use
another lock utility
Something has to draw a window over the user's session. Lightdm does
_not_ do this.
If you use dm-tool to tell lightdm to lock the screen, it calls logind
over dbus, and whatever you use in the user's session to hide the screen
needs to receive the dbus signal from logind to lock the screen. In
On top of that, dm-tool switch-to-greeter does exactly what it is
suppose to do, it switches to the greeter and does _not_ ask the session
manager to activate the screen lock for the activate user session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Would it be accepted, that lxlock were changed not to use dm-tool at
all, but other means such as slock which does not run on any daemon and
would not listen to dbus signal anyway?
Another option, if dm-tool is used, would be to use the command dm-tool
switch-to-greeter preceded by some command
I tried installing this light-locker and logging out and in:
http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
Thereafter Ctrl-Alt-F7 will not bypass the greeter anymore, no mater whether
you use light-locker-command -l or dm-tool lock or dm-tool
switch-to-greeter to bring
My fault. Apparently it also locks the active user session (and allows
user switching).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
Jarno Suni,
in reply to #11 and #13:
a) you need to be logged in, then follow the steps:
- lock the screen with Shutdown Lock Screen ;
- on lightdm screen, just do ctrl+alt+F7 : you arrive on the desktop, without
typing any password.
b) althought the webupd8 article mentioned Ctrl + Alt + 7,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxsession (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
** Also affects: lxsession (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage notifications
You need to lock the screensaver before using the dm-lock tool to switch
to the greeter.
For example:
gnome-screensaver-command -l
dm-tool switch-to-greeter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I reproduce this whitout needing to switch tty (Lubuntu 13.10) :
- lock the screen with Shutdown Lock Screen ;
- on lightdm screen, just do ctrl+alt+F7 : you arrive on the desktop, without
typing any password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: lightdm (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To manage
hi,
i've just done a fresh install of Lubuntu saucy 13.10 and I can confirm
that lightdm is not keeping the system locked.
Comment #8 is correct.
- lock the screen with Shutdown Lock Screen ;
- on lightdm screen, just do ctrl+alt+F7 : you arrive on the desktop, without
typing any password.
find attached the lightdm log.
** Attachment added: lightdm log
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1205384/+attachment/3883010/+files/lightdm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can't anybody reproduce this?
** Description changed:
Steps to reproduce:
- 1)lock your screen
+ 1)lock your screen using dm-tool switch-to-greeter or dm-tool lock
2)switch to console via ctrl+alt+F1
3)switch back to X via ctrl+alt+F7
Result: session is unlocked without entering a
** Summary changed:
- Lock can be cirumvented by switching to console
+ Lock can be circumvented by switching to console
** Description changed:
Steps to reproduce:
1)lock your screen
2)switch to console via ctrl+alt+F1
3)switch back to X via ctrl+alt+F7
- Result: session is unlocked
Thank you for your bug report, I can't confirm that. How do you lock the
screen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205384
Title:
Lock can be circumvented by switching to console
To
Your response time is astonishingly quick, thanks for that!
I've been calling lxlock (lxsession package) which is essentially just a script
file calling
dm-tool switch-to-greeter
I just verified that calling this directly from a terminal and then following
my steps to reproduce leads to the
98 matches
Mail list logo
