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
>> 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
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
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
All,
Is there a command line method available for disabling Trinity KDED
Daemons after starting Trinity? I did not see anything obvious from
kded --help.
Thanks.
Darrell
>I started from the fact that these bugs are in the TDE (maybe a
>KDE3) long
>time, and that they do not cause visible problems => not block
>R14.0.0.
>But you're right that their current visibility increase in their
>importance.
Yes, the messages have been around since KDE3 but never were seen.
:-)
>I will try now to focus on this bug.
Life is quieter here at home (at the moment). I should be able to
test patches.
Darrell
>Blocker reports (Open items: 3):
>1655 New stderr messages as a result of commit 5354555
> -- I believe that this bug is not blocking for R14.0.0
Also please refer to comment 8 in the bug report. I stopped using
tdepowersave because within a couple of hours of using Trinity that
specific message creates HUGE xsession-error logs. The message
appends the xsession-error log at a rate of once every second. That
really needs to be fixed before R14 is released. :-)
Darrell
Hello all,
I would say that the work on the R14 successfully moving forward.
On Etherpad are listed only a few opened bug reports.
I chalked little notes. Please take a look at it.
Regressions (Open items: 2):
1615 TDEPowersave will autosuspend to ram only once
-- seems already fixed
1597 Pressing the power button shutdown computer, regardless of what I set in
tdepowersave
-- seems already fixed
Available patches (Open items: 5):
1560 several FTBFS building R14.0.0
-- tqt3 : build as shared library instead of static library
- I believe that there is nothing against commit it?
-- python-tqt : fix FTBFS
- requires a deeper decision because
- pyqt3TQtSignal × pyqt3QtSignal => sip-tqt × original sip
-- tdenetwork : use alternate 'resolv.conf' in kppp, if available
- I do not know whether to commit or leave as distribution specific?
1199 Build issue: tdelibs FTBFS on older distro with Xorg under /usr/X11R6
-- patches contained here are not intended to push into GIT
-- some of them could be commited, some would have to be adjusted
-- I believe that this bug is not blocking for R14.0.0
1146 Build issue: fusion-icon does not install python module in python_sitelib
-- it would be good to incorporate findings PYTHON_SITELIB path to makefile
1054 Build issue: soundkonverter FTBFS without --with-extra-includes
-- will be fixed soon - patch waiting for test
952 TDEBase, TDELibs translation to Russian and Ukrainian update
-- the task of updating translations are wider than this one update
-- that's why I suggest defer updating translations to maintanance releases
Blocker reports (Open items: 3):
1655 New stderr messages as a result of commit 5354555
-- I believe that this bug is not blocking for R14.0.0
1528 R14 Tdm cannot start after a system upgrade from 3.5.13 kdm
-- this is probably resolved, pending confirmation
1453 TDM broken in R14 nightlies
-- this is still valid?
Critical reports (Open items: 3):
1233 turn-off and restart not finished in TDE 3.5.13.1
-- this bug is somewhat mysterious
-- I believe that this bug is not blocking for R14.0.0
1168 Build issue: python-tqt FTBFS
-- patch waiting for test
--
Slavek
On Sun, 29 Sep 2013 13:02:34 -0500 "Slávek Banko"
<slavek.banko(a)axis.cz> wrote:
>Hello all,
>
>I would say that the work on the R14 successfully moving forward.
>On Etherpad are listed only a few opened bug reports.
>I chalked little notes. Please take a look at it.
>
>
>Regressions (Open items: 2):
>1615 TDEPowersave will autosuspend to ram only once
> -- seems already fixed
>1597 Pressing the power button shutdown computer, regardless of
>what I set in
>tdepowersave
> -- seems already fixed
>
>
>Available patches (Open items: 5):
>1560 several FTBFS building R14.0.0
> -- tqt3 : build as shared library instead of static library
> - I believe that there is nothing against commit it?
> -- python-tqt : fix FTBFS
> - requires a deeper decision because
> - pyqt3TQtSignal × pyqt3QtSignal => sip-tqt × original sip
> -- tdenetwork : use alternate 'resolv.conf' in kppp, if available
> - I do not know whether to commit or leave as distribution
>specific?
>1199 Build issue: tdelibs FTBFS on older distro with Xorg under
>/usr/X11R6
> -- patches contained here are not intended to push into GIT
> -- some of them could be commited, some would have to be adjusted
> -- I believe that this bug is not blocking for R14.0.0
>1146 Build issue: fusion-icon does not install python module in
>python_sitelib
> -- it would be good to incorporate findings PYTHON_SITELIB path
>to makefile
>1054 Build issue: soundkonverter FTBFS without --with-extra-
>includes
> -- will be fixed soon - patch waiting for test
>952 TDEBase, TDELibs translation to Russian and Ukrainian update
> -- the task of updating translations are wider than this one
>update
> -- that's why I suggest defer updating translations to
>maintanance releases
>
>
>Blocker reports (Open items: 3):
>1655 New stderr messages as a result of commit 5354555
> -- I believe that this bug is not blocking for R14.0.0
>1528 R14 Tdm cannot start after a system upgrade from 3.5.13 kdm
> -- this is probably resolved, pending confirmation
>1453 TDM broken in R14 nightlies
> -- this is still valid?
>
>
>Critical reports (Open items: 3):
>1233 turn-off and restart not finished in TDE 3.5.13.1
> -- this bug is somewhat mysterious
> -- I believe that this bug is not blocking for R14.0.0
>1168 Build issue: python-tqt FTBFS
> -- patch waiting for test
Regarding 1615: The original problem description was resolved, but
please refer to comment 25 for why the report was not closed.
Regarding 1655: I am concerned with the following:
* tdeio (tdeioslave): WARNING: Can't communicate with
kded_kpasswdserver!
* tdeio (KIOConnection): ERROR: Header read failed, errno=104
* tdeio (KIOConnection): ERROR: Header has invalid size (-1)
* tdeio (KIOConnection): ERROR: Could not write data
* tdeio (TDELauncher): ERROR: SlavePool: No communication with
slave.
* tdecore (KLibLoader): WARNING: KLibrary: symbol not found
* [dcopserver] Corrupt data!
As Commit 5354555 (2013-08-26) exposed these messages, would be
nice if we tried to resolve them before pushing R14 out the door.
In the bug report I posted comments how to repeatedly invoke some
of the messages. Who knows which of these messages are associated
with other bug reports.
Regarding 1054 and 1168: I tested the patches and responded
accordingly in the bug reports. Those patches can be pushed and the
reports closed as resolved. Good job! :-)
Regarding the proposed release schedule dates, I was updating those
regularly but family emergencies have been keeping me away from the
project of late. :-(
Darrell
Is there gdb pretty-printers for (t)qt3 and tde/kde3 classes?
If you don't know, «pretty-printer» is a python script for printing various
types in nice human-readable way e.g. QString as normal string, QList as
number of values etc.
