Hey,
our development page [0] is no longer correct. It says "patches from SVN"
it should say "patches from GIT".
Calvin
[0] http://trinitydesktop.org/development.php
Tim,
Qupzilla is a light weight web browser written in C++ using Qt4. Is this the type of app that should build on Trinity using the TQt3 interface layer?
http://www.qupzilla.com/
Darrell
We have in the sources a shell script that updates a user's profile configuration files to be compatible with the recent R14 XDG changes. The script is installed to $TDEDIR/bin/r14-xdg-update.
The script is called once from starttde and thereafter is not run again from starttde. The wcript can be run manually at any time by passing the "force" parameter at the command line.
If you look at the script you will see some "TODO" comments. There probably are other TODO items that I have not considered.
This script does a good job against its original intent but needs further testing. No user in this team uses Trinity in the exact same way. Therefore robust testing and improvements to the script are needed to cover unforseen corner cases.
We need to find bugs and oversights before we move into release candidate status for R14.0.0.
Please remember the script is only for R14 and cannot be tested in with 3.5.13 or 3.5.13.1. Using the script in those releases will break the user's profile. Testing the script can be performed only with R14.
Thanks much!
Darrell
I notice the following messages in my xsession log when I start KMail:
[tdeinit] kmail is executable and not a library. Launching with exec.
TQObject::connect: Incompatible sender/receiver arguments
KMFolderMgr::msgRemoved(KMFolder*,TQ_UINT32) --> KMMsgIndex::slotRemoveMessage(TQ_UINT32)
TQObject::connect: Incompatible sender/receiver arguments
KMFolderMgr::msgAdded(KMFolder*,TQ_UINT32) --> KMMsgIndex::slotAddMessage(TQ_UINT32)
TQObject::connect: Incompatible sender/receiver arguments
KMFolderMgr::msgRemoved(KMFolder*,TQ_UINT32) --> KMMsgIndex::slotRemoveMessage(TQ_UINT32)
TQObject::connect: Incompatible sender/receiver arguments
KMFolderMgr::msgAdded(KMFolder*,TQ_UINT32) --> KMMsgIndex::slotAddMessage(TQ_UINT32)
Do the messages mean a bug?
Darrell
Hi all,
Some migration issues that still seem to be there:
Renaming issues with system directories. Two I ran into:
/etc/trinity/kdm -> /etc/trinity/tdm
/opt/trinity/share/apps/kdm -> /opt/trinity/share/apps/tdm
Often both directories exist with different files being placed in
different directories. The configuration files mainly look for files in
the kdm variants of the directories. I can imagine that kdm/tdm is not
the only program that needs attention.
I also still haven't seen the r14 user profile migration script on Ubuntu.
I'm not sure how things are planned exactly now, but I suppose there
should be a second script that can be used to perform and diagnose the
KDE3->TDE migration on a system level.
Best regards,
Julius
We are pleased to announce the addition of a full suite of LDAP/Kerberos
tools to the TDE bounty program! These tools are geared towards
enterprise users, and cover all aspects of creating, managing, and using
LDAP/Kerberos realms. For more information, screenshots, statistics, and
demo videos, please visit the TDE RFE page at
http://www.trinitydesktop.org/crfe/#finished
Timothy Pearson
Trinity Desktop Project
Hi
During what I chose patches for 3.5.13.1, I noticed that filelight-l10n seems
completely superfluous. Everything is already in the filelight. Binary
package filelight-l10n even can not be installed because the files are in
conflict with those of filelight package.
I overlooked something or it really is?
Slavek
--
