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
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
Quoting 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.
Can you give more detail how to do this? Man pages have no mention of
debug at all.
My entire pam.d/unity looks
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 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
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
Hi Andrea,
Thanks for the reply. It wasn't until I posted that I noticed my unity
version was still old. Goes to show I shouldn't make assumptions about what
gets updated!
Cheers,
Robin
Robin, a fix for this issue is scheduled for next SRU (almost ready!).
Resetting unity from tt1 should be just
Robin, a fix for this issue is scheduled for next SRU (almost ready!).
Resetting unity from tt1 should be just fine. Or you can run metacity
--replace.
2015-01-08 17:01 GMT+01:00 nybbler nybble...@gmail.com:
I've just run into this with Ubuntu 14.04.1, updated today at about
15:45. I didn't
It's a dfferrent new bug. I think there is already a similar bug open. What
languages are you using? Please try to unlock after changing the language
in the keyboard indicator.
On 7 Jan 2015 09:41, Páll Haraldsson pall.haralds...@gmail.com wrote:
Do you have multiple keyboard layouts?
Yes, BUT
Do you have multiple keyboard layouts?
On 6 Jan 2015 16:11, Páll Haraldsson pall.haralds...@gmail.com wrote:
I had a new development.. Maybe I should report as a new bug? In case
this helps anyone as a workaround or to fix the bug I thought I would
post here:
I had the lock screen complain
On 12/10/2014 09:24 PM, Andrea Azzarone wrote:
Please consider answering the question markes ad *** IMPORTANT *** in the
description.
2014-12-11 1:26 GMT+01:00 harrychillboy 1311...@bugs.launchpad.net:
Bug description:
*** IMPORTANT **
If you can reproduce this bug please be sure to
1) The bug just bit my boss again. Here's the auth.log:
Dec 10 09:13:23 anolis compiz: PAM unable to dlopen(pam_kwallet.so):
/lib/security/pam_kwallet.so: cannot open shared object file: No such
file or directory
Dec 10 09:13:23 anolis compiz: PAM adding faulty module: pam_kwallet.so
Dec 10
Please consider answering the question markes ad *** IMPORTANT *** in the
description.
2014-12-11 1:26 GMT+01:00 harrychillboy 1311...@bugs.launchpad.net:
These lines appear as error meesages in auth.log
Dec 10 07:26:10 ThinkPad dbus[724]: [system] Rejected send message,
1) Maybe I'm just derping, but how do I run gnome-screensaver?
$ ps -ef | grep -i screensaver
peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i screensaver
$ gnome-screensaver
** (gnome-screensaver:24665): WARNING **: screensaver already running in
this session
2) If this is an LDAP
You need to enable accessibility (e.g. on screen keyabord) from the control
center.
2014-12-09 14:56 GMT+01:00 msp3k p...@nimbios.org:
1) Maybe I'm just derping, but how do I run gnome-screensaver?
$ ps -ef | grep -i screensaver
peek 24604 24163 0 08:51 pts/47 00:00:00 grep -i
Okay, I set System Settings Universal Access Typing On Screen
Keyboard = On
Then I hit alt+control+L to lock.
Sure enough, I got what looks like gnome-screensaver.
Via an SSH login I confirmed that gnome-screensaver was indeed running,
and running as me and not as root.
Entering my password
Because we don't show a text entry if PAM (the authentication module) does
not respond correctly. We wait for PAM to ask the passoword not the
opposite, and if PAM fails there is nothing we can do about. Briefly PAM
works like that: we ask to authenticate the current user, pam responds
asking us
I must have missed something. Permissions on what path? And what
should the permissions be?
Michael Peek
On 12/06/2014 09:03 AM, Andrea Azzarone wrote:
We released a fix but it does not work. The one we released was about
text entry not showing randomly on multimonitor and seems to be fixed.
Please consider sending me in private the auth.log file.
On 5 Dec 2014 11:26, Philipp Wendler 1311...@bugs.launchpad.net wrote:
We also have this problem on several machines, and I hope I can contribute
to getting it fixed.
Removing light-locker fixed the double unlock problem, but not this
I am using ldap as well.
Out of 80 hosts and 110 users this bug only affects one user on one host.
(Unfortunately that user happens to be one of my bosses.)
It's irregular, but frequent.
Michael Peek
On 12/05/2014 09:06 AM, Andrea Azzarone wrote:
@Philipp also I just read you are using ldap.
Light-locker is not installed on our machines.
On 12/01/2014 10:56 AM, LGB [Gábor Lénárt] wrote:
I don't know if it helps, but I always had problems like no input field
for password or the double unlock (if the first problem does not
occur, unlock presented another unlock field with a sightly
Out of 90-somethign users this bug only seems to affect one user. (Of
course, that user happens to be one of my bosses...) Because the
problem is hard to reproduce I have a feeling that it'lll be difficult
to track down and fix.
Michael
On 11/03/2014 05:18 PM, Bruce MacNaughton wrote:
msp3k
I would like to know the answer to that as well. Back in the good 'ol
days the screen lock was a separate process, and pkill -9
gnome-screensaver would bring back the desktop. But now...? There is
a process called /usr/lib/unity/unity-panel-service --lockscreen-mode,
but if I kill -9 on it, it
When I do that, I get the desktop back, but no dash, launcher, or panel.
On 11/03/2014 08:54 AM, Erik wrote:
unity --replace
On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton bmacnaugh...@msn.com
wrote:
I have this problem but can access the desktop using SSH. Is there a
process I can
Suggest to try patch - in comments of this thread.
It's helped me.
2014-10-18 11:43 GMT+04:00 harrychillboy 1311...@bugs.launchpad.net:
This is annoying and specially happens while working on dual monitors with
my laptop. Its has intel hd4000 builtin graphics.
* password input will be
I've used my laptop with built in display since the release of 14.04
(upgraded from 13.10) and did never see this issue until I started connect
a second display, then I've been getting this issue. It's definitely dual
screen related.
I've also been seeing this issue on my computer at work, also
27 matches
Mail list logo
