tde-users

users@trinitydesktop.org

4347 discussions

restoring keyboard settings after kvm switch use
by David Emerson 19 Dec '14

19 Dec '14

Hi all, I have made changes in kcontrol > peripherals > keyboard (repeat delay/rate). This works great when I boot up the computer. However, if I use a KVM switch to go to another computer and come back, the keyboard repeat delay and rate are messed up (probably default settings, not my settings.) What can I do about this, so that my keyboard repeat settings will be automatically applied when a (new) keyboard is plugged in / replugged? I can see that it is possible to set something up through udev, but I don't know how to script TDE changes that appear to require the GUI. How to script this? Or perhaps udev is not the right approach? Thanks! ~David. Just upgraded to R14, looking good so far! Great work guys

2 1

509 maximum bandwidth exceeded
by John Pisini 19 Dec '14

19 Dec '14

I suppose it's good that so many people are trying to get Trinity.

3 3

bug 236: user feedback needed
by Michele Calgaro 18 Dec '14

18 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bug 236 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=236) is about KOrganizer and the length of a new ToDo event when selecting a single slot in the day agenda. The behavior is awkward because different from when longer intervals are selected. I would like some feedback from users/developers about the best way to fix it. Proposed options: 1) leave everything as it is. The user can change the above option to get a 15 minutes interval. IMO, a little awkward. 2) leave everything as it is but change the default value of the "Default duration of new appointment" to 15 minutes, so that by default double-clicking on a 15 minutes interval gives a 15 minutes interval. Users can still change the default interval if they want. 3) ignore the "Default duration" option and just use the length of the actual interval selected in the agenda. 4) others... IMO, option 3 or 2 will do. Please put forward your suggestions. The bug will be fixed as part of R14.0.1. Cheers Michele -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUktiNAAoJECp1t8qK3tXPGzIP/1UUxpc5JhdIWXBV4J4cBT6w 2mkX6K4e1nYzDjkkqw8qguUhoOFW/bki5goSADpHS5bccvlNCyYanmuWUwqwN1y8 gkNClyJ+TKzNG8Q+3vSZUZ8PuD+8AUU7heysgyn1h5LA+O5+p38XlZuhIgUfZBIk qOEcWib8/pLoZ8GSDE+UbUvm2ITiXYZWBw80mNoVsQA89CW9peeWPRkTPIuv7zHG ZmGopBuLJQUVLx//QaHh4yk/TSPQFEfu2bZUFmIIYdclHAD7t5VYxJeGk72NLfN5 j/xYVF5bFIBhufXRwMTLI2kyeOtFjVZEJVbjEzw0MloD7NC6w6whJ/JLSoTDyFUB c7I6eoiSeWKcm/VrFV186n/3KJvkyycmXzBswuzjaDLmnu8eT27IGNID1H4wW7W6 BfnDsexKKOFZge9tJ19Sx36z6ayY5Gllz01BU6DcrI7piGTf/5XPcRQbTzyYAOa6 zzSnv1NWZq0PCXGyO4o7jVWsS5cZnbk8KY1Ofy6FfALUZpBkRUcyshZMaocraZ9u bi22Lu3zCkPkjWX31DkL4AKv7V1tm9lmcULyRrMn6dnKmkz5fLao1v06mvViyGNu 2tb3yKPOQWuOChVabWjwld84PoQn7fkoIoprAksfsO3HqT+l8X00eE5p//duMRm+ Aqjgo+txoDuOLQO8+dwq =yUx4 -----END PGP SIGNATURE-----

1 0

R14.0.x and alternative 'preliminary-stable-builds' apt source
by Slávek Banko 17 Dec '14

17 Dec '14

Hi all, who you are accustomed to using my alternative apt source known as 'preliminary-stable-builds'. I would like to say a few informations about the current state and further perspectives. At the time of announcement final R14.0.0 all packages accurately matches state source code R14.0.0. Currently are underway final build, which only removes the "preliminary" number out from the version number. For example, for tdebase 4:14.0.0-s~1492-0debian6.0.0+169 => 4:14.0.0-s-0debian6.0.0+0. Therefore in the upcoming days we can expect update of many packages. In the future you can expect that into apt source will be included preliminary packages for the upcoming release R14.0.1. If you were previously accustomed to using my PPA v3.5.13-sru, know that it will work in the same way. Indeed, the same source packages I'll upload to this alternative apt source, as well as to new PPA on build-farm. From this PPA will be subsequently released the final maintenance versions. Thank you for your support in work on TDE! -- Slávek

