tde-users

users@trinitydesktop.org

4290 discussions

OS13.1: nothing provides trinity-tdenetwork-*, jasper, maybe others?
by Jagged O'Neill 01 Jun '14

01 Jun '14

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

2 4

libr-dev, gettext-kde
by Michael Howard 01 Jun '14

01 Jun '14

Hi List, Michele, I found on a google search a question asked by Michele about building from source using tde_packaging where libr-dev & gettext-kde wee unmet dependencies (http://trinity-devel.pearsoncomputing.net/?0::10775:get:1). I did not find an answer to the quetion though. As I'm currently facing the same problem, does anybody know the answer? Michele, did you get an answer? Cheers, Mike. --

3 14

Re: [trinity-users] libr-dev, gettext-kde
by Timothy Pearson 01 Jun '14

01 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224 > > On 31/05/2014 17:20, Slávek Banko wrote: >> On Saturday 31 of May 2014 17:42:58 Michael Howard wrote: >>> On 31/05/2014 16:30, Michele Calgaro wrote: >>>>>> As I'm currently facing the same problem, does anybody know the >>>>>> answer? >>>>>> Michele, did you get an answer? >>>>> The simplest option is to add the apt source with build dependencies. >>>>> You have three options for this: >>>>> 1) nightly-build-deps - but contain multiple packages that are not >>>>> needed: deb >>>>> http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-build >>>>> s/debian _distribution_ main 2) deps-r14 (on build-farm) - contain >>>>> only >>>>> the necessary packages: deb >>>>> http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/deps-r14/ubuntu >>>>> _distribution_ main 3) deps-r14 (alternative) - same as 2), wider >>>>> bandwidth, contain packages also for mips deb >>>>> http://mirror.xcer.cz/trinity-sb _distribution_ deps-r14 >>>> Hi Michael, >>>> Slavek already gave you good advice. >>>> Another way is to build libr and gettext-kde from sources, as I do. >>>> You >>>> can use this sources, from the same Slavek's repo. deb-src >>>> http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14 Just replace >>>> jessie with the distro you are using. >>>> If you want, you can first browse it at >>>> http://mirror.xcer.cz/trinity-sb/dists/ >>>> >>>> Just for your understanding, to build TDE in Debian and Ubuntu you >>>> need >>>> some extra packages which are not part of the main TDE repo. libr and >>>> gettext-kde are two of them. You can find the others at the address >>>> indicated. Also when building, remember to bump up the version number >>>> of >>>> all packages (**EXCEPT** the deps-r14 ones) to 4:14.0.0 to avoid >>>> broken >>>> dependecies). >>> Sorry, forgot to clarify. Do you mean that _all_ packages, e.g. Amarok, >>> should be versioned at 4:14.0.0 ? >>> >>> Cheers, >>> Mike. >> If I understand correctly, you want to build amarok package only, not >> the >> complete set of TDE packages. In this case, you just deal with a version >> of >> the amarok package. >> > Actually, I'm building the complete set. For both amd64 and arm*. > > I have built, and use R14 from source from a year or more ago, using > source from GIT but not paying any attention to packaging. Both for > amd64 & armel. > > I am currently going through the process of building from GIT source > again, this time packaging. Firstly for amd64 and once complete, for > armv7hf (I have anumber of ARM devices/requirements). > > I use Amarok as an example as that is my media player of choice, and I > use it to play audio, from ARM devices, over the network. > > Amarok armv7hf from nightly builds does not work and I've noticed that > from building (amd64) using tde_packaging (from git) that the debian > build does not appear to use cmake but instead uses autotools?. Very > odd. Is that correct? > > Any info appreciated. > > Cheers, > Mike. How does Amarok fail on the armv7hf platform? Tim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iFYEARELAAYFAlOKNuIACgkQLaxZSoRZrGFwOQDfcaSTfcWr18acUJFlVXntCotY vf+ptab5Z6UPUQDfdkRr9D9PGSTheRPtvxUzbw6ZRj3QUeul0V5+3A== =PBp4 -----END PGP SIGNATURE-----

2 1

Thinkpad X41 key 234 is interpreted suddenly as button-1 (mouse)
by Uwe Brauer 31 May '14

31 May '14

Hi I am running Kubuntu 10.04 with trinity 3.5.13, the keys which are sitting above the left and right arrow were recognized by xev as 234 and 233 and I mapped them via xmodmap. keycode 234 = F30 keycode 233 = F31 However out of a sudden, the right key 234, is now interpreted as a mouse button, button-1, even by xev. I restarted the Xserver rebooted the machine, no change. I am desperate. Anybody could help me please. thanks Uwe Brauer

2 2

Most simple way to upgrade Trinity
by Aleksey Midenkov 27 May '14

27 May '14

aptitude safe-upgrade '?version(4:3.5.13)' if 4:3.5.13 is currently installed version.

8 24

upgrade testing
by Greg Madden 25 May '14

25 May '14

Thought I would start a thread to gather info on what method(s) work to upgrade from 3.5.13.2 > R14. I did this from konsole in an x session. System: Debian Squeeze LTS, AMD64. I changed my sources list to the nightlies. Ran "apt-get update". There is one package to be removed, many new packages to be installed and fewer to be upgraded. 'apt-get upgrade' will not install the new packages, they are held back. I used 'aptitude upgrade' and the resolver figured out all the depends, new installs, upgrades and removal. Almost perfect, better than any previous upgrades. A couple of things I noticed is my desktop wallpaper was set at the default, I like 'alien nights' :-) Ending my current session via the logout dialog drops me to a cli, I have to 'restart tdm-trinity'. I did test this on a vm (cloned) I have for legacy support purposes. Real hardware may be different. -- Peace, Greg

