All,
I have received several requests to implement some type of translation
framework in order to make submitting translations to TDE easier (this
includes making sure they actually end up in GIT). Apparently the current
process is cumbersome and error prone; I can attest to this as we have at
least one large translations patch languishing in the bugtracker that
cannot be cleanly applied to the current GIT sources.
My question is: what would all you translators like to see out of the
translation framework? Are there any existing open-source services that
you prefer to use and/or might be usable with TDE? I would also like to
know what your preferred workflow is so that I can try to design something
to match.
Thanks!
Tim
All,
The QuickBuild build farm was taken offline this morning and will remain
offline indefinitely. While I realize this pushes R14 release further
out, the cold hard reality is that donations have fallen so much, along
with the bad economy impacting my own finances, that I cannot afford to
keep the build farm running at this time. Finances were already strained
with the Web server upgrade, as the new software required newer hardware
to keep performance at a reasonable level.
My intention was to keep the build farm running until R14 was released,
then see if any donations came in to cover some of the costs. However,
this morning the main chiller was destroyed due to sudden power
brownouts/surges, forcing the build farm offline. As I do not have the
funds to replace this chiller, and with the onset of spring/warmer
temperatures here, I cannot restart the build farm at this time.
I will do my best to bring one builder online for each architecture in the
next few days, but this severe drop in build power will obviously cause
full archive rebuilds to take several months at minimum. As a result we
need to start looking at dropping support for older Ubuntu versions,
though I did not want to take this step as I know some larger deployments
depend on this support.
All other TDE services are not affected at this time.
Sorry for the bad news!
Timothy Pearson
Trinity Desktop Project
Tim, All,
In working though testing, I used 'tdedebugdialog --fullmode' and set the '0
generic' output to file kdebug.dbg (the default name) for all 4 (information,
warning, error, etc). That file was over 46 Megabytes and 431,000 lines
repeating tdepowersave activity in a 12 hour period. tdepowersave is constantly
churning away in the following loop (2 examples):
tdepowersave: unmonitored device changed: /sys/devices/
tdepowersave: unmonitored device changed:
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3//dev/input/event3
tdepowersave: unmonitored device changed:
/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input5/event4//dev/input/event4
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:03.0/net/enp0s3/enp0s3
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:04.0/input/input3/event2//dev/input/event2
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/input/input2/event1//dev/input/event1
tdepowersave: unmonitored device changed:
/sys/devices/platform/i8042/serio0/input/input0/event0//dev/input/event0
tdepowersave: unmonitored device changed:
/sys/devices/platform/i8042/serio1/input/input7/event6//dev/input/event6
tdepowersave: unmonitored device changed:
/sys/devices/platform/pcspkr/input/input6/event5//dev/input/event5
tdepowersave: unmonitored device changed: /sys/devices/
tdepowersave: unmonitored device changed:
/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3//dev/input/event3
tdepowersave: unmonitored device changed:
/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input5/event4//dev/input/event4
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:03.0/net/enp0s3/enp0s3
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:04.0/input/input3/event2//dev/input/event2
tdepowersave: unmonitored device changed:
/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/input/input2/event1//dev/input/event1
tdepowersave: unmonitored device changed:
/sys/devices/platform/i8042/serio0/input/input0/event0//dev/input/event0
tdepowersave: unmonitored device changed:
/sys/devices/platform/i8042/serio1/input/input7/event6//dev/input/event6
tdepowersave: unmonitored device changed:
/sys/devices/platform/pcspkr/input/input6/event5//dev/input/event5
This is with the tde_dbus_hardwarecontrol happily set and not doing its
repeating loop. Why is tdepowersave changing unmonitored devices multiple times
per second? Is this just it spitting out what activity it read for various
hardware devices (net, mouse, speaker)?? My mouse is usb, so I can see input
there (not while I'm sleeping though), but why would any of the serial devices
every change - they are not used. This looks like a true race condition, because
none of my devices are changing, and they are certainly not changing multiple
times every second while I'm asleep :)
--
David C. Rankin, J.D.,P.E.
> My question is: what would all you translators like to see out of the
> translation framework? Are there any existing open-source services that
> you prefer to use and/or might be usable with TDE? I would also like to
> know what your preferred workflow is so that I can try to design something
> to match.
During the week end, I told to Michele that I had planned to work(*) on the French translation for ktorrent this week.
I was going to fill in bugzilla with a patch to apply on the French po file, but when I read your email, I'm not sure that's the right way to handle that.
I've never done that kind of translating before, consequently, I can't tell you what tool I'd like to work with.
Regards.
gregory
(*) I don't intend to translate the software entirely but at least I'd like to remove some English vocab displayed on the main frame as well as in the menu (in the most common options/parameters).
Dear all,
bug 1833 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=1833) reports discontinued links to KBabel po compendium files.
I googled a lot and seems the problem goes back to the KDE days.
I am looking at removing those links and perhaps the whole TMX and PO compendium module pages, but before doing that I would like to know if any of you has been able to use them and in case which link you have used.
Feedback is appreciated.
Thanks
Michele
Hi all,
in the past few days I have tested on my private builer building TDE R14.0.0
for Ubuntu 14.04 (Trusty). All base packages as well as all applications has
been successfully built. It seems that we are ready to add support for Ubuntu
14.04 in nightly-builds.
--
Slavek
Hi all,
during a recent test building for Ubuntu 14.04 (Trusty), I also tested the
parallel build of all packages. In the test I set 4 parallel jobs. The
problems I have seen only the following packages:
- tdebindings
- tdegames
- tdemultimedia
- gwenview
- kmplayer
- koffice
--
Slavek
All,
Testing the new soft-freeze packages has disclosed a horrible problem with
tdepowersave taking nearly 100% of the CPU. My laptop was nearly on fire this
morning:
[screenshot]
http://www.3111skyline.com/dl/dt/trinity/ss/tdeowersave-97percent.jpg
Earlier in development I saw tdepowesave in the 20-40% range, but never at
near 100% of CPU. What to try?
--
David C. Rankin, J.D.,P.E.
All,
After rebuilding tdebase, I experienced a set of 'X-dialog' (not k-dialog)
errors related to xdg-update-script failures on login. The x-dialog warned that
this script would continue to run on each login -- not good. The error said
there were permission or path failures involved. There was also a file placed in
~/.trinity named: r14-xdg-update-validation-test9.txt containing:
<Filename>kde-kcpuload.desktop</Filename>
<Filename>kde-knutclient.desktop</Filename>
<Filename>kde-kcpuload.desktop</Filename>
<Filename>kde-knutclient.desktop</Filename>
<Filename>kde-k3bsetup2.desktop</Filename>
<Filename>kde-k3bsetup2.desktop</Filename>
<Filename>kde-kcpuload.desktop</Filename>
<Filename>kde-knutclient.desktop</Filename>
<Filename>kde-k3bsetup2.desktop</Filename>
<Filename>kde-konqfilemgr.desktop</Filename>
The failure warning about path and permission problems must have occurred
before .xsession-error activation. Looking at the .xsession-error, here were
some new messages that stood out:
[r14-xdg-update] Performing a profile update for Trinity release R14 XDG compliance.
[r14-xdg-update]
[r14-xdg-update] To run this script against a different user directory, or automated
[r14-xdg-update] from within another script, pass the directory path as a parameter.
[r14-xdg-update] For example: r14-xdg-update /home/user_dir
[r14-xdg-update] Use the user home directory and not the profile directory.
[r14-xdg-update] User directory: /home/david
[r14-xdg-update] Profile directory: /home/david/.trinity
[r14-xdg-update]
[r14-xdg-update] Renaming some configuration files and directories.
[r14-xdg-update] dockdevtocpluginrc->doctdevtocpluginrc
[r14-xdg-update] kdevgrepviewrc->tdevgrepviewrc
[r14-xdg-update] kdevsnippetrc->tdevsnippetrc
[r14-xdg-update] kdevfileselectorrc->tdevfileselectorrc
[r14-xdg-update] kdevdesignerrc->tdevdesignerrc
[r14-xdg-update] kdevdocumentation->tdevdocumentation
[r14-xdg-update] kdevfileselector->tdevfileselector
[r14-xdg-update] kdevabbrev->tdevabbrev
WHY WAS RENAMING CONFIG FILES NECESSARY -- NONE OF THESE FILES CONFLICT WITH
ANYTHING AT ALL?? Was the approach just a massive sed -e 's/k/tde/g' kdevelop/*
and then patching whatever got caught up in the mix? That just seems like a bad
idea...
Additional messages were:
[tdeinit] Got SETENV
'SESSION_MANAGER=local/valhalla:@/tmp/.ICE-unix/635,unix/valhalla:/tmp/.ICE-unix/635,inet6/valhalla:57874,inet/valhalla:36274'
from tdelauncher.
[tdeinit] Got SETENV 'XCURSOR_THEME=default' from tdelauncher.
[tdeinit] Got SETENV
'GTK_RC_FILES=/etc/gtk/gtkrc:/home/david/.gtkrc:/home/david/.trinity/share/config/gtkrc'
from tdelauncher.
[tdeinit] Got SETENV
'GTK2_RC_FILES=/home/david/.gtkrc-2.0-kde-kde4:/home/david/.trinity/share/config/gtkrc-2.0'
from tdelauncher.
Huh? Why is anything trying to set a directory on my system with "kde4" in its
name?? If we are renaming things to make tde its own, then that is certainly the
type of thing that would be OK to rename...
--
David C. Rankin, J.D.,P.E.