tde-devels

devels@trinitydesktop.org

9 participants
3819 discussions

kdebindings, pyqt3, pykde3
by Darrell Anderson 03 Nov '11

03 Nov '11

How are these bindings supposed to be built now? In the past pyqt3 and pykde3 were built separatebly before building kdebindings. I notice in the 3.5.13 tarballs two packages named pykdeextensions and python-trinity. Do these packages replace pyqt3 and pykde3? Darrell

1 0

kdelibs 3.5.13 tarball fails to build
by Darrell Anderson 03 Nov '11

03 Nov '11

Recently I reported I could not build kdelibs from SVN. I now am trying to build from the 3.5.13 tarballs. I am having the same failure. Building on Slackware 13.1. GCC 4.4.4. Clean chroot build environment. I am building everything to install to /opt/trinity including tqtinterface. qt3, qca, qca-tls, tqtinterface, dbus-tqt, dbus-1-tqt, arts built without error. I built qt3 from the Trinity 3.3.8.d sources. I am building kdelibs using cmake and I am building "out of source." Log: http://humanreadable.nfshost.com/trinity/build_logs/kdelibs-3.5.13-i486-1-b… The log contains environment variables. The variables show that my build script is finding all paths. My cmake directives: cmake ${TMP}/${PRGNAM} \ -DCMAKE_C_FLAGS:STRING="$CPUOPT" \ -DCMAKE_CXX_FLAGS:STRING="$CPUOPT" \ -DCMAKE_INSTALL_PREFIX=${PREFIX} \ -DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \ -DLIB_SUFFIX=${LIBDIRSUFFIX} \ -DMAN_INSTALL_DIR=${MANDIR} \ -DQTDIR=$QTDIR \ -DQT_LIBRARY_DIRS=${QTDIR}/lib \ -DCMAKE_SKIP_RPATH=OFF \ -DBUILD_ALL=ON \ -DWITH_LIBART=ON \ -DWITH_LIBIDN=ON \ -DWITH_LUA=$LUA \ -DWITH_TIFF=ON \ -DWITH_JASPER=ON \ -DWITH_OPENEXR=ON \ -DWITH_UTEMPTER=ON \ -DWITH_AVAHI=$DNSSD \ -DWITH_ASPELL=ON \ -DWITH_HSPELL=OFF Thanks much. Darrell

3 7

kdebase build problems
by Calvin Morrison 03 Nov '11

03 Nov '11

Hello. Having some trouble with building kdebase. It doesn't seem to be able to find dbus-tqt ==> Making package: trinity 1240522-1 (Thu Nov 3 15:35:40 EDT 2011) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving Sources... -> Found kdebase-3.5.13.tar.gz ==> Validating source files with md5sums... kdebase-3.5.13.tar.gz ... Passed ==> Extracting Sources... -> Extracting kdebase-3.5.13.tar.gz with bsdtar ==> Removing existing pkg/ directory... ==> Starting build()... ==> Setting PATH, CMAKE and Trinity Environment variables ==> Creating out-of-source build directory: /mnt/home/calvin/builds/trinity/tde-packaging/arch/release/trinity-kdebase/src/build ==> Starting cmake... -- tmoc path: /opt/trinity/bin/tmoc -- moc path: /opt/qt/bin/moc -- uic path: /opt/qt/bin/uic -- checking for 'TDE' -- found 'TDE', version 3.5.13 CMake Error at cmake/modules/TDEMacros.cmake:20 (message): ################################################# dbus-tqt is required, but was not found on your system ################################################# Call Stack (most recent call first): ConfigureChecks.cmake:203 (tde_message_fatal) CMakeLists.txt:139 (include) what is weird is that my PKG_CONFIG_PATH is set to: /opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig:/opt/qt/pkgconfig:/opt/qt/pkgconfig and in /opt/trinity/lib/pkgconfig/ are: dbus-1-tqt.pc and dbus-tqt.pc Anyone have ideas for this? Calvin

1 0

qca, qca-tls
by Darrell Anderson 03 Nov '11

03 Nov '11

I don't see either package in svn or the tarballs. Are these packages now obsolete with 3.5.13? Or just build them separately as done previously? Darrell

1 0

November: Post Release Meeting 11/15/2011
by Calvin Morrison 03 Nov '11

03 Nov '11

