| Summary: | Libreoffice Edit->Change menu display is faulty under KDE4 with libreoffice-kde installed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Juergen Harms <juergen.harms> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | ennael1, marja11, yochenhsieh |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | Errata | ||
| Source RPM: | libreoffice-kde | CVE: | |
| Status comment: | |||
|
Description
Juergen Harms
2011-05-07 21:06:41 CEST
I can reproduce this bug, with libreoffice-kde installed _and_ with the KDE widget style set to IaOra-kde. Setting the KDE widget style to Oxygen or Plastique makes the check marks appear correctly. FWIW, I think libreoffice-kde is more trouble than gain, with it: - there's no visual feed back when hovering over a button on the toolbars in LO - anomalies such as that check mark bug (in this report) appear oxygen-gtk gives a much more Oxygen-ised look to LO, but without libreoffice-kde you lose the KDE file chooser in LO, i.e. without it LO uses its own file picker/chooser dialogue/widget. (IMHO, libreoffice-kde shouldn't be shipped, or if shipped should be dubbed with "experimental" or something like that in the summary). CC:
(none) =>
ennael1 P.S. if my assessment about the cause of the bug is wrong, please revert the the report summary changes I did. Summary:
Libreoffice Edit->Change menu display is faulty =>
Libreoffice Edit->Change menu display is faulty under KDE4 with libreoffice-kde installed Your modification to the report summary is OK. I had not tried with other KDE styles (in fact I normally use Oxygen - but so far kept what comes out of the box to economize time on KDE setup while testing). Changing the style to Oxygen is a good workaround. Suggestions if the bug persists until the official becomes released: - ship KDE with Oxygen installed by default (hopefully Oxygen does not introduce other problems - I will use it as off now and see) - and/or put a note with the workaround into the release notes (release errors) That might justify lowering the severity to normal Or libreoffice-kde shouldn't be installed by default, then only caveat is losing the kde file picker integration, but given that one usually spends more on working/editing a document than saving it, I think that's a good trade off. That is a fair alternative. The L.O file picker is intuitive enough not to shock somebody who expects "KDE behaviour". Just testing how L.O works without libreoffice-KDE, I realised that the L.O user interface has quite some other glitches that disappear when that module is un-installed. Assuming that L.O will fix this problem some time: how is the way back? - or should there be no way back since the KDE interface yet adds heaviness to something that is already overweight? With all due respect to L.O. upstream devs who worked on the -kde integration, they got the file picker integration right, but the widget style "Oxygen"isation was bad from the word go, IMHO. OTOH, upstream KDE devs who created oxygen-gtk got all the theme'ing right in the oxygen-gtk engine... I think L.O. and oxygen-gtk devs should communicate, maybe upstream L.O. can drop the widget styling from libreoffice-kde and keep only the KDE file picker integration, and if users was Oxygen looks under KDE they can use oxygen-gtk (which is mature enough now that most of the major distros are planning on shipping it by default). libreoffice-kde also caused other problems. Please see bug 815: Some chinese characters in the ui displayed as unreadable squares. CC:
(none) =>
yochenhsieh Added to the Errata http://www.mageia.org/wiki/doku.php?id=mageia1:errata#libreoffice-kde_issues .
Manuel Hiebel
2011-11-27 21:20:01 CET
Whiteboard:
(none) =>
Errata what about this on latest cauldron ? with LO 3.5 (In reply to comment #10) > what about this on latest cauldron ? with LO 3.5 @ Juergen Can you reply please, is this bug still there? (I don't have time to read what this bug is about, nor to try to reproduce it) Whiteboard:
Errata =>
Errata NEEDINFO Looks OK now, I think the bug can be closed (In reply to comment #12) > Looks OK now, I think the bug can be closed Ok great, Thanks Status:
NEW =>
RESOLVED |