https://bugs.kde.org/show_bug.cgi?id=373839
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||7.2.0
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=373839
graeme.rub...@gmail.com changed:
What|Removed |Added
CC||graeme.rub...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=373839
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|5.4.0 |4.12.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #30 from Kristian Karl ---
I can confirm, that the issue still exists.
I tried using digikam-6.1.0-git-20190321T102236-x86-64.appimage
If there's anything I can do, to try to pin-point the problem, I'm happy to
help out.
--
You are
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #29 from caulier.gil...@gmail.com ---
After 3 weeks of work, i finally completed the compilation of AppImage using Qt
5.11.3 + QWebkit 5.212.
New 6.1.0 pre-release AppImage bundle can be found here (64 bits only for the
moment) :
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #28 from Kristian Karl ---
Complete printout of information regarding the VM machine
$ VBoxManage showvminfo "Kubuntu 18.04"
Name:Kubuntu 18.04
Groups: /
Guest OS:Ubuntu (64-bit)
UUID:
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #27 from Kristian Karl ---
System
===
Processors: 1 CPU
Base memory: 4610 MB
Acceleration: VT-x/AMD-V, Nested Paging, KVM Paravirtualization
Display
===
Video memory: 33 MB
Acceleration: 3D
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #26 from caulier.gil...@gmail.com ---
ok,
What's about the cores assigned to the VM ? Same for the system memory and the
video memory.
This is important because it can influence to the rendering performances.
Gilles Caulier
--
You are
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #25 from Kristian Karl ---
With 3D Acceleration enabled, I still get flickering on my VirtualBox
installation, I'm afraid.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #24 from caulier.gil...@gmail.com ---
Well, try again with this option...
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #23 from Kristian Karl ---
No. 3D Acceleration was disabled.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #22 from caulier.gil...@gmail.com ---
In virtualbox, did you enable 3D support (openGL)
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #21 from Kristian Karl ---
I tested the latest appimage of Digikam (digikam-5.9.0-01-x86-64.appimage) on
the latest KUbuntu (18-04.1) version on Virtualbox.
1) I used images from http://cswww.essex.ac.uk/mv/allfaces/faces94.html
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #20 from caulier.gil...@gmail.com ---
Another way to experiment :
In appimage, we use Qt 5.9.6 LTS. Perhaps a major update to Qt 5.11.x can solve
this problem.
Gilles Caulier
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #19 from Kristian Karl ---
Maybe a long shot, but could maybe this method be involved somehow?
https://github.com/KDE/digikam/blob/c013f88088bf08e321e4da8be71a61b02b67af2c/core/libs/widgets/itemview/dcategorizedview.cpp#L70-L132
I'll add
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #18 from Kristian Karl ---
I think that maybe the resolution might be involved somehow.
If I use may 2560x1440, I don't get any flickering.
When I use 3840x2160, I do get flickering.
Please note, that the digikam window is maximized in
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #17 from Kristian Karl ---
I use x11
echo $XDG_SESSION_TYPE
x11
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #16 from caulier.gil...@gmail.com ---
Do you use X11 or Wayland ?
I never tested AppImage with Wayland, and think it must miss some piece of Qt
plugins in the bundle.
Gilles Caulier
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #15 from Kristian Karl ---
Oh sorry!
Desktop: KDE Neon (Plasma 5.13.4,KDE frameworks 5.49.0, Qt 5.11.1 ) on Ubuntu
18.04
Display manager and extension:
cat /etc/X11/default-display-manager
/usr/bin/sddm
Graphics card and driver?
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #14 from Maik Qualmann ---
That's right, the thumbnails are "preloaded" by the Paint Event. The thumbnail
task will send a signal to the image model that the thumbnail is available and
it will be drawn. By you over and over again. The
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #13 from Kristian Karl ---
Some more details observed while debugging.
It seems like ThumbnailLoadingTask is getting called repeatably during flicker:
libdigikamcore.so.6.0.0!Digikam::ThumbnailCreator::loadDetail(const
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #12 from Kristian Karl ---
When debugging this morning, I paused during flicker, and paused execution.
Every time I paused , the stack trace for Digikam code started at:
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #11 from Kristian Karl ---
Absolutely!
I'll try some debugging of my own in the meantime. I got a dual screen setup to
hel me debug now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #10 from Maik Qualmann ---
The first thing that is strange is that you constantly have a paint event. As I
said, usually only when the mouse pointer or a window moves in front of it or
the view is scrolled. The second question is where the
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #9 from Kristian Karl ---
I tested this on a different 4k screen, and I get the same problem.
Using the latest from git: 0890e2005cae874dd1fcf71c2d3642152c00eff0, digikam
produces the following on the terminal during this flickering
:
:
https://bugs.kde.org/show_bug.cgi?id=373839
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #8 from Maik
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #7 from caulier.gil...@gmail.com ---
The AppImage Linux Bundle have been recompiled with last changes from source
code and is available here for testing :
https://files.kde.org/digikam/
Take a care : 6.0.0 is a beta release for the moment.
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #6 from Kristian Karl ---
I have seen this problem on 2 different 4K screens. One connected to my
midtower machine.
And last, my laptop Lenovo Thinkpad X240 connected using Display Port to a BenQ
BL3201PT
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #5 from caulier.gil...@gmail.com ---
Here, i tried with digiKam 5.7.0 + Qt 5.9. + KF5 5.35, and OpenCV 3.1.0 with a
4K monitor under Mageia6. I cannot reproduce the problem.
Which screen resolution do you use exactly ?
Gilles Caulier
--
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #4 from Kristian Karl ---
The flickering still exists digikam 5.7.0, installed from neon CI repository:
aptitude show digikam
Package: digikam
https://bugs.kde.org/show_bug.cgi?id=373839
caulier.gil...@gmail.com changed:
What|Removed |Added
Platform|Other |Appimage
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=373839
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|5.3.0 |5.4.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #3 from Kristian Karl ---
Yes, I could reproduce the problem on the pre-release 5.4.0 AppImage.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373839
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #1 from Kristian Karl ---
I noticed this first, when using a maximized Digikam window on a 4K monitor,
where enough faces/thumbnails were rendered to cause the flickering.
Reducing the size of the Digikam
35 matches
Mail list logo