Hello all, Good work team, and thank you to everyone who helped with the release! Now that the release is out the door, we are looking ahead to the next release. At this meeting we will discuss our goals and our ideas for 3.5.14. If everyone could start to thinking about what they would like to do, or see done for 3.5.14 that would be great. Please bring your thoughts to the meeting. Please checkout the following links and contribute as such: Roadmap for 3.5.14: http://www.trinitydesktop.org/wiki/bin/view/Developers/3_5_14_Roadmap Release Goals for 3.5.14: http://www.trinitydesktop.org/wiki/bin/view/Developers/3_5_14_Release_Goals Etherpad for November Meeting: http://trinity.etherpad.trinitydesktop.org/15 This meeting is for everyone interested helping trinity desktop. That means, Packagers, Contributors, Developers, and even Users! If you are interested in getting involved and don't know where to start, please come to this meeting to find out how you can help! There will more detailed time information as we draw closer to the meeting. The meeting will probably occur in the early evening EST. Please RSVP and let us know if you can/cannot make it. Thank you, Calvin Morrison Trinity Desktop Team.

6 7

on releases :)
by Aaron J. Seigo 03 Nov '11

03 Nov '11

hi everyone ... first off, congratulations on a new release! the way i see Trinity, it is the continuation of work on the 3.5 codebase. nobody else is doing it, nobody else seems willing to do it outside of Trinity and there are people who want to use it. these are all great things and a strength of free and open source software. as such, i see Trinity doing a service by giving those who wish to continue using KDE 3.x the ability to do so without facing software obsolence through bit rot. this makes those folks happier, and prevents them from feeling like their only remaining response is to behave poorly towards those working on the 4.x codebases. it's win-win in the truest sense of the word. but i'm not going to whitewash things either: there are those who use Trinity who really dislike 4.x and those in the KDE community who see Trinity as a safe haven for people who have (or continue to) behave poorly. this is beyond unfortunate since Trinity and the KDE Platform and Workspaces 4.x both provide good things to the same group of people: those who use KDE software. so i'd like to see the remaining negativity put behind us so all of us working on KDE code can co-exist in good spirit, happy in the knowledge that everyone is getting what they want and doing so in the spirit of true freedom. i hope you feel similarly. this was the spirit in which we encouraged people to work on the 3.x code if they wanted to and, unlike some other communities who have in recent times openly berated and made fun of people who wanted to do similar things for their software, have been supporters and agreed with the goals you have. so when i see the announcements on sites starting with quotes like this: "Disappointed with KDE 4's performance and other shortcomings, Timothy Pearson continued KDE 3.5 development under the name Trinity." i cringe a little inside because that does nothing but stir up hornets' nests. when i read this in the announcement to the mailing list: "Why upgrade from KDE3.5.10, the latest release available from KDE e.V.? Simply put, Trinity is faster, more secure, and far more feature rich than 3.5.10 ever was!" (http://trinity-devel.pearsoncomputing.net/?0::3271) i feel sad because Trinity should really not be trying to stand out as a _competitor_ to 3.5.10 but as the continuation of that code base. (btw, KDE e.V. never puts out KDE releases; the community of participants and contirbutors does that.) by positioning Trinity as a competitor when no such competition exists only serves to strengthen us/them lines that simply do not exist in reality. personally, i'm tired of the needless divisions in F/OSS that arise because people can not simply live and let live, because we for some reason feel the need to constantly tear each other down in an attempt to make our own efforts seem more presentable and respectable. what rubbish. Trinity, as the continuation of the 3.5 codebase, stands on its own feet alongside Plasma Desktop and the rest of the 4.x products. we should therefore also stand as allies and friends. we should also stand for what we are, not for what (or who) we are not. as the developers, and therefore leaders of the Trinity project, please consider this when working on and then publicizing your next release. i appreciate your time and patience if you've read this far :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks

6 7

TDE 3.5.13: kstreamripper FTBFS
by Francois Andriot 02 Nov '11

02 Nov '11

Hello, compiling kstreamripper on RHEL/Fedora fails with following error: ========== g++ -o src/addnewstream.o -c -I/opt/trinity/include/ -I/usr/lib64/qt-3.3/include/ -I/opt/trinity/include/tqt -DNDEBUG -DNO_DEBUG -DQT_NO_TRANSLATION -Isrc -I. src/addnewstream.cpp g++ -o src/addnewstreamimpl.o -c -I/opt/trinity/include/ -I/usr/lib64/qt-3.3/include/ -I/opt/trinity/include/tqt -DNDEBUG -DNO_DEBUG -DQT_NO_TRANSLATION -Isrc -I. src/addnewstreamimpl.cpp /usr/lib64/qt-3.3/bin/moc -o src/addnewstreamimpl_moc.cpp src/addnewstreamimpl.h g++ -o src/addnewstreamimpl_moc.o -c -I/opt/trinity/include/ -I/usr/lib64/qt-3.3/include/ -I/opt/trinity/include/tqt -DNDEBUG -DNO_DEBUG -DQT_NO_TRANSLATION -Isrc -I. src/addnewstreamimpl_moc.cpp src/addnewstreamimpl.h:29: error: ISO C++ forbids declaration of 'TQ_OBJECT' with no type src/addnewstreamimpl.h:31: error: expected ';' before 'public' scons: *** [src/addnewstreamimpl_moc.o] Error 1 ========== Problem solved with '#include <tqt.h>' in 'addnewstreamimpl.h', see attached patch. Thanks Francois Andriot

