trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: January 2012

Re: [trinity-users] KDE 3.5.13 up ! and Kaffeine OSD

From: Darrell Anderson <humanreadable@...>
Date: Tue, 17 Jan 2012 10:19:27 -0800 (PST)
> Just succeeded in downloading and installing Kaffeine
> 3.5.13 (and some other parts) on a brand new Linux
> Mint 12 (Lisa) OS install. So thank you so much for the
> work, it's great.
> Only worry so far is the colours of the OSD.
> I saw there were some posts around here http://permalink.gmane.org/gmane.comp.desktop.trinity.devel/1975
> 
> about that issue, but no changes in xine configuration has
> any effect on the problem.
> So I made some more investigations.
> 
> I have a 3.5.12 version rolling on the same machine on a
> Debian Squeeze third boot disk, 
> so I simply and roughly compare and replace some pieces to
> see what was the origin of this presumably bug.
> Finally, replacing only the libxinepart.so in
> /opt/trinity/lib/trinity of Lisa by the 3.5.12 version 
> I have in /opt/trinity/lib/kde3 of Squeeze (name of
> directory seems to have change between these two versions)
> changes back the OSD to its initial colours.
> 
> If it can help further more :
> Squeeze version date     : sam. 14 août
> 2010 09:29:58
> Lisa version date     : sam. 15 oct. 2011
> 02:35:36
>  
> So I presume this library has something related to that
> issue.
> 
> I'm not a developer, but if I can help comparing source or
> finding more
> information, just let me know. I can easily compare
> versions as they are
> both rolling on the same machine ;).
> 
> Cheers and thanks so much again for your fantastic work at
> TDE.

Bug report 727 was filed against the OSD colors. Reading the report discussion reveals the colors are estabalished in xine-part/kxinewidget.h, which is from where libxinepart.so gets built. We haven't investigated further. We still need to determine whether Qt3 is playing a role because the code in Kaffeine 3.5.13 is identical to Kaffeine 0.8.8, which I have installed in KDE 3.5.10 on the same hardware and do not experience the problem.

With your sleuthing we now can narrow the focus to a specific shared library and that helps!

Do you have access to the Bugzilla to add that information? If not then let me know and I'll add that tidbit of information.

Darrell