** Changed in: guidance
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/65791
Title:
DPMS timeout restored incorrectly on login
--
ubuntu-bugs mailing list
ubuntu-bu
** Changed in: guidance (upstream)
Status: Confirmed => Fix Released
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Awesome. Now, what about a SRU for Edgy?
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Fix uploaded to Feisty (and also committed to KDE SVN for 3.5.6 and 4.0)
** Changed in: kdebase (Ubuntu)
Status: Fix Committed => Fix Released
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https:
On Saturday 06 January 2007 15:27, Luka Renko wrote:
> I did not get any response from last changer of kenergy, so I have
> prepared patch for kdebase that should address this for feisty.
Is this recorded on bugs.kde.org? If you CCMAIL: kde-devel, I'm pretty sure
someone can commit the fix to KDE
I did not get any response from last changer of kenergy, so I have
prepared patch for kdebase that should address this for feisty.
Debdiff is available on:
http://lure.lu.funpic.de/kubuntu/feisty/kdebase16.debdiff
** Changed in: kdebase (Ubuntu)
Status: Confirmed => Fix Committed
** Chan
I find this bug very annoying, as I have to adjust those settings
_every_ time I log in!
It has taken 2 months already Please do something about it !
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
ht
Jonh, thanks for pushing this one forward. I think both of suggested
patches are not really appropriate, as they just cure the side effect
and not the root cause. The issue is that kdisplayrc contains values in
minutes, therefore it does not make sense to change defaults to seconds
as suggested by
There must be a more complete way of just simply castrating kdebase of
kenergy altogether, since its functionality is all done by guidance, and
heck kenergy isn't even user-visible in any fashion.
I'd rather see that happen than any of the workarounds posted this far.
I still have an inclination
Here is my patch.
--- energy.cpp~ 2006-12-05 23:12:07.0 -0200
+++ energy.cpp 2006-12-05 23:15:14.0 -0200
@@ -77,8 +77,8 @@
#endif
static const int DFLT_STANDBY = 0;
-static const int DFLT_SUSPEND = 30;
-static const int DFLT_OFF = 60;
+static const int DFLT_SUSPEND = 1
Hi John, greetings for nailing the bug! I wouldn't have the time not
even to try.
By taking a look on the code, it seems the multiply by 60 thing crept in when
they added the capability to get the system settings. The hardwired constants
DFLT_STANDBY, DFLT_SUSPEND and DFLT_OFF are meant to be mi
Testing packages available by putting the following in your
sources.list:
"deb http://buntudot.org/people/~jdong/kdebase/ ./"
Package built from Edgy kdebase with that one patch above.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
wrong status
** Changed in: kdebase (Ubuntu)
Status: Rejected => Confirmed
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Found the culprit in kdebase. This patch makes DPMS timeouts accurate
again. I will upload some testing packages soon.
--- kdebase-3.5.5.orig/kcontrol/energy/energy.cpp
+++ kdebase-3.5.5/kcontrol/energy/energy.cpp
@@ -340,7 +340,7 @@
if (hasDPMS) {
if (enable) {
DPMSEnab
This (trapping xset) has already been done.
https://launchpad.net/distros/ubuntu/+source/kde-guidance/+bug/65791/comments/10
It seems what is changing the setting is not using xset.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubu
Exactly. So it's _not_ a bug in guidance. Can someone who suffers from
this problem just look up the real problem? Replacing xset with some
debugging trap would help _a_lot_ here.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu
That actually doesn't work on my system -- it restores the DPMS timeout
too early and it gets overwritten again. Previously I had a sleep 20 &&
displayconfig-restore and similar lines for 20,30,and 40 second delays,
but even then when my system is under IO load and logging in, it would
not work.
-
An easier on the system workaround is:
ln -s /usr/bin/displayconfig-restore ~/.kde/Autostart/displayconfig-
restore
It uses the system settings value (the real one, not multiplied by 60 as
system settings insists on displaying).
--
DPMS timeout restored incorrectly on login
https://launchpad.ne
John Dong wrote:
> A horrific workaround I'm currently using is a python script in the
> background that checks DPMS periodically and resets it if it's an
> unexpected value
It sure is brute force, but it works for me!
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/
** Changed in: guidance (upstream)
Status: Unknown => Confirmed
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: KDE Bug Tracking System #128696
http://bugs.kde.org/show_bug.cgi?id=128696
** Also affects: guidance (upstream) via
http://bugs.kde.org/show_bug.cgi?id=128696
Importance: Unknown
Status: Unknown
--
DPMS timeout restored incorrectly on login
https://launchpad.n
A horrific workaround I'm currently using is a python script in the
background that checks DPMS periodically and resets it if it's an
unexpected value
[EMAIL PROTECTED]:~$ cat /usr/local/bin/dpmswatch
#!/usr/bin/python
import os
import time
while True:
st=os.popen('xset -q | grep Standby').r
Just tried the nv driver. Same problem.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Kubuntu edgy here shows this problem. I'm using the nVidia closed source
driver.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I already did that, Simon... only thing that uses xset is
displayconfig-restore, and it does call it with correct values.
I am using closed-source fglrx.
On 11/11/06, Simon Edwards <[EMAIL PROTECTED]> wrote:
>
> Thanks for the info John. My next step would be to 'wedge' the xset
> binary with a s
Thanks for the info John. My next step would be to 'wedge' the xset
binary with a something dummy. At least I don't have to bother now. I
wonder which API xset uses for setting DPMS mmm.
Is this driver related in some way? I'm using the closed source nVidia
driver.
--
DPMS timeout restored i
On Saturday 11 November 2006 17:43, John Dong wrote:
> Simon: Lure & I also spent some time investigating this prior to Edgy's
> release, and we arrived at the same conclusion as you -- guidance is
> behaving properly, but something else in the login sequence is changing
> the DPMS timeout.
>
>
> I
Simon: Lure & I also spent some time investigating this prior to Edgy's
release, and we arrived at the same conclusion as you -- guidance is
behaving properly, but something else in the login sequence is changing
the DPMS timeout.
In addition, I tried trapping xset with my own dummy binary, and
A few weeks ago I spent some time trying to get to the bottom of this
problem. It appears that guidance is working fine and is setting the
dpms values correctly during login. But once the login sequence is
complete xset reports wrong values. I've checked that displayconfig-
restore is using the cor
Sorry, but the patch doesn't fix this problem. Although it fixes the bug
about not saving monitor power off setting (bug #46585
https://launchpad.net/bugs/46585 and KDE bug tracker bug #128696
https://bugs.kde.org/show_bug.cgi?id=128696 ).
I made a clean install of Kubuntu 6.10, applied the fix an
Good. :)
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Attached fix went into KDE svn yesterday.
** Attachment added: "Fix saving DPMS settings on apply"
http://librarian.launchpad.net/4981950/displayconfig-fix-dpms-saving.diff
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs
I'm seeing this problem on Edgy. If I set the Offtime to 30 minutes, it
reverts to 5 hours. If I set the Offtime to 1 minute, it reverts to 1
hour.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
I have the exact same issue on Kubuntu Edgy also...
When I select 15minutes, the value is always 5 hours after login.
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
Similar report but after resume: bug 65734
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Similar report also on Gnome - see bug 66277
** Bug 66026 has been marked a duplicate of this bug
** Bug 66215 has been marked a duplicate of this bug
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
http
** Bug 65887 has been marked a duplicate of this bug
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Lure and abattoir both have indicated that they experience this too.
** Changed in: kde-guidance (Ubuntu)
Status: Unconfirmed => Confirmed
--
DPMS timeout restored incorrectly on login
https://launchpad.net/bugs/65791
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://li
38 matches
Mail list logo
