[kwin] [Bug 486948] Repeated segmentation fault crashes in various KWin::EffectWindow related functions
https://bugs.kde.org/show_bug.cgi?id=486948 --- Comment #7 from Adam L --- Created attachment 170089 --> https://bugs.kde.org/attachment.cgi?id=170089=edit Backtrace 7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483793] With certain scale factors, popup flickers rapidly on hover, changing between two sizes or other graphical glitches
https://bugs.kde.org/show_bug.cgi?id=483793 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #3 from Adam Fontenot --- I see this issue at 1:1 (no scaling). It's not especially reliable. I do seem to only see it when moving the cursor from an adjacent VD, but it only starts happening ~20% of the time. Once it starts happening, it will continue as long as you move the cursor quickly enough that the preview doesn't get reset. Extremely visually annoying and probably an epilepsy risk for some users. Seems to flicker at exactly the monitor rate (every other frame at 60 fps). Operating System: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487715] New: alt-d-s shortcut to open desktop settings does nothing until you click on the desktop once (Plasma 6.0.90)
https://bugs.kde.org/show_bug.cgi?id=487715 Bug ID: 487715 Summary: alt-d-s shortcut to open desktop settings does nothing until you click on the desktop once (Plasma 6.0.90) Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: ad...@happyassassin.net Target Milestone: --- SUMMARY When first starting a Plasma 6.0.90 desktop, if you hit alt-d-s without doing anything else, it doesn't launch Desktop Settings as it should. However, e.g. alt-f2 does work to open a launcher dialog. If you click on the desktop once, alt-d-s now works as expected. I guess this is a focus issue? STEPS TO REPRODUCE 1. Log into a clean Plasma 6.0.90 desktop (tested on Fedora Rawhide) 2. Immediately, without doing anything else, hit alt-d-s 3. Now click once on the desktop and hit alt-d-s again OBSERVED RESULT First alt-d-s does not launch desktop settings, second one does EXPECTED RESULT First alt-d-s should launch desktop settings SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide, Plasma 6.0.90 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487595] Breeze icon theme uses copyrighted icons without acknowledgement or compliance with the owners' guidelines
https://bugs.kde.org/show_bug.cgi?id=487595 --- Comment #2 from Adam Williamson --- The icon you are using for Facebook *is* the 'f' from the Facebook logo, isolated from the rest of the Facebook logo and with its color changed, both against Facebook's guidelines for using the logo - https://about.meta.com/brand/resources/facebook/logo/ . It is copyrighted, obviously, by Meta, and is definitely not under the LGPL. "However, a few companies provide their own icon graphic for various sizes, in which case, we should simply copy/paste into the icon collection for our system." I really think you need to refer this to an actual lawyer. I can refer you to Red Hat's legal team if it would help. You cannot assume you are legally permitted to just "copy/paste" an icon whose copyright is owned by someone else into your project, because that isn't the case. It is legally equivalent to copying the entire text of a popular novel, or the entirety of Taylor Swift's latest song, into your project. If you don't have their permission to do it, you can get in trouble. Brands typically focus on typical promotional activities when publishing guidelines that provide implicit permission to reuse their branding in certain cases - for e.g. the Facebook guidelines I posted are highly focused on marketing things like including the logo in a business website. When the guidelines don't cover your case, the safest course is to assume you have *no* permission to use or redistribute the copyrighted material, because that's typically how the law works. It's never safe to assume you can just redistribute somebody else's copyright material, and it's certainly never safe to imply that *you* created it, and it's under the LGPL, if it isn't. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Implement feature to disable touchpad when mouse is plugged in when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Adam Beer changed: What|Removed |Added CC||a.beer_...@live.ca -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487595] New: Breeze icon theme uses copyrighted icons without acknowledgement or compliance with the owners' guidelines
https://bugs.kde.org/show_bug.cgi?id=487595 Bug ID: 487595 Summary: Breeze icon theme uses copyrighted icons without acknowledgement or compliance with the owners' guidelines Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: ad...@happyassassin.net CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY The breeze icon theme repo includes https://github.com/KDE/breeze-icons/blob/master/COPYING-ICONS , which appears to describe the copyright claims for icons in the repository. It seems to claim that all the icons are original works and copyrighted under the LGPL. However, this is clearly not true. For example, breeze-icons/icons/actions/22/im-skype.svg is very clearly a modified version of Microsoft's Skype icon. This is copyrighted by Microsoft, and is very definitely not under the LGPL. Also, Microsoft provides a restrictive set of "brand guidelines" for Skype - currently at https://secure.skypeassets.com/content/dam/scom/pdf/skype_brand_guidelines.pdf - which specifically states "Do not alter the Skype icon in any way, including changing the colors, angle, or dimensions", but Breeze has made it monochrome. Similarly, breeze-icons/icons/actions/22/im-facebook.svg is a modified version of Facebook's own icon, which again is very definitely not LGPL. And again, this project is also violating the owner's brand guidelines - https://about.meta.com/brand/resources/facebook/logo/ - which specifically state "DON'T change the color of the logo" and "DON'T use just the 'f' from our logo". These are only two examples, there are several others (e.g. im-google.svg ). STEPS TO REPRODUCE 1. Clone the git repo. 2. Read the copyright information. 3. Observe the presence of icons copyrighted by others without acknowledgement or license compliance. OBSERVED RESULT There are lots. EXPECTED RESULT There shouldn't be any. SOFTWARE/OS VERSIONS Irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425154] Setting an application to open application/octet-stream has unexpected behavior
https://bugs.kde.org/show_bug.cgi?id=425154 --- Comment #12 from Adam Fontenot --- Just a quick clarificatory comment, since this bug has received some recent attention. I believe that all inheritance order issues have been fixed along with Bug 475200, including the issue described by D. Debnath above. The remaining issues with file associations are: * Issue where applications receive an *unintended* low level file association, and this leads to unexpected or unwanted behavior, and the underlying cause of the issue isn't surfaced to the user in a helpful way via the File Associations KCM. (That's this issue.) * Issue where certain applications like Okular which provide multiple .desktop files are duplicated in the file association menu, without causing any further harmful effects. (Bug 481473) If anyone finds any other issues with file associations, a new bug should be filed. If files are still opening in Okular by default despite a more direct association being set for the file type, please provide a test case if possible. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476618] kde connect is not reconnecting, manual intervention is necessary to do so
https://bugs.kde.org/show_bug.cgi?id=476618 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 423282] KDE connect disconnects from android phone (oneplus/huawei ...)
https://bugs.kde.org/show_bug.cgi?id=423282 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 382365] kdeconnect does not connect automatically
https://bugs.kde.org/show_bug.cgi?id=382365 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 465582] Kde Connect doen't reconnect
https://bugs.kde.org/show_bug.cgi?id=465582 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477670] KDEConnect is unable to connect to paired devices after sleep
https://bugs.kde.org/show_bug.cgi?id=477670 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476354] The app will not connect my laptop to my phone a second time. It only works the first time
https://bugs.kde.org/show_bug.cgi?id=476354 Adam Piggott changed: What|Removed |Added CC||kde-bugs@proactiveservices. ||co.uk -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 487024] New: kioworker crashes in thumbnailer when TIFF file is exported from Darktable
https://bugs.kde.org/show_bug.cgi?id=487024 Bug ID: 487024 Summary: kioworker crashes in thumbnailer when TIFF file is exported from Darktable Classification: Frameworks and Libraries Product: kio-extras Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 169481 --> https://bugs.kde.org/attachment.cgi?id=169481=edit kcrash info SUMMARY kioworker crashes whenever I export a TIFF file from Darktable. It appears to be trying to thumbnail an incomplete file, which makes the zlib decoder unhappy. The file itself is fine, and a thumbnail is immediately created and visible in Dolphin as soon as the export is complete. I'm not sure what part of the stack is to blame here. Should the thumbnailer not be attempting to make a thumbnail for a partially saved file? Should libtiff not be attempting to decompress a faulty, incomplete file? Should zlib not be triggering an error condition? STEPS TO REPRODUCE 1. Export a 16 bit TIFF file (compression mode "deflate with predictor") from Darktable; I set the output directory to the Desktop for this test. OBSERVED RESULT Crash in kioworker. No visible result except that kcrash dialogue appears, if installed, for kioworker. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION #4 inflate_fast (strm=strm@entry=0x5f45e25f3d00, start=start@entry=31188) at /usr/src/debug/zlib/zlib-1.3.1/inffast.c:104 #5 0x76e073330735 in inflate (strm=strm@entry=0x5f45e25f3d00, flush=flush@entry=1) at /usr/src/debug/zlib/zlib-1.3.1/inflate.c:1029 #6 0x76e05f4be4c2 in ZIPDecode (tif=0x5f45e25f89a0, op=, occ=31188, s=) at /usr/src/debug/libtiff/libtiff/libtiff/tif_zip.c:259 #7 0x76e05f4b9d1d in PredictorDecodeRow (tif=0x5f45e25f89a0, op0=0x76dfd477e5a0 "b\264\236\327\377\377\026\005\242", occ0=31188, s=) at /usr/src/debug/libtiff/libtiff/libtiff/tif_predict.c:566 #8 0x76e05f4c3149 in TIFFReadScanline (tif=0x5f45e25f89a0, buf=0x76dfd477e5a0, row=895, sample=) at /usr/src/debug/libtiff/libtiff/libtiff/tif_read.c:458 #9 0x76e0664b27b2 in QTiffHandler::read (this=0x5f45e25f4ea0, image=0x7fff6a0675e0) at /usr/src/debug/qt6-imageformats/qtimageformats-everywhere-src-6.7.0/src/plugins/imageformats/tiff/qtiffhandler.cpp:467 #10 0x76e07173f8e2 in QImageReader::read (this=this@entry=0x7fff6a0675b0, image=image@entry=0x7fff6a0675e0) at /usr/src/debug/qt6-base/qtbase/src/gui/image/qimagereader.cpp:1206 #11 0x76e07173ffca in QImageReader::read (this=this@entry=0x7fff6a0675b0, image=image@entry=0x7fff6a0675e0) at /usr/src/debug/qt6-base/qtbase/src/gui/image/qimagereader.cpp:1278 #12 0x76e06c0625e9 in ImageCreator::create (this=this@entry=0x5f45e252c2e0, request=...) at /usr/src/debug/kio-extras/kio-extras-24.02.2/thumbnail/imagecreator.cpp:92 #13 0x76e0741e59fe in ThumbnailProtocol::createThumbnail (this=this@entry=0x7fff6a067b50, thumbCreator=thumbCreator@entry=0x5f45e26f5df0, filePath=..., width=256, height=height@entry=256, thumbnail=...) at /usr/src/debug/kio-extras/kio-extras-24.02.2/thumbnail/thumbnail.cpp:786 #14 0x76e0741eaefe in ThumbnailProtocol::get (this=0x7fff6a067b50, url=) at /usr/src/debug/kio-extras/kio-extras-24.02.2/thumbnail/thumbnail.cpp:248 #15 0x76e0740bdb04 in ??? () at /usr/lib/libKF6KIOCore.so.6 #16 0x76e0740b965e in ??? () at /usr/lib/libKF6KIOCore.so.6 #17 0x76e074166de4 in ??? () at /usr/lib/libKF6KIOCore.so.6 #18 0x76e0741e7967 in kdemain (argc=, argv=) at /usr/src/debug/kio-extras/kio-extras-24.02.2/thumbnail/thumbnail.cpp:116 #19 0x5f45e13df220 in ??? () #20 0x76e073841d4a in ??? () at /usr/lib/libc.so.6 #21 0x76e073841e0c in __libc_start_main () at /usr/lib/libc.so.6 #22 0x5f45e13df4e5 in ??? () -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485646] OBS problem- recording
https://bugs.kde.org/show_bug.cgi?id=485646 --- Comment #3 from Adam --- Thanks for help -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485646] OBS problem- recording
https://bugs.kde.org/show_bug.cgi?id=485646 --- Comment #2 from Adam --- No one replies on the OBS forum -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485921] Gap between two external displays appearing every time when closing the laptop
https://bugs.kde.org/show_bug.cgi?id=485921 --- Comment #1 from Adam --- Created attachment 168762 --> https://bugs.kde.org/attachment.cgi?id=168762=edit setup before -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 485921] New: Gap between two external displays appearing every time when closing the laptop
https://bugs.kde.org/show_bug.cgi?id=485921 Bug ID: 485921 Summary: Gap between two external displays appearing every time when closing the laptop Classification: Applications Product: systemsettings Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: asiema...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 168761 --> https://bugs.kde.org/attachment.cgi?id=168761=edit setup after closing laptop. SUMMARY I have a setup with 2 external displays and one from my laptop. I only use opened laptop for bootup, then I immediately close it. Every time, since some update, there is a gap between my external monitors after I close the laptop. I need to readjust it manually by pulling the second monitor next to the 1st one. I attached the screenshots with display setup with and without built-in display. In the 3 display setup my built-in screen is to the left, not even between externals. OBSERVED RESULT Setting for two external displays not saving up correctly, gap appearing every time after closing the laptop built-in display. EXPECTED RESULT Setting of two external displays saved. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Fedora Linux 39 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485646] New: OBS problem- recording
https://bugs.kde.org/show_bug.cgi?id=485646 Bug ID: 485646 Summary: OBS problem- recording Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a-boraw...@o2.pl Target Milestone: --- In OBS I have no sound in the recorded video. In speakers and headphones on the front of the panel. The microphone works well. OBS latest 30.1.2 KDE Neon in the latest version with Plasma 6, all updates installed continuously. In Plasma 5.27 there were no problems with this Nvidia drivers ver: 535.171.04 from PPA. Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel: 6.5.0-27 Graphics platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418
--- Comment #2 from Adam Fontenot ---
Thanks for working on this! It took some effort to build against Qt6, but I did
succeed and all the books I've tried so far are working.
Couple of thoughts:
It probably makes sense to synthesize an ID field rather than using the Google
Books ones that look like "GoogleBooks:fnG8BAAAQBAJ".
The URL field has a bunch of useless stuff in it, all of the following links
for this book are previews of the book:
{http://books.google.com/books/download/Ecoregions-sample-epub.acsm?id=fnG8BAAAQBAJ=epub=acs4_fulfillment_token_type=sample=gbs_api
http://books.google.com/books/download/Ecoregions-sample-pdf.acsm?id=fnG8BAAAQBAJ=pdf=acs4_fulfillment_token_type=sample=gbs_api
http://play.google.com/books/reader?id=fnG8BAAAQBAJ==gbs_api}
It would be better to link to the official Google Books page, even if the link
has to be synthesized: https://books.google.com/books?id=fnG8BAAAQBAJ
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 481471] Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??)
https://bugs.kde.org/show_bug.cgi?id=481471 --- Comment #10 from Adam Fontenot --- QA: patch fixes the issue for me when applied on top of 24.02.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448234] Usage of Qt SVG renderer causes some 3rd-party app icons to be mis-rendered
https://bugs.kde.org/show_bug.cgi?id=448234 --- Comment #31 from Adam Fontenot --- Another important 6.7 regression probably worth mentioning here: causes extreme memory use including OOM conditions on some problematic SVG files (I've seen quite a few in the Adwaita theme). I've managed to crash both Dolphin and Gwenview this way after upgrading to 6.7, there will probably be numerous reports by other users about this and we should probably have somewhere to dupe them to... Upstream report I found: https://bugreports.qt.io/browse/QTBUG-124287 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448234] Usage of Qt SVG renderer causes some 3rd-party app icons to be mis-rendered
https://bugs.kde.org/show_bug.cgi?id=448234 --- Comment #29 from Adam Fontenot --- (In reply to Nate Graham from comment #28) > Qt 6.7 is released now. Can anyone using it already see if this is fixed now > for these icons: > - App icons for Monera, Kooha, Cheese, and Solanum > - Oxygen's edit-bomb and document-revert icons Cheese: no Kooha: no Solanum: no Monero: no -> fixed upstream by switching to PNG icons: https://github.com/flathub/org.getmonero.Monero/commit/81541b90924fa23033175dd3a719f3c2c779b3b7 -> original icon is not fixed: https://raw.githubusercontent.com/flathub/org.getmonero.Monero/afa2f2420a52e2da9f0af964dc2069d993f79cb9/extra/org.getmonero.Monero.svg edit-bomb.svgz: looks OK to me? document-revert.svgz: **regression!** - renders worse than shown in Bug 467151 Note that some progress has been made on this change: https://codereview.qt-project.org/c/qt/qtsvg/+/531968 If it gets finished, then that would probably fix most (?) broken icons, although I don't know that it will land before 6.8 or later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478614] Cursor "hit box" is offset under Wayland on QEMU VMs
https://bugs.kde.org/show_bug.cgi?id=478614 Adam Williamson changed: What|Removed |Added CC||ad...@happyassassin.net --- Comment #6 from Adam Williamson --- I'm seeing offset today in Fedora 40 on Wayland with a libvirt VM with virtio graphics :( The usual "real position is slightly lower and to the right of the apparent position" case. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479235] System Monitor crashes in ItemBranchIndicators::paint()
https://bugs.kde.org/show_bug.cgi?id=479235 Adam Williamson changed: What|Removed |Added CC||ad...@happyassassin.net --- Comment #4 from Adam Williamson --- Also affecting Fedora 40 downstream: https://bugzilla.redhat.com/show_bug.cgi?id=2273737 . It's a release blocker candidate ATM. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483970] File properties dialog is missing padding when using Breeze style
https://bugs.kde.org/show_bug.cgi?id=483970 --- Comment #3 from Adam D --- Created attachment 168157 --> https://bugs.kde.org/attachment.cgi?id=168157=edit Bad padding on the edges of System Settings > Display & Monitor > Gamma Thought I'd mention that this is not only properties dialogs. Here's an example of it happening in the system settings under Display & Monitor > Gamma. Most other sections of the System Settings look fine though. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484421] New: KBibTex sometimes loses track of the active element, resulting in shortcuts affecting the wrong item and other issues
https://bugs.kde.org/show_bug.cgi?id=484421 Bug ID: 484421 Summary: KBibTex sometimes loses track of the active element, resulting in shortcuts affecting the wrong item and other issues Classification: Applications Product: KBibTeX Version: 0.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User interface Assignee: fisc...@unix-ag.uni-kl.de Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY After you import a new item via paste, resulting in the selected element automatically changing, this element selection can get "lost" internally, so that ctrl-d will open the document for the previously selected element, ctrl-e will edit the previously selected element. This affects the Element menu item as well. STEPS TO REPRODUCE 1. Open KBT and create a new document. Add a new element. I added a journal paper using the DOI. 2. Add a local PDF to the newly created element. Make sure that the element is selected, and check that ctrl-d opens the PDF as expected. 3. Copy a BiBTeX citation to your clipboard in another application. I copied a citation from KWrite, downloaded from a Google Books page. 4. Paste the citation in KBT by pressing ctrl-v. 5. Observe that the newly created element for the pasted citation is selected in KBT. Click the Element menu item to open the menu. 6. Observe that there is no sub-menu for "View Document", because there is no local file corresponding to the newly created element. Close the sub-menu **by clicking on the Element menu item again**. 7. Observe that in the interface the newly created element remains selected. Immediately press ctrl-e. OBSERVED RESULT The editing window for the **first** element created in the reproduction steps is opened. If you click on the Element menu item, the View Document option will give access to the PDF file, and ctrl-d will open it. In other words, KBT acts as if the wrong element were active in the element selection panel. The true selected element has been lost. This somehow happens *after* the menu is opened in step 5. EXPECTED RESULT The editing window for the newly created element is opened. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland Note: my distribution builds KBT against Qt 5, not Qt 6. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 484418] New: Support for searching and adding book citations (e.g. from Google Books, WorldCat)
https://bugs.kde.org/show_bug.cgi?id=484418 Bug ID: 484418 Summary: Support for searching and adding book citations (e.g. from Google Books, WorldCat) Classification: Applications Product: KBibTeX Version: 0.10 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Network/online search Assignee: fisc...@unix-ag.uni-kl.de Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- User story: I was looking for a lightweight citation and document manager, ideally a native Qt application. I don't need anything as complicated or heavy as Zotero or Evernote (my distribution doesn't package Zotero, anyway). I found KBibTeX and decided to see if it would meet my needs. Most of the time I'm trying to keep track of books (usually physical copies) that I've read, and might need to cite in various places - or even just remember where I might have read something. As it stands, KBT has a lot of features for importing citations from DOIs or other sources like JSTOR, but nothing (as far as I can tell) for automatically creating citations for books using e.g. an ISBN. I attempted to create citations by searching for ISBNs using the Google Scholar engine. In some cases the searches just failed because Scholar indexes articles, not books. In other cases, I was successful in that my searches did return results, but the resulting citations were missing obvious and important fields like "Publisher", "Location", and "ISBN", which are used in most citation styles for books. - Possible solutions: * Google Books is probably the easiest source to add because there's an API for fetching data for ISBNs with no API key required. [1] Downloading a BiBTeX format citation for a given Google Books ID is also trivial. [2] I'm not sure about the relative completeness of various catalogues, so WorldCat might have some books that Google Books lacks. * WorldCat seems to be a common source of citation data for books. For example, Citer [3], an open source web based tool for creating citations on Wikipedia, uses WorldCat as a primary source of data for ISBNs. WorldCat has search results for ISBN values that KBT could display to the user [4], and the source HTML code of each page looks pretty easy to scrape. * Do what I'm doing now, which is attempt to find the exact version of the book on Google Books manually, download a BibTex citation, open the resulting file, and copy and paste the citation into KBT. Pretty painful. [1] https://www.googleapis.com/books/v1/volumes?q=isbn:1493905244 [2] https://books.google.com/books/download/Ecoregions.bibtex?id=fnG8BAAAQBAJ=bibtex [3] https://github.com/5j9/citer [4] https://search.worldcat.org/search?qt=wikipedia=isbn%3A0444885994 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484332] New: Discover crash when click on Installed
https://bugs.kde.org/show_bug.cgi?id=484332 Bug ID: 484332 Summary: Discover crash when click on Installed Classification: Applications Product: Discover Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Installed page Assignee: plasma-b...@kde.org Reporter: topw70+gb0xdqmr5ekupnbiom1o15jdtj0radlbnzpqobds54d2tkc i...@sharklasers.com CC: aleix...@kde.org Target Milestone: --- Created attachment 167657 --> https://bugs.kde.org/attachment.cgi?id=167657=edit Backtrace STEPS TO REPRODUCE 1. Open Discover 2. Click on Installed 3. It always crashes SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION The backtrace is without debuginfod when I tried with enabled debuginfod It prints this: Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault. 0x7fffc59acd4a in KNSCore::ResultsStream::fetch (this=0x5786e0b0) at /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70 Cancelling download of source file /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp... warning: 70 /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp: No such file or directory -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 Adam D changed: What|Removed |Added CC||debroe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 484017] New: Yellow highlight and pop-up note color is (subjectively) too intense, should use a muted color similar to Plasma's sticky note yellow
https://bugs.kde.org/show_bug.cgi?id=484017 Bug ID: 484017 Summary: Yellow highlight and pop-up note color is (subjectively) too intense, should use a muted color similar to Plasma's sticky note yellow Classification: Applications Product: okular Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- The Plasma sticky note applet used to use this dreadful harsh RGB-maxed yellow color as the background: https://i.stack.imgur.com/debL2.png The color was changed to a vastly superior color that's similar to that of a real sticky note: https://blog.broulik.de/wp-content/uploads/2023/11/Screenshot_20231104_122120.png Okular color for reference: https://cdn.kde.org/screenshots/okular/okular-annotation.png I propose we move away from using this color on highlights and pop-up notes in Okular by default. The default color stops for a yellow sticky note set by Plasma appear to be #f7eabf, #f9eecd. Something in that range might be appropriate. One potential option is to make the pop-up note background less intense than the highlighter color, since they essentially serve different purposes. We could go with the sticky note color for Okular's popup notes, and something a little brighter for the highlighter (but still less intense than what we have now). VDG input would probably be helpful here. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 484011] New: Document loses keyboard focus after adding a pop-up note
https://bugs.kde.org/show_bug.cgi?id=484011 Bug ID: 484011 Summary: Document loses keyboard focus after adding a pop-up note Classification: Applications Product: okular Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY This prevents you from (a) navigating the document using the keyboard, e.g. with the arrow keys, and (b) switching tools using the numbered shortcuts, e.g. switching back to the highlight tool. STEPS TO REPRODUCE 1. Make a trivial PDF document. I exported a few paragraphs of Lorem Ipsum from LibreOffice to a PDF. Open in Okular. 2. Press 6 to switch your tool to the pop-up note. 3. Click in the document to add a pop-up note, and add a word or two to the note. Click the little X button on the note with your cursor. 4. Try to navigate the document with the arrow keys. Try to switch tools by pressing 1 (highlighter). 5. Click on the window chrome, e.g. in an empty part of the toolbar underneath the menu bar. Try keyboard navigation again. 6. Click somewhere in the document area. This may require you to resize the document so that you can click in a place that won't add another pop-up note. Now try keyboard navigation again. OBSERVED RESULT Okular does not respond to keyboard input until after refocusing the document viewing widget in step 6. EXPECTED RESULT Okular responds to keyboard input in step 4. Steps 5/6 are not applicable. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483970] Breeze Application Style has no padding on properties menus in KDE Neon 6
https://bugs.kde.org/show_bug.cgi?id=483970 --- Comment #1 from Adam D --- Created attachment 167452 --> https://bugs.kde.org/attachment.cgi?id=167452=edit A different Application Style with better padding An example of the padding being present (albeit still smaller than before the update). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483970] New: Breeze Application Style has no padding on properties menus in KDE Neon 6
https://bugs.kde.org/show_bug.cgi?id=483970 Bug ID: 483970 Summary: Breeze Application Style has no padding on properties menus in KDE Neon 6 Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: debroe...@gmail.com Target Milestone: --- Created attachment 167451 --> https://bugs.kde.org/attachment.cgi?id=167451=edit Breeze with 2 examples of no padding SUMMARY After updating to KDE Neon 6.0 a large number of settings were changed. I reverted/fixed most of them but for some reason the padding for the controls inside a large number of windows (e.g. file properties in dolphin, edit application from the application launcher, etc) has completely broken. A lot of the controls are smashed up against each other/the edge of the window. This only happens when the Application Style is set to Breeze in the Global Theme in System Settings. Changing the Application Style to any of the other options has (mostly) appropriate padding — although it's still not what it used to be before the update (vertical padding is a bit off). STEPS TO REPRODUCE 1. Change the Application Style in System Settings to Breeze. 2. Right click on an application in the application launcher to bring up a properties window (any settings window will do). 3. Observe there is no padding for controls. OBSERVED RESULT Padding is missing from controls in properties menus while using the Breeze Application Style. EXPECTED RESULT Breeze Application Style should have bigger/existing padding to controls in properties menus. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483397] Corrupt output when recording full screen, works fine when recording a rectangle selection
https://bugs.kde.org/show_bug.cgi?id=483397 --- Comment #3 from Adam Fontenot --- I'm not able to reproduce this with a new user account, even when I copy over my .config and .local. There's probably some other configuration I'm missing somewhere. I'm going to keep trying to figure out the cause. This is a pretty new computer that was only on Plasma 5 for about a month, and has always had an very vanilla configuration. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483398] Cannot record a one pixel line on the right or bottom edge of the screen when using a rectangular selection
https://bugs.kde.org/show_bug.cgi?id=483398 --- Comment #4 from Adam Fontenot --- I think the original report may have been a bit unclear. This isn't only an issue with the recording, it's also an issue with the rectangular selection tool. Simply opening the Screen Sharing portal window and trying to select the whole screen shows "1919 x 1079" in the middle of the screen, as part of the selection preview. Taking screenshots is simply how I checked that the issue is with the right and bottom edges, as opposed to the top and left edges. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481359] Left-clicking the screen-sharing session indicator in the systray spawns a toplevel window
https://bugs.kde.org/show_bug.cgi?id=481359 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483397] Corrupt output when recording full screen, works fine when recording a rectangle selection
https://bugs.kde.org/show_bug.cgi?id=483397 --- Comment #2 from Adam Fontenot --- Integrated AMDGPU on mobile Ryzen 5000 series. 1:1 scale at 1080p on my built-in laptop screen. Broken hardware encoding of the video is not a possible cause - this is x264 encoded video with both Kooha and the Gstreamer script. Incidentally, the little tiny preview of the screen in the Screen Sharing portal window looks normal. I wonder if there's any reason the portal would provide the video stream in a different format when selecting the whole screen. Perhaps the internal pipeline for the video changes the format slightly when cropping to a rectangular screen area, avoiding an issue with Gstreamer-based recording on my system. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483398] Cannot record a one pixel line on the right or bottom edge of the screen when using a rectangular selection
https://bugs.kde.org/show_bug.cgi?id=483398 Adam Fontenot changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Adam Fontenot --- This is 1:1 1080p, no scaling. Integrated AMDGPU. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481461] Clicking checkbox to select content to share does not work
https://bugs.kde.org/show_bug.cgi?id=481461 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Adam Fontenot --- I reproduced this just now on portal version 6.0.1 and Qt 6.6.2. Reproduction (two different ways): 1. Install Kooha, and use that to open the portal Screen Share window. 2. Use the Python snippet here: https://gitlab.gnome.org/-/snippets/19 Confirming on that basis. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483398] New: Cannot record a one pixel line on the right or bottom edge of the screen when using a rectangular selection
https://bugs.kde.org/show_bug.cgi?id=483398 Bug ID: 483398 Summary: Cannot record a one pixel line on the right or bottom edge of the screen when using a rectangular selection Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY This prevents, for example, selecting the full screen using a rectangular selection. On my 1920x1080 laptop screen, attempting to select the full screen results in a selection of 1919x1079 STEPS TO REPRODUCE 1. Try to select the bottom right corner of your screen in the "Screen Sharing" window. 2. Compare a recording of the selection to a screenshot of your screen, e.g. taken with Spectacle. OBSERVED RESULT The recording is missing the bottom row of pixels and the rightmost column. EXPECTED RESULT You can select all the way to the edge of the screen. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 483397] New: Corrupt output when recording full screen, works fine when recording a rectangle selection
https://bugs.kde.org/show_bug.cgi?id=483397 Bug ID: 483397 Summary: Corrupt output when recording full screen, works fine when recording a rectangle selection Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Created attachment 167079 --> https://bugs.kde.org/attachment.cgi?id=167079=edit screenshot of the screen recording showing the issue SUMMARY This is reproducible using screen recording apps like Kooha, and also with simple scripts that may help narrow down the issue, like this one: https://gitlab.gnome.org/-/snippets/19 Tested on 6.0.1 because of Arch version, but 6.0.2 (latest release) doesn't have anything in the changelog that seems relevant. STEPS TO REPRODUCE 1. Open e.g. Kooha, and select to record the full screen. The portal "Screen Sharing" window will appear. 2. Select the checkbox on "Laptop screen" (or something else appropriate to recording whole screen in your case). 3. Uncheck "Allow restoring on future sessions" - I haven't checked if this makes a difference. 4. Click share and record a few seconds of video, then stop. OBSERVED RESULT Garbage output, see screenshot. Repeating the reproduction steps but choosing a rectangular region works fine. EXPECTED RESULT Working output SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
https://bugs.kde.org/show_bug.cgi?id=372116 Adam Batkin changed: What|Removed |Added CC||a...@batkin.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482013] Unhandled instruction 0xD5380008 on arm platform (mrs x8, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=482013 Adam Folwarczny changed: What|Removed |Added CC||adam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482615] Gwenview: segfault in FITSData::calculateMinMax
https://bugs.kde.org/show_bug.cgi?id=482615 --- Comment #1 from Adam Fontenot --- Created attachment 166527 --> https://bugs.kde.org/attachment.cgi?id=166527=edit backtrace for crash #0 0x77e855a2 in FITSData::calculateMinMax (this=0x7fffcbdff7c0) at /usr/src/debug/gwenview/gwenview-24.02.0/lib/imageformats/fitsformat/fitsdata.cpp:327 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482615] New: Gwenview: segfault in FITSData::calculateMinMax
https://bugs.kde.org/show_bug.cgi?id=482615 Bug ID: 482615 Summary: Gwenview: segfault in FITSData::calculateMinMax Classification: Applications Product: gwenview Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 166526 --> https://bugs.kde.org/attachment.cgi?id=166526=edit file that will crash Gwenview when you try to open it SUMMARY The file in question is probably corrupt, but this should not segfault Gwenview. STEPS TO REPRODUCE 1. Open attached file in Gwenview. (Alternatively, if you have a valid PNG file and this file in the same directory, and no other image files, opening the PNG will also crash Gwenview, probably because it tries to pre-load the other file.) OBSERVED RESULT Segfault. See backtrace. EXPECTED RESULT No segfault. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 --- Comment #2 from Adam Pigg --- Id like to add to this. I run my desktop at 125%, in wayland, and attached a screenshot, scaled 300% in gimp. The font rendering issue only seems to affect the kmail message pane, other text in plasma6 is fine. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482445] kmail font rendering broken on plasma 6 and HiDPI (scaled) display
https://bugs.kde.org/show_bug.cgi?id=482445 Adam Pigg changed: What|Removed |Added CC||a...@piggz.co.uk --- Comment #1 from Adam Pigg --- Created attachment 166416 --> https://bugs.kde.org/attachment.cgi?id=166416=edit Kmail font rendering 125% scale, wayland, blown 300% no filter -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 444537] when toggling keyboard layout, shortcuts continue to use the old layout
https://bugs.kde.org/show_bug.cgi?id=444537 Adam Fontenot changed: What|Removed |Added Version|5.87.0 |6.0.0 --- Comment #2 from Adam Fontenot --- Reproduced on 6.0.0 under X11. Not sure if the component could have changed, but in any case khotkeys is dead now, but global shortcuts for e.g. opening Dolphin are still present under "Shortcuts" in System Settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460840] KWin doesn't respect sub-pixel rendering setting for window titles
https://bugs.kde.org/show_bug.cgi?id=460840 Adam Fontenot changed: What|Removed |Added Version|5.26.0 |6.0.0 --- Comment #2 from Adam Fontenot --- Reproduced on 6.0.0. Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471801] Upgrading 5.27.5 -> 5.27.6 broke dvorak layout and advanced keyboard behavior
https://bugs.kde.org/show_bug.cgi?id=471801 Adam Fontenot changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Adam Fontenot --- This is almost certainly a one-off issue related to changing the "dvk" layout to "English (Dvorak)", and might not even be KDE specific. Since no one has reproduced, I'm going to close it. It could potentially affect others on pre-5.27.6 to 6.0 upgrade paths, however. If anyone encounters this, please reopen the issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474009] Konsole v23.08.0+ breaks console rendering when displaying certain emojis
https://bugs.kde.org/show_bug.cgi?id=474009 Adam Fontenot changed: What|Removed |Added URL||https://bugs.launchpad.net/ ||byobu/+bug/1641819 Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #10 from Adam Fontenot --- Going to close this one as an upstream issue with Byobu. Other terminal applications that break when rendering wide characters should have bugs reported against them as well. Other Konsole issues with rendering emojis are handled in other bugs. If there's a specific test case for an issue with Konsole, this can be reopened. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474310] Konsole eats a space after most unqualified emojis
https://bugs.kde.org/show_bug.cgi?id=474310 Adam Fontenot changed: What|Removed |Added Version|23.08.0 |24.02.0 --- Comment #2 from Adam Fontenot --- Reproduced on 24.02. Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455170] "Maximization" visual effect briefly appears *above* window when moving window away from activation point at top of screen
https://bugs.kde.org/show_bug.cgi?id=455170 Adam Fontenot changed: What|Removed |Added Version|5.24.5 |6.0.0 --- Comment #2 from Adam Fontenot --- Tested and reproduced on 6.0.0. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474309] Emoji font button is too wide
https://bugs.kde.org/show_bug.cgi?id=474309 Adam Fontenot changed: What|Removed |Added Version|23.08.0 |24.02.0 --- Comment #2 from Adam Fontenot --- Tested and reproduced on 24.02. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 469876] "View Key" button doesn't display the key for the device that requested pairing
https://bugs.kde.org/show_bug.cgi?id=469876 Adam Fontenot changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Adam Fontenot --- This appears to have been fixed as of 24.02. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445082] user-places.xbel is not updated when changing XDG user directories via System Settings, or after changing user name / moving home location
https://bugs.kde.org/show_bug.cgi?id=445082 Adam Fontenot changed: What|Removed |Added Summary|user-places.xbel is not |user-places.xbel is not |updated after change of |updated when changing XDG |user name / change of user |user directories via System |home location |Settings, or after changing ||user name / moving home ||location -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427669] Title / header text is duplicated in many settings panes
https://bugs.kde.org/show_bug.cgi?id=427669 Adam Fontenot changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Adam Fontenot --- I'm pretty satisfied with the way this looks now in Plasma 6 - a lot more care has been taken in providing a proper system settings hierarchy and the labeling is less haphazard. If a KDE dev or someone in VDG disagree, feel free to re-open. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481473] File associations do not de-duplicate applications using X-KDE-AliasFor, resulting in some applications being shown twice or more
https://bugs.kde.org/show_bug.cgi?id=481473 Adam Fontenot changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=452566 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 452566] KDE offers to open mimetype with application twice when it inherits the association twice
https://bugs.kde.org/show_bug.cgi?id=452566 Adam Fontenot changed: What|Removed |Added Resolution|--- |FIXED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=481473 Status|CONFIRMED |RESOLVED --- Comment #4 from Adam Fontenot --- I believe this has been fixed, probably as part of Bug 475200. There is a related bug where certain applications that provide multiple .desktop files will be shown twice (or more). Okular is one of these: https://bugs.kde.org/show_bug.cgi?id=481473 There is a related bug describing user-confusing situations where an app unexpectedly inherits a file type due to a low level mimetype assignment like application/octet-stream: Bug 425154. Fortunately this situation is now much less painful thanks to two fixes to inheritance ordering. Okular should no longer take over all your files like it used to do. I think I have managed to find and report all other issues with file associations, and they're now fixed as of Plasma 6! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482345] Certain characters in file name completely break Dolphin's text rendering across multiple lines
https://bugs.kde.org/show_bug.cgi?id=482345 --- Comment #2 from Adam Fontenot --- I see this with a source build as well, built just now on latest: https://invent.kde.org/system/dolphin/-/tree/6231e67120cf4abae696b736e9d851464338f4dd It's possible that the height of the character in my font is triggering the issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482345] New: Certain characters in file name completely break Dolphin's text rendering across multiple lines
https://bugs.kde.org/show_bug.cgi?id=482345 Bug ID: 482345 Summary: Certain characters in file name completely break Dolphin's text rendering across multiple lines Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 166376 --> https://bugs.kde.org/attachment.cgi?id=166376=edit screenshot of the issue SUMMARY Probably the character is taller than expected? But it completely break's Dolphin's rendering of the text, and not just right around the unexpected character. STEPS TO REPRODUCE 1. `touch 'this is some text⧸this is some text.txt'` 2. Look at the resulting file in Dolphin. Note that the character above is not a slash, it's U+29F8. OBSERVED RESULT Broken text rendering - see screenshot. Affects both thumbnail view and details view. The font shown here is Source Sans 3 11 pt. EXPECTED RESULT No broken text. Specifically, text that is too tall for the box should just overflow it (or be cut off), without changing the line width. (Even if changing the line width were reasonable, something has clearly gone badly wrong in this case.) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482254] Visual inconsistency: some folder icons use theme "accent" color, others do not
https://bugs.kde.org/show_bug.cgi?id=482254 Adam Fontenot changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |visual-des...@kde.org CC||kain...@gmail.com, ||m...@nueljl.in Product|dolphin |Breeze Component|general |Icons Version|24.02.0 |5.93.0 --- Comment #1 from Adam Fontenot --- Ugh, I forgot to change the product after I decided to file this against Breeze. Apologies for the noise. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482254] New: Visual inconsistency: some folder icons use theme "accent" color, others do not
https://bugs.kde.org/show_bug.cgi?id=482254 Bug ID: 482254 Summary: Visual inconsistency: some folder icons use theme "accent" color, others do not Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 166319 --> https://bugs.kde.org/attachment.cgi?id=166319=edit screenshot of the problem SUMMARY I'm filing this against Breeze because this is probably an issue with the SVG icons, but I've only seen the issue in Dolphin, and it might be a result of how Dolphin renders the icon. This is perhaps related to Bug 478016, but that bug points out issues when *highlighting* folder icons, whereas this bug is pointing out that color issues are apparent for certain icons in all conditions. STEPS TO REPRODUCE 1. Set your icons to Breeze icons. Set a color theme other than Breeze, and set your accent color to follow your color theme. 2. Open Dolphin. Go to the properties for a folder, and set the icon to Breeze's folder-design icon. Set another folder's icon to Breeze's folder-development icon. 3. Look at the resulting icons in Dolphin, in thumbnail view, with no icons focused or selected. OBSERVED RESULT folder-development follows my accent color, folder-design does not follow my accent color - it uses the default Breeze accent color instead. Strangely, the built in preview for the icon in the Dolphin properties window shows an icon that *does* follow the accent color. This seems consistent across icons that I see issues with - the preview always looks right. folder-chart is also broken, as well as probably others - I don't have an exhaustive list. EXPECTED RESULT All folder icons follow the accent color. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482249] New: Okular text selection glitch confuses beginning and end of selection in PDFs
https://bugs.kde.org/show_bug.cgi?id=482249 Bug ID: 482249 Summary: Okular text selection glitch confuses beginning and end of selection in PDFs Classification: Applications Product: okular Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 166317 --> https://bugs.kde.org/attachment.cgi?id=166317=edit screencast showing the issue SUMMARY This is Okular 24.02.0, not 24.01.95. I realize PDFs can be fickle, but this issue is consistent across all PDFs I've tested, including some very basic ones. Copy your favorite "lorem ipsum" text into a LibreOffice Writer document, export it to PDF, and you should be able to reproduce this issue. STEPS TO REPRODUCE 1. Start selecting some text by clicking on a line in the document, and then dragging down to select multiple lines or sentences. 2. While continuing to hold down the mouse button, drag to the left (further left than you began the selection on the top line). OBSERVED RESULT The *starting* point of the selection changes (is moved left). EXPECTED RESULT The *ending* point of the selection changes, on the final line of the selection. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481471] Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??)
https://bugs.kde.org/show_bug.cgi?id=481471 --- Comment #7 from Adam Fontenot --- The changes probably fix Bug 482006, which was duped to this. I think it should be unduped and this should stay open. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481471] Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??)
https://bugs.kde.org/show_bug.cgi?id=481471 Adam Fontenot changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #6 from Adam Fontenot --- Reopening: I tested the patch (against 24.02.0), and it did not fix the issue! My reading of the commit message suggests that this was intended to fix something else. I'm not using any shortcuts to start Spectacle in this case, and I'm not activating one recording while another one is in progress. Reproduction: 1. Take a video of a rectangular region of the screen. STOP the recording, and return to the Spectacle interface. 2. Without closing Spectacle, switch from the "Recording" tab to the "Screenshot" tab. 3. Open the rectangular select tool for screenshots. 4. Hit the enter key to immediately select the preset rectangular region. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482079] click target for virtual desktops is too small in the overview effect, clicking bottom of virtual desktop closes the effect instead
https://bugs.kde.org/show_bug.cgi?id=482079 --- Comment #3 from Adam Fontenot --- (In reply to Nate Graham from comment #2) > When you hover over a desktop, it slightly expands. I think what's happening > is that the click area is the original size not the expanded size. If you look closely at the video, you'll see that I'm clicking inside the original bounds of the virtual desktop. So I don't *think* this is the cause, although it's possible something related to the expansion effect is responsible. I'd say the bottom 15-20% of the virtual desktop area cancels the overview, in my tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482079] New: click target for virtual desktops is too small in the overview effect, clicking bottom of virtual desktop closes the effect instead
https://bugs.kde.org/show_bug.cgi?id=482079 Bug ID: 482079 Summary: click target for virtual desktops is too small in the overview effect, clicking bottom of virtual desktop closes the effect instead Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 166214 --> https://bugs.kde.org/attachment.cgi?id=166214=edit screencast showing the issue SUMMARY It seems the clickable area on the virtual desktop in the effect is a bit too small. I am able to close the effect by clicking on the bottom of any virtual desktop representation, rather than switching to the desktop in question. Screen is 1440p at 1:1. This is Plasma 6, not 5.93.0. STEPS TO REPRODUCE 1. Open the overview effect (I have a hot corner for this). 2. Click on the very bottom of one of the virtual desktops (one you aren't currently on) at the top. OBSERVED RESULT The effect closes. EXPECTED RESULT The clicked virtual desktop is made active. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480798] KDE / KWin slowly eats (leaks?) my graphics memory (GART) until it begins stuttering
https://bugs.kde.org/show_bug.cgi?id=480798 Adam Fontenot changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Adam Fontenot --- I haven't see the issue recur, so I'm going to close this for now. I'll reopen this if it happens again. Some notes for others who may have encountered similar issues: * The issue began for me either after Plasma 6 beta 1 or beta 2 was installed. It was clearly present continuously for some time - even before I diagnosed the issue, any time Plasma had been running for more than a few days I would encounter performance issues. * The Plasma 6 Wayland session still uses quite a bit more graphics memory than Xorg, and this amount grows over time. Recently (since I stopped being able to reproduce the bug), I see 2-3 GB of graphics memory held under Wayland after about a week of use, vs ~0.5 GB for Xorg. But I haven't seen 50+% utilization of GART since I reported the issue. * The way you'd confirm you have the issue on an AMD system is, (a) you see a lot of memory use that is not attributable to applications, cache, or ZFS ARC, (b) the memory is not automatically reclaimed when you start an application that uses a lot of memory - it crashes or you get an OOM condition, and (c) running `radeontop` shows 90+% utilization of "GTT" memory, (d) closing all userspace applications doesn't reduce it significantly, and (e) closing your Plasma session and returning to a VTERM immediately reduces GART / GTT usage to ~0%. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 482013] New: Unhandled instruction 0xD5380008 on arm platform (mrs x8, midr_el1)
https://bugs.kde.org/show_bug.cgi?id=482013
Bug ID: 482013
Summary: Unhandled instruction 0xD5380008 on arm platform (mrs
x8, midr_el1)
Classification: Developer tools
Product: valgrind
Version: 3.22.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: adam...@gmail.com
Target Milestone: ---
SUMMARY
ARM64 front end: branch_etc
disInstr(arm64): unhandled instruction 0xD5380008
disInstr(arm64): 1101'0101 0011'1000 ' '1000
==3277832== valgrind: Unrecognised instruction at address 0x8ebb81c.
==3277832==at 0x8EBB81C: setSysRegVal (util_impl.cpp:123)
==3277832==by 0x8EBB81C: Xbyak_aarch64::util::Cpu::Cpu()
(util_impl.cpp:233)
==3277832==by 0x8E9597F: cpu (cpu_isa_traits.hpp:171)
==3277832==by 0x8E9597F: mayiuse (cpu_isa_traits.hpp:188)
==3277832==by 0x8E9597F:
dnnl::impl::cpu::aarch64::tr::jit_single_blk_kernel_t::applicable(dnnl::impl::cpu::aarch64::tr::prb_t
const&) (jit_uni_reorder.cpp:1905)
==3277832==by 0x8E955C7:
dnnl::impl::cpu::aarch64::jit_blk_reorder_t::pd_t::create(dnnl::impl::reorder_pd_t**,
dnnl_engine*, dnnl_primitive_attr const*, dnnl_engine*, dnnl_memory_desc
const*, dnnl_engine*, dnnl_memory_desc const*) (jit_uni_reorder.cpp:2936)
OBSERVED RESULT
valgrind reports unhandled instruction error
EXPECTED RESULT
Valgrind understand instruction mentioned above
SOFTWARE/OS VERSIONS
Linux arm64
ADDITIONAL INFORMATION
The error comes from dnnl library.
Compile command:
clang++-10 -MMD -MF -DENABLE_NEON -DENABLE_OMP -DNDEBUG -DDISABLE_VERBOSE
-DDNNL_DISABLE_PRIMITIVE_CACHE -DDNNL_ENABLE_CONCURRENT_EXEC
-DDNNL_ENABLE_JIT_PROFILING=0 -DDNNL_ENABLE_MAX_CPU_ISA -DDNNL_AARCH64=1
-I../../deps/build/dnnl/src -I../../deps/build/dnnl/include
-I../../deps/build/dnnl/src/cpu/aarch64/xbyak_aarch64/xbyak_aarch64
-I../../deps/build/acl/arm_compute -I../../deps/build/acl
-I../../deps/build/acl/include -I../../deps/build/openmp/pregenerated/include
-I../../deps/build/libcxx/include -I../../deps/build/libcxxabi/include
-fopenmp -fno-strict-aliasing -funwind-tables -fPIC -fcolor-diagnostics
--target=aarch64-linux-gnu -fstack-protector-strong -pthread -O3 -fno-ident
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g2
--sysroot=/opt/xenial -fvisibility=hidden -fvisibility-inlines-hidden -frtti
-fexceptions -std=c++14 -nostdinc++ -c
../../deps/build/dnnl/src/cpu/aarch64/xbyak_aarch64/src/util_impl.cpp
Function with unrecognized instruction:
<_ZN13Xbyak_aarch644util3Cpu12setSysRegValEv>:
0: d5380008mrs x8, midr_el1
4: f9003c08str x8, [x0, #120]
8: d65f03c0ret
Implementation:
#define XBYAK_AARCH64_READ_SYSREG(var, ID) asm("mrs %0, " #ID : "=r"(var));
void Cpu::setSysRegVal() {
#ifdef __linux__
XBYAK_AARCH64_READ_SYSREG(midr_el1_, MIDR_EL1);
#endif
}
Codes comes from opendll (util_impl.cpp)
oneAPI Deep Neural Network Library (oneDNN)
https://github.com/oneapi-src/oneDNN/blob/rls-v3.1/src/cpu/aarch64/xbyak_aarch64/src/util_impl.cpp
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 481970] New: Dolphin
https://bugs.kde.org/show_bug.cgi?id=481970 Bug ID: 481970 Summary: Dolphin Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: a-boraw...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- the dolphin is cut off on the left side. Trash, documents, etc. are missing. Linux/KDE Plasma: KDE NEON (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481391] When a user has a panel on the top of the screen, rectangular area screencasts are recorded in the wrong location
https://bugs.kde.org/show_bug.cgi?id=481391 --- Comment #5 from Adam Fontenot --- Created attachment 166123 --> https://bugs.kde.org/attachment.cgi?id=166123=edit spectacle screencast showing the horizontal offset and recording outline issue Can confirm that the patch fixes the issue, but note that I do still see the issue with the recording being offset *horizontally* sometimes. I'm mentioning this here because I'm not sure if it has the same root cause as this issue with the panel, or something else like the "divisible by two" thing. I can open up another bug for this if it would be useful. Attaching a screen recording showing what I mean (this is after applying the commit that fixes this issue). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481779] New: Android TV support
https://bugs.kde.org/show_bug.cgi?id=481779 Bug ID: 481779 Summary: Android TV support Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: alexander.adam+...@vade.io CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Right now the KDE Connect app doesn't show natively on Android TV devices because the metadata is missing. Hence only third party launchers can launch KDE Connect on Android TV although it especially useful on Android TV devices as they often only have limited input capabilities and often no built-in possibilities to manage files on these devices externally. KDE Connect enables these functions easily but the requirement of needing a third party launcher to even start and pair it adds an additional barrier to non-tech-savvy folks. STEPS TO REPRODUCE 1. Install KDE Connect on Android TV 2. try to launch it in a default launcher OBSERVED RESULT The app doesn't show up EXPECTED RESULT It shows up SOFTWARE/OS VERSIONS All Android versions ADDITIONAL INFORMATION Google provides documentation on what is needed for proper Android TV support (i.e. a handy checklist at https://developer.android.com/training/tv/publishing/checklist ) and apparently it is possible to work with virtual devices ( https://developer.android.com/training/tv/start/start#run-on-a-virtual-device ). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481391] When a user has a panel on the top of the screen, rectangular area screencasts are recorded in the wrong location
https://bugs.kde.org/show_bug.cgi?id=481391 Adam Fontenot changed: What|Removed |Added Summary|Video recordings sometimes |When a user has a panel on |record in the incorrect |the top of the screen, |location and include the|rectangular area |dashed rectangle outline|screencasts are recorded in ||the wrong location -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481391] Video recordings sometimes record in the incorrect location and include the dashed rectangle outline
https://bugs.kde.org/show_bug.cgi?id=481391 --- Comment #2 from Adam Fontenot --- As confirmation, I moved my panel to the bottom of the screen and it fixed the issue with the recording being in the wrong place. Very strange. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #11 from Adam Fontenot --- My discussion above was about VP9, I've been investigating quality issues with H.264 today. Rather, the lack thereof, because the results are pretty okay for me. `m_avCodecContext->global_quality` is equivalent to setting the `-q` option on the ffmpeg command line. Unfortunately, as is clear from the documentation [1], libx264 ignores the global quality setting *entirely*. So on most ffmpeg versions it's equivalent to the default of CRF 23, which is pretty tolerable quality for screen recordings. As evidence of this, when recording the screen with libx264, Spectacle prints the following to the terminal: [libx264 @ 0x77274430b640] -qscale is ignored, -crf is recommended. As a result the file I get is encoded with `rc=crf`, since that's the default. I'm not sure how Hector got `rc=abr` in their files, my understanding is that this is only applicable to two pass encodes, not for streaming encoding as is used here. At any rate, what's clear is that the current H.264 code needs to be replaced. At present the quality settings are a complete noop. See also: https://trac.ffmpeg.org/ticket/3238 [1] https://ffmpeg.org/ffmpeg-codecs.html#Options-35 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481390] Video format preference does not use standard settings management behavior
https://bugs.kde.org/show_bug.cgi?id=481390 --- Comment #7 from Adam Fontenot --- I've filed a bug for the other issue, which I've just discovered the precise cause of. https://bugs.kde.org/show_bug.cgi?id=481727 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481727] New: Recording H.264 of a rectangular region fails 75% of the time with "not divisible by 2" error
https://bugs.kde.org/show_bug.cgi?id=481727 Bug ID: 481727 Summary: Recording H.264 of a rectangular region fails 75% of the time with "not divisible by 2" error Classification: Applications Product: Spectacle Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: adam.m.fontenot+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY At first, as originally reported in Bug 481390, I thought H.264 recording always fails. Turns out, I was just unlucky and it failed the first half dozen times I tested it. I didn't realize debugging information was provided when you run Spectacle in the terminal, but I did so and immediately found the issue: [libx264 @ 0x75f4302e9400] width not divisible by 2 (573x365) kpipewire_record_logging: Could not open codec Generic error in an external library kpipewire_record_logging: No encoder could be created STEPS TO REPRODUCE 1. Select a rectangular region of the screen for recording, with H.264 selected as your codec. Make sure that one or both of the dimensions is not divisible by two (e.g. 573x365 in my example). 2. Try to start recording video. OBSERVED RESULT Nothing is ever recorded or output, Spectacle minimizes itself to the taskbar (red recording icon), but clicking on this icon does nothing. Spectacle has to be killed from the task manager or terminal. EXPECTED RESULT Spectacle should prevent selecting unacceptable rectangular regions for the current video codec. **Moreover**, Spectacle should respond to errors from Pipewire in a way that is (a) visible to the user, and (b) does not make Spectacle unusable until it is killed and restarted. My guess is that this sort-of affects VP9 as well, in that this is why the recording is usually one pixel *wider* than expected and includes the dashed rectangular outline that shows the recording region. This is in part what I reported in Bug 481391, although there are other issues here too. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481390] Video format preference does not use standard settings management behavior
https://bugs.kde.org/show_bug.cgi?id=481390 --- Comment #6 from Adam Fontenot --- Thanks for the fix, it does appear to resolve the issue when I cherry-pick your changes. Should I file a different bug for the issue with recording h264? Bug 478868 is about the output being corrupt when encoding h264 on a discrete GPU, but I've never seen this issue and don't have a discrete GPU. My issue is that when trying to record h264, Spectacle disappears with the red "recording" icon in the taskbar, but seems to hang. I can't stop the recording by pressing the icon, there's no discernable CPU use by Spectacle, and no output file is ever created, even in the /tmp Spectacle directory. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481701] Neochat segfaults immediately upon opening the program
https://bugs.kde.org/show_bug.cgi?id=481701 --- Comment #2 from Adam Fontenot --- (In reply to duha.bugs from comment #1) > This is likely https://bugs.kde.org/show_bug.cgi?id=478229 It's possible but the traceback is very different. I crash in libQuotient, whereas that library is not in the two backtraces for the bug you linked. Maybe I'll copy my traceback over to the Gitlab in case it's useful there. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481701] New: Neochat segfaults immediately upon opening the program
https://bugs.kde.org/show_bug.cgi?id=481701 Bug ID: 481701 Summary: Neochat segfaults immediately upon opening the program Classification: Applications Product: NeoChat Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: adam.m.fontenot+...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166029 --> https://bugs.kde.org/attachment.cgi?id=166029=edit crash traceback SUMMARY Neochat segfaults immediately upon opening the application, without any interaction. STEPS TO REPRODUCE 1. Log into your account (username, password) using Neochat. 2. Search for a room and join the room (I clicked on a couple of KDE rooms). Neochat immediately crashed for me, with no backtrace. That's probably Bug 479735. 3. Open Neochat again. OBSERVED RESULT Segfault. Backtrace is *not* similar to 479735, I see a crash in `QJsonObject`. EXPECTED RESULT No segfault. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 460509] Baloo indexes files temporarily mounted from other file systems
https://bugs.kde.org/show_bug.cgi?id=460509 --- Comment #9 from Adam Fontenot --- (In reply to tagwerk19 from comment #8) > (In reply to Adam Fontenot from comment #7) > > My merge request from Oct 2022 never got any review. I rebased the changes > > and I'm leaving a note about it here in the hope that we can close this > > issue. > I remember stumbling upon this and then finding it near impossible to find > it again. > https://invent.kde.org/plasma/plasma-desktop/-/issues/71 > It might be of interest, it certainly runs against some of my earlier > thoughts. Encouraging better choices with network mounts is a good thing, but this is still needed. The issues I've seen with indexing are the result of FUSE mounts, not /etc/fstab or `mount -t nfs` type mounts that hang in the way this Plasma issue describes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #14 from Adam Fontenot --- > IMO, baloo needs to ignore all FUSE mounts My merge request that needs review does this, if I'm not mistaken. It's still possible to manually opt in. That may fix this issue. https://invent.kde.org/frameworks/baloo/-/merge_requests/96/ -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #9 from Adam Fontenot --- Created attachment 165948 --> https://bugs.kde.org/attachment.cgi?id=165948=edit illustration of crf 20 vs 31 in a fullscreen recording As a quick illustration, I've taken two fullscreen (60 fps 1080p) screencasts with comparable details (I scrolled up and down this page in my browser for a bit), at both CRF 31 (the default) and CRF 20 (with my patch). The result illustrates the way that VP9 cheats on flat fields quite well. This area of the screen shown in the image is basically static in the video, and contains large regions of a single color. The encoder cheats a lot here, with a result that is visibly much worse with CRF 31. For common screencast use cases, like recording bugs and features, this is a worst case scenario of sorts, since you'd like to see relatively crisp looking text and icons. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 --- Comment #8 from Adam Fontenot --- (In reply to Noah Davis from comment #7) > From all the reading of encoder documentation I've done in the past, 31 is > not low, it's average and actually looks decent when doing fullscreen > recording. In my own tests, there was not a significant difference in > quality between 20 CRF and 31 CRF when doing fullscreen recording either. > For me, fullscreen is 1080p@60Hz or 4K@60Hz. For some reason, recording a > smaller region has a strong negative effect on recording quality, so we may > need to scale quality with region size inversely. I think the issue is more likely to lie elsewhere. There are very few actual frames in my screencast, which is an issue not only for seeking, but also for the efficiency of the encoder. This is probably not as noticeable with full motion 24 fps or 60 fps video, but in the case of my screencast, there are only 90 actual frames in the file, because KPipeWire seems to be dropping duplicate frames rather than sending them to the encoder. In a 15.35 second clip with a nominal framerate of 60 fps, you expect to see 921 frames. So ffmpeg has only encoded 1 in 10 frames, due to the missing duplicates. The low number of frames means that the quality of the video depends on the quality of the individual frames much more. At a relatively low quality CRF like 31, the encoder is probably cheating too much on these frames. This is combined with the fact that video encoders are optimized for full motion video, not screencasts, so their quality metrics cheat heavily on flat fields (regions of nearly solid color) because they can be smoothed out and encoded at a very small size. That's clearly visible in my screencast. The recommendation for CRF 31 seems to come from Google, and I'm skeptical of their figures. They consistently underestimate bitrates needed for reasonable quality, as is readily apparent if you watch their encodes for YouTube. Interestingly, they recommend a CRF of 15 for 4K video, so VP9's CRF metric does not seem particularly consistent. For what it's worth, their example encode of "Tears of Steel" (the open source Blender film) at CRF 31 and 1080p strikes me as rather poor, and that has the advantage of being a two-pass encode. [1] I'm not trying to be overly debate-y here; there's not going to be a single one-size-fits-all value for all resolutions and all use cases. The correct approach is probably to allow setting the CRF directly in the Spectacle settings and passing the value to KPipeWire. [1] https://developers.google.com/media/vp9/settings/vod/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 460509] Baloo indexes files temporarily mounted from other file systems
https://bugs.kde.org/show_bug.cgi?id=460509 --- Comment #7 from Adam Fontenot --- My merge request from Oct 2022 never got any review. I rebased the changes and I'm leaving a note about it here in the hope that we can close this issue. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476186] Screen recording quality is terrible
https://bugs.kde.org/show_bug.cgi?id=476186 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #6 from Adam Fontenot --- Created attachment 165924 --> https://bugs.kde.org/attachment.cgi?id=165924=edit screencast illustrating poor recording quality I see this on the latest beta (kpipewire 5.92.3, spectacle 24.01.95) with VP9 recording. As requested I'm attaching a video, which is a short recording I made of Crosswords [1] to illustrate a bug with that program. These are clearly encoding artifacts stemming from the very low CRF used by default (31) for VP9. I was able to mostly fix the issue by changing the default quality to 20, which seems like a much more reasonable default. [1] https://gitlab.gnome.org/jrb/crosswords -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 481481] New: Gwenview inhibits laptop suspend when viewing an image
https://bugs.kde.org/show_bug.cgi?id=481481 Bug ID: 481481 Summary: Gwenview inhibits laptop suspend when viewing an image Classification: Applications Product: gwenview Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY Gwenview always prevents my screen from locking and my laptop from going to sleep, with no way to change this. STEPS TO REPRODUCE 1. Open any image (e.g. a simple PNG) in Gwenview OBSERVED RESULT After a few seconds, when clicking on the "Power and Battery" applet in the taskbar, I see the text "Gwenview is currently blocking sleep and screen locking (Viewing media)". This appears to be correct - the screen does not lock. EXPECTED RESULT I expect Gwenview to block sleep only in a few instances, e.g. when viewing a fullscreen slideshow or when viewing a video with sound. I looked for options to disable this feature in the Gwenview settings, but didn't find anything. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481473] New: File associations do not de-duplicate applications using X-KDE-AliasFor, resulting in some applications being shown twice or more
https://bugs.kde.org/show_bug.cgi?id=481473 Bug ID: 481473 Summary: File associations do not de-duplicate applications using X-KDE-AliasFor, resulting in some applications being shown twice or more Classification: Applications Product: systemsettings Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: kcm_filetypes Assignee: plasma-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: fa...@kde.org Target Milestone: --- SUMMARY For reasons unknown to me, some KDE applications (e.g. Okular) have multiple .desktop files for different filetypes. Okular, for example, has `okularApplication_md.desktop` and `okularApplication_txt.desktop`, along with many others. This causes an issue in that all Markdown (.md) files are also plain text (.txt) files. So if you try to open a Markdown file, you'll see Okular twice in the list of possible applications. Unless applications are supposed to *never* have multiple .desktop entries, KDE needs to deduplicate these. It appears that the way KDE applications are indicating the use of multiple .desktop entries is via the use of the `X-KDE-AliasFor` line, e.g. X-KDE-AliasFor=org.kde.okular.desktop Similarly, if a user assigns an application to a file type (e.g. I have Okular set to open PDF files), and the application also inherits the file type via a different .desktop file (e.g. okularApplication_pdf.desktop), the application will be shown twice for the file. KDE should most likely only add the first entry that appears in its search with a specific alias to the applications that can open a given file type. STEPS TO REPRODUCE 1. Make a simple Markdown (.md) file. 2. Right click the file and see what applications Dolphin gives you to open it. OBSERVED RESULT Okular appears in the list twice. EXPECTED RESULT Okular appears in the list once. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481471] Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??)
https://bugs.kde.org/show_bug.cgi?id=481471 --- Comment #1 from Adam Fontenot --- This also sort-of happens if you take two rectangular area screencasts back to back. The difference is that the desktop remains interactable, so I can kill spectacle without having to resort to a different vterm. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481471] New: Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??)
https://bugs.kde.org/show_bug.cgi?id=481471 Bug ID: 481471 Summary: Attempting to take a rectangular area screenshot after taking a rectangular area screen*cast* banishes my desktop to the shadow realm (??) Classification: Applications Product: Spectacle Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: adam.m.fontenot+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 165906 --> https://bugs.kde.org/attachment.cgi?id=165906=edit photo of a screen showing the problem SUMMARY This is fully reproducible for me. STEPS TO REPRODUCE 1. Take a video of a rectangular region of the screen. I can only do this with VP9 due to another bug. 2. Without closing Spectacle, open the rectangle select tool for screenshots. 3. Hit the enter key to accept the rectangular selection, without modifying it. OBSERVED RESULT See photo. (The reproduction steps break my desktop so I have no easy way to take a screenshot of the problem.) A darkened version of my screen appears, which is non-interactable. It looks like a fullscreen window except that it appears below the "real" panel at the top. I'm unable to close it or switch to a different application. I'm forced to switch vterms and `pkill spectacle` to escape the situation. The Spectacle related widgets shown in the image (like the rectangle select tool) are likewise non-interactable. EXPECTED RESULT Spectacle takes a screenshot of a rectangular area, as requested. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481391] Video recordings sometimes record in the incorrect location and include the dashed rectangle outline
https://bugs.kde.org/show_bug.cgi?id=481391 --- Comment #1 from Adam Fontenot --- A different bug I just encountered and am about to report is making me think that it's relevant that I have a top panel. It's about the same width as the vertical offset of the recording from the requested location. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 481445] New: Please add stream recording
https://bugs.kde.org/show_bug.cgi?id=481445 Bug ID: 481445 Summary: Please add stream recording Classification: Applications Product: Haruna Version: 0.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: ada...@proton.me Target Milestone: --- SUMMARY ** There is no capability to record live stream, which is present in mpv with option '--record-stream'. I'm fairly certain this appeals to most users that play streams. ** SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481391] New: Video recordings sometimes record in the incorrect location and include the dashed rectangle outline
https://bugs.kde.org/show_bug.cgi?id=481391 Bug ID: 481391 Summary: Video recordings sometimes record in the incorrect location and include the dashed rectangle outline Classification: Applications Product: Spectacle Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: adam.m.fontenot+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 165846 --> https://bugs.kde.org/attachment.cgi?id=165846=edit frame of a screencast showing the issue SUMMARY When I select a rectangle outline for Spectacle to record a screencast, the actual location of the recording is (usually?) shifted slightly from the location I choose, and the resulting recording includes the dashed line that shows the recording location. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481256] [Feature Request] Add feature to increase the bitrate of screencasts
https://bugs.kde.org/show_bug.cgi?id=481256 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #2 from Adam Fontenot --- Created attachment 165845 --> https://bugs.kde.org/attachment.cgi?id=165845=edit quality issues - screencast top, screenshot bottom Maybe a quick fix would be to bump the default quality delivered by kpipewire? The screencasts I've recorded are not even usable, the bitrate is so low. Attached screenshot to show the issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481390] New: Recording H.264 doesn't work
https://bugs.kde.org/show_bug.cgi?id=481390 Bug ID: 481390 Summary: Recording H.264 doesn't work Classification: Applications Product: Spectacle Version: 24.01.95 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: adam.m.fontenot+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Changing the video format to H.264 / MP4 doesn't enable the "apply" button on the settings form, and if you change some other setting to enable it, and save the settings with H.264, recording a video hangs and has to be killed from the terminal. STEPS TO REPRODUCE 1. Open the configuration window and go to the "Video Saving" options. 2. Change to MP4 / H.264. 3. Change the filename field and save the settings. 4. Try to record a screencast of a rectangular portion of the screen. OBSERVED RESULT The apply button isn't enabled after step 2. If you click "OK" and then close and reopen Spectacle, the video settings won't be saved. In step 4, Spectacle gets stuck in recording mode. The red "recording" icon appears in the taskbar, but clicking on it does nothing. I ended up having to kill Spectacle from the terminal. EXPECTED RESULT Settings are saved and Spectacle records H.264 video successfully. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481338] New: Pressing ESC to close the Overview effect can hang KWin
https://bugs.kde.org/show_bug.cgi?id=481338 Bug ID: 481338 Summary: Pressing ESC to close the Overview effect can hang KWin Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY Unfortunately (?), I've only encountered this once. I have not reproduced it yet, although I'm not in the habit of closing Overview with a shortcut so I may not encounter it again organically. STEPS TO REPRODUCE 1. Have a bunch of applications running in a Plasma 6 Wayland session. 2. Open Overview. (I did this with a hot corner.) 3. Pres the ESC key. OBSERVED RESULT KWin immediately hangs, with the Overview effect still visible on the screen. Cursor not visible. Restarting plasmashell in a vterm did not resolve the issue, so I had to kill (and lost) my session. EXPECTED RESULT No hang; ordinarily the ESC key closes the effect. I immediately tried to reproduce the issue just now, and this ordinarily works. It's not clear to me what was different about this other instance. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481335] New: Edge trigger (hot corner) for Overview effect cycles between Overview and "Grid View", with no way to change this
https://bugs.kde.org/show_bug.cgi?id=481335 Bug ID: 481335 Summary: Edge trigger (hot corner) for Overview effect cycles between Overview and "Grid View", with no way to change this Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY I've had an edge trigger for the "present windows" effect for as long as I've been using KDE. At some point, during the transition to Plasma 6, this became the "overview" effect. "Present Windows" is still available as an edge trigger action, however. This is actually nice, because it helped me discover the Overview effect, and I really like it. What I have no use for, however, is the "grid view" effect. This is an effect that displays the virtual desktops in a grid, and has the default global shortcut Meta+G; the KCM for the Overview effect calls it "grid view". Unfortunately, if you hit the hot corner again when the Overview effect is displayed, it goes to grid view instead. I'd prefer it to simply toggle the overview (closing it and returning to the previous desktop view). STEPS TO REPRODUCE 1. Enable "Overview" as one of your edge trigger actions. 2. Hit the edge trigger to launch overview. Hit the edge trigger again. OBSERVED RESULT The Overview effect changes and becomes the "Grid View" instead. EXPECTED RESULT The edge trigger should probably have multiple options, e.g. "Overview", "Overview - Grid View", and "Overview - Cycle". This would be similar to how "Present Windows" has multiple edge trigger options to change its behavior. On the other hand, toggling between the two Overview views is very strange behavior, given that the main Overview effect already shows the virtual desktops. Unsurprisingly, there isn't a default global shortcut to toggle the views like this. So an alternative might be to have the edge trigger just toggle Overview, with no other options. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
