6 Mar
2022
6 Mar
'22
8:56 p.m.
On 2022/03/07 11:21 AM, Felix Miata wrote:
Felix Miata composed on 2022-02-15 19:43 (UTC-0500):
I may have mentioned this already, but the source code for jasper 1.9 is available on the
extra dependencies repo.
In debian we build this already. Not sure what is happening in the RPM world though.
https://mirror.git.trinitydesktop.org/gitea/TDE/extra-dependencies/src/bran…
Cheers
Michele
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
I tried installing trinity-tdm on a TW installation that had had only xdm, and
none of Trinity. Installation count came to 57 packages, but "broken",
because
libjasper4 is neither installed nor available. TDM doesn't appear broken in any
functional way, though as usual, I run it "themeless", with the default look
inherited from KDE that I consider to be a theme superior to all others I've been
exposed to.
Since I know nothing meaningful about building, I can't imagine why François
wasn't been able to build using libjasper6. :(
Also, on first attempt to start TDM (at boot), it doesn't, because it wants to
start X before /dev/dri/card0 exists:
# grep \(EE *old
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) Screen 0 deleted because of no matching config section.
[ 7.611] (EE) Device(s) detected, but none match those in the config file.
[ 7.611] (EE)
[ 7.611] (EE) no screens found(EE)
Is this a case where KMS needs to be triggered early in boot? Is there some way to
delay TDM's attempt to get X started? I tried tdmrc OpenDelay=25 instead of 15,
but it didn't help, and neither StartAttempts=5 instead of 4.