[kscreenlocker] [Bug 473247] Telling people to hit Ctrl+Alt+F1 when the screen locker is broken is not always (or ever?) accurate
https://bugs.kde.org/show_bug.cgi?id=473247 Jens Reimann changed: What|Removed |Added CC||ct...@dentrassi.de --- Comment #6 from Jens Reimann --- I just ran into the same issue. Using Ctrl-Alt-F3 worked for me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487285] New: Date/Time correction tool applies corrections twice, and in seemingly random order
https://bugs.kde.org/show_bug.cgi?id=487285 Bug ID: 487285 Summary: Date/Time correction tool applies corrections twice, and in seemingly random order Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Date Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY When using the date/time correction tool, there are two small issues that confuse me. 1. When pressing Apply, the correction is not applied in the order the files are listed in but seemingly random. The list selection then jumps around randomly which is confusing. 2. When pressing OK after having pressed Apply, the correction is applied *again*, which causes an unnecessary delay. In both cases I was correcting the timestamp of mp4 video files using the "[x] use Exiftool" option, based on the mp4 filename which was MMDD_HHMMSS_*.mp4. STEPS TO REPRODUCE 1. Get videos named like above 2. Use date/time correction like described above 3. Observe issues like mentioned above EXPECTED RESULT 1. Apply changes in the order the files are listed, or list the files in the order the changes are applied (preferably, the former) 2. Do not re-apply when changes have already been applied, and OK is pressed. SOFTWARE/OS VERSIONS: KDE Neon 24.04 with all updates applied, & Digikam 20240512 appimage 64bit. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 Jens Müller changed: What|Removed |Added CC||b...@tessarakt.de --- Comment #5 from Jens Müller --- I noticed this behavior in this document: https://www.segeberg.de/PDF/Eingliederungshilfe_Folgeantrag_.PDF?ObjSvrID=3466=485=1=PDF=1&_ts=1634808034 with Okular 23.08.5 on current Ubuntu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482476] Weird mouse and cursor behavior in video games
https://bugs.kde.org/show_bug.cgi?id=482476 --- Comment #29 from Jens Ramke --- (In reply to Jens Ramke from comment #28) > I'm still encountering this bug with kwin 6.0.3.1 in both `Mass Effect > Legendary Edition` and `Doom Eternal`, but not in `Portal RTX`. > > Operating System: Arch Linux > KDE Plasma Version: 6.0.3 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.7.0 > Kernel Version: 6.7.12-zen4-xanmod1-1 (64-bit) > Graphics Platform: Wayland > Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor > Memory: 62.0 GiB of RAM > Graphics Processor: AMD Radeon Graphics (onboard, primary) > Graphics Processor: NVIDIA RTX 4090 (secondary through prime) > Manufacturer: Micro-Star International Co., Ltd. > Product Name: MS-7E12 > System Version: 1.0 It seems be be fixed with version 6.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482476] Weird mouse and cursor behavior in video games
https://bugs.kde.org/show_bug.cgi?id=482476 Jens Ramke changed: What|Removed |Added Version|6.0.1 |6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482476] Weird mouse and cursor behavior in video games
https://bugs.kde.org/show_bug.cgi?id=482476 Jens Ramke changed: What|Removed |Added CC||jens.ra...@gmail.com --- Comment #28 from Jens Ramke --- I'm still encountering this bug with kwin 6.0.3.1 in both `Mass Effect Legendary Edition` and `Doom Eternal`, but not in `Portal RTX`. Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.12-zen4-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: AMD Radeon Graphics (onboard, primary) Graphics Processor: NVIDIA RTX 4090 (secondary through prime) Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7E12 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288 Jens Küspert changed: What|Removed |Added CC||jens.kuesp...@posteo.de Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #8 from Jens Küspert --- I see this error too. Is there a known work-around? Maybe fresh install of the packages? My situation is as follows: $ ldd -d /usr/lib/x86_64-linux-gnu/signon/extensions/libkeyring-kwallet.so linux-vdso.so.1 (0x7fff78b54000) libKF5Wallet.so.5 => /lib/x86_64-linux-gnu/libKF5Wallet.so.5 (0x7f1ab899f000) libsignon-extension.so.1 => /lib/x86_64-linux-gnu/libsignon-extension.so.1 (0x7f1ab8988000) libQt5Core.so.5 => /lib/x86_64-linux-gnu/libQt5Core.so.5 (0x7f1ab840) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f1ab800) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f1ab8968000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f1ab7c0) libKF5WindowSystem.so.5 => /lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 (0x7f1ab83aa000) libKF5ConfigCore.so.5 => /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 (0x7f1ab833d000) libQt5DBus.so.5 => /lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x7f1ab82aa000) libQt6DBus.so.6 => /lib/x86_64-linux-gnu/libQt6DBus.so.6 (0x7f1ab7f46000) libQt6Core.so.6 => /lib/x86_64-linux-gnu/libQt6Core.so.6 (0x7f1ab760) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7f1ab7e7f000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f1ab828c000) libdouble-conversion.so.3 => /lib/x86_64-linux-gnu/libdouble-conversion.so.3 (0x7f1ab8277000) libicui18n.so.70 => /lib/x86_64-linux-gnu/libicui18n.so.70 (0x7f1ab720) libicuuc.so.70 => /lib/x86_64-linux-gnu/libicuuc.so.70 (0x7f1ab7005000) libpcre2-16.so.0 => /lib/x86_64-linux-gnu/libpcre2-16.so.0 (0x7f1ab7576000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f1ab6f36000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f1ab6dfc000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f1ab6d15000) /lib64/ld-linux-x86-64.so.2 (0x7f1ab89f1000) libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x7f1ab6bd5000) libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x7f1ab824b000) libxcb-keysyms.so.1 => /lib/x86_64-linux-gnu/libxcb-keysyms.so.1 (0x7f1ab8244000) libQt5X11Extras.so.5 => /lib/x86_64-linux-gnu/libQt5X11Extras.so.5 (0x7f1ab823d000) libQt5Widgets.so.5 => /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x7f1ab640) libQt5Gui.so.5 => /lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x7f1ab5c0) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f1ab7e31000) libb2.so.1 => /lib/x86_64-linux-gnu/libb2.so.1 (0x7f1ab7be2000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f1ab7bb7000) liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f1ab7556000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f1ab823) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f1ab5ac2000) libicudata.so.70 => /lib/x86_64-linux-gnu/libicudata.so.70 (0x7f1ab3e0) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7f1ab6b5f000) libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x7f1ab7e2b000) libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x7f1ab7baf000) libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x7f1ab6ad8000) libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x7f1ab63c5000) libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x7f1ab62f6000) libmd4c.so.0 => /lib/x86_64-linux-gnu/libmd4c.so.0 (0x7f1ab7544000) libgomp.so.1 => /lib/x86_64-linux-gnu/libgomp.so.1 (0x7f1ab5a78000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7f1ab5a52000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7f1ab5a3a000) libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x7f1ab3d48000) libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x7f1ab3d14000) libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x7f1ab3c4c000) libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3 (0x7f1ab3c25000) libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x7f1ab7537000)
[dolphin] [Bug 484671] New: WebDAV shared files all show "Jan 1 1970" as modification time since 6.0 upgrade
https://bugs.kde.org/show_bug.cgi?id=484671 Bug ID: 484671 Summary: WebDAV shared files all show "Jan 1 1970" as modification time since 6.0 upgrade Classification: Applications Product: dolphin Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a Nextcloud 28 instance running to share files with other people. I have a shortcut in my Dolphin sidebar to use the Files area of this instance shared using WebDAVs: webdavs://HOSTNAME/remote.php/dav/files/MY_EMAIL/ Since upgrading to KDE 6, all files I can see on this share have the modification time "Jan 1, 1970". This also happens when using `kioclient ls ` on the command line: ``` $ kioclient stat webdavs://../Documents/xx.xls NAME xx.xls SIZE 471552 FILE_TYPE 010 MIME_TYPE application/vnd.ms-excel ACCESS0600 MODIFICATION_TIME Thu Jan 1 00:00:00 1970 CREATION_TIME Sun Mar 24 13:08:26 2024 ``` Using other WebDAV clients (e.g. `cadaver` display the modification time correctly. This also does not happen wit other remote protocols, e.g. `kio_fish`. It sesms to be a regression when moving from KDE 5 to KDE 6. SOFTWARE/OS VERSIONS: KDE Neon 22.04 with all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Jens K changed: What|Removed |Added CC||karate...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484211] Spectacle should convert old format string in filename
https://bugs.kde.org/show_bug.cgi?id=484211 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #2 from Jens --- I also just got bitten by this. How about the conversion script actually checks for the "%" placeholder in the filename template, and runs based on that result, instead of the config file timestamp? I think we should still do this, there may be a number of users who have upgraded but haven't used Spectacle yet, and haven't noticed this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484482] New: Dragging an image on a tag does not assign this tag to the image
https://bugs.kde.org/show_bug.cgi?id=484482 Bug ID: 484482 Summary: Dragging an image on a tag does not assign this tag to the image Classification: Applications Product: digikam Version: 8.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Open right sidebar, select tag tree view 2. Drag an image onto this tag, choose "assign this tag to the image" in the popup context menu OBSERVED RESULT: Tag is not assigned to the image. EXPECTED RESULT: Tag should be assigned to the image. SOFTWARE/OS VERSIONS: KDE Neon 22.04, Digikam appimage 20240324. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484250] Discover cannot find packages that 'apt search' can find
https://bugs.kde.org/show_bug.cgi?id=484250 --- Comment #2 from Jens --- Both mentioned packages are "applications" (i.e. desktop apps that end users can use). How you distinguish apps from packages? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480779] Can not add Google to Online Accounts anymore
https://bugs.kde.org/show_bug.cgi?id=480779 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #7 from Jens --- I have he same issue on KDE Neon based on Ubuntu 22.04 with KDE 6 upgraded from KDE 5. Additionally, existing Google accounts do not show any files any more (the loading never stops). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484250] New: Discover cannot find packages that 'apt search' can find
https://bugs.kde.org/show_bug.cgi?id=484250 Bug ID: 484250 Summary: Discover cannot find packages that 'apt search' can find Classification: Applications Product: Discover Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: aleix...@kde.org Target Milestone: --- SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. start discover and konsole 2. Use discover and apt search to find 'xmedcon' and 'sightviewer' packages 3. compare results OBSERVED RESULT Discover cannot find either. ' apt search' finds both. EXPECTED RESULT Search results by apt should be included in Discover's results. SOFTWARE/OS VERSIONS: KDE Neon 22.04 LTS with KDE 6.0.2 and all updates applied -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443444] ISOs located on external NTFS disks are only displayed in the hamburger menu after you quit and restart Dolphin.
https://bugs.kde.org/show_bug.cgi?id=443444 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #4 from Jens --- This bug is still present on Dolphin 24.02.0 as of KDE 6.0.2. I can mount some ISOs from the context menu and they will show up in Dolphin right away, but others don't work. What's more (different bug), if the ISO label contains spaces or special characters (like "Tim's Favorite Documents" :-) ), the ISO will shows up as a disk but a click on it won't mount it, it'll show an error message. And also, if I unmount them using Dolphin, they will stay in the sidebar as unmounted loop devices. Removing the actual loop device does not seem possible using Dolphin yet (I use "gdisks" to do this). -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 482203] New: drkonqi-sentry-postman keeps uploading with full speed
https://bugs.kde.org/show_bug.cgi?id=482203 Bug ID: 482203 Summary: drkonqi-sentry-postman keeps uploading with full speed Classification: Applications Product: drkonqi Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jens.ra...@gmail.com Target Milestone: --- SUMMARY drkonqi-sentry-postman (6.0.0) keeps uploading something with full speed, severely disrupting other network traffic, e.g. youtube streaming. New drkonqi-sentry-postman instances keep reappearing in the process list. At this point many MiB of, to me, unknown data have been uploaded to somewhere. The uploads persist after a reboot. I've had a lot of kate crashes previously today. STEPS TO REPRODUCE 1. Produce lots of crashes of e.g. kate OBSERVED RESULT Network is congested and barely usable EXPECTED RESULT Uploading stops at some point and/or rate is limited. Uploading can be stopped by user. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.6-zen4-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.0 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482080] breeze and plasma-integration Qt5 builds not installed by default
https://bugs.kde.org/show_bug.cgi?id=482080 --- Comment #2 from Jens Küspert --- (In reply to David Redondo from comment #1) > The problem seems to be breeze and plasma-integration for Qt5 are not > installed by default That could be an explanation for the look. In my opionion it would be more straight-forward to build the timetracke against kf6 and qt6, just as in testing. Anyway: What packages need to be installed in order to get breeze ans plasma-integration für Qt5? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482152] When starting the LSP, Kate crashes.
https://bugs.kde.org/show_bug.cgi?id=482152 Jens Ramke changed: What|Removed |Added CC||jens.ra...@gmail.com --- Comment #1 from Jens Ramke --- *** Bug 482158 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482158] Kate crashes when opening python file with LSP server running
https://bugs.kde.org/show_bug.cgi?id=482158 Jens Ramke changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Jens Ramke --- *** This bug has been marked as a duplicate of bug 482152 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482158] New: Kate crashes when opening python file with LSP server running
https://bugs.kde.org/show_bug.cgi?id=482158 Bug ID: 482158 Summary: Kate crashes when opening python file with LSP server running Classification: Applications Product: kate Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: jens.ra...@gmail.com Target Milestone: --- Application: kate (24.02.0) Qt Version: 6.7.0 Frameworks Version: 6.0.0 Operating System: Linux 6.7.6-zen4-xanmod1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.0 [CoredumpBackend] -- Information about the crash: Opening any sufficientliuy large python file crashes Kate after a few seconds when python-lsp-server is used. The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7759dd893c6a in operator== (p2=..., p1=...) at /usr/include/qt6/QtCore/qshareddata.h:202 #7 0x7759dfd9f55f in DiagnosticsView::addMarks (item=0x5dfbc56d75b0, doc=0x5dfbc495edb0, this=0x5dfbc463b320) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1044 #8 DiagnosticsView::addMarksRec (this=this@entry=0x5dfbc463b320, doc=doc@entry=0x5dfbc495edb0, item=0x5dfbc56d75b0) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1088 #9 0x7759dfd9f1aa in DiagnosticsView::addMarksRec (this=this@entry=0x5dfbc463b320, doc=doc@entry=0x5dfbc495edb0, item=) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1090 #10 0x7759dfd9f1aa in DiagnosticsView::addMarksRec (this=this@entry=0x5dfbc463b320, doc=doc@entry=0x5dfbc495edb0, item=) at /usr/src/debug/kate/kate-24.02.0/apps/lib/diagnostics/diagnosticview.cpp:1090 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482080] New: ktimetracker not built since 2022
https://bugs.kde.org/show_bug.cgi?id=482080 Bug ID: 482080 Summary: ktimetracker not built since 2022 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: jens.kuesp...@posteo.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** The binary package of ktimetracker has not been built since 2022-09-08. When installing on a freshly upgraded Neon with Plasma 6 and KF6 it looks ugly, since it uses kf5-libs. This does *not* happen in testing, since it is built with new liberaries. *** STEPS TO REPRODUCE 1. Take Neon user 2. Install ktimetracker (version 4:5.0.1-3+22.04+jammy+release+build3) 3. Start ktimetracker OBSERVED RESULT Dependencies to kf5. EXPECTED RESULT Usage of kf6 (as in Neon testing). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 22.04 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 (ktimetracker says 5.115.0) Qt Version: 6.6.2 (ktimetracker says 5.15.12) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480763] Resizing the application launcher menu on the upper right corner freezes the Plasma session.
https://bugs.kde.org/show_bug.cgi?id=480763 --- Comment #1 from Gerold Jens Wucherpfennig --- Kickoff is actually "shaking", trying to move back and forwards. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480763] New: Resizing the application launcher menu on the upper right corner freezes the Plasma session.
https://bugs.kde.org/show_bug.cgi?id=480763 Bug ID: 480763 Summary: Resizing the application launcher menu on the upper right corner freezes the Plasma session. Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: gjwucherpfen...@gmx.net CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Resizing the application launcher menu on the upper right corner freezes the Plasma session. STEPS TO REPRODUCE 1. Start neon-testing-20240130-0309.iso in VirtualBox. 2. Click at the Kickoff Application Launcher. 3. Click at the upper right corner of Kickoff. OBSERVED RESULT Kickoff freezes and the CPU is at 100%. EXPECTED RESULT The expected result is to be able to resize Kickoff. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (neon-testing-20240130-0309.iso) KDE Plasma Version: 6.0 RC1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479704] Nearby face tag editor fields overlap each other, making targeted editing impossible
https://bugs.kde.org/show_bug.cgi?id=479704 --- Comment #2 from Jens --- Actually, I was maybe hoping for a kind of middle ground: show the rectangles, but show the edit field only when hovering over the rectangles (and the space between rectangle & edit field so you can actually reach the edit field). This way, you would instantly see which objects are detected as faces, but with lots of faces the edit fields would not overlap the image. Maybe we could even fade out the rectangles some seconds after the last move of the mouse cursor and show them again when the user uses the mouse again. This would remove the need to keep toggling between showing and hiding them to see what is behind all those edit fields ... Just some thoughts :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479748] New: Confirming / rejecting faces using the image preview (not the thumbnail) should advance to the next unconfirmed face, not to the last confirmed one
https://bugs.kde.org/show_bug.cgi?id=479748 Bug ID: 479748 Summary: Confirming / rejecting faces using the image preview (not the thumbnail) should advance to the next unconfirmed face, not to the last confirmed one Classification: Applications Product: digikam Version: 8.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- STEPS TO REPRODUCE 1. In Faces, go to a face where there are suggestions detected by Digikam which you can confirm/reject/ignore. 2. Instead of doing this inside the thumbnails view, double click the image (to see the whole picture) and confirm/reject/ignore the face there. OBSERVED RESULT Digikam will confirm/reject/ignore the face, and then show the image with the *last* (confirmed) face of that person. If there are a lot of faces for this person, and you exit the preview by pressing ESC, the thumbnails list will have scrolled all the way down. To view the next face suggestion thumbnail, the user needs to scroll all the way up again. EXPECTED RESULT When confirming/rejecting/ignoring face suggestions in image preview, Digikam should - IMHO - advance to the next unconfirmed suggestion, not the last confirmed face. This makes the process of face tagging much more efficient. SOFTWARE/OS VERSIONS: KDE Neon 22.04, Digikam appimage 2024.01.07 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479704] New: Nearby face tag editor fields overlap each other, making targeted editing impossible
https://bugs.kde.org/show_bug.cgi?id=479704 Bug ID: 479704 Summary: Nearby face tag editor fields overlap each other, making targeted editing impossible Classification: Applications Product: digikam Version: 8.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 164849 --> https://bugs.kde.org/attachment.cgi?id=164849=edit Screenshot with overlapping face tag edit fields SUMMARY It is best to see the attachment. STEPS TO REPRODUCE 1. Create photo with many faces close to each other 2. Start face detection 3. Enable faces editor to label the faces OBSERVED RESULT Face editor fields overlap each other. It is not possible to close them except by marking them as ignored or deleting them, which is not what I intend. I want to label all, but I also need to see which editor field belongs to which face rectangle. EXPECTED RESULT Editor fields should not overlap, or (at least) if the mouse clicks on a face rectangle, all non-related editor fields should be hidden. Or (perhaps better), the edit fields can be made movable by dragging with the mouse (possibly Ctrl-click or something) so you can disentangle them if needed. SOFTWARE/OS VERSIONS: KDE Neon 22.04, Digikam preview appimage 2024.01.07 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 --- Comment #14 from Jens --- Great, that does it. Thank you for tracking this down! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 --- Comment #10 from Jens --- Thank you for the mtime patch! I use the preview versions exactly for this purpose, to be able to report bugs. I can send you an image by private email if this is OK, I just don't want to attach it to a public bug report. However, I don't actually think the images themselves are relevant. I can assure you the images I import had no "Photoshop Urgency" attribute set when imported, they come directly from the camera and I changed nothing on the camera, no firmware update or settings, in the last year. I am pretty convinced this appeared after upgrading Digikam. I just did a "bisect" of my collection to find when this "Urgency" tag started appearing. This tag was not applied when rating photos using this appimage on 2023-09-28: -rwxrw-r-- 1 jens jens 250725568 Sep 16 22:56 digiKam-8.2.0-20230916T093515-x86-64_da62242c9f77e794a78c031a8248480c.appimage The tag *was* applied when rating photos by the same camera using this appimage on 2023-12-19: -rwxrw-r-- 1 jens jens 255956160 Okt 11 22:24 digiKam-8.2.0-20231007T150049-x86-64_8b40e8da45c132f84a7c0629766a4c64.appimage ... and all later versions. In between 2023-09-28 and 2023-12-19, I haven't yet rated or otherwise touched any of my imported images and none of them have this Urgency tag. So I suspect something happened between these two appimage versions. What could this be? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 --- Comment #6 from Jens --- Here -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 --- Comment #5 from Jens --- Created attachment 164723 --> https://bugs.kde.org/attachment.cgi?id=164723=edit after assigning a rating -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 --- Comment #4 from Jens --- Created attachment 164722 --> https://bugs.kde.org/attachment.cgi?id=164722=edit before assigning a rating -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479430] New: Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order
https://bugs.kde.org/show_bug.cgi?id=479430 Bug ID: 479430 Summary: Assigning Ratings using Ctrl+[1..9] assigns a color code during preview && modifies "By Date" sort order Classification: Applications Product: digikam Version: 8.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Rating Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Since upgrading to 2024-01-01 (also in 2024-01-03 appimage), when I preview an image and then press Ctrl-1..5 to assign stars / ratings, this automatically also assings a color to the image and gives it a colored border. This did not happen before. Also, when assigning a rating or color, sorting images "By Date" seems to use the sidecar XML filesystem modification date (?) and not the original image date (EXIF, IPTC or filessystem), because the images are resorted upon assigning ratings when choosing "Sort by Date". I let Digikam write metadata only in sidecar files, the originals are never touched. This also did not happen with previews (start of December) appimage snapshots. The hotkeys are default: Ctrl-NUM for rating and Ctrl-Alt-NUM for color codes. STEPS TO REPRODUCE 1. Set digikam to write only to metadata sidecar files, and to sort by image date 2. Tag some images during preview 3. Watch color codes being assigned and sort order being modified SOFTWARE/OS VERSIONS: KDE Neon 22.04, with 2024-01-03 Digikam appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479275] Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275 --- Comment #6 from Jens --- I would have to rename & fix several 100 face tags, this would take me several hours Can we automate this using a SQlite script or similar which just does it directly in the SQLite database? If you can give me some details about the SQL structure I can perhaps whip up a script, which in turn may help others. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479275] Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275 --- Comment #4 from Jens --- OK, this is understandable, but I actually loved the possibility to organize my face tags in a hierarchy directly upon creation. No way to do this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 479275] Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275
--- Comment #2 from Jens ---
Thanks, I have. But I'm a bit confused ...
does this mean I have to rename & fix my >500 name tags manually?
If so, which ones ("/" or "\" variant)?
And what about name/face tag hierarachies, can they still exist? Can I still
have a "People/Family/John" and a "Work/Colleagues/John"?
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 479275] New: Duplicate tags created with "\" as separator since upgrade to 8.3
https://bugs.kde.org/show_bug.cgi?id=479275 Bug ID: 479275 Summary: Duplicate tags created with "\" as separator since upgrade to 8.3 Classification: Applications Product: digikam Version: 8.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 164605 --> https://bugs.kde.org/attachment.cgi?id=164605=edit Example screenshot of issue SUMMARY Since upgrading to the newest 8.3.0 pre-release appimage, my tags directory has blown up because many tags (not all) have been duplicated with a backslash as the separator, in addition to the correct "/" (which gets interpreted by Digikam as a hierarchy). See screenshot. STEPS TO REPRODUCE 1. Install Digikam 8.2 2. Create some tags 3. Upgrade go 8.3 pre-release (December) SOFTWARE/OS VERSIONS: KDE Neon 22.08 LTS, Digikam 20240101 (911d1a7c02b08) appimage -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Jens changed: What|Removed |Added CC||jens-bugs.kde.org@spamfreem ||ail.de --- Comment #28 from Jens --- I'm getting this too since today. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478649] New: Does not work with several Nextcloud online accounts (shows no files)
https://bugs.kde.org/show_bug.cgi?id=478649 Bug ID: 478649 Summary: Does not work with several Nextcloud online accounts (shows no files) Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kaccounts Assignee: plasma-b...@kde.org Reporter: jens-bugs.kde@spamfreemail.de CC: ad...@leinir.dk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create two Nextcloud accounts, and upload some files to each 2. Create accounts in Online Accounts for these two 3. Try to access them via Dolphins 'Network' OBSERVED RESULT The first one shows all files. The second one shows no files. There is no error message, it just appears empty. If I create the accounts in a different order, the second one will show files, and the first one won't. It does not (seem to) matter whether login happens using App Tokens or using the user password. EXPECTED RESULT Both online accounts should show their respective files. SOFTWARE/OS VERSIONS: KDE Neon 22.04 LTS with all updates applied as of today. ADDITIONAL INFORMATION: I also have one Google Drive account configured in KDE Online Accounts which works flawleessly. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 478434] New: Allow cropping the image after making the screenshot
https://bugs.kde.org/show_bug.cgi?id=478434 Bug ID: 478434 Summary: Allow cropping the image after making the screenshot Classification: Applications Product: Spectacle Version: 23.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: ct...@dentrassi.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY I would like to be able to crop a screenshot after I made it. Similar to adding annotations. STEPS TO REPRODUCE 1. Create a screenshot 2. "here" I would like to crop the image 3. OBSERVED RESULT I cannot crop the image. EXPECTED RESULT I would want to have the ability to crop the image. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.4-200.fc39.x86_64 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477234] Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded
https://bugs.kde.org/show_bug.cgi?id=477234 --- Comment #2 from Jens Radloff --- (In reply to Juraj from comment #1) > This extension is still Qt5 only. > Thank you for reporting. You are welcome. Does that mean it makes no sense to report new bugs in Falkon for all current and maybe future Falkon versions which are still based on QT5? Should I wait with reporting new bug issues until the Falkon source code will be based on QT6 and can locally get cloned using git? Or does it depend on specific software elements, like (specific) browser extensions, if it makes sense to currently or still test them or not? Are there specific browser extensions embedded into the Falkon QT5 based source code which will not be available anymore in the future QT6 based Falkon source code? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of previous default search engine) is displayed there + searche
https://bugs.kde.org/show_bug.cgi?id=477142 --- Comment #3 from Jens Radloff --- (In reply to Jens Radloff from comment #1) > These values for the parameters for a Startpage search engine entry work, i. > e. searches with Startpage through the search bar execute successful > searches by Startpage.com: > > Name: StartPage > URL: https://www.startpage.com/sp/search?query=%s > Post data: > Shortcut: sp Having created a completely new git clone of the Falkon source code in another local directory some days ago, then having compiled and installed this clone, I can confirm that the search URL "https://startpage.com/do/search; in the preferences for the Startpage search engine in the Preferences dialog > Other > Manage search engines/Search Engines Manager > Edit button > "Url" field is the search URL that is predefined in the Falkon source code. This predefined search URL results in non-working searches if StartPage is used for searching via the Search Bar. Note that in the Search Engines Manager > Edit window for StartPage the field "Post Data" contains the string "query=%s=web=english" as predefined by the current Falkon source code. Using this string in the "Post Data" field in connection with the search URL "https://www.startpage.com/sp/search?query=%s; (which itself works, see above) in the "Url" field of the Startpage settings results in erroneous search results when Startpage is used by using the Search Bar for searching for any string. I typed "duck" into the Search Bar (before that I selected Startpage as the search engine to be used for the search by selecting its corresponding icon left to the Search Bar), pressed ENTER, then Startpage showed the results of this search, and it appears that at the top of this result page the string "%s" is shown in the Start Page search field at the top of the result page. Thus Startpage had applied a search for the string "%s". That means that the predefined string "https://www.startpage.com/sp/search?query=%s; in the "Post Data" field in the settings for Startpage in the Search Engines Manager works improperly. But if you leave the "Post Data" field empty, then searches with Startpage via the Search Bar results in correct search result web pages. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477236] Both English and German texts in Preferences window and in "Site Info" window
https://bugs.kde.org/show_bug.cgi?id=477236 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org --- Comment #1 from Jens Radloff --- Created attachment 163292 --> https://bugs.kde.org/attachment.cgi?id=163292=edit "Preferences" window: Elements show both texts in English and German -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477236] New: Both English and German texts in Preferences window and in "Site Info" window
https://bugs.kde.org/show_bug.cgi?id=477236
Bug ID: 477236
Summary: Both English and German texts in Preferences window
and in "Site Info" window
Classification: Applications
Product: Falkon
Version: 24.01.75
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: s...@mailbox.org
Target Milestone: ---
Created attachment 163291
--> https://bugs.kde.org/attachment.cgi?id=163291=edit
"Site Info" window: The "Save" button shows this word translated into German
("Speichern")
1. Click the lock icon left from the Adress Bar. This icon shows the following
tooltip text: "Show information about this page".
2. Click the "More ..." button: The "Site Info" window is displayed.
3. Click the "Media" tab.
The "Save" button shows the German word "Speichern", which means "save". See
the attached screenshot.
4. Menu Edit > Preferences:
English and German texts are mixed in this window. See the attached screenshot.
The elements in my Falkon compilation mainly show English texts, like the menu
names, menu entries andmost buttons. German texts are not expected in my Falkon
compilation.
Is it possible to define in which language GUI elements in Falkon should get
displayed in Falkon when configuring Falkons source code with the cmake
command? I cannot find any information about this in the output of the "cmake
--help" command when I execute this command in the build directory of my Falkon
project diretory where I am compiling Falkon git clones.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 477234] Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded
https://bugs.kde.org/show_bug.cgi?id=477234 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477234] New: Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded
https://bugs.kde.org/show_bug.cgi?id=477234 Bug ID: 477234 Summary: Extension "Aktion ausführen" (this German text can be translated into English like "Execute Action") cannot get loaded Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- Menü Edit > Preferences > Extensions: Attempting to select/activate the extension with the German text "Aktion ausführen"* results in the error message "Error! Falkon. Cannot load extension!" * This German text can be translated into English like "Execute Action". SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477232] Missing file extensions in file names of locally saved images from web pages, where these images were downloaded via the "Site Info" window
https://bugs.kde.org/show_bug.cgi?id=477232 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477232] New: Missing file extensions in file names of locally saved images from web pages, where these images were downloaded via the "Site Info" window
https://bugs.kde.org/show_bug.cgi?id=477232 Bug ID: 477232 Summary: Missing file extensions in file names of locally saved images from web pages, where these images were downloaded via the "Site Info" window Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- 1. Open https://www.ardaudiothek.de/episode/geht-ein-mann-zum-arzt/hautkrebsscreening-scan-mich-6-6/rbb/12846195/ with the Falkon browser. 2. Click the lock icon left from the Adress Bar. This icon shows the following tooltip text: "Show information about this page". 3. Click the "More ..." button: The "Site Info" window is displayed. 4. Click the "Media" tab. Information about the images displayed at the above-mentioned URL gets displayed below. 5. Click any entry in this list. 6. Click the "Save" button. Note: In my Falkon compilation this button does not show the English word "Save", but instead the German word "Speichern", which means "Save" in English. Probably all menu names, menu entries and most buttons in the GUI of my Falkon compilation normally show texts in English. I will create an extra bug report about this behavior. 7. Download the selected image to your local disk. Before downloading, do not change the file name of the selected image. The downloaded image file has a file name without any file extensions. If I open the properties of such a downloaded image file on my hard disk, its file properties tell me that the file is a *.png file. I cannot find the file name of the downloaded image file in the HTML code of the web page which I am currently viewing at the URL specified above. Falkon seems to generate file names for downloading which are completely different to the file names of the image files that are specified in the HTML code of the above-mentioned URL. But the HTML code of this URL contains file names which have the *.png file extension. That's strange: I just repeated the steps mentioned above, but this time the file name of the image file I could download to my hard disk has the *.png file extension. Note that I am currently on a slightly different URL, i. e. https://www.deutschlandfunk.de/ SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477143] Segmentation fault when closing Falkon (every time?)
https://bugs.kde.org/show_bug.cgi?id=477143 --- Comment #1 from Jens Radloff --- Since I changed the URL which successfully applies Internet searches using the Startpage.com in the address bar, as described in bug report 477142 (https://bugs.kde.org/show_bug.cgi?id=477142), the segmentation fault which I reported here in this bug report does not occur anymore. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of previous default search engine) is displayed there + searche
https://bugs.kde.org/show_bug.cgi?id=477142 --- Comment #2 from Jens Radloff --- The search URL which I specified in my last comment is taken from this URL: https://support.startpage.com/hc/en-us/articles/4520913488148-Search-strings-adding-Startpage-to-unsupported-web-browsers An extra information to the initial description of the behavior described in the first post in this bug report: The behavior as described above occurs even if the option "Search with Default Engine" is activated in menu Edit > Preferences > Tabs > Adress Bar. Note here that the pattern "Search with Default Engine" is a quote from the Falkon GUI, this pattern should get corrected to "Search with default search engine" - the word "search" should be added, and the pattern "default search engine" does not require capital letters at the beginning of each word in it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of previous default search engine) is displayed there + searche
https://bugs.kde.org/show_bug.cgi?id=477142 Jens Radloff changed: What|Removed |Added Summary|Search bar next to address |Search bar next to address |bar: Icon of new default|bar: Icon of new default |search engine is not|search engine is not |displayed there + text |displayed there + text |"DuckDuckGo" (name of |"DuckDuckGo" (name of |standard search engine) is |previous default search |displayed there + searches |engine) is displayed there |in address bar get executed |+ searches in address bar |using DuckDuckGo|get executed using ||DuckDuckGo -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of standard search engine) is displayed there + searches in add
https://bugs.kde.org/show_bug.cgi?id=477142 --- Comment #1 from Jens Radloff --- The above-mentioned URL parameter in the Startpage.com settings which defines a new search engine entry via menu Edit > Preferences > Other > Manage search engines has a wrong value. With this value searches using the Startpage search engine entry in the search bar do not work. I cannot remember how I generated the wrong value for the URL parameter which I specified above. Is this wrong value maybe a preset value by Falkon? These values for the parameters for a Startpage search engine entry work, i. e. searches with Startpage through the search bar execute successful searches by Startpage.com: Name: StartPage URL: https://www.startpage.com/sp/search?query=%s Post data: Shortcut: sp -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477105] All buttons are missing in the Navigation Toolbar
https://bugs.kde.org/show_bug.cgi?id=477105 --- Comment #2 from Jens Radloff --- Hi, I installed the following breeze-related non-dev, non-gtk, non-xfce and non-Gnome icon packages from the Debian repositories for Debian 12: - breeze-icon-theme-rcc - qml-module-org-kde-qqc2breezestyle After each installation of one of these packages I logged out from KDE and logged again into KDE, then each time I started Falkon - but each time the buttons which are subject to this bug report here were not displayed. When I search for all packages which are installed or are available in/for my Debian 12 installation using the command "apt list *icon*", this command returns 172 installed or installable packages. Viewing the names of these 172 packages I know about some packages that they are not used by Falkon, like packages related to gtk or Gnome. But there are too many package names left where I do not (exaktly) know if Falkon could make use of them to display the missing buttons as described in this bug report. And I do not know how to search the source code of Falkon which I cloned from github for information about the name(s) of Debian package(s) that could be necessary to let Falkon display the buttons mentioned in this bug report. Do you have any suggestions how I could search the Falkon source code for possibly missing Debian packages on my machine? > or check how the icons are configured for Qt programs. I do not know how to do that. And could it be possible that I would need to install one or more certain *-dev packages to use them for re-compilation of Falkon against these unknown *-dev packages? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477143] Segmentation fault when closing Falkon (every time?)
https://bugs.kde.org/show_bug.cgi?id=477143 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477143] New: Segmentation fault when closing Falkon (every time?)
https://bugs.kde.org/show_bug.cgi?id=477143 Bug ID: 477143 Summary: Segmentation fault when closing Falkon (every time?) Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- Often or maybe always, when I close the Falkon window the KDE application Dr Konqi returns this information: "Unfortunately the program has been stopped unexpectedly" (translated by myself from German into English). I let Dr Konqi start to collect information for a bug report. This is the result: "Application: Falkon (falkon), signal: Segmentation fault [KCrash Handler] #4 0x7fb4cf6e8a2a in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb4d02ff2a1 in History::resetHistory() () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #6 0x7fb4d03e1ba1 in History::clearHistory() () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #7 0x7fb4d037a442 in MainApplication::saveSettings() () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #8 0x7fb4d0352e53 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (MainApplication::*)()>::call(void (MainApplication::*)(), MainApplication*, void**) () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #9 0x7fb4d0352c69 in void QtPrivate::FunctionPointer::call, void>(void (MainApplication::*)(), MainApplication*, void**) () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #10 0x7fb4d0352859 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /home/xxx/programme/falkon_git_clone/falkon/bin/lib/x86_64-linux-gnu/libFalkonPrivate.so.3 #11 0x7fb4cf6e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fb4cf6b07ea in QCoreApplication::aboutToQuit(QCoreApplication::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb4cf6b4b49 in QCoreApplicationPrivate::execCleanup() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb4cf6b82f0 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x55dbf24d780a in main () [Inferior 1 (process 4952) detached]" Dr Konqi states: "The collected information about the crash is probably useless". Note: I am noticing this behavior often since I recompiled Falkon in the Falkon project directory in my Home directory, where I ran a "make uninstall" in the build directory of my Falkon project directory, a cmake with the "-D BUILD_PYTHON_SUPPORT=ON" option in the cmake command line, then make, make install. During my first compilation of Falkon I did not use the "-D BUILD_PYTHON_SUPPORT=ON" option in the cmake command line. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of standard search engine) is displayed there + searches in add
https://bugs.kde.org/show_bug.cgi?id=477142 Jens Radloff changed: What|Removed |Added Summary|Search bar next to address |Search bar next to address |bar: Icon of new default|bar: Icon of new default |search engine is not|search engine is not |displayed there + text |displayed there + text |"DuckDuckGo" (name of |"DuckDuckGo" (name of |standard search engine) is |standard search engine) is |displayed there + searches |displayed there + searches |in address bar get |in address bar get executed |executing using DuckDuckGo |using DuckDuckGo -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of standard search engine) is displayed there + searches in add
https://bugs.kde.org/show_bug.cgi?id=477142 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477142] New: Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of standard search engine) is displayed there + searches i
https://bugs.kde.org/show_bug.cgi?id=477142 Bug ID: 477142 Summary: Search bar next to address bar: Icon of new default search engine is not displayed there + text "DuckDuckGo" (name of standard search engine) is displayed there + searches in address bar get executing using DuckDuckGo Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- After a fresh installation of Falkon, the standard search engine in Falkon is DuckDuckGo in the search bar next to the address bar at the top of the Falkon browser. An icon at the left edge of the search bar indicates that DuckDuckGo is set as the currently active search engine. I defined an additional search engine via menu Edit > Preferences > Other > Manage search engines: I added the search engine Startpage.com to the list of existing search engines with the following parameters: Name: StartPage URL: https://startpage.com/do/search Post data: query=%s=web=english Shortcut: sp Startpage.com has a unique icon which is shown there. In the list of all available search engines in the "Manage Search Engines - Falkon" window the Startpage.com entry has been set by myself as the default search engine and has been moved to the first (top) position of all search engines in that list. But when you close the "Manage Search Engines - Falkon" window, the search bar at the top of the main Falkon window does not show the icon for the new default search engine Startpage.com, but still the icon for DuckDuckGo plus the text "DuckDuckgo" inside the address bar. And if you type a search term into the address bar and then execute an Internet search, your search gets applied using the DuckDuckGo search engine. This behavior continues to exist if you close Falkon and start Falkon again. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477140] No cut, copy and paste option in context menu in Bookmarks Library window/Bookmark Manager
https://bugs.kde.org/show_bug.cgi?id=477140 Jens Radloff changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477140] New: No cut, copy and paste option in context menu in Bookmarks Library window/Bookmark Manager
https://bugs.kde.org/show_bug.cgi?id=477140 Bug ID: 477140 Summary: No cut, copy and paste option in context menu in Bookmarks Library window/Bookmark Manager Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- In menu Bookmarks > Organize Bookmarks > (a window gets opened with the title "Library" -> shouldn't this window name be "Bookmark Library"?) existing bookmarks and folders cannot get cut, copied nor paste somewhere else in this window using the context menu of the mouse. So you cannot properly sort your bookmarks and folders there. SOFTWARE/OS VERSIONS KDE Plasma: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477105] All buttons are missing in the Navigation Toolbar
https://bugs.kde.org/show_bug.cgi?id=477105 Jens changed: What|Removed |Added CC||s...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 477105] New: All buttons are missing in the Navigation Toolbar
https://bugs.kde.org/show_bug.cgi?id=477105 Bug ID: 477105 Summary: All buttons are missing in the Navigation Toolbar Classification: Applications Product: Falkon Version: 24.01.75 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: s...@mailbox.org Target Milestone: --- The graphical representations of all buttons like "the Back", "Forward" and "Reload" button are not displayed in the Navigation Toolbar, but if you move the mouse over the places where they should be displayed, you notice that their respective positions in the Navigation Toolbar already have been defined. Because either you see the respective tooltip of the respective button, and/or you see the edges of a rectangular area ofd the respective position where the respective button should be displayed. And when you click these invisible buttons they do what they are expected to do. Additionally, if you want to open a new tab next to an existing tab, you can do that by left-clicking on a invisible button right to the right edge of the tab indicator of the mostly right positioned tab. If you move your mouse over that position, you see a tooltop with the text "New Tab". SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #9 from Jens --- (In reply to Juraj from comment #8) > Falkon uses QtWebEngine and not QtWebkit. Thank you for this clarification. Until now I mixed up these two browser rendering engines / I did not know that there is another renedering web engine called QTWebEngine. > Yes, I can confirm that this happens with Qt5 based Falkon. > Will be fixed in Qt6 variant. OK. So this bug report here cannot be closed yet, because when QT6 will have been released one day in a first final version, this future version of QT needs to be checked against this bug report, right? > This is due to using older Chromium version as a base and the website > expects the "latest" version (the web developers do not care about backwards > compatibility) I guess, here you are referring to a future QTWebEngine that will have been built against a final version of QT6, right? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #7 from Jens --- Yes, the behavior as described in this bug report issue occurs, too, if the source code of Falkon has been configured using cmake with the configuration option "-D BUILD_PYTHON_SUPPORT=ON" + has been compiled and re-installed again. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #6 from Jens --- Update: - Installed QtWebEngine/QtWebKit version: 5.15.13 - this is the QtWebkit version provided by Debian 12 packages - Falkon source code configured again using cmake, this time with the "-D BUILD_PYTHON_SUPPORT=ON" option. I then re-compiled and re-installed the compiled binaries. I will now check if the behavior still occurs, as described in this bug report - I am not able to compile the latest available source code of Qtwebkit (via a git clone) because cmake configuration requires Python 2 for this source code, but Debian 12 does not provide Python 2 packages anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476961] New: Small panels cover maximized windows
https://bugs.kde.org/show_bug.cgi?id=476961 Bug ID: 476961 Summary: Small panels cover maximized windows Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jens.ra...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY In 5.27.80, small panels, i.e. not covering the whole screen width or height, do not reduce the window maximization size. This causes window content to be drawn underneath the panels and some content to be unreachable. This is a regression from the previous versions. STEPS TO REPRODUCE 1. Add a horizontal or vertical panel to the workspace on a side where no panel is currently used. 2. Set size to "Fit content" OBSERVED RESULT Maximized windows are using the full screen size. Small panels are covering them. EXPECTED RESULT The size of maximized windows is reduced by small panels. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-zen2-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B89 System Version: 1.0 ADDITIONAL INFORMATION Use case: Two vertical panels at top left and bottom left positions of the workspace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476931] Screen rotation rendering quality regression
https://bugs.kde.org/show_bug.cgi?id=476931 --- Comment #3 from Jens Ramke --- Is it maybe still using the original vertical resolution of 1440 pixels instead of 2560 (rotated)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476931] Screen rotation rendering quality regression
https://bugs.kde.org/show_bug.cgi?id=476931 --- Comment #2 from Jens Ramke --- Created attachment 163114 --> https://bugs.kde.org/attachment.cgi?id=163114=edit drm_info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476931] Screen rotation rendering quality regression
https://bugs.kde.org/show_bug.cgi?id=476931 --- Comment #1 from Jens Ramke --- kscreen-doctor output: Output: 1 DP-1 enabled connected priority 2 DisplayPort Modes: 0:2560x1440@60*! 1:2048x1080@60 2:2048x1080@24 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1600x1200@60 7:1280x1024@75 8:1280x1024@60 9:1152x864@75 10:1280x720@60 11:1280x720@60 12:1280x720@50 13:1024x768@75 14:1024x768@60 15:800x600@75 16:800x600@60 17:720x576@50 18:720x480@60 19:640x480@75 20:640x480@60 21:640x480@60 Geometry: 0,0 1440x2560 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476931] New: Screen rotation rendering quality regression
https://bugs.kde.org/show_bug.cgi?id=476931 Bug ID: 476931 Summary: Screen rotation rendering quality regression Classification: Plasma Product: kwin Version: 5.27.80 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: jens.ra...@gmail.com Target Milestone: --- Created attachment 163113 --> https://bugs.kde.org/attachment.cgi?id=163113=edit OBS recording in full resolution SUMMARY Since version 5.27.80, 90° screen rotation with nvidia GPU leads to distorted text and cursor rendering. 180° rotation is not affected. STEPS TO REPRODUCE 1. Install 5.27.80 alpha on system with nvidia GPU 2. Rotate screen 90° left or right OBSERVED RESULT Screen content, especially fonts and cursors are rendered in lower resolution. Straight, angled lines are visibly jagged with crawling pixels when moving. EXPECTED RESULT Rotated screen content is rendered in full resolution like in previous versions (5.27). SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-zen2-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Graphics driver: nvidia-beta-dkms 545.29.02-1 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B89 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 476853] New: Markup doesn't accept non-anglican characters
https://bugs.kde.org/show_bug.cgi?id=476853 Bug ID: 476853 Summary: Markup doesn't accept non-anglican characters Classification: Applications Product: ghostwriter Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: ohy...@disroot.org Target Milestone: --- Words ending in Å, Ä or Ö are not correctly rendered when put within Markdown symbols like for bold "**text+å**" *** STEPS TO REPRODUCE 1. Write a word ending in "å" 2. Try to use **+** to make it format to bold text OBSERVED RESULT The markdown presents as "not bold" text. If you remove the foreign symbol it does turn to proper markdown rendering EXPECTED RESULT That markdown should show correctly SOFTWARE/OS VERSIONS Linux: Garuda Linux Latest Plasma ADDITIONAL INFORMATION Key here is that like many who do not speak English natively I have my system set to use English as a language to make it easier to repair or fix small bugs (searching in English provides more results). So Ghostwriter may perhaps see my native use of å, ä and ö as foreign characters not to be included. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #5 from Jens --- Created attachment 163047 --> https://bugs.kde.org/attachment.cgi?id=163047=edit 3: LibreWolf - Having clicked the red play button -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #4 from Jens --- Created attachment 163046 --> https://bugs.kde.org/attachment.cgi?id=163046=edit 2: LibreWolf - Having clicked the play button, turns red, ready to play -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #3 from Jens --- Created attachment 163045 --> https://bugs.kde.org/attachment.cgi?id=163045=edit 1 LibreWolf - Before clicking the play button -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 --- Comment #2 from Jens --- Created attachment 163044 --> https://bugs.kde.org/attachment.cgi?id=163044=edit 3: Falkon - Having clicked the red play button -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836 Jens changed: What|Removed |Added CC||arbeitosau...@arcor.de --- Comment #1 from Jens --- Created attachment 163043 --> https://bugs.kde.org/attachment.cgi?id=163043=edit 2: Falkoon - Having clicked the play button, turns red, ready to play -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 476836] New: Preview area of linked audio file behaves unexpected in Mastodon frontend
https://bugs.kde.org/show_bug.cgi?id=476836
Bug ID: 476836
Summary: Preview area of linked audio file behaves unexpected
in Mastodon frontend
Classification: Applications
Product: Falkon
Version: 24.01.75
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: arbeitosau...@arcor.de
Target Milestone: ---
Created attachment 163042
--> https://bugs.kde.org/attachment.cgi?id=163042=edit
1: Falkon - before clicking the play button
On the Mastodon instance where my Mastodon account is located, within a certain
Mastodon post ("toot") the preview area of a remote audio file behaves
unexpected in my timeline in the Falkon browser. In that post the remote audio
file is specified by an URL pointing to a remote server.
I guess this behavior does not only affect this single Mastodon post, but all
Mastodon posts containing links to audio files on remote servers, at least to
https://www.deutschlandfunk.de/.
The behavior can be described as follows:
The preview area in the above-mentioned Mastodon post contains a play button in
the middle of the preview area. The preview area is correctly displayed before
clicking the play button. If you click the play button, the play button turns
into another color (red), something which must be intended by the Mastodon
software, but at the same time the size of the preview window gets drastically
reduced in vertical perspective, and the play button nearly disappears at the
upper edge of the preview area.
If you then click the red play button, the audio file gets played (and you can
hear its content), but the vertical size of the preview area is still
drastically reduced.
In the LibreWolf browser (version 119.0.1-1) instead, the preview area in this
Mastodon post does change in its vertical size when you click the play button
for the first time (then the play button turns red, but audio is not played
yet), and when you then click the red audio button, the size of the preview
area does not get altered, and the audio file is played.
See the attached six screenshots.
This is the URL of the Mastodon post where I noticed the behavior as described
above in the Falkon browser:
https://sueden.social/@wikinaut@berlin.social/111391448082255253
The Mastodon version on the Mastodon instance where my Mastodon account is
located is 4.2.1.
I found this information in the web site source text of my Mastodon instance:
"https://github.com/mastodon/mastodon","version":"4.2.1;
The following MPRIS-related Debian 12 packages are installed on my machine:
libmpris-qt5-1/stable,now 1.0.6-2 amd64 [Installiert,automatisch]
libmpris-qt5-dev/stable,now 1.0.6-2 amd64 [installiert]
mopidy-mpris/stable,now 3.0.3-1 all [installiert]
mpv-mpris/stable,now 0.7.1-1 amd64 [installiert]
qml-module-org-nemomobile-mpris/stable,now 1.0.6-2 amd64 [installiert]
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 12.2
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 476706] New: There is no indication if a process is terminated when using --hold
https://bugs.kde.org/show_bug.cgi?id=476706 Bug ID: 476706 Summary: There is no indication if a process is terminated when using --hold Classification: Applications Product: konsole Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ct...@dentrassi.de Target Milestone: --- SUMMARY When using `--hold` (or `--no-close`) a tab of a process will remain open (which is expected). But there is no indication if the process is still running or not. STEPS TO REPRODUCE 1. run `konsole --hold -e true` 2. try to figure out of `true` is still running or not OBSERVED RESULT No indication seen. EXPECTED RESULT I would expect that there is a message like with other terminals: ``` The process is terminated … do X in order to close this tab. ``` And/or some visual indication on the tab's label. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-200.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 473835] New: disable auto-suspend for VMs by default to avoid virtio hang
https://bugs.kde.org/show_bug.cgi?id=473835 Bug ID: 473835 Summary: disable auto-suspend for VMs by default to avoid virtio hang Classification: Plasma Product: Powerdevil Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: peter...@redhat.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When running KDE Plasma in a VM with virt-manager for example virtio graphics is used by default which does not work with suspend currently. This causes the VM to hang hard after 15min idle by default. It would be better to disable auto-suspend when Plasma is running in a VM by default. I believe that GNOME 45 will do this too (at least for Fedora 39). Downstream bug is https://bugzilla.redhat.com/show_bug.cgi?id=2232711 STEPS TO REPRODUCE 1. Install Fedora KDE Plasma in a VM with virt-manager (with virtio driver) 2. Login and leave Plasma idle for 15min OBSERVED RESULT 2. VM tries to suspend and hangs hard. EXPECTED RESULT Avoid auto-suspending by default in a VM where it is less useful anyway. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 39 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION powerdevil-5.27.7 (Lol managed to hit this bug while writing the report ;o) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043
--- Comment #3 from Jens Ramke ---
Application: Dolphin (23.08.0)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-zen2-xanmod1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Dolphion crashes after F4 is pressed to open Konsole.
The crash can be reproduced every time.
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fb2bc77197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1151
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7fb29845b144 in Konsole::Screen::setReplMode(int)
(this=0x55998aeb8310, mode=3) at
/usr/src/debug/konsole/konsole-23.08.0/src/Screen.cpp:2395
#11 0x7fb298476fdb in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int)
(this=, tokenSize=, terminator=7) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:1080
#12 0x7fb298467290 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) (this=this@entry=0x55998b8745c0,
newState=newState@entry=Konsole::Vt102Emulation::Ground, cc=cc@entry=7) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:434
#13 0x7fb29846761c in
Konsole::Vt102Emulation::receiveChars(QVector const&)
(this=0x55998b8745c0, chars=) at
/usr/src/debug/konsole/konsole-23.08.0/src/Vt102Emulation.cpp:900
#14 0x7fb298441bea in Konsole::Emulation::receiveData(char const*, int)
(this=0x55998b8745c0, text=0x55998b950d68 "\033]133;C\a", length=8) at
/usr/src/debug/konsole/konsole-23.08.0/src/Emulation.cpp:233
#15 0x7fb2bbad1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffea7efb800, r=, this=0x55998b879dd0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x55998b8773c0,
signal_index=17, argv=0x7ffea7efb800) at kernel/qobject.cpp:3925
#17 0x7fb29842f93b in Konsole::Pty::receivedData(char const*, int)
(this=, _t1=, _t2=) at
/usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154
#18 0x7fb2984477c9 in Konsole::Pty::dataReceived() (this=0x55998b8773c0) at
/usr/src/debug/konsole/konsole-23.08.0/src/Pty.cpp:101
#19 0x7fb2bbad1637 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffea7efb8d0, r=, this=0x55998b879c90, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x55998b877440,
signal_index=3, argv=0x7ffea7efb8d0) at kernel/qobject.cpp:3925
#21 0x7fb2a20200c7 in KPtyDevicePrivate::_k_canRead() (this=0x55998b82d150)
at /usr/src/debug/kpty/kpty-5.109.0/src/kptydevice.cpp:291
#22 0x7fb2a2020369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7ffea7efba60,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7ffea7efba60) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7fb2bbad17f3 in doActivate(QObject*, int, void**)
(sender=0x55998b8795b0, signal_index=5, argv=0x7ffea7efba60) at
kernel/qobject.cpp:3937
#25 0x7fb2bbad2ea9 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x55998b8795b0,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7fb2bbad2f9b in QSocketNotifier::event(QEvent*) (this=0x55998b8795b0,
e=) at kernel/qsocketnotifier.h:115
#27 0x7fb2bc77893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55998b8795b0, e=0x7ffea7efbb70) at
kernel/qapplication.cpp:3640
#28 0x7fb2bba9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55998b8795b0, event=0x7ffea7efbb70) at
kernel/qcoreapplication.cpp:1064
#29 0x7fb2bbaea276 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x55998aada720) at kernel/qeventdispatcher_glib.cpp:107
#30 0x7fb2b9b0fa31 in g_main_dispatch (context=0x7fb2bee0) at
../glib/glib/gmain.c:3460
#31 g_main_context_dispatch (context=0x7fb2bee0) at
../glib/glib/gmain.c:4200
#32 0x7fb2b9b6ccc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7fb2bee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#33 0x7fb2b9b0d0e2 in g_main_context_iteration (context=0x7fb2bee0,
may_block=1) at ../glib/glib/gmain.c:4343
#34
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 Jens Ramke changed: What|Removed |Added Summary|Yakuake crash on command|Embedded Konsole crash on |execution |command execution Version|23.07.80|23.08.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Yakuake crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 --- Comment #1 from Jens Ramke --- Also happens when konsole is opened in dolphin with F4 (right away due to cd, I think), which crashes dolphin. Does _not_ happen if konsole is opened directly. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 473043] New: Yakuake crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043
Bug ID: 473043
Summary: Yakuake crash on command execution
Classification: Applications
Product: yakuake
Version: 23.07.80
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: jens.ra...@gmail.com
Target Milestone: ---
Application: yakuake (23.07.80)
Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.8-zen2-xanmod1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Yakuake crashes each time Enter is pressed after typing a command, like "ls",
"grep", "htop" etc.
The crash can be reproduced every time.
-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f763d57197b in QScopedPointer >::operator->() const (this=)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1149
#8 QAction::d_func() (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#9 QAction::setVisible(bool) (this=0x0, b=true) at kernel/qaction.cpp:1051
#10 0x7f7627ed40a4 in Konsole::Screen::setReplMode(int)
(this=0x560c8bb68680, mode=3) at
/usr/src/debug/konsole/konsole-23.07.80/src/Screen.cpp:2395
#11 0x7f7627eeff6b in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int)
(this=, tokenSize=, terminator=7) at
/usr/src/debug/konsole/konsole-23.07.80/src/Vt102Emulation.cpp:1080
#12 0x7f7627ee0220 in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) (this=this@entry=0x560c8c12f3c0,
newState=newState@entry=Konsole::Vt102Emulation::Ground, cc=cc@entry=7) at
/usr/src/debug/konsole/konsole-23.07.80/src/Vt102Emulation.cpp:434
#13 0x7f7627ee05ac in
Konsole::Vt102Emulation::receiveChars(QVector const&)
(this=0x560c8c12f3c0, chars=) at
/usr/src/debug/konsole/konsole-23.07.80/src/Vt102Emulation.cpp:900
#14 0x7f7627ebab8a in Konsole::Emulation::receiveData(char const*, int)
(this=0x560c8c12f3c0, text=0x560c8c221b08 "\033]133;C\a", length=8) at
/usr/src/debug/konsole/konsole-23.07.80/src/Emulation.cpp:233
#15 0x7f763c8d0807 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff84b92d40, r=, this=0x560c8bef62e0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#16 doActivate(QObject*, int, void**) (sender=0x560c8bdf8900,
signal_index=17, argv=0x7fff84b92d40) at kernel/qobject.cpp:3925
#17 0x7f7627ea88cb in Konsole::Pty::receivedData(char const*, int)
(this=, _t1=, _t2=) at
/usr/src/debug/konsole/build/src/konsoleprivate_autogen/EWIEGA46WW/moc_Pty.cpp:154
#18 0x7f7627ec0769 in Konsole::Pty::dataReceived() (this=0x560c8bdf8900) at
/usr/src/debug/konsole/konsole-23.07.80/src/Pty.cpp:101
#19 0x7f763c8d0807 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff84b92e10, r=, this=0x560c8bef61a0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x560c8bdf8980,
signal_index=3, argv=0x7fff84b92e10) at kernel/qobject.cpp:3925
#21 0x7f76344ab0c7 in KPtyDevicePrivate::_k_canRead() (this=0x560c8beadf80)
at /usr/src/debug/kpty/kpty-5.108.0/src/kptydevice.cpp:291
#22 0x7f76344ab369 in KPtyDevice::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_c=, _a=0x7fff84b92fa0,
_id=, _o=) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7fff84b92fa0) at
/usr/src/debug/kpty/build/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7f763c8d09c3 in doActivate(QObject*, int, void**)
(sender=0x560c8bdf8a90, signal_index=5, argv=0x7fff84b92fa0) at
kernel/qobject.cpp:3937
#25 0x7f763c8d2079 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x560c8bdf8a90,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:185
#26 0x7f763c8d216b in QSocketNotifier::event(QEvent*) (this=0x560c8bdf8a90,
e=) at kernel/qsocketnotifier.h:115
#27 0x7f763d57893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x560c8bdf8a90, e=0x7fff84b930b0) at
kernel/qapplication.cpp:3640
#28 0x7f763c89b8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x560c8bdf8a90, event=0x7fff84b930b0) at
kernel/qcoreapplication.cpp:1064
#29 0x7f763c8e9496 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x560c8b975900) at kernel/qeventdispatcher_glib.cpp:107
#30 0x7f763b081a31 in g_main_dispatch
[digikam] [Bug 471015] New: Error messages in Panorama tool incomplete because window contents cannot scroll
https://bugs.kde.org/show_bug.cgi?id=471015 Bug ID: 471015 Summary: Error messages in Panorama tool incomplete because window contents cannot scroll Classification: Applications Product: digikam Version: 8.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-Panorama Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- Created attachment 159646 --> https://bugs.kde.org/attachment.cgi?id=159646=edit error message output with actual error far down the text SUMMARY: see $SUBJECT STEPS TO REPRODUCE 1. Select a few images that cannot be processed as panorama 2. Try it anway 3. Wait for the "hugin_executor" error message display OBSERVED RESULT The error message output is too long for the window content but cannot be scrolled, so it is truncated. Maximizing the window helps, but only to a certain extent and probably only because I have a 27" screen. EXPECTED RESULT The error message should be completely visible, and - possibly - the actual error (see screenshot, it is far down the text) should be highlighted, and/or shown first. SOFTWARE/OS VERSIONS: KDE Neon 22.04 with Digikam appimage 2023-06-13. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #5 from Jens --- Thanks! I can confirm an Appimage update did the trick. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #3 from Jens --- digiKam-8.1.0-20230416T171333-x86-64_01d0723f008a295794bb4ed3dde25ca4.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 --- Comment #2 from Jens --- https://invent.kde.org/graphics/digikam/commit/37193a9cf14141ff119ac468dae6c74dd061d8b2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469963] New: Keyboard shortcuts not saved
https://bugs.kde.org/show_bug.cgi?id=469963 Bug ID: 469963 Summary: Keyboard shortcuts not saved Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Keyboard Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. Open keyboard shortcuts editor 2. Modify shortcuts, e.g. "Space bar = Preview" and "Next image = PgDown" (instead of Spacebar) 3. Save, and test 4. Quit, restart Digikam, then test again OBSERVED RESULT After step 3, the modified shortcuts work. After step 4, they don't work any more. So they are not saved to disk in a persistent way. EXPECTED RESULT Modified shortcuts should persist across Digikam sessions, reboots, etc. SOFTWARE/OS VERSIONS: KDE Neon with KDE Plasma 22.04 with all updates applied Digikam current Appimage 8.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393158] Geolocation Editor does not show existing Location tags
https://bugs.kde.org/show_bug.cgi?id=393158 --- Comment #10 from Jens --- Yes, still valid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377228] Assign only deepest level reverse geotag to image to avoid tag spam
https://bugs.kde.org/show_bug.cgi?id=377228 --- Comment #15 from Jens --- Yes, I saw. That's great. How about old images? Was the location metadata also written previously (in addition to tags), or is it possible to write location metadata to all images that have location tags in a batch? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 --- Comment #10 from Jens Küspert --- As it seems, there are applications involved: $ akonadiconsole akonadiconsole: error while loading shared libraries: libKF5TextAutoCorrection.so.1: cannot open shared object file: No such file or directory $ kalendar QML debugging is enabled. Only use this in a safe environment. QQmlApplicationEngine failed to load component qrc:/main.qml:19:1: plugin cannot be loaded for module "org.kde.kalendar.mail": Cannot load library /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kalendar/mail/libkalendar_mail_plugin.so: (libKF5TextAutoCorrection.so.1: cannot open shared object file: No such file or directory) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error
https://bugs.kde.org/show_bug.cgi?id=469599 Jens Küspert changed: What|Removed |Added CC||jens.kuesp...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of image properties sidebar tab.
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #38 from Jens --- Thank you, this is definitely going in the right direction! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377228] Assign only deepest level reverse geotag to image to avoid tag spam
https://bugs.kde.org/show_bug.cgi?id=377228 --- Comment #13 from Jens --- Yes, still valid. (8.1.0-git appimage) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384086] Rotation of some images (JPEG, by Samsung S5 smartphone) during import is incorrect
https://bugs.kde.org/show_bug.cgi?id=384086 --- Comment #12 from Jens --- I cannot say, do you still have the images I sent as an example? I don't have the originals any more. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417709] Copy/clone common metadata (rating, location, tags, ...) when creating panorama image
https://bugs.kde.org/show_bug.cgi?id=417709 --- Comment #9 from Jens --- Still valid with 8.1.0-git appimage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468917] Settings for Icon-Distance in the Systemtray in tablet-mode not changeable
https://bugs.kde.org/show_bug.cgi?id=468917 --- Comment #4 from Jens Küspert --- Thanks for the suggestion – this helps a little bit. But I still can't see, why this shouldn't be configurable. Anyway, thanks for your consideration. Regard this bug as closed, if you wish. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468917] Settings for Icon-Distance in the Systemtray in tablet-mode not changeable
https://bugs.kde.org/show_bug.cgi?id=468917 --- Comment #2 from Jens Küspert --- Not everyone is using the tablet just with their fingers. I'm using a pen and don't need this extra space. As a default the spacing is OK, but it should be possible to change that. --> Simple by Default, Powerful when Needed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468917] Settings for Icon-Distance in the Systemtray in tablet-mode not changeable
https://bugs.kde.org/show_bug.cgi?id=468917 Jens Küspert changed: What|Removed |Added Summary|Settings for Icon-Distanc |Settings for Icon-Distance |in the Systemtray in|in the Systemtray in |tablet-mode not changeable |tablet-mode not changeable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468917] New: Settings for Icon-Distanc in the Systemtray in tablet-mode not changeable
https://bugs.kde.org/show_bug.cgi?id=468917 Bug ID: 468917 Summary: Settings for Icon-Distanc in the Systemtray in tablet-mode not changeable Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: jens.kuesp...@posteo.de CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 158393 --> https://bugs.kde.org/attachment.cgi?id=158393=edit Screenshot of Settingspage (in German) STEPS TO REPRODUCE 1. Activate Tablet-Mode 2. Open Settings for Systemtray 3. In "General" it should be possible to change the distance-setting. OBSERVED RESULT It is greyed out as "Large" EXPECTED RESULT It should be possible to change the setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 22.04 KDE Plasma Version: 5.27.4 (see above) KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468714] New: Enhancements for Photo Grouping in Image View
https://bugs.kde.org/show_bug.cgi?id=468714 Bug ID: 468714 Summary: Enhancements for Photo Grouping in Image View Classification: Applications Product: digikam Version: 8.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Albums-ItemGroup Assignee: digikam-bugs-n...@kde.org Reporter: jens_westeme...@web.de Target Milestone: --- Grouping of images is a very useful feature for me. I have several images of type .orf, .arw and corresponding .jpg and .tif in my albums and I group them by name and can apply geo-data, tags, ratings, ... consistently. But I have some enhancement requests (or need some help to find it if already exists): 1. Order of grouped images. After importing photos, I select all of them and do grouping by name. I know how to (by selecting single images in right sequence) control this by grouping single images, but I would like to define an order in case of multiple groupings (e.g. .tif top, .jpg second, .arw/.orf third, ) to always see the developed image version first. 2. Filtering of grouped images. If I filter for raw data, only the .arw images appear (the .orf images are second in stack). I would like to see all raw images of all grouped images for further processing. Always doing ungroup / group operations for filtering is annoying. 3. Drag support for groups. I can copy/move all images of a group within digiKam. But when I drag a group into an external application (all 5 raw images of a series for HDR processing), only the first image moves over. Filtering for raw (see top 2) and drag the whole stack to an external program would be helpful. 4. Grouping along Timelaps / Burst I don't know how this is supposed to work. The images of one bursts have different names, grouping along date works mostly, but requires re-check. Thanks for this great tool. Greetings, Jens -- You are receiving this mail because: You are watching all bug changes.
