You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked and did not find my issue in the already reported ones
Describe the bug
In the last few months (I didn't notice from which version) when the darktable is launched, timeline is not displayed or is displayed partially. The timeline view becomes normal only after clicking LMB on it or after scrolling the mouse wheel over it.
Steps to reproduce
run darktable
see like screenshots 5.1.0+473_linux-1.png, 5.1.0+473_windows10-1.png
click LMB on timeline or hover mouse over timeline and scroll the mouse wheel.
see like screenshots 5.1.0+473_windows10-2.png, 5.1.0+473_linux-2.png
Expected behavior
normal view as on screenshots 5.1.0+473_windows10-2.png, 5.1.0+473_linux-2.png immediately after starting the darktable
Is there an existing issue for this?
Describe the bug
In the last few months (I didn't notice from which version) when the darktable is launched, timeline is not displayed or is displayed partially. The timeline view becomes normal only after clicking LMB on it or after scrolling the mouse wheel over it.
Steps to reproduce
Expected behavior
normal view as on screenshots 5.1.0+473_windows10-2.png, 5.1.0+473_linux-2.png immediately after starting the darktable
Logfile | Screenshot | Screencast
5.1.0+473_windows10-1.png




5.1.0+473_linux-1.png
5.1.0+473_windows10-2.png
5.1.0+473_linux-2.png
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.1.0+473~g51e22e438a
What OS are you using?
Linux, Windows
What is the version of your OS?
Windows 10, Debian 12
Describe your system
No response
Are you using OpenCL GPU in darktable?
Yes
I tried to turn opencl on and off
If yes, what is the GPU card and driver?
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
The text was updated successfully, but these errors were encountered: