GNOME Bugzilla – Bug 743937
File > New Menu is not visible anymore
Last modified: 2015-03-08 15:08:08 UTC
Created attachment 296027 [details] Screenshot of Menu I am running 2.8.14 on Mac OS, Yosemite 10.2.2. After scaling an image to the size previously stated by the selection tool, in the menu bar the menu entry for File > New does not exist anymore. As you can see in the attached image, there is no entry for File (Datei) -> New (Neu). Nach Skalieren eines Bildes auf die aktuelle Auswahl mittels Kontextmenü rechte Maustaste > Bild > Auf Auswahl zuschneiden ist im Menü der Eintrag Datei > Neu nicht mehr vorhanden.
Where did you get GIMP from?
Directly from the Gimp website.
Ok, can anyone reproduce this?
Dark theme in the screenshot - is this the build from download.gimp.org or the one from lisanet?
I was not able to reproduce it on OS X 10.7.5 with GIMP 2.8.14 from wgo [1], or with local builds of GIMP 2.8.14 and GIMP git master (not bundled, with latest gtk-mac-integration 2.07, dependencies via MacPorts). OS X 10.7.5 is quite dated though - it might be possible that the observed issue only happens on Yosemite ... [1] the package created by Sven Claussner: http://download.gimp.org/pub/gimp/v2.8/osx/gimp-2.8.14.dmg
Chris, do you use the version mentioned by su-v in comment 5?
I am running 2.8.14 on Mac OS, Yosemite 10.2.2.
From the link in comment 5, or the version from lisanet?
From http://download.gimp.org/pub/gimp/v2.8/osx/gimp-2.8.14.dmg.torrent
Quoting from the ChangeLog file included in the DMGs of the most recent uploads by skl on 2015-01-09 and 2015-01-11: http://sourceforge.net/projects/gimponosx/files/?source=navbar e.g. for Gimp-2.8.14p2-Mavericks-Yosemite.dmg <quote> 2.8.14p2 (Mavericks Yosemite) ============================ 09.01.2015 * lots of bug fixed: <…> * fixed a bug, where using the context menu (right-click on the canvas) has totally scrambled the main menubar <…> </quote> There is no further information provided (neither at gimp.lisanet.de, nor in the repo maintained for 'GIMP on OS X' at sf.net), so I cannot tell whether that bug was specific to skl's build, or not. Some notes: 1) In my tests it does not reproduce with the official wgo build and with local builds which all use the original gtk-mac-integration library instead of lisanet's fork. 2) the same patch seems to be in the 2.8.14p2 packages for Lion and Mountain Lion by skl which indicates that it is not specific to Yosemite (for builds which are affected).
(In reply to su-v from comment #10) > Quoting from the ChangeLog file included in the DMGs of the most recent > uploads by skl on 2015-01-09 and 2015-01-11: Just to clarify: I only looked at the ChangeLog file but did not install & run skl's build.
Hm... the GIMP screenshot in the original post shows a dark ui theme - IIRC the one from downloads doesn't have that one by default. How easy is it for OSX users to run a different GIMP version than they think, i.e. the lisanet one instead of the wgo one - and will they be able to tell the difference somehow?
Created attachment 296981 [details] Finder info for GIMP from skl and wgo (In reply to Michael Schumacher from comment #12) > How easy is it for OSX users to run a different GIMP version than they > think, i.e. the lisanet one instead of the wgo one Define 'easy' - forget which link was clicked for the download? Don't keep the DMG file after installing it? It likely can happen quite easily ... > and will they be able to tell the difference somehow? Select the application in the Finder, use 'Cmd+I' (or 'File > Get Info') and read the copyright message displayed in the info dialog is quite easy: official build: © 1995-2013 The GIMP Development Team skl's latest build: © 2001-2014 The GIMP Team, build by skl 2014 for GIMP on OS X, http://gimp.lisanet.de The two builds also identify differently in console logs and crash reports: Chillida:_gimp_temp su_v$ defaults read $(pwd)/GIMP-skl.app/Contents/Info CFBundleIdentifier de.lisanet.gimp Chillida:_gimp_temp su_v$ defaults read $(pwd)/GIMP-wgo.app/Contents/Info CFBundleIdentifier org.gnome.gimp Chillida:_gimp_temp su_v$ The app icon for the two builds also differs (see attachment).
Ok, this would solve it if the user provides this information. For quick id by looking at screenshot only - can we assume that "dark theme == this is not the wgo build"?
(In reply to Michael Schumacher from comment #14) > Ok, this would solve it if the user provides this information. > > For quick id by looking at screenshot only - can we assume that "dark theme > == this is not the wgo build"? Yes - out-of-the-box the wgo build uses a light theme. Screenshots of wgo build launched with new preferences (after switching to swm): https://www.dropbox.com/sh/eftshsitexihpez/AADgQY0JFW5Cii7n1tlxfTbla?dl=0
The info is as follows: © 2001-2014 The GIMP Team, build by skl 2014 for GIMP on OS X, http://gimp.lisanet.de
(In reply to su-v from comment #15) > Yes - out-of-the-box the wgo build uses a light theme. Thanks.
So, Chris, You were using a thirds-party build. Apparently this build might have been fixed in the meantime, otherwise you could install and run the one that is directly downloaded from our site.
In any case, this is nothing we can fix. Closing as NOTGNOME.