Bug 88164 - Text in menus not rendered by LibreOffice
Summary: Text in menus not rendered by LibreOffice
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-07 15:45 UTC by Oliver Neukum
Modified: 2015-10-22 04:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
kernel log (135.41 KB, text/plain)
2015-01-07 15:45 UTC, Oliver Neukum
no flags Details
X log (34.13 KB, text/plain)
2015-01-07 15:55 UTC, Oliver Neukum
no flags Details

Description Oliver Neukum 2015-01-07 15:45:18 UTC
Created attachment 111922 [details]
kernel log

I am seeing the text in menus not rendered at all in LibreOffice and only in LibreOffice. Text not in menus works. If I take a screenshot the menus are in the screenshot as they should be.
This is a regression between kernel 3.17.0 and 3.18
Comment 1 Ilia Mirkin 2015-01-07 15:51:36 UTC
I see that you're booting with nouveau.noaccel=1 -- this disables all acceleration. However xf86-video-nouveau should still get used in that case; perhaps there's an issue in how the noaccel fallbacks are set up. Can you pastebin the xorg log?

As an aside, why are you disabling acceleration? What happens if you remove noaccel=1?
Comment 2 Oliver Neukum 2015-01-07 15:53:46 UTC
If I boot without noaccel=1 the system locks up within seconds after logging in.
Comment 3 Oliver Neukum 2015-01-07 15:55:42 UTC
Created attachment 111924 [details]
X log

The log is taken after booting and logging in.
Comment 4 Ilia Mirkin 2015-01-07 17:01:39 UTC
I just noticed that you said that this is a regression from 3.17 to 3.18 -- that is _very_ surprising, as acceleration is not being used and it's all just software rendering. Perhaps there's more going on here... Could you try doing a bisect? You can limit it to drivers/gpu/drm to speed things up.
Comment 5 Oliver Neukum 2015-01-08 09:12:44 UTC
(In reply to Ilia Mirkin from comment #4)
> I just noticed that you said that this is a regression from 3.17 to 3.18 --
> that is _very_ surprising, as acceleration is not being used and it's all
> just software rendering. Perhaps there's more going on here... Could you try
> doing a bisect? You can limit it to drivers/gpu/drm to speed things up.

I just rechecked with vanilla v3.17. It does work. I am starting a bisection.
Comment 6 Oliver Neukum 2015-01-08 13:09:56 UTC
(In reply to Oliver Neukum from comment #5)
> (In reply to Ilia Mirkin from comment #4)
> > I just noticed that you said that this is a regression from 3.17 to 3.18 --
> > that is _very_ surprising, as acceleration is not being used and it's all
> > just software rendering. Perhaps there's more going on here... Could you try
> > doing a bisect? You can limit it to drivers/gpu/drm to speed things up.
> 
> I just rechecked with vanilla v3.17. It does work. I am starting a bisection.

I need to retract this. The bug is triggered by the lack of desktop effects. If I activate desktop effects in KDE it starts working again.
Comment 7 Ilia Mirkin 2015-10-22 04:19:47 UTC
Sounds like a bug in something unrelated to nouveau... with nouveau.noaccel=1 neither the ddx nor user programs are using nvidia gpu hw for acceleration.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.