This seems to have been fixed in unity-greeter, but not lightdm-gtk-
greeter. And in any case, how can the unity-greeter inactivity timeout
be tuned? gsettings under the lightdm account?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Confirming fixed in mainstream trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays on forever
Status in The Ubuntu
** No longer affects: hundredpapercuts
** Changed in: ubuntu-power-consumption
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
** Branch linked: lp:ubuntu/trusty-proposed/unity-greeter
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays on forever
This bug was fixed in the package unity-greeter - 14.04.9-0ubuntu1
---
unity-greeter (14.04.9-0ubuntu1) trusty; urgency=medium
* New upstream release:
- Correctly handle SIGTERM and quit cleanly. We were previously not stopping
the signal and so not cleaning up on exit.
** Branch linked: lp:~robert-ancell/unity-greeter/screensaver
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays
Fixed in lp:~robert-ancell/unity-greeter/screensaver. The default
screensaver timeout is 300s but this can be changed by editing the
idle-timeout gsettings key for unity-greeter.
i.e. for testing create
/usr/share/glib-2.0/schemas/10_unity-settings-daemon.gschema.override:
In fixing bug 128 I noticed that gnome-screensaver is only running
sometimes (when it did run the focus bug would occur). So that is
probably a factor here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in
Rocko, this new locker is implemented by unity and is a new bug. The
greeter does not use this method.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
Yes, I can see that it must be the new unity-greeter screen-locker that
is blocking the screen power-down. As minnigaliev-r says, if you lock
the screen with ctrl-alt-L or super-L, the screen locks but never powers
off, but as soon as you enter your password to unlock it the screen
powers off and
The new lock screen is implemented on top of Unity and it only looks
like the login screen.
I reported the lock screen not turning off monitor.
https://bugs.launchpad.net/unity/+bug/1292041
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Ubuntu 14.04 Unity
Problem steel persist even on new lock screen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor
The new lightdm-style screensaver that just landed in 14.04 also does
not turn off the screen. Is the screensaver implemented by lightdm and
therefore related to this bug, or is this a new bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is
With new display blocker after Ctrl+Alt+L monitor is not turn off even
after some hours of downtime.
After enter the password and show desktop monitor is turn off if do not
touch mouse or keyboard for 2 seconds.
If display blocker will be set automatically - monitor turn off normaly.
--
You
** Package changed: gnome-settings-daemon (Ubuntu) = unity-settings-
daemon (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login
It will probably be easiest to make unity-greeter implement the required
D-Bus interface and do the power off itself.
** Changed in: linux
Status: New = Invalid
** Changed in: unity-settings-daemon (Ubuntu)
Importance: Low = High
--
You received this bug notification because you are
Eugene Crosser:
if you do assign some settings in the command line or from the display-setup
script, something resets them back shortly afterwards.
That would be g-s-d's power plugin. See gpm-common.c,
disable_builtin_screensaver() and
gsd_power_enable_screensaver_watchdog(). g-s-d's power
The issue there seems to be that the gnome-settings-daemon power plugin
relies on gnome-screensaver to turn off the screen, or the screensaver
is not running on the greeter... we either need to teach unity-greeter
to turn off the screen or to fix u-s-d to work without gnome-screensaver
** Also
Dear friends, please note that gdm works fine (it is currently my
workaround):
$ sudo apt-get install gdm
(and/or)
$ sudo dpkg-reconfigure gdm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
I've read through the portions of Xorg that are directly related to the
screensaver timeouts (dixSaveScreens() and friends) and it appears that
my suspicion is incorrect. I was unable to find any sort of built-in
default screensaver. Another dead end.
Then I remembered that the kernel has a
@Ted, I am not convinced that you are re-assigning the blame correctly.
I have no 13.04 to compare, but I believe that if the kernel (setterm) blanking
timeout affected the X screen in 13.04, that was probably a bug rather than a
feature. X blanking is controlled by the builtin screensaver
My (completely unconfirmed) suspicion at this point is that the problem
lies in xorg-server. I'm guessing that xorg-server has a built-in
default screensaver of some sort that turns off the monitor. In 13.04,
this was working fine. In 13.10, it no longer is. I'm going to shift
my focus to
** Also affects: xorg-server
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor
Through some script trickery, I was able to get g-s-d running in debug
mode. It appears from the debug output that in 13.04, g-s-d's power
plugin is *not* responsible for powering off the monitor when lightdm
/unity-greeter is up. The question is: Who is?
(Power is out here, probably for a
** Tags added: ubuntu-desktop-trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays on forever
Status in One Hundred
** Changed in: unity-greeter
Importance: Undecided = High
** Changed in: unity-greeter
Status: Confirmed = Triaged
** No longer affects: lightdm (Ubuntu)
** No longer affects: lightdm
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Project changed: unity-greeter = unity-greeter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays on forever
Unity greeter doesn't do anything to control the power management. It
runs gnome-settings-daemon to do this. It seems likely the problem is
either unity-greeter not configuring / running the correct plugin in
g-s-d or g-s-d being broken.
--
You received this bug notification because you are a
Robert, my observations show that the problem is not that proper setting
are *not applied*, but that they are *overridden* with wrong values
afterwards.
(It conceivable though that g-s-d may be applying the wrong values
after my display-setup-script has applied the right ones. Can you tell
where
Robert Ancell:
It seems likely the problem is either unity-greeter not configuring / running
the correct plugin in g-s-d
It appears that the power plugin is indeed running in both 13.04 and
13.10 as I am seeing logging from it in /var/log/lightdm/x-0-greeter.log
in both 13.04 and 13.10.
or
Apparently, it implies that something that is started as a part of
the greeter session, i.e. the greeter itself, or one of the
indicators, resets the DPMS settings.
That's an interesting comment, maybe somebody could try with lightdm-
gtk-greeter to see if that happens there as well?
--
You
It turns out that in 13.04, display power-off (when lightdm is up) is
driven by the X screensaver timeouts. If I do this:
xset s 60 60
...in lightdm's display-setup-script, the screen powers off (in 13.04)
in one minute instead of the usual 10.
13.10 has the X screensaver timeouts set to 10
** Changed in: lightdm (Ubuntu)
Importance: Undecided = Medium
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New = Confirmed
** Changed in: hundredpapercuts
Importance: Undecided = Medium
** Changed in:
Thanks, Eugene. Your solution works for me as well.
To complete this workaround, I've added a script to handle turning off
the X dpms timeouts when the user logs in. Here are the three files
that I've created. First, the config file:
/etc/lightdm/lightdm.conf.d/50-dpms.conf
--- cut here
Workaround works for me as well, but seems to trump the Turn off screen
when inactive setting for my desktop session. I have that set for 10
minutes and immediate lock, but with this enabled it will blank the
screen at the scripts timeout and will not lock.
--
You received this bug notification
I've found something that may be useful both for diagnosis and as a
workaround.
If you define a display-setu-script in the lightdm configuration, like
this:
[SeatDefaults]
display-setup-script=/path/to/display-setup.sh
and put this command in the display-setup.sh:
xset dpms 120 125 130
this
Eugene Crosser 1245...@bugs.launchpad.net writes:
I've found something that may be useful both for diagnosis and as a
workaround.
If you define a display-setu-script in the lightdm configuration, like
this:
[SeatDefaults]
display-setup-script=/path/to/display-setup.sh
and put this
I also can confirm this works. Thank you, Eugene!
It took me an embarrassing number of tries to get this right, so for
others wanting to implement this work-around:
printf
'\n[SeatDefaults]\ndisplay-setup-script=/usr/bin/bug1245474-work-around.sh\n'
|sudo tee
** Also affects: unity-greeter
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays
** Summary changed:
- saucy regression: on login screen, monitor stays on forever
+ [regression] on login screen, monitor stays on forever
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
40 matches
Mail list logo
