Darktable broke for me after the last stable update, and it seems to be an issue with the libgphoto2 library. Arch has already fixed it (Commits · main · Arch Linux / Packaging / Packages / libgphoto2 · GitLab), but that fix isn’t in Manjaro’s next stable release. Since Darktable is critical and I don’t want to use the Flatpak, I’ve stopped updating.
Does anyone know when libgphoto2 2.5.32-2 will hit the Stable branch?
Curious… Although I see a message about libgphoto2_port.so.12 having no version information available, it’s non-fatal and Darktable works as usual. I’ve actually downgraded DT because the latest version has an annoying bug (reported upstream) whereby changes to which filters are expanded/contracted in the UI are ignored. The non-fatal error occurs with both the latest and downgraded version.
Is this actually stopping your Darktable working completely?
Your post has been moved to a dedicated topic. Please provide system information as described (below) and any other details that might help others to help you.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; 
Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
libgphoto2 2.5.32-1.1 should fix that …
I don’t use Darktable every day, but on Testing I have libgphoto 2.5.32-2 and it’s running well.
Just tried the latest stable update on the other laptop, and Darktable after the upgrade to 5.2 works correctly. But on the main desktop, the app started to run into segfaults:
this is darktable 5.2.0 reporting a segfault:
warning: Currently logging to /tmp/darktable_bt_7WZQ92.txt. Turn the logging off and on to make the new setting effective.
#0 0x00007efcd30ade22 in ?? () from /usr/lib/libc.so.6
#1 0x00007efcd30a1fda in ?? () from /usr/lib/libc.so.6
#2 0x00007efcd30a2024 in ?? () from /usr/lib/libc.so.6
#3 0x00007efcd311292f in wait4 () from /usr/lib/libc.so.6
#4 0x00007efcd339ed34 in ?? () from /usr/bin/../lib/darktable/libdarktable.so
#5 <signal handler called>
#6 0x0000000000000000 in ?? ()
#7 0x00007efc01b27d00 in ?? () from /usr/lib/libportmidi.so.2
#8 0x00007efc01b275bd in Pm_Read () from /usr/lib/libportmidi.so.2
#9 0x00007efc01b6d2d6 in ?? () from /usr/lib/darktable/plugins/lighttable/libmidi.so
#10 0x00007efcd2ec6511 in ?? () from /usr/lib/libglib-2.0.so.0
#11 0x00007efcd2ec487d in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x00007efcd2ec5cd7 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007efcd2ec6097 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#14 0x00007efcd2a2a1cf in gtk_main () from /usr/lib/libgtk-3.so.0
#15 0x00007efcd34ebea1 in dt_gui_gtk_run () from /usr/bin/../lib/darktable/libdarktable.so
#16 0x000055924ce951db in ?? ()
#17 0x00007efcd30376b5 in ?? () from /usr/lib/libc.so.6
#18 0x00007efcd3037769 in __libc_start_main () from /usr/lib/libc.so.6
#19 0x000055924ce95275 in ?? ()
Here is the shortened output from inxi:
System:
Kernel: 6.12.34-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.15.0
wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Memory:
System RAM: total: 32 GiB available: 31.27 GiB used: 5.26 GiB (16.8%)
CPU:
Info: model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ gen: 1+
level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB
desc: 8x512 KiB L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 1406 min/max: 1550/3200 boost: enabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 1406 2: 1406 3: 1406
4: 1406 5: 1406 6: 1406 7: 1406 8: 1406 9: 1406 10: 1406 11: 1406 12: 1406
13: 1406 14: 1406 15: 1406 16: 1406 bogomips: 102232
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia
v: 575.64 alternate: nouveau,nvidia_drm non-free: 550-570.xx+ status: current
(as of 2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 06:00.0
chip-ID: 10de:1c82 class-ID: 0300
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 166 s-size: 392x220mm (15.43x8.66")
s-diag: 450mm (17.7")
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Mi 27 NU
serial: <filter> built: 2022 res: mode: 2560x1440 hz: 60 scale: 100% (1)
dpi: 109 gamma: 1.2 chroma: red: x: 0.694 y: 0.302 green: x: 0.200
y: 0.757 blue: x: 0.153 y: 0.055 white: x: 0.314 y: 0.329
size: 597x335mm (23.5x13.19") diag: 685mm (27") ratio: 16:9
modes: 3840x2160, 2560x1440, 1920x1080, 1680x1050, 1600x900, 1280x1024,
1440x900, 1280x800, 1152x864, 1280x720, 1024x768, 800x600, 720x576,
720x480, 640x480
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.