Now that 8.3.0-2 has landed in testing, I can confirm that the bug
has been fixed.
Thanks, Detlef
On 19.08.23 22:00, Steven Robbins wrote:
1. Test a build without SSE4.
I built 8.1.0-2 from sources (which took 70 minutes on my machine,
btw), removed the version from "sid" that I had installed the other day
and then did:
root@fluke:~# dpkg -i digikam_8.1.0-2_amd64.deb
On Saturday, August 19, 2023 11:53:35 A.M. CDT you wrote:
>Hi Steve,
>
>I'm afraid, it doesn't prevent digikam from crashing.
>
>Here is what I did (after fetching the latest updates from "testing" this
> morning):
[ ... ]
>Not sure if my approach is the preferred way to test
Hi Steve,
I'm afraid, it doesn't prevent digikam from crashing.
Here is what I did (after fetching the latest updates from "testing" this
morning):
root@fluke:/etc/apt# sed -i 's/trixie/sid/' sources.list
root@fluke:/etc/apt# apt-get update
Get:1 http://ftp.de.debian.org/debian sid
On Monday, August 14, 2023 8:52:14 A.M. CDT Steven Robbins wrote:
> So I'm back to square 1, very confused by your crash.
I have made a change to digikam and uploaded 8.1.0-3 last night. It should
avoid calling SSE 4 functions if only SSE 2 is detected. I'd appreciate if
you could try it
On Monday, August 14, 2023 1:25:23 A.M. CDT Detlef Matthiessen wrote:
>Hi Steve,
>
>right after I replied to the bug report, I noticed:
>
> dm@fluke:/tmp$ diff test-no-sse4 test-sse4
> dm@fluke:/tmp$
>
>Can you confirm that the attached binaries are identical?
Nice catch. They are
Hi Steve,
dm@fluke:/tmp$ g++ matrixtest.cc -I /usr/include/x86_64-linux-gnu/qt5 -msse2
-msse4.1 -fPIC -lQt5Core
dm@fluke:/tmp$ ./a.out
Hello
Hm.
Just to be sure, I also ran the attached executables, however they are giving
me the same result:
dm@fluke:/tmp$ ./test-sse4
Hello
Hi Steve,
On 13.08.23 00:05, Steven Robbins wrote:
There must be more than this? Normally a backtrace shows a number of stack frames. Did
you type "bt" in the gdb propmpt after the crash?
Sorry, missed that part. My bad.
Program received signal SIGILL, Illegal instruction.
On Sun, 30 Jul 2023 07:27:51 +0200 Detlef Matthiessen
wrote:
>
>Hi Steve,
>
>I've got:
>
> Program received signal SIGILL, Illegal instruction.
> 0x76cc20d3 in operator* (m1=..., m2=...) at
> /usr/include/x86_64-linux-gnu/qt5/
QtGui/qmatrix4x4.h:642
> Downloading source file
On Sun, 30 Jul 2023 10:22:19 +0200 Detlef Matthiessen
wrote:
> On 30.07.23 07:45, Detlef Matthiessen wrote:
> > 642QMatrix4x4 m = m1;
>
>On a related note: a quick search for "digikam" and "642" yields the
following bug report:
>
On 30.07.23 07:45, Detlef Matthiessen wrote:
642 QMatrix4x4 m = m1;
On a related note: a quick search for "digikam" and "642" yields the
following bug report:
https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/2000718
https://bugs.kde.org/show_bug.cgi?id=465548
Admittedly,
On 30.07.23 07:27, Detlef Matthiessen wrote:
Program received signal SIGILL, Illegal instruction.
0x76cc20d3 in operator* (m1=..., m2=...) at
/usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:642
Downloading source file /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
642
Hi Steve,
I've got:
Program received signal SIGILL, Illegal instruction.
0x76cc20d3 in operator* (m1=..., m2=...) at
/usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:642
Downloading source file /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h
642
On Thursday, July 27, 2023 3:23:07 A.M. CDT Detlef Matthiessen wrote:
> after updating digikam from 7.9.0-2 to 8.1.0-2, it crashes almost instantly:
> dm@fluke:~$ digikam
> Illegal instruction
>
> (...)
>
> If you need more information, please let me know.
Thanks -- we'll need a backtrace from
Package: digikam
Version: 4:8.1.0-2
Severity: important
Dear Maintainer,
after updating digikam from 7.9.0-2 to 8.1.0-2, it crashes almost instantly:
dm@fluke:~$ digikam
Illegal instruction
The CPU I'm running this on is a rather old Quad Core:
dm@fluke:~$ lscpu
Architecture:x86_64
15 matches
Mail list logo
