Created attachment 124373 [details] Screen of Bildbearbeiten SUMMARY STEPS TO REPRODUCE 1. Open digikam6.4.0 AppImage on Debian Stretch 64 Bit with NVIDIA Graphics 2. Open "Bildbearbeiten" (German) English ImageEditor OBSERVED RESULT The Picture is showen twice and the gui isn't usable The same behavior is when i open the "Leuchttisch" english: Light Table EXPECTED RESULT Like in digikam 6.3.0 the gui should open only once SOFTWARE/OS VERSIONS Debian: Buster Linux: 4.19.0-6-amd64 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3
Created attachment 124374 [details] Screenshot of "Leuchttisch"
Update: I have compiled digikam from sources wich wasrealy painful. When I start this version of digikam, everything looks good.
So it's a packaging problem.... Gilles Caulier
Do you use Wayland? This Qt Bug Report may related to: https://bugreports.qt.io/browse/QTBUG-68575 Maik
Hi Maik, I did not use wayland. echo $XDG_SESSION_TYPE returns x11 Sven
Which Qt version is used by both digiKam (RPM and compiled). Look in Help/Components Info for details. Gilles Caulier
Compiled Version is using: KDE Frameworks 5.54.0 Qt 5.11.3 (kompiliert gegen 5.11.3) Das xcb Fenstersystem App Image Version 6.4.0 (having the crash) is using: KDE Frameworks 5.61.0 Qt 5.13.1 (kompiliert gegen 5.13.1) Das xcb Fenstersystem App Image Version 6.3.0 (without crash) is using: KDE Frameworks 5.59.0 Qt 5.11.3 (kompiliert gegen 5.11.3) Das xcb Fenstersystem
Created attachment 124398 [details] Double Picture in the main screen Digikam 6.4.0 compiled Hi, now I can reproduce the problem even in the compiled version and in the digikam 6.3.0 AppImage. After I open Configure -> Digikam einrichten (Configure Digikam) I have the same efect even in the main screen. But if I change the window size, the problem goes away (in the digikam 6.3.0 Appimage and the compiled version, not so in the digikam 6.4.0 AppImage). I will order a new Graphic-Adapter, I realy want to know if this is the same when I switch from NVIDIA to AMDGPU. Digikam is the only Application with this problem.
Did you use Hdpi screen (as 4K monitor ) ? Gilles Caulier
Yes I have two Monitors one ist a 4k Monitor Sven Am 9. Dezember 2019 13:54:25 schrieb bugzilla_noreply@kde.org: > https://bugs.kde.org/show_bug.cgi?id=414943 > > > --- Comment #9 from caulier.gilles@gmail.com --- > Did you use Hdpi screen (as 4K monitor ) ? > > > Gilles Caulier > > > -- > You are receiving this mail because: > You reported the bug.
ok, I suspected this point. Qt < 5.12 has problem with Hdpi screen. We already seen dysfunctions under MacOS. Please try the 7.0.0 pre release bundle AppImage for Linux available here : https://files.kde.org/digikam/ This one is compiled with last Qt 5.13 stable. If it crash, please run the appImage with "debug" argument and follow instruction here : https://www.digikam.org/contribute/ Report the crash backtrace in this file. Gilles Caulier
nknown: Numeric mode unsupported in the posix collation implementation unknown: Ignoring punctuation unsupported in the posix collation implementation unknown: Numeric mode unsupported in the posix collation implementation unknown: Ignoring punctuation unsupported in the posix collation implementation Digikam::CIETongueWidget::setProfile: Profile white point : x= 0.312713 y= 0.32912 Y= 1 Digikam::CIETongueWidget::setProfile: dkCmsReadICCMatrixRGB2XYZ(2): [ 0.435852 , 0.38533 , 0.143021 ] [ 0.222382 , 0.717041 , 0.0605927 ] [ 0.013916 , 0.0971375 , 0.713837 ] Digikam::CIETongueWidget::setProfile: d->Primaries.Red : X= 0.461196 Y= 0.232948 Z= 0.00978772 Digikam::CIETongueWidget::setProfile: d->Primaries.Green : X= 0.415454 Y= 0.719903 Z= 0.0802877 Digikam::CIETongueWidget::setProfile: d->Primaries.Blue : X= 0.115485 Y= 0.0520762 Z= 0.536577 [New Thread 0x7fffa49f0700 (LWP 22855)] [New Thread 0x7fff7ffff700 (LWP 22856)] [New Thread 0x7fff84e09700 (LWP 22857)] ^C Thread 1 "digikam" received signal SIGINT, Interrupt. 0x00007ffff3c74819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt# Invalid character '#' in expression. (gdb) bt #0 0x00007ffff3c74819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef6e1136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef6e125c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff45d1a5f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_digikaa2nHsB/usr/lib/libQt5Core.so.5 #4 0x00007ffff4578f82 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_digikaa2nHsB/usr/lib/libQt5Core.so.5 #5 0x00007ffff45818a0 in QCoreApplication::exec() () from /tmp/.mount_digikaa2nHsB/usr/lib/libQt5Core.so.5 #6 0x00000000004057f8 in main (argc=1, argv=<optimized out>) at /b/dktemp/digikam-master/core/app/main/main.cpp:334 (gdb) quit A debugging session is active. Inferior 1 [process 22818] will be killed. Quit anyway? (y or n) y
Crash is similar to this problem: https://stackoverflow.com/questions/11859227/qt-qcoreapplicationexec-crash-on-ubuntu-12-04 Maik
After I switched from NVIDIA to AMDGPU the problem disapears. Now I have a new problem: If in Prview more than 20 Pictures shalle be shown, not all Pictures are shown and all shown pictures will flickering. I will open an other bug for this. This problem is not as bad than the other, as I can make my window smaler.
For the flickering we already have an old bug report. Somewhere there must be a problem in the interaction between Qt and the Gnome window manager. I have never seen such malfunctions here under KWin. Maik
The problem with the picture shown twice happend again. I found out, that it happens if I set in the "System-Settings -> Display" the option for scale the Monitor. I have scaled it to 2,1. If I change this settings to 1 or if I remove the 2nd display, everything is okay.
Is the environment variable QT_SCALE_FACTOR set correctly in your desktop environment? Maik
The QT_SCALE_FACTOR is NOT set. The following QT_* vars are set: QT_ACCESSIBILITY="1" QT_AUTO_SCREEN_SCALE_FACTOR="0" QT_SCREEN_SCALE_FACTORS="DisplayPort-0=2.1;HDMI-A-0=2.1;DVI-D-0=2.1;"
Try this in the console: export QT_AUTO_SCREEN_SCALE_FACTOR=1 digikam Maik
With QT_AUTO_SCREEN_SCALE_FACTOR=1 the bug occured.
digiKam 7.0.0 stable release is now published and now available as FlatPak: 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
Hi Sven, Please try using digiKam 7.5.0 pre-release AppImage available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
@Sven digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier
It was never reported again, we can close. Maik