[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#824105: libreoffice-kde: Toolbars corrupt with plasma unless OOO_FORCE_DESKTOP=kde is used



Solved.

It turns out that xserver-xorg-video-intel had become un-installed on my 
machine. I do not know how this happened, although apt-cache show says:

"""
 The use of this driver is discouraged if your hw is new enough (ca.
 2007 and newer). You can try uninstalling this driver and let the
 server use it's [sic] builtin modesetting driver instead.
"""

I recently reinstalled to go to multiarch amd64 to try and squeeze some extra 
performance for video editing; perhaps the intel driver wasn't installed by 
default. My graphics controller is "VGA compatible controller: Intel 
Corporation Core Processor Integrated Graphics Controller (rev 02)" and 
installing xserver-xorg-video-intel causes libreoffice to work well again with 
correctly rendered toolbars.

I don't know why only libreoffice was compromised, but this bug can be closed as 
bogus/not belonging to this package. Thanks for your assistance, and for 
showing me interesting bits of the source code.

Nick/.


On Thursday 12 May 2016 13:56:47 Rene Engelhard wrote:
> Hi,
> 
> On Thu, May 12, 2016 at 11:16:16AM +0100, Nick Bailey wrote:
> > Setting OOO_FORCE_DESKTOP=kde resolves this, so this is a minor bug.
> > However, I would have thought libreoffice-kde should make sure this
> > happens anyway? (unless plasma is somehow miss-representing its
> > identity?)
> 
> http://opengrok.libreoffice.org/xref/core/vcl/unx/generic/desktopdetect/desk
> topdetector.cxx#288
> 
> That setting it to kde - which is KDE3(!) - helps here is interesting :)
> 
> See
> http://opengrok.libreoffice.org/xref/core/vcl/unx/generic/desktopdetect/des
> ktopdetector.cxx#234 ff.
> 
> What is your KDE_FULL_SESSION and KDE_SESSION_VERSION environment variables
> inside a Plasma session?
> 
> > The bug is reported against the latest version because I pushed the
> > machine
> > to sid temporarily to make sure it hadn't been addressed. In fact, it has
> > been affecting my machine for while (at least several months).
> 
> And the version you used before was? We should then mark it as found in
> that version, not the current one (which is what you did)
> 
> Regards,
> 
> Rene


Reply to: