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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
I wanted to let you know that the QuickBuild system has been restored to
full functionality. All builds are now proceeding normally.
Thank you again for your generosity in helping replace the failed chiller;
this would not have been possible without your support!
Timothy Pearson
Trinity Desktop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlM4qwcACgkQLaxZSoRZrGEjaADfST3TIU4iesNPpqd/JxkgccZS
6x+evbEuoCjFUQDeMY6hoYufTxMRqmHbNiXTk0V2U+6Aiw+IvbjIhQ==
=QEpJ
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
When TDE crashes and Dr. Konqi appears...
...please click "Report Crash" instead of "Close". TDE now has a powerful
automated crash reporting system that will let you submit a crash report
with as little as three mouse clicks--no personal information, logins, or
version descriptions are required. Of course we would appreciate a
problem description and possibly a contact Email address, but if you don't
have time or just don't want to give that information out you can still
submit the crash report for analysis and repair.
Thank you for using TDE!
Timothy Pearson
Trinity Desktop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlM4nasACgkQLaxZSoRZrGFwHgDgkHL4zhQbDw2+PJ5FnToY/r8q
yfG9xi41P61SfwDfWLSU0Njc2IrGxoauyNB9HnoCuUXYveHipU/dfg==
=iioR
-----END PGP SIGNATURE-----
Hi Guys,
I think I may have stumbled across a bug in the version of Trinity that
I use. PCLinuxOS from Alexandre's iso.
If I click on "Home" Konqueror opens, if I then open a second new window
by right clicking and choosing "Open in a new Window" on a directory.
I now have two open windows.
If I then create a new directory in the first window and open that. I
now have three windows.
If I now try to drag and drop a file from the second window into the new
3rd window the files end up in the first window. Not in the new 3rd
directory.
The same happens if I try to create a directory or a file in the new
directory. It appears in the first window.
Files do drag and drop correctly from the first window into any
directory in that window.
It gets very confusing items that you think you have put somewhere
appearing somewhere else.
--
Best Regards:
Baron.
Hi all,
in light of the recent problems on the build-farm, I used the fact that
ever since work on v3.5.13-sru I have the automated preparation of source
packages and at the same time I have a private builder where I am doing
the test building, and where I have available all supported Debian and
Ubuntu distributions (for example, see my test for building on Ubuntu
Trusty). I optimize my production line for building packages, so now I
have ready alternative APT source containing packages for all supported
Debian and Ubuntu distributions.
The same packages will be in the future uploaded to my PPA on build-farm,
where they will serve as maintanance releases for R14. Similarly, as was
my PPA for v3.5.13-sru branch. Therefore, this apt source I call 'R14
preliminary stable-builds'. In order that the packages were readily
available, they are synced to my primary mirror.
What to do if you want to use it?
1) Add the source to sources.list:
deb http://mirror.xcer.cz/trinity-sb *distribution-name* deps-r14 main-r14
2) From some public GPG keyserver download my key and import it into APT:
sudo apt-key adv --keyserver pks.gpg.cz --recv-keys ED1F4884
3) Update the packages in such a way as you used to do it :)
I hope it will be helpful.
--
Slavek
