Question

1

How do you disable the global menu in digikam?

rated 0 times [ 1] [ 0] / answers: 1 / hits: 916 / 2 Years ago, wed, march 16, 2022, 9:08:18

I use digikam which suffers from a bug that means the editor loses its menu after the first launch. In 11.04 I could disable the global menu for digikam by launching it with:

APPMENU_DISPLAY_BOTH=1 digikam

However this appears to have stopped working in 11.10. Is there some other way to get an application to show the menubar in the window rather than the panel?

(Just checked and APPMENU_DISPLAY_BOTH=1 gedit does lead to gedit having a menu in the window. But maybe there is some other way?)

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

untroo

Add To Favorites

Follow

Total Points: 3

Total Questions: 110

Total Answers: 95

Location: Palestine

Member since Thu, Oct 28, 2021

3 Years ago

answered 2 Years ago sweetrifiabl · Accepted Answer

Your question is '..to disable the global menu in digikam'

What you've been doing previously is not disabling the global menu but enabling both the global & in app window menu. (which by the way should still work

To actually disable global on an individual qt4 app's you use this in various ways

QT_X11_NO_NATIVE_MENUBAR=1

For opening digikam from a menu, dash, ie. thru it's .desktop, then you simply edit the Exec= line in it's .desktop or if using unity & a quicklist the Exec= in the quicklist entry. Example on digikam's .desktop

gksudo gedit /usr/share/applications/kde4/digikam.desktop

Then use this as the Exec= line in the .desktop

Exec=env QT_X11_NO_NATIVE_MENUBAR=1 digikam -caption "%c" %i

For starting from a terminal you'd do this instead (or create an alias

export QT_X11_NO_NATIVE_MENUBAR=1; digikam

For starting from Alt+F2 - a bit more complicated, probably not of interest here

As far as why you can't use your old 'both' method, not sure. If inclined to pursue I'd start by creating a new user, logging into it & seeing if it works there. If so it's something local to your user, you can track it down if desired with a little time & effort