tde-devels

devels@trinitydesktop.org

7 participants
3840 discussions

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

Re: [trinity-devel] Can't load kate tabbar extension (bug report 1664)
by Darrell Anderson 26 Oct '13

26 Oct '13

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

1 0

Re: [trinity-devel] Can't load kate tabbar extension (bug report 1664)
by Darrell Anderson 25 Oct '13

25 Oct '13

>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

1 0

Can't load kate tabbar extension (bug report 1664)
by Darrell Anderson 24 Oct '13

24 Oct '13

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

1 0

Re: [trinity-devel] Commit cced03e1 2013-10-17
by Darrell Anderson 24 Oct '13

24 Oct '13

>> You mean something like the attached patch? >> >...added missing definition TDEICONLOADER_DEBUG in config.h.cmake Um, yes, I think so. I presumed something similar was needed but I wanted one of the experts to say as much. :-) * Are you going to push the patch? * How do we test the binaries compiled correctly when WITH_TDEICONLOADER_DEBUG=true? Backtraces? * Is this an option normally left as false and changed to true only when a developer asks for that change to help debug related problems? Darrell

2 2

TDE strict dependency on binutils in Debian Jessie/Wheezy
by Michele Calgaro 24 Oct '13

24 Oct '13

HI there, is anybody aware of any good reason why tdelibs14-trinity and some other packages have a very strict dependency on binutils in Debian Jessie and Wheezy (and I suspect also on previous versions and in Ubuntu, even though I didn't check)? For example I get dependencies such as: binutils (>= 2.23.52.20130828), binutils (<< 2.23.52.20130829). The problem with such kind of dependency is that when binutils is updated, I need to do a full rebuild of TDE before I can update the binutils package on my machine. After the full rebuild is completed, everything can be updated, but I don't see the reason for having the '<<' part of the dependency since it doesn't seem to affect anything: TDE builds with both the old and the new binutils package. So I am wondering if such strict dependency is intentional or if it is something that we are dragging along from the past (perhaps because of a broken or incompatible binutils version in the past). If there isn't any particular reason, I will open a bug report in a few days about this point. Thanks Michele

3 9

Commit cced03e1 2013-10-17
by Darrell Anderson 23 Oct '13

23 Oct '13

Tim, Commit cced03e1 2013-10-17 disabled the constant generation of backtraces in TDEIconLoader. The patch inidcates that KICONLOADER_CHECKS must now be explicitly defined. I presume the only people who want to do that are folks wanting to troubleshoot related problems. Should the need arise, where is the appropriate place to define KICONLOADER_CHECKS? Darrell

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels