tde-devels

devels@trinitydesktop.org

1 participants
3754 discussions

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>>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

11 years, 3 months

Compiling with gcc visibility enabled

by Darrell Anderson

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

11 years, 3 months

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>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

11 years, 3 months

Re: [trinity-devel] Fixed reaching fully activated state in screen saver

by Darrell Anderson

>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

11 years, 3 months

Re: [trinity-devel] HAL call in LockProcess::showVkbd

by Darrell Anderson

>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

11 years, 3 months

HAL call in LockProcess::showVkbd

by Slávek Banko

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

11 years, 3 months

casper-trinity and ubiquity-trinity for ubuntu nightly-livecd

by Slávek Banko

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

11 years, 3 months

Fixed reaching fully activated state in screen saver

by Slávek Banko

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

11 years, 3 months

Re: [trinity-devel] Can't load kate tabbar extension (bug report 1664)

by Darrell Anderson

>>I wanted to help test the patch provided in bug report 1664. >> >>I am unable to get the tabbar extension to appear in kate. This >is >> >>true for systems with or without the 1664 patch. I select the >>check >>box in Settings -> Plugins but the bar never appears. When I >again >> >>open Settings the check box is unchecked. >> >>Here is what I see in my xsession-errors log: >> >>tdecore (KLibLoader): WARNING: KLibrary: symbol not found >>tdecore (KLibLoader): WARNING: The library >>libkatetabbarextensionplugin does not offer an >>init_libkatetabbarextensionplugin function. >> >>I see similar stderr messages with the Kate File Templates >plugin: >> >>tdecore (KLibLoader): WARNING: KLibrary: symbol not found >>tdecore (KLibLoader): WARNING: The library katefiletemplates does > >>not offer an init_katefiletemplates function. >> >>This is a recent git package set from a day ago. >> >>Would somebody else affirm this behavior? > >I have a virtual machine running Trinity. The package set is from >July 29. I see the same behavior there in that selecting the >plugin >check boxes results in the tabbar not appearing and when >immediately thereafter opening the Settings dialog the check boxes > >are cleared. I do not see the stderr messages but I suspect that >is >because this older package set does not include commit 5354555. > >I have a 3.5.13.0 virtual machine. There I am able to enable the >tabbar extension. That tells me only that something changed from >3.5.13.0 to pre R14. > >The problem appears with or without the tdeaddons patch. I suspect > >tdelibs, either a corner case I have stumbled across or something >in my build script configuration options. The problem occurs with >a fresh profile too. I performed a complete package set rebuild. As always, a clean build environment. Same problem. Darrell

11 years, 3 months

Re: [trinity-devel] Can't load kate tabbar extension (bug report 1664)

by Darrell Anderson

>I wanted to help test the patch provided in bug report 1664. > >I am unable to get the tabbar extension to appear in kate. This is > >true for systems with or without the 1664 patch. I select the >check >box in Settings -> Plugins but the bar never appears. When I again > >open Settings the check box is unchecked. > >Here is what I see in my xsession-errors log: > >tdecore (KLibLoader): WARNING: KLibrary: symbol not found >tdecore (KLibLoader): WARNING: The library >libkatetabbarextensionplugin does not offer an >init_libkatetabbarextensionplugin function. > >I see similar stderr messages with the Kate File Templates plugin: > >tdecore (KLibLoader): WARNING: KLibrary: symbol not found >tdecore (KLibLoader): WARNING: The library katefiletemplates does >not offer an init_katefiletemplates function. > >This is a recent git package set from a day ago. > >Would somebody else affirm this behavior? I have a virtual machine running Trinity. The package set is from July 29. I see the same behavior there in that selecting the plugin check boxes results in the tabbar not appearing and when immediately thereafter opening the Settings dialog the check boxes are cleared. I do not see the stderr messages but I suspect that is because this older package set does not include commit 5354555. I have a 3.5.13.0 virtual machine. There I am able to enable the tabbar extension. That tells me only that something changed from 3.5.13.0 to pre R14. The problem appears with or without the tdeaddons patch. I suspect tdelibs, either a corner case I have stumbled across or something in my build script configuration options. The problem occurs with a fresh profile too. Darrell

11 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels