Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

darktable 5.0 crashes on paste of stack to different image #18340

Open
1 task done
cycomanic opened this issue Feb 2, 2025 · 1 comment
Open
1 task done

darktable 5.0 crashes on paste of stack to different image #18340

cycomanic opened this issue Feb 2, 2025 · 1 comment
Labels
Fixed in master Has already been fixed in current master branch

Comments

@cycomanic
Copy link
Contributor

Is there an existing issue for this?

  • I checked and did not find my issue in the already reported ones

Describe the bug

Paste of history stack to a different image on the filmstrip below the main image inside the darkroom reliably crashes darktable 5.0 on arch linux for me. Stacktrace below (not terribly informative):

Steps to reproduce

  1. Open image in darkroom
  2. copy edit history
  3. paste to another image on the filmstrip below
  4. darktable will freeze and shortly after close

Expected behavior

No response

Logfile | Screenshot | Screencast

Thread 1 "darktable" received signal SIGSEGV, Segmentation fault.
0x00007ffff6614df1 in g_type_check_instance_is_fundamentally_a () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0 0x00007ffff6614df1 in g_type_check_instance_is_fundamentally_a () from /usr/lib/libgobject-2.0.so.0
#1 0x00007ffff65ef7bc in g_object_ref () from /usr/lib/libgobject-2.0.so.0
#2 0x00007ffff734584c in gdk_window_set_cursor () from /usr/lib/libgdk-3.so.0
#3 0x00007ffff7ad92ba in dt_gui_cursor_clear_busy () from /usr/bin/../lib/darktable/libdarktable.so
#4 0x00007ffff79a62d0 in _cursor_clear_busy () from /usr/bin/../lib/darktable/libdarktable.so
#5 0x00007ffff769652a in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00007ffff770a0b0 in ?? () from /usr/lib/libglib-2.0.so.0
#7 0x00007ffff769e477 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff6c0a457 in gtk_main () from /usr/lib/libgtk-3.so.0
#9 0x00007ffff7ad3119 in dt_gui_gtk_run () from /usr/bin/../lib/darktable/libdarktable.so
#10 0x0000555555555183 in ?? ()
#11 0x00007ffff74261ce in ?? () from /usr/lib/libc.so.6
#12 0x00007ffff742628a in __libc_start_main () from /usr/lib/libc.so.6
#13 0x0000555555555265 in ?? ()

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

darktable 5.0.0

What OS are you using?

Linux

What is the version of your OS?

cachyos (arch derivative)

Describe your system

No response

Are you using OpenCL GPU in darktable?

No

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

@ralfbrown
Copy link
Collaborator

Backtrace shows that the crash involves turning off the busy cursor; I think this has been fixed in Master.

Can you try running a nightly build?

@ralfbrown ralfbrown added the Fixed in master Has already been fixed in current master branch label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in master Has already been fixed in current master branch
Projects
None yet
Development

No branches or pull requests

2 participants