Additional xsession-error log messages that might be related to the
recent renaming (or they might be isolated bugs):
* 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 (TDEProcess): WARNING: _attachPty() 17
* tdecore (TDEProcess): WARNING: _attachPty() 13
* tdesu: WARNING: unknown super user command
For consistency, should KIOConnection be renamed to
TDEIOConnection? Looks like tdelibs is the only affected module,
although there are some remaining remnant "KIO" usages in tdelibs,
tdepim, tdenetwork, tdebase, tdevelop, tdesdk, tde-i18n, kshowmail,
krusader, kdirstat, tdeio-apt, tork, digikam.
Darrell
>All,
>
>Hopefully these problems are easy to resolve and I don't have to
>file formal bug reports. I don't recall seeing these error
>messages
>until after the recent k->tde renaming patches. There are no
>related stability issues or crashes, but the messages indicate
>various apps are failing to perform as intended.
>
>* tdepowersave: WARNING: Unknown error while acquire
>org.freedesktop.Policy.Power interface
>
>* tdepowersave: WARNING: Couldn't request charge_level.unit for
>udi:
>/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:0
>0
>/PNP0C0A:00/power_supply/BAT0/
>
>* tdeio (tdeioslave): WARNING: Can't communicate with
>kded_kpasswdserver!
>
>More than likely the messages are caused by inadvertent renaming
>changes, or the renaming changes are correct but associated code
>needs respective updating. If the errors can't be easily resolved
>here in the list then I'll file official bug reports, all as
>Blocker against the R14 release because if I'm seeing these errors
>
>then I suspect there are additional similar errors that other
>users
>are seeing.
>
>If you are using git with the latest patches then please review
>your xsession-errors log for possible related error messages.
The patch for tdepowersave is quite short but seems the commonality
among the three error messages is authentication? Then again, I see
the two tdepowersave error messages when logged in as root too.
Therefore not an authentication problem per se, but likely a
related renaming bug in the authinfo code?
Darrell
All,
Hopefully these problems are easy to resolve and I don't have to
file formal bug reports. I don't recall seeing these error messages
until after the recent k->tde renaming patches. There are no
related stability issues or crashes, but the messages indicate
various apps are failing to perform as intended.
* tdepowersave: WARNING: Unknown error while acquire
org.freedesktop.Policy.Power interface
* tdepowersave: WARNING: Couldn't request charge_level.unit for
udi:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:00
/PNP0C0A:00/power_supply/BAT0/
* tdeio (tdeioslave): WARNING: Can't communicate with
kded_kpasswdserver!
More than likely the messages are caused by inadvertent renaming
changes, or the renaming changes are correct but associated code
needs respective updating. If the errors can't be easily resolved
here in the list then I'll file official bug reports, all as
Blocker against the R14 release because if I'm seeing these errors
then I suspect there are additional similar errors that other users
are seeing.
If you are using git with the latest patches then please review
your xsession-errors log for possible related error messages.
Thanks!
Darrell
Last night I ran a new build set with the latest k->tde renaming
patches from Slavek. I updated my main three machines this morning.
Thus far no related problems encountered.
Slavek, good work and thanks!
Darrell
All,
Many of the TDE services will be going offline for scheduled maintenance
20:00 08/31/2013. A full list of affected services is:
* QuickBuild
* Web Services
* Bug Tracker
* GIT System
* IRC Bot
* Etherpad
* Patchwork
* LiveCD Builder
* Automated Builds
The mailing lists will remain active, and I will send another announcement
when services have been restored.
Thank you for your patience during this process!
Tim
>I hate to be a pest, but what is the status of this project?
>
>Thanks!
I've been running build sets every day for a few days. No build
failures or easily noticeable usability issues. Slavek gets the
final say but I believe he wants to incorporate a handful of minor
tweaks we discovered yesterday. Likely we are ready to start
pushing patches Real Soon Now. :-)
Darrell
Tim, Slavek,
Perhaps the convert kde3->tde script could be updated to include
renaming *.kdevelop files to *.tdevelop?
That would include updating po(t), Doxyfile, doxygen files, etc.,
such as KDevelop->TDevelop; although we should be careful not to
modify "About" strings that credit the original KDevelop team
members.
Darrell
tquic crashes during build of tdebase/tdeioslaves. I'm not sure if it's a
bug or something wrong about my system...
Any ideas?
Build log in the attachment.
Hi there,
today I run into a FTBFS when building libraries/pytdeextensions on debian/testing (jessie).
The package actually compiles, but the building process actually fails after that when invoking "dh_python".
dh_python -ppytdeextensions-trinity
make: dh_python: Command not found
I tracked down the problem to be in the file "debian/python-distutils-jaunty.mk", where "dh_python2" needs to
be invoked instead of "dh_python" and prepared a patch for it.
While looking at the problem I also spotted that the patch "11_fix_get_libdir_name.diff" was out-of-sync with
the code by 63 lines, so I updated the patch to point to the correct line.
With both patches, the package builds correctly.
I don't know if you are having the same problem I had. The nightly built package is not ready at the time
of writing (it is schedule for building in a few hours), so I can't compare.
I don't know whether the patch for "dh_python" breaks the building for debian/wheezy, since last year I didn't have any
problem compiling in such environment. If so, a separate entry needs to be created in the tde-packaging for
debian/jessie (instead of pointing to wheezy) and the patch added to the "libraries/pytdeextensions" files.
Cheers
Michele