Launchpad has imported 1 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=10205.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-06-28T05:00:39+00:00 Wirawan Purwanto wrote: I am running xfce4 version 4.8.0.2 with all its bell and whistles (including XFPM version 1.0.11) in Debian 7 (wheezy). The installation includes xscreensaver, which I don't mind using. I am reporting a problem where XFPM and xscreensaver have disagreement on the DPMS parameters. Each software has its own store of DPMS parameters (i.e. whether DPMS is enabled, and the timeout values for Standby, Suspend, and Off). XFPM stores the settings in the XFCE setting registry, where xscreensaver stores its parameters in ~/.xscreensaver file. If I set, say, the DPMS "Off" timeout value that is different in both software, then it is not clear who will give the last word. You can observe this issue by alternating the invocation of xscreensaver-demo and XFPM setting dialog. Whichever tool is invoked for the last time, that's what eventually sets the DPMS settings. (I use "xset q" to check the applied DPMS parameters in the X server.) But this is not the whole story. In XFPM settings dialog, if the timeout values are not changed (ie. the values are the same upon closing the dialog box), then no changes were done on the X DPMS settings, so in the end XFPM set of values did not get applied upon closing the dialog box. I also post this problem here (post #3) http://forum.xfce.org/viewtopic.php?pid=30157#p30157 Here's my proposal: *) since XFPM is supposed to be an upper-level tool, it may be necessary to make XFPM to override the settings of xscreensaver, too, to be consistent. Say, if a user changes the XFPM DPMS timeout settings, the new values are propagated to ~/.xscreensaver (if that program is running). The problem becomes more interesting with reading-in the XFPM values. Do we need to let XFPM read from ~/.xscreensaver too? *) Alternatively, in both XFPM and xscreensaver there should be an option which basically is: "don't mess with the X DPMS settings", as suggested by these bug reports: https://bugzilla.xfce.org/show_bug.cgi?id=6595 https://bugzilla.xfce.org/show_bug.cgi?id=10192 In this case, we can let XFPM handle all the DPMS settings, and not allow xscreensaver to mess with any. Or vice versa if the user wants it. Let me know what you think. Wirawan Reply at: https://bugs.launchpad.net/ubuntu/+source/xfce4-power- manager/+bug/889394/comments/3 ** Changed in: xfce4-power-manager Status: Unknown => Confirmed ** Changed in: xfce4-power-manager Importance: Unknown => Medium ** Bug watch added: Xfce Bugzilla #6595 https://bugzilla.xfce.org/show_bug.cgi?id=6595 ** Bug watch added: Xfce Bugzilla #10192 https://bugzilla.xfce.org/show_bug.cgi?id=10192 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889394 Title: xscreensaver and xfce4-power-manager conflict To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/889394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
