Hi Steve,
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: 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
12 -- pid=1073797
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 = 1073797
KCrash: Arguments: /usr/bin/digikam
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
[2]+ Stopped digikam
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
Am Montag, 1. Mai 2023, 08:21:12 CEST schrieb Steve Robbins:
> I’ve just uploaded new version with upstream patch for the splash screen.
> Would love to know I how it works on your system.
>
> Sent from my iPhone
>
> > 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 iPhone
> >
> >>> On 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),
> >> > > 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/28977ed2aac8a3575b979725
> >> e3141dd94b104833
> >>
> >> to the Debian package. I can test if it fixes the problem for me.
> >>
> >> Thanks
> >> Rainer
> >>
> >> --
> >> Rainer Dorsch
> >> http://bokomoko.de/
--
Rainer Dorsch
http://bokomoko.de/
