tde-devels

devels@trinitydesktop.org

7 participants
3786 discussions

Re: [trinity-devel] Fixed reaching fully activated state in screen saver
by Darrell Anderson 28 Oct '13

28 Oct '13

>As I now noticed a problem with the necessity of user input (for >interrupt the >screen saver) you reported also in the bug report 1615. It is >possible that >bug fixed in commit cbbc7ad0 could be related also with NFS on >/home? > >Can you try it? I created a test patch to restore autosupend in tdepowersave when $HOME is a network mount. I attached the patch to bug report 1623. After rebuilding tdelibs with the test patch, commit cbbc7ad0 does not resolve the problem of trying to autosuspend when $HOME is a network mount. Darrell

1 0

Re: [trinity-devel] Fixed reaching fully activated state in screen saver
by Darrell Anderson 28 Oct '13

28 Oct '13

>To test the problem, which was fixed, it is simple: >1) Make sure that you have enabled lock screen before suspend or >standby. >2) Set the screen saver run after a short time. >3) Once the screensaver is activated, press button to go into >suspend mode. Or >set in tdepowersave autosuspend for a short time => a little >longer than time >to activate screen saver. >4) Look, that nothing happens (for any length of time), until you >cause an >activity that will lead to stop screen saver. >5) Only after stopping screen saver follows immediately switch >into desired >suspend mode. I tested tdepowersave before applying the patch. In tdepowersave I set the screensaver to 1 minute and autosuspend to 2 minutes. Without the patch the following happens: * After 1 minute the screensaver starts. * After 2 minutes the suspend-to-ram 30 second timeout dialog does not appear. * Thereafter the laptop never automatically goes into suspend-to- ram mode by itself. * Any user action interrupts the screensaver. * The laptop then goes into suspend-to-ram mode and the suspend-to- ram 30 second timeout dialog never appears. With the patch: * After 1 minute the screensaver starts. * After 2 minutes the suspend-to-ram 30 second timeout dialog appears. * After 30 seconds the laptop automatically goes into suspend-to- ram mode by itself. * Upon restoring from suspend-to-ram, the screensaver lock dialog appears. Well done! Darrell

1 0

Re: [trinity-devel] Fixed reaching fully activated state in screen saver
by Darrell Anderson 28 Oct '13

28 Oct '13

>>As I now noticed a problem with the necessity of user input (for >>interrupt the >>screen saver) you reported also in the bug report 1615. It is >>possible that >>bug fixed in commit cbbc7ad0 could be related also with NFS on >>/home? >> >>Can you try it? > >To test, I believe we have to rebuild tdebase with commit cbbc7ad0 > >and rebuild tdelibs with commits 9d76cb9 reversed and possibly >ba6b2079 reversed. > >That is, to test whether commit cbbc7ad0 resolves the NFS problem >as well, we need to restore the ability to autosuspend in >tdepowersave when $HOME is an NFS mount. Currently that ability is > >disabled in tdepowersave through commit 9d76cb9. > >What do you think? > >If, after testing NFS $HOME with commit cbbc7ad0, bug report 1623 >still exists to address the NFS mount problem. The proposed >solution in 1623 is to study the KDE powerdevil code, which uses >upower. I tried for a few hours trying to rebuild packages with reversed patches, in the hopes of restoring autosuspend when $HOME is a network mount. I gave up as there are too many changes for my C++ skills to overcome. We can't test whether commit cbbc7ad0 resolves the problem until the autosuspend feature is restored to tdepowersave when $HOME is a network mount. I really want to see autosuspend work with tdepowersave when $HOME is a network mount. If you can restore autosuspend when $HOME is a network mount, then I'd be happy to retest tdepowersave with commit cbbc7ad0. Darrell

1 0

Compiling with gcc visibility enabled
by Darrell Anderson 27 Oct '13

27 Oct '13

