As xflock4 is just a script to issue lock command with whatever
screensaver/locker is in use, I juast started to suspect some kind on
race condition, where screen lock has not enough time to activate on
start of suspend sequence.
As crude workaround I tried to add a script in /etc/pm/sleep.d, whic
There's more to it - commands with --quit and --restart options won't do
anything
~$ ps -ef | grep power-manager | grep -v grep
u**+ 25698 23969 0 00:45 ?00:00:00 xfce4-power-manager
~$ xfce4-power-manager --quit
~$ ps -ef | grep power-manager | grep -v grep
u**+ 25698 23969 0 00
There seems to be quite a mess with xfce4-power-manager
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-
manager/+bug/973778
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137
Title:
"Lock
It is actually a desktop computer. Suspend is made from logout-dialog.
There might actually be one other problem related to this, because power
manager settings can not be accessed properly - something quite similar
to report #1302244.
--
You received this bug notification because you are a memb
Then we have another problem - although "Lock screen before sleep" is
checked in xfce4-session, screen remains unlocked on resume if light-
locker has --no-lock-on-suspend variable set.
Manual activation of xflock4 locks screen though. Problem might be in
xfce4-session then.
All in all - if --no-
** Information type changed from Private Security 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/137
Title:
"Lock on suspend" variable cannot be set
To manage notifications ab
I just tried a bit of "surgery" - I made a new installation (from the
scratch) into Virtualbox and took all contents of /etc/pam.d and merged
it into my main system - the one with this bug - thus overwriting files
with new ones but keeping all additional files - not from the system
itself - untouc
Well... as stated in #34 status us set to Fix released for gtk+3.0, but
what about Saucy users? Do we have to move on using Trusty to get this
bug fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
If this bug is marked as confirmed for lxdm, then it must also be marked
as such for lightdm as same workaround is applicable for both of them in
case of a problem as seen in #33 - which was my case BTW.
Of course it depends on which display manager is used as only one can be
in use at a time - Ub
Both of my installations were upgraded by means of Update Manager in
usual way, however one of them did not show this problem. Both are
64-bit.
About this reference to previously mentioned archlinux thread - it looks
quite obvious, that problem poassaibly had some relation to lightdm,
because it w
Just a small addition - my problem was also present on login screen as
it was not possible to issue shut down or restart command from there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240336
Title
Well... I am not sure, whether it will help or not, but I had two
installations upgraded 13.04 -> 13.10.
One worked fine, other one got this very same problem. I am not
completely sure, is this crude workaround or not, but I found help in
this archlinux forum thread as all symptoms were the same.
This is occuring now with Maverick and in interesting way - if numlock
is activated in BIOS settings, then it is on initially, but very shortly
after the grub menu numlock LED goes OFF and stays off.
I previously had the numlockx on in XFCE startup and it worked before.
As I primarily use XFCE as
I had the same problem before on Lucid, when I tried the updates from
the kubuntu-ppa repositories, which gave the 4.7 version of qt. I tried
this repeatedly and always rolled back because of this problem.
Now with Maverick there's nowhere to roll back to, but luckily there
just might be a solutio
*** This bug is a duplicate of bug 322518 ***
https://bugs.launchpad.net/bugs/322518
I should note here, that this all happens, when connection is managed
using NetworkManager - as if in clean unaltered install.
I put this bug initially under gnome-system-tools, because the situation
is kind
As I said before, this appeares in syslog, when the network connection
is established - I discovered it initially, when I was trying to "debug"
the problems with the wireless connection on laptop.
The problem is not that the ntpdate runs all time in the background, but
the script /etc/network/if-u
Public bug reported:
Binary package hint: gnome-system-tools
$ lsb_release -rd
Description:Ubuntu 10.04 LTS
Release:10.04
$ uname -a
Linux U-001 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010
x86_64 GNU/Linux
$ apt-cache policy gnome-system-tools
gnome-system-tools:
17 matches
Mail list logo