1 0

Trinity Desktop Environment (TDE) v3.5.13 Released!
by Timothy Pearson 02 Nov '11

02 Nov '11

Trinity Desktop Environment version 3.5.13 has been released! This version provides significant enhancements to areas such as desktop security, GTK application support, and general usability. You will find a detailed list of upgrades and improvements to the Trinity system here: http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13 Installation instructions for Debian, Ubuntu, Fedora, RedHat, and Slackware are available on the Trinity project home page: http://www.trinitydesktop.org/ If you would like to compile Trinity from source instead of using the prebuilt binaries, instructions are available here: http://www.trinitydesktop.org/wiki/bin/view/Developers/HowToBuild And the source itself can be downloaded from the main project Website at: http://www.trinitydesktop.org/ Simply click on the 3.5.13 link on the lower left hand side of the screen. Why upgrade from KDE3.5.10, the latest release available from KDE e.V.? Simply put, Trinity is faster, more secure, and far more feature rich than 3.5.10 ever was! It incorporates the latest patches from multiple KDE enhancement projects, such as OpenSUSE, Chakra, and Ubuntu. If you do find a bug, please don't hesitate to report it to the project bugtracker at http://bugs.pearsoncomputing.net/ If you would like to connect with other Trinity users and/or developers, or simply want to be informed of the latest updates to the Trinity system, the official project mailing lists are available here: http://www.trinitydesktop.org/mailinglist.php This release was the result of collaboration between several open source developers; their names are listed at http://www.trinitydesktop.org/contributors.php The Trinity project would like to thank them for their support! If you like the Trinity project, why not donate to help keep it alive? Your contributions help fund both the Trinity project infrastructure and the development of new features. Details are available here: http://www.trinitydesktop.org/donate.php Be sure to let us know what you think of this release, and enjoy! Timothy Pearson Trinity Desktop Project NOTE: Binary packages are currently being uploaded to the worldwide mirror system. Sources are already available, however the binaries may take a day or two to become available to all mirrors.

4 5

RE: [trinity-users] Nightly Builds, Ubuntu Natty, dead in water
by Timothy Pearson 02 Nov '11

02 Nov '11

> Got this when I tried to run hal-trinity manually: > > Nov 2 10:25:03 toto kernel: [ 6448.428655] hald[3942]: segfault at 0 ip 000000000041059b sp 00007fff40a1d690 error 4 in hald[400000+52000] Nov 2 10:25:03 toto init: hal-trinity main process (3942) killed by SEGV signal <snip> There is no way to run 3.5.12 on Natty without a reinstall, and even then you will probably run into some odd dependency problems. My suggestion is this: 1. Use dpkg --purge --force-all to remove all hal related packages (i.e. all packages with hal in their name; use dpkg -l | grep hal to find them) 2. apt-get update 3. apt-get -f install 4. Reboot I have seen the HAL files end up in an inconsistent state on distribution upgrades before, which causes all kinds of havoc in HAL-dependent programs. This sequence has always fixed the problem for me. Tim

1 0

[kdebase 3.5.13] hardcoded /usr/lib/libnspr4.so in startkde
by François ANDRIOT 02 Nov '11

02 Nov '11

Hello, under some circonstances, the startkde script goes through the following code. 417 if [ -n $KGTK_PRELOAD ]; then 418 if [ -e /usr/lib/libnspr4.so ]; then 419 KGTK_NSPR_PRELOAD="/usr/lib/libnspr4.so:" 420 fi 421 export LD_PRELOAD=$KGTK_PRELOAD:$KGTK_NSPR_PRELOAD$LD_PRELOAD 422 fi The problem is that, under RHEL/Fedora, the library "/usr/lib/libnspr4.so" (if present) is compiled for x86, not x86_64. So every command I use in the konsole gives the following warning: ERROR: ld.so: object '/usr/lib/libnspr4.so' from LD_PRELOAD cannot be preloaded: ignored. The correct path for x86_64 should be "/usr/lib64/libnspr4.so". As a quick fix, I suggest the following change: if [ -n $KGTK_PRELOAD ]; then if [ -e /usr/lib64/libnspr4.so ]; then KGTK_NSPR_PRELOAD="/usr/lib64/libnspr4.so:" elif [ -e /usr/lib/libnspr4.so ]; then KGTK_NSPR_PRELOAD="/usr/lib/libnspr4.so:" fi export LD_PRELOAD=$KGTK_PRELOAD:$KGTK_NSPR_PRELOAD$LD_PRELOAD fi Any better solution is welcome :) Thanks Francois Andriot

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels