Created attachment 187999 [details] Described Attachments I used the 8.9.0 weekly Appimage until the version of 16.12.2025. There were no problems with this version. The last pictures were added to the database with this version. Even after that, the start and work with Digikam was not a problem. But with the next available weekly until today (9.0.0) there is a problem after the start of the program. On the one hand, it may happen that the program window sticks without any interaction after the start to the left edge of the screen with the left edge. After another attempt, the program window will also be displayed correctly placed in the center of the screen. STEPS TO REPRODUCE 1. Start Digikam Appimage 2. Do nothing, wait 3. After a few seconds DK crashes OBSERVED RESULT In both possibilities, the program starts and shows the known surface. It runs a process in background (ventilator noise), the previews remain empty and then Digikam crashes after a few seconds. EXPECTED RESULT Normal behavior would now be the set scanning for new images and viewing the previews. The App not crashing. Like its was in Versions till the weekly till 16.12.2025. Version 8.8.0 is now installed again and works with same database and pictures without any kind of this described problems. SOFTWARE/OS VERSIONS Digikam Appimage weekly newer than from 16.12.2025 LinuxMint 22.2 on AMD Ryzen 9 5900X, 64 Gb RAM. ADDITIONAL INFORMATION I tried to use a Debug-Version and tried after the manual but with no success. I'm not a console junky or a programmer. As attachment three recorded tracks and a screenschot after App-Start short before crash with empty picturepreviews. The tracks are two crashes and one start without any problems. After that there where only crashes.
Please download the AppImage with "debug" in its name. In the terminal, start the AppImage with the "debug" option (without quotation marks). Type "r + Enter" to continue. After the crash, type "bt + Enter" and post the resulting output here. Maik
Maik, This simple method to run the AppImage in gdb break the debugger at startup (segmentation fault due to binary compatibility). In my office where we have also an AppImage version for a customer application, i search for an universal solution. Look here : https://www.digikam.org/contribute/#appimage-bundle It's more technical but it work for all host linux. Typically, there is a 30s tempo at first init of digiKam waiting to continue. This allow to launch a second terminal with GDB connected to the digiKam process ID. Gilles
> https://www.digikam.org/contribute/#appimage-bundle As I wrote before, I had already tried. Just a few days ago. I generally opened a terminal, then another terminal in the directory where the downloaded Debug app image is located. See attached screenshot of my attempt today :-( https://nowtransfer.de/74b373359b44 I had today previously downloaded the normal weekly app image for testing and installed with Appimagelauncher. This time the program window opened again at the left edge of the screen. But surprisingly stable, the previews were also displayed this time. However, the operation was not possible as usual. When you double click on an image preview, the preview window opened as usual. But in this, for example, the picture in the enlarged view could no longer be dragged by mouse. I had never before showed any picture info in this window, now there where shown infos. In normal case i could go back to the complete album overview with a double klick on the picture in the preview window ... dosn't work anymore. I must go to the in the menue to go there back. I closed the App and installed Version 8.8 again, because i can't work with Digikam in newer versions anymore :-(((
Sorry, i coudnt edit anymore. After ended the described Version from today, an new start crashed it like described in the bug report.
We're working on a metadata overlay; your issue is already fixed in the current git/master repository, and it will be available to you again with the next AppImage release. When we implement new features, daily snapshots may contain errors. Maik
(In reply to Maik Qualmann from comment #5) > When we implement new features, daily snapshots may contain errors. I am aware of this. I'm trying to draw attention to problems here with a bug report. And probably no one else knows the program better than you. In addition, every now and then you are given the advice to try out the current version. It is also practical to be able to benefit from a few bug fixes that have already been implemented compared to the stable version. Until December 16th It worked without any problems, so it can be assumed that something slipped from that point on. I can still work with version 8.8. But I'm afraid a new stable version might no longer work for me under these unresolved circumstances.
Now, after a lot of trying, I actually managed to unpack the debug app image and start Digikam in this squashfs-root directory. It worked without causing any problems!!! However, I was unable to get the debugger to cooperate with the commands copied from the instructions in a second window (see above). Now the question is, why does Digikam Debug work this way without any problems, while the normal app image crashes as described above? In this respect, it is not clear to me how this procedure with the debug app image can provide any insight if, in contrast to the app image, it behaves in a stable manner. But I'm not a developer or programmer either ;-) And as already mentioned, both 8.8 and later weekly until 16.12. also ran without crashing. 8.8 runs now without problems again. Where is the error? I don't know why this Debug-thing not worked ... :( ua@ua-Big:~/Downloads$ pid=$(pidof digikam) ; binary=$(readlink -f "/proc/$pid/exe") ; dir=$(dirname "\$binary") ; gdb "\$binary" -p \$pid -ex "set sysroot \$dir" -ex "set solib-search-path \$dir/usr/lib" -ex "catch throw" -ex "continue" GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... $binary: File or directory not found. Illegal process id: $pid. Catchpoint 1 (throw) The program is not running. (gdb)
Well the AppImage is a chrooted like bundle. It must run without any host system dependencies excepted the core libc which depend of the Linux Kernel and vis-versa). https://en.wikipedia.org/wiki/AppImage The chroot (https://en.wikipedia.org/wiki/Chroot) allow to secure the program execution and the host system. With the AppImage this is done at the first time of the startup. Executable is decompressed in memory and mounted somewhere in /tmp using Fuse. After that it run as a chrooted program. The way to uncompress manually the appimage and run it as well will reduce the chroot operation (i'm not sure about this point). This can have good side-effects at run time. In other word something is not well compatible in your system with the AppImage mechanism or something is missing. It's difficult to judge without to be online on your computer, but it's another story... Best regards Gilles Caulier
„In other word something is not well compatible in your system with the AppImage mechanism or something is missing.“ Hmm, this explanation is a bit too simple for me. I use Appimagelauncher in one of the last 3.0 beta versions. This is how I install all the app images I have used so far. The last app image installed was the updated version of Krita on December 15th. All previously installed app images work smoothly and do not crash. I don't know how often I repeated it now, including the Digikam 8.9.0 weeklys until December 16th. worked. The Digikam 8.8 app image works. Newer Digikam app images no longer work. I started today's debug version normally after my attempt described above. Crash. I then tried again with the normal app image, crash. I just uninstalled Appimagelauncher again, started Digikam Appimage manually by simply double-clicking it, and it crashed. Digikam 8.8 installed again, running... All other app images work... I haven't changed anything else on my system and now you tell me it's a bug on my system? What should I look for?
I never said that you system is not compatible with all AppImage bundle. I said that something is not compatible with the last version of the digiKam AppImage. Main changes : switch from Qt6.9 to Qt 6.10 for security and bugfixes. Not all Qt Applications uses the last Qt version in a bundle. Again with hack with the debugger, it's diffcult to found where is the problem... Gilles Caulier
Sorry, that now sounds a little bit different for me ;-) I don't know why this debugger thing does not work or can not find digikam. I had the manual window open to get it right ... Good night ;-)
Git commit 66e54e56797eea5a030f3195232882ac3d8b45d6 by Gilles Caulier. Committed on 29/12/2025 at 14:36. Pushed by cgilles into branch 'master'. Linux AppImage: include a script to hack digiKam at startup in debug mode with a remote GDB M +5 -0 project/bundles/appimage/04-build-appimage.sh A +65 -0 project/bundles/appimage/data/run_remote_gdb.sh https://invent.kde.org/graphics/digikam/-/commit/66e54e56797eea5a030f3195232882ac3d8b45d6
Hi, I review whole debugging with the AppImage and I written a bash script (included in the next AppImage bundle de facto). The script works as expected on my computer and can be used with your version of the AppImage. It can be downloaded here : https://invent.kde.org/graphics/digikam/-/raw/master/project/bundles/appimage/data/run_remote_gdb.sh?ref_type=heads To use it it's very similar than the previous procedure available in the web site, expected that we don't need to use a very long command line in the second terminal instance. Best regards Gilles Caulier
I updated the procedure to use the remote GDB script : https://www.digikam.org/contribute/#appimage-bundle
dk_nanodot@unbox.at Let's me hear if all work as expected on your computer. Best regards Gilles Caulier
dk_nanodot@unbox.at Screen-cast about to start a remote debugging session with gdb with 2 terminals: https://www.digikam.org/vid/content/contribute/appimage_remote_gdb.mp4 Best Gilles Caulier
I renamed the remote GDB script. It's here now : https://invent.kde.org/graphics/digikam/-/raw/master/project/bundles/appimage/data/run_digikam_gdb.sh?ref_type=heads
Thank you for your efforts! I think i was to fast ;-))) But i tried with the scriptname before. Digikam starts in its squash, but the script in the second console dos not run. See screenshot. https://nowtransfer.de/7dbaf4075f74
I think i got it. The Bashscript must be run „Ausführbar“ as a Programm!!!
Startet Digikam, clicked at a Preview, opend Preview, doubleklick in picture to go back to previews, than closed the App in the menu. ua@ua-Big:~/Downloads$ sudo ./run_remote_gdb.sh [sudo] Passwort für ua: Check run as root passed... pid=17248 binary=/home/ua/Downloads/squashfs-root/usr/bin/digikam dir=/home/ua/Downloads/squashfs-root/usr/bin [New LWP 17250] [New LWP 17249] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___fstatat64 (fd=-100, file=0x789ea31cca27 "/etc/localtime", buf=0x7ffee5441d30, flag=0) at ../sysdeps/unix/sysv/linux/fstatat64.c:159 Catchpoint 1 (throw) [New Thread 0x789e7ffff6c0 (LWP 17272)] [Detaching after vfork from child process 17273] [Detaching after vfork from child process 17274] [Detaching after vfork from child process 17275] [Detaching after vfork from child process 17276] [Detaching after vfork from child process 17277] [Detaching after vfork from child process 17278] [Detaching after vfork from child process 17279] [Detaching after vfork from child process 17280] [Detaching after vfork from child process 17281] [Detaching after vfork from child process 17282] [Detaching after vfork from child process 17283] [Detaching after vfork from child process 17284] [Detaching after vfork from child process 17285] [Detaching after vfork from child process 17286] [Detaching after vfork from child process 17287] [Detaching after vfork from child process 17288] [New Thread 0x789e7f7fe6c0 (LWP 17289)] [New Thread 0x789e7effd6c0 (LWP 17290)] [New Thread 0x789e7e7fc6c0 (LWP 17291)] [New Thread 0x789e7dffb6c0 (LWP 17292)] [New Thread 0x789e7d7fa6c0 (LWP 17309)] [Thread 0x789e7d7fa6c0 (LWP 17309) exited] [New Thread 0x789e7d7fa6c0 (LWP 17310)] [New Thread 0x789e623646c0 (LWP 17311)] [New Thread 0x789e61b636c0 (LWP 17312)] [New Thread 0x789e613626c0 (LWP 17313)] [New Thread 0x789e60b616c0 (LWP 17314)] [New Thread 0x789e4ffff6c0 (LWP 17315)] [Detaching after vfork from child process 17316] [New Thread 0x789e4c2f26c0 (LWP 17317)] [New Thread 0x789e4baf16c0 (LWP 17318)] [New Thread 0x789e4b2f06c0 (LWP 17319)] [New Thread 0x789e4aaef6c0 (LWP 17320)] [New Thread 0x789e32b6b6c0 (LWP 17322)] [Detaching after fork from child process 17323] [Detaching after fork from child process 17324] [Detaching after fork from child process 17325] [New Thread 0x789e3236a6c0 (LWP 17328)] [New Thread 0x789e31b696c0 (LWP 17329)] [New Thread 0x789e313686c0 (LWP 17330)] [New Thread 0x789e30b676c0 (LWP 17331)] [New Thread 0x789e273ff6c0 (LWP 17332)] [New Thread 0x789e26bfe6c0 (LWP 17333)] [New Thread 0x789e263fd6c0 (LWP 17334)] [New Thread 0x789e253fb6c0 (LWP 17335)] [New Thread 0x789e25bfc6c0 (LWP 17336)] [New Thread 0x789e24bfa6c0 (LWP 17337)] [New Thread 0x789dfffff6c0 (LWP 17338)] [New Thread 0x789dfeffd6c0 (LWP 17340)] [New Thread 0x789dff7fe6c0 (LWP 17339)] [New Thread 0x789dfe7fc6c0 (LWP 17341)] [New Thread 0x789dfdffb6c0 (LWP 17342)] [New Thread 0x789dfd7fa6c0 (LWP 17343)] [New Thread 0x789dfcff96c0 (LWP 17344)] [New Thread 0x789dd3fff6c0 (LWP 17345)] [New Thread 0x789dd37fe6c0 (LWP 17346)] [Thread 0x789dfcff96c0 (LWP 17344) exited] [New Thread 0x789dd27fc6c0 (LWP 17348)] [New Thread 0x789dd2ffd6c0 (LWP 17347)] [Thread 0x789dd3fff6c0 (LWP 17345) exited] [New Thread 0x789dd3fff6c0 (LWP 17349)] [Thread 0x789dd2ffd6c0 (LWP 17347) exited] [New Thread 0x789dfcff96c0 (LWP 17350)] [New Thread 0x789dd2ffd6c0 (LWP 17351)] [Thread 0x789dd3fff6c0 (LWP 17349) exited] [New Thread 0x789dd1ffb6c0 (LWP 17352)] [Thread 0x789dfcff96c0 (LWP 17350) exited] [New Thread 0x789dfcff96c0 (LWP 17353)] [New Thread 0x789dd3fff6c0 (LWP 17354)] [New Thread 0x789dd17fa6c0 (LWP 17355)] [Thread 0x789dd3fff6c0 (LWP 17354) exited] [New Thread 0x789dd3fff6c0 (LWP 17356)] [Thread 0x789dd17fa6c0 (LWP 17355) exited] [New Thread 0x789dd17fa6c0 (LWP 17357)] [Thread 0x789dd3fff6c0 (LWP 17356) exited] [New Thread 0x789dd0ff96c0 (LWP 17358)] [Thread 0x789dd17fa6c0 (LWP 17357) exited] [Thread 0x789dd0ff96c0 (LWP 17358) exited] [New Thread 0x789dd0ff96c0 (LWP 17359)] [New Thread 0x789dd17fa6c0 (LWP 17360)] [Thread 0x789dd0ff96c0 (LWP 17359) exited] [New Thread 0x789dd0ff96c0 (LWP 17361)] [Thread 0x789dd17fa6c0 (LWP 17360) exited] [New Thread 0x789dd17fa6c0 (LWP 17362)] [Thread 0x789dd0ff96c0 (LWP 17361) exited] [New Thread 0x789dd0ff96c0 (LWP 17363)] [Thread 0x789dd17fa6c0 (LWP 17362) exited] [Thread 0x789dd0ff96c0 (LWP 17363) exited] [New Thread 0x789dd0ff96c0 (LWP 17364)] [New Thread 0x789dd17fa6c0 (LWP 17365)] [New Thread 0x789dd3fff6c0 (LWP 17374)] [New Thread 0x789da7fff6c0 (LWP 17375)] [New Thread 0x789da77fe6c0 (LWP 17376)] [New Thread 0x789da6ffd6c0 (LWP 17377)] [New Thread 0x789da67fc6c0 (LWP 17378)] [New Thread 0x789da5ffb6c0 (LWP 17379)] [New Thread 0x789da57fa6c0 (LWP 17380)] [New Thread 0x789da4ff96c0 (LWP 17381)] [Thread 0x789da57fa6c0 (LWP 17380) exited] [New Thread 0x789d83fff6c0 (LWP 17382)] [Thread 0x789da4ff96c0 (LWP 17381) exited] [New Thread 0x789da4ff96c0 (LWP 17383)] [Thread 0x789d83fff6c0 (LWP 17382) exited] [New Thread 0x789d83fff6c0 (LWP 17384)] [Thread 0x789da4ff96c0 (LWP 17383) exited] [New Thread 0x789da4ff96c0 (LWP 17385)] [New Thread 0x789da57fa6c0 (LWP 17386)] [Thread 0x789da4ff96c0 (LWP 17385) exited] [Thread 0x789d83fff6c0 (LWP 17384) exited] [New Thread 0x789d7bfff6c0 (LWP 17387)] [New Thread 0x789da4ff96c0 (LWP 17388)] [New Thread 0x789d83fff6c0 (LWP 17389)] [Thread 0x789d7bfff6c0 (LWP 17387) exited] [New Thread 0x789d82ffd6c0 (LWP 17390)] [New Thread 0x789d837fe6c0 (LWP 17391)] [Thread 0x789da4ff96c0 (LWP 17388) exited] [New Thread 0x789da4ff96c0 (LWP 17392)] [Thread 0x789d837fe6c0 (LWP 17391) exited] [New Thread 0x789d837fe6c0 (LWP 17393)] [New Thread 0x789d7bfff6c0 (LWP 17394)] [Thread 0x789da4ff96c0 (LWP 17392) exited] [New Thread 0x789d81ffb6c0 (LWP 17395)] [New Thread 0x789d827fc6c0 (LWP 17396)] [Thread 0x789d837fe6c0 (LWP 17393) exited] [New Thread 0x789d837fe6c0 (LWP 17397)] [Thread 0x789d827fc6c0 (LWP 17396) exited] [Thread 0x789d837fe6c0 (LWP 17397) exited] [New Thread 0x789d837fe6c0 (LWP 17398)] [New Thread 0x789d827fc6c0 (LWP 17399)] [New Thread 0x789da4ff96c0 (LWP 17400)] [New Thread 0x789d817fa6c0 (LWP 17401)] [Thread 0x789da4ff96c0 (LWP 17400) exited] [New Thread 0x789da4ff96c0 (LWP 17402)] [Thread 0x789d817fa6c0 (LWP 17401) exited] [New Thread 0x789d80ff96c0 (LWP 17403)] [Thread 0x789da4ff96c0 (LWP 17402) exited] [New Thread 0x789da4ff96c0 (LWP 17404)] [Thread 0x789d80ff96c0 (LWP 17403) exited] [Thread 0x789da4ff96c0 (LWP 17404) exited] [New Thread 0x789da4ff96c0 (LWP 17405)] [New Thread 0x789d80ff96c0 (LWP 17406)] [Thread 0x789da4ff96c0 (LWP 17405) exited] [New Thread 0x789da4ff96c0 (LWP 17407)] [Thread 0x789d80ff96c0 (LWP 17406) exited] [New Thread 0x789d817fa6c0 (LWP 17408)] [Thread 0x789da4ff96c0 (LWP 17407) exited] [New Thread 0x789d80ff96c0 (LWP 17409)] [Thread 0x789d817fa6c0 (LWP 17408) exited] [New Thread 0x789da4ff96c0 (LWP 17410)] [New Thread 0x789d817fa6c0 (LWP 17411)] [Thread 0x789d80ff96c0 (LWP 17409) exited] [New Thread 0x789d80ff96c0 (LWP 17412)] [New Thread 0x789d7b7fe6c0 (LWP 17413)] [New Thread 0x789d7affd6c0 (LWP 17414)] [Thread 0x789d80ff96c0 (LWP 17412) exited] [Thread 0x789d7b7fe6c0 (LWP 17413) exited] [Thread 0x789d817fa6c0 (LWP 17411) exited] [Thread 0x789da4ff96c0 (LWP 17410) exited] [New Thread 0x789d817fa6c0 (LWP 17415)] [New Thread 0x789d7b7fe6c0 (LWP 17416)] [Thread 0x789d7affd6c0 (LWP 17414) exited] [New Thread 0x789d7affd6c0 (LWP 17417)] [Thread 0x789d817fa6c0 (LWP 17415) exited] [Thread 0x789d7affd6c0 (LWP 17417) exited] [Thread 0x789d7b7fe6c0 (LWP 17416) exited] [New Thread 0x789d7b7fe6c0 (LWP 17418)] [New Thread 0x789d7affd6c0 (LWP 17419)] [New Thread 0x789d817fa6c0 (LWP 17420)] [Thread 0x789d7b7fe6c0 (LWP 17418) exited] [New Thread 0x789d7b7fe6c0 (LWP 17421)] [Thread 0x789d7affd6c0 (LWP 17419) exited] [New Thread 0x789d7affd6c0 (LWP 17422)] [Thread 0x789d817fa6c0 (LWP 17420) exited] [Thread 0x789d7b7fe6c0 (LWP 17421) exited] [Thread 0x789d7affd6c0 (LWP 17422) exited] [New Thread 0x789d7affd6c0 (LWP 17423)] [New Thread 0x789d7b7fe6c0 (LWP 17424)] [New Thread 0x789d817fa6c0 (LWP 17425)] [Thread 0x789d7affd6c0 (LWP 17423) exited] [New Thread 0x789d7affd6c0 (LWP 17426)] [New Thread 0x789d80ff96c0 (LWP 17427)] [Thread 0x789d7affd6c0 (LWP 17426) exited] [Thread 0x789d7b7fe6c0 (LWP 17424) exited] [Thread 0x789d817fa6c0 (LWP 17425) exited] [Thread 0x789d80ff96c0 (LWP 17427) exited] [New Thread 0x789d80ff96c0 (LWP 17428)] [New Thread 0x789d817fa6c0 (LWP 17429)] [New Thread 0x789d7b7fe6c0 (LWP 17430)] [Thread 0x789d80ff96c0 (LWP 17428) exited] [New Thread 0x789d80ff96c0 (LWP 17431)] [Thread 0x789d817fa6c0 (LWP 17429) exited] [New Thread 0x789d817fa6c0 (LWP 17432)] [Thread 0x789d7b7fe6c0 (LWP 17430) exited] [Thread 0x789d80ff96c0 (LWP 17431) exited] [New Thread 0x789d7b7fe6c0 (LWP 17433)] [New Thread 0x789d80ff96c0 (LWP 17434)] [Thread 0x789d7b7fe6c0 (LWP 17433) exited] [Thread 0x789d817fa6c0 (LWP 17432) exited] [New Thread 0x789d7b7fe6c0 (LWP 17435)] [New Thread 0x789d817fa6c0 (LWP 17436)] [Thread 0x789d7b7fe6c0 (LWP 17435) exited] [Thread 0x789d80ff96c0 (LWP 17434) exited] [New Thread 0x789d7b7fe6c0 (LWP 17437)] [Thread 0x789d817fa6c0 (LWP 17436) exited] [New Thread 0x789d817fa6c0 (LWP 17438)] [New Thread 0x789d80ff96c0 (LWP 17439)] [Thread 0x789d817fa6c0 (LWP 17438) exited] [New Thread 0x789d817fa6c0 (LWP 17440)] [Thread 0x789d7b7fe6c0 (LWP 17437) exited] [Thread 0x789d80ff96c0 (LWP 17439) exited] [Thread 0x789d817fa6c0 (LWP 17440) exited] [New Thread 0x789d817fa6c0 (LWP 17441)] [New Thread 0x789d80ff96c0 (LWP 17442)] [Thread 0x789d817fa6c0 (LWP 17441) exited] [New Thread 0x789d7b7fe6c0 (LWP 17443)] [New Thread 0x789d817fa6c0 (LWP 17444)] [Thread 0x789d80ff96c0 (LWP 17442) exited] [New Thread 0x789d80ff96c0 (LWP 17445)] [Thread 0x789d817fa6c0 (LWP 17444) exited] [New Thread 0x789d817fa6c0 (LWP 17446)] [Thread 0x789d7b7fe6c0 (LWP 17443) exited] [New Thread 0x789d7b7fe6c0 (LWP 17447)] [New Thread 0x789d7affd6c0 (LWP 17448)] [Thread 0x789d7b7fe6c0 (LWP 17447) exited] [Thread 0x789d80ff96c0 (LWP 17445) exited] [New Thread 0x789d7b7fe6c0 (LWP 17449)] [New Thread 0x789d80ff96c0 (LWP 17450)] [Thread 0x789d7b7fe6c0 (LWP 17449) exited] [Thread 0x789d817fa6c0 (LWP 17446) exited] [New Thread 0x789d7b7fe6c0 (LWP 17451)] [Thread 0x789d80ff96c0 (LWP 17450) exited] [Thread 0x789d7affd6c0 (LWP 17448) exited] [New Thread 0x789d80ff96c0 (LWP 17452)] [New Thread 0x789d7affd6c0 (LWP 17453)] [Thread 0x789d80ff96c0 (LWP 17452) exited] [Thread 0x789d7b7fe6c0 (LWP 17451) exited] [New Thread 0x789d80ff96c0 (LWP 17454)] [Thread 0x789d7affd6c0 (LWP 17453) exited] [Thread 0x789dd3fff6c0 (LWP 17374) exited] [Thread 0x789da67fc6c0 (LWP 17378) exited] [Thread 0x789da77fe6c0 (LWP 17376) exited] [New Thread 0x789da77fe6c0 (LWP 17455)] [New Thread 0x789da67fc6c0 (LWP 17456)] [Thread 0x789d837fe6c0 (LWP 17398) exited] [New Thread 0x789d837fe6c0 (LWP 17457)] [New Thread 0x789dd3fff6c0 (LWP 17458)] [New Thread 0x789d7affd6c0 (LWP 17459)] [New Thread 0x789da4ff96c0 (LWP 17460)] [New Thread 0x789d817fa6c0 (LWP 17461)] [Thread 0x789da7fff6c0 (LWP 17375) exited] [Thread 0x789da5ffb6c0 (LWP 17379) exited] [Thread 0x789da6ffd6c0 (LWP 17377) exited] [Thread 0x789d827fc6c0 (LWP 17399) exited] [Thread 0x789d82ffd6c0 (LWP 17390) exited] [Thread 0x789d83fff6c0 (LWP 17389) exited] [Thread 0x789dd37fe6c0 (LWP 17346) exited] [Thread 0x789d81ffb6c0 (LWP 17395) exited] [Thread 0x789da57fa6c0 (LWP 17386) exited] [Thread 0x789dd27fc6c0 (LWP 17348) exited] [Thread 0x789dd2ffd6c0 (LWP 17351) exited] [Thread 0x789d80ff96c0 (LWP 17454) exited] [Thread 0x789dd1ffb6c0 (LWP 17352) exited] [Thread 0x789d7bfff6c0 (LWP 17394) exited] [Thread 0x789e60b616c0 (LWP 17314) exited] [Thread 0x789da67fc6c0 (LWP 17456) exited] [Thread 0x789da77fe6c0 (LWP 17455) exited] [Thread 0x789d837fe6c0 (LWP 17457) exited] [Thread 0x789da4ff96c0 (LWP 17460) exited] [Thread 0x789d817fa6c0 (LWP 17461) exited] [Thread 0x789dd3fff6c0 (LWP 17458) exited] [Thread 0x789e7effd6c0 (LWP 17290) exited] [Thread 0x789e7dffb6c0 (LWP 17292) exited] [Thread 0x789e7e7fc6c0 (LWP 17291) exited] [Thread 0x789e7f7fe6c0 (LWP 17289) exited] [Thread 0x789d7affd6c0 (LWP 17459) exited] [New Thread 0x789d7affd6c0 (LWP 17478)] [New Thread 0x789e7e7fc6c0 (LWP 17479)] [New Thread 0x789e7dffb6c0 (LWP 17480)] [New Thread 0x789d817fa6c0 (LWP 17523)] [New Thread 0x789e7f5fe6c0 (LWP 17526)] [New Thread 0x789e60b616c0 (LWP 17527)] [New Thread 0x789dd3fff6c0 (LWP 17528)] [New Thread 0x789dd37fe6c0 (LWP 17529)] [New Thread 0x789dd25a36c0 (LWP 17530)] [New Thread 0x789da7fff6c0 (LWP 17531)] [Thread 0x789e7ffff6c0 (LWP 17272) exited] [New Thread 0x789e7ffff6c0 (LWP 17533)] [Thread 0x789dfd7fa6c0 (LWP 17343) exited] [Thread 0x789dfe7fc6c0 (LWP 17341) exited] [Thread 0x789dfeffd6c0 (LWP 17340) exited] [Thread 0x789e24bfa6c0 (LWP 17337) exited] [Thread 0x789e26bfe6c0 (LWP 17333) exited] [Thread 0x789e31b696c0 (LWP 17329) exited] [Thread 0x789dfdffb6c0 (LWP 17342) exited] [Thread 0x789e60b616c0 (LWP 17527) exited] [Thread 0x789dd37fe6c0 (LWP 17529) exited] [Thread 0x789e7f5fe6c0 (LWP 17526) exited] [Thread 0x789e7e7fc6c0 (LWP 17479) exited] [Thread 0x789dd3fff6c0 (LWP 17528) exited] [Thread 0x789d817fa6c0 (LWP 17523) exited] [Thread 0x789e7dffb6c0 (LWP 17480) exited] [Thread 0x789d7affd6c0 (LWP 17478) exited] [Thread 0x789e4ffff6c0 (LWP 17315) exited] [Thread 0x789dfcff96c0 (LWP 17353) exited] [Thread 0x789e86bfe6c0 (LWP 17250) exited] [Thread 0x789e4aaef6c0 (LWP 17320) exited] [Thread 0x789da7fff6c0 (LWP 17531) exited] [Thread 0x789e4b2f06c0 (LWP 17319) exited] [Thread 0x789e4baf16c0 (LWP 17318) exited] [Thread 0x789e4c2f26c0 (LWP 17317) exited] [Thread 0x789dd25a36c0 (LWP 17530) exited] [Thread 0x789e613626c0 (LWP 17313) exited] [Thread 0x789e61b636c0 (LWP 17312) exited] [Thread 0x789e7d7fa6c0 (LWP 17310) exited] [Thread 0x789e623646c0 (LWP 17311) exited] [Thread 0x789e873ff6c0 (LWP 17249) exited] [Thread 0x789dd17fa6c0 (LWP 17365) exited] [Thread 0x789dd0ff96c0 (LWP 17364) exited] [Thread 0x789dff7fe6c0 (LWP 17339) exited] [Thread 0x789dfffff6c0 (LWP 17338) exited] [Thread 0x789e25bfc6c0 (LWP 17336) exited] [Thread 0x789e253fb6c0 (LWP 17335) exited] [Thread 0x789e263fd6c0 (LWP 17334) exited] [Thread 0x789e273ff6c0 (LWP 17332) exited] [Thread 0x789e30b676c0 (LWP 17331) exited] [Thread 0x789e313686c0 (LWP 17330) exited] [Thread 0x789e3236a6c0 (LWP 17328) exited] [Thread 0x789e32b6b6c0 (LWP 17322) exited] [Thread 0x789e87f23280 (LWP 17248) exited] [Thread 0x789e7ffff6c0 (LWP 17533) exited] [New process 17248] [Inferior 1 (process 17248) exited normally]
Sorry i don't speak German. What does it mean ? Perhaps you don't have a sudoer account on your computer? Mine is not Mint Linux, it's Kubuntu, but both are Ubuntu/Debian based with the same rules to switch a standard account with the admin rights. https://forums.linuxmint.com/viewtopic.php?t=352323 I tried to run the script without sudo on my computer, but the Linux security service denied this operation. Debugging an application remotely is a kind of hacker technics. Of course, here it's not the case (:=)))... Gilles Caulier
In your comment #20, there is nothing to see. All is fine. No crash. In the terminal #1, if you run "./squashfs-root/AppRun" without the "debug" argument, it's works ? Gilles Caulier
The .sh file has to be marked as „runable“, simmilar like to get an appimage to run. I don't know how to describe, but normaly Appimagelauncher does this automaticly with an appimage. For this try with the debug-appimage i didin't do this with appimagelauncher, i set this manualy as „runable“ ;-) Ahh, i think it's like chmod but with the mouse ;-) But as you see above, it worked now!!!
As in my comment in https://bugs.kde.org/show_bug.cgi?id=513837#c7 But the normal Appimage crashes. I'll try this, moment please ;-)
What do you mean ? Running the AppImage as usual (with debugging session) works fine. It's also the case with the Appimage without the debug symbols (no -debug suffix) ? Gilles Caulier
Yes it works. Without a crash. The debug-Appimage normaly startet crashes.
Both versions of the appimage crashes if i start them normaly.
I really like using Appimages because they are easy to use for the user. So far I haven't had any special incidents. However, I prefer to install apps natively via apt with .deb ;-)
It's crazy... Sound like a bug in the AppImage extraction engine. In the digiKam build process with package the bundle with the rolling release version of the AppImage tool binary. Perhaps there is a binary incompatibility here... Look here : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/appimage/04-build-appimage.sh?ref_type=heads#L640 In this part of the build script, we update the AppImage SDK only if the "functions.sh" script is not present on the VM. As i rebuild recently the whole AppImage system on the VM, the AppImage SDK have been updated. I do it every 6 month for security reasons, to have a clean build VM. I take a look to an older AppImage SDK : https://github.com/AppImageCommunity/pkg2appimage/commits/master/ The SDK have been updated in July. I'm sure that older AppImage VM was build before this date. Can can explain the problem. Gilles
We will see, i am not an expert. I would just like to point out the unusual behavior when starting the app images. Instead of opening the user interface in the middle of the screen, which is preset in the corresponding system settings as is usual for me, they were stuck to the left edge of the screen. By the way, this also happened when starting from the sqash directory, but in this case it had no consequences because the app remained stable. Of course I don't know if that could be relevant.
All my other Appimages i use, like Digikam 8.8 (till the weekly of 16.12. has done) start with its windows in the middle.
The non restored windows application is a recurrent problem with the KDE framework used in the background, as with digiKam. "Now, Plasma’s Wayland support isn’t perfect yet (any more than its X11 support was perfect). In particular, the two remaining major sources of complaints are window position restoring and headless RDP. We’re aware and working on solutions! I can’t make any promises about outcomes, but I can promise effort on these topics." source : https://pointieststick.com/2025/12/28/highlights-from-2025/
Git commit 626c8852be4160d23b86019ffe383063bb8a76b9 by Gilles Caulier. Committed on 29/12/2025 at 20:47. Pushed by cgilles into branch 'master'. Use older AppImageKit release to compile AppImage bundle under XUbuntu 22.04. We need to plan to use the new AppImageTool instead (https://github.com/AppImage/appimagetool/releases/tag/continuous) M +12 -2 project/bundles/appimage/04-build-appimage.sh A +- -- project/bundles/appimage/appimagekit/AppImageTool-x86_64.AppImage A +457 -0 project/bundles/appimage/appimagekit/functions.sh https://invent.kde.org/graphics/digikam/-/commit/626c8852be4160d23b86019ffe383063bb8a76b9
dk_nanodot@unbox.at I restored an older AppImageKit version, which is now obsolete officially, but working fine under XUbuntu 22.04, the Linux version used to compile the bundle for the binary compatibility. The AppImage 9.0.0 pre-release will be online in a few minute for testing... Best Gilles Caulier
Done. Please try file published just now (digiKam-9.0.0-20251229T180511-Qt6-x86-64.appimage) or one later Gilles Caulier
digiKam-9.0.0-20251229T180511-Qt6-x86-64.appimage I'm afraid to say it, but it crashes. I tried to start it twice. I had previously deleted the 8.8 app image and had caches etc. cleaned. When first started, Digikam stuck to the left edge of the monitor again. The second time it actually started in the middle of the screen. But in both attempts the program interface appeared as already described, the only change compared to previous attempts, the image previews are displayed (perhaps due to the successful starts from Squash?), Digikam crashed again after a few seconds. The time until the crash always seems to be similar. Interaction with the program interface was not possible with the mouse.
Is this the time after the T in the filename? I think i will try with the next version tomorrow again.
OK, just checked online again, the app image was from 2025-12-29 21:02. So it was probably the new one. That was a bit irritating.
Ok. The problem is not in the appimagekit. With the non-debug version, try to start the appimage as well (not the unpacked stuff), like this : QT_LOGGING_RULES="*=true" digiKam-9.0.0-20251229T180511-Qt6-x86-64.appimage If it's works, the trace on the console will be very verbose. I'm interested by this contains. If it do not works, i will need to change one line in the internal AppRun script and regenerate the bundle (tomorrow). Best regards Gilles Caulier
Do you use the Linux Mint Cinnamon or Xfce version ?
dk_nanodot@unbox.at I just installed a VM with Linux Mint 22.2 Cinnamon and downloaded the last 9.0.0 pre-release AppImage... Suspense... It works... Gilles Caulier
Created attachment 188071 [details] digiKam 9.0.0 pre-release AppImage starting properly under Linux Mint 22.2 VM
See the screencast attached to this report about digiKam 9.0.0 AppImage starting as expected under Linux Mint.
Maik, It's not at all an AppImage problem. I will revert my last commits. I suspect an OpenGL init : WebEngine or something else... Gilles
dk_nanodot@unbox.at Are you another application installed in native and using Qt 6.10.x ? Which GPU card did you use ? here in my VM no GPU emulated at all. Did you uses Wayland ? Typically no as LM is based on Ubuntu 24.04, but extra package can be installed after all. If yes, have you installed the X11-Wayland gateway (normally as we are in transition stage with Wayland, it's auto). Can you share your digikamrc configuration file. It's located in your home dir at $HOME/.config/digikamrc Gilles Caulier
Created attachment 188072 [details] Heutiger erster Versuch
Good morning Gilles, Appimage freshly downloaded, marked as executable, started. Program window on the left side of the screen. Surprisingly, Digikam remained stable and could be operated. The report: https://nowtransfer.de/fe164d91e6cc Started a second time, program window to the left again, crashed after a few seconds. The ending in the report is similar to that in previous attempts, see attached reports to the bug report or a little later. Shit, just realized I hadn't backed up the report :((( But the ending was identical to previous reports. I'll try it again right now.
dk_nanodot@unbox.at 2nd video a little bit longer with another start of digiKam, this time with one test album in the collection. All works as expected as you can see... https://imgur.com/a/doybMUb Gilles Caulier
Second start with crash ... https://nowtransfer.de/998b5293e264
I started digiKam plenty of time. No crash at not, problem is not reproducible on the VM. So i suspect the GPU/OpenGL support. Please respond to my Q from comment #45... Gilles
Maik, 1/ From the crash report we have : export QT_LOGGING_RULES="digikam*=true" /home/ua/Apps/digiKam-9.0.0-20251229T180511-Qt6-x86-64_bb3decbaad0b47281340a4228fd51b8d.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. -- to extract the bundle contents locally, use option '--appimage-extract' on the command line. awk: Kommandozeile:1: Warnung: Das Kommandozeilen-Argument »/etc/upstream-release« ist ein Verzeichnis: wird übersprungen awk: Kommandozeile:1: Warnung: Das Kommandozeilen-Argument »/etc/upstream-release« ist ein Verzeichnis: wird übersprungen -- Detected host Linux LinuxMint-64-22.2 The awk warnings from the AppRun bash script can have side effects. 2/ At end of the trace : Marble::GeoSceneSettings::setPropertyValue: GeoSceneSettings: Property "navigation" to false Digikam::ExifToolParser::exifToolAvailable: Check ExifTool availability: true Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 4129 Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 4029 Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::BuildTrashCountersJob(0x5a7f427a4960) time: 1773 Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::TagsJob(0x5a7f5b0b22a0) time: 1601 Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::DatesJob(0x5a7f5b121b20) time: 1625 Digikam::ItemMarkerTiler::slotSourceModelReset: ---- Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 1217 Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 1112 Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 1015 Marble::FileManagerPrivate::cleanupLoader: Finished loading all placemarks 1111 Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::AlbumsJob(0x5a7f5bcb45a0) time: 1778 Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::NewItemsFinder::slotStart: scan mode: ScanDeferredFiles /tmp/.mount_digiKaNp1Mcu/AppRun: Zeile 266: 10789 Speicherzugriffsfehler (Speicherabzug geschrieben) digikam $@ It sound like it crash in the database scan controller... Gilles
Sorry, I'm a bit overwhelmed with all the open windows on the desktop, the copying of texts and commands, then text into the translator, so only German to English so that you can understand me... A bit too much of everything ;-) System: AMD Ryzen 9 5900X, 64 Gb RAM Kernel: 6.8.0-90-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.4.8 tk: GTK v: 3.24.41 wm: Muffin v: 6.4.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.2 Zara base: Ubuntu 24.04 noble Machine: Type: Desktop Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0 serial: <superuser required> uuid: <superuser required> UEFI: American Megatrends LLC. v: A.N1 date: 09/22/2025 CPU: Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP smt: enabled arch: Zen 3+ rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB Speed (MHz): avg: 2715 high: 4950 min/max: 2200/3700 boost: enabled cores: 1: 2200 2: 2200 3: 3914 4: 3700 5: 4950 6: 2200 7: 2200 8: 3700 9: 2200 10: 3700 11: 2200 12: 2200 13: 2800 14: 3700 15: 2200 16: 2200 17: 2200 18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2200 24: 3517 bogomips: 177610 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia v: 550.163.01 arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1 bus-ID: 2d:00.0 chip-ID: 10de:1b81 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x1080 s-dpi: 97 s-size: 670x283mm (26.38x11.14") s-diag: 727mm (28.63") Monitor-1: HDMI-0 res: 2560x1080 hz: 60 dpi: 96 size: 677x290mm (26.65x11.42") diag: 736mm (29") modes: N/A API: EGL v: 1.5 hw: drv: nvidia nouveau drv: nvidia platforms: device: 0 drv: nvidia device: 1 drv: nouveau device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.163.01 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
dk_nanodot@unbox.at Perhaps you have a problematic file in your collection. 9.0.0 appimage is build now with _all_ digiKam dependencies updated (jpeg, png, heif, webp, tiff, libraw, ffmpeg, exiv2, exiftool, etc). Perhaps one lib dislike one file from your collection. Create a new fresh account, download the AppImage in the home dir, and run it from scratch. Add a new empty collection and fill it step by step, progressively with new files to see if crash is reproducible. Gilles Caulier
dk_nanodot@unbox.at You have 2 differents GPU on you computer ? one NVIDIA, one AMD ? Gilles Caulier
I also suspected the scan controller, but some of the early crash reports even came from situations where the scan hadn't started yet. After December 16th, we added to the scan controller a wildcard search for ignored directories. @dk_nanodot@unbox.at: Are you using any additional ignored directory entries? Maik
No, i have only one GPU installed. The Motherboared self has no GPU. Another small note about the respective program runs and crashes. After starting, the program window opens (on the left edge of the screen); you can see that a process is running because the fan is running faster. If the program remains stable, a message will appear at the bottom right that will start a scan for new images or something similar. The latter does not appear if the program crashes, so it crashes before this overlay appears at the bottom right! If the current Digikam weekly remained stable, then there were no error messages about any problems and the images could be opened normally in the preview etc. Digikam 8.8 until weekly on December 16th. have and had no problem with my pictures. Other programs also work with it without any problems. So far there has been no report about this.
I have no ignored Directorys in the Preferences.
dk_nanodot@unbox.at Please take a look also this FAQ, about the Software OpenGL rendering support: https://www.digikam.org/documentation/faq/#digikam-freezes-at-startup-with-or-without-main-window If this can help... Gilles Caulier
My digikam_systemrc in Home/config/ [System] disableOpenCL=false dnnOpenCLTested=true enableAIAutoTools=true enableAesthetic=false enableAutoTags=false enableDnnOpenCL=false enableFaceEngine=true enableHWTConv=true enableHWVideo=true enableLogging=false enableOpenCL=true facesEnginePath=/home/ua/.local/share/digikam/facesengine proxyAuth=false proxyPort=8080 proxyType=0 proxyUrl= softwareOpenGL=true useHighDpiPixmaps=false useHighDpiScaling=false videoBackend=ffmpeg
Nice : disableOpenCL=false ...and... enableOpenCL=true It must stay only one (:=)))... Remove the disable... one and set enable... one to false. Try again Gilles
digiKam-9.0.0-20251230T092056-Qt6-x86-64.appimage The new digikam_systemrc [System] dnnOpenCLTested=true enableAIAutoTools=true enableAesthetic=false enableAutoTags=false enableDnnOpenCL=false enableFaceEngine=true enableHWTConv=true enableHWVideo=true enableLogging=false enableOpenCL=false facesEnginePath=/home/ua/.local/share/digikam/facesengine proxyAuth=false proxyPort=8080 proxyType=0 proxyUrl= softwareOpenGL=true useHighDpiPixmaps=false useHighDpiScaling=false videoBackend=ffmpeg And the crash ;-) https://nowtransfer.de/57edfef41c07
I'm no longer available until the weekend. I wish you and all the developers of Digikam a happy New Year and a Happy New Year!!!
Happy new year too. It's clear : Digikam::ActionThreadBase::cancel: Cancel Main Thread Digikam::ActionThreadBase::slotJobFinished: One job is done Digikam::AlbumsJob(0x5f9fc435b000) time: 1826 Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::FaceDb::setting: FaceDB SelectFaceSetting val ret = 0 Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::ActionThreadBase::cancel: Finish Main Thread Digikam::NewItemsFinder::slotStart: scan mode: ScanDeferredFiles /tmp/.mount_digiKautedDX/AppRun: Zeile 266: 23265 Speicherzugriffsfehler (Speicherabzug geschrieben) digikam $@ The crash appears while scanning collection in the background. Sounds like a problematic file to parse. Did you operate my tips from the comment #53 ? Best regards Gilles Caulier
I don't believe the problem lies with the Collection Scanner, as logs have already been posted where the scan hasn't even started. It also doesn't align with the observation regarding the window position when the problem occurs. We need a backtrace; anything else is just guesswork. Maik
Please set this value to false: softwareOpenGL=false Maik
Good morning and happy new year, Since I just had some time, I wanted to share the following test results. Digikam Appimage was installed in a recent weekly on an older computer (MacPro 8-core, 2008, old GPU) under LinuxMint 21.3 Cinnamon, which had been used there for a long time. There, too, the program window stuck to the left edge of the screen after starting. Even after several starts, the program remained stable enough that I no longer had to uninstall it and use it generally. The images managed on the older computer are a mirror of the image data on the computer, which is descriped plagued by digicam. Before I tried Digikam on the older computer as described, I manually created a completely new mirroring of the data (i.e. no pure overwriting of image data!). It was noticed that during the copying process a message appeared asking whether a file should be overwritten with a more recent one. These two affected files were actually in one directory and identical versions of an image with the same file name, but one with .JPG and one with .jpg as the file extension. The problem was solved quickly. But since Digikam weekly runs until December 16th. As well as the stable version up to 8.8, neither this nor the old computer previously caused any problems, so I am currently assuming that the pictures in my collection are in order so far. The problem described with the newer weeklys currently still exists on the newer computer, as already described several times.
>The problem described with the newer weeklys currently still exists on the newer computer, as already described several times. As Maik said previously, the only way to identify where is the problem here is to get a GDB backtrace with current AppImage pre-release bundle 9.0.0. Best regards Gilles Caulier
Today, the current weekly app image was downloaded and started for testing: Digikam application window sticks to the left, then crashes. Deinstalled. Then downloaded and started the Digikam debug app image: 1st start attempt, window on the left, scan with display at the bottom right is carried out, Digikam remains stable. The program is operated somewhat with the mouse. Finished again without any problems. 2nd start attempt, window opens in the middle of the screen, otherwise like 1st start attempt. 3rd start attempt, window opens on the left again, otherwise like 1st start attempt. 4. Attempt to start, window opens again on the left, program crashes. Previous debug reports failed to detect anything problematic as the debug version started in the squash directory remained stable. Mentioned again, even under LinuxMint 21.3 the program window was stuck on the left. I had this behavior not until version 16.12. and cannot be observed with all previously used weekly and stable. I honestly don't have time to help anymore. Job comes first. The stable version 8.8 continues to run well for now.