Bug 92780 - Presenter console fails to display (shows black screen in Compiz, nothing in Kwin)
Summary: Presenter console fails to display (shows black screen in Compiz, nothing in ...
Status: RESOLVED DUPLICATE of bug 91574
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.0.0.3 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-16 05:10 UTC by Roland Taylor
Modified: 2015-07-16 21:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Taylor 2015-07-16 05:10:19 UTC
This seems to be a major regression from 4.4.x. It was working in 4.4.x but now upon upgrading to 5.0 it is no longer working. I'm on Ubuntu 15.04, and using the pre-release ppa.

The only other potential cause of an issue is that I use bleeding edge intel drivers, but the presenter console was working fine with this driver on 4.4.x.

I have not yet tested with the stock intel driver.

I would also like to note that this occured on a stock Windows 7 system, but has since been fixed since the latest update.

The same problem occurs running 5.1 nightly builds.

Using gtk2 as opposed to gtk3 does not change anything.

Here is the only output from the terminal:

** (soffice:3909): CRITICAL **: GdkPixbuf* bitmapToPixbuf(SalBitmap*, SalBitmap*): assertion 'pBitmap->mnBitCount == 24' failed

** (soffice:3909): WARNING **: Invalidate all children called


** (soffice:3909): WARNING **: Invalidate all children called

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
Comment 1 Roland Taylor 2015-07-16 05:12:28 UTC
I forgot to mention - after exiting the presentation, this failed presenter console remains on screen, and there is no way out of it without killing soffice.bin.
Comment 2 tommy27 2015-07-16 12:25:05 UTC
please take a look at Bug 91574
is this a different issue?
Comment 3 Roland Taylor 2015-07-16 21:37:43 UTC
Yes, sorry for the duplicate.

*** This bug has been marked as a duplicate of bug 91574 ***