Bug 13910 - KompoZer pull down menus are blackened out
Summary: KompoZer pull down menus are blackened out
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard: MGA4TOO 5alpha2
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-14 23:12 CEST by William Kenney
Modified: 2015-01-25 10:26 CET (History)
3 users (show)

See Also:
Source RPM: oxygen-gtk
CVE:
Status comment:


Attachments

Description William Kenney 2014-08-14 23:12:04 CEST
kompoZer is an ( old ) WYSIWYG content editor.

To replicate simply open one of the pull down menues
File/Edit/View/Insert/Format/Table/Tools/Help
and the selections will be blackened out. Probably
needs to be recompiled with the new GTK or something.
This bug also occurs in M4.

Aside from this kompoZer is long since died. It has
been forked to:

http://bluegriffon.org/

I have downloaded a Bluegriffon:

bluegriffon-1.5.1-1.fc16.i686.rpm

and installed that just fine on M4. Are we too far along
with M5 to replace kompoZer with Bluegriffon? FWIW
Bluegriffon also exhibits the same blackened pull down menus.

Reproducible: 

Steps to Reproduce:
William Kenney 2014-08-14 23:13:23 CEST

Whiteboard: (none) => 5alpha2

William Kenney 2014-08-14 23:13:56 CEST

Summary: KompoZer pull down menues are blackened out => KompoZer pull down menus are blackened out

Comment 1 David Walser 2014-08-15 17:27:02 CEST
Known issue, although I was surprised I couldn't find another Mageia bug report for it.  We do have a package request for bluegriffon in Bug 3132.

It's not as simple as rebuilding, as we've done that before Mageia 4 already.

Of course, if BlueGriffon does the same thing, that doesn't help us.

CC: (none) => mageia, mageia
Assignee: bugsquad => mageia
Whiteboard: 5alpha2 => MGA4TOO 5alpha2

Comment 2 William Kenney 2014-08-15 17:38:57 CEST
Would it be easier to just scrap KompoZer and go to Bluegriffon
rather then fix KompoZer or is it just a push?
Comment 3 David Walser 2014-08-15 19:51:51 CEST
I don't know.  If they both have the same problem, it's probably the same bug with the same fix.  However, I doubt we'll be the ones fixing it unless another distro finds/makes a patch.  In that case, not many distros have bluegriffon packaged, so higher likelihood with kompozer.  If upstream fixes it, kompozer is dead upstream, so only chance there is with bluegriffon.

Anyway, if bluegriffon was easy to package we'd have already done it years ago...
Comment 4 Luc Menut 2014-10-27 19:58:21 CET
Could you try to launch kompozer and/or bluegriffon in a terminal with OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner

OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner kompozer
OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner bluegriffon

Is there the same problem, or does it work better?

CC: (none) => lmenut

Comment 5 William Kenney 2014-10-27 20:10:22 CET
(In reply to Luc Menut from comment #4)

> OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner kompozer

Wow! How bout that. That worked perfectly.
I'll try bluegriffon later but I bet it works there too.
Comment 6 Luc Menut 2014-10-28 23:46:00 CET
This should be fixed in Cauldron with oxygen-gtk-1.4.6-1.mga5 (without needing to use OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner).

I plan to update oxygen-gtk for mga4 in coming weeks.

Status: NEW => RESOLVED
Hardware: i586 => All
Resolution: (none) => FIXED
Source RPM: kompozer-0.8-0.b3.5.mga4.i586.rpm => oxygen-gtk

Comment 7 William Kenney 2014-10-29 00:16:31 CET
(In reply to Luc Menut from comment #6)

> This should be fixed in Cauldron with oxygen-gtk-1.4.6-1.mga5 (without
> needing to use OXYGEN_APPLICATION_NAME_OVERRIDE=xulrunner).
> 
> I plan to update oxygen-gtk for mga4 in coming weeks.

Many thanks for your help.
Comment 8 Luc Menut 2015-01-25 10:26:24 CET
For the record, an update (oxygen-gtk-1.4.6-2.mga4) for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0004.html

Note You need to log in before you can comment on or make changes to this bug.