Hello
Anoyone have tried to install TDE in Ubuntu WSL?
I tried to start it but some errors arose:
:/opt/trinity/bin$ /opt/trinity/bin/starttde
[starttde] Starting starttde.
[starttde] This script is /opt/trinity/bin/starttde
[starttde] TDE version is R14.0.6
[starttde] TDE base directory is /opt/trinity
[starttde] TDEHOME is not set.
[starttde] Set TDEHOME to /home/jpadilla/.trinity.
[starttde] Setting TDEROOTHOME to /root/.trinity.
/opt/trinity/bin/starttde: 1: test:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program:
unexpected operator
/opt/trinity/bin/starttde: 1: test:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program:
unexpected operator
/opt/trinity/bin/starttde: 1: test:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program:
unexpected operator
/opt/trinity/bin/starttde: 1: eval: Syntax error: "(" unexpected
I can start kdesktop and twin and konqueror but not the whole desktop
experience.
Can you help me?
Greetings
Hi
I am running Ubuntu 16.04 (64bit) and 4.14.06.
Since yesterday I have the following problems
1. when hitting an icon in the panel I receive TDElauncher cannot be
reached via DCOP.
2. When trying to copy the icon to the desktop I also obtain cannot
talk to tdelauncher.
So I have to log out and to logout, then it works for a while but not
for long. What is the issue here?
Regards
Uwe Brauer
Hi,
there is one software the development of which was stopped before KDE
moved to plasma, and hence it requires KDE 3. That's why I have TDE
running on a virtualbox. I would prefer that package to be available
within my system, but I didn't succeed so far. The worst case that
happened was that it rendered my system almost useless.
Here is the setup:
I run Manjaro stable up to date, an Arch derivate. Trinity or TDE is not
available for that distribution, as far as I know.
I want to use Quanta+ from TDE.
Is there a way to get that done? (Maybe I get my hands at the source
code some day, but I have no experience with C++ and am not sure if that
will ever yield workable results).
Regards,
Martin
Hello folks,
Been using TDE on openSUSE for a while(and S.u.S.E since v5.3 *sigh*)
but I think it's time to move to a non systemD infested distro. I'm
not here to debate the merits of it, I've made my decision and I'm
looking for advice from those that run TDE on distros that don't use
systemD.
There's Devuan(never really been a fan of Debian or uBuntu tho). I'm
just afraid that Devuan won't be able to keep up.
Would love to go back to Slackware, but it seems the lastest version
is 3.5.13ish??
Anyway, if you use a non-systemD distro, please let me know how TDE works on it.
Thanx
Hello all,
Just decided to let my Debian 10 update, which it did. Next reboot I got
greeted by xfce's login screen (I had installed Debian with xfce), managed to
find my way back into TDE running the usuall dpkg-reconfigure lightdm.
However I was wondering: if I remove lightdm, what will happen next update?
Thierry
> On 10/19/19, deloptes <deloptes(a)gmail.com> wrote:
> > When you define a problem, you can also find a solution - simply saying "I
> > don't like it" is not a problem definition.
>
> I'm not gonna waste time rehashing why I don't want systemD. Went
> through something similar when KDE4 came out and was told to get with
> the programs and "upgrade". A new version is usually not an upgrade.
>
> > I've been using Debian with sysv-init, but only because systemd was
causing
> > problems and I needed time to learn it. The concept of keeping systemd and
> > using init was a very good solution. I think I'll keep it on the server,
> > but for the desktop, I do not see a reason why you should not use systemd.
>
> Yep and other people don't see why we don't use KDE5 or GNOME3 instead
> of mate/cinnamon.
>
> > I guess you are also not driving a car from the 30ies.
>
> Nope. I have 2 from the 80s though. Would have no problem with a car
> that old. I might spent a bit more in gas, but my paid off vehicles
> don't have a monthly payment & the insurance is cheaper. Always trade
> offs.
>
> Kinda like my almost 15 year old Thinkpad T60p. Does what I need and
> has the 4x3 screen that makes it easier for me to get stuff done.
>
> ---------------------------------------------------------------------
Agreed Larry.
My reply is NOT intended to upset anyone.
It's not my place to tell others what to want or use.
Just answer the question, which is PCLOS Big Daddy build by Alistair Izzard.
Not perfect but I can get everything I need done. Video/audio editing,
desktop publishing, internet, email and more. Very reliable, hasn't failed me
yet. Thanks Ali.
If someone else wants to use something else, wonderful. I look forward the
comparison and stories about it. Difference is wonderful.
Just answer the question, the why of this question belongs only to the one
asking.
For the record....
1974 Chevy Nova Coupe Hatchback RS
Thinkpad T60 with a WD SSD
Kate hopes off the soap box and mysteriously disappears to the mist.
Greetings;
I just noticed that 1 of the 2 lists I had sorted into subdirs by the
year, was placing new incoming messages in a subdir I had prepared to
hold the 2019 messges, even though the filter rules said to put new
incoming that matched that filer rule, into the main folder.
So I shift marked the 2019 folders content a month at a time and drug it
back to the main emc folder, leaving the 2019 folder empty, so I deleted
in and its 3 subdirs. This of course crashed kmail. On restart, its now
doing 95%+ but is doing it for only a few milliseconds per core,
switching faster than gkrellm can accurately track. But for some reason
its skipping core2? ?? ??? And then it crashed again, and I submitted
that report. Now on the restart, which nicely saved this message, its
back to using all 4 cores for a couple seconds each. But I mentioned
it, so it just stuck on core0 for about 15 seconds.
Now trying to get some clues from lsof and a few filter stages of grep, I
find one instance per year for the emc folder, but the other, "coco"
folder and all its subdirs will need a final |wc -l showing 170
instances. I just found I'd not nukes the coco's 2019 indice stuff, so
one more restart. But I'll send this first...
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Greetings all;
Are you send those to /dev/null? I've sent a whole bunch of them.
These crashes always seem to be preceded by a couple days of a kmail
session burning up a core of 4 cores, bouncing to the next available
core, at 99 to 100% at 15 second or so intervals.
These seem to be related to kmail finding trash files in its database,
causing problems while re-indexing. I have two folders which are
subfolders with a given years messages manually sorted into that years
corpus.
When I relaunch kmail after one of these crashes, I am getting advisories
that so-and-so has an index problem, and its generally the top level
folder, and 2 or 3 of its subfolders that are named. And the older
folders are slowly being emptied, as in messages are disappearing
despite having no expiry set up.
Can anything be done, or is there something I can check-uncheck
someplace?
Thanks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Hi,
recently I followed your discussion regarding "device monitor". I did a
refresh on the repository yesterday and compiled latest what I got,
installed today and two things made a very good impression.
The icon and "Device Monitor" is nice and secondly suddenly my tdebluez app
started notifying me when I connect or disconnect one of the phones. I am
sure this was not working before and I am not aware of changing anything on
the code in this context, so something must have been repaired perhaps in
the context of device management.
Thank you all for the effort!