Bug 268457 - oxygen-gtk: No menu bar with emacs
Summary: oxygen-gtk: No menu bar with emacs
Status: CLOSED DUPLICATE of bug 263182
Alias: None
Product: Oxygen
Classification: Plasma
Component: gtk2-engine (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 14:12 UTC by Christian L
Modified: 2011-07-29 23:29 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
emacs menu without menu bar (87.11 KB, image/jpeg)
2011-03-14 14:12 UTC, Christian L
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian L 2011-03-14 14:12:53 UTC
Created attachment 57968 [details]
emacs menu without menu bar

Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

No menu bar is shown in emacs menus. The menu is appearing, but there's no contrast drawn for the menu bar (see attached filed)

This problem does only appear with oxygen-gtk. The pose no problems with other gtk style. 

I'm running x64 linux with an actual built of emacs 23.2. 

Reproducible: Always
Comment 1 Ruslan Kabatsayev 2011-03-14 14:36:16 UTC
Most likely duplicate of bug 263182
Comment 2 Christian L 2011-03-14 17:06:54 UTC
I don't think it's a duplicate. Furthermore, the bug indicated by you has already been marked as resolved.

Have you looked at the attached picture? The effect may be similar and even may have a similar cause, but the matter of "no menu bar" seems to be specific and new to me.

Regards
Christian
Comment 3 Ruslan Kabatsayev 2011-03-14 17:28:08 UTC
Well, if you say there's no selection indication, then you'll have to admit that there's nothing of Oxygen at all in emacs window on your screenshot, which is just the same as the bug i've mentioned.
See Holger Arnold's posts in that bug, they might be of some use to you.
Comment 4 Ruslan Kabatsayev 2011-03-14 17:30:11 UTC
P.S. i'd rather resolve it as WORKSFORME, not as FIXED, but i don't have the right to change resolution :)
Comment 5 Hugo Pereira Da Costa 2011-03-14 19:24:29 UTC
As Ruslan indicated, 
oxygen is not the style used for this screenshot. 
Have you actually looked at the screenshot of bug 263182 ?
It is indeed identical as yours.

This is likely some installation settings, some distro specific config file for emacs, or anything. 

You can try post here the content of your $HOME/.gtkrc though I doubt it would help.

And I cannot reproduce here ...
Comment 6 Christian L 2011-03-14 20:09:57 UTC
You are right, Hugo. It looks absolutely the same. 

It definitely is a duplicate. 

I had seen the bug 263182 before but, as it has been closed, I thought it would be the worth to notify my problem. 

Thanks already for your assistance. I don't want this to become a private issue. 

Anyway, I have the following message starting emacs via a console in KDE 4.6.1. The same message reported Holger in the mentioned bug (his comment 2).  

      (emacs:5613): GLib-GObject-WARNING **: plugin 'oxygen-gtk' failed to register type 'OxygenStyle'

So I'll check my installation and the problem may disappear through a next update, as with Holger. 

Thanks, 
Christian
Comment 7 Hugo Pereira Da Costa 2011-03-15 18:05:51 UTC
Yeah. So basically "(emacs:5613): GLib-GObject-WARNING **: plugin 'oxygen-gtk' failed to register type 'OxygenStyle'" means that oxygen  gtk tries to use oxygen-gtk but fails.

So this is likely not a problem of configuration.
My best guess is that emacs (dirty dirty) forces pre-loading some libraries that are not the ones against which oxygen-gtk was compiled. As a result, oxygen-gtk gets (and reports) undefined symbols, and therefore cannot be loaded.

There is really nothing we can do about it (strictly speaking, its an emacs bug; and it is not the only one doing the same *bad* things).
Comment 8 Holger Arnold 2011-03-16 18:28:48 UTC
@Christian: unfortunately, the problem won't disappear just by updating.  There must be some other reason.  Perhaps some library is missing?

@Hugo (or some other GTK expert): is there a way to find out what exactly causes these "failed to register" messages?  The debug options of GTK are not very helpful.
Comment 9 Hugo Pereira Da Costa 2011-03-18 10:51:41 UTC
So marking as duplicate, to avoid having related posts sent at two different places. I re-oppened the other bug (though again: this is *not* an oxygen-gtk bug), because I too would like to have this fixed (or figure a workaround).

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