tde-users

users@trinitydesktop.org

9 participants
4393 discussions

KDM Bug?
by Mag. Dr. Nikolaus Klepp 28 Jan '12

28 Jan '12

Could somebody please verify on Debian/Wheezy: Running KDM select FVWM (or any other WM) as sessiontype. Log in, FVWM starts but trerminates immediatle. .xsession-errors says, that an other WM is already running and FVWM should be started with "-replace". Nik -- Mag. Dr. Nikolaus Klepp Einnehmerstraße 14 A-4810 Gmunden Tel.: +43 650 82 11 724 email: office(a)klepp.biz

2 2

reordering Documents list in Kate
by Calvin Morrison 28 Jan '12

28 Jan '12

Hi, is it possible to reorder documents within kate's Documents side bar? I know you can sort them, but I often would like to be able to change this. I think I am just missing an obvious option. Calvin

3 4

qt3 download
by Bartlomiej Zimon 27 Jan '12

27 Jan '12

Hi all How to download qt3 from git because link from HowToBuild provides to empty file Best regards Bartlomiej Zimon

2 5

Kicker appler
by L0ner sh4dou 27 Jan '12

27 Jan '12

Does anyone know if there is an applet for kicker that runs periodically a script and displays it's output. I have a script that once run displays me current CPU temp. Usually I run periodically in a terminal using watch command, but I'd like to incorporate it's result into kicker panel, since running a konsole for just one command that displays something like "64C" is a little overkill to me, and uses too much of my workspace.

5 8

Problems with kwin
by Jeff Taylor 27 Jan '12

27 Jan '12

I've been running trinity since the ubuntu team tried to shove kde4 onto us. Through the various versions, and including most recently with a clean install off the trinity maverick cd, I have had the problem that when I log out of my desktop, kde does not save what programs I had open at the time (which should be restored when I log back in). The only solution I have found to this issue is to link to kwin in ~/.kde3/Autostart/ (now with 3.5.13 its in ~/.trinity/Autostart/). Also of note is that kwin is NOT found in 'ps' unless I do this. Now it is my understanding that if kwin is not running, I should be seeing a lack of desktop affects - noticeable things like window borders and such - however when my desktop starts up there are no apparent visual problems. Yet unless I start kwin in Autostart, when I log out of my desktop and back in again, I am always returned to a desktop with konsole and firefox opening up, but nothing else. Once kwin is added to Autostart, my desktop always opens up to whatever programs I had running when I logged out (including correct window and multi-desktop placement). My wife's system: maverick trinity with the standard updates applied. My system: maverick trinity installed, do-release-upgrade to natty, then pulled the apt sources to upgrade to trinity 3.5.13. Through none of these steps did kwin save my desktop on logout. What I would like to know is if there was an issue at some point along this path that kwin did not get added to the normal kde startup process, and if there is a more appropriate way that I should get it to run when a user logs in?

6 14

Update Errors
by Raevyn Vieria-Madison 27 Jan '12

27 Jan '12

Hello So I installed Kubuntu 11.10 (Oneirc or whatever) and then installed Trinity. It seemed to go fine, until I logged in. I originally had one Adept update showing for something to do with Ogg (sorry.. I generally just update without to much evaluating) but it failed. I then tried updating again and this time, the enclosed screenshot is what I got. Several broken updates. And now it appears to have locked the /var/ directory O.o Does anyone have any ideas?

2 1

repository
by Frank Lienhard 26 Jan '12

26 Jan '12

Hello, I recently hadn't much time to follow the maillist, so sorry if that's kind of unnecessary question. The repository for installation is ready for installations and (in my case) nightly sync for local repositories again? Thanks for all the great work in any case Frank

2 1

kdm-trinity bug question
by James D. Freels 25 Jan '12

25 Jan '12

From a regular user ... I have also noticed the runaway cpu issue with kdm-trinity. I also understand that the issue is to be resolved with the release of R14 of the trinity desktop (3.5.14 ?). In the mean time, I have been using gdm for my login desktop, but I would prefer to use kdm-trinity. Is there anyway to obtain a package now with the bug corrected for 3.5.13 ? I can wait, but I am impatient at times ... I can build packages using apt-get -b source ... -- James D. Freels, Ph.D. Oak Ridge National Laboratory freelsjd(a)ornl.gov 865-576-8645

2 2

Trinity on Xephyr
by Raevyn Vieria-Madison 25 Jan '12

25 Jan '12

Hey all! I am wondering if anyone has tried using Xephyr with Trinity? I discovered it when I just installed Debian to make a desktop of GNOME an I found a site that talks about getting KDE 4 to work with it, but I am meeting no success. The program is installed and seems to work, but I cant get kdm or gdm or anything to come up is all. The site was: http://techbase.kde.org/Getting_Started/Run/Nested_Session

1 0

Couple of problems with V3.5.13
by leee 22 Jan '12

22 Jan '12

Hi, I've just upgraded a couple of my Debian Squeeze systems to Trinity V3.5.13 and I've hit a couple of problems straight away, one very serious and the other less so. I haven't checked the full Trinity/KDE suite yet for any other problems but the two I've had so far mean I'm going to have to regress - which will take a lot of time and will not be fun. The lesser of the two problems is that ksysguard can no longer see the lm-sensors readings. Xsensors still worked, confirming that lm-sensors was still ok, so I tried regressing ksysguardd & ksysguard back to V3.5.12, which was only partly successfull; whilst ksysguard V3.5.12 would now pick up the lm-sensors data when run as a desktop app, the panel applet failed completely, telling me I should check my installation. The more serious problem concerns the changes to kdm and the kdm greeter. One of the systems I upgraded is used primarily as a render node and has no keyboard, mouse or monitor attached to it - I maintain and configure it entirely via vnc. I noticed that, after logging into it via ssh and running 'top', kdm_greet was 'thrashing', using ~99% cpu. When I actually started a Trinity session kdm_greet cpu dropped to ~85% but artsd was now using ~10% cpu and kicker was using ~2% cpu. After artsd 'timed-out' its cpu usage dropped and kdm_greet picked up the slack, rising back up to ~97% cpu. Kicker cpu remained at ~2%. I found the earlier thread in the mailing list archives concerning disabling the Ctrl/Alt/Delete 'feature' and while this does indeed stop the Ctrl/Alt/Del feature on the other system I upgraded, which does have a kb, mouse & screen, it did nothing to stop kdm-greet from thrashing the cpu on the 'headless' system. This is a _big_ show stopper, for me at least, hence the _need_ to regress. I'm also a bit perturbed as to why this change to kdm was made in the first place. I moved to KDE3 because Gnome had been dumbed down too much and because the Gnome devs seemed intent on on forcing people to work in the way that _they_ thought people should work. I subsequently moved to Trinity because of similar issues with KDE4 but now Trinity seems to be showing signs of following along the same path. Whilst this new Ctrl/Alt/Del 'feature' may have seemed like a 'Good Idea' at the time it was not one of the original features of KDE3 and significantly changes its behaviour. However, it was precisely because I wanted retain the original KDE behaviour that I switched to Trinity in the first place. Another change I noticed after the upgrade that showed similar signs of this trend was that the Reveal Desktop applet had been added to my Quick Launcher tray. Now personally, I don't have _any_ desktop icons, precisely because I don't want to have to waste time revealing the desktop to get at a hidden icon and then have to re-show all the windows I had open, which is why I use the quick launcher in the first place (and in any case I wouldn't/don't have desktop icons for specific data items either because there isn't enough desktop real estate, even at 1920x1200 for all the different data items I use). Sure, this one was easily fixed, first by making it removable (it was pegged as unremovable) and then removing it, but why was it force-added when, if I had wanted it, it would have already been there in the first place? I'm now a bit confused about the purpose of Trinity. I was under the impression that the project was started to so that people who knew what they were doing and knew how they wanted to work could continue to do so without having changes to their systems and workflows forced upon them. In this context, it seemed that Trinity was never intended to challenge the other mainstream desktop environments, which have been dumbed down by their developers to force their [the developer's] ideas of best practice upon a perceived lowest common denominator user. If this is/was the case then that old maxim applies - it if isn't broke, don't try to fix it. Now whilst I have to admit that my first post to this list has been rather critical I'd like to emphasise that I'm not trying to flame anyone here; far from it in fact. So far, Trinity has been a godsend to me, enabling me to carry on working how _I_ want to work, for which I am very greatfull indeed. However, I do need to decide though, whether I'm going to be able to continue using it for the foreseeable future. Regards, LeeE

3 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users