Bug#1034310: digikam crashes after upgrade from bullseye to bookworm
Rainer Dorsch
Version: 4:7.9.0-1+b2
Severity: grave
Dear Maintainer,
after the upgrade from bullseye to bookworm, digikam does not start anymore, but crashes on startup.
I put the severity to grave, since I cannot judge how many users would be affected after an upgrade. Feel free to downgrade the bug report if there is any evidence, that only few users are affected.
I logged the output when starting digikam. First it stops itself, then it aborts:
rd@h370:~$ digikam > digikam.log 2>&1
[1]+ Stopped digikam > digikam.log 2>&1
rd@h370:~$ fg
digikam > digikam.log 2>&1
Aborted (core dumped)
rd@h370:~$
The (uncompressed) digikam.log is huge, therefore I made it available here:
https://bokomoko.de/~rd/Debian/digikam.log.xz
It might be that it is a side effect of the upgrade, but at least for apt the system looks ok
root@h370:~# apt full-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
root@h370:~#
and after very initial testing I have not seen other issues in the system.
If you need anything more, please let me know.
Thanks
Rainer
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages digikam depends on:
ii digikam-data 4:7.9.0-1
ii digikam-private-libs 4:7.9.0-1+b2
ii libc6 2.36-8
ii libgcc-s1 12.2.0-14
ii libkf5configcore5 5.103.0-1
ii libkf5coreaddons5 5.103.0-1
ii libkf5i18n5 5.103.0-1
ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.6
ii libqt5core5a 5.15.8+dfsg-3
ii libqt5gui5 5.15.8+dfsg-3
ii libqt5sql5 5.15.8+dfsg-3
ii libqt5sql5-mysql 5.15.8+dfsg-3
ii libqt5sql5-sqlite 5.15.8+dfsg-3
ii libqt5widgets5 5.15.8+dfsg-3
ii libstdc++6 12.2.0-14
ii perl 5.36.0-7
Versions of packages digikam recommends:
ii chromium [www-browser] 112.0.5615.49-2
ii ffmpegthumbs 4:22.12.3-1
ii firefox-esr [www-browser] 102.9.0esr-2
ii konqueror [www-browser] 4:22.12.3-1
ii lynx [www-browser] 2.9.0dev.12-1
Versions of packages digikam suggests:
ii breeze-icon-theme 4:5.103.0-1
pn digikam-doc <none>
ii systemsettings 4:5.27.2-1
-- no debconf information
Rainer Dorsch
I provided a backtrace and upstream acknowledged the bug to be fixed in 8.1.0:
Am Freitag, 14. April 2023, 13:33:51 CEST schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=466170
>
> --- Comment #6 from Maik Qualmann <metzp...@gmail.com> ---
> Thanks for the interesting backtrace. We have had these strange crashes in
> connection with the splash screen before, especially with macOS. It's a race
> condition. I'll fix it tonight. The patch will only be officially included
> in digiKam-8.1.0. Alternatively, you could already test it by setting the
> entry "Show Splash=true" to "Show Splash=false" in the digikamrc.
>
> Maik
--
Rainer Dorsch
http://bokomoko.de/
Steven Robbins
> Thanks Marco, that is a good link.
>
> I provided a backtrace and upstream acknowledged the bug to be fixed in
8.1.0:
I've looked at the upstream bug, and all the information you provided. That's
awesome -- I wish that every bug submitter would be as thorough as you!
It seems that, even with disabling the splash screen, you still experience the
bug -- is that correct?
I can say that I'm not experiencing any such crash. I created a new user to
test from scratch. I see the splash screen come and go, then the pop-up that
offers to download the faces data files. I can download them or not and it all
works fine either way.
So it's puzzling. I'm also using an x64 system, but I run on the "sid/
unstable" distribution so I have slightly different versions of the dependency
packages. Maybe it's worth attempting an upgrade of some or all of these to
see if the problem goes away?
Perhaps start with libkf5configcore5, since the failing assert seems to be in
that library:
qt_assert_x(char const*, char const*, char const*, int) () at /lib/
x86_64-linux-gnu/libQt5Core.so.5
Here is the list from my system today.
Versions of packages digikam depends on:
ii digikam-data 4:7.9.0-1
ii digikam-private-libs 4:7.9.0-1+b2
ii libgcc-s1 12.2.0-14
ii libkf5configcore5 5.103.0-2
ii libkf5i18n5 5.103.0-1
ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.6
ii libqt5gui5 5.15.8+dfsg-7
ii libqt5sql5 5.15.8+dfsg-7
ii libqt5sql5-mysql 5.15.8+dfsg-7
ii libqt5sql5-sqlite 5.15.8+dfsg-7
ii libqt5widgets5 5.15.8+dfsg-7
ii perl 5.36.0-7
Versions of packages digikam recommends:
ii ffmpegthumbs 4:22.12.3-1
ii firefox-esr [www-browser] 102.10.0esr-1
ii google-chrome-stable [www-browser] 112.0.5615.121-1
ii lynx [www-browser] 2.9.0dev.12-1
Versions of packages digikam suggests:
ii breeze-icon-theme 4:5.103.0-1
pn digikam-doc <none>
ii systemsettings 4:5.27.2-1
-Steve
Rainer Dorsch
Hi Steve,
Am Mittwoch, 26. April 2023, 05:49:03 CEST schrieben Sie:
> On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
> > Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
> > > I'd be interested to know if the issue persists on your system after
> > > upgrading.
> >
> > Yes, it repros always.
>
> OK.
>
> > -- System Information:
> > Debian Release: 12.0
> >
> > APT prefers testing-security
> > APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105,
> >
> > 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> > LANGUAGE=de:en_US
>
> I'm still not able to reproduce the issue. Today I was trying with the same
> locale as you (de_DE.UTF-8). I have seen issues in the past with certain
> locales -- typically in software that isn't careful enough and gets into
> trouble when a locale switches the period and comma in number formats.
Be aware that upstream also was unable to repro the issue and finally they managed to understand and fix the problem by the traces I was able to generated.
> Even though I wasn't able to reproduce the problem here, it would be
> interesting if you can try with locale set to en_US for example:
There is no change if I unset LANG:
rd@h370:~/tmp.nobackup$ unset LANG
rd@h370:~/tmp.nobackup$ digikam
digikam.facedb: Cannot found faces engine model "shapepredictor.dat"
digikam.facedb: Faces recognition feature cannot be used!
digikam.facedb: Cannot found faces engine DNN model "openface_nn4.small2.v1.t7"
digikam.facedb: Faces recognition feature cannot be used!
kf.xmlgui: Unhandled container to remove : Digikam::DigikamApp
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 363
21 -- exe=/usr/bin/digikam
13 -- platform=xcb
11 -- display=:0
16 -- appname=digikam
17 -- apppath=/usr/bin
9 -- signal=6
11 -- pid=459194
17 -- appversion=7.9.0
20 -- programname=digiKam
31 -- bugaddress=sub...@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = digikam path = /usr/bin pid = 459194
KCrash: Arguments: /usr/bin/digikam
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
[1]+ Stopped digikam
rd@h370:~/tmp.nobackup$
> I have no idea where else to look. Given that no-one else has reported
> this, I'm leaning towards downgrading the severity to keep digikam in the
> upcoming release.
That is certainly and option. For me as a user it would be helpful if you would highlight in the changelog that I get during the upgrade the information to disable the splash screen if they run into this issue.
Alternatively you could apply the bugfix
https://invent.kde.org/graphics/digikam/-/commit/28977ed2aac8a3575b979725e3141dd94b104833
to the Debian package. I can test if it fixes the problem for me.
Thanks
Rainer
Steve Robbins
On Apr 26, 2023, at 8:24 AM, Steve Robbins <st...@sumost.ca> wrote:
I understood that upstream fixed a splash screen bug from your traces. I do plan to look into applying that patch.But I thought that even after disabling the splash screen you were seeing a second crash? That is what I’m trying to figure out.Sent from my iPhoneOn Apr 26, 2023, at 1:24 AM, Rainer Dorsch <m...@bokomoko.de> wrote:
Hi Steve,
Am Mittwoch, 26. April 2023, 05:49:03 CEST schrieben Sie:
> On Tuesday, April 25, 2023 12:50:39 P.M. CDT Rainer Dorsch wrote:
> > Am Dienstag, 25. April 2023, 03:51:44 CEST schrieben Sie:
> > > I'd be interested to know if the issue persists on your system after
> > > upgrading.
> >
> > Yes, it repros always.
>
> OK.
>
> > -- System Information:
> > Debian Release: 12.0
> >
> > APT prefers testing-security
> > APT policy: (500, 'testing-security'), (500, 'testing-debug'), (105,
> >
> > 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 6.1.0-7-amd64 (SMP w/6 CPU threads; PREEMPT)
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
Rainer Dorsch
many thanks for applying the patch. I reenabled the splash screen in digikamrc
and it seems to crash at the same location again:
rd@h370:~$ apt-cache policy digikam
digikam:
Installed: 4:7.9.0-2
Candidate: 4:7.9.0-2
Version table:
*** 4:7.9.0-2 100
100 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
4:7.9.0-1+b2 500
500 http://ftp-stud.hs-esslingen.de/debian bookworm/main amd64
Packages
rd@h370:~$ digikam
digikam.facedb: Faces recognition feature cannot be used!
digikam.facedb: Cannot found faces engine DNN model
"openface_nn4.small2.v1.t7"
digikam.facedb: Faces recognition feature cannot be used!
kf.xmlgui: Unhandled container to remove : Digikam::DigikamApp
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h,
line 363
21 -- exe=/usr/bin/digikam
13 -- platform=xcb
11 -- display=:0
16 -- appname=digikam
17 -- apppath=/usr/bin
9 -- signal=6
20 -- programname=digiKam
31 -- bugaddress=sub...@bugs.kde.org
KCrash: crashing... crashRecursionCounter = 2
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
rd@h370:~$
I will create a trace and append it to the upstream bugreport:
https://bugs.kde.org/show_bug.cgi?id=466170
Thanks again
Rainer
Steven Robbins
thanks
On Tue, 25 Apr 2023 22:49:03 -0500 Steven Robbins <st...@sumost.ca> wrote:
> Given that no-one else has reported this,
> I'm leaning towards downgrading the severity to keep digikam in the upcoming
> release.
please reply to let us know.
-Steve
Steven Robbins
Debian now has 8.1.0 uploaded to testing. I'm wondering if you can test that
and report back whether the issue persists or not.
Thanks,
-Steve
On Mon, 01 May 2023 23:37:00 +0200 Rainer Dorsch <m...@bokomoko.de> wrote:
> Comment 35 in upstream bugreport:
>
> https://bugs.kde.org/show_bug.cgi?id=466170#c35
>
> Thanks for the backtrace, the problem in slotEmptyMessageTimer() is known
and
> was fixed about 5 months ago. We seem to have forgotten the backport to
> digiKam-7.x.x when I look at the history. Only with digiKam-8.0.0 will the
> problem no longer occur.