Summary: | LibreOffice fresh Impress make blank screen when start SLIDESHOW | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Radomír Palovský <r.palovsky> |
Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | xiscofauli |
Priority: | medium | ||
Version: | 6.2.0.0.beta1+ | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 102495, 103610 |
Description
Radomír Palovský
2019-02-26 10:48:45 UTC
Problem is fully solved when reinstalation from libreoffice-fresh to libreoffice-still was made. *** Bug 123718 has been marked as a duplicate of this bug. *** I can't reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 8aa579830b20072af8d6e149d6b279362fe98b91 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided Ok, this is a KDE5. i can reproduce it in Version: 6.3.0.0.alpha0+ Build ID: 17b25fd3df237a64d6a28fbc57b869e080963193 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-03-13_20:42:25 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Reproduced back to Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: kde5; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded in Version: 6.2.0.0.alpha1 Build ID: ff46ad24d1d3cbcea45895520483ed1fd4ff488b CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: kde5; Locale: en-US (en_US.UTF-8); Calc: threaded it crashes when launching the slideshow. thus, this is not a KDE5 regression Is this bug 119718? (In reply to Katarina Behrens (CIB) from comment #6) > Is this bug 119718? Yep, it's. I knew a similar bug was already reported but I couldn't find it before... *** This bug has been marked as a duplicate of bug 119718 *** |