tde-users June 2014

users@trinitydesktop.org

26 participants
25 discussions

PCLinuxOS non-official TDE remaster, version April 30, 2014 is available on trinitydesktop.org
by Alexandre 02 Jun '14

02 Jun '14

Hi, My remaster is now available on trinitydesktop.org, for those who didn't wanted to download it from MEGA or FileFactory. Here it is: http://trinitydesktop.org/wiki/bin/view/Documentation/LiveCDs Pay attention to download the April, 30, 2014 version, or else you might download an older release! If you need to see my release announcement, check it in the first post of May, in this mailing list. Have a great day! -Alexandre

3 2

TDM/kdm is running and lets me log in, but then I only get an xterm entitled "Failsafe"
by Jagged O'Neill 01 Jun '14

01 Jun '14

High again, that was a short trip into paradise... After playing around a bit in TDE, and additionally installing some other handy software (xmms, geeqie, povray, and some others), I just wanted to start copying some files from the old to the new box. But I had chosen a default disk partitioning at install-time, and my /home was only 25GB, which I then wanted to resize. Not knowing what it is all about (first-timer), I followed the recommen- dation to do the resizing when the FS is not mounted, so I logged out, set off `umount /home`, which failed, because some trinity processes did not exit and held files open. Such things happens even with the best software around, so I didn't find it suspicious enough to jot down the files and processes (and I'm still not sure whether they are (one of) the reason(s) for what has happened then. I resized the volume for the /home FS, which was done in a second, rebooted, logged on in TDM as before, but was presented only with one single xterm. No window manager, no kicker, nothing from the previous session... nothing at all... Meanwhile I found my way to the freenode#trinity-desktop channel, where SlavekB tried to help me out with this already. No error output in .xsession-errors; I ran /opt/trinity/bin/kdm manually, redirecting it's stdout and stderr to some files... no output... sure, it writes to a "custom file", namely /var/log/kdm.log, which was already beyond 100MB when I checked. This is, however, full of some lines that say (II) AIGLX: Suspending AIGLX clients for VT switch which happens far too often, but either before or after the TDE session doesn't come up. I just moved all the old log out of my way, to see what it is actually printing when things go wrong. The startup merely copied the X servers log, and it was 68 lines long when the SAK screen appeared, (fortunately) only one of which was such an (II) line as mentioned. After logging in, the log file grew by only two lines, the following ones: QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QDialog) Negative sizes (-1,-1) are not possible what's that? I can't imagine that these lines are a description of the reason for the malfunction. Even before I asked for help on freenode, I tried some possibly curative actions on my own. I moved ~/.trinity to ~/.trinity.old, in the hope there was just something wrong with my config... I also moved other files out of the way of a new session, of which I thought they might have to do with the desktop environment, as there are: ~/.dbus ~/.kderc ~/.qt ~/.xcompmgrrc In the older kdm.log I also found the following message: kdm_config [935] info: Cannot open master configuration file /opt/trinity/share/config/kdm/kdmdistrc That file does indeed not exist, and after I looked into that dir, and read the README file, I used /opt/trinity/bin/genkdmconf --no-old to create a new config, but it was actually the same as the old one, except it had SAK enabled, which SlavekB suggested to deactivate, to see if that may be the reason... there were/are no other trinity processes running before the login and after the failure to ignite the session, just kdm is happily running with nothing to do, and some SAK processes if enabled... Any further suggestions? Thanks in advance, best regards, Jagged -- valgrind python -c 'for i in range(1,1): print(i)' 2>&1 | grep error

2 1

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users June 2014