[frameworks-baloo] [Bug 434919] Baloo does not exclude folders correctly if $HOME has a trailing slash
https://bugs.kde.org/show_bug.cgi?id=434919 --- Comment #5 from Oded Arbel --- (In reply to Nate Graham from comment #4) > Oh nice! > > An alternative or supplemental solution might be to sanitize the input paths > entered using the KCM, which lives in plasma-desktop. That wouldn't work as an alternative in this case as the KCM sets up the paths using $HOME/ (and I think that's correct) so in my case KCM would still cause the config file to contain the double slash. That code change, does cause the KCM to display the configured paths as "~//folder name", which is a bit weird, so some modification there might also be in order - I'll take a look. -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 428748] If there is no sound device, plasma_session crashes in Phonon::Factory::backend() on login
https://bugs.kde.org/show_bug.cgi?id=428748 --- Comment #5 from tildearrow --- (In reply to Harald Sitter from comment #2) > Unfortunately that backtrace is fairly useless -> > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Backtraces Unfortunately, I do not have any time to recompile the entirety of KDE and Qt in order to reproduce a bug that happens once every 3 months. I am very sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393957] Horizontal layout option for horizontal panels
https://bugs.kde.org/show_bug.cgi?id=393957 Nate Graham changed: What|Removed |Added Version Fixed In||5.22 Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||cd68df165a9360e6c0f94b7f7c0 ||c7ebb04df370a Resolution|--- |FIXED --- Comment #12 from Nate Graham --- Git commit cd68df165a9360e6c0f94b7f7c0c7ebb04df370a by Nate Graham, on behalf of Momo Cao. Committed on 26/03/2021 at 04:56. Pushed by ngraham into branch 'master'. Add a setting to show date and time in one line FIXED-IN: 5.22 M +8-0applets/digital-clock/package/contents/config/main.xml M +7-13 applets/digital-clock/package/contents/ui/DigitalClock.qml M +20 -4applets/digital-clock/package/contents/ui/configAppearance.qml https://invent.kde.org/plasma/plasma-workspace/commit/cd68df165a9360e6c0f94b7f7c0c7ebb04df370a -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 428506] There are two "Add new account" buttons when no account is configured
https://bugs.kde.org/show_bug.cgi?id=428506 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Patrick Silva --- Fixed on neon unstable. :) Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428977] Dragging tabs from Firefox over the desktop results in a crash
https://bugs.kde.org/show_bug.cgi?id=428977 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #14 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.
[kdenlive] [Bug 429611] gst_audio_format_from_string: assertion 'format != NULL' failed
https://bugs.kde.org/show_bug.cgi?id=429611 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.
[plasmashell] [Bug 415316] Plasmashell crashed when scrolling with mousewheel on the network widget
https://bugs.kde.org/show_bug.cgi?id=415316 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[kdenlive] [Bug 420639] kdenlive UI crash - modifying transform effect parameter (any)
https://bugs.kde.org/show_bug.cgi?id=420639 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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.
[plasmashell] [Bug 418246] Multimedia keys of keyboard not working in 5.17 and 5.18
https://bugs.kde.org/show_bug.cgi?id=418246 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #25 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.
[plasmashell] [Bug 432994] Crash on display rotate
https://bugs.kde.org/show_bug.cgi?id=432994 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[krusader] [Bug 434293] krusader - two markings instead of one
https://bugs.kde.org/show_bug.cgi?id=434293 --- 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.
[kdenlive] [Bug 415324] KDenLive User interface is blank
https://bugs.kde.org/show_bug.cgi?id=415324 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[plasmashell] [Bug 430511] Hang when multiple virtual desktops are renamed to empty name
https://bugs.kde.org/show_bug.cgi?id=430511 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kdenlive] [Bug 403079] Kdenlive crash when click on project monitor tab
https://bugs.kde.org/show_bug.cgi?id=403079 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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.
[kdenlive] [Bug 424564] When I try to render a project, it never moves beyond the "waiting" phase
https://bugs.kde.org/show_bug.cgi?id=424564 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[phonon-backend-gstreamer] [Bug 428748] If there is no sound device, plasma_session crashes in Phonon::Factory::backend() on login
https://bugs.kde.org/show_bug.cgi?id=428748 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kdenlive] [Bug 403224] Freeze when opening projects or creating clips
https://bugs.kde.org/show_bug.cgi?id=403224 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 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.
[kdenlive] [Bug 431936] Audio playback issue when skipping to point in timeline
https://bugs.kde.org/show_bug.cgi?id=431936 --- Comment #8 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.
[krusader] [Bug 433353] "Move to trash" not working
https://bugs.kde.org/show_bug.cgi?id=433353 --- Comment #6 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.
[kdenlive] [Bug 430704] Pitch Compensation Disabled
https://bugs.kde.org/show_bug.cgi?id=430704 --- Comment #3 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.
[kdenlive] [Bug 424684] Project Fails to Load Files at 53%
https://bugs.kde.org/show_bug.cgi?id=424684 --- Comment #9 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.
[kwin] [Bug 422645] Often when Firefox starts, desktop content briefly shifts down and right
https://bugs.kde.org/show_bug.cgi?id=422645 --- Comment #6 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.
[kdenlive] [Bug 411292] Speed/Reverse adjustment clips not properly copying/pasting on timeline
https://bugs.kde.org/show_bug.cgi?id=411292 --- 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.
[kdenlive] [Bug 403532] [Feature Request] Shortcuts for multicam editing
https://bugs.kde.org/show_bug.cgi?id=403532 --- Comment #3 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.
[kdenlive] [Bug 399994] Fcitx not avaliabe with appimage
https://bugs.kde.org/show_bug.cgi?id=34 --- Comment #7 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.
[kdenlive] [Bug 409477] I can't open my project
https://bugs.kde.org/show_bug.cgi?id=409477 --- Comment #11 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.
[kdenlive] [Bug 365697] git master - moving to another workspace then coming back makes mouse pointer point to wrong position in layout (video example included)
https://bugs.kde.org/show_bug.cgi?id=365697 --- Comment #4 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.
[systemsettings] [Bug 414501] Cannot type accented characters (í, ã, etc) in any text fields in QML KCMs embedded in QWidgets view (works in the sidebar's text field)
https://bugs.kde.org/show_bug.cgi?id=414501 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Nate Graham --- I also cannot reproduce the issue any longer in Plasma 5.21. Looks like this got fixed. Hooray! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all
https://bugs.kde.org/show_bug.cgi?id=434949 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #3 from Nate Graham --- You're right, my mistake. Sorry about that. Is this just when setting shortcuts? It's not seen anywhere else? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] Fonts with a very tall baseline cause text to overflow into the next cell
https://bugs.kde.org/show_bug.cgi?id=434814 --- Comment #11 from Nate Graham --- In Plasma and QML-based apps, the size of practically everything is based on the metrics of the current font--including the baseline height. So if you use a font with a very tall baseline, everything will be bigger. That's what was going on. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 317666] juk startup is slow if using tree mode
https://bugs.kde.org/show_bug.cgi?id=317666 --- Comment #8 from Michael Pyne --- Git commit a65a4e8a037bae5d2731267b60ed61bf09526413 by Michael Pyne. Committed on 26/03/2021 at 01:52. Pushed by mpyne into branch 'release/21.04'. tag_scan: Fix painful rescan of music metadata on startup. For the longest time, JuK has suffered from a problem where its intended behavior to load music metadata from a cached database, instead of re-scanning every individual track on startup, was not working right. There has been debugging lines in JuK since all the way back to 2013 trying to trace what area of startup sequence was taking up all the time, but to no avail in helping me fix the bug. The Problem === Recently I took a different approach, of adding a debug-only crash whenever we would load a music track tag the "slow" way, and long story short there were two bugs that each would cause slowdown: 1. Playlists aside from the CollectionList would cause every music track in that playlist to be re-scanned. What this means is that every though the music in the CollectionList would be loaded quickly, if you had that same music track in a separate Playlist, that music track would reload the same tags from disk rather than copying from the existing CollectionList item. This was especially bad for users of the old "tree mode" view, since every individual artist *and* album were rendered as individual playlists, which would therefore each re-scan the music over and over again. 2. JuK supports a "folder scan" feature, and in fact really wants the user to have at least one folder assigned. Any music identified in this folder is added to the CollectionList automatically on startup and, you guessed it, causes the music track information to be loaded from disk, even if the music was already in the CollectionList! :( The net effect is that most music would be re-scanned on startup unless you were a user who used CollectionList exclusively, and had most of your music not visible to the folder scanner. The Solution Due to how painful this problem has been, I had ended up adding a threaded solution for the folder scan process. This didn't help make things any faster but at least the GUI wasn't frozen. But now that the threading code is present I judged it would be easier and safer to make the central object holding track metadata (CollectionList's m_itemsDict) available in thread-safe fashion. This then permitted me to check for whether a track has already been loaded when performing folder scan, and to check whether a track has already been loaded when creating a new (non-CollectionList) Playlist. In either event if the track already exists, then we copy the FileHandle rather than create a new one. The combination speeds up loading significantly, taking anywhere from 60% to 70% off of the total time to load on my system, with mostly a CollectionList under folder scan and few additional playlists. In this configuration I go from about 5.4 seconds to 1.5 seconds with cold caches. The difference should be even more stark on systems where disk I/O is expensive, or where there are a great number of tracks in playlists outside of the CollectionList. I consider this a bugfix (and there are even multiple bug reports) so I will backport shortly. CHANGELOG:Reduce startup time by 60-70% or more. Related: bug 428772 FIXED-IN:21.04 (cherry picked from commit d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab) M +58 -25 collectionlist.cpp M +5-3collectionlist.h M +11 -3directoryloader.cpp M +6-1filehandle.cpp M +10 -1playlist.cpp https://invent.kde.org/multimedia/juk/commit/a65a4e8a037bae5d2731267b60ed61bf09526413 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 428772] JuK painful folder scanning at the EVERY (Re)start
https://bugs.kde.org/show_bug.cgi?id=428772 --- Comment #2 from Michael Pyne --- Git commit a65a4e8a037bae5d2731267b60ed61bf09526413 by Michael Pyne. Committed on 26/03/2021 at 01:52. Pushed by mpyne into branch 'release/21.04'. tag_scan: Fix painful rescan of music metadata on startup. For the longest time, JuK has suffered from a problem where its intended behavior to load music metadata from a cached database, instead of re-scanning every individual track on startup, was not working right. There has been debugging lines in JuK since all the way back to 2013 trying to trace what area of startup sequence was taking up all the time, but to no avail in helping me fix the bug. The Problem === Recently I took a different approach, of adding a debug-only crash whenever we would load a music track tag the "slow" way, and long story short there were two bugs that each would cause slowdown: 1. Playlists aside from the CollectionList would cause every music track in that playlist to be re-scanned. What this means is that every though the music in the CollectionList would be loaded quickly, if you had that same music track in a separate Playlist, that music track would reload the same tags from disk rather than copying from the existing CollectionList item. This was especially bad for users of the old "tree mode" view, since every individual artist *and* album were rendered as individual playlists, which would therefore each re-scan the music over and over again. 2. JuK supports a "folder scan" feature, and in fact really wants the user to have at least one folder assigned. Any music identified in this folder is added to the CollectionList automatically on startup and, you guessed it, causes the music track information to be loaded from disk, even if the music was already in the CollectionList! :( The net effect is that most music would be re-scanned on startup unless you were a user who used CollectionList exclusively, and had most of your music not visible to the folder scanner. The Solution Due to how painful this problem has been, I had ended up adding a threaded solution for the folder scan process. This didn't help make things any faster but at least the GUI wasn't frozen. But now that the threading code is present I judged it would be easier and safer to make the central object holding track metadata (CollectionList's m_itemsDict) available in thread-safe fashion. This then permitted me to check for whether a track has already been loaded when performing folder scan, and to check whether a track has already been loaded when creating a new (non-CollectionList) Playlist. In either event if the track already exists, then we copy the FileHandle rather than create a new one. The combination speeds up loading significantly, taking anywhere from 60% to 70% off of the total time to load on my system, with mostly a CollectionList under folder scan and few additional playlists. In this configuration I go from about 5.4 seconds to 1.5 seconds with cold caches. The difference should be even more stark on systems where disk I/O is expensive, or where there are a great number of tracks in playlists outside of the CollectionList. I consider this a bugfix (and there are even multiple bug reports) so I will backport shortly. CHANGELOG:Reduce startup time by 60-70% or more. Related: bug 317666 FIXED-IN:21.04 (cherry picked from commit d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab) M +58 -25 collectionlist.cpp M +5-3collectionlist.h M +11 -3directoryloader.cpp M +6-1filehandle.cpp M +10 -1playlist.cpp https://invent.kde.org/multimedia/juk/commit/a65a4e8a037bae5d2731267b60ed61bf09526413 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 428772] JuK painful folder scanning at the EVERY (Re)start
https://bugs.kde.org/show_bug.cgi?id=428772 Michael Pyne changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/juk/commit/d6b28a9b4 ||c8e21a0b9ccd5bb7585091e501d ||94ab Version Fixed In||21.04 Status|REPORTED|RESOLVED --- Comment #1 from Michael Pyne --- Git commit d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab by Michael Pyne. Committed on 26/03/2021 at 01:48. Pushed by mpyne into branch 'master'. tag_scan: Fix painful rescan of music metadata on startup. For the longest time, JuK has suffered from a problem where its intended behavior to load music metadata from a cached database, instead of re-scanning every individual track on startup, was not working right. There has been debugging lines in JuK since all the way back to 2013 trying to trace what area of startup sequence was taking up all the time, but to no avail in helping me fix the bug. The Problem === Recently I took a different approach, of adding a debug-only crash whenever we would load a music track tag the "slow" way, and long story short there were two bugs that each would cause slowdown: 1. Playlists aside from the CollectionList would cause every music track in that playlist to be re-scanned. What this means is that every though the music in the CollectionList would be loaded quickly, if you had that same music track in a separate Playlist, that music track would reload the same tags from disk rather than copying from the existing CollectionList item. This was especially bad for users of the old "tree mode" view, since every individual artist *and* album were rendered as individual playlists, which would therefore each re-scan the music over and over again. 2. JuK supports a "folder scan" feature, and in fact really wants the user to have at least one folder assigned. Any music identified in this folder is added to the CollectionList automatically on startup and, you guessed it, causes the music track information to be loaded from disk, even if the music was already in the CollectionList! :( The net effect is that most music would be re-scanned on startup unless you were a user who used CollectionList exclusively, and had most of your music not visible to the folder scanner. The Solution Due to how painful this problem has been, I had ended up adding a threaded solution for the folder scan process. This didn't help make things any faster but at least the GUI wasn't frozen. But now that the threading code is present I judged it would be easier and safer to make the central object holding track metadata (CollectionList's m_itemsDict) available in thread-safe fashion. This then permitted me to check for whether a track has already been loaded when performing folder scan, and to check whether a track has already been loaded when creating a new (non-CollectionList) Playlist. In either event if the track already exists, then we copy the FileHandle rather than create a new one. The combination speeds up loading significantly, taking anywhere from 60% to 70% off of the total time to load on my system, with mostly a CollectionList under folder scan and few additional playlists. In this configuration I go from about 5.4 seconds to 1.5 seconds with cold caches. The difference should be even more stark on systems where disk I/O is expensive, or where there are a great number of tracks in playlists outside of the CollectionList. I consider this a bugfix (and there are even multiple bug reports) so I will backport shortly. CHANGELOG:Reduce startup time by 60-70% or more. Related: bug 317666 FIXED-IN:21.04 M +58 -25 collectionlist.cpp M +5-3collectionlist.h M +11 -3directoryloader.cpp M +6-1filehandle.cpp M +10 -1playlist.cpp https://invent.kde.org/multimedia/juk/commit/d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 317666] juk startup is slow if using tree mode
https://bugs.kde.org/show_bug.cgi?id=317666 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/juk/commit/d6b28a9b4 ||c8e21a0b9ccd5bb7585091e501d ||94ab Version Fixed In||21.04 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Michael Pyne --- Git commit d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab by Michael Pyne. Committed on 26/03/2021 at 01:48. Pushed by mpyne into branch 'master'. tag_scan: Fix painful rescan of music metadata on startup. For the longest time, JuK has suffered from a problem where its intended behavior to load music metadata from a cached database, instead of re-scanning every individual track on startup, was not working right. There has been debugging lines in JuK since all the way back to 2013 trying to trace what area of startup sequence was taking up all the time, but to no avail in helping me fix the bug. The Problem === Recently I took a different approach, of adding a debug-only crash whenever we would load a music track tag the "slow" way, and long story short there were two bugs that each would cause slowdown: 1. Playlists aside from the CollectionList would cause every music track in that playlist to be re-scanned. What this means is that every though the music in the CollectionList would be loaded quickly, if you had that same music track in a separate Playlist, that music track would reload the same tags from disk rather than copying from the existing CollectionList item. This was especially bad for users of the old "tree mode" view, since every individual artist *and* album were rendered as individual playlists, which would therefore each re-scan the music over and over again. 2. JuK supports a "folder scan" feature, and in fact really wants the user to have at least one folder assigned. Any music identified in this folder is added to the CollectionList automatically on startup and, you guessed it, causes the music track information to be loaded from disk, even if the music was already in the CollectionList! :( The net effect is that most music would be re-scanned on startup unless you were a user who used CollectionList exclusively, and had most of your music not visible to the folder scanner. The Solution Due to how painful this problem has been, I had ended up adding a threaded solution for the folder scan process. This didn't help make things any faster but at least the GUI wasn't frozen. But now that the threading code is present I judged it would be easier and safer to make the central object holding track metadata (CollectionList's m_itemsDict) available in thread-safe fashion. This then permitted me to check for whether a track has already been loaded when performing folder scan, and to check whether a track has already been loaded when creating a new (non-CollectionList) Playlist. In either event if the track already exists, then we copy the FileHandle rather than create a new one. The combination speeds up loading significantly, taking anywhere from 60% to 70% off of the total time to load on my system, with mostly a CollectionList under folder scan and few additional playlists. In this configuration I go from about 5.4 seconds to 1.5 seconds with cold caches. The difference should be even more stark on systems where disk I/O is expensive, or where there are a great number of tracks in playlists outside of the CollectionList. I consider this a bugfix (and there are even multiple bug reports) so I will backport shortly. CHANGELOG:Reduce startup time by 60-70% or more. Related: bug 428772 FIXED-IN:21.04 M +58 -25 collectionlist.cpp M +5-3collectionlist.h M +11 -3directoryloader.cpp M +6-1filehandle.cpp M +10 -1playlist.cpp https://invent.kde.org/multimedia/juk/commit/d6b28a9b4c8e21a0b9ccd5bb7585091e501d94ab -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] Fonts with a very tall baseline cause text to overflow into the next cell
https://bugs.kde.org/show_bug.cgi?id=434814 --- Comment #10 from cpum...@gmail.com --- One thing that I noticed is that everything changed on my system. Not just the widget explorer. I'm talking every single app, including non-KDE apps. My system looks completely different now. Buttons are smaller. Everything looks like it shrunk after resetting the fonts. The Application Launcher buttons are smaller, context menus are smaller, toolbars are smaller, etc. It seems like the resolution changed somehow with the font change. The only thing that makes sense to me is that maybe for some reason there was a newline character \n with the font which provided extra height to all the UI elements. I don't know why else this would happen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 434955] exception "assertion 'GDK_IS_DISPLAY (display)' failed is" thrown with "SystemTray" Kotlin/Java library
https://bugs.kde.org/show_bug.cgi?id=434955 solonova...@12oclockpoint.com changed: What|Removed |Added Version|unspecified |5.21.3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 434955] New: exception "assertion 'GDK_IS_DISPLAY (display)' failed is" thrown with "SystemTray" Kotlin/Java library
https://bugs.kde.org/show_bug.cgi?id=434955 Bug ID: 434955 Summary: exception "assertion 'GDK_IS_DISPLAY (display)' failed is" thrown with "SystemTray" Kotlin/Java library Product: Breeze Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: solonova...@12oclockpoint.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY "assertion 'GDK_IS_DISPLAY (display)' failed" is thrown many times while using the Kotlin/Java library "SystemTray" Relevant issues: - Suwayomi/Tachidesk issue: https://github.com/Suwayomi/Tachidesk/issues/38 - dorkbox/SystemTray issue: https://github.com/dorkbox/SystemTray/issues/142 We're currently unsure if the issue is being caused by SystemTray misusing the API, or by Breeze-GTK doing something weird. This only seems to occur with the Breeze GTK theme and no other themes. (Except the "Default" theme in the KDE GTK settings menu??) STEPS TO REPRODUCE 1. Enable Breeze theme 2. Run an application that contains the Kotlin/Java library "SystemTray" (eg. the application "Tachidesk") 3. The following is logged about 10 times before the program hangs, and does not do anything afterwards: (java:343959): Gdk-CRITICAL **: 12:13:43.182: gdk_x11_get_xatom_by_name_for_display: assertion 'GDK_IS_DISPLAY (display)' failed OBSERVED RESULT Application logs many errors & ceases to respond. EXPECTED RESULT The application doesn't error. SOFTWARE/OS VERSIONS Operating System Version: Arch Linux x86_64 5.10.11-arch1-1 Display Server: X11 DE Version: Plasmashell 5.21.3 Qt Version: 5.15.2 KDE Frameworks Version: 5.80.0 GPU Version: Nvidia RTX 2070 GPU Driver Version: 460.67-3 Breeze Version: 5.21.3-1, packages `breeze` and `breeze-gtk` from the AUR -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] Fonts with a very tall baseline cause text to overflow into the next cell
https://bugs.kde.org/show_bug.cgi?id=434814 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] Fonts with a very tall baseline cause text to overflow into the next cell
https://bugs.kde.org/show_bug.cgi?id=434814 Nate Graham changed: What|Removed |Added Summary|When a widget has a long|Fonts with a very tall |description, other buttons |baseline cause text to |will overlap the text |overflow into the next cell Resolution|WAITINGFORINFO |--- Status|RESOLVED|REPORTED --- Comment #9 from Nate Graham --- I had a feeling it was related to fonts. I'm glad it's fixed for you now, but we still need to fix this layout problem for everyone else who happens to be using a font like this. :) -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 434921] Removing the 'wacom' kernel module while a wacom tablet is plugged in freezes computer.
https://bugs.kde.org/show_bug.cgi?id=434921 --- Comment #2 from Noah --- (In reply to Valerii Malov from comment #1) > Can you please check if this is reproducible while your tablet is plugged > in, but you're not logged into KDE? > e.g. have only login manager running on one terminal, plug in the tablet & > run modprobe -r from another tty? I logged out of KDE so that I'm looking at the SDDM login screen on tty7, then switched to tty1 without a gui. Then, I logged in on tty1 and ran 'sudo modprobe -r wacom' while my tablet was connected. The same behavior occurred as when I was on the KDE desktop session, but the journalctl entry looks a little different for when I ran the command. It doesn't seem to show an error this time. journalctl reads: "Mar 25 20:09:56 darkTower sudo[19426]: noah : TTY=tty1 ; PWD=/home/noah ; USER=root ; COMMAND=/usr/sbin/modprobe -r wacom Mar 25 20:09:56 darkTower sudo[19426]: pam_unix(sudo:session): session opened for user root(uid=0) by noah(uid=1000) Mar 25 20:09:57 darkTower sudo[19426]: pam_unix(sudo:session): session closed for user root" -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434910] General sidebar button in Klipper settings can't accept left click in its upper area
https://bugs.kde.org/show_bug.cgi?id=434910 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/plasma/plasma-workspace/-/merge_requests/742 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 318538] Krunner grabs all key presses when no application has focus. Please make that feature configurable (plasma 4 and plasma 5)
https://bugs.kde.org/show_bug.cgi?id=318538 zeert...@outlook.com changed: What|Removed |Added CC||zeert...@outlook.com --- Comment #9 from zeert...@outlook.com --- This feature is also annoying when I am typing in a window and the desktop suddenly regains focus. This happened a few time when I began typing in Yakuake before the desktop had full started, but it can happen on other occasions at well. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434933] Balance calculation discrepancy in Future payments
https://bugs.kde.org/show_bug.cgi?id=434933 --- Comment #7 from Jack --- So the same file shows the problem on your desktop but not on your laptop, using the same version of KMM? Do you have the same Distro and version on both machines? If so, then it will likely remain a mystery. If not, you might try to figure out what other package you upgraded at the time the problem appeared. Specifically consider any of the packages the openSuse package of KMM depends on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] When a widget has a long description, other buttons will overlap the text
https://bugs.kde.org/show_bug.cgi?id=434814 cpum...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #8 from cpum...@gmail.com --- The problem is now fixed. Solution: After changing the font, I tried to change it back but realized that the option was unavailable. The original font that I was using was called Noto Sans. It was available, but called by different names such as "Noto Sans CJK HK" and "Noto Sans CJK JP." The plain option "Noto Sans" wasn't any of the choices. My fixed width font was called "Hack" but no longer exists. I am not sure why these fonts don't exist anymore since I never changed the settings for the fonts. It seems they got corrupted somehow over time from the updates. Strange. Maybe the real bug here is that fonts disappeared and the system thinks we're using the now non-existent fonts? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434904] Implement a triangle menu filter for Kickoff's categories sidebar
https://bugs.kde.org/show_bug.cgi?id=434904 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/396 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] When a widget has a long description, other buttons will overlap the text
https://bugs.kde.org/show_bug.cgi?id=434814 --- Comment #7 from Nate Graham --- Yeah there is definitely something weird with your font's baseline. No, it's not happening to me. What happens if you switch the "Normal" font to something else, and then back again? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] When a widget has a long description, other buttons will overlap the text
https://bugs.kde.org/show_bug.cgi?id=434814 --- Comment #6 from cpum...@gmail.com --- Do the labels also appear on top of the buttons on your computer? (Note: this is on the settings page for colors.) Besides this, I can't find any other potential place in Plasma where the same problem could be happening as with the widget explorer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434814] When a widget has a long description, other buttons will overlap the text
https://bugs.kde.org/show_bug.cgi?id=434814 --- Comment #5 from cpum...@gmail.com --- Created attachment 137067 --> https://bugs.kde.org/attachment.cgi?id=137067=edit Seems it might be happening with the colors page too with settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 434919] Baloo does not exclude folders correctly if $HOME has a trailing slash
https://bugs.kde.org/show_bug.cgi?id=434919 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Nate Graham --- Oh nice! An alternative or supplemental solution might be to sanitize the input paths entered using the KCM, which lives in plasma-desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434736] Option to use a grid instead of a list for all right panel views, not just the favorites view
https://bugs.kde.org/show_bug.cgi?id=434736 --- Comment #11 from Marco --- Unfortunately classic plain menu always "lags" in any circumstances when overloaded with installed applications, and with every graphic card. Other menus se can add as plasmoids are way too simple to cover all the functionality kickoff 2.0 finally covers in a functional way. We, as user, only lack the chance customize It a Little more to make It perfect to our needs. I always thought What distinguishes KDE from other DE Is High customization to one's needs. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434888] Add support for AVIF images
https://bugs.kde.org/show_bug.cgi?id=434888 Albert Astals Cid changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/c38af3e6 ||95be5e0cd59732effdc5bb7d63a ||67951 --- Comment #12 from Albert Astals Cid --- Git commit c38af3e695be5e0cd59732effdc5bb7d63a67951 by Albert Astals Cid. Committed on 24/03/2021 at 22:42. Pushed by aacid into branch 'release/21.04'. Add a few more formats supported by qimageformat plugins Related: bug 434889 M +6-1generators/kimgio/libokularGenerator_kimgio.json M +1-1generators/kimgio/okularApplication_kimgio.desktop M +1-1generators/kimgio/okularKimgio.desktop M +1-1generators/kimgio/org.kde.mobile.okular_kimgio.desktop https://invent.kde.org/graphics/okular/commit/c38af3e695be5e0cd59732effdc5bb7d63a67951 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434889] Add support for WEBP images
https://bugs.kde.org/show_bug.cgi?id=434889 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/c38af3e6 ||95be5e0cd59732effdc5bb7d63a ||67951 --- Comment #2 from Albert Astals Cid --- Git commit c38af3e695be5e0cd59732effdc5bb7d63a67951 by Albert Astals Cid. Committed on 24/03/2021 at 22:42. Pushed by aacid into branch 'release/21.04'. Add a few more formats supported by qimageformat plugins Related: bug 434888 M +6-1generators/kimgio/libokularGenerator_kimgio.json M +1-1generators/kimgio/okularApplication_kimgio.desktop M +1-1generators/kimgio/okularKimgio.desktop M +1-1generators/kimgio/org.kde.mobile.okular_kimgio.desktop https://invent.kde.org/graphics/okular/commit/c38af3e695be5e0cd59732effdc5bb7d63a67951 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434736] Option to use a grid instead of a list for all right panel views, not just the favorites view
https://bugs.kde.org/show_bug.cgi?id=434736 --- Comment #10 from Marco --- But at least leave the user the freedom over that, freedom of choice and customization to their needs, I don't think this switch would be weird at all when searching. It's a thing other KDE menus already do. Even vanilla Gnome does that. I, as a visual and usability designer myself working for 20 Years in this field (even though not in open source projects) don't think, and my point is this, that it is weirder than having that aspect covered only in One part of the menu and not in all the others, I can see why It has been chosen ti show "favorites" but then it's inconsistent to leave the chance to view them back "in a list". So, I'm asking where Is the consistecy of that First choicein First hand then?. It's Just handy. Handy as It would be applied to the rest for visual and very fast users. It's like being visually ergonomic and convenient. Not quite like removing One click or two to complete One task, but It goes really close to that for some users like me Who would like to see non proprietary software reach some peaks. We had tò wait for so long tò reach a functional vanilla menù ok KDE. Precipua kickoff wasn't so convenient. And the alternative basic menu always, always, renders poorly when there are a lot of applications installed If you Will, technically speaking, under the light of design principles What we have now It Is indeed inconsistent for perceptive reasons that are too long for me to express and define here (I spent 5 Years of university to learn about them) I don't mean by no means to offend anybody here, it's Just mere technical speech. Please seriously consider adding that option too (that has already been coded). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 434919] Baloo does not exclude folders correctly if $HOME has a trailing slash
https://bugs.kde.org/show_bug.cgi?id=434919 --- Comment #3 from Oded Arbel --- (In reply to Nate Graham from comment #2) > Interesting. I'll investigate. This change solved the problem for me: https://invent.kde.org/frameworks/baloo/-/merge_requests/43 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419264] right click doesn't work on the right side of the timeline
https://bugs.kde.org/show_bug.cgi?id=419264 CzAndrew changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from CzAndrew --- I just tested with 20.12.3, on Win10, and the problem has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406159] make the project monitor's toolbar editable
https://bugs.kde.org/show_bug.cgi?id=406159 Julius Künzel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||jk.kde...@smartlab.uber.spa ||ce Ever confirmed|0 |1 --- Comment #1 from Julius Künzel --- Thanks for your report! I think this would be a good improvement. This would also solve the first point of this report: https://bugs.kde.org/show_bug.cgi?id=426984 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408345] Extract audio does not work if there is space in the path
https://bugs.kde.org/show_bug.cgi?id=408345 --- Comment #3 from CzAndrew --- I confirm that the bug has been fixed. Tested on v20.12.3; Win10. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426984] Feature Requests - Buttons, Layouts, Text
https://bugs.kde.org/show_bug.cgi?id=426984 Julius Künzel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||jk.kde...@smartlab.uber.spa ||ce Ever confirmed|0 |1 --- Comment #1 from Julius Künzel --- Thanks for your report! 1. a valid feature request, nothing to add 2. on a fresh install (or if you delete [instruction for linux] ~./config/kdenliverc, ~/.config/kdenlive-layoutsrc and ~/.config/kdenlive-appimagerc) "editing" is the default. If you just updated there are might some leftovers of an old installation. 3. can you explain this point a bit more (maybe with a screenshot)? I don't really understand what you want… (e.g. which text? the UI text, title clip text,…) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418615] Allow multiple views of the project content
https://bugs.kde.org/show_bug.cgi?id=418615 --- Comment #2 from Julius Künzel --- Similar report https://bugs.kde.org/show_bug.cgi?id=415551 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415551] tab bar for folders in project bin
https://bugs.kde.org/show_bug.cgi?id=415551 Julius Künzel changed: What|Removed |Added Ever confirmed|0 |1 CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|CONFIRMED --- Comment #2 from Julius Künzel --- Similar to https://bugs.kde.org/show_bug.cgi?id=418615 -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 420302] Application crashes when closing intentionally
https://bugs.kde.org/show_bug.cgi?id=420302 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ |ation/parley/commit/3a8c04e |ation/parley/commit/e06375d |903f2f8ac66024a2c171641a1d6 |b7b71d4b0216e02bea9595da0cd |f6d7fa |5fc9b8 --- Comment #9 from Albert Astals Cid --- Git commit e06375db7b71d4b0216e02bea9595da0cd5fc9b8 by Albert Astals Cid, on behalf of Hartmut Riesenbeck. Committed on 25/03/2021 at 22:32. Pushed by aacid into branch 'release/21.04'. Fix segfault on quit Reproducible segmentation fault when start practice a collection and quit immediately from statistics main window without changing anything. The segfault is only shown on console output. DrKonqi window doesn't open. The segfault appears when ParleyDocument member is deleted in ParleyMainWindows destructor. The destroyed signal of ParleyDocuments KEduVocDocument member calls a slot to update the window cation which want to access an already deleted KEduVocDocument pointer. To fix this, the destroyed signal connection is removed before deleting the ParleyDocument member in ParleyMainWindows destructor. (cherry picked from commit 3a8c04e903f2f8ac66024a2c171641a1d6f6d7fa) M +6-0src/parleymainwindow.cpp https://invent.kde.org/education/parley/commit/e06375db7b71d4b0216e02bea9595da0cd5fc9b8 -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 420302] Application crashes when closing intentionally
https://bugs.kde.org/show_bug.cgi?id=420302 Hartmut Riesenbeck changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ |ation/parley/commit/ad449a1 |ation/parley/commit/3a8c04e |e78de2f320afa4e02a9598e0778 |903f2f8ac66024a2c171641a1d6 |50cf42 |f6d7fa --- Comment #8 from Hartmut Riesenbeck --- Git commit 3a8c04e903f2f8ac66024a2c171641a1d6f6d7fa by Hartmut Riesenbeck. Committed on 25/03/2021 at 19:41. Pushed by aacid into branch 'master'. Fix segfault on quit Reproducible segmentation fault when start practice a collection and quit immediately from statistics main window without changing anything. The segfault is only shown on console output. DrKonqi window doesn't open. The segfault appears when ParleyDocument member is deleted in ParleyMainWindows destructor. The destroyed signal of ParleyDocuments KEduVocDocument member calls a slot to update the window cation which want to access an already deleted KEduVocDocument pointer. To fix this, the destroyed signal connection is removed before deleting the ParleyDocument member in ParleyMainWindows destructor. M +6-0src/parleymainwindow.cpp https://invent.kde.org/education/parley/commit/3a8c04e903f2f8ac66024a2c171641a1d6f6d7fa -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418615] Allow multiple views of the project content
https://bugs.kde.org/show_bug.cgi?id=418615 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #1 from Julius Künzel --- Thanks for your feature request! This is related: https://invent.kde.org/multimedia/kdenlive/-/merge_requests/189 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] Cannot type accented characters (í, ã, etc) in any text fields in QML KCMs embedded in QWidgets view (works in the sidebar's text field)
https://bugs.kde.org/show_bug.cgi?id=414501 --- Comment #8 from Petros --- This has been fixed for me. Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.25-1-lts OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 6.8 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424146] Sound channel mixer does not afect in render
https://bugs.kde.org/show_bug.cgi?id=424146 Julius Künzel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|NEEDSINFO --- Comment #2 from Julius Künzel --- Can you please update to the latest version (20.12.3 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening? If persists please try also to disable "parallel processing" in the render setting and try again (as asked by @emohr) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418704] Monitors zoom to 100% if Waveform or such activated
https://bugs.kde.org/show_bug.cgi?id=418704 Julius Künzel changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||jk.kde...@smartlab.uber.spa ||ce -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433889] Title Clip Editor Background slider in an incorrect position
https://bugs.kde.org/show_bug.cgi?id=433889 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Assignee|j...@kdenlive.org |jk.kde...@smartlab.uber.spa ||ce --- Comment #1 from Julius Künzel --- Thanks for your report! I can confirm this. Working on a fix… -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all
https://bugs.kde.org/show_bug.cgi?id=434949 --- Comment #2 from 80p3fy7...@cloud-mail.top --- (In reply to Nate Graham from comment #1) > This one is actually a duplicate of none of those, but rather Bug 414501. > > *** This bug has been marked as a duplicate of bug 414501 *** Huh? I cannot reproduce bug 414501. Accented characters (é è ç à) work just fine here in Workspace Behavior > Desktop Effects search bar. All the links I mentioned describe the exact same issue that I reported, namely AZERTY keyboard/keymap users who cannot assign a shortcut with accented keys. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 434919] Baloo does not exclude folders correctly if $HOME has a trailing slash
https://bugs.kde.org/show_bug.cgi?id=434919 --- Comment #2 from Nate Graham --- Interesting. I'll investigate. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434370] Switch user fails
https://bugs.kde.org/show_bug.cgi?id=434370 --- Comment #9 from Nate Graham --- It sounds like there is a bug in SDDM then, if it defaults to false instead of true. Can you please file a bug on SDDM about this? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 andrey...@ya.ru changed: What|Removed |Added Version|17.04.0 |20.12.2 Platform|Fedora RPMs |Manjaro --- Comment #9 from andrey...@ya.ru --- This is not a bug in the preview. It is bad when i want to save ARW to JPEG. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416276] Feature "Insert clip zone" doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=416276 Julius Künzel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jk.kde...@smartlab.uber.spa ||ce Resolution|--- |FIXED --- Comment #3 from Julius Künzel --- Thanks for your report! It seems we can close this as you found the solution and the doc is updated. Btw version 19.08.2 is very old (current is 20.12.3, 21.04 is coming in april). I highly recommend you to update. There have been many fixes and new features! https://kdenlive.org/en/download/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434954] New: Support firewalld zones
https://bugs.kde.org/show_bug.cgi?id=434954 Bug ID: 434954 Summary: Support firewalld zones Product: systemsettings Version: unspecified Platform: unspecified URL: https://invent.kde.org/plasma/plasma-firewall/-/issues /16 OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_firewall Assignee: plasma-b...@kde.org Reporter: kevin.kof...@chello.at CC: tcanabr...@kde.org Target Milestone: --- Firewalld has a central concept called "zones". Those are the main setting to make in the firewalld. They correspond to a whole profile of rules. All rules are part of one or more zones. Switching the zone switches the entire rule set. (Those zones are implemented deep in the backend, not in the UI, i.e., the UI should use the backend's zones and not attempt to come up with its own.) Think of it as the equivalent of sysv runlevels or systemd targets, but for a firewall. Unfortunately, this concept does not seem to be implemented in Plasma Firewall yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434953] Rule creation interface is hard to use
https://bugs.kde.org/show_bug.cgi?id=434953 Kevin Kofler changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434952] Support firewalld services / UFW application profiles
https://bugs.kde.org/show_bug.cgi?id=434952 Kevin Kofler changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434953] New: Rule creation interface is hard to use
https://bugs.kde.org/show_bug.cgi?id=434953 Bug ID: 434953 Summary: Rule creation interface is hard to use Product: systemsettings Version: unspecified Platform: unspecified URL: https://invent.kde.org/plasma/plasma-firewall/-/issues /15 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_firewall Assignee: plasma-b...@kde.org Reporter: kevin.kof...@chello.at CC: tcanabr...@kde.org Target Milestone: --- Looking at the code here and the screenshot under https://www.omgubuntu.co.uk/2021/01/kde-plasma-5-21-features , it looks like the rule creation interface was taken almost unmodified from the predecessor nx-firewall (formerly nomad-firewall). Unfortunately, this interface is unnecessarily hard to use. UFW-KDE, the old KDE 4 KCM from upstream UFW, had a "simple" mode (which was the default) and an "advanced" mode (easily enabled through a dropdown at the top). In the "simple" mode, only the destination port (for an incoming rule) was shown (with the possibility to pick an application profile instead of a port number, see also #14 (closed)), all the other settings (source address, source port, destination address) were hidden and set to "any". In the "advanced" mode, everything was shown. Plasma Firewall currently only has the equivalent of the "advanced" mode. The rationale there is (and I tend to agree with whomever came up with that design) that an inexperienced user will not know that the destination port is the only setting that really matters in nearly all cases and what to do with the other settings. The "simple" mode allows such users to just open up a port (or ideally an application profile, see #14 (closed)) without knowing the technical details. And if you need to set everything, you can quickly switch to "advanced" mode. I think Plasma Firewall would greatly benefit from having such a "simple" mode, or something equivalent (could also be, e.g., a separate "Add simple rule" or "Quickly add rule" button), available as well. Of course, if you are editing a rule that uses advanced settings, it should automatically come up in "advanced" mode so that the non-default settings are clearly visible. Somewhat related to this, the defaults when creating a new rule should probably be Incoming and Allow, at least if the firewall is set to default deny. See also: https://github.com/nx-desktop/nx-firewall/issues/16 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434930] Unexpected Crash in Connection manager
https://bugs.kde.org/show_bug.cgi?id=434930 Nate Graham changed: What|Removed |Added Component|general |kcm_networkmanagement Assignee|plasma-b...@kde.org |jgrul...@redhat.com CC||n...@kde.org, ||plasma-b...@kde.org --- Comment #1 from Nate Graham --- Mostly not in KDE code. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 andrey...@ya.ru changed: What|Removed |Added CC||andrey...@ya.ru -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434849] The vdso is not available when running on ppc64*
https://bugs.kde.org/show_bug.cgi?id=434849
pedro...@linux.ibm.com changed:
What|Removed |Added
CC||pedro...@linux.ibm.com
--- Comment #3 from pedro...@linux.ibm.com ---
(In reply to Mark Wielaard from comment #2)
> This is done deliberately, see coregrind/m_initimg/initimg-linux.c
> (setup_client_stack):
>
> case AT_SYSINFO_EHDR: {
> /* Trash this, because we don't reproduce it */
> const NSegment* ehdrseg =
> VG_(am_find_nsegment)((Addr)auxv->u.a_ptr);
> vg_assert(ehdrseg);
> VG_(am_munmap_valgrind)(ehdrseg->start, ehdrseg->end -
> ehdrseg->start);
> auxv->a_type = AT_IGNORE;
> break;
> }
>
It seems that this case statement is #ifdefed out for ppc, and some other
arches, correct? So shouldn't AT_SYSINFO_EHDR, and the vDSO, be available for
these arches?
> Is there a reason you need AT_SYSINFO_EHDR?
It's used in glibc for ppc for the backtrace function that prints out return
addresses for all frames in a stack. The symbol from the vDSO for the signal
trampoline is used to handle the backtrace when there's a signal, which doesn't
work when it's run under Valgrind, due to the missing vDSO.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 434927] When audio plays, the volume slider button goes under the volume bar
https://bugs.kde.org/show_bug.cgi?id=434927 Nate Graham changed: What|Removed |Added Priority|NOR |HI CC||k...@david-redondo.de, ||k...@davidedmundson.co.uk, ||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression --- Comment #1 from Nate Graham --- I can intermittently confirm, but not always. Right now it's working, but it will break again at some point. This issue was introduced by the input/output level monitoring feature in Plasma 5.21. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434952] New: Support firewalld services / UFW application profiles
https://bugs.kde.org/show_bug.cgi?id=434952 Bug ID: 434952 Summary: Support firewalld services / UFW application profiles Product: systemsettings Version: unspecified Platform: unspecified URL: https://invent.kde.org/plasma/plasma-firewall/-/issues /14 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_firewall Assignee: plasma-b...@kde.org Reporter: kevin.kof...@chello.at CC: tcanabr...@kde.org Target Milestone: --- Looking at the code here and the screenshot under https://www.omgubuntu.co.uk/2021/01/kde-plasma-5-21-features , it looks like, just like its predecessor nx-firewall (formerly nomad-firewall), plasma-firewall has no UI to pick one of the predefined application profiles (firewalld calls them "services") known to firewalld or UFW, and open the ports for it. Instead, you have to know the port number(s) to create a rule. This makes the KCM impractical to use. Please support the predefined application profiles of the underlying firewall backend, which make it very easy to open up the ports for a given application. See also: https://github.com/nx-desktop/nx-firewall/issues/15 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434922] cpu load plasmoid remain blank and cannot find sensors
https://bugs.kde.org/show_bug.cgi?id=434922 Nate Graham changed: What|Removed |Added Assignee|ksysguard-b...@kde.org |plasma-b...@kde.org Product|plasma-systemmonitor|plasmashell Target Milestone|--- |1.0 Component|general |System Monitor CC||n...@kde.org, ||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421363] Transform to tiny size causes Krita to crash to desktop
https://bugs.kde.org/show_bug.cgi?id=421363 --- Comment #6 from Sharaf --- small correction to my previous statement. Less than 1.0 / (1 << 8). My brain somehow thought that the inverse of 1 << 8 is 1 >> 8 :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434951] New: Weather widget icon too large on panels over 38 pixels in height
https://bugs.kde.org/show_bug.cgi?id=434951 Bug ID: 434951 Summary: Weather widget icon too large on panels over 38 pixels in height Product: plasmashell Version: 5.21.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: nortex...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 137066 --> https://bugs.kde.org/attachment.cgi?id=137066=edit Weather widget icon too large with panel height of 46 When the tray "panel icon size" is set to small and the panel height is 38 or above, the weather widget icon becomes larger than the others and starts to touch the adjacent icons. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421223] Issues with adding guides and rendering to the end
https://bugs.kde.org/show_bug.cgi?id=421223 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #4 from Julius Künzel --- (In reply to martian from comment #2) > I just tried to solve this bug by myself. > > changing line 481(near about) of src/dialogs/renderwidget.cpp to: > double projectDuration = GenTime(pCore->projectDuration() - 2, > pCore->getCurrentFps()).ms() / 1000; > > seems to solve the issue... > > I am still in doubt that how it solves the issue(and what caused the issue), > I would highly appreciate someone who can help me understand how this fix > works. Thanks for the report and your attempt to fix! It would be nice if you can open a merge request on https://invent.kde.org/multimedia/kdenlive. On GitLab we can review coding contributions better… -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421363] Transform to tiny size causes Krita to crash to desktop
https://bugs.kde.org/show_bug.cgi?id=421363 Sharaf changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/47fa74d03 ||20547fd4a46be1069466f10f7e1 ||5b8b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Sharaf --- Git commit 47fa74d0320547fd4a46be1069466f10f7e15b8b by Sharaf Zaman. Committed on 25/03/2021 at 21:27. Pushed by szaman into branch 'master'. Bugfix: Transform tool crash when scaled to a few pixels M +1-1libs/image/kis_filter_weights_buffer.h https://invent.kde.org/graphics/krita/commit/47fa74d0320547fd4a46be1069466f10f7e15b8b -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434370] Switch user fails
https://bugs.kde.org/show_bug.cgi?id=434370 --- Comment #8 from medin --- (In reply to Nate Graham from comment #7) > (In reply to Bharadwaj Raju from comment #3) > > However maybe SDDM behaviour should be changed so if a user attempts to > > login to existing session it should redirect them to that TTY. > This is a configurable behavior in SDDM. It's controlled by the value of > ReuseSession=true in /etc/sddm.conf (or /etc/sddm.conf.d/kde_settings.conf, > if you have that) and it now defaults to true in SDDM itself unless > overridden by the user or the distro: > https://github.com/sddm/sddm/blob/develop/src/common/Configuration.h#L94 > > So there are two options here: > 1. You or your distro have set ReuseSession=false in the config file > 2. Your distro is shipping an old version of SDDM that does not have this > change of the default settings yet > 3. There is a bug in SDDM preventing session re-using from working properly > > Either way, this isn't a KDE bug. Please figure out which of those things is > the problem, and then follow up with the appropriate party. :) Thanks! I have SDDM 0.19.0-3, and the option ReuseSession is truly set by default to false, I never touched this file. After changing its value to true, the problem is solved, Thanks for your help :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385046] Bug at starting du to a bad position of melt.exe
https://bugs.kde.org/show_bug.cgi?id=385046 Julius Künzel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #5 from Julius Künzel --- Can you please test again with 20.12.3? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434920] File properties dialog should have the Location field clickable to open the parent folder in a browser
https://bugs.kde.org/show_bug.cgi?id=434920 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Keywords||usability Product|plasmashell |frameworks-kio Assignee|k...@davidedmundson.co.uk|kio-bugs-n...@kde.org Target Milestone|1.0 |--- CC||kdelibs-b...@kde.org, ||n...@kde.org Status|REPORTED|CONFIRMED Component|general |Properties dialog Version|master |unspecified --- Comment #1 from Nate Graham --- Seems quite reasonable to me. It could be a clickable link, yeah. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434913] Sometimes part of the dropdown of Krunner is semi-transparent on Wayland
https://bugs.kde.org/show_bug.cgi?id=434913 Nate Graham changed: What|Removed |Added Version|unspecified |git master Component|general |wayland-generic Product|krunner |kwin Assignee|alexander.loh...@gmx.de |kwin-bugs-n...@kde.org Summary|Sometimes dropdown of |Sometimes part of the |Krunner is semi-transparent |dropdown of Krunner is |on Wayland |semi-transparent on Wayland CC||n...@kde.org --- Comment #1 from Nate Graham --- This is probably going to end up being an issue in either KWin, or Plasma more generally. Starting with KWin. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434912] File selector remembers last thumbnail previewed in last selected path
https://bugs.kde.org/show_bug.cgi?id=434912 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=247268 --- Comment #2 from Nate Graham --- Reminds me of Bug 247268. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 247268] Preview in file dialog doesn't return to showing the selected file when mouse passes over another file and leaves list viewport without passing over the background
https://bugs.kde.org/show_bug.cgi?id=247268 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434912 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434933] Balance calculation discrepancy in Future payments
https://bugs.kde.org/show_bug.cgi?id=434933 John Hudson changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #6 from John Hudson --- Thanks for the suggestion. It looks as if it is device specific - perhaps corruption of a library on my desktop. I back the file up weekly and so I updated my latest backup on my backup laptop step by step and the problem did not appear. However, when I copied the file to my desktop, even after reinstalling KMyMoney, the problem persisted. Finally, I copied the file to a notebook running the same release as the desktop and the problem did not appear. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434912] File selector remembers last thumbnail previewed in last selected path
https://bugs.kde.org/show_bug.cgi?id=434912 Nate Graham changed: What|Removed |Added Product|plasmashell |frameworks-kio Target Milestone|1.0 |--- Assignee|k...@davidedmundson.co.uk|kio-bugs-n...@kde.org Ever confirmed|0 |1 Severity|normal |minor Status|REPORTED|CONFIRMED CC||kdelibs-b...@kde.org, ||n...@kde.org Component|general |Open/save dialogs Version|5.21.3 |5.80.0 --- Comment #1 from Nate Graham --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434910] General sidebar button in Klipper settings can't accept left click in its upper area
https://bugs.kde.org/show_bug.cgi?id=434910 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Component|plasma-widget |general Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can confirm. How weird. Does not seem to happen for other QWidgets-based settings dialogs using this style. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434907] Not remember the previous searched text
https://bugs.kde.org/show_bug.cgi?id=434907 Nate Graham changed: What|Removed |Added Keywords||usability CC||n...@kde.org --- Comment #1 from Nate Graham --- So you want the search text to be cleared automatically when closing the popup? Either always or optionally? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] Cannot type accented characters (í, ã, etc) in any text fields in QML KCMs embedded in QWidgets view (works in the sidebar's text field)
https://bugs.kde.org/show_bug.cgi?id=414501 Nate Graham changed: What|Removed |Added CC||80p3fy7...@cloud-mail.top --- Comment #7 from Nate Graham --- *** Bug 434949 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434949] Custom shortcuts containing accented keys ("é" "è" "ç" "à") aren't working at all
https://bugs.kde.org/show_bug.cgi?id=434949 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@david-redondo.de, ||n...@kde.org Assignee|k...@michael-jansen.biz |plasma-b...@kde.org Component|kcm_khotkeys|kcm_keys Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- This one is actually a duplicate of none of those, but rather Bug 414501. *** This bug has been marked as a duplicate of bug 414501 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 434948] "Tasks" progress resets for each separate task
https://bugs.kde.org/show_bug.cgi?id=434948 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Yup, can confirm. This jumpiness kind of drives me crazy. :) -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 434947] RTL resizing problem
https://bugs.kde.org/show_bug.cgi?id=434947 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
