darktable icon indicating copy to clipboard operation
darktable copied to clipboard

Some buttons not working on macOS + darktable v3.8

Open tomtomtls opened this issue 3 years ago • 13 comments

To Reproduce

  1. Go to 'Darkroom'
  2. Click on 'Presets' (or Ctrl + Click)
  3. Create a new preset or duplicate one (same behaviour)
  4. Try to add a widget to Quick Settings or a module to a group
  5. The "+" button do not open the list where one should select the widget or module

Other context / same behaviour regarding another button

  1. Go to 'Darkroom'
  2. Click on the arrow at the bottom of the screen to show/hide thumnails
  3. Nothing happens
  4. Use the Shift + Cmd + b shortcut
  5. Thumbnails are shown or hidden as expected

Expected behavior First case: a list with modules or widgets should allow the user to choose an item to be added to Quick Settings or another group Second case: thumnails are supposed to be hidden when the button / arrow is clicked

Screencast https://mesphotosetvideos.fr/CannotAddWidgetorModule.mov

Which commit introduced the error I am using darktable v3.8 as a fresh installation (not an update)

Platform

  • darktable version : 3.8 and another set of tests with 3.8.0+59_ge758e1366
  • OS : OSx Big Sur 11.6.2
  • Memory : 16 Go
  • Graphics card : Intel UHD Graphics 617 1536 Mo
  • Graphics driver :
  • OpenCL installed :
  • OpenCL activated :
  • Xorg :
  • Desktop :
  • GTK+ :
  • gcc :
  • cflags :
  • CMAKE_BUILD_TYPE :

