[digikam] [Bug 422345] libQT5WebEngine crash

2021-12-13 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=422345

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||7.5.0
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #19 from Maik Qualmann  ---
Thanks for the feedback.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2021-12-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #18 from aymeric.rat...@gmail.com ---
I checked with version 7.4 and no more issue, very stable. Ticket can be
closed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2021-12-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|7.0.0   |7.2.0

--- Comment #17 from caulier.gil...@gmail.com ---
Americ, 

Stable digiKam 7.4.0 AppImage is published. Please check if problem is
reproducible.

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2021-07-19 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #16 from caulier.gil...@gmail.com ---
With next digiKam 7.4.0 release, AppImage bundle is compiled using a more
recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used.
ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and
video formats.

https://i.imgur.com/XV1tZkL.png

Please check if problem still reproducible with this version available as
pre-release here:

https://files.kde.org/digikam/

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2021-04-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #15 from aymeric.rat...@gmail.com ---
With digiKam-7.2.0-x86-64-debug.appimage, I have :

Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default
sRGB ICC profile.
unknown: End Of Image  ( 1 )
Digikam::StackedView::setViewMode: Stacked View Mode :  1
[New Thread 0x7fff64ff9700 (LWP 1939)]

Thread 12 "ThreadPoolForeg" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff9e7fc700 (LWP 20499)]
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65  ../sysdeps/x86_64/multiarch/strlen-avx2.S: Aucun fichier ou dossier de
ce type.
(gdb) bt
#0  0x73a2b181 in __strlen_avx2 () at
../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x77dc3799 in  () at /lib/x86_64-linux-gnu/libudev.so.0
#2  0x77dc3931 in  () at /lib/x86_64-linux-gnu/libudev.so.0
#3  0x77dc3aac in  () at /lib/x86_64-linux-gnu/libudev.so.0
#4  0x77dc5ca3 in udev_device_get_subsystem () at
/lib/x86_64-linux-gnu/libudev.so.0
#5  0x7fffe2a1e903 in udev_monitor_receive_device () at
/tmp/.mount_digiKaern6cF/usr/lib/libudev.so.1
#6  0x7fffe796ba62 in  () at
/tmp/.mount_digiKaern6cF/usr/lib/libQt5WebEngineCore.so.5
#7  0x7fff840029c0 in  ()
#8  0x7fff9e7fb410 in  ()
#9  0x7fff90001cc8 in  ()
#10 0x in  ()

I will switch to Bullseye, so many it will disappear with newer version of QT

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2021-03-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #14 from caulier.gil...@gmail.com ---
digiKam 7.2.0 official release is published with more than 360 files closed
from bugzilla:

https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/

Can you reproduce the dysfunction with this version ?

Thanks in advance for your feedback

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-07-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #13 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #12 from aymeric.rat...@gmail.com ---
Created attachment 130128
  --> https://bugs.kde.org/attachment.cgi?id=130128=edit
trace 20200713

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #11 from aymeric.rat...@gmail.com ---
Hi,

Seems overall more stable but I could still encounter same bug, randomly.
I uploaded latest trace.
command:
./digikam-7.0.0-20200713T054546-x86-64-debug.appimage  debug > debugtrace.txt

Aymeric

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #10 from caulier.gil...@gmail.com ---
Hi,

Can you check if this crash still exist with last weekly AppImage build
available here :

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #9 from caulier.gil...@gmail.com ---
Note : I'm surpized to see Qt 5.11.3 version, as i ported DK AppImage to last
5.14.2.

Please try with last weekly bundle available here :

https://files.kde.org/digikam/

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #8 from caulier.gil...@gmail.com ---
Hi,

Yes, you can report this dysfunction to Qt team.

Check well if no other one file already exists on this topic. If yes, just
append a comment with a link to this entry.

Best

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #7 from aymeric.rat...@gmail.com ---
a echo $XDG_SESSION_TYPE returns x11, so not wayland
Should I report this bug to QT ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-27 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=422345

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #6 from Maik Qualmann  ---
Well, there is nothing we can do about a crash within QWebEngine. The function
"udev_device_get_subsystem()" probably returns an empty string in your system.
Which then leads to a crash. Do you use Wayland in Debian?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-27 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #5 from aymeric.rat...@gmail.com ---
Did I provide enough information ?
If not, please be more detailed on the procedure, I think I followed
instructions as document.
Regards
Aymeric

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #4 from aymeric.rat...@gmail.com ---
Created attachment 129016
  --> https://bugs.kde.org/attachment.cgi?id=129016=edit
