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 bec
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
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
> wrote:
>
>> I have this problem but can access the desktop using SSH. Is there a
>> process I can kill/restart to
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:
&g
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 si
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. T
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
We use the same setup, and have had the same experiences:
1) LDAP configuration hasn't changed in years
2) Login screen works fine
3) Home areas are served via NFS+automount
4) Problems only appeared after installing 14.04 (we did fresh installs
though, not upgrades)
Michael Peek
On 12/08/2014 03
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 issue,
> You need to enable accessibility (e.g. on screen keyabord) from the control
> center.
>
> 2014-12-09 14:56 GMT+01:00 msp3k :
>
>> 1) Maybe I'm just derping, but how do I run gnome-screensaver?
>>
>> $ ps -ef | grep -i screensaver
>> peek 24604 24163
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 09:15
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 s
12 matches
Mail list logo
