SUMMARY The cursor is very large and jagged - ugly It still functions STEPS TO REPRODUCE 1. Load the programme and there it is! 2. 3. OBSERVED RESULT Large jagged cursor which returns to normal as it passes from the Digikam container screen into the background ChromeOS screen EXPECTED RESULT Normal sized cursor just like it does for me with Appimage version pf Digikam v6.4 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Running Appimage version of Digikam in Crostini container of ChromeOS v84
We don't do anything with the cursor. It may be related to bug 420727, but the change does not affect the cursor. Maik
Same here on Ubuntu 18.04.5 64bit with Appimage. Before I used digikam 6.4.0 with Appimage, there the normal system cursor was used. But now a ugly black cursor is shown inside digikam.
Please try the current AppImage from digiKam-7.2.0-RC to see whether the problem can still be reproduced. https://files.kde.org/digikam/ Maik
Created attachment 135470 [details] attachment-1664-0.html Good Evening Maik I downloaded this file from your link. digiKam-7.2.0-rc-20210206T180751-x86-64-debug.appimage Which was the larger & later of the two appimages. Unfortunately the cursor is still large and jaggedy like the others. The appimage for v 6.4.0x86-64.appimage is the last version where the cursor was normal (for me). Disappointing, kind regards David Get BlueMail for Android On 6 Feb 2021, 9:23 pm, at 9:23 pm, Maik Qualmann <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #3 from Maik Qualmann <metzpinguin@gmail.com> --- >Please try the current AppImage from digiKam-7.2.0-RC to see whether >the >problem can still be reproduced. > >https://files.kde.org/digikam/ > >Maik > >-- >You are receiving this mail because: >You reported the bug.
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
Created attachment 140173 [details] attachment-28126-0.html Good morning Giles I appreciate your efforts to resolve this cursor issue. I downloaded the 7.4 appimage from your link. Unfortunately it can't get it to open. So unable to comment. kind regards David Ward Get TypeApp for Android On 19 Jul 2021, 7:53 am, at 7:53 am, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #5 from caulier.gilles@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 reported the bug.
> Unfortunately it can't get it to open. What do you mean exactly ? Did you set this file as executable (chmod +r) ? Gilles Caulier
Created attachment 140174 [details] attachment-31477-0.html Giles I set the file as executable using Nautilus file manager. I then right click and select run Just as I have done with other appimage files including Digikam. Nothing happens - it does not open! I downloaded the smaller of the two appimage files digiKam-7.4.0-20210718T194158-x86-64.appimage Hope that helps Regards David Ward Get TypeApp for Android On 19 Jul 2021, 08:39, at 08:39, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #7 from caulier.gilles@gmail.com --- >> Unfortunately it can't get it to open. > >What do you mean exactly ? > >Did you set this file as executable (chmod +r) ? > >Gilles Caulier > >-- >You are receiving this mail because: >You reported the bug.
Forget Nautilus stuff... Open aconsole, got to the directory where appimage is stored, and start it as a simple executable. Report here the console trace just to be sure. Gilles Caulier
Created attachment 140175 [details] attachment-4201-0.html Giles I am afraid you have exceeded my limited knowledge of Linux there I am just a simple user of apps, I am afraid. I do delve into things & try a bit, but quickly get lost in the jargon! [You have my permission to roll your eyes to heaven at this point] Am willing to learn Would a console be the terminal app? How do you start something as a simple executable? ( run and the filename?) Presumably you would like the file made executabe with +chmod (as opposed to the Nautilus method) as part of this sequence? (I have done this before in the dim & distant past so could probably find out how to do it again) regards David Ward Get TypeApp for Android On 19 Jul 2021, 9:07 am, at 9:07 am, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #9 from caulier.gilles@gmail.com --- >Forget Nautilus stuff... > >Open aconsole, got to the directory where appimage is stored, and start >it as a >simple executable. > >Report here the console trace just to be sure. > >Gilles Caulier > >-- >You are receiving this mail because: >You reported the bug.
From my computer and a terminal : [gilles@localhost ~]$ pwd /home/gilles [gilles@localhost ~]$ cd Downloads/ [gilles@localhost Downloads]$ ll total 242668 ... -rw-rw-r-- 1 gilles gilles 248173760 Jul 19 04:57 digiKam-7.4.0-20210718T194158-x86-64.appimage ... [gilles@localhost Downloads]$ chmod +x ./digiKam-7.4.0-20210718T194158-x86-64.appimage [gilles@localhost Downloads]$ ./digiKam-7.4.0-20210718T194158-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found unknown: Qt translations path: "/tmp/.mount_digiKa1AvSAd/usr/share/digikam/translations" unknown: Loaded locale: "en_US" from catalog: "qt" unknown: Loaded locale: "en_US" from catalog: "qtbase" unknown: Loaded locale: "en_US" from catalog: "qt_help" Digikam::ApplicationSettings::setApplicationStyle: Switch to widget style: "" Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled Digikam::AlbumManager::setDatabase: Database Parameters: Type: "QSQLITE" DB Core Name: "/mnt/data/photos/digikam4.db" DB Thumbs Name: "/mnt/data/photos/thumbnails-digikam.db" DB Face Name: "/mnt/data/photos/recognition.db" DB Similarity Name: "/mnt/data/photos/similarity.db" Connect Options: "" Host Name: "" Host port: -1 Internal Server: false Internal Server Path: "" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config file "/tmp/.mount_digiKa1AvSAd/usr/share/digikam/database/dbconfig.xml" Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID => expected: 3 found: 3 Digikam::CoreDbSchemaUpdater::update: Core database: running schema update Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure version 13 Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates 13 to 13 Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location "/photos" uuid "volumeid:?uuid=19b4bf65-70f0-4aba-ae50-8d85e05a05bc" Digikam::CollectionManager::updateLocations: location for "/mnt/data/photos" is available true Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified : "LINUX" Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam: 12265807872 ...
Created attachment 140181 [details] attachment-18018-0.html Gille (Sorry for the Gles!) I think I understood what you were after. the '-rw-rw-r--' command didn't seem to work not sure if it was vital Here is the Terminal screen output from what I did david3ward@penguin:~$ pwd /home/david3ward david3ward@penguin:~$ cd Apps/Digikam/ david3ward@penguin:~/Apps/Digikam$ -rw-rw-r-- digiKam-7.4.0-20210718T194158-x86-64.appimage -bash: -rw-rw-r--: command not found david3ward@penguin:~/Apps/Digikam$ david3ward@penguin:~/Apps/Digikam$ chmod +x digiKam-7.4.0-20210718T194158-x86-64.appimage david3ward@penguin:~/Apps/Digikam$ chmod +x ./digiKam-7.4.0-20210718T194158-x86-64.appimage david3ward@penguin:~/Apps/Digikam$ ./digiKam-7.4.0-20210718T194158-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libxcb-dri3.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libdigikamgui.so.7.4.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libMagick++-7.Q16HDRI.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libMagickCore-7.Q16HDRI.so.9) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libdigikamcore.so.7.4.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Widgets.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Gui.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libmarblewidget-qt5.so.28) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Quick.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQt5Qml.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_objdetect.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_calib3d.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_features2d.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_dnn.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_imgproc.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_ml.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_core.so.4.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libfftw3.so.3) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libxml2.so.2) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libtiff.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libpng16.so.16) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libexiv2.so.27) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavcodec.so.58) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavfilter.so.7) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libavutil.so.56) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libswscale.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libjasper.so.4) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/liblensfun.so.2) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libQtAV.so.1) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libKF5GuiAddons.so.5) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libastro.so.1) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libexif.so.12) digikam: /usr/lib/x86_64-linux-gnu/libnss3.so: version `NSS_3.65' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libsmime3.so) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopus.so.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libswresample.so.3) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libvpx.so.6) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopenjp2.so.7) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libSDL2-2.0.so.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_imgproc.so.3.4) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libopencv_core.so.3.4) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libass.so.9) digikam: /usr/lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /tmp/.mount_digiKayTAEeL/usr/lib/libgnutls.so.30) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libsqlite3.so.0) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libicui18n.so.63) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libicuuc.so.63) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libsndfile.so.1) digikam: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_digiKayTAEeL/usr/lib/libFLAC.so.8) david3ward@penguin:~/Apps/Digikam$ regards David Ward Get TypeApp for Android On 19 Jul 2021, 9:59 am, at 9:59 am, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #11 from caulier.gilles@gmail.com --- >From my computer and a terminal : > >[gilles@localhost ~]$ pwd >/home/gilles >[gilles@localhost ~]$ cd Downloads/ >[gilles@localhost Downloads]$ ll >total 242668 >... >-rw-rw-r-- 1 gilles gilles 248173760 Jul 19 04:57 >digiKam-7.4.0-20210718T194158-x86-64.appimage >... >[gilles@localhost Downloads]$ chmod +x >./digiKam-7.4.0-20210718T194158-x86-64.appimage >[gilles@localhost Downloads]$ >./digiKam-7.4.0-20210718T194158-x86-64.appimage >-- digiKam Linux AppImage Bundle >-- Use 'help' as CLI argument to know all available options for digiKam >application. >-- Notes: to integrate this bundle to your desktop, use >AppImageLauncher. >-- to enable all debug messages on the console, use 'export >QT_LOGGING_RULES="digikam*=true"'. >libudev.so.0 >libxcb-dri3.so.0 >-- Preloading shared libs: :/usr/lib64/libxcb-dri3.so.0 >Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file >found >Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file >found >unknown: Qt translations path: >"/tmp/.mount_digiKa1AvSAd/usr/share/digikam/translations" >unknown: Loaded locale: "en_US" from catalog: "qt" >unknown: Loaded locale: "en_US" from catalog: "qtbase" >unknown: Loaded locale: "en_US" from catalog: "qt_help" >Digikam::ApplicationSettings::setApplicationStyle: Switch to widget >style: "" >Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled >Digikam::AlbumManager::setDatabase: Database Parameters: > Type: "QSQLITE" > DB Core Name: "/mnt/data/photos/digikam4.db" > DB Thumbs Name: "/mnt/data/photos/thumbnails-digikam.db" > DB Face Name: "/mnt/data/photos/recognition.db" > DB Similarity Name: "/mnt/data/photos/similarity.db" > Connect Options: "" > Host Name: "" > Host port: -1 > Internal Server: false > Internal Server Path: "" > Internal Server Admin Cmd: "mysqladmin" > Internal Server Serv Cmd: "" > Internal Server Init Cmd: "" > Username: "" > Password: "" > >Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code >from config >file "/tmp/.mount_digiKa1AvSAd/usr/share/digikam/database/dbconfig.xml" >Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version >ID => >expected: 3 found: 3 >Digikam::CoreDbSchemaUpdater::update: Core database: running schema >update >Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a >structure >version 13 >Digikam::CoreDbSchemaUpdater::makeUpdates: Core database: makeUpdates >13 to >13 >Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location >"/photos" > uuid "volumeid:?uuid=19b4bf65-70f0-4aba-ae50-8d85e05a05bc" >Digikam::CollectionManager::updateLocations: location for >"/mnt/data/photos" >is available true >Digikam::KMemoryInfo::update: KMemoryInfo: Platform identified : >"LINUX" >Digikam::KMemoryInfo::bytes: KMemoryInfo: TotalRam: 12265807872 >... > >-- >You are receiving this mail because: >You reported the bug.
Which Linux system didi you use exactly ?
Created attachment 140182 [details] attachment-23994-0.html Not sure The one that is installed on Chromebooks ChromeOS v91 Get TypeApp for Android On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #13 from caulier.gilles@gmail.com --- >Which Linux system didi you use exactly ? > >-- >You are receiving this mail because: >You reported the bug.
Created attachment 140183 [details] attachment-24595-0.html I think it is a version of Debian running in a container Get TypeApp for Android On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_noreply@kde.org wrote: >https://bugs.kde.org/show_bug.cgi?id=425352 > >--- Comment #13 from caulier.gilles@gmail.com --- >Which Linux system didi you use exactly ? > >-- >You are receiving this mail because: >You reported the bug.
Created attachment 140184 [details] attachment-25844-0.html Seems to be Debian buster david3ward@penguin:~$ sudo apt-get update && sudo apt-get dist-upgrade Get:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease [17.6 kB] Hit:2 https://deb.debian.org/debian buster InRelease Ign:3 http://repo.vivaldi.com/stable/deb stable InRelease Hit:4 https://deb.debian.org/debian-security buster/updates InRelease Hit:5 http://repo.vivaldi.com/stable/deb stable Release Err:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ECA9D5AF2B98B3A0 Ign:6 https://storage.googleapis.com/cros-packages/91 buster InRelease Hit:7 https://storage.googleapis.com/cros-packages/91 buster Release Hit:8 https://packages.bluemail.me/repos/debian ./ InRelease Reading package lists... Done W: GPG error: http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ECA9D5AF2B98B3A0 E: The repository 'http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. david3ward@penguin:~$ Get TypeApp for Android On 19 Jul 2021, 12:01 pm, at 12:01 pm, David Ward <david3ward@gmail.com> wrote: >I think it is a version of Debian running in a container > >Get TypeApp for Android > >On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_noreply@kde.org wrote: >>https://bugs.kde.org/show_bug.cgi?id=425352 >> >>--- Comment #13 from caulier.gilles@gmail.com --- >>Which Linux system didi you use exactly ? >> >>-- >>You are receiving this mail because: >>You reported the bug.
Created attachment 140585 [details] attachment-9602-0.html Have discovered some additional information which may help resolve this issue. I have poor eyesight and activate 'show large cusor' to increase size of cursor by about 20% under chrome OS system accessibility menu. If I deactivate this, the cursor becomes small (too small for me) under chromeOS and even smaller in Digikam - but it is sharp and behaves well. Unlike the huge, blocky, somewhat erratic cursor which appears Digikam if I have 'show large cursor@ activated in chrome OS It would seem the issue may lie in the way chrome OS accessibility feature interacts with the Linux container. I hope this helps in some way. David Ward Get TypeApp for Android On 19 Jul 2021, 12:11 pm, at 12:11 pm, David Ward <david3ward@gmail.com> wrote: >Seems to be Debian buster > >david3ward@penguin:~$ sudo apt-get update && sudo apt-get dist-upgrade >Get:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute InRelease >[17.6 kB] >Hit:2 https://deb.debian.org/debian buster >InRelease >Ign:3 http://repo.vivaldi.com/stable/deb stable >InRelease >Hit:4 https://deb.debian.org/debian-security buster/updates >InRelease >Hit:5 http://repo.vivaldi.com/stable/deb stable >Release >Err:1 http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute >InRelease > The following signatures couldn't be verified because the public key >is not available: NO_PUBKEY ECA9D5AF2B98B3A0 >Ign:6 https://storage.googleapis.com/cros-packages/91 buster >InRelease >Hit:7 https://storage.googleapis.com/cros-packages/91 buster >Release >Hit:8 https://packages.bluemail.me/repos/debian ./ >InRelease >Reading package lists... Done >W: GPG error: http://ppa.launchpad.net/mdoyen/homebank/ubuntu hirsute >InRelease: The following signatures couldn't be verified because the >public key is not available: NO_PUBKEY ECA9D5AF2B98B3A0 >E: The repository 'http://ppa.launchpad.net/mdoyen/homebank/ubuntu >hirsute InRelease' is not signed. >N: Updating from such a repository can't be done securely, and is >therefore disabled by default. >N: See apt-secure(8) manpage for repository creation and user >configuration details. >david3ward@penguin:~$ > >Get TypeApp for Android > >On 19 Jul 2021, 12:01 pm, at 12:01 pm, David Ward ><david3ward@gmail.com> wrote: >>I think it is a version of Debian running in a container >> >>Get TypeApp for Android >> >>On 19 Jul 2021, 11:53 am, at 11:53 am, bugzilla_noreply@kde.org wrote: >>>https://bugs.kde.org/show_bug.cgi?id=425352 >>> >>>--- Comment #13 from caulier.gilles@gmail.com --- >>>Which Linux system didi you use exactly ? >>> >>>-- >>>You are receiving this mail because: >>>You reported the bug.
Can you still reproduce it with some more recent version of Plasma?
Good afternoon I am currently running version 7.7.0 on Debian 11 on an Asus CX9 chromebook. The large, jagged cursor is no longer an issue. I am no longer able to reproduce it. Many thanks for your efforts in sorting these things out. David Ward On 7/28/22 12:53, postix wrote: > https://bugs.kde.org/show_bug.cgi?id=425352 > > postix <postix@posteo.eu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > CC| |postix@posteo.eu > Resolution|--- |WAITINGFORINFO > > --- Comment #18 from postix <postix@posteo.eu> --- > Can you still reproduce it with some more recent version of Plasma? >