Red Hat Bugzilla – Bug 232159
gtk-qt-engine: squirrely disappearing icons, menu items in openoffice
Last modified: 2008-03-13 03:48:14 EDT
Description of problem:
icons in openoffice disappear and then re-appear on mouseover:
when ooo apps are first launched, all looks normal. Moving the mouse over any
icon or menu causes all of the icons and menu items to disappear, leaving only
the grey frames. But they appear when the cursor is over them and work normally.
This occurs for the toolbar icons as well as all menu items, including the text
in the menus.
Version-Release number of selected component (if applicable):
launch an ooo app and try to use it.
Steps to Reproduce:
1. launch ooo app
2. mouse over any toolbar icon or use the menus
icons and menu items disappear and appear only when the cursor is over them
things should remain in place and not play silly games
I am assuming this is related to previous similar FC4 bugs I've seen with
gtk-qt-engine, if not, my apologies.
Yep, see also bug #163110 and
Hrm, I'm unable to reproduce (it WORKSFORME regardless of how I launch ooo).
Could you try toggling your gtk-qt-engine settings via
KControl -> Appearance&Themes -> GTK Styles and Fonts
and try setting "Gtk Styles" to various things like Clearlooks, Bluecurve, Qt
OK I started ooo just now the problem had magically fixed itself about 90% of
the way (no yum updates or any changes on my part since OP). There still was
some disappearing of _certain_ menu items when the mouse was over them this
time. But all the toolbar icons were OK.
Then went into the GTK Styles Controller and saw I had "Use my KDE Style..."
selected. My KDE style is "Light Style, 3rd revision"
But on selecting anyone one of the other styles in the drop-down, oowriter works
100%, no problems.
So I guess this is 99% solved, and workaround is to use Bluecurve or another
thanks for looking into it!
No the Problem ist not solved and makes me crazy since some months :-(
If you use ooo2.1/oo2.2 from the original-packages there is no problem, but they
will "kill" package-cleanup --problems from yum-utils.
the problem is away if you start openoffice directly, and then you also can open
documents with double-click in konqueror - but if the apllication not is running
and you do this the icons are away
It is not a solve to use another style, because as i choosed the keramik-theme i
would have all applicatoons in this style and gnome is no alternative for
I dont understand that the problem is only here if u use the feodra-package of
openoffice - what happens in this build?
> I dont understand that the problem is only here if u use the feodra-package of
> openoffice - what happens in this build?
has something to do with gnome-theming not present in standard/upstream ooo
builds. Past that, dunno.
As I said, I'm personally unable to reproduce (see comment #2), still. I use
kde plastik theme, crystalsvg icons.
it is also with plastik theme
i have tried it this moment with the result that all my personally
keramik-settings are destroyed and openoffice is stupid as before.
terrible enough that there is 2.0.x in a moment where 2.2 is out, the original
runs much better but the better way is the package-manager
This bug is bitting in rawhide
Keramik theme & style.
(In reply to comment #7)
> This bug is bitting in rawhide
> Keramik theme & style.
Hmm what i dont understand is that the only application with the bug is
openoffice, and only the openoffice from fedroa and not the original.
If there is a bug in keramik why thunderbird and firefox who also
gtk-apllications and other gnome-applications like gthumb does not have any
> i dont understand is that the only application with the bug is
From what I've gathered from the gtk-qt-engine maintainer: openoffice (re)draws
it's gtk widgets in a unique (arguabley non-standard and/or buggy) way.
Upstream ooo doesn't use/include gtk theming.
To narrow it down if keramik is to blame, try something else, like plastik. Do
the problems still occur?
On my machine yes it is also with plastik
See one of my last posts:
>it is also with plastik theme
>i have tried it this moment with the result that all my personally
>keramik-settings are destroyed and openoffice is stupid as before.
My problem is that with the original-ooo "check-packages --problems" is broken,
in other way i would not use the fedora-one with the display bug.
but i am sure that not ooo himself has the bug, because it is only in the
fedora-version. ooo 2.1 and 2.2 are making no troubles in this way
Yep still there with various styles & themes etc, not found one which works.
Same with Fedora 7 and OpenOffice 2.2
That does not make happy and i think it would be better to remove the changes
for gnome on fc7 instead users must break the package-manager under kde
OpenOffice is, in practice, a critical application for many who use Fedora 7. I
would suggest that a bug that makes this application essentially unusable in a
normal setup (and without a lot of fiddling) should be treated as much more
severe than just "medium." Fix this; if not, it's going to cause people to
switch to different distributions.
gtk-qt-engine-0.70-5.20070811svn.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
On Rawhide (VMware setup) this seems to work now
[root@fedora-test ~]# rpm -qa | grep gtk-qt
[root@fedora-test ~]# rpm -qa | grep openoffice
My Fedora 7 machines i wont test anymore because the app-links and
file-open-settings are not compatible with the packages from de.openoffice.org
and after creating a own repo with the original-packages updates in office,
private lan and on machines of friends work perfect.
gtk-qt-engine-0.70-5.20070811svn.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
OpenOffice seems fundamentally usable; yet, there are some broken interactions
in there. I've opened bug #266621 to describe the problems I'm currently seeing
in more detail.
I'm still seeing this problem, *sometimes*. It seems only to happen when I
specify a file on the command line (i.e., "openoffice.org $filename"), not when
I start the program and then open a file. And even then, only with some files ...
I've actually currently got a .ppt file that reliably reproduces this problem
every time -- icons go screwy when I open it from the command line, but if I
open it from within OO.o things are fine. It's sort of an internal document so
I'd rather not post it in this bug report, but I can probably send it privately
Created attachment 291371 [details]
PowerPoint slides that reproduce the icon problem
This is still happening with gtk-qt-engine-0.8-1.fc8, especially when I open
files on the command line -- still, *sometimes*. At the moment, I can reproduce
it every time opening the attached document on the command line (i.e.,
"openoffice.org iva2007-slides.ppt"), but ONLY if the document is on my vfat
Windows XP partition. If I copy it to my home directory, nothing bad happens.
I'll try making an istanbul movie of this ...
Created attachment 291373 [details]
Movie of the icon problem manifesting
Okay, I wasn't hallucinating -- this weird thing does happen with this file
*only* when I open it on the command line from my fat32 partition. Check out
the attached video. Argh!
NB: Upstream is aware of this; activity seems to be at
gtk-qt-engine-0.8-4.fc8 has been submitted as an update for Fedora 8
gtk-qt-engine-0.8-4.fc7 has been submitted as an update for Fedora 7
gtk-qt-engine-0.8-4.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gtk-qt-engine'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-2165
gtk-qt-engine-0.8-4.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
gtk-qt-engine-0.8-4.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.