1 0

Re: [trinity-users] Trinity Desktop Environment R14.0.0 Released!
by vreher＠cox.net 17 Dec '14

17 Dec '14

---- Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA224 > > The Trinity Desktop Environment (TDE) development team is pleased to > announce the immediate availability of the new TDE R14.0.0 release. The > Trinity Desktop Environment is a complete software desktop environment > designed for Unix-like operating systems, intended for computer users > preferring a traditional desktop model, and is free/libre software. > > Unlike previous releases TDE R14.0.0 has been in development for over two > years. This extended development period has allowed us to create a better, > more stable and more feature-rich product than previous TDE releases. R14 > is brimming with new features, such as a new hardware manager based on > udev (HAL is no longer required), full network-manager 0.9 support, a > brand new compositor (compton), built-in threading support, and much more! > > Version scheme change > > Also new in this release is a change from the KDE v3.5.x series > versioning. In line with our new, separate identity, and to avoid > incorrect comparisons with KDE SC based on version number alone, we are > dropping the old versioning scheme and replacing it with our new R-series > versioning scheme. Each new release from this point forward will be > identified with three numbers prefixed with an R (standing for "Release"); > the first number is the major series, the second is the minor series, and > the last is the Stable Release Update (SRU) identifier. A stable series > will be indicated by a single Rxx.yy identifier, e.g. R14.0. Major > overhauls of the codebase that significantly and permanently change the > way TDE functions, such as the transition from HAL to the TDE Hardware > Library or the new style engine, will only occur when the major series > number increments. Normal, incremental development, including new > features, will be indicated with an increment of the minor version number. > Bug fixes backported to a stable series (Rxx.yy)--with no new features or > changed functionality--will be indicated via an increment of the SRU > identifier alone. > > Getting TDE > > Installation instructions and binary packages are immediately available > for Debian and Ubuntu. Packages for RedHat/CentOs, Fedora, Mageia, > OpenSUSE, and PCLinuxOS are being built by their respective maintainers > and will be made available at a later date. > > Live CDs with TDE R14.0.0 preinstalled are available at > https://wiki.trinitydesktop.org/LiveCDs . > > Major Improvements from 3.5.13.x > > The following is a list of the major improvements TDE R14.0.0 includes. * > New HAL-independent hardware support based on udev. HAL support is still > available for those systems (such as *bsd) that require it. > * Significant renaming of applications, libraries, and packages to avoid > conflicts with other desktop environments (most notably KDE). This allows > TDE to be installed in parallel with other desktop environments without > significant negative interaction. > * Upgrades to TQt3 (TDE's fork of Qt 3.3.8). TQt3 upgrades include a new, > modern style engine, multi-threading support, and improved speed and > stability. > * Support for network-manager 0.9 and newer. > * Switched compositor from Kompmgr to Compton-TDE, a fork of Compton with > TDE-specific features. > * Added builds for armel/armhf architectures on Debian and armhf on > Raspbian Wheezy. > * File mimetype detection system now based on libmagic. > > To see more highlights of this release, please visit the TDE R14.0.0 > information page at > https://wiki.trinitydesktop.org/Release_Notes_For_R14.0.0 . > > About TDE > > The Trinity Desktop Environment (TDE) was forked by Timothy Pearson in > 2008 from the last official release of the K Desktop Environment's third > series (KDE3), version 3.5.10. It existed as a set of modified KDE3 > packages for Ubuntu until 2009, when it was merged onto a proper source > control system (KDE SVN) and rebranded as TDE. Shortly thereafter, TDE's > core infrastructure was created utilizing spare computing capacity from > Raptor Engineering; these infrastructure resources currently include the > world's only Launchpad system based outside of Canonical Ltd. As the > project grew, the TDE team migrated off of KDE's SVN server onto our own > GIT server and has been completely independent from KDE from 2011 onward. > > - From the beginning of the TDE project, individuals from around the world > have contributed to TDE, and our original desire to provide a powerful, > functional desktop environment in the traditional style has been upheld. > The TDE project still is led by Timothy Pearson utilizing Raptor > Engineering's computing resources. TDE currently is growing faster than it > ever has before, with many new contributors--and our dependable core team > of developers--helping to add new functionality, repair bugs, answer > questions on the mailing lists, and increase TDE's overall quality. > > TDE fits into a niche similar to that of the MATE project for Gnome, but > TDE is geared more toward those who want a productive, efficient interface > with a high customization potential. Our dedicated team is continuing to > refine TDE instead of rebuilding it from scratch; this prolonged > development is something rarely seen in the open source applications > arena. While our niche position may not be as glamorous as some of the > larger projects such as KDE and Gnome we believe TDE is no less important > to those who rely on it and use it in their daily work, and we hope that > in the future our niche will continue to grow. > > Developers Wanted > > The TDE development team is small but friendly. If you wish to > participate in the TDE development process, please visit > https://www.trinitydesktop.org/helpwanted.php for additional information. > > User Feedback > > Feedback from our users is an integral part of a large, user-experience > oriented project such TDE. Whether you want to report a bug, suggest an > improvement, or simply let us know your opinion of TDE, please feel free > to contact us. Two good places to start communication are the project's > mailing lists at https://www.trinitydesktop.org/mailinglist.php and its > bug tracker at https://bugs.trinitydesktop.org . > > Contribute to the TDE Project > > Creating TDE requires significant computing resources and bandwidth. > Please consider helping to keep us online with a donation at > https://www.trinitydesktop.org/donate.php . Without your financial > assistance, TDE would not be possible! > > Press Contact Information > > Project Founder/Administrator: Timothy Pearson, > kb9vqf(a)pearsoncomputing.net -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iFYEARELAAYFAlSQln8ACgkQLaxZSoRZrGH6YADgybpgKaNr2Q8Q3vb56nzL4NtC > lsmpXHIyWPZHCwDbBcGsKBtWM6pgYhizFqDRmsDDm/Ptug9yHQ17zQ== > =B/8v > -----END PGP SIGNATURE----- > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net > For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net > Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ > Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > Thanks to you and the rest of the development team for this early Christmas gift! I am currently running on a version built from git sources downloaded last February and will be compiling R14 from the new source tarballs. Are these instructions current: https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules ?