2 2

Making Kile aware of new file extensions
by Jan Stolarek 21 May '14

21 May '14

I'm working in Kile on a LaTeX file with *.mng extensions. Due to the strange file extension Kile does not recognize it as source LaTeX file and almost all editing capabilities provided by Kile are gone. For example it does not recognize document structure and the autocompletion of references and citations is gone. How can I make Kile aware that this is in fact a LaTeX file? Janek

5 6

Re: [trinity-users] Most simple way to upgrade Trinity
by Michele Calgaro 21 May '14

21 May '14

> for Debian based distros, I would normally recommend a clean install after a proper backup is done. That's actually a very good way: no risk loosing anything and at the same time preserve a clean environment. Of course it takes some additional time. Another safe way is to run aptitude, upgrade the list of packages (press U) and then try to do small upgrades step by step, checking each time that there are no conflicts. In case there are some, explore the suggested possible solutions and choose the one that represent the best fit for your needs. As for TDE 3.5.13.2 --> TDE 14.0.0 upgrade, a lot of packages have been renamed, in particular kdelibs4c2a has become tdelibs14. That means that the upgrade will have to be done as a single step. Expect several packages to be removed and do not forget to manually select the new renamed packages to be installed if needed (ex: kdebase is now called tdebase). Overall, I would suggest a backup and clean installed, as Michael already said. Cheers Michele

1 0

TDE on SID
by Thierry de Coulon 21 May '14

21 May '14

Hello all, This is NOT a complain, just a question. While I'm working with a perfectly working Wheezy + TDE, I've had the curiosity to install "Siduction", a rolling distribution based on SID. I've tried to install Trinity Desktop from the nightly builds (using jessie as target distribution). desktop-base-trinity installed correctly, but kde-trinity depends tde-trinity taht won't be installed. My question: does this mean that Trinity and SID are incompatible (which I would understand, given that it's impossible - and makes little sense -to provide compatible packages) or is it one of these situations where packages are just being (re)created for Jessie and I should try it later. ANd if so how can I know when such a situation occurs? Siduction is not interesting if I can't get a sensible desktop... Regards, Thierry

19 72

Starting yakuake with specified colours on log in by a user
by Ken Heard 12 May '14

12 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is it possible to have yakuake start whenever a user logs on so that the user does not have to start it from a terminal emulator when s/he wants to use it? The colours I want it to use are green on black, but running in a terminal emulator command "yakuake --bg black --fg green" as specified in the manual do not produce the desired result. Yakuake will open but with the default colours black on white. I am presently using Debian Squeeze with KDE-Trinity, and package yakuake-trinity. Regards, Ken Heard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAlNuf8AACgkQlNlJzOkJmTcRmACeJus7LXxZJCX/rUPd9hl+byJY BFoAnA7qhZAdbDPWsgQAUNQpnlQWgjWo =BDQM -----END PGP SIGNATURE-----

3 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users