On Sunday, August 27, 2023 12:43:31 P.M. CDT Karine Crèvecœur wrote:
> (gdb) disassemble
>…
>0x76cc20e8 <+136>: movaps %xmm8,%xmm4
>0x76cc20ec <+140>: mov%edx,-0x4c(%rsp)
>0x76cc20f0 <+144>: mov0x38(%r9),%rdx
>0x76cc20f4 <+148>:
Hello Rainer,
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 wrote:
> Comment 35 in upstream bugreport:
>
>
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
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
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
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:
>
clone 1028507 -1
retitle -1 Create face-recognition data package
thanks
On Tuesday, July 18, 2023 5:38:21 A.M. CDT Gregor Riepl wrote:
> Would it be possible to create a separate Debian package with this data
> and add it as a Recommends: dependency?
Yes, and thanks for the reminder. The
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
forwarded 1028507 https://bugs.kde.org/show_bug.cgi?id=438317
thanks
On Thu, 12 Jan 2023 06:24:07 +0100 Christoph Anton Mitterer
wrote:
> Every time when starting digikam, a dialog pops up asking to download
> some engines for redeye removal and face detection from the internet,
> which would
Severity: normal
thanks
On Tue, 25 Apr 2023 22:49:03 -0500 Steven Robbins wrote:
> Given that no-one else has reported this,
> I'm leaning towards downgrading the severity to keep digikam in the upcoming
> release.
Setting severity to normal. If anyone reading this has encountered
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
>
Hi Rainer,
On Sun, 16 Apr 2023 09:38:07 +0200 Rainer Dorsch wrote:
> Let me elaborate a somewhat:
>
> The spash screen bug I found is visible in the backtrace in comment 5:
>
> https://bugs.kde.org/show_bug.cgi?id=466170#c5
>
> According to Maik, the bug is triggered by a race condition
Just a note to say that I have used a Debian "testing" chroot environment and
can reproduce the reported crash. I will be investigating more in the coming
days.
-Steve
signature.asc
Description: This is a digitally signed message part.
___
On Fri, 14 Apr 2023 14:24:31 +0200 Rainer Dorsch wrote:
> Thanks Marco, that is a good link.
>
> I provided a backtrace and upstream acknowledged the bug to be fixed in
8.1.0:
Hello Rainer,
I've looked at the upstream bug, and all the information you provided. That's
awesome -- I wish that
On Sunday, November 27, 2022 3:49:18 P.M. CST you wrote:
> Package: digikam
> Version: 4:7.7.0-3+b1
> Severity: normal
>
> Dear Maintainer,
>
> Would be nice to ave this version in bookworm
Will certainly get a new version into bookworm. It looks like there will be a
7.9.0 in the next week
Building with recent gcc fails due to symbols file issues; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012920
Can someone help? I have no idea how to manipulate symbols files.
Thanks,
-Steve
signature.asc
Description: This is a digitally signed message part.
On Thursday, July 21, 2022 11:24:03 A.M. CDT Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > severity 1004769 important
>
> Bug #1004769 [src:digikam] Video support missing (FTBFS with ffmpeg 5.0)
> Severity set to 'important' from 'serious'
I had
On Sunday, July 17, 2022 4:09:20 A.M. CDT you wrote:
> Le 16/07/2022 à 18:50, Steven Robbins a écrit :
> > I would say that there may well be others in your situation so if you do
> > find a method please report back to this bug.
>
>For my personnal use, until upstream p
On Monday, July 11, 2022 1:38:31 A.M. CDT Christian Marillat wrote:
> After a rebuild under pbuilder, I confirm that libheif-dev is missing
> from Build-Depends. Adding libheif-dev in Build-Depends fix this issue.
Thank you for debugging this. I have uploaded -2 with the added build-
depends.
On Monday, July 11, 2022 1:02:23 A.M. CDT you wrote:
> (The more problems I see related to major library upgrades in debian,
> the less convinced I am that only supporting a single (major) version
> for all libraries really is a good idea. Then I again I am not the one
> doing the work, so I am
On Saturday, July 9, 2022 8:26:21 A.M. CDT Christian Marillat wrote:
> Package: digikam
> Version: 4:7.7.0-1
> Severity: normal
>
> Dear Maintainer,
>
> Since the last version .heic files aren't
> displayed correctly. See attached screen capture.
I agree that does look odd. Can you share the
On Thursday, June 16, 2022 2:06:04 P.M. CDT Vincent Danjean wrote:
> According to the answer, this bug is already fixed in 7.7.0.
Digikam 7.7.0 was uploaded to Debian a few days ago; closing bug.
-Steve
signature.asc
Description: This is a digitally signed message part.
control: severity -1 normal
On Fri, 25 Feb 2022 22:55:12 +0100 Sebastian Ramacher
wrote:
> On 2022-02-21 16:05:37 -0600, Steven Robbins wrote:
> > On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher
> > wrote:
> > > Source: digikam
> > > Version: 4:7.1.
On Saturday, April 23, 2022 7:23:48 A.M. CDT Hoareau Jean Pierre wrote:
> Package: digikam
> Version: 4:7.6.0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> I installed Debian "Bookworm" in order to test this version. When launching
> "Digikam" I get a
On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher
wrote:
> Source: digikam
> Version: 4:7.1.0-2
I have just uploaded Digikam 7.5.0 to unstable. If you have a chance to re-
try the build, would appreciate knowing if it now builds with new ffmpeg.
Thanks,
-Steve
signature.asc
Description:
On Mon, 03 May 2021 14:54:07 +0200 Philipp Marek
wrote:
> Package: digikam
> Version: 4:7.1.0-2
> Severity: normal
> X-Debbugs-Cc: phil...@marek.priv.at
>
> Just "apt-get install digikam -t testing" doesn't work - libcharls2 is
> left at 2.0.0+dfsg-1, but this digikam needs at least
On Tuesday, August 24, 2021 4:32:33 A.M. CDT Alain Bertrand wrote:
>
> Launching digikam
> digikam: symbol lookup error:
> /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol:
> FT_Palette_Select and digikam exits
I have not encountered this myself.
A quick google suggested
Hello!
On Wednesday, January 6, 2021 3:05:38 P.M. CST R. Lemos wrote:
> In /usr/lib/x86_64-linux-gnu/libopencv_dnn.so.4.5.1 I've found a
> symbol `_ZN2cv3dnn14dnn4_v202011173NetC1Ev`. It differs from expected
> `_ZN2cv3dnn14dnn4_v202009083NetC1Ev` on `...20201117...` (expected
>
On Wednesday, January 6, 2021 12:43:52 P.M. CST R. Lemos wrote:
> Package: digikam
> Version: 4:7.1.0-1+b1
> Severity: normal
>
> The program crashes with message
>
> > digikam: symbol lookup error: /usr/lib/digikam/libdigikamcore.so.7.1.0:
> > undefined symbol:
On Wednesday, August 19, 2020 9:03:03 A.M. CDT Pino Toscano wrote:
> In data mercoledì 19 agosto 2020 15:38:46 CEST, Steven Robbins ha scritto:
> > On Wednesday, August 19, 2020 5:48:50 A.M. CDT Pino Toscano wrote:
> > > Hi Steve,
> > >
> > > Can you please not
On Wednesday, August 19, 2020 5:48:50 A.M. CDT Pino Toscano wrote:
> Hi Steve,
>
> Can you please not upload binaries, and do source-only uploads?
I was under the impression that a new source tarball required a binary upload.
I'll certainly do a source-only when transition to unstable.
Right
On Wed, 04 Sep 2013 14:29:04 +0200 Johannes Rohr wrote:
> Package: digikam
> Version: 4:3.1.0-4
> Severity: normal
>
> Digikam saves the mysql password in ~/.kde/share/config/digikamrc. Instead it
should be stored securely in kdewallet
>
Confirmed that the issue remains in Digikam 7.0.0
Hello Christoph,
As discussed in the bug, both Augustin and I have failed to reproduce your
symptoms. I noticed yesterday that you use a different locale than I, so I am
wondering whether that is part of the issue.
On Sun, 16 Apr 2017 15:44:44 +0200 Christoph Anton Mitterer
wrote:
>
Eric,
Thank you for the bug report. Per your question: I do indeed test before
uploading -- I've been using Digikam 7 since I uploaded last week.
On Monday, February 24, 2020 4:38:40 A.M. CST Eric Valette wrote:
> valette@tri-yann4:~$ digikam --version
> digikam: error while loading shared
On Monday, February 10, 2020 7:08:17 P.M. CST Christoph Anton Mitterer wrote:
> On Mon, 2020-02-10 at 12:56 +0100, Agustin Martin wrote:
> > Triaging some Debian bugs. Tried to reproduce this problem with
> > digikam
> > 4:6.4.0+dfsg-2 (currently in sid) but switching maps seems to work.
> > Is
36 matches
Mail list logo
