[Bug 1322227] Re: "Lock on suspend" variable cannot be set
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, which will just make a 3 s delay on start of suspend/hibernate sequence and it looks like problem is cured... -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973778] Re: Unable to connect to Xfce Power Manager
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:45 ?00:00:00 xfce4-power-manager u**+ 25705 23969 0 00:45 ?00:00:00 xfce4-power-manager --quit ~$ xfce4-power-manager --restart ~$ ps -ef | grep power-manager | grep -v grep u**+ 25698 23969 0 00:45 ?00:00:00 xfce4-power-manager u**+ 25705 23969 0 00:45 ?00:00:00 xfce4-power-manager --quit u**+ 25711 23969 0 00:45 ?00:00:00 xfce4-power-manager --restart because it seems like initial instance of xfce4-power-manager "does not exist" for session manager? Maybe this explains these "did not receive a reply" messages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973778 Title: Unable to connect to Xfce Power Manager To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/973778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322227] Re: "Lock on suspend" variable cannot be set
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 on suspend" variable cannot be set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322227] Re: "Lock on suspend" variable cannot be set
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322227] Re: "Lock on suspend" variable cannot be set
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-lock-on-suspend variable is not set on running light-locker, then everything works and screen is locked on resume. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322227] Re: "Lock on suspend" variable cannot be set
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
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 - untouched. And guess what? Everything seems to work WITHOUT these "workarounds" tried before. This implies to the difference in some other file in /etc/pam.d, which is "left over" from 13.04 and causing this problem - other file than /etc/pam.d/lightdm. -- 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: Not authorized to perform operation / Unable to determine the session we are in: No session for pid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171342] Re: mouse scroll wheel not working in gedit & System Monitor
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/1171342 Title: mouse scroll wheel not working in gedit & System Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1171342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation....
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 - Ubuntu has lightdm and Lubuntu has lxdm... -- 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: Not authorized to perform operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation....
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 was present without logging in (inability to chutdown or restart). This maybe screwed up user session with "no session for..." messages and no visible sessions for loginctl. This workaround fixed both problems. -- 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: Not authorized to perform operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation....
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: Not authorized to perform operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation....
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. https://bbs.archlinux.org/viewtopic.php?id=167947 To be exact - post #5 had the thing, that solved the problem - polkit- gnome-authentication-agent-1 is up and all related stuff is usable again. Maybe this will provide some help... -- 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: Not authorized to perform operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218202] Re: numlockx does not turn num lock keyboard light on.
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 desktop, I noticed the problem right away. LED is indicating numpad status wrongly on XFCE desktop, but not in tty's, although few toggles with numlock key are needed to get it right in tty's, but LED still stays "wrong way" on the desktop. -- numlockx does not turn num lock keyboard light on. https://bugs.launchpad.net/bugs/218202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659546] Re: kmix (with pulseaudio) main channel affects other channels as well. also there is no way to control channels directly anymore
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 solution to this. http://forum.sabayon.org/viewtopic.php?t=21776 -- kmix (with pulseaudio) main channel affects other channels as well. also there is no way to control channels directly anymore https://bugs.launchpad.net/bugs/659546 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585053] Re: ntpdate shouldn't be run by ifup on desktops (conflict with time-admin's NTP options)
*** 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 of misleading from the point of ordinary user - synchronisation takes place even when the user has not changed the setting from "Manual" to "Keep synchronised". Of course there is more than one way to fix this misleading situation. If we are considering the simplest - removing the dependency of ntpdate - then the bug should may be considered to be against package ubuntu-minimal, which brings the ntpdate in for standard install. -- ntpdate shouldn't be run by ifup on desktops (conflict with time-admin's NTP options) https://bugs.launchpad.net/bugs/585053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585053] Re: ntpdate running in the background by default
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-up.d/ntpdate does run every time when the network connection is established, as I explained before already. There is one thing though - if ntp support is installed, then the selected servers are configurable from the time-admin, but the /etc/network/if-up.d/ntpdate is still invoked every time even when time settings is set to "Manual" from time-admin, although it respects the server selection made in time-admin (obviously from /etc/ntp.conf) and server selection from /etc/default/ntpdate is ignored. All-in-all: 1. There is no way to prevent ntpdate to run every time, when network connection is established - setting to "Manual" in time-admin has no affect on this. 2. Servers can be selected after the installation of ntp support and this selection is then respected by the /etc/network/if-up.d/ntpdate script. P.S. There is no "Synchronise now" button in time settings panel any more. ** Summary changed: - ntpdate running in the background by default + no user interface to configure whether time synchronisation is always made on establishing the network connection. -- no user interface to configure whether time synchronisation is always made on establishing the network connection. https://bugs.launchpad.net/bugs/585053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585053] [NEW] no user interface to configure ntpdate
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: Installed: 2.30.0-0ubuntu2 Candidate: 2.30.0-0ubuntu2 It would be logical to expect, that when the time setting is set to "Manual" in the time-admin, then time is really set manually, and there is no synchronisation over the network However even then there are lines like this in the system log: ntpdate[1364]: adjust time server 91.189.94.4 offset 0.099757 sec It is like that even after the clean install, when this setting was on manual and clicking caused the message about the need to install NTP support to pop out. Interesting... ntp is not installed, but something is still trying to adjust the time with the server, on this IP, which happens to be ntp.ubuntu.com. Even more interesting was to observe, that after installing the NTP support and changing the time-admin setting to "Keep synchronised with internet servers" and even after the selecting totally different servers, there is still this same line on the system log every time after establishing the network connection. Of course then I discovered that this is doings of ntpdate, which is installed by default as dependancy of ubuntu-minimal and has this same ntp.ubuntu.com in its configuration - and there is no way to see or change it from the user interface. Other solution could be of course dropping the dependancy in a way, that ntpdate would not be installed by default on standard desktop installation, but I am not sure, if this could brake something else and would therefore be impossible. The server(s) defined in /etc/default/ntpdate are not visible from the user interface and there no way to configure them. I really do not want to describe it as "calling home" (as the setting with ntp.ubuntu.com has no connection to user interface), but there is possibility, that someone else would. In some places it could be even seen as security risk, when the system is connecting somewhere without any according configuration or the way to configure this... ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Tags: ntp ntpdate time-admin -- no user interface to configure ntpdate https://bugs.launchpad.net/bugs/585053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
