Message: previous - next
Month: January 2012

Re: [trinity-users] K Menu - kicker crash

From: Mike Howard <mike@...>
Date: Sat, 14 Jan 2012 22:17:11 +0000
On 14/01/2012 22:09, Mike Howard wrote:
> On 14/01/2012 21:41, Timothy Pearson wrote:
>>> On Saturday 14 January 2012 10:22:22 am Dan Youngquist wrote:
>>>> On 01/14/2012 10:38 AM, Calvin Morrison wrote:
>>>>> This bug is fixed in git.  It was a libart issue. Will be there in 
>>>>> R14
>>>> I have the same problem on 2 different machines -- the only 2 installs
>>>> of
>>>> 3.5.13 I've done so far -- and it's been reported on the list at least
>>>> twice since then.  So I think it must be a common problem that lots of
>>>> folks run into.  I haven't tried the patch yet, but am about to do so.
>>>> But most who get to the website, install Trinity, and have this 
>>>> problem
>>>> won't know there's a patch -- they'll just see a great big bug that's
>>>> still
>>>> there, and uninstall Trinity and never try it again.  So I think 
>>>> it's a
>>>> really bad idea to leave it unfixed until R14.
>>> The OP was building from source on a Wheezy system, this IS 
>>> different than
>>> a user
>>> visiting the TDE website&  installing the binaries on a Wheezy system.
>>> AFAIK, TDE3.5.13 is compiled on a Squeeze box, for the Debian stuff, 
>>> and I
>>> would
>>> not expect them to necessarily work 100% on Wheezy.  The install
>>> instructions are
>>> for Lenny&  Squeeze.
>>> I have tested TDE3..5..13&  Wheezy in a Vbox instance and would not 
>>> want
>>> to use on
>>> my production boxes.
>>> Caveat,  I don't think running a Wheezy guest on a Squeeze host is a 
>>> valid
>>> test
>>> though. To many kernel&  Xorg cahnges, to name a few,  some stuff just
>>> won't
>>> work.
>> My experience with Wheezy in a full VM has been terrible.  Too much
>> instability in core system libs--I strongly recommend that TDE users DO
>> NOT UPGRADE TO WHEEZY unless they are prepared to lose access to TDE 
>> (and
>> other software packages) until Wheezy is marked as stable.
> I'm a little confused now so please bear with me, or just ignore me as 
> you choose :)
> I'm not at all sure where libart comes into my equation. I have 
> libart-2.0-2 & libart-2.0-dev installed on my system, as debs, but  
> not libart-lgpl. Nor does libart-lgpl appear in the stable sources, 
> except as an almost empty sub-folder of konstruct/libs or in apt on 
> either Squeeze or Wheezy.
Or does libart-lgpl produce libart-2.0-2 & libart-2.0-dev? Figured that 
once Tim's link actually opened. Sorry.

Michael Howard        mike at dewberryfields dot co dot uk