console trace

shell command:
./digikam-7.0.0-rc-20200601T143303-x86-64-debug.appimage debug > debugtrace.txt

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #3 from caulier.gil...@gmail.com ---
No more suitable information.

Can you give me the full backtrace from the console, including all command
lines used to run digiKam ?

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

--- Comment #2 from aymeric.rat...@gmail.com ---
Is it better like this ?:


... many  (too many) RST like this (relatively new behavior)
unknown: RST3  ( 3 )
unknown: RST4  ( 3 )
unknown: RST5  ( 3 )
unknown: RST6  ( 3 )
unknown: RST7  ( 3 )
unknown: RST0  ( 3 )
unknown: RST1  ( 3 )
unknown: RST2  ( 3 )
unknown: End Of Image  ( 1 )
Digikam::ItemLister::listImageTagPropertySearch: Search result: 12777
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff7d5eb700 (LWP 5131) exited]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff65172700 (LWP 5132) exited]
Digikam::CollectionScanner::completeHistoryScanning: items to tag ()
Digikam::CollectionScanner::completeScan: Complete scan took: 13290 msecs.
Digikam::adjustedEnvironmentForAppImage: Adjusting environment variables for
AppImage bundle
[Detaching after fork from child process 5133]
Digikam::DNotificationWrapper: Event is dispatched to desktop notifier through
DBUS
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  12  CPU core to
run threads
[New Thread 0x7fff65172700 (LWP 5137)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff7d5eb700 (LWP 5138)]
Digikam::ActionThreadBase::slotJobFinished: One job is done
[Thread 0x7fff65172700 (LWP 5137) exited]
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff7d5eb700 (LWP 5138) exited]
[Thread 0x7fffa67fc700 (LWP 5064) exited]
[Thread 0x7fffb4d0f700 (LWP 5060) exited]
[Thread 0x7fffb5d11700 (LWP 5058) exited]
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  12  CPU core to
run threads
[New Thread 0x7fffb5d11700 (LWP 5165)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fffb4d0f700 (LWP 5166)]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fffb5d11700 (LWP 5165) exited]
[Thread 0x7fffb4d0f700 (LWP 5166) exited]
[Thread 0x7fff67fff700 (LWP 5097) exited]
[Thread 0x7fff7ddec700 (LWP 5090) exited]
[Thread 0x7fff7edee700 (LWP 5091) exited]
[Thread 0x7fffa7fff700 (LWP 5061) exited]
[New Thread 0x7fffa7fff700 (LWP 5447)]
[Thread 0x7fffa7fff700 (LWP 5447) exited]
[New Thread 0x7fffa7fff700 (LWP 5526)]

Thread 14 "ThreadPoolForeg" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa6ffd700 (LWP 5063)]
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65  ../sysdeps/x86_64/multiarch/strlen-avx2.S: Aucun fichier ou dossier de
ce type.
(gdb) bt
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x77dc3799 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0
#2  0x77dc3931 in ?? () from /lib/x86_64-linux-gnu/libudev.so.0
#3  0x77dc3aac in ?? () from /lib/x86_64-linux-gnu/libudev.so.0
#4  0x77dc5ca3 in udev_device_get_subsystem () from
/lib/x86_64-linux-gnu/libudev.so.0
#5  0x7fffe2508903 in udev_monitor_receive_device () from
/tmp/.mount_digikaWEJick/usr/lib/libudev.so.1
#6  0x7fffe7182a62 in ?? () from
/tmp/.mount_digikaWEJick/usr/lib/libQt5WebEngineCore.so.5
#7  0x in ?? ()
(gdb)

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 422345] libQT5WebEngine crash

2020-06-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=422345

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
There is no digiKam symbols visible in your trace.

1/ donwload the debug version of AppImage
2/ run the bundle with -debug argument.
3/ when it crash in debugger, enter "bt" to get detailed backtrace.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.