Re: bizarre look of libreoffice under KDE/compiz
On Sun, 23 Oct 2011 22:02:31 +0200, Pavlos Parissis wrote:
> On 23 October 2011 12:16, Camaleón <noelamac@gmail.com> wrote:
>> Hi, please, avoid using html formatted messages, they render very badly
>> in some e-mail readers :-)
> Sorry I forgot to disable html on gmail.
This looks better, thanks.
(...)
>> Let's recap...
>>
>> - KDE
>> - Compiz
>> - Cairo-dock
>> - Discrete VGA card (Radeon HD 4290) + radeon driver
>> - Backported kernel
>>
>> I think you are putting too much spicy on the soup :-)
>
> Is it really? I don't think I am asking too much. There are plenty of
> users using all of these and I can't believe that on a modern hardware
> is too much to have all of these.
Modern hardware knows nothing about such software mixture.
I mean, if we are referring to the hardware layer, your computer can be
able to run all those applications just fine but speaking purely about
software, I fear to run just _one_ of the said components so imagine
running all of them at a time... it has to be a complete headache for
your system (KDE environment is now managed by kwin -which provides
compositing- and you are also running Compiz -which provides
compositing-, then you have added Cairo-dock -to enhance the desktop look
& feel- and all that is managed by a VGA card that is not very powerful -
mid-range- with a backported kernel.
I would considered myself lucky if my system can be started with all that.
>> I would try to disable compiz and see what happens. It could be "cairo-
>> dock" or "compiz" (or a mix of a lot of other things, the soup has many
>> ingredients...) the ones making the screen goes corrupted. If disabling
>> compiz fixes the problem (the same as happens with GNOME) I would
>> contact compiz at their forums or mailing lists.
>
> I was about to do that, but I said I want to find the solution of the
> problem rather to work around it.
Disabling components will help you to find what is causing LO (it was
just LO?) to render badly and you will be able to direct your report to
the proper project/package to they can fix it or tell you what to "tweak"
to make the error dissapear :-)
Greetings,
--
Camaleón
Reply to: