https://bugs.kde.org/show_bug.cgi?id=373284
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=373284
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||6.0.0
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=373284
Ritesh Raj Sarraf changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=373284
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|general |Portability
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #11 from Ritesh Raj Sarraf ---
As for the initial crash, for which the steps to reproduce I have, I'm not sure
if I have a better trace. It looks like Debian doesn't have the necessary
dbgsym symbols packaged. :-(
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #10 from Ritesh Raj Sarraf ---
I'm not sure if I have clear steps to reproduce, for this crash [1]. But, now
I've installed some more debug packages. If the crash occurs again, and I have
a better trace, I'll share
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #9 from caulier.gil...@gmail.com ---
Can you run digiKam in GDB from a console as explained here :
https://www.digikam.org/contrib
The current backtrace do not indicate where it crash exactly.
Q : Which video card driver do you use ?
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #8 from Ritesh Raj Sarraf ---
No. I'm still on Xorg.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #7 from caulier.gil...@gmail.com ---
Do you use Wayland instead X11 on your system ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #6 from Ritesh Raj Sarraf ---
I got one more crash, just now, in a different subsystem. In case you need the
full report, let me know. I have it locally.
ProcStatus:
Name: digikam
Umask: 0022
State: S
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #5 from Ritesh Raj Sarraf ---
By the way, I'm seeing this not just with Album deletion, but also with
deleting Tags through Tag Manager.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #4 from Ritesh Raj Sarraf ---
Yes. You seem to be correct. On another machine, with the same digikam
packages, I am not able to reproduce the issue with the same steps.
On the other hand, I removed the collection,
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #3 from caulier.gil...@gmail.com ---
So, it's not a BC issue with Qt5.
I suspect now a database failure or a wrong application setting.
Now, please create a new account, import your collection, creating a new
database (in a different place
https://bugs.kde.org/show_bug.cgi?id=373284
--- Comment #2 from Ritesh Raj Sarraf ---
Hello Gilles,
Yes. I was able to crash the AppImage build too.
digikam.iojob: DTrash: Image album root path:
"/media/SSHD/rrs-home/Data/Pictures/Digikam Managed"
digikam.iojob: Trash
https://bugs.kde.org/show_bug.cgi?id=373284
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
15 matches
Mail list logo