Hello,
On a new Lenovo ThinkPad T440S I installed Trinity from
exegnulinux_4.2.iso dated 24-Jul-2013. This is in addition to a
preinstalled Windows 7 Professional. Running wicd does not detect any
wireless networks, however, wicd in Trinity in my older laptop does
detect them. And Windows in the ThinkPad also detects the networks,
so wireless must be enabled. AND wicd doesn't even see a wired
network when connected with a LAN cable.
Do I need to configure wicd?
Or install from a newer image such as exegnu_wheezy_r14_26032014.iso?
Or install (L|X)Ubuntu and set up Trinity on top of that?
Robert
I've just upgraded to Debian Jessie, and things seem to work, with two
exceptions:
1 I couldn't run xinit /opt/trinity/bin/startkde
because ksmserver-trinity was not reinstalled by default. I think
because of dependency problems,
since I had to downgrade a few packages to get it to install. But that
is now sorted.
2 Having got Trinity to run, everything (so far) seems to work
except kmail, my favourite program!
4:3.5.13.2-0debian7.0.0.+0 has been installed.
I get the following:
23:40 ~>kmail
kmail: error while loading shared libraries: libkmailprivate.so:
cannot open shared object file: No such file or directory
But it's there...
23:41 ~>la /opt/trinity/lib/libkmailprivate.so
-rw-r--r-- 1 root root 8071664 Jun 14 2013
/opt/trinity/lib/libkmailprivate.so
It seems to be the only file with this problem - it has the same
permissions as all the rest.
Where do I look next?
And before you ask, no, I'm not using kmail to write this, but
webmail, so sigs and things are a bit different...
cheers
ant
I already said this twice in the past, but there wasn't much response: I'd like to help with
translating Trinity into Polish language. At the moment there are many translations missing. I am
willing to do the translation as long as I don't need to get into technical details like learning
some fancy developer tools and alike. Just plain text files or some really simple dev tools.
Janek
I'm referring to the batch of packages at
http://www.mirrorservice.org/sites/trinitydesktop.org/trinity/releases/3.5.…
as the "official" 3.5.13.2 SRU, and was wondering if things like the old KDE
desktop-popup-on-usbstick-insert is expected to work?
I'm running hal-0.5.14, though that may not have been installed at the time I
compiled kdelibs-trinity-3.5.13.2. I do notice that the
kdelibs-trinity-3.5.13.2 that's on the official 3.5.13.2 SRU release page
does _not_ have a visible "WITH_HAL" option, nor any other h/w related
settings such as "WITH_UDISK" etc.
So is it a known "feature" that this release doesn't isn't expected to work
with hot-pluggable h/w, or is it just me?
z.
Hello,
I'm a bit frustrated:
http://www.mirrorservice.org/sites/trinitydesktop.org/trinity/releases/3.5.…
gives a list of trinity packages in TDE 3.5.13.2. To use one example of a
package listed on that page (there are many more examples), I can get
kdelibs-trinity-3.5.13.2.tar.xz from there.
Now I go to the git webpage:
http://git.trinitydesktop.org/cgit/
and there is no such package as kdelibs-trinity or kde* anything for that
matter.
But, there is tdelibs, with a tdelibs-3.5.13.2 tarball:
v3.5.13.2 tdelibs-3.5.13.2.zip tdelibs-3.5.13.2.tar.gz Slávek Banko 10
months
So, just to state what's looking pretty obvious, your
http://www.mirrorservice.org/sites/trinitydesktop.org/trinity/releases/3.5.…
release page is about as useful as tits on a boar, right?
Look, tdelibs-3.5.13.2, for all intents and purposes, has the appearance of
belonging to trinity-blah-blah-blah release "3.5.13.2". But its not listed
on the release page for the oh so boldly announced: "2013.07.21: Trinity
Desktop Environment 3.5.13.2 SRU Released!"
Why am I wrong in assuming that packageXXX-3.5.13.2 would belong to the "TDE
3.5.13.2 SRU Released!" collection of tarballs? Isn't 3.5.13.2 == 3.5.13.2 ?
Maybe not.
And even if I'm wrong about that, why isn't kdelibs-trinity even so much as
listed on the GIT page? Even if its obsolete, there should a dead-link or
something there saying so...whatever, not important.
What is important is the fact that kdelibs-trinity-3.5.13.2 is vastly
different than tdelibs-3.5.13.2, to wit, tdelibs has additional directories
and functionality, etc. So two packages, each with the same version, only
one of which is needed, and both of which fullfill the same role, are
currently in a state where the obsolete one is listed as part of the official
release download page, and the good one can't even be found referenced as
part of the official release.
So is there a collection of tarballs for a particular release, such as
3.5.13.2 SRU, or not? Should I just pull all tarballs from the git page?
And if its just something as simple as a rename of kdelibs-trinity ->
tdelibs, why wasn't the version bumped when extra directories were added?
Never mind, I don't care about the "why" of anything. I just want to know
where the hell I can download a set of "official" (whatever that means)
packages for tde-3.5.13.2. And the release page ain't it...And by the way,
I'm looking for source code, not some pansy mamby-pamby prebuilt set of
binaries.
Thanks,
z.
I tried the latest r14 nightly out on Ubuntu 12.04 for the most part it works very well, hats off to you guys.
Seems faster than 3.5 and svg files seem to be handled better in this version. I like the reorganization of the control panel menus.
A couple of small things I noticed Konqueror the file manager locks up (on two machines and a VM) requiring it to be shut then reopened. Also KLcdDimmer no longer works in this version. If I get some free time I will open bug reports but I am not really sure what to put in for the file manager I get no errors it just stops responding but will let me close it and reopen no issues.
> I have repaired HAL-related problems before by completely purging and
> reinstalling the hal and hal-trinity packages and their configuration
> files (literally, via "sudo dpkg --purge --force-all hal-trinity
> libhal-storage1 libhal1" followed by "sudo apt-get -f install"). You
> might want to give this a try, as HAL tends to have rather severe problems
> after a dist-upgrade in my experience.
I tried that but it didn't help. I also tried purging hal package but with no result.
One thing that changed after the upgrade is that kpowersave icon in the tray is greyed out when I
log into Trinity, as if HAL was not accessable. Only after several seconds it becomes normal.
Please note that kpowersave reports HAL as enabled and complains when I shut down hal daemon. So
there seems to be some communication between them (just reading from HAL?). Is there any way I
can debug this? I recall struggling with similar problem under KDE3 and OpenSUSE. Back then it
was a matter of some dbus permissions.
> This embarrassing situation was a strong motivator for the complete
> removal of HAL in R14. ;-)
This begs the question when will R14 be released.
Janek
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
> Hi Timothy,
>
> I'm running 3.5.13.2
>
> Janek
I have repaired HAL-related problems before by completely purging and
reinstalling the hal and hal-trinity packages and their configuration
files (literally, via "sudo dpkg --purge --force-all hal-trinity
libhal-storage1 libhal1" followed by "sudo apt-get -f install"). You
might want to give this a try, as HAL tends to have rather severe problems
after a dist-upgrade in my experience.
This embarrassing situation was a strong motivator for the complete
removal of HAL in R14. ;-)
Tim
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlM7LjoACgkQLaxZSoRZrGFajwDeIKvHMrETaZW1lUAMhdeYZVn0
fKubPXJY06MNFQDgxZStp+o3PKVTRlZ+uIL5Nizr/VDflFsBjORpBQ==
=qSEm
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlM7LlMACgkQLaxZSoRZrGGf6QDgkA/VQlbsEEsMtOz5ZYGcC/zF
859G4lRyCiuMNwDfbGMAYOxdolzns8h+eCvSRdyLOskKr+t+9qWyNg==
=420V
-----END PGP SIGNATURE-----
I recently upgraded from Squeeze to Wheezy and at the sam time I upgraded Trinity. I just realized
that after this upgrade KPowerSave:
a) always indicates that the power cord is plug in, even if it's not;
b) does not show battery level
c) after going into KPowerSave settings display and selecting a power scheme on the first tabs
display brightness and CPU speed are greyed out and marked as "not supported"
Calling `acpi -b` indicates battery level correctly.
I also notcied that in KControlCenter I can't control brightness in Display settings. OTOH I can
change display broghtness by using function keys.
I suspect that I might be missing some packages or that permissions might be incorrect. Thoughts?
Janek
