Release Notes For 3.5.13
New or Improved from 3.5.12
This section highlights some of the most useful improvements to the Trinity system.
Many bugs have been fixed and new features have been added; a partial list follows.
Back End Improvements
- 3.5.13 development starts at SVN revision r1182534
- Ported tqtinterface, arts, kdelibs, kdebase, kdeartwork, kdesdk, kdegraphics, kdepim, kdenetwork, kwebdev, and kdevelop to CMake.
- The Trinity project is now maintaining the required Qt glue libraries for poppler, avahi, and other applications
- Trinity is now using the TQ* class namespace within all modules, libraries, and applications except kdebindings
- Many bug fixes and crash fixes
- Additional Trinity rebranding
- Added new "Monitor and Display" control center module for system wide single/multi monitor and display configuration
- Enhanced GTK Qt theme engine; tabs, checkboxes, menu backgrounds and much more now display correctly in the Trinity style
- An optional Secure Attention Key has been implemented to further secure the login and desktop lock dialogs
- A new widget theme, Asteroid, has been added
- A built-in TDE X11 compositor is now included, and certain Trinity applications, such as Amarok, now detect and use true ARGB transparency when available
- A TDE-specific DBUS notification client has been added for higher integration with common applications such as Firefox and NetworkManager
- Prevent OpenGL screensavers from locking up the display
- Fixed Flash plugin segfaults in Konqueror
- Enhanced QuickLaunch Kicker applet
- Added "Deep Buttons" option to Kicker
New programs ↑ The following new programs have been added to the Trinity software suite:
- DPMS support added
- Gamma configuration now available as an alternative to ICC colorspace configuration
- Multi-monitor configuration backend added
- The new Monitor and Display control center module, built upon libkrandr
As of the 3.5.13 release the Trinity project has taken over maintenance of Qt3.
- This means we are the new "upstream" location for up-to-date Qt3 source code.
- Since there have been no updates or stable releases from Nokia/Trolltech in many years and there are literally hundreds patches floating around, there was a significant need for a central location.
- By maintaining Qt3 it will allow us to continue to improve Qt3 outside the scope of Trinity. It will also provide a central location for Linux distributions to build packages from, and contributers to submit code to.
- For obvious reasons any Qt3 version released by this project is licensed under the GPL only; holders of Trolltech Qt licenses may not use these versions in their proprietary projects.
ARM builds for Debian Squeeze of all Trinity components are available for installation from the release archive. If this experiment works well, ARM builds may also be made available for Ubuntu in TDE v3.5.14.
- Francois Andriot has published builds of TDE v3.5.13 for RHEL5, RHEL6, and Fedora 15
Trinity can be installed alongside KDE4.x with few problems. Trinity automatically detects and adjusts for KDE4.x programs, so that users can easily run KDE4 applications from within the Trinity environment.
Bugs in the tracker fixed for this release include, but are not limited to:
Assisting the Project
If you are interested in helping out, please contact:
A Bluetooth developer who could re-activate Trinity's Bluetooth functions would be greatly appreciated. Also, developers who can help squash some of the bugs in our bug tracker are always needed!
When upgrading an Ubuntu installation kpowersave is unable to remove a prior file diversion. To fix, simply run: sudo dpkg-divert --remove /etc/acpi/powerbtn.sh
There is a mailing list for Trinity users available here: Mailing Lists This is a great place for users to share tips and tricks, and you can also sign up to receive announcements related to Trinity.
We want to hear what you think about the current release of Trinity. We want to know if it Rocks, if it is just OK, or if it is flat out wrong. No matter the feedback, as long as it is in line with the FOSS Code of Conduct, we would like to hear it.
So what are you waiting for? Head on over to the Feedback Page and let us know!