2 1

Can't modify Desktop Behaviour
by Thierry de Coulon 15 Dec '14

15 Dec '14

Hello all Trinity users, On one machine (a T400), recently installed with Wheezy 7.7 and TDE 3.5.13.2, I can't change the Desktop Behaviour. If I unselect "Show icons on desktop" they stay. If, in Device Icons, I choose "Show device icons", the screen goes black, then comes back unchanged (and the options have also been set back). kdesktoprc seems ok, same as any other install. It's not very important because that's not a main machine but I'm puzzled as to why this happens. Thierry

2 2

kcontrol: /symbol lookup error : /opt/trinity/lib/libkdeinit_kcontrol.so: undefined symbol: _ZN9KListView9selectAllEb
by Felix Miata 15 Dec '14

15 Dec '14

Debian 6.0 system is "up to date", in that apt-get udate; apt-get upgrade find nothing new. TDE is 3.5.13. Settings menu option for Control Center produces nothing, while from Konsole, the message in $SUBJECT. Individual settings from the main menu is among the worst UIs on the planet. Please, how can I get kcontrol working (without hours of updating)? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

3 11

QT5 and Systemd
by Pascal Deporte 11 Dec '14

11 Dec '14

Hello. Trinity Desktop on Debian: I have a question: Do passing KDE 4 (QT4) to KF5 (QT5) will affect the operation of Trinity or development? Another question: For Trinity, is what systemd is a problem or not?

4 3

Confusion about building from sources (R13.2 on Slack 14.1)
by Jagged O'Neill 09 Dec '14

09 Dec '14

High, now I'm trying to build R13.2 on Slackware 14.1, trying to follow the instructions found at https://wiki.trinitydesktop.org/How_to_Build_TDE_Core_Modules This doc leaves several questions open: 1. It doesn't say which release this is about. In the "Suggested Build Order" section it talks about tqt3, so I guess it's about R14 already, though R14 isn't (actually) released yet. And what if any- one is forced (or just likes) to install R13.2 or even older release anyway? 2. It isn't clear about the build tool to use for the different packages. When talking about the autoconf -> cmake migration, there should be some details of which package in which release is to be done with which build tool, or each package should have a quick note about this in the README or whatever... I think qt3 itself is neither, but I'm not sure. It has no 'admin' and no 'cmake' subdirectory, but if this is an acceptable exception for me. It should be mentioned anyway, maybe for others, or maybe merely for the sake of being documented (or is it documented elsewhere already?). 3. Problems compiling tqtinterface: I manually ran ./configure on qt3 and it installed in almost no time, or rather, with almost no fiddling. But now I'm stuck for hours with the second step, tqtinterface. It has both a 'cmake' and an 'admin' subdirectory, but since the page mentioned above lists it in section "Building Packages with cmake", I first tried cmake, indeed. But with the instructions listed under "Performing a cmake Build" it just didn't work. It stopped after failing to run a cmTryCompileExec step, in which the compiler is called with /usr/bin/c++ -I/opt/trinity-3.5.13.2/qt3/include -DHAVE_USABLE_QT3 CMakeFiles/cmTryCompileExec737936600.dir/src.cxx.o -o cmTryCompileExec737936600 -rdynamic -L/opt/trinity-3.5.13.2/qt3/lib -lqt-mt This version is already altered from the "default"... I have put in the include path option, without which even the compilation failed, of course. But even then this step failed, due to countless undefined references, because the command line issued tells the linker to only drag in qt-mt, but none of X11, Xext, dl, z, jpeg, png, mng, and I don't know how many else. I have put in those mentioned here manually in a step-by-step, incremental, very tedious build/less $erroroutput/edit $buildscript process. Shouldn't the script, that tries to compile the program, know which libraries it needs and instruct the linker to drag them in? What am I doing wrong? Of course, maybe the "ready for cmake" list is indeed for R14, and as such doesn't match my sources. Buuuuuut... trying with autoconf also fails, because there isn't even a configure script. Oh, wait, I didn't _re_generate autoconf/automake files yet, as it has been suggested. But then, trying it yields nothing productive anyway: Copying the mentioned files from /usr/share/aclocal/libtool.m4 /usr/share/libtool/config/ltmain.sh (maybe they're wrong?), then running $ make -f admin/Makefile.common *** automake (GNU automake) 1.11.5 found. *** Creating acinclude.m4 make[1]: Entering directory `/home/jagged/src/trinity-build/tqtinterface-trinity-3.5.13.2' make[1]: *** No rule to make target `libltdl/ltdl.m4', needed by `acinclude.m4'. Stop. make[1]: Leaving directory `/home/jagged/src/trinity-build/tqtinterface-trinity-3.5.13.2' make: *** [cvs] Error 1 Well, I'm completely clueless... :-/ Just in case it matters: Slackware 14.1, kernel 3.10.17 gcc version 4.8.2 ld 2.23.52.0.1.20130226 No idea if I should attach the error output from a cmake approach. 4. Some other points that I find a bit confusing - In the "configure and build" code boxes, you use /opt/trinity/lib/qt3* for QTDIR, but /opt/trinity/qt3* in PATH and PKG_CONFIG_PATH. Is this correct? (It could be that some later step establishes some /opt/trinity/lib/qt3* dir, but after configuring qt3 with -prefix=/opt/trinity/qt3, and installing the result, there is no such directory (yet).) - Introducing a parameter named $CPUOPT ist just... well... confusing. So much for now. Thanks in advance for any suggestion. Regards, Jagged PS: Since it is a wiki, I guess I could help improving it, if desired (it's not that I'm an observing but otherwise passive nagger), just at the moment I think my experience is close to zero... -- valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error

3 6

Skype no sound (was: xine finds no audio drivers)
by Robert Peters 08 Dec '14

08 Dec '14

On 6 December 2014 at 10:00, Robert Peters <robertpeters9(a)gmail.com> wrote: > Hi, > I'm running an install from exegnu-jessv-20141125 on a recent > ThinkPad. Amarok when starting complains: > xine was unable to initialize any audio drivers. > Haven't found anything satisfactory in searching, but the problem goes > back at least to KDE3. > BTW, VCL works okay, after I select the mixer. Maybe it uses different drivers. > Robert Got alsa - xine - kmix - amarok working okay, by making sure that basic Trinity packages are installed. Now trying to get sound in Skype. A search showed that newer Skype requires PulseAudio and recommended installing pavucontrol. Compiling from source required installing several dependencies. Dbus strongly recommended, but it has broken dependencies. Still no sound. I wonder if it all requires systemd. In which case, are there any usable Skype alternatives? Robert

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users