10 Mar
2023
10 Mar
'23
5:21 a.m.
I made these comments in response to a different topic and suspect
they were overlooked as a result. Hence, another attempt. On a Fedora
37 system with KDE (5) working, I installed TDE. All of it except
the applications.
Having KDE 5 installed before installing TDE seems to have resulted
in some confusion. The DE startup splash screen, for example, says it
is starting Plasma by KDE. Once started, it does appear to actually
be TDE.
But some parts of TDE don't work as expected. For example, the TDE
Control Center doesn't start if selected from the start menu. Nothing
at all happens. Starting kcontrol from a shell does start what appears
to be the program but nothing in it works. On exit, the shell reports,
"WARNING: No TDE menu group with X-TDE-BaseGroup=settings found |
Defaulting to Settings/".
Is this sort of installation expected to work? Would it have been
better to start with a fresh install?
--
Dave Close, Compata, Irvine CA "What right does Congress have to go
dave(a)compata.com, +1 714 434 7359 around making laws just because they
dhclose(a)alumni.caltech.edu deem it necessary?" -- Marion Barry
10 Mar
10 Mar
9:23 p.m.
On Thursday 09 Mar 2023 21:21:58 Dave Close via tde-users wrote:
I made these comments in response to a different topic
and suspect
they were overlooked as a result. Hence, another attempt. On a Fedora
37 system with KDE (5) working, I installed TDE. All of it except
the applications.
Having KDE 5 installed before installing TDE seems to have resulted
in some confusion. The DE startup splash screen, for example, says it
is starting Plasma by KDE. Once started, it does appear to actually
be TDE.
But some parts of TDE don't work as expected. For example, the TDE
Control Center doesn't start if selected from the start menu. Nothing
at all happens. Starting kcontrol from a shell does start what appears
to be the program but nothing in it works. On exit, the shell reports,
"WARNING: No TDE menu group with X-TDE-BaseGroup=settings found |
Defaulting to Settings/".
Is this sort of installation expected to work? Would it have been
better to start with a fresh install?
I am using TDE installed after KDE-4 all the time, and I love it. I can get
the best of both worlds, using KDE-4 apps in TDE when I prefer them to the
Trinity versions, and using the Trinity versions when I prefer them. However
this is an old system, installed around March 2017, with Trinity installed
over a late Debian Jessie system that came with KDE-4. I installed TDM, so
that is what I log in with. I actually work in TDE all the time, unless I
have to use one of two programs that used not to work in Trinity. I just
started one of those programs, Geomview, in Trinity just now, and to my
surprise, it opened some windows. So perhaps I might even be able to use that
in Trinity now.
Regards, Chris
11 Mar
11 Mar
2:04 a.m.
On Friday 10 March 2023 03:23:18 pm Chris Austin via tde-users wrote:
I've done this in the past as well. I do remember that a few programs would
only not cause problems if the were run in a different Desktop (which I
thought was weird, but 'eh, it worked).
Best,
Michael
On Thursday 09 Mar 2023 21:21:58 Dave Close via
tde-users wrote:
> I made these comments in response to a different topic and suspect
> they were overlooked as a result. Hence, another attempt. On a Fedora
> 37 system with KDE (5) working, I installed TDE. All of it except
> the applications.
Hi Dave,
AFAIK all of TDE has been re-named so that it does not interfere with, or is
interfered by, KDE. Slávek would have the definitive answer.
I’m going to guess that not installing all of TDE caused the odd behavior. I
would try creating a live USB (Fedora 37 w/ KDE5) and then install all of TDE
to it for testing.
> Having KDE 5 installed before installing TDE
seems to have resulted
> in some confusion. The DE startup splash screen, for example, says it
> is starting Plasma by KDE. Once started, it does appear to actually
> be TDE.
That would be normal until you re-configure the startup splash screen from
using KDE to using TDE's [login manager?] (I don't know the actual name of
that).
But some parts
of TDE don't work as expected. For example, the TDE
Control Center doesn't start if selected from the start menu. Nothing
at all happens. Starting kcontrol from a shell does start what appears
to be the program but nothing in it works. On exit, the shell reports,
"WARNING: No TDE menu group with X-TDE-BaseGroup=settings found |
Defaulting to Settings/".
Is this sort of installation expected to work? Would it have been
better to start with a fresh install?
I am using TDE installed after KDE-4 all the time, and I love it. I can
get the best of both worlds, using KDE-4 apps in TDE when I prefer them to
the Trinity versions, and using the Trinity versions when I prefer them.
However this is an old system, installed around March 2017, with Trinity
installed over a late Debian Jessie system that came with KDE-4. I
installed TDM, so that is what I log in with. I actually work in TDE all
the time, unless I have to use one of two programs that used not to work in
Trinity. I just started one of those programs, Geomview, in Trinity just
now, and to my surprise, it opened some windows. So perhaps I might even
be able to use that in Trinity now. 
2:08 a.m.
On 3/10/23 8:04 PM, Michael via tde-users wrote:
AFAIK all of TDE has been re-named so that it does not
interfere with, or is
interfered by, KDE. Slávek would have the definitive answer.
What does that mean? All conflicting binary and lib names have been
renamed? TDE can be installed in /usr along with KDE and other normal
DEs? Or TDE remains relegated to /opt purgatory?
4:24 a.m.
On 2023-03-10 20:08:37 Darrell Anderson via tde-users wrote:
On 3/10/23 8:04 PM, Michael via tde-users wrote:
I'm not sure about KDE plasma, but when the KDE team replaced KDE3 with KDE4 they
assumed
that their users would immediately upgrade their KDE, so they used the same program or
library names that KDE3 had been using, so that mixing programs or libraries from both
KDEs caused a certain amount of chaos.
The Trinity team has converted all of the Trinity component names to avoid collisions
between KDE and TDE, but until they completed that migration it was not possible to have
both KDE and TDE installed at the same time.
Leslie
--
Platform: GNU/Linux
Hardware: x86_64
Distribution: openSUSE Leap 15.4
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0
AFAIK all of TDE has been re-named so that it
does not interfere with, or
is interfered by, KDE. Slávek would have the definitive answer.
What does that mean? All conflicting binary and lib names have been
renamed? TDE can be installed in /usr along with KDE and other normal
DEs? Or TDE remains relegated to /opt purgatory? 
7:18 a.m.
On Saturday 11 of March 2023 03:08:37 Darrell Anderson via tde-users wrote:
On 3/10/23 8:04 PM, Michael via tde-users wrote:
Many libraries and several binaries have been renamed, but there are still
many binaries that could cause conflicts in the event of installation
in /usr/... so there is still a good idea to install TDE in a separate
directory such as /opt /trinity/... The renaming of all other libraries
and binaries is still a big topic that we will not avoid sooner or later.
Because such extensive renaming, however, will not benefit existing users,
but potentially only problems, it requires thorough planning and has a
lower priority.
Cheers
--
Slávek
AFAIK all of TDE has been re-named so that it
does not interfere with,
or is interfered by, KDE. Slávek would have the definitive answer.
What does that mean? All conflicting binary and lib names have been
renamed? TDE can be installed in /usr along with KDE and other normal
DEs? Or TDE remains relegated to /opt purgatory?
____________________________________________________
4:20 a.m.
On 2023-03-10 20:04:25 Michael via tde-users wrote:
I've done this in the past as well. I do remember that a few programs
would only not cause problems if the were run in a different Desktop (which
I thought was weird, but 'eh, it worked).
Best,
Michael --
Platform: GNU/Linux
Hardware: x86_64
Distribution: openSUSE Leap 15.4
Desktop Environment: Trinity
Qt: 3.5.0
TDE: R14.0.13
tde-config: 1.0
On Friday 10 March 2023 03:23:18 pm Chris Austin via
tde-users wrote:
Here's what my openSUSE system, which uses update-alternatives to
switch between multiple
applications, shows:
| ~
| ● update-alternatives --config default-displaymanager
| There are 5 choices for the alternative default-displaymanager
(providing /usr/lib/X11/displaymanagers/default-displaymanager).
|
| Selection Path Priority Status
| ------------------------------------------------------------
| * 0 /usr/lib/X11/displaymanagers/tdm 30 auto mode
| 1 /usr/lib/X11/displaymanagers/console 5 manual mode
| 2 /usr/lib/X11/displaymanagers/gdm 25 manual mode
| 3 /usr/lib/X11/displaymanagers/lightdm 15 manual mode
| 4 /usr/lib/X11/displaymanagers/tdm 30 manual mode
| 5 /usr/lib/X11/displaymanagers/xdm 10 manual mode
|
| Press <enter> to keep the current choice[*], or type selection number:
| @22:14:55,root@pinto rc=0
Even if your system doesn't use update-alternatives, you should find a
displaymanagers
subdirectory somewhere in your system. Perhaps you'll have to look for
"kdm" in your
library directories?
Leslie
On Thursday 09 Mar 2023 21:21:58 Dave Close via
tde-users wrote:
> I made these comments in response to a different topic and suspect
> they were overlooked as a result. Hence, another attempt. On a Fedora
> 37 system with KDE (5) working, I installed TDE. All of it except
> the applications.
Hi Dave,
AFAIK all of TDE has been re-named so that it does not interfere with, or
is interfered by, KDE. Slávek would have the definitive answer.
I’m going to guess that not installing all of TDE caused the odd behavior.
I would try creating a live USB (Fedora 37 w/ KDE5) and then install all of
TDE to it for testing.
> Having KDE 5 installed before installing TDE
seems to have resulted
> in some confusion. The DE startup splash screen, for example, says it
> is starting Plasma by KDE. Once started, it does appear to actually
> be TDE.
That would be normal until you re-configure the startup splash screen from
using KDE to using TDE's [login manager?] (I don't know the actual name of
that). But some
parts of TDE don't work as expected. For example, the TDE
Control Center doesn't start if selected from the start menu. Nothing
at all happens. Starting kcontrol from a shell does start what appears
to be the program but nothing in it works. On exit, the shell reports,
"WARNING: No TDE menu group with X-TDE-BaseGroup=settings found |
Defaulting to Settings/".
Is this sort of installation expected to work? Would it have been
better to start with a fresh install?
I am using TDE installed after KDE-4 all the time, and I love it. I can
get the best of both worlds, using KDE-4 apps in TDE when I prefer them
to the Trinity versions, and using the Trinity versions when I prefer
them. However this is an old system, installed around March 2017, with
Trinity installed over a late Debian Jessie system that came with KDE-4.
I installed TDM, so that is what I log in with. I actually work in TDE
all the time, unless I have to use one of two programs that used not to
work in Trinity. I just started one of those programs, Geomview, in
Trinity just now, and to my surprise, it opened some windows. So perhaps
I might even be able to use that in Trinity now.
421
days inactive
422
days old
6 comments
6 participants
participants (6)
-
Chris Austin -
Darrell Anderson -
Dave Close -
J Leslie Turriff -
Michael -
Slávek Banko