31 May
2014
31 May
'14
11:14 p.m.
High everyone,
I tried to install TDE on OS 13.1 earlier this year, on a VM somewhere on
the net, and though I found helping minds here, I abandoned the idea, due
to the fact that it won't be very useful anyway over a sluggish connection
as mine.
Now I got a new box, on which I want to install Trinity, because it's the
only DE that I find really useful. I guess the computer is powerful enough
to even run KDE 4, but I want my kicker...
So much to the asides, now to the point:
When I tried to install TDE on that VM, I've had problems obviously because
there were already KDE 4 components installed; I remembered that and avoided
any other KDE stuff by just installing the base system with minimal X.
I followed the steps described on
http://trinitydesktop.org/wiki/bin/view/Documentation/OpenSUSEBinaryInstall…
and it was fine until I reached the `zypper install trinity-desktop` command.
I tried both the command line version and the YaST frontend, and both
complained:
-----------------
Problem: trinity-desktop-3.5.13.2-2.oss131.opt.noarch requires trinity-tdenetwork >=
3.5.13.2, but this requirement can not be provided
uninstallable providers: trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64[trinity]
Solution 1: do not install trinity-desktop-3.5.13.2-2.oss131.opt.noarch
Solution 2: break trinity-desktop-3.5.13.2-2.oss131.opt.noarch by ignoring some of its
dependencies
-----------------
Okay, but the objected package is there... what's wrong?
I then tried to first install tdenetwork first (only command line), and it
also complained, but in a way that I really did not expect:
-----------------
Problem: nothing provides jasper needed by
trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64
Solution 1: do not install trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64
Solution 2: break trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64 by ignoring some of its
dependencies
-----------------
I'm a peaceful man, so I decided not to break anything, hence I'm back
again on this mailing list to ask for your help. I'm sure you know already
what went wrong...
Thanks in advance and best regards,
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
1 Jun
1 Jun
8:23 a.m.
New subject: [trinity-users] OS13.1: nothing provides trinity-tdenetwork-*, jasper, maybe others?
Le 01/06/2014 01:14, Jagged O'Neill a écrit :
[...]
I then tried to first install tdenetwork first (only command line), and it
also complained, but in a way that I really did not expect:
-----------------
Problem: nothing provides jasper needed by
trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64
Solution 1: do not install trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64
Solution 2: break trinity-tdenetwork-3.5.13.2-3.oss131.opt.x86_64 by ignoring some of
its dependencies
-----------------
I'm a peaceful man, so I decided not to break anything, hence I'm back
again on this mailing list to ask for your help. I'm sure you know already
what went wrong...
This is really strange that zypper complains about missing jasper,
because the jasper package exists and is located in the main repository !
For example:
http://suse.uni-leipzig.de/pub/ftp.opensuse.org/opensuse/distribution/13.1/…
Are you sure you haven't disabled the main opensuse repository by
incident in Yast ?
Francois
10:39 a.m.
New subject: [trinity-users] OS13.1: nothing provides trinity-tdenetwork-*, jasper, maybe others?
On Sun, Jun 01, 2014 at 10:23:48AM +0200, François Andriot wrote:
Are you sure you haven't disabled the main
opensuse repository by
incident in Yast ?
Yes, I'm quite sure, no such accident happened...
Because I deactivated it deliberately :-D (I'm under limited bandwidth
currently, and since I installed OS from the DVD Image anyway, I wanted
to stay with this until the machine is set up far enough to update all
packages in one go.
And I didn't reckon with such fundamental packages (it's a jpeg lib, as
I just read) to not be on the DVD.
Anyway, I reactivated the online repos and tried again. And yes, this
time it could find jasper, but instead it complained:
- trinity-desktop can't be installed because nothing provides
trinity-tdeaccessibility
trying to install this manually beforehand, complains about:
- nothing provides libmad.so.0()(64bit) needed by trinity-ksayit-*
Learning from former errors, I now just enabled _all_ online repos that
the installer originally established, even those that it didn't activate
on its own. Still, when looking up libmad, the only matching packages
are trinity-akode-libmad and its debuginfo.
(If I remember correctly from some months ago,) trinity-desktop is a
meta package, right? I could just manually select tde, twin, tdm and
kicker and hope it won't break by dependencies? Quick-try...
Now I am a bit surprised... starting with just "kicker" (thinking it
will drag in twin and other stuff...) it actually dragged in things
of which I really didn't imagine they exist at all, e.g.:
- kdebase3-runtime (from openSUSE-13.1-OSS)
- kde3libs (from the same repo)
So there's still "support" for KDE 3.5.10 in OS?
Anyway, I'm afraid, from my VM experiences some time back, that it
would raise problems with the TDE installation, if I'm going to install
any original KDE component.
Sooo... I hope you see this through (I don't) and can help...
Thanks again
Best regards,
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
11:50 a.m.
New subject: [trinity-users] OS13.1: nothing provides trinity-tdenetwork-*, jasper, maybe others?
Le 01/06/2014 12:39, Jagged O'Neill a écrit :
On Sun, Jun 01, 2014 at 10:23:48AM +0200, François
Andriot wrote:
The "libmad" library, as well
as some other "tainted" libraries (mostly
audio/video related stuff such as ffmpeg ...), is not provided by
opensuse itself, nor provided by trinity project.
It is provided by the 3rd party "packman" repository.
You should have added it manually to your computer, or download and
install packages manually.
See: http://packman.links2linux.org/
Are you sure you haven't disabled the main
opensuse repository by
incident in Yast ?
Yes, I'm quite sure, no such accident happened...
Because I deactivated it deliberately :-D (I'm under limited bandwidth
currently, and since I installed OS from the DVD Image anyway, I wanted
to stay with this until the machine is set up far enough to update all
packages in one go.
And I didn't reckon with such fundamental packages (it's a jpeg lib, as
I just read) to not be on the DVD.
Anyway, I reactivated the online repos and tried again. And yes, this
time it could find jasper, but instead it complained:
- trinity-desktop can't be installed because nothing provides
trinity-tdeaccessibility
trying to install this manually beforehand, complains about:
- nothing provides libmad.so.0()(64bit) needed by trinity-ksayit-*
Learning from former errors, I now just enabled _all_ online repos that
the installer originally established, even those that it didn't activate
on its own. Still, when looking up libmad, the only matching packages
are trinity-akode-libmad and its debuginfo.
(If I remember correctly from some months ago,) trinity-desktop is a
meta package, right? I could just manually select tde, twin, tdm and
kicker and hope it won't break by dependencies? Quick-try...
Now I am a bit surprised... starting with just "kicker" (thinking it
will drag in twin and other stuff...) it actually dragged in things
of which I really didn't imagine they exist at all, e.g.:
- kdebase3-runtime (from openSUSE-13.1-OSS)
- kde3libs (from the same repo)
So there's still "support" for KDE 3.5.10 in OS?
There are still some KDE3 packages in the opensuse main repository, but
you should not install them.
Instead, you must install their TDE equivalents. This is easy: all
trinity packages are prefixed with "trinity-".
In your example, install packages "trinity-kicker", "trinity-twin",
"trinity-tdm", etc ... and not "kicker", "kdm",
"kwin" ...
So, first, remove anything related to kde3:
zypper remove kdelibs3 kdebase3 arts
See the entire command line here:
https://www.trinitydesktop.org/wiki/bin/view/Documentation/OpenSUSEBinaryIn…
Then, install the Trinity packages.
If you do not want the entire Trinity stuff, you can install a smaller
metapackage called "trinity-tdebase", which allows to run a Trinity session.
zypper install trinity-tdebase
François
Anyway, I'm afraid, from my VM experiences some time back, that it
would raise problems with the TDE installation, if I'm going to install
any original KDE component.
Sooo... I hope you see this through (I don't) and can help...
Thanks again
Best regards,
Jagged
1:22 p.m.
New subject: [trinity-users] OS13.1: nothing provides trinity-tdenetwork-*, jasper, maybe others?
Due to all the new exaltation, I almost forgot to reply here ;-)
On Sun, Jun 01, 2014 at 01:50:17PM +0200, François Andriot wrote:
I didn't even install any of those. (And sorry for my imprecision; these
KDE packages were auto-selected when I chose to install trinity-kicker.)
The "libmad" library, as well as some other
"tainted" libraries
(mostly audio/video related stuff such as ffmpeg ...), is not
provided by opensuse itself, nor provided by trinity project.
It is provided by the 3rd party "packman" repository.
You should have added it manually to your computer, or download and
install packages manually.
See: http://packman.links2linux.org/
Yes, heard about packman before :-/ just added it and now TDE installed
So there's still "support" for KDE
3.5.10 in OS?
There are still some KDE3 packages in the opensuse main repository,
but you should not install them.
So, first, remove anything related to kde3:
zypper remove kdelibs3 kdebase3 arts If you do not want the entire Trinity stuff, you can
install a
smaller metapackage called "trinity-tdebase", which allows to run a
Trinity session.
zypper install trinity-tdebase
Yeah, I opted for that one; first I was a bit irritated, because "after"
installing the packages, YaST just quit, where on my older systems it
took quite some time to run configurations afterwards --- now it looked
as if it just crashed at one point. Looked into `yast2 sw_single` and
everything seemed to be fine.
Then I just set TDM as the default, `init 1; init 5`, and I was presented
with TDM. After putting in the password the irritation went on --- I just
had an empty screen, and mouse clicking did nothing... oh, right click
gave a menu... I was in TWM... just 5 more seconds of irritation, then
I logged out, chose TDE in the login menu, and now (almost) everything is
fine.
The only thing I figured to not work was starting a new (second) session.
The screen went black and for about 30 seconds I couldn't do anything;
then I was presented with the TDM login screen again. Not for the second
session, but for a freshly started first one --- the other session has
been killed.
Second thing: <Ctrl>-<Alt>-<Del> doesn't work, but I assume it's
something
in the settings...
Anyway, thanks for your help and time, I really appreciate it!
I'm gonna have a great time without KDE4/Gnome/blablabla... :-)
Best regards,
Jagged
--
valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error
3617
days inactive
3618
days old
4 comments
2 participants
participants (2)
-
François Andriot -
Jagged O'Neill