Additional context

  • Can you reproduce with another darktable version(s)? yes with version 3.6.1 also installed from scratch ; same behaviour on 2 different Mac hardware (MBA 2019 / Mac mini)
  • Can you reproduce with a RAW or Jpeg or both? both
  • Are the steps above reproducible with a fresh edit (i.e. after discarding history)? yes
  • If the issue is with the output image, attach an XMP file if (you'll have to change the extension to .txt)
  • Is the issue still present using an empty/new config-dir (e.g. start darktable with --configdir "/tmp")? yes
  • Do you use lua scripts? no
    • What lua scripts start automatically?
    • What lua scripts were running when the bug occurred?

tomtomtls avatar Jan 12 '22 22:01 tomtomtls

More details: I just managed to launch DT in debug mode to catch info. And... the menu widget menu was almost accessible: can you see it behind the module window? (!)

Capture d’écran 2022-01-14 à 22 16 23

Not sure if it is linked to the problem since I could not reproduce it for the moment, but launching the app in debug mode forced (my native) french language, whereas I set darktable to use english.

tomtomtls avatar Jan 14 '22 21:01 tomtomtls

I have the same issue (iMac 27'', macOS 11.6.2), but only in fullscreen mode: the dialog does not work, nothing happens when the + buttons are pressed. Also the red window close button partly does not react.

The following sequence often seems to put it into normal working mode: hide the dialog (yellow button), cmd-tab to change to a different application like the web browser, retrieve the dialog from there again (by clicking on its icon in the dock).

Luckily, in window mode everything seems to work as expected!

Starting darktable from the command line and in debug mode, I get the following error messages (no idea if it is related or not): (darktable:3593): GLib-GObject-WARNING **: 20:48:28.119: invalid cast from 'GtkMenuBar' to 'GtkWindow' (darktable:3593): Gtk-CRITICAL **: 20:48:28.119: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed

geni1105 avatar Jan 15 '22 20:01 geni1105

Thank you for the windows mode workaround! I always work in full screen mode, but as soon as I switched to windows mode I could set my own preset!!!

tomtomtls avatar Jan 15 '22 20:01 tomtomtls

So that's seems a specific MacOS bug when in full screen. You just have now to wait that a developer who work on MacOS see that and start testing/working on that.

Nilvus avatar Jan 19 '22 11:01 Nilvus

Ready to help / test if needed.

tomtomtls avatar Jan 19 '22 12:01 tomtomtls

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Mar 21 '22 00:03 github-actions[bot]

Up to get a fix if possible 🤞🏼

tomtomtls avatar Mar 28 '22 19:03 tomtomtls

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar May 28 '22 00:05 github-actions[bot]

Another up to -hopefully- get a fix. Still willing to help as much as possible, just tell me what I can do 👍

tomtomtls avatar May 28 '22 13:05 tomtomtls

did you check if that might be an upstream bug in gtk?

MStraeten avatar May 29 '22 05:05 MStraeten

Not sure how I can do that (somewhere in gtk project follow up I guess?), but I will check darktable v4 since UI seems to be heavily rebuilt.

tomtomtls avatar Jul 05 '22 09:07 tomtomtls

Not sure how I can do that (somewhere in gtk project follow up I guess?), but I will check darktable v4 since UI seems to be heavily rebuilt.

As of today no change/fix. Users, many working I guess in fullscreen mode, are not aware of the work-around and will think it's not working alltogether.

jbrogaard avatar Aug 04 '22 20:08 jbrogaard

This issue did not get any activity in the past 60 days and will be closed in 365 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Oct 04 '22 00:10 github-actions[bot]

Hello, I'm new to Darktable and I'm having the same issue. A lot of commands do not respond. Unfortunately, in my case, nothing changes even if I leave full-screen mode and use windows mode. Mac mini Arm M1 - MacBook Pro Arm M1 Pro

Drill01 avatar Jan 06 '23 13:01 Drill01

Hello, I'm new to Darktable and I'm having the same issue. A lot of commands do not respond. Unfortunately, in my case, nothing changes even if I leave full-screen mode and use windows mode. Mac mini Arm M1 - MacBook Pro Arm M1 Pro

Your issue is a duplicate of #12727 most likely.

parafin avatar Jan 06 '23 14:01 parafin

An old issue, probably fixed. A last package had been done to fix some Gtk issues. See there: https://discuss.pixls.us/t/current-osx-build/13213/596 @tomtomtls and @jbrogaard: could you test if downloading last darktable MacOS package updating few days ago in link above, and post feedback here if your issue is fixed? @tomtomtls: if fixed, think about closing your issue yourself. Thanks.

Nilvus avatar Jan 31 '23 17:01 Nilvus

Still does not work in fullscreen mode unfortunately (macOS 11.7.3, Intel; tested with official darktable 4.2.0, self-built 4.3.0+ from current master, and @MStraeten's latest build).

Behavior is the same on all, and a bit improved compared to my earlier comment: '+' buttons to manage darkroom presets do not react, but after cmd-tab'ing to a different application and back it usually works.

geni1105 avatar Feb 04 '23 15:02 geni1105

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Apr 06 '23 00:04 github-actions[bot]

Not sure if this comment can help, if it's the same issue of not, nor what data might be of use so I'm just going to throw some stuff here.

There are usability issues on my configuration:

  • installed yesterday through homebrew
  • Apple M1 Pro - OS X Ventura 13.4.1
  • Darktable 4.4.2
  • the issues only seem to occur when using Darktable on my Lenovo monitor (connected to the mac through a docking station). When putting the window on the macbook screen it seems to behave OK, even with the monitor still connected. Using Fullscreen or Window mode makes no difference.

There are:

  • select boxes that seem to have missing items, like the preset selector only showing two options when there are in fact more
  • buttons not responding, like the close button of the presets config window
  • difficult to control scrolling behaviors.
Click to see gif screenshot

darktable

Not sure how I can get extra debug info like the Gtk version. Please let me know if I can help or if I should open / follow another ticket.

Campano avatar Aug 10 '23 23:08 Campano

the issue seems to be a gtk issue - see https://github.com/darktable-org/darktable/issues/14856 (there’s also a link to an arm build using a gtk3 version that doesn’t show that behaviour - but has a redraw issue ;) )

MStraeten avatar Aug 11 '23 05:08 MStraeten

Closing this since gtk related - a newer gtk version doesn’t behave this way but shows ne issues ;)

MStraeten avatar Aug 11 '23 05:08 MStraeten