[digikam] [Bug 480345] Crash when reading Exif.Photo.UserComment containing emoji
https://bugs.kde.org/show_bug.cgi?id=480345 --- Comment #12 from caulier.gil...@gmail.com --- Do you means that i can switch also the Exiv2 version for MXE to 0.28.x now ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 480345] Crash when reading Exif.Photo.UserComment containing emoji
https://bugs.kde.org/show_bug.cgi?id=480345 --- Comment #11 from Maik Qualmann --- We also have the problem with the file path encoding with the VCPKG build. Which I don't understand since this build was supposed to use Windows' Utf8 API. But it's not a problem because in this case we automatically fall back to ExifTool - so it's just a performance problem. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479086] “window preview” Fade effect, and non-interactable areas
https://bugs.kde.org/show_bug.cgi?id=479086 --- Comment #14 from Fernando M. Muniz --- Further proof that the fade is glitch when using that way, is that if you have both windows you're comparing maximized the fade works as intended, just like the gif. -- 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.
[plasma-browser-integration] [Bug 481425] Pulling in Relevant Information with Plasma Integration
https://bugs.kde.org/show_bug.cgi?id=481425 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com Resolution|--- |INTENTIONAL --- Comment #2 from fanzhuyi...@gmail.com --- This would lead to many privacy concerns. For bug reporting, you can copy that information by going to system settings->about this system -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481441] Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland
https://bugs.kde.org/show_bug.cgi?id=481441 --- Comment #1 from fanzhuyi...@gmail.com --- *** Bug 481442 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481442] Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland
https://bugs.kde.org/show_bug.cgi?id=481442 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 481441 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480072] cannot disable window drag on left click in window (kdenlive) bloody annoying
https://bugs.kde.org/show_bug.cgi?id=480072 --- Comment #4 from djhbr...@gmail.com --- there is an app bug in the kde bug reporting user interface... because it takes up so much space with rhubarb it doesn't let a commenter see the last comment she is commenting on! and this bug is a kde design concept bug, not a kdenlive implementation bug, because any icon is of necessity immediately adjacent to background - that's where the edge of the icon is. Your suggestion of increasing the invisible drag area is a good workaround, but in my view, it's a Band-Aid solution to a problem that should never have been there in the first place, because background window drag is a completely unnecessary and idiotic idea. Swiping might be good for flipping through photos of drag artists, but kde would have you dragging their whole photo album window around instead. It's ridiculous! Imagine if trombones were designed like that - every time you wanted to play a different pitch, the trombone would fly out of your hands and hit the first violinist on the back of her head! i will leave it to you to decide what to tell kde cuckoo drag artist designers :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #257 from brenb...@brenbarn.net --- (In reply to Nate Graham from comment #253) > Experience also shows that even > if we did something super in-your-face and added a giant banner in the > Region & Language KCM that said: > > "ALERT! Changing this only affects KDE apps! It will not affect the way > dates are expressed in any non-KDE app such as Thunderbird, Firefox, Chrome, > LibreOffice, and Blender" > > ...then I can 100% guarantee you that we would *still* get bug reports from > confused users complaining that Thunderbird, Firefox, Chrome, LibreOffice, > and Blender don't respect their date display preferences. And we would have > to explain the underlying reason over and over again. To put it bluntly, so what? Just create a FAQ about it and close those bug reports as invalid. The fact that people will ask why it doesn't work in all cases doesn't seem like a good reason to not fix it in some cases. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 424633] Clicking on a link to open in external browser makes the article scroll to top in Akregator
https://bugs.kde.org/show_bug.cgi?id=424633 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/akregator/-/merge_requests/47 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481444] Switching users fails to show the SDDM if only 1 user
https://bugs.kde.org/show_bug.cgi?id=481444 fanzhuyi...@gmail.com changed: What|Removed |Added Severity|critical|major CC||fanzhuyi...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from fanzhuyi...@gmail.com --- Can't reproduce on plasma 6 source build, wayland, arch linux -- switching user works as expected even when there is only one user. Could you provide the output of journalctl -b when this happens? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #256 from Kevin Kofler --- Also, there is no consistency anyway, since console and GTK applications use glibc locales, whereas Qt uses ICU locales and only tries to map the glibc locales to those internally. So you end up with en_DK working in everything except Qt applications and en_SE working only in Qt applications, making those popular workarounds for more international-friendly English locales useless. And for the same reason, a custom glibc locale will also not work in Qt applications. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #255 from Kevin Kofler --- I am in general very much for consistency, but being consistently wrong is just not helpful. Even within a country, there can be distinct regional, local, ethnical, or personal preferences, so just having these settings be per country (or per language/country pair for those countries speaking more than one language) just cannot cover it. And many users prefer having their system in English (or some other foreign language), but still expect date formats etc. to follow the rules of their country (but not using its language for weekdays, month names, etc.), which is not covered by the locale system either. So the status quo is frequently not just not according to the user preferences, but genuinely wrong. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481390] Recording H.264 doesn't work
https://bugs.kde.org/show_bug.cgi?id=481390 Doug changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||dougsha...@protonmail.com --- Comment #1 from Doug --- Spectacle is hanging on me when i Record a Rectangular Region in either H.264 or WebM. Otherwise, I am getting the same results- the Apply button is not activated, and video settings aren't saved upon restart of Spectacle. Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-18-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Pro WX 3200 Series -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481444] New: Switching users fails to show the SDDM if only 1 user
https://bugs.kde.org/show_bug.cgi?id=481444 Bug ID: 481444 Summary: Switching users fails to show the SDDM if only 1 user Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ghostcode...@gmail.com Target Milestone: --- If there's only 1 user using the same computer, whether it's a Desktop PC or a laptop, and that user attempts to switch users through KDE' Application Launcher, a black screen appears where the SDDM should. STEPS TO REPRODUCE: 1. From with KDE's Application Launcher, click on "Leave", then click on "Switch User". OBSERVED RESULT: A black screen appears in place of the SDDM. EXPECTED RESULT: The SDDM should appear as normal. As of this writing, my current system specs is as follows: Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Mesa version: 23.3.5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481443] Switching from X11 to Wayland causes black screen due to SDDM
https://bugs.kde.org/show_bug.cgi?id=481443 GhostCoder22 changed: What|Removed |Added Summary|Wwitching from X11 to |Switching from X11 to |Wayland causes black screen |Wayland causes black screen |due to SDDM |due to SDDM -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 479964] Lock screen showing PKCS#11 error and referring to smart cards and fingerprint when neither have been set up
https://bugs.kde.org/show_bug.cgi?id=479964 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478780] Overview Animation Laggy and Low Frame Rate
https://bugs.kde.org/show_bug.cgi?id=478780 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479617] dolphin crashed when trying to view properties of file
https://bugs.kde.org/show_bug.cgi?id=479617 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396335] Gaming mouse loses configuration after booting windows, is restored by reconnecting it again
https://bugs.kde.org/show_bug.cgi?id=396335 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481443] New: Wwitching from X11 to Wayland causes black screen due to SDDM
https://bugs.kde.org/show_bug.cgi?id=481443 Bug ID: 481443 Summary: Wwitching from X11 to Wayland causes black screen due to SDDM 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: ghostcode...@gmail.com Target Milestone: --- Even though I'm able to successfully switch from Wayland to X11, switching from X11 back to Wayland however requires a reboot otherwise the set SDDM causes the screen to go completely black which then requires me to force me to shutdown my laptop in order to reboot it. STEPS TO REPRODUCE: 1. From with KDE's Application Launcher, click on "Leave", then click on "Log Out". 2. From within the SDDM that appears, click on "Desktop session" to the bottom-left, then click on "Wayland". OBSERVED RESULT: Setting the desktop session from X11 to Wayland produces a black screen. EXPECTED RESULT: Setting the desktop session from X11 to Wayland should bring up the Linux desktop. As of this writing, my current system specs is as follows: Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Mesa version: 23.3.5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481442] New: Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland
https://bugs.kde.org/show_bug.cgi?id=481442 Bug ID: 481442 Summary: Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland 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: ghostcode...@gmail.com Target Milestone: --- I'm a relatively new Linux user having just switched from Windows 22H2 over to Fedora 39 KDE Desktop spin several months ago. My chosen Graphics Platform is Wayland. My problem is, Calibre E-book Editor has the GUI option of undocking two sub-window panes (which I accidentally did while exploring the application) and I cannot figure out how to re-dock them within Wayland. I tried switching to X11 to re-dock the undocked sub-windows, and even though I was successful in redocking the undocked sub-windows, they re-undock themselves after switching back to Wayland. I even tried double-clicking on the two sub-windows I wish to re-dock to the main Calibre E-book Editor window, but all that does is maximize the sub-window I double-clicked the title bar of. STEPS TO REPRODUCE: 1. From within ebook-editor (Calibre E-book Editor), click on the undock button at the docked window pane. 2. Double-click undocked sub-window. OBSERVED RESULT: Undocked sub-window fails to redock when the Graphics Platform is set to Wayland. EXPECTED RESULT: Sub-window should redock to the main Calibre E-book Editor window when the Graphics Platform is set to Wayland. As of this writing, my current system specs is as follows: Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Mesa version: 23.3.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481254] moving desktop icons from one monitor to another results the icons don't show up on the second monitor
https://bugs.kde.org/show_bug.cgi?id=481254 Doug changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dougsha...@protonmail.com Ever confirmed|0 |1 --- Comment #1 from Doug --- Can reproduce. Icons don't have to be there during upgrade to KDE6. You can add icons and move them and reproduce. Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-18-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Pro WX 3200 Series -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481441] New: Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland
https://bugs.kde.org/show_bug.cgi?id=481441 Bug ID: 481441 Summary: Undocking sub-window panes fails to re-dock when Graphics Platform is Wayland 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: ghostcode...@gmail.com Target Milestone: --- I'm a relatively new Linux user having just switched from Windows 22H2 over to Fedora 39 KDE Desktop spin several months ago. My chosen Graphics Platform is Wayland. My problem is, Calibre E-book Editor has the GUI option of undocking two sub-window panes (which I accidentally did while exploring the application) and I cannot figure out how to re-dock them within Wayland. I tried switching to X11 to re-dock the undocked sub-windows, and even though I was successful in redocking the undocked sub-windows, they re-undock themselves after switching back to Wayland. I even tried double-clicking on the two sub-windows I wish to re-dock to the main Calibre E-book Editor window, but all that does is maximize the sub-window I double-clicked the title bar of. STEPS TO REPRODUCE: 1. From within ebook-editor (Calibre E-book Editor), click on the undock button at the docked window pane. 2. Double-click undocked sub-window. OBSERVED RESULT: Undocked sub-window fails to redock when the Graphics Platform is set to Wayland. EXPECTED RESULT: Sub-window should redock to the main Calibre E-book Editor window when the Graphics Platform is set to Wayland. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481392] The line seperating the attached side panel from the main view should imho stop where it meets the horizontal line above the status bar
https://bugs.kde.org/show_bug.cgi?id=481392 Doug changed: What|Removed |Added CC||dougsha...@protonmail.com --- Comment #4 from Doug --- I think another benefit of that line continuing to the bottom of the window is consistency when in dual pane mode. It would look odd without that line there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462932] Add preview videos for all effects
https://bugs.kde.org/show_bug.cgi?id=462932 nealheine...@gmail.com changed: What|Removed |Added CC||nealheine...@gmail.com --- Comment #1 from nealheine...@gmail.com --- These are so helpful for understanding what effects these options control. For new users like myself its essential for effects related to things like modal dialogs. I'm not sure what these are so I wouldn't know how to test it. Sidenote: These effects are awesome and the level of customization is the best out there; keep up the great work! Also I see that this request is over a year old, if I can help with recording videos let me know. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481437] Cannot click KHamburger menu when "Configure Toolbar" window is open
https://bugs.kde.org/show_bug.cgi?id=481437 Doug changed: What|Removed |Added Summary|Cannot click KHamburger |Cannot click KHamburger |menu|menu when "Configure ||Toolbar" window is open Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481437] Cannot click KHamburger menu
https://bugs.kde.org/show_bug.cgi?id=481437 Doug changed: What|Removed |Added CC||dougsha...@protonmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Doug --- Can reproduce Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-18-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Pro WX 3200 Series -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 481438] Main window is blocked
https://bugs.kde.org/show_bug.cgi?id=481438 Doug changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||dougsha...@protonmail.com --- Comment #1 from Doug --- It looks like in Dolphin or Okular, the toolbars are locked when the Configure Toolbar window is open, but one can still interact with the menus and document content. In Kate, nothing can be interacted with when the Configure Toolbar window is open. It is inconsistent, for sure, but is there a benefit to being able to interact with some of the interface, but not all? I am guessing the toolbar has to be locked to edit it? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 479141] Graphical glitches in presentation mode
https://bugs.kde.org/show_bug.cgi?id=479141 --- Comment #10 from Doug --- (In reply to Albert Astals Cid from comment #9) > Does the problem go away when not using wayland? No, it is only a problem in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 481101] Enable File Search can't be permanently disabled
https://bugs.kde.org/show_bug.cgi?id=481101 --- Comment #3 from MarkW --- (In reply to MarkW from comment #2) > > * Do you see the snapshots "elsewhere" in the filesystem? > > Yes, these snapshots are elsewhere in the filesystem, but I specifically > disabled `baloo` from indexing those locations a while back: > > exclude > folders[$e]=$HOME/.cache/,$HOME/.local/,/mnt/,/run/media/,/.snapshot/,/home/.snapshot;/config I've just had a "doh!" moment. The paths for the snapshots is wrong in the exclude folders setting. They should be `.snapshots`, not `.snapshot`. I have corrected them and re-enabled baloo now to see whether its bad behaviour continues, or whether it will now settle down. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 48118] per directory notes on side bar
https://bugs.kde.org/show_bug.cgi?id=48118 Doug changed: What|Removed |Added CC||fi...@tutanota.com --- Comment #2 from Doug --- *** Bug 480976 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480976] Desktop Effects Window Open/Close Animation "Scale": Task Switcher creates enormous graphical artefacts on screen when "Window close scale" is set to a high number
https://bugs.kde.org/show_bug.cgi?id=480976 Doug changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #4 from Doug --- *** This bug has been marked as a duplicate of bug 48118 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481420] Sort by video length
https://bugs.kde.org/show_bug.cgi?id=481420 --- Comment #4 from nealheine...@gmail.com --- Created attachment 165878 --> https://bugs.kde.org/attachment.cgi?id=165878=edit Current video sort options -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481420] Sort by video length
https://bugs.kde.org/show_bug.cgi?id=481420 --- Comment #3 from nealheine...@gmail.com --- (In reply to Patrick Silva from comment #2) > > *** This bug has been marked as a duplicate of bug 406506 *** Forgive my ignorance on this matter, but I dont see where this is a duplicate request of 406506, I've read through it a couple times and while I understand that resolving request 406506 would have to be completed in order to start thinking about how you would sort by video length on folders not indexed, I dont see any mention about sorting videos by length. Also as it stands now, a video folder that is indexed still requires an awkward workaround to be sorted by length. The only sort options under video are aspect ratio or famerate. See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 481101] Enable File Search can't be permanently disabled
https://bugs.kde.org/show_bug.cgi?id=481101 --- Comment #2 from MarkW --- Thanks for your comprehensive reply. > There has to be something else messing with it, this is not the usual > behaviour... I'm stumped as to what is causing this TBH. > If it is disabled it generally stays disabled, and you can see the option in > the >.config/baloofilerc When I execute `balooctl disable`, `~/.config/baloofilerc` is updated by adding the following to the top of the file: >[Basic Settings] >Indexing-Enabled=false Once I reboot, the above is once again deleted from the file and baloo_file keeps running. > Keep an eye on this, see if it is being changed back. You could try setting > the config to "read only"... Making it read only once it is disabled works. Thanks! > * Do you see the snapshots "elsewhere" in the filesystem? Yes, these snapshots are elsewhere in the filesystem, but I specifically disabled `baloo` from indexing those locations a while back: ``` exclude folders[$e]=$HOME/.cache/,$HOME/.local/,/mnt/,/run/media/,/.snapshot/,/home/.snapshot;/config ``` > * If you do a "stat one-of-your-files.txt", do you see the device number > and inode of the file change (after the snapshot/reboot)? No, the device number and inode remain unchanged. > * If you do a "balooshow one-of-your-files.txt" do you see the DocID > change? (the Id is built from the device number and inode. The way this is > done has recently been changed to avoid reindexing, specifically in the BTRFS > case) No, the `DocID` stays the same. > * If you do a "baloosearch -i one-of-your-files.txt" do you get a single > result or many? I get a single result. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374426] HTML email is unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=374426 318...@gmail.com changed: What|Removed |Added CC||318...@gmail.com --- Comment #3 from 318...@gmail.com --- This is still an issue for me on Linux Mint 21.3 Cinnamon with the Kontact 23.08.4 flatpak. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481440] New: No Audio - Identified Kernel Issue from Arch - with Solution - See Links in Description
https://bugs.kde.org/show_bug.cgi?id=481440 Bug ID: 481440 Summary: No Audio - Identified Kernel Issue from Arch - with Solution - See Links in Description Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kirk.h...@gmail.com Target Milestone: --- Hello Manjaro Triagers, first - much love to you all, have been appreciating Manjaro for several years now. 2nd - please reply if possible - if this issue is yet known there with team. I am Trying to decide if perhaps I should return the laptop SUMMARY - There is an identified issue for many newer laptops with built in amplifiers. Arch has apparently started to fix the issue for certain kernels but it has not moved here yet it seems. Im running 6.6.10-1 My Device Asus Zenbook Um3402Ya Here are links of Arch Team Members who have reputation to post about the issue https://wiki.archlinux.org/title/ASUS_Zenbook_UM3402YA https://superuser.com/questions/1719920/no-sound-from-internal-speakers-on-laptop-but-headphone-jack-and-hdmi-works/1754954#1754954 https://gist.github.com/masselstine/8fe9634b4c31cef07b8dfab089e4eb38 OBSERVED RESULT - No Audio EXPECTED RESULT - Audio SOFTWARE/OS VERSIONS Windows: Yes Dual Boot Windows 11 Linux/KDE Plasma: 6.6.10-1 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 481394] Ability to sort search results in the import screen
https://bugs.kde.org/show_bug.cgi?id=481394 --- Comment #2 from Ben Wilson-Hill --- (In reply to Urs Fleisch from comment #1) > The import results are sorted in exactly the order of the tracks. This order > is fixed. The import results can be reordered by using the "Match with:" > buttons or by drag'n'drop of rows. This concept does not allow another sort > order. Normally it shouldn't be a problem to keep track of the results, as > they only contain the tracks from a single album. Thank you Urs. I should've been more specific sorry. The track-listing is quite manageable, it's the album list I find I have the problem. If it could show maybe a little more information - eg. Country of release, or something like that, that could make identifying the specific release more efficient is what I was thinking. Or even the ability to search against release number could be a good solution?! Just to give you an idea, I was looking up "In Utero" by Nirvana. There are over 400 entries in Discogs, and adding more search terms in Kid3, I can eliminate most irrelevant results. I can find the details on the website, but matching it against the search results in Kid3 can be a bit tedious in cases like these. Just a way to sort those results more easily would be great. Let me know if some screenshots could be useful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #8 from Dominic --- I know it's insecure and a bad practice but I ran kdesu systemsettings and was able to enter the modules that are broken. Could it be a plasmoid or colorscheme is causing things to break? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #254 from Dotan Cohen --- (In reply to Nate Graham from comment #253) > We can indeed implement option 1 and fix this issue for KDE apps. > Thank you. I'm sure that the two hundred people here commenting, and untold frustrated others, appreciate this. > If your perspective is "I would rather have it work the way I want at least > some of the time than none of the time", that's valid. > Thank you. > The problem is that if we make this possible to satisfy those people, we're > making the system more confusing for people who don't have that preference, > or don't even know that that preference is a thing that can exist. > I understand your viewpoint, and I appreciate you conceding that viewpoint to the KDE users who have been begging for this horrible bug to be fixed for years. > Gradually we're trying to move away from what I call "broken promise" global > options: options that are presented as global in scope but really aren't > because they only affect some parts of the system. Experience shows that > these options are a recurring source of bug reports from normal users as > well as picky technical users who care a lot about consistency. > Then maybe just label the feature "KDE Date Format" as that is all that KDE can effect. Or even a stand-alone KDE Settings tool (not in System Settings) to make the change, so that no one will complain that it does not affect the entire System. In any case, that promise is broken already in System Settings in some other places, for instance Windows appearance options do not affect Java nor WXwidgets applications. > When we can't fully get rid of kinds of options, we try to add textual > explanations, but even those are imperfect. Experience also shows that even > if we did something super in-your-face and added a giant banner in the > Region & Language KCM that said: > > "ALERT! Changing this only affects KDE apps! It will not affect the way > dates are expressed in any non-KDE app such as Thunderbird, Firefox, Chrome, > LibreOffice, and Blender" > > ...then I can 100% guarantee you that we would *still* get bug reports from > confused users complaining that Thunderbird, Firefox, Chrome, LibreOffice, > and Blender don't respect their date display preferences. And we would have > to explain the underlying reason over and over again. > Then put the options in a KDE Settings submenu, or a standalone KDE settings application to compliment System Settings. But KDE users need this bug fixed. > So for you folks who want it to at least work some of the time because some > is better than none, I understand your perspective, but hopefully you can > see how satisfying this preference would make the system less coherent to > people without that preference. Yes, I see both perspectives. Now which is the lesser evil: KDE applications do not respect cultural date formats and there is absolutely no solution (so KDE apps display their dates wrong), or some people might be confused as to why they need to configure their non-KDE apps' date formats in addition to their KDE date format setting? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404 --- Comment #6 from 318...@gmail.com --- This is still an issue for me on Linux Mint 21.3 Cinnamon using the Kontact 23.08.4 flatpak. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme
https://bugs.kde.org/show_bug.cgi?id=383404 318...@gmail.com changed: What|Removed |Added CC||318...@gmail.com --- Comment #5 from 318...@gmail.com --- Created attachment 165877 --> https://bugs.kde.org/attachment.cgi?id=165877=edit A screenshot of Kontact's feed reader, showing the application in Breeze Dark but the feed content in a light theme -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481439] New: Consistent UI proposal
https://bugs.kde.org/show_bug.cgi?id=481439 Bug ID: 481439 Summary: Consistent UI proposal Classification: Applications Product: dolphin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: saileshpoud...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 165876 --> https://bugs.kde.org/attachment.cgi?id=165876=edit POC SUMMARY Having the same line strip thickness would make the plasma look more consistent. Using repetition as a design principle to make it look more consistent. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480554] Sound theme window hides some icons when resized in French (and probably other locals too)
https://bugs.kde.org/show_bug.cgi?id=480554 Ismael Asensio changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/3e1bb77e9ee0a5d3cff71798b |t/3a59f73ac8f50d5b0f9a025d0 |a257bfbfc96b7e5 |2d1f720430011b8 --- Comment #3 from Ismael Asensio --- Git commit 3a59f73ac8f50d5b0f9a025d02d1f720430011b8 by Ismael Asensio. Committed on 17/02/2024 at 00:40. Pushed by iasensio into branch 'Plasma/6.0'. kcms/soundtheme: Fix items overflowing the card Allow the label to shrink and elide, so it doesn't push the buttons out of the card's frame, which can happen with larger fonts or in more verbose languages. With this also drop the "compact mode" concept and just place the general preview button above. It simplifies the layout and avoids UI jumpiness and edge cases. We cannot currently set a minimum size for the cards right now, so let's adapt to it the best way possible. FIXED-IN: 6.0 (cherry picked from commit 3e1bb77e9ee0a5d3cff71798ba257bfbfc96b7e5) M +8-4kcms/soundtheme/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/3a59f73ac8f50d5b0f9a025d02d1f720430011b8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 481438] New: Main window is blocked
https://bugs.kde.org/show_bug.cgi?id=481438 Bug ID: 481438 Summary: Main window is blocked Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: saileshpoud...@gmail.com Target Milestone: --- SUMMARY After opening Configure Toolbars window, we cannot use the main window or the menu. STEPS TO REPRODUCE 1. Open kate 2. Open Configure Toolbars 3. Now the menu is blocked in main window. OBSERVED RESULT Main window is blocked. EXPECTED RESULT Main window shouldn't be blocked. Opening other applications with same window doesn't block the main window like dolphin and okular. SOFTWARE/OS VERSIONS Using plasma 6.1 dev on neon unstable in wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464856] Non-maximized auto-hidden Panel should un-hide when cursor moves to any part of its screen edge, not just the part of the edge that's over the panel
https://bugs.kde.org/show_bug.cgi?id=464856 --- Comment #8 from Nate Graham --- True. I wonder how often people put a single small auto-hide panel on a screen edge though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464856] Non-maximized auto-hidden Panel should un-hide when cursor moves to any part of its screen edge, not just the part of the edge that's over the panel
https://bugs.kde.org/show_bug.cgi?id=464856 --- Comment #7 from fanzhuyi...@gmail.com --- (In reply to Nate Graham from comment #6) > (In reply to fanzhuyifan from comment #5) > > One concern is that this might degrade the ability to interact with other UI > > elements near screen edges, like scroll bars on the right. > It's already an issue, so at least that wouldn't be a regression. I think this would be a regression if such an auto-hide panel has small length. Currently it only interferes with the part of the edge corresponding to its shape, but with this change it will interfere with interactions on the whole edge. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 439129] Add the ability to uninstall the emoji selector
https://bugs.kde.org/show_bug.cgi?id=439129 nealheine...@gmail.com changed: What|Removed |Added CC||nealheine...@gmail.com --- Comment #1 from nealheine...@gmail.com --- I also cannot uninstall on Debian testing. Since this issue is more widespread I think this should be triaged to the plasmashell team. As for my use case I would like to use a different emoji app, I should be free to do so. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464856] Non-maximized auto-hidden Panel should un-hide when cursor moves to any part of its screen edge, not just the part of the edge that's over the panel
https://bugs.kde.org/show_bug.cgi?id=464856 --- Comment #6 from Nate Graham --- (In reply to fanzhuyifan from comment #5) > One concern is that this might degrade the ability to interact with other UI > elements near screen edges, like scroll bars on the right. It's already an issue, so at least that wouldn't be a regression. > Another question is whether we want to support multiple auto-hide panels on > the same edge. That's a good point. My first thought is that if there's only one auto-hide panel, make its activation zone span the entire screen edge. And if there's more than one, don't, and give each one an activation zone linked to its shape. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481437] New: Cannot click KHamburger menu
https://bugs.kde.org/show_bug.cgi?id=481437 Bug ID: 481437 Summary: Cannot click KHamburger menu Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: saileshpoud...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY After certain criteria is met, khamburger menu need to be clicked nearly 5 or more times to open the menu. STEPS TO REPRODUCE 1. Open dolphin. 2. Open configure toolbars 3. Now click on Khamburger menu of dolphin. OBSERVED RESULT Menu click doesn't effect the button for certain clicks. EXPECTED RESULT Khamburger menu should be clickable without any delay clicks. SOFTWARE/OS VERSIONS Tested on plasma 6.1 dev from neon unstable. I am on wayland. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 479333] Unable to print non-A4 page sizes correctly with KDE applications
https://bugs.kde.org/show_bug.cgi?id=479333 --- Comment #4 from Leisquid Li --- (In reply to Nate Graham from comment #3) > Thanks. Oh you're welcome. Best regards, Leisquid Li -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469819] kbd_backlight restored to wrong value after lid close-open
https://bugs.kde.org/show_bug.cgi?id=469819 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464856] Non-maximized auto-hidden Panel should un-hide when cursor moves to any part of its screen edge, not just the part of the edge that's over the panel
https://bugs.kde.org/show_bug.cgi?id=464856 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #5 from fanzhuyi...@gmail.com --- I think this makes sense -- currently having both screen edge actions and a auto-hiding panel on the same edge is broken anyways. One concern is that this might degrade the ability to interact with other UI elements near screen edges, like scroll bars on the right. Another question is whether we want to support multiple auto-hide panels on the same edge. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480554] Sound theme window hides some icons when resized in French (and probably other locals too)
https://bugs.kde.org/show_bug.cgi?id=480554 Ismael Asensio changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/3e1bb77e9ee0a5d3cff71798b ||a257bfbfc96b7e5 Version Fixed In||6.0 --- Comment #2 from Ismael Asensio --- Git commit 3e1bb77e9ee0a5d3cff71798ba257bfbfc96b7e5 by Ismael Asensio. Committed on 17/02/2024 at 00:20. Pushed by iasensio into branch 'master'. kcms/soundtheme: Fix items overflowing the card Allow the label to shrink and elide, so it doesn't push the buttons out of the card's frame, which can happen with larger fonts or in more verbose languages. With this also drop the "compact mode" concept and just place the general preview button above. It simplifies the layout and avoids UI jumpiness and edge cases. We cannot currently set a minimum size for the cards right now, so let's adapt to it the best way possible. FIXED-IN: 6.0 M +8-4kcms/soundtheme/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/3e1bb77e9ee0a5d3cff71798ba257bfbfc96b7e5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480828] kwin: poor experience with Gtk apps and 175% display scaling
https://bugs.kde.org/show_bug.cgi?id=480828 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/104 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481282] Screen edge effect does not correspond with actual length of edge that can be triggered
https://bugs.kde.org/show_bug.cgi?id=481282 --- Comment #8 from Nate Graham --- My thinking would be that the entire screen edge would both highlight visually and also act as a triggering area. So the visual effect would match the triggering area, not the panel width. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481282] Screen edge effect does not correspond with actual length of edge that can be triggered
https://bugs.kde.org/show_bug.cgi?id=481282 --- Comment #7 from fanzhuyi...@gmail.com --- (In reply to Nate Graham from comment #4) > Sort of mutually exclusive with Bug 464856; maybe we should mark that as > INTENTIONAL? Or change this around to implement that, rather than this? Oh do you mean in that case we would want the edge trigger effect to only highlight the panel, but make the edge trigger everywhere? That would require deeper changes to the current code I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481282] Screen edge effect does not correspond with actual length of edge that can be triggered
https://bugs.kde.org/show_bug.cgi?id=481282 --- Comment #6 from Nate Graham --- I see, cool. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 481245] Spurious crash when copying to the clipboard in plasma mobile
https://bugs.kde.org/show_bug.cgi?id=481245 --- Comment #1 from Paul Sajna --- It seems related to the toast/popup the browser has when it does a copy successfully in bitwarden web vault. Messing with kwin somehow. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481282] Screen edge effect does not correspond with actual length of edge that can be triggered
https://bugs.kde.org/show_bug.cgi?id=481282 --- Comment #5 from fanzhuyi...@gmail.com --- (In reply to Nate Graham from comment #4) > Sort of mutually exclusive with Bug 464856; maybe we should mark that as > INTENTIONAL? Or change this around to implement that, rather than this? I don't think it is mutually exclusive -- we can just make the panel reserve the whole edge and we could solve both issues. The commit fixing this was only about the visual effect code, and making it consistent with what was requested. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481397] functional issue with window management
https://bugs.kde.org/show_bug.cgi?id=481397 saxn changed: What|Removed |Added Platform|Arch Linux |Neon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481397] functional issue with window management
https://bugs.kde.org/show_bug.cgi?id=481397 saxn changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from saxn --- (In reply to Nate Graham from comment #1) I am using wayland. On neon unstable. Trying out new plasma 6.1 beta. The issue is seen both on overview effect and desktop grid effect. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406506] Wish - Show metadata of files stored on locations non-indexed by baloo in details view mode
https://bugs.kde.org/show_bug.cgi?id=406506 Patrick Silva changed: What|Removed |Added CC||nealheine...@gmail.com --- Comment #23 from Patrick Silva --- *** Bug 481420 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481420] Sort by video length
https://bugs.kde.org/show_bug.cgi?id=481420 Patrick Silva changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 406506 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481282] Screen edge effect does not correspond with actual length of edge that can be triggered
https://bugs.kde.org/show_bug.cgi?id=481282 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464856 --- Comment #4 from Nate Graham --- Sort of mutually exclusive with Bug 464856; maybe we should mark that as INTENTIONAL? Or change this around to implement that, rather than this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464856] Non-maximized auto-hidden Panel should un-hide when cursor moves to any part of its screen edge, not just the part of the edge that's over the panel
https://bugs.kde.org/show_bug.cgi?id=464856 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=481282 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461561] Confusing default device in Display Configuration when using monitor with laptop screen disabled
https://bugs.kde.org/show_bug.cgi?id=461561 --- Comment #5 from Nate Graham --- Fixed by David Edmundson with https://invent.kde.org/plasma/kscreen/-/commit/5cf9c326baabfd8b55cee7fa09ef3c0a9b488f42! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479466] Extra, unwanted accessibility events coming from system tray items
https://bugs.kde.org/show_bug.cgi?id=479466 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/fc1055ff81118573ef6d63100 |t/4c49e11e60581db58ad79613e |de8d3a3958a867a |5b4d70e39446fc6 --- Comment #4 from Fushan Wen --- Git commit 4c49e11e60581db58ad79613e5b4d70e39446fc6 by Fushan Wen. Committed on 16/02/2024 at 23:50. Pushed by fusionfuture into branch 'Plasma/6.0'. applets/systemtray: remove unnecessary focus hack FIXED-IN: 6.0 (cherry picked from commit fc1055ff81118573ef6d63100de8d3a3958a867a) M +46 -13 appiumtests/systemtraytest.py M +1-1applets/systemtray/package/contents/ui/ExpanderArrow.qml M +1-7applets/systemtray/package/contents/ui/items/AbstractItem.qml M +0-5applets/systemtray/package/contents/ui/items/ItemLoader.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/4c49e11e60581db58ad79613e5b4d70e39446fc6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481433] With System Settings' minimum window size, buttons in per-event notification UI can get pushed out of the frame
https://bugs.kde.org/show_bug.cgi?id=481433 Ismael Asensio changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/761eb760023315ba280a14676 |t/879de1b4cc9a5011f325cc564 |d182e935db4ffd8 |ac9c19754841194 --- Comment #3 from Ismael Asensio --- Git commit 879de1b4cc9a5011f325cc564ac9c19754841194 by Ismael Asensio. Committed on 16/02/2024 at 23:22. Pushed by iasensio into branch 'Plasma/6.0'. kcms/notifications: Fix delegate's minimum size The RowLayout within the delegate will not shrink below its content's implicit width, even when it overflows the external width constraint. We can use some Layout properties in a creative way to reduce this, so that the TextField can shrink but keeps its regular size when the space available is wider. FIXED-IN: 6.0 (cherry picked from commit 761eb760023315ba280a14676d182e935db4ffd8) M +5-0kcms/notifications/ui/ApplicationConfiguration.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/879de1b4cc9a5011f325cc564ac9c19754841194 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479466] Extra, unwanted accessibility events coming from system tray items
https://bugs.kde.org/show_bug.cgi?id=479466 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/fc1055ff81118573ef6d63100 ||de8d3a3958a867a Version Fixed In||6.0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Fushan Wen --- Git commit fc1055ff81118573ef6d63100de8d3a3958a867a by Fushan Wen. Committed on 16/02/2024 at 23:20. Pushed by fusionfuture into branch 'master'. applets/systemtray: remove unnecessary focus hack FIXED-IN: 6.0 M +46 -13 appiumtests/systemtraytest.py M +1-1applets/systemtray/package/contents/ui/ExpanderArrow.qml M +1-7applets/systemtray/package/contents/ui/items/AbstractItem.qml M +0-5applets/systemtray/package/contents/ui/items/ItemLoader.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/fc1055ff81118573ef6d63100de8d3a3958a867a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 --- Comment #3 from Bernhard --- Might be worth mentioning that Alacrity (the terminal) is also set to use plasma background blur effect (in case there is some strange interaction) On Fri, 16 Feb 2024, 23:17 Niccolò Venerandi, wrote: > https://bugs.kde.org/show_bug.cgi?id=481380 > > Niccolò Venerandi changed: > >What|Removed |Added > > > CC||nicc...@venerandi.com > > --- Comment #2 from Niccolò Venerandi --- > (This seems to be the contrast effect) > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481392] The line seperating the attached side panel from the main view should imho stop where it meets the horizontal line above the status bar
https://bugs.kde.org/show_bug.cgi?id=481392 --- Comment #3 from 31...@tuta.io --- I said no other app looks like proposal 2b and for kde apps this is true (to my knowledge), but it might still be worth mentioning that PCManFM-Qt from the lxqt project does it like that. Since it's another file manager using qt, I thought it might be relevant. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481433] With System Settings' minimum window size, buttons in per-event notification UI can get pushed out of the frame
https://bugs.kde.org/show_bug.cgi?id=481433 Ismael Asensio changed: What|Removed |Added Version Fixed In||6.0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/761eb760023315ba280a14676 ||d182e935db4ffd8 --- Comment #2 from Ismael Asensio --- Git commit 761eb760023315ba280a14676d182e935db4ffd8 by Ismael Asensio. Committed on 16/02/2024 at 21:50. Pushed by iasensio into branch 'master'. kcms/notifications: Fix delegate's minimum size The RowLayout within the delegate will not shrink below its content's implicit width, even when it overflows the external width constraint. We can use some Layout properties in a creative way to reduce this, so that the TextField can shrink but keeps its regular size when the space available is wider. FIXED-IN: 6.0 M +5-0kcms/notifications/ui/ApplicationConfiguration.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/761eb760023315ba280a14676d182e935db4ffd8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480554] Sound theme window hides some icons when resized in French (and probably other locals too)
https://bugs.kde.org/show_bug.cgi?id=480554 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3917 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481435] Annotations made while in Rectangular Region overlay end up in the wrong place
https://bugs.kde.org/show_bug.cgi?id=481435 --- Comment #6 from Nate Graham --- Greaṫ! But now I have to wonder: in what universe do you do a Rectangular Region screenshot and not drag a box around something? :D Isn't that the use case of Rectangular Region instead of Full Screen? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481435] Annotations made while in Rectangular Region overlay end up in the wrong place
https://bugs.kde.org/show_bug.cgi?id=481435 Noah Davis changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Noah Davis --- Ok, so I did not test actually cropping the rectangle screenshot. The problem occurs when I actually set a rectangular area to capture. Curiously, the problem only applies to the last annotation. Previous annotations are fine and the problem goes away if I undo and redo the last annotation. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 --- Comment #25 from Valter Mura --- I also tried "apt-get --check" and I got the following: The following packages has unmet dependencies: kpim6-akonadi-contacts : Depends: kf6-ktextaddons (>= 0.0.1+p22.04+vstable+git20240206.0340) but it is not installed kpim6-kidentitymanagement : Depends: kf6-ktextaddons (>= 0.0.1+p22.04+vstable+git20240208.0427) but it is not installed kpim6-kpimtextedit : Depends: kf6-ktextaddons (>= 0.0.1+p22.04+vstable+git20240206.0340) but it is not installed kpim6-libkleo : Depends: kf6-ktextaddons (>= 0.0.1+p22.04+vstable+git20240208.0427) but it is not installed libsasl2-modules-kdexoauth2 : Depends: libkpimgapi5-data but it is not installed So, I tried, again, to give the command "apt --fix-broken-install" and I got the following errors (in Italian, sorry, I cannot now translate the strings): Preparativi per estrarre .../kf6-ktextaddons_0.0.1+p22.04+vstable+git20240215.0159-0_amd64.deb... Estrazione di kf6-ktextaddons (0.0.1+p22.04+vstable+git20240215.0159-0)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/kf6-ktextaddons_0.0.1+p22.04+vstable+git20240215.0159-0_amd64.deb (--unpack): tentata sovrascrittura di "/usr/share/locale/ar/LC_MESSAGES/libtextautocorrection.mo" presente anche nel pacchetto libkf5textaddons-data 1.5.2+p22.04+vstable+git20240109.0209-0 dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe interrotta) Preparativi per estrarre .../libkpimgapi5-data_23.08.4+p22.04+vstable+git20240207.0942-0_all.deb... Estrazione di libkpimgapi5-data (23.08.4+p22.04+vstable+git20240207.0942-0)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libkpimgapi5-data_23.08.4+p22.04+vstable+git20240207.0942-0_all.deb (--unpack): tentata sovrascrittura di "/usr/share/locale/ar/LC_MESSAGES/libkgapi_qt.qm" presente anche nel pacchetto libkpimgapi-data 23.08.4+p22.04+vstable+git20240108.0456-0 Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/kf6-ktextaddons_0.0.1+p22.04+vstable+git20240215.0159-0_amd64.deb /var/cache/apt/archives/libkpimgapi5-data_23.08.4+p22.04+vstable+git20240207.0942-0_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481392] The line seperating the attached side panel from the main view should imho stop where it meets the horizontal line above the status bar
https://bugs.kde.org/show_bug.cgi?id=481392 --- Comment #2 from 31...@tuta.io --- (In reply to Nate Graham from comment #1) > The current look is intentional, sorry. If the line didn't go all the way to > the bottom, then the sidebar would lack an unbroken visual line that makes > it clearly look like a sidebar as in other KDE apps with sidebars. I never had an issue with that line in other apps, so I went through a bunch of kde apps to see what's different here. I think I have identified it. In other apps, the sidebar usually has a different background colour than the bottom bar below the main view, or -in absence of a bar at the bottom - the main view itself. Also, there are some other kde apps that also have a status bar at the bottom, for example kid3, filelight and kate, and there the line and the sidebar usually end above the status bar and the horizontal line above the status bar goes all the way across. Though it is noteworthy that unlike in those examples, in dolphin the status bar contents have always been limited to only below the main view. So there is in my opinion some inconsistency, but my proposed solution was false. Unless you really just want to keep it as it is (in which case, okay, fine, I'll get used to it), I have two (and a half) other ideas for your consideration based on my observations above. 1. Change the colour of the sidebar to match the main view instead of the status bar. -> looks like, for example, systemsettings pages that have a bar at the bottom 2. Change the colour of the sidebar to match the main view instead of the status bar and make the horizontal line above the statusbar extend all the way across and stop the vertical line of the sidebar above the statusbar -> looks like, for example, kate, filelight, kid3 (2b. Same as 2., without changing the colour of the sidebar. -> looks like no other app, but I can see the argument that having a different colour for the main view and the sidebar just looks better in a file manager.) If you don't want to do any of that, that's also fine, I'm not going to annoy you any further -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 481293] The context menu of the selectable label opens at wrong position
https://bugs.kde.org/show_bug.cgi?id=481293 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/qqc2-desktop-style/- ||/commit/3c64f731aa115372964 ||fff2756d3d874953526ae Version Fixed In||6.0 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Fushan Wen --- Git commit 3c64f731aa115372964fff2756d3d874953526ae by Fushan Wen. Committed on 16/02/2024 at 22:56. Pushed by fusionfuture into branch 'master'. Menu: fix TextFieldContextMenu opening at wrong position QQuickMenu places the menu based on the size of its parent and its size, but when all menu items are invisible, the ListView in Menu.qml calculates its contentHeight based on an assumed average size (100), which causes the menu height to become excessively huge when there are many invisible menu items, so when repositioning the menu will be placed at a wrong position. This uses childrenRect.height to only include visible items. FIXED-IN: 6.0 M +5-3org.kde.desktop/Menu.qml https://invent.kde.org/frameworks/qqc2-desktop-style/-/commit/3c64f731aa115372964fff2756d3d874953526ae -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481435] Annotations made while in Rectangular Region overlay end up in the wrong place
https://bugs.kde.org/show_bug.cgi?id=481435 --- Comment #4 from Nate Graham --- I just tried it with my dual-screen setup (4k@225% on the left, 1080p@110% on the right) and got the same result. Here's a video that shows it happening, in case my description was not clear enough. I couldn't attach it as I was unable to compress it enough to get it under the 4 MB size limit on Bugzilla. https://imgur.com/zr2utzN -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479184] Remove/Restrict Spectacle's nonotify option in the wayland session context for security reasons
https://bugs.kde.org/show_bug.cgi?id=479184 --- Comment #7 from Nate Graham --- I appreciate your understanding. FWIW the sandboxing and portals systems seem designed to support a use case where we can't necessarily trust our own apps, more akin to the Google Play store on Android. However from my perspective this is ceding most of the field before battle has even been joined. If we can't prevent the user from installing actively malicious software on their system, I think we've already lost. Android shows us what this world looks like: 99% of the free apps on the Google Play store are garbage that's at best only mildly user-hostile and at worse is using every dark pattern in the book to try to harm you. Even the strongest sandbox is no protection at all for local software that can trick the user into giving it permission to do whatever it wants. This approach passes the buck by saying, "well, I told you there was a risk, you you clicked on the Accept button anyway!" But it should be obvious that this is not an effective system for truly protecting the user. We have decades of experience to show us that regular people will click on anything, won't read dialogs, don't understand digital risks, etc. Putting the responsibility on them is wrong. Personally I think what we should be striving for us to keep actively bad software out of our apps stores and software repos in the first place, and therefore off the devices of casual users who are least able to manage the risks of malicious apps. But this is a much larger topic. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480104] # Plasmashell crashed when Media Player Widget was activated (after wake up from sleep)
https://bugs.kde.org/show_bug.cgi?id=480104 --- Comment #2 from Balázs R. --- (In reply to Akseli Lahtinen from comment #1) > Hi, can you install debug symbols and try to reproduce the crash? Thanks! > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Debian Hi, I don't know what does it exactly mean, but I try ... - I have read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ - I have setup DEBUGINFOD_URLS in: /etc/profile, ~/.profile, ~/.bashrc - apt-get install debuginfod elfutils gdb plasma-desktop-dev - reboot - reproduced bug - Application: Plasma (plasmashell), signal: Segmentation fault PID: 1728 (plasmashell) UID: 1000 (bazsi) GID: 1000 (bazsi) Signal: 11 (SEGV) Timestamp: Fri 2024-02-16 23:34:49 CET (14s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (bazsi) Boot ID: 261c1e6ee05e422091b7c326f455ac11 Machine ID: e8665c6cbce94f97b11ac43a0734db52 Hostname: charlie Storage: /var/lib/systemd/coredump/core.plasmashell.1000.261c1e6ee05e422091b7c326f455ac11.1728.170812288900.zst (present) Size on Disk: 51.1M Message: Process 1728 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 1728: #0 0x7f02c7ca9e2c __pthread_kill_implementation (libc.so.6 + 0x8ae2c) #1 0x7f02c7c5afb2 __GI_raise (libc.so.6 + 0x3bfb2) #2 0x7f02ca24cb46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f02c7c5b050 __restore_rt (libc.so.6 + 0x3c050) #4 0x7f02c7ca9e2c __pthread_kill_implementation (libc.so.6 + 0x8ae2c) #5 0x7f02c7c5afb2 __GI_raise (libc.so.6 + 0x3bfb2) #6 0x7f02c7c5b050 __restore_rt (libc.so.6 + 0x3c050) #7 0x7f02c7ca4e94 __futex_abstimed_wait_common64 (libc.so.6 + 0x85e94) #8 0x7f02c7ca7558 __pthread_cond_wait_common (libc.so.6 + 0x88558) #9 0x7f02c7ed1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #10 0x7f02c9c0bd58 n/a (libQt5Quick.so.5 + 0x20bd58) #11 0x7f02c9c0d013 n/a (libQt5Quick.so.5 + 0x20d013) #12 0x7f02c85493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1493f5) #13 0x7f02c8d62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #14 0x7f02c80b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #15 0x7f02c853e5cd _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e5cd) #16 0x7f02c8511cac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111cac) #17 0x7f02c2afbeca n/a (libQt5XcbQpa.so.5 + 0x6deca) #18 0x7f02c6a527a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #19 0x7f02c6a52a38 n/a (libglib-2.0.so.0 + 0x54a38) #20 0x7f02c6a52acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #21 0x7f02c8109836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f02c80b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7f02c80b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x55d4d3fc6dc3 n/a (plasmashell + 0x26dc3) #25 0x7f02c7c4624a __libc_start_call_main (libc.so.6 + 0x2724a) #26 0x7f02c7c46305 __libc_start_main_impl (libc.so.6 + 0x27305) #27 0x55d4d3fc6ee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1763: #0 0x7f02c7d1b15f __GI___poll (libc.so.6 + 0xfc15f) #1 0x7f02c6a529ae n/a (libglib-2.0.so.0 + 0x549ae) #2 0x7f02c6a52acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #3 0x7f02c810984e _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30984e) #4 0x7f02c80b017b
[neon] [Bug 480704] BIG CRASH AFTER LATEST UPDATE IN TESTING EDITION - 2024-02-01
https://bugs.kde.org/show_bug.cgi?id=480704 --- Comment #24 from Valter Mura --- (In reply to Valter Mura from comment #21) > HI, > ok, the system now restarted, but returns the following error: > "Aggiornamento di 1 pacchetto non riuscito > Error while installing package: trying to overwrite > '/usr/share/locale/ar/LC_MESSAGES/libtextautocorrection.mo', which is also > in package libkf5textaddons-data 1.5.2+p22.04+vstable+git20240109.0209-0" > > Now, many things don't work, for example: > - Firefox doesn't have Icon > - Widgets don't work, returning the error: "This widget was written for an > unknown older version of Plasma and is not compatible with Plasma 6. Please > contact the widget's author for an updated version.Error loading applet: > Package does not exist." (unknown widget); and "This widget was written for > an unknown older version of Plasma and is not compatible with Plasma 6. > Contact the author of the widget for an updated version." (Weather Widget > and Key State); for System Monitor widget, no sensor is available. > - Lokalize crashes; KDEsvn crashes > > I attach a screenshot of my desktop > > My present system: > Operating System: KDE neon Testing Edition > KDE Plasma Version: 6.0.0 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.1 > Kernel Version: 6.5.0-14-generic (64-bit) > Graphics Platform: Wayland > Graphics Processor: NVE7 I'm still stuck in this error... I can't go further... I don't know if there's a workaround. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 455189] Icons-only buttons don't become text-only buttons when telling the system to show text instead of icons on buttons
https://bugs.kde.org/show_bug.cgi?id=455189
--- Comment #10 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<4wy78...@rokejulianlockhart.addy.io> ---
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #9)
> (In reply to Nate Graham from comment #8)
> > This is fixed in KF6.
>
> Surely, per
> https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/
> 367#note_871639 and
> https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/
> 367#note_870785, this is not remediated?
Ah —
https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/367#note_872508.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 455189] Icons-only buttons don't become text-only buttons when telling the system to show text instead of icons on buttons
https://bugs.kde.org/show_bug.cgi?id=455189
--- Comment #9 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<4wy78...@rokejulianlockhart.addy.io> ---
(In reply to Nate Graham from comment #8)
> This is fixed in KF6.
Surely, per
https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/367#note_871639
and
https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/367#note_870785,
this is not remediated?
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 481435] Annotations made while in Rectangular Region overlay end up in the wrong place
https://bugs.kde.org/show_bug.cgi?id=481435 Nate Graham changed: What|Removed |Added Version|23.04.1 |git-master --- Comment #3 from Nate Graham --- That is a mistake, it's current git master. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications
https://bugs.kde.org/show_bug.cgi?id=481069 --- Comment #7 from Nate Graham --- (In reply to Flossy Cat from comment #6) > Anyhow, my counterquestion was not rhetorical, but in earnest. I really > think it worth answering, because together we have just demonstrated that a > valuable and powerful feature was removed on a whim without checking its > user base and its UX value: > > How does KDE know which features are unused and how is removal decided? We largely have no idea. It's an unfortunate side effect of our commitment to not spy on our users. It means we're in the dark about what they actually do with our software when they're not somehow making noise about it publicly. Features that get bug reports and that people are talking about in public (on social media, in our forum, in reviews of our software, etc) are features that we know people use. Other ones... well, we don't. We try not to remove stuff for no reason, but when a feature's code is old and flawed at a fundamental level and it seems like it's blocking an effort to do something new, that's when the feature is going to end up on the chopping block rather than getting fixed if no one can find anyone who uses it. This is obviously pretty flawed but I don't know how we can do any better without turning to the dark side and spying on our users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481430] my workspace/plasmashell crashes and turn to black, flashing repeatedly
https://bugs.kde.org/show_bug.cgi?id=481430 --- Comment #3 from athos2...@gmail.com --- thanks! Em sex., 16 de fev. de 2024 às 17:34, escreveu: > https://bugs.kde.org/show_bug.cgi?id=481430 > > fanzhuyi...@gmail.com changed: > >What|Removed |Added > > > Resolution|--- |UNMAINTAINED > Status|REPORTED|RESOLVED > CC||fanzhuyi...@gmail.com > > --- Comment #2 from fanzhuyi...@gmail.com --- > Thank you for your bug report! > > Debian advises users to not submit bugs upstream > (https://www.debian.org/Bugs/Reporting), as this version of the KDE > software is > out of support from KDE, and so it's possible that the bug exists only in > Debian at this point. > Could you report the bug to Debian using the report bug utility > (https://packages.debian.org/stable/utils/reportbug)? If necessary, the > maintainer of the package will forward the bug upstream. > > Thanks for understanding! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481380] Docked floating panel obscures adjacent screen with its blurred background
https://bugs.kde.org/show_bug.cgi?id=481380 Niccolò Venerandi changed: What|Removed |Added CC||nicc...@venerandi.com --- Comment #2 from Niccolò Venerandi --- (This seems to be the contrast effect) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481433] With System Settings' minimum window size, buttons in per-event notification UI can get pushed out of the frame
https://bugs.kde.org/show_bug.cgi?id=481433 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3916 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible
https://bugs.kde.org/show_bug.cgi?id=481197 Niccolò Venerandi changed: What|Removed |Added CC||nicc...@venerandi.com Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #6 from Niccolò Venerandi --- Mh, yeah, reopening as this seems to be its own issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481379] Sometimes Panel continuously floats and defloats when window is in the wrong spot (or the right spot?!)
https://bugs.kde.org/show_bug.cgi?id=481379 fanzhuyi...@gmail.com changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/ |9309df10945cf092a5a855b8d34 |e3a270ef18ecc85624e2c835d2e |c6b024060b77b |49f6b1cca382b --- Comment #11 from fanzhuyi...@gmail.com --- Git commit e3a270ef18ecc85624e2c835d2e49f6b1cca382b by Yifan Zhu. Committed on 16/02/2024 at 21:37. Pushed by fanzhuyifan into branch 'Plasma/6.0'. Panel: use new API to calculate regionGeometry Previously the compensation for floatingness was done in qml, which had rounding errors that caused the panel to continuously float/defloat. Use new api that calculates regionGeometry independent of floatingness. This also simplifies the code. FIXED-IN: 6.0 (cherry picked from commit 9309df10945cf092a5a855b8d34c6b024060b77b) M +2-4desktoppackage/contents/views/Panel.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/e3a270ef18ecc85624e2c835d2e49f6b1cca382b -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481420] Sort by video length
https://bugs.kde.org/show_bug.cgi?id=481420 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- (In reply to nealheinecke from comment #0) > I'd like to be able to sort videos by length. I do understand the workaround > by enabling indexing then sorting by audio length, but this not intuitive to > new users and doesn't work for removable media. It does appear that there is > a duration listed for files not indexed in the details tab of file > properties, so the information is already collected to sort by. The duration is metadata embedded in each of the files. To get it you either need to open the file, extract and decode the metadata or ask a service that has already done it Dolphin, on it's own, reads enough of the file to get the duration (when you look at the properties, after an F11) but it doesn't read the metadata of all the files it shows you and give you the durations in a "duration" column. When Dolphin sees that Baloo is running and has indexed the folder, it will ask it for the "Duration" values and display them. You can then sort them. So, yes. You can do this but you depend on Baloo having done the work -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 481389] Possible "fix" for reliability issues
https://bugs.kde.org/show_bug.cgi?id=481389 --- Comment #2 from Robert Walker --- Thanks for the consideration and info - great to know different SMS functions will have their own threads. I'll continue to monitor and try to contribute how I can. I think this is a great effort and something that I find very valuable; if there are other ways I can contribute please don't hesitate to ping me (testing, documentation, etc.). I'm new to the KDE project but have a pretty significant C# & SQL background and hope to get involved soon. Thanks for the effort! -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 481436] Error code 11 when adding specific RSS feed
https://bugs.kde.org/show_bug.cgi?id=481436 --- Comment #1 from Marco Boneff --- Sorry, this is probably a duplicate of bug 443286. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481434] Every time I wait 2-3 seconds until I can do something after putting the pen down
https://bugs.kde.org/show_bug.cgi?id=481434 Halla Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- Hi Charlotte, I'm sorry, but this is very likely a problem with your system, and not with Krita. This sounds like it might be better to ask other Krita users for advice, instead of filing a bug report: our most active community forum is https://krita-artists.org. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479184] Remove/Restrict Spectacle's nonotify option in the wayland session context for security reasons
https://bugs.kde.org/show_bug.cgi?id=479184 --- Comment #6 from Noah Davis --- To be clear, if there was infrastructure for a more comprehensive solution that spectacle could adopt, I would not oppose that. I just oppose removing this option for the reasons already given. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 481436] New: Error code 11 when adding specific RSS feed
https://bugs.kde.org/show_bug.cgi?id=481436 Bug ID: 481436 Summary: Error code 11 when adding specific RSS feed Classification: Applications Product: kasts Version: 23.08.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: marco.bon...@gmail.com Target Milestone: --- Created attachment 165873 --> https://bugs.kde.org/attachment.cgi?id=165873=edit Error message (in italian, sorry) Cannot add feed *** Any attempt to add Destination Linux feed fails with error code 11 *** STEPS TO REPRODUCE 1. Open Kasts 2. Select Subscriptions 3. Click on "Add podcast" 4. Paste the podcast feed: https://destinationlinux.org/feed/mp3/ 5. Confirm OBSERVED RESULT Podcast update fails with error 11 EXPECTED RESULT Episodes list is fetched SOFTWARE/OS VERSIONS Linux Manjaro Linux x86_64 Kasts running in GNOME 45.3 Kasts version 23.08.4-1 (Official Package) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 480609] Ugly gap between Yakuake's window and a floating top panel
https://bugs.kde.org/show_bug.cgi?id=480609 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3915 -- You are receiving this mail because: You are watching all bug changes.