All, Recently I stumbled across a bug with building tdeaddons. The resolution was to change in my build script --enable-gcc-hidden- visibility to --disable-gcc-hidden-visibility. We have bug report 1285 to address the problem of compiling with hidden symbol support but no work has proceeded with that report. Currently we have no dependable list of which packages to build with gcc visibility enabled. What is the safe/sane policy for our build scripts? Darrell

1 0

Re: [trinity-devel] Fixed reaching fully activated state in screen saver
by Darrell Anderson 27 Oct '13

27 Oct '13

>As I now noticed a problem with the necessity of user input (for >interrupt the >screen saver) you reported also in the bug report 1615. It is >possible that >bug fixed in commit cbbc7ad0 could be related also with NFS on >/home? > >Can you try it? To test, I believe we have to rebuild tdebase with commit cbbc7ad0 and rebuild tdelibs with commits 9d76cb9 reversed and possibly ba6b2079 reversed. That is, to test whether commit cbbc7ad0 resolves the NFS problem as well, we need to restore the ability to autosuspend in tdepowersave when $HOME is an NFS mount. Currently that ability is disabled in tdepowersave through commit 9d76cb9. What do you think? If, after testing NFS $HOME with commit cbbc7ad0, bug report 1623 still exists to address the NFS mount problem. The proposed solution in 1623 is to study the KDE powerdevil code, which uses upower. Darrell

1 0

Re: [trinity-devel] Fixed reaching fully activated state in screen saver
by Darrell Anderson 27 Oct '13

27 Oct '13

>while investigating the problem, when autosuspend in TDEpowersave >as well as >change the suspend state in response to pressing a suspend/power >button hangs >when the screen saver is active, I found that SaverEngine never >reached >Saving state. Lock process not correctly sent a signal on fully >activation >back to SaverEngine. For this reason, SaverEngine may behave >incorrectly in >different situations. > >I fixed this in commit cbbc7ad0 (tdebase). > >Please test the correct behavior of screen saver. What steps are required to test? Darrell

3 3

Re: [trinity-devel] HAL call in LockProcess::showVkbd
by Darrell Anderson 27 Oct '13

27 Oct '13

>Hello all, > >I noticed that in tdebase / kdesktop / lock / lockprocess.cc in >LockProcess::showVkbd is system call "hal-find-by-property ..." >This obviously does not work if HAL is not present in the system. > >How to replace this? For example counting the number of connected >keyboards from tdehw library? > >Also could be added support for using kvkbd. A while ago I filed bug report 1624 about that message/call. http://bugs.trinitydesktop.org/show_bug.cgi?id=1624 Are we ever going to get serious about getting R14 out the door? Darrell

1 0

HAL call in LockProcess::showVkbd
by Slávek Banko 27 Oct '13

27 Oct '13

Hello all, I noticed that in tdebase / kdesktop / lock / lockprocess.cc in LockProcess::showVkbd is system call "hal-find-by-property ..." This obviously does not work if HAL is not present in the system. How to replace this? For example counting the number of connected keyboards from tdehw library? Also could be added support for using kvkbd. Slavek

1 0

casper-trinity and ubiquity-trinity for ubuntu nightly-livecd
by Slávek Banko 27 Oct '13

27 Oct '13

Tim, during testing Ubuntu nightly-livecd I noticed that in the casper is there a hack to ensure automatic login. And settings for automatic login in the installation on disk (Ubiquity) does not work. Know that the package casper-trinity addresses exactly that you do not need to hack the automatic login into upstream package casper. And package ubiquity-trinity solves setting autologin in Ubiquity to work after installing on the disk. Slavek

1 0

Fixed reaching fully activated state in screen saver
by Slávek Banko 26 Oct '13

26 Oct '13

Hi all, while investigating the problem, when autosuspend in TDEpowersave as well as change the suspend state in response to pressing a suspend/power button hangs when the screen saver is active, I found that SaverEngine never reached Saving state. Lock process not correctly sent a signal on fully activation back to SaverEngine. For this reason, SaverEngine may behave incorrectly in different situations. I fixed this in commit cbbc7ad0 (tdebase). Please test the correct behavior of screen saver. Thanks Slavek

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels