** Tags removed: rls-w-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage notifications
** Also affects: unity (Ubuntu Trusty)
Importance: Undecided
Status: New
** No longer affects: unity (Ubuntu Xenial)
** Also affects: unity (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu Xenial)
Status: New => Fix Released
** Changed
Well, we have a bug related to this: Now everytime second user get
logged, we're seeing "Authentication Failure: Switch to greeter"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package unity - 7.4.5+16.04.20171201.3
---
unity (7.4.5+16.04.20171201.3) xenial; urgency=medium
[ Marco Trevisan (Treviño) ]
* InputMonitor: add an unity class that monitors XInput2 events and
converts them to XEvent
* EdgeBarrierController: use
I can't reproduce the issue, but for sure this fix doesn't bring any
regression, while we didn't get any report of this happening with unity
7.4.5+16.04.20171201.3, so we can safely mark this as verified.
Feel free to reopen in case.
** Tags removed: verification-needed
=/ I'm also facing this issue. The curious part is that the issue happens more
if I take a while to reboot the machine. I mean, if I don't reboot and just
put the machine to sleep this issue start to happens more and more. I also
realized that when I use two different users in the machine it
I'm using 16.04 with this kernel 4.13.0-26-generic and this unity
version: 7.4.0+16.04.20160906-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is
Unable to reproduce the bug (in VirtualBox - low graphics mode, single
monitor) so I can't verify the fix. Unable to switch to non-lowgfx
because I get 'No such key 'lowgfx'' when trying to run `gsettings set
com.canonical.Unity lowgfx false`.
--
You received this bug notification because you
@Andrea:
@include common-auth
auth optional pam_gnome_keyring.so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password
Can you check the output of "cat /etc/pam.d/unity" ?
On Mon, Jan 8, 2018 at 10:03 PM, Markus Birth <1311...@bugs.launchpad.net>
wrote:
> @Andrea: Yes, no "switch to greeter" for me anymore. But still I get the
> LightDM lock screen (with working password field) instead of GDM3.
>
> --
> You
@Andrea: Yes, no "switch to greeter" for me anymore. But still I get the
LightDM lock screen (with working password field) instead of GDM3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
works just fine here on my lenovo lappy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage
@Markus do you get it all the times?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage notifications
Maybe regression? -
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input
A few reboots later, I'm now able to unlock the notebook from the
LightDM lockscreen. There's no "switch to greeter" anymore, but a real
password entry field which works. However, I still don't know why I had
the GDM3 lockscreen before.
--
You received this bug notification because you are a
Using the "Switch to greeter..." button you should be able to login
without any Ctrl+Alt+F1 press, isn't it?
Andrea might help more here, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Just for the record: I had Ubuntu 17.10 (upgraded from 17.04 which was
upgraded from 16.10) running on my HP Spectre x360 just fine with GDM3
and Unity and when the screensaver kicked in or I locked the screen, it
turned to the GDM3 greeter.
A few days ago, I cleared my SSD and installed 17.10
I wanted to install proposed package but there seems to be an issue of
dependencies I can not resolve (see below). Please provide a novice
instructions how to install this. Thanks.
username@username-G501JW:~$ sudo apt-get install unity/xenial-proposedReading
package lists... Done
Building
Hello LGB, or anyone else affected,
Accepted unity into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/unity/7.4.5+16.04.20171116 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
*** IMPORTANT **
*** The fix is not included in TRUSTY. Will be included with next SRU.
***
If you can reproduce this bug please be sure to provide the following info:
1. Do you use a multi-head setup? If yes, using just one monitor fixes the
issue?
2.
This is getting wores.. The workaround mentioned above "@Klemen, as a
work around I make sure that a second user is logged in (most of the
time one of my children). If I am locked out, I can switch to a
different X-session (ctrl-alt-f8 or so) and then switch to my user with
the menu in the top
@azzar1: I faced today again this issue, after install the modified
Unity from the PPA. I resumed after suspend. Yesterday all the family
logged in.
Unfortunately, the content of ~/.cache/upstart/unity7.log is a single
line:
ATTENTION: default value of option force_s3tc_enable overridden by
This has been bugging me for some time. Out family of 3 switch users and
it happens randomly for some users while others still work.
The only workaround I got is that I made a dummy user that I always
login on terminal 7. When any in the family gets this problem they hit
CTRL+ALT+F7 to that user
And the "fix" doesn't work as I'm using Unity 7.4 on Xenial LTS patched
up with the newest fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input
I would suggest one of the following options:
1. $ unity
2. login/logout
3. reboot
compiz --repalce will fail because compiz will not be started by upstart
and logging will be send to stderr/stdout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Andrea: is a restart required or a `compiz --replace &` is enough?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
Hi, I pushed on this ppa [1] a modified unity7 with more debugging. Can you
please:
1. $ sudo add-apt-repository ppa:azzar1/unity7-testing
2. $ sudo apt-update
3. $ sudo apt upgrade (make sure unity is updated)
4. $ unity
Lock the system, after the problem happens write somewhere at what time the
Well, I did an update this weekend and now I am not seeing the problem
any longer. I'm not sure what got updated or how it fixed it but I am
able to move the mouse and the login screen comes back and I am up and
working again.
--
You received this bug notification because you are a member of
Not sure if this is important, but I can notice the following: if I
switch to the second (or any other than me) logged user (Ctrl + Alt +
F8), it works normally. I can, then, in second Xorg session, select my
user from indicators and then log in.
And, I'm not sure if this is related, but appears
The lack of indicators might indicate a problem on the upstart user
session. This upstart failure can confuse PAM as well. I'm going to
propose a branch that will allow the system to lock if there are such
types of failures.
--
You received this bug notification because you are a member of
@Andrea, sorry, just now I got able to take a shot from the screen using
my mobile. And you were right: no icons in indicators.
Yesterday, several users logged in my machine, then, during the night,
screenlock was activated.
** Attachment added: "cannot-login-2017-07-31.jpg"
@Andrea, sure, as soon as I face this issue I'll capture it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
@Andrea, yes, the username is properly displayed above the missing
password input field.
@Mark, you have to:
1. go to a TTY (press Ctrl + Alt + F1 to open it) and run this command: sudo
loginctl unlock-sessions
2. get back to X.org (press Ctrl + Alt + F7)
3. now restart compiz with: compiz
can you post a capture of the full lockscreen?
El 30 jul. 2017 4:20, "Mark Elston" <1311...@bugs.launchpad.net>
escribió:
> Here is a capture of the top row of the lock screen.
>
> And, it seems that neither the `compiz --replace` nor the `unity
> --replace` works for me. I get back my desktop
Here is a capture of the top row of the lock screen.
And, it seems that neither the `compiz --replace` nor the `unity
--replace` works for me. I get back my desktop but can't interact with
it.
** Attachment added: "Top row of lock screen"
My lock screen simply shows the system name. Not the user name.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
@rael-gc what about username as per screenshot? I'm trying to understand
if somehow unity fails to start the pam auth flow.
** Attachment added: "Screenshot from 2017-07-29 19-42-56.png"
@Andrea, yes, indicators are properly displayed. The only missing item
in the screen is the field to input the password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking
I'm seeing the issue as well and I see the top panel shows up like in
your screenshot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to
Hi all,
can you please tell me if when this happens the top panel (in the
lockscreen) is correctly displayed with all the indicators like in the
attached screenshot. I'm trying to understand if this is a rendering
issue or a PAM one.
Thanks!
** Information type changed from Public Security to
1. Yes, multi-head setup.
2. It appears to happen always when I have users switching and locking screen
(my wife and kids uses my machine and I see this happen when they start to use).
3. Never used ldap in this machine.
4. /var/log/auth.log:
Jul 24 11:36:10 rael-m3800 lightdm: PAM unable 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/1311316
Title:
After locking screen there is no input field to type password for
unlock
This bug is right now hitting me too. I see just the mouse cursor when
trying to unlock. No fields, no letters, no menu, nothing.
- Current Ubuntu Xenial HWE Ubuntu 16.04.2 LTS
- No multi-head setup.
- It happens to me all the time when the screen is locked.
- No ldap
- Unity version Version:
This really isn't acceptable for our use. We may have a rather smallish
organization (I manage 103 Ubuntu machines, most of them user-facing
workstations) but we are a national research institute and we give Linux
and Ubuntu international attention every time we have a group of
scientists arrive
@Klemen, as a work around I make sure that a second user is logged in
(most of the time one of my children). If I am locked out, I can switch
to a different X-session (ctrl-alt-f8 or so) and then switch to my user
with the menu in the top left corner. Then I can enter my password.
--
You
No. It is this bug. It is exactly as screenshot I found on the right:
https://launchpadlibrarian.net/192258901/Screenshot%20from%202014-12-10%2009%3A21%3A32.png
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Klemen I wonder if it's really this bug, or if it is the infamous bug
in Linux 4.4/4.3 that causes text to mess up and icons to not appear
correctly?
https://bbs.archlinux.org/viewtopic.php?id=209065
This is not funny any more... Ubuntu 16.04 desktop is not usable any
more...
The issues described by posters above used to happen to me only once per
14 days... Then once per week... And now it happens daily. I can not use
the system. The only way is to power off the computer and power it back
I see I'm not the only one having this problem. Running Ubuntu 16.04.2
LTS, light-locker not installed, Unity 7.4.0+16.04. I haven't found any
workaround yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see I'm not the only one having this problem. Running Ubuntu 16.04.2
LTS, light-locker not installed, Unity 7.4.0+16.04. I haven't found any
workaround yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What the beep? A bug, 3 years old which is still bugging people and the
bug report says "Fix Released"???
Has anyone found a workaround which does not include typing hackish-
looking commands, which my wife and kids cannot do? Has anyone tried
using xscreensaver and that worked as a workaround?
Unity 7.5.0+16.10. and it still happens. light-locker is not installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password
Unity 7.4.0 on Ubuntu 16.04 and this happened FOUR times today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
@igor-lopez described perfectly what happens here (switching users then
get back from lock screen).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no
Using 16.04.1 on a dual monitor.
Still facing this issue several times after get back from lock screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no
I don't have a dual monitor or anything, when I opened the lid of my
laptop in the morning the usual login/unlock screen did not display a
password prompt, it just showed my name and no buttons, no text inputs,
nothing.
This was the workaround that worked for me (from another pts/vc):
DISPLAY=:0
running 16.04.1
Fujitsu Lifebook E752
single head.
no screensaver that i know of.
i don't use locking, but when returning from sleep the screen is locked.
so far, most of the times the pw-field is there, but not usable.
i also think that there should be icons in the top right corner and a clock
I have had this bug since I installed 16.04 (Not an upgrade)
It does not happen often but when it happens it is always when returning to my
normal user id after having switched to another user id.
So basically I click upper right corner and selects another user, say user2,
when I am logged in
I also started having this issue after upgrading from 15.10 to 16.04.
Sometimes I can see the flicker of the gnome-screensaver-dialog showing
up, but most of the time I just see my previous screen, without anywhere
to type in the password, and everything locked (nothing is interactive).
Typing
@Jung-Kyu Park: Thanks, I subscribed to that bug. However, that bug
doesn't reference anything regarding no input on the password field when
resuming from suspend, so I still suffer from this bug (1311316).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Jeremy and Lesam if you use intel graphics, I think it is proper to you
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1568604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm still having this problem even after all the latest updates. The
status says "fixed released" but I'm still facing this issue. I'm using
Ubuntu MATE 16.04. This doesn't happen every time, but sometimes when
resuming from suspend, I cannot type my password. The work-around that
works for me is
16.04, intel chip, dual monitor, same problem. Although just hitting
Ctrl + Atl + Fx and back solves it without needing to kill unity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
I'm on Ubuntu 14.04.4 LTS Trusty. This report applies to a few weeks
back (was at least 14.04.3).
If I recall, I did get the input field (but months earlier I got no
input field onces in a while).
Sorry, I forgot to report, but then could reproduce easily, since memory
was low. If I locked the
Same problem here. I cannot recover even using lightdm, so I have to
reboot. I now when this is going to happen because first only one of the
input field is locked. Then, next time I lock my account both are
locked. This is about to happen now, so you can check my current
auth.log
1. Do you use a
** Tags added: rls-w-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage notifications about
I think I have something similar but then I use ubuntu 14.04 gnome with
gdm so I don't think it is unity/light-dm related
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking
This bug started manifesting on 14.04.02 LTS after installing updates
today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type
Problem occurs with up-to-date Ubuntu 14.04.2 on Dell Inspiron 7348.
Ctrl+Alt+F2 and service lightdm restart does the trick (with work lost of
course).
1. Do you use a multi-head setup? If yes, using just one monitor fixes the
issue?
No multi-head
2. Can you reproduce all the time?
If a
I tried reverting back to 3.13.0-45, but the session still crashes when
the screen times out while the mouse is positioned over the VM. Next I
will try reverting Unity versions, if that is possible. Kernel is back
to 3.13.0-51.
One other item - if the screen times out with the mouse in the
I have 14.04 LTS with the latest kernel update that is pushed out to
update-notifier, applied today.
I don't appear to have ldap as it is not currently running.
I ran my VM with only the built-in screen today, but I did not experience the
session crash.
auth.log from today attached with names
I was experiencing similar problems to post #32 above using VMware
Player 6, latest version.
Dual monitors. I don't recall seeing the problem with only one, i.e. the
built-in laptop one.
Problem did not occur every time - only after some varying amount of run time.
AFAIK I don't use ldap, but I
Hello, I have experienced this bug a few times even with the posted
fix. Would it be possible to reopen? 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/1311316
Title:
After locking
Okay, after some auto-updates made to 7.2.4 the problem never
reoccurred.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password
The bug is not fixed.
I happened again with 7.2.4.
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
@Andrea, I did not have light-locker.
I just manually upgraded to 7.2.4 (apparently you do this by typing sudo
apt-get dist-upgrade).
Will let you know if this happens again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Andrea is This fixed included for 15.04 as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage
Yes.
On 25 Mar 2015 11:05, Daniel Halvorsen 1311...@bugs.launchpad.net wrote:
@Andrea is This fixed included for 15.04 as well?
--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input
@Jonathan do you have light-locker installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage
And btw do you need 7.2.4+14.04.20141217-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage
So:
$ dpkg -l unity
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
And btw you need 7.2.4+14.04.20141217-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To manage
How do I obtain the fix?
This still happens.
I have Ubuntu 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
My understanding is that if you type:
dpkg -l unity
And see the version number 7.2.x, then you have the patch.
Michael Peek
On 03/18/2015 05:11 AM, Jonathan Laserson wrote:
How do I obtain the fix?
This still happens.
I have Ubuntu 14.04 LTS.
--
You received this bug notification
I have this problem too.
Ubuntu 14.10 x86_64
Unity 7.3.1+14.10.20141016-0ubuntu1
Using a multi seat setup (2 users working the same time on different
screens connected to different VGA cards).
BTW, I use sudo loginctl unlock-sessions as a workaround.
Very harmful bug and hurts a lot the Wife
The fix for this was included in some other fixes released into Ubuntu
14.04 LTS in Unity 7.2.4 (see bug #1308540).
** Changed in: unity/7.2
Status: In Progress = Fix Released
** Changed in: unity/7.2
Milestone: 7.2.5 = None
--
You received this bug notification because you are a
** Changed in: unity/7.2
Milestone: 7.2.4 = 7.2.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
To
Is there a fix for this bug? If so, how do I apply it? It happens to me
every 4-5 days.
Here is the tail of my /var/log/auth.log:
Mar 3 19:17:01 genovo CRON[28307]: pam_unix(cron:session): session closed for
user root
Mar 3 20:06:49 genovo compiz: PAM unable to dlopen(pam_kwallet.so):
Can any of the people still experiencing the problems to add 'debug' to
in /etc/pam.d/unity to each of the modules used and potentially post
some of their /var/log/auth.log. For me I found this is an issue of the
PAM module for fprtind giving me:
Feb 23 12:52:23 botev-ThinkPad-T440 unity[2008]:
After another ~2 days and a bunch of hibernations I can confirm that
uninstalling Light-locker did the trick for me. I experienced absolutely
no problems in whatsoever. It even fixed two other bugs related to
login here.
Thanks again!
--
You received this bug notification because you are a
From the auth log file. There was nothing about unity, but a lot of logs
created by lightdm. Because you confirmed that you were locking/unlocking
the phone I thought about light locker.
On 17 Feb 2015 21:31, Burko rs...@web.de wrote:
I just did. Im curious how it will turn out. I just rebooted,
It was a login or a lock/unlock?
On 17 Feb 2015 16:21, Burko rs...@web.de wrote:
I updated my machine recently to the current Unity 7.2.4 and this
solved this issue for some time.
BUT: Now I am experiencing it again, exactly 50 % ( that is actually 25 %
of time, see below) of times I log
I am afraid I don't know what you mean. I try to explain it a bit more:
It was a login after a suspend, meaning a unlock-lock.
I was already logged in and hibernated the machine. Then I waked it up again,
so in that way it was a lock-unlock. But just considering the unlock procedure
it was an
I updated my machine recently to the current Unity 7.2.4 and this
solved this issue for some time.
BUT: Now I am experiencing it again, exactly 50 % ( that is actually 25 % of
time, see below) of times I log into my maschine. My case if different, though.
When my Laptop wakes up from sleep I
I think you are still using it. Please try to unistall it.
On 17 Feb 2015 19:35, Burko rs...@web.de wrote:
Yes, I do. However, I thought that is part of LXDE. And I only have an
old install of XFCE which I installed back in the 13.10 days,
--
You received this bug notification because you
I just did. Im curious how it will turn out. I just rebooted, so I will
anticipate how long everything works out as expected.
How did you came across this assumption that I have light-locker
installed? Did I miss a hint?
--
You received this bug notification because you are a member of Ubuntu
Do you have light locker installed?
On 17 Feb 2015 18:11, Burko rs...@web.de wrote:
I am afraid I don't know what you mean. I try to explain it a bit more:
It was a login after a suspend, meaning a unlock-lock.
I was already logged in and hibernated the machine. Then I waked it up
again, so
Yes, I do. However, I thought that is part of LXDE. And I only have an
old install of XFCE which I installed back in the 13.10 days,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
I see this on systems with LDAP, and systems without. It's just happened
on this machine, which is built from scratch about 1 week ago. It's with
a new user - so all the user config is as created by a new clean Ubuntu
system. I haven't customised PAM at all.
I see lots of failures in auth.log,
I have the same bug as described on my fresh install of Ubuntu 14.04, however
I'm with a newer kernel because of problems with my wifi drivers in previous
versions, which were fixed:
Linux
3.17.3-031703-generic
#201411141335 SMP Fri Nov 14 18:36:40 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
1 - 100 of 252 matches
Mail list logo
