[krunner] [Bug 492205] KRunner deprioritizing "most clicked" result
https://bugs.kde.org/show_bug.cgi?id=492205 --- Comment #1 from Reuben --- Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-41-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 492205] KRunner deprioritizing "most clicked" result
https://bugs.kde.org/show_bug.cgi?id=492205 Reuben changed: What|Removed |Added Summary|KRunner depriotizing "most |KRunner deprioritizing |clicked" result |"most clicked" result -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 492205] New: KRunner depriotizing "most clicked" result
https://bugs.kde.org/show_bug.cgi?id=492205 Bug ID: 492205 Summary: KRunner depriotizing "most clicked" result Classification: Plasma Product: krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 172966 --> https://bugs.kde.org/attachment.cgi?id=172966&action=edit chrome appearing in wrong place SUMMARY When I search "chr" in krunner, 100% of the time I click on the Google Chrome application. However, this is 11 items down in my krunner results for this search, meaning that clicking with the mouse is quicker than selecting with the keyboard. I should be able to type "chr " and open the item that I opened by choice previously from this search. That means that not only items but also sections should be sorted by recency. Maybe this is an option. If you don't want to do this, then at least krunner plugins should be sortable by the user. In my case, 99.9% of the time I am opening an application. I like that I can search other stuff, and don't really want to turn all of the other plugins off - but I would certainly set applications to show first. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490810] New: Discover spams notification system for system restarts
https://bugs.kde.org/show_bug.cgi?id=490810 Bug ID: 490810 Summary: Discover spams notification system for system restarts Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- Created attachment 171978 --> https://bugs.kde.org/attachment.cgi?id=171978&action=edit Notification spam SUMMARY When a package requires a system restart, it spams the notification system. STEPS TO REPRODUCE 1. Apply system updated that require system restart OBSERVED RESULT See attached EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-38-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488168] New: Wayland - flameshot scaling of screenshot is wrong
https://bugs.kde.org/show_bug.cgi?id=488168 Bug ID: 488168 Summary: Wayland - flameshot scaling of screenshot is wrong 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: k...@flavor8.com Target Milestone: --- SUMMARY I realize flameshot is not a KDE app (the overlay is significantly better UX than the default, and it would be nice to officially adopt it!) - but the developer states that this bug is caused by the underlying wayland compositor. STEPS TO REPRODUCE 1. Use plasma wayland 2. Use fractional scaling 3. Set up flameshot 4. Take screenshot OBSERVED RESULT Flameshot does not receive scaled image. See https://github.com/flameshot-org/flameshot/issues/3614 EXPECTED RESULT It should work identically to Xse SOFTWARE/OS VERSIONS Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488157] Error message appears when Elisa is opened, then the app crashes after a while
https://bugs.kde.org/show_bug.cgi?id=488157 --- Comment #3 from Reuben Parfrey --- Created attachment 170224 --> https://bugs.kde.org/attachment.cgi?id=170224&action=edit Elisa working when opened through Terminal -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488157] Error message appears when Elisa is opened, then the app crashes after a while
https://bugs.kde.org/show_bug.cgi?id=488157 --- Comment #2 from Reuben Parfrey --- Created attachment 170223 --> https://bugs.kde.org/attachment.cgi?id=170223&action=edit The error message that appears -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488157] Error message appears when Elisa is opened, then the app crashes after a while
https://bugs.kde.org/show_bug.cgi?id=488157 --- Comment #1 from Reuben Parfrey --- Created attachment 170222 --> https://bugs.kde.org/attachment.cgi?id=170222&action=edit Screen recording of the issue -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 488157] New: Error message appears when Elisa is opened, then the app crashes after a while
https://bugs.kde.org/show_bug.cgi?id=488157 Bug ID: 488157 Summary: Error message appears when Elisa is opened, then the app crashes after a while Classification: Applications Product: Elisa Version: 24.05.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: reubenparf...@gmail.com Target Milestone: --- SUMMARY Elisa opens as normal, but an error appears which reads "Launching Elisa (Failed) - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. " This error appears after approximately 30 seconds of the app being open. After this the program appears to work as normal, however it seems to randomly crash a few minutes after this error appears. This crash happens regardless of whether there is music playing or not. Interestingly, when launching Elisa through the terminal, some output appears but the error message does not. Also, the crash after a few minutes no longer happens. I have attached a screen recording of the error message appearing 30 seconds after Elisa is launched, along with screenshots of the error message, and Elisa launched through the Terminal working as normal. STEPS TO REPRODUCE 1. Open Elisa via Kickoff, Task Manager, KRunner, etc... 2. Wait around 30 seconds, an error appears which states: "Launching Elisa (Failed) - Did not receive a reply..." 3. Leave Elisa open. Observe that the program eventually crashes a few minutes after this error message appears. OBSERVED RESULT An error message appears soon after the program is launched, but Elisa appears to still work as normal. After a few minutes, Elisa crashes seemingly out of nowhere. This crash happens whether there is music playing or not. If Elisa is launched through the Terminal, this does not happen. EXPECTED RESULT Elisa opens normally through KRunner, Kickoff, etc... , and the error message does not appear. The program does not crash after a few minutes. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240605 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 System Version: ThinkPad T480 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #11 from Reuben --- I run into this multiple times a day and it really impacts productivity. How can I clear the file picker settings? Or the mime settings? Or whatever it uses. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485786] Moving a directory/file with the cursor crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=485786 Reuben Parfrey changed: What|Removed |Added CC||reubenparf...@gmail.com --- Comment #3 from Reuben Parfrey --- Just wanted to add on to this and say that I'm having this issue too. Here's my system info: Operating System: openSUSE Tumbleweed 20240419 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO System Version: ThinkPad T480 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482973] Sudo dialog should not permit background typing
https://bugs.kde.org/show_bug.cgi?id=482973 --- Comment #1 from Reuben --- I figured out how this happens. The "update all" button is in the top right of the window. With focus follows mouse, you are used to ...focus being under the mouse... so by default you move the cursor to the dialog. If you are slightly sloppy about this, discover grabs focus and your password goes into the wrong place. It's no the kind of thing that happens if you are being slow and deliberate, but if the whole thing (move mouse, type password) is done on autopilot very quickly, it can happen (and as above, has done for me half a dozen times or so in the past couple years.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482973] New: Sudo dialog should not permit background typing
https://bugs.kde.org/show_bug.cgi?id=482973 Bug ID: 482973 Summary: Sudo dialog should not permit background typing 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: k...@flavor8.com Target Milestone: --- Created attachment 166790 --> https://bugs.kde.org/attachment.cgi?id=166790&action=edit demonstration With focus follows mouse, it's quite possible to inadvertently type your password somewhere that you didn't intend. This is particularly odious with apps that (might) keep history, e.g. Discover. See attached video for demonstration. I've done this probably half a dozen times with Discover in the past two years, so this is not theoretical. Users who don't realize that some applications write history to disk in plain text may not change their password when this happens. The sudo dialog should somehow protect against this. One possibility would be to own the glass of the screen and prevent background typing (though, maybe some users copy/paste passwords from password managers? - but this could be accomodated for with a button to dismiss the sneezeguard, since it's an exception to the general usage pattern). Another possibility would be to detect loss of focus and react very prominently, e.g. by highlighting the sudo dialog. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 481326] KWard does not install properly
https://bugs.kde.org/show_bug.cgi?id=481326 Reuben changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Reuben --- Thank you so much, It worked perfectly. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 481326] New: KWard does not install properly
https://bugs.kde.org/show_bug.cgi?id=481326 Bug ID: 481326 Summary: KWard does not install properly Classification: Applications Product: rkward Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: R Console Assignee: rkward-de...@kde.org Reporter: jrm1...@gmail.com Target Milestone: --- SUMMARY *** I am trying to install rKWARd on a Mac. MacOs 14.2.1 I followed all instruction on the install webpage and installed R 4.3.2, then KWard 0.7.5 Everytime I start Kward I get the following message The backend process failed to start with exit code 6, message: 'dyld[2067]: Library not loaded: @rpath/libR.dylib Referenced from: <486CAC2A-C75D-3CFF-9A10-B9AF33F2175C> /Applications/rkward.app/Contents/MacOS/rkward.rbackend Reason: tried: '/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/R/R.framework/Resources/lib/libR.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/R/R.framework/Resources/lib/libR.dylib' (no such file), './libR.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/R/R.framework/Resources/lib/libR.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/R/R.framework/Resources/lib/libR.dylib' (no such file), './libR.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/usr/lib/libR.dylib' (no such file, not in dyld cache) '. The R backend will be shut down immediately. This means, you can not use any more functions that rely on it. I.e. you can do hardly anything at all, not even save the workspace (but if you're lucky, R already did that). What you can do, however, is save any open command-files, the output, or copy data out of open data editors. Quit RKWard after that. Sorry! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 14.2.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: Kward 0.7.5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477411] New: Youtube video in chrome started playing when laptop awakened on lock screen
https://bugs.kde.org/show_bug.cgi?id=477411 Bug ID: 477411 Summary: Youtube video in chrome started playing when laptop awakened on lock screen 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: k...@flavor8.com Target Milestone: --- SUMMARY Unclear how this happened, but I will try to repro. Locked (and closed the screen of) the laptop overnight, with chrome as the focused application and a paused youtube video in the active tab. Opened the laptop lid in the morning. While still on lock screen, before I'd attempted to enter password or interacted with the screen at all, the youtube video started playing. Further, as a side bug, the volume keys did not work until I had logged in. This is a clear privacy issue. I can see the value of "audio _continues_ playing while screen is locked" (e.g. laptop is running the audio for a party) but a session which has been inactive for 8 or 9 hours has no business being able to send audio before being unlocked. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-13-generic (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: XPS 9320 SOFTWARE/OS VERSIONS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #9 from Reuben --- Hm, are there logs I can look at? Perhaps a way to turn on debug mode in Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #7 from Reuben --- To clarify - it happens regularly with different files, but only specific files cause the issue (which then breaks preview for all files). Example file attached in https://bugs.kde.org/show_bug.cgi?id=476463#c1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476876] New: Close button in "present windows" should be in the same location as window decorations
https://bugs.kde.org/show_bug.cgi?id=476876 Bug ID: 476876 Summary: Close button in "present windows" should be in the same location as window decorations 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: k...@flavor8.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Using window decoration settings, move the close button to the top left of windows & apply 2. Now bring up "present windows", e.g. by pushing into top left of screen OBSERVED RESULT Close button in "present windows" representation of windows is always on the right. EXPECTED RESULT It should obey location as configured by user/theme. (There is an edge case where the user has gotten rid of their close button, in which case arbitrary choice is fine.) SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476460] Multiple Breeze themes shown in SDDM theme chooser
https://bugs.kde.org/show_bug.cgi?id=476460 --- Comment #2 from Reuben --- Found it under: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1872833 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476444] SDDM theme chooser glitches when installing two themes at once
https://bugs.kde.org/show_bug.cgi?id=476444 --- Comment #3 from Reuben --- No - the second one doesn't appear in the list after clicking away and back. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476457] When SDDM theme crashes, user is left with useless login screen
https://bugs.kde.org/show_bug.cgi?id=476457 --- Comment #3 from Reuben --- Filed in SDDM. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #5 from Reuben --- This flie specifically triggers the bug, and then breaks the preview for all pngs browsed too subsequently (which previously were working fine). It does not break preview of other files (pdfs, jpgs). This has happened to me for months, and I only realized that there was this triggering element to the bug while filing the ticket. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #3 from Reuben --- Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #2 from Reuben --- Created attachment 162820 --> https://bugs.kde.org/attachment.cgi?id=162820&action=edit regular browsing prior to the bug being triggered -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476463] File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 --- Comment #1 from Reuben --- Created attachment 162819 --> https://bugs.kde.org/attachment.cgi?id=162819&action=edit here is a file which when browsed over causes it -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476463] New: File chooser shows wrong preview action for PNGs
https://bugs.kde.org/show_bug.cgi?id=476463 Bug ID: 476463 Summary: File chooser shows wrong preview action for PNGs 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: k...@flavor8.com Target Milestone: --- Created attachment 162818 --> https://bugs.kde.org/attachment.cgi?id=162818&action=edit example of bug SUMMARY This appears to be a regression of #169716. STEPS TO REPRODUCE 1. From chrome, file > open 2. Browse PNGs, until one of them triggers the preview to switch to an empty media player OBSERVED RESULT Now all PNGs show an empty media player, even though some where originally working. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476461] New: Default SDDM theme chooser sort should be "best" / rethink sort
https://bugs.kde.org/show_bug.cgi?id=476461 Bug ID: 476461 Summary: Default SDDM theme chooser sort should be "best" / rethink sort 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: k...@flavor8.com Target Milestone: --- SUMMARY The SDDM theme chooser offers as potential sort options: Recent (default), Alphabetical, Highest Rated, Most Downloads. Average users are unlikely to want any of these. "Best" (or "Hot") should be the default, which is some weighted combination of "most downloads", "highest rated", and ideally "certified to work" (see sibling tickets). Potentially remove the "sort" option altogether. The issues with the others (again, for average, non sddm theme enthusiast users): * Recent - who cares? Any garbage could be uploaded most recently. * Alphabetical - who cares? A user who has one in mind will search. Occasionally they may come to a new install with a vague memory that there's several C64 themes to choose between and want to browse by name, but search (VERY slowly) actually works well in this scenario. * Highest Rating - I am going to guess there is no protection against uploading a new theme and rating it 5*. IS it more sophisticated than that? If so, it should actually be named something else. If not, it should be dropped, since it can be gamed. * Most Downloads - this one is somewhat useful, though it really should be sliding window based. Nobody cares what SDDM themes were downloaded in 2014. I'd suggest a 12 month window. If the theme choosing feature is kept at all (see sibling bugs/feature reqs) then you _could_ make a "New / Experimental" tab to allow new and unvetted themes to be featured. If a user installs from there, ideally you track them successfully logging in to boost the theme's "certified to work", and _maybe_ proactively ask them a couple of questions on their first login. That way the social proof features are actually useful. (How many people are actually going back to settings to rate their login theme after switching, after the next reboot? Vanishingly few.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476460] New: Multiple Breeze themes shown in SDDM theme chooser
https://bugs.kde.org/show_bug.cgi?id=476460 Bug ID: 476460 Summary: Multiple Breeze themes shown in SDDM theme chooser 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: k...@flavor8.com Target Milestone: --- Created attachment 162817 --> https://bugs.kde.org/attachment.cgi?id=162817&action=edit breezy SUMMARY See screenshot. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476459] New: Feature request: SDDM - allow setting wallpaper without changing theme
https://bugs.kde.org/show_bug.cgi?id=476459 Bug ID: 476459 Summary: Feature request: SDDM - allow setting wallpaper without changing theme 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: k...@flavor8.com Target Milestone: --- SUMMARY 98.95% of the time that users find their way to the SDDM theme chooser, they're actually looking to change the wallpaper on the login screen and don't actually care about switching theme. (Science proves it!) Android is an instructive example here; if you change the wallpaper, you get the option to set it for desktop + login, or just desktop. Plasma should work the same way. The user should not even have to know that SDDM is a thing; it's just the login screen. Additionally, wallpaper changes made via the UI should apply instantly to SDDM, so that the user can toggle to the lock screen and back. IMO (see sibling tickets) the entire SDDM theme chooser could be bumped from the settings panel, and this feature offered instead. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476458] New: SDDM themes need curation
https://bugs.kde.org/show_bug.cgi?id=476458 Bug ID: 476458 Summary: SDDM themes need curation 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: k...@flavor8.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to the SDDM theme chooser in settings 2. Browse themes OBSERVED RESULT There are many very amateur themes in the chooser. While there is the banner warning about it being user generated content, so many of these are so terrible that I don't believe plasma should be offering them via the default UI. Wallpaper is one thing, but the login screen needs to be robust and to be competent - a user who stumbles there way into changing the sddm theme and then forgets what they did (it doesn't, after all, reflect immediately) is then "stuck" with an amateur screen. (Furthermore some of these actually crash sddm, per my sibling bug). I'd suggest rethinking whether to even offer the feature (separate ticket), but at minimum there needs to be some kind of qa or gatekeeping to what gets admitted to the chooser. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476457] When SDDM theme crashes, user is left with useless login screen
https://bugs.kde.org/show_bug.cgi?id=476457 --- Comment #1 from Reuben --- Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476457] New: When SDDM theme crashes, user is left with useless login screen
https://bugs.kde.org/show_bug.cgi?id=476457 Bug ID: 476457 Summary: When SDDM theme crashes, user is left with useless login screen 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: k...@flavor8.com Target Milestone: --- Created attachment 162816 --> https://bugs.kde.org/attachment.cgi?id=162816&action=edit "whoops i broke the computer" SUMMARY I believe this is quite severe - unless a user knows how to toggle to a different virtual console (ctrl alt f1, f2, ...) then they may believe they "broke their computer". SDDM really needs a default/stable login screen that it can fall back to. STEPS TO REPRODUCE 1. Using plasma settings, set sddm login screen to C64-Classic-Fancy (I am not picking on this particular theme, though I will file a separate lower prio issue about themes in the selector) 2. Reboot (or restart X) OBSERVED RESULT End up on the screen shown in attachment with a large virtual keyboard and no UI. (For context this is a 34" monitor, so the keyboard size is absurd in any scenario.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476444] SDDM theme chooser glitches when installing two themes at once
https://bugs.kde.org/show_bug.cgi?id=476444 --- Comment #1 from Reuben --- Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476444] New: SDDM theme chooser glitches when installing two themes at once
https://bugs.kde.org/show_bug.cgi?id=476444 Bug ID: 476444 Summary: SDDM theme chooser glitches when installing two themes at once 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: k...@flavor8.com Target Milestone: --- Created attachment 162809 --> https://bugs.kde.org/attachment.cgi?id=162809&action=edit showing issue SUMMARY STEPS TO REPRODUCE 1. Startup & Shutdown > Login Screen 2. Get new SDDM themes 3. Click install on theme A and wait for evidence that something is happening 4. Click install on theme B OBSERVED RESULT Theme B eventually sort of half installs. There's a green checkmark on it, but it isn't (and doesn't become) available in the options in the main window. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476443] SDDM theme chooser is very laggy, frequently loses images it had already displayed
https://bugs.kde.org/show_bug.cgi?id=476443 Reuben changed: What|Removed |Added Summary|SDDM theme chooser is very |SDDM theme chooser is very |laggy, frequently loses |laggy, frequently loses |images it had already |images it had already |disaplyed |displayed -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476443] New: SDDM theme chooser is very laggy, frequently loses images it had already disaplyed
https://bugs.kde.org/show_bug.cgi?id=476443 Bug ID: 476443 Summary: SDDM theme chooser is very laggy, frequently loses images it had already disaplyed 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: k...@flavor8.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Be on a 15Mb connection 2. Go to settings, startup & shutdown, Login Screen 3. Click Get new SDDM themes Browse OBSERVED RESULT This UI could really use some love. The previews are a) very slow to download (which might be my current slow connection), but just scrolling around, it frequently decides to throw away all the preview images it has already rendered and re-render them. EXPECTED RESULT More slickness. It would also be lovely if there were a handful of pro themes in there, but that's an aside. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467324] Feature Request: Stamp annotations with fixed length/width ratio
https://bugs.kde.org/show_bug.cgi?id=467324 Reuben Martin changed: What|Removed |Added CC||reube...@gmail.com --- Comment #2 from Reuben Martin --- It also needs to re-draw the image in real time within the dotted outline so that you can preview scale and placement while dragging. This lack of aspect locking and preview makes for a very clunky stamp tool. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472977] New: Sudo dialog should defeat focus follows mouse
https://bugs.kde.org/show_bug.cgi?id=472977 Bug ID: 472977 Summary: Sudo dialog should defeat focus follows mouse Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 0. Have window behavior / focus set to "focus follows mouse" because you're not a heretic 1. Open Discover from the "updates available" prompt in the system tray 2. Click on update all / sudo dialog pops up 3. Somehow move mouse before typing password (I will try to repro and update - I've done this often enough now that there's more than just pebkac going on) OBSERVED RESULT Password is entered into the search field in Discover (because Discover grabs focus on the search field) and presumably has the potential to end up in system logs somewhere = bad times. EXPECTED RESULT Because Discover (and ideally the solution can be applied more generally) knows that it launched the sudo dialog, it should disable keyboard input until the sudo dialog is closed one way or the other. I.e. the sudo dialog should be a true modal rather than a float-in-front dialog. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-26-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468499] New: Make gwenview browsing UX compatible with dolphin / tighter integration
https://bugs.kde.org/show_bug.cgi?id=468499 Bug ID: 468499 Summary: Make gwenview browsing UX compatible with dolphin / tighter integration Classification: Applications Product: gwenview Version: 23.03.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- SUMMARY This may not be a gwenview issue, but filing here as a start. The experience of double clicking on an image in dolphin, and then browsing images that are side by side with it, is jarring. I would bet that this is how 90% of kde users encounter gwenview, 90% of the time. Issues: a) Sort order not preserved between dolphin and gwenview. b) When you press escape / close the full image, you end up back in gwenview's browser, not dolphin. This is highly confusing. c) If you browsed through a few dozen images, when you go back to dolphin you are located where you originally invoked gwenview, not where you finished. I also think gwenview's edit tools sidebar should show by default (since, while the button is there on the toolbar, it's not completely discoverable), and that in addition it should have an "edit with" cta, listing whatever image editing tools are installed. It could even always feature KDE suite tools (krita, ...) to drive installation/usage, if not already installed. Rationale for the latter is that the context menu/"open with" submenu is hard to find, and contains irrelevant entries anyway (chrome, imagemagick?!!) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466897] New: Discover is not resilient to network changes
https://bugs.kde.org/show_bug.cgi?id=466897 Bug ID: 466897 Summary: Discover is not resilient to network changes Classification: Applications Product: Discover Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Start upgrade of packages on wired network connection 2. Midway through, connect wifi, disconnect wired 3. OBSERVED RESULT Discover freezes and is unable to recover EXPECTED RESULT On network loss, discover should wait until a network connection is available and resume; alternately offer the user the option to rollback to clean state SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466896] Cancel flatpak upgrade does nothing
https://bugs.kde.org/show_bug.cgi?id=466896 Reuben changed: What|Removed |Added Version|unspecified |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466896] New: Cancel flatpak upgrade does nothing
https://bugs.kde.org/show_bug.cgi?id=466896 Bug ID: 466896 Summary: Cancel flatpak upgrade does nothing Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- STEPS TO REPRODUCE 1. Start upgrade of flatpak package, e.g. Zoom 2. Go to tasks, hit cancel 3. OBSERVED RESULT Nothing gets cancelled EXPECTED RESULT Task gets cancelled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464716] New: Very slow render time on restaurant menu
https://bugs.kde.org/show_bug.cgi?id=464716 Bug ID: 464716 Summary: Very slow render time on restaurant menu Classification: Applications Product: okular Version: 22.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Created attachment 155544 --> https://bugs.kde.org/attachment.cgi?id=155544&action=edit restaurant menu SUMMARY I've attached a 2.5MB 7 "page" restaurant menu. It looks like it's just one long image rather than properly encoded. Scrolling through this menu using the pager in the sidebar, there are 5-6 second pauses where the page that is scrolled to just displays as a white screen before it renders (on an 8 core i7). There appears to be no caching of previously rendered content (despite 32GB of ram being available) so scrolling up a previous page has the same issue, even if it was rendered just 30 seconds before. This seems to happen less when the app isn't full screened, so there may be some upscaling happening that slows it down. STEPS TO REPRODUCE 1. Open attached document 2. Scroll using the sidebar (you may need to scroll up and down fast to trigger it) 3. OBSERVED RESULT White screen for extensive period while rendering happens EXPECTED RESULT No delay in rendering SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.10 Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-29-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459872] Session freezes entirely and doesn't recover after AMD GPU reset caused by VAAPI
https://bugs.kde.org/show_bug.cgi?id=459872 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453147] amdgpu: GPU reset crash loop
https://bugs.kde.org/show_bug.cgi?id=453147 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462498] New: Discover identifies proprietary licenses as "roprietary"
https://bugs.kde.org/show_bug.cgi?id=462498 Bug ID: 462498 Summary: Discover identifies proprietary licenses as "roprietary" Classification: Applications Product: Discover Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- Created attachment 154195 --> https://bugs.kde.org/attachment.cgi?id=154195&action=edit roprietary SUMMARY See attached screenshot. SUMMARY Discover's UI doesn't warn users that Snap updates packages without user consent, that updates won't be visible in Discover's periodic notifications about system updates, and that applications installed by Snap will be restarted by the Snap system. These are all counter to expectations and different from everything else that Discover offers in search results, and so Snaps listed by Discover should contain an info panel above the fold that makes this clear. Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462497] New: Discover should warn that Snaps will be updated independently of Discover
https://bugs.kde.org/show_bug.cgi?id=462497 Bug ID: 462497 Summary: Discover should warn that Snaps will be updated independently of Discover Classification: Applications Product: Discover Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover's UI doesn't warn users that Snap updates packages without user consent, that updates won't be visible in Discover's periodic notifications about system updates, and that applications installed by Snap will be restarted by the Snap system. These are all counter to expectations and different from everything else that Discover offers in search results, and so Snaps listed by Discover should contain an info panel above the fold that makes this clear. Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462494] New: Discover should warn about flatpaks packaged by third parties
https://bugs.kde.org/show_bug.cgi?id=462494 Bug ID: 462494 Summary: Discover should warn about flatpaks packaged by third parties Classification: Applications Product: Discover Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- Created attachment 154193 --> https://bugs.kde.org/attachment.cgi?id=154193&action=edit flatpak intellij SUMMARY Discover's UI makes no distinction between flatpaks packaged by the developer and those packaged by third parties. It should. For example, see attached screenshot of IntelliJ. There are several things wrong here: 1) It says this is Apache 2.0 license (IntelliJ ultimate is commercial software) 2) It relies on the packager fessing up to not being affiliated to Jetbrains in the description, rather than highlighting that fact with some kind of caution or warning (compare to its display of the snap distribution of IntelliJ, which _is_ distributed by Jetbrains s SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460858] New: Don't switch away from "simultaneous output" if a device becomes unavailable
https://bugs.kde.org/show_bug.cgi?id=460858 Bug ID: 460858 Summary: Don't switch away from "simultaneous output" if a device becomes unavailable Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY Don't switch away from "simultaneous output" if a device becomes no longer present. (E.g. when I take the USB dongle for my headset to the coffee shop, or even on vacation, when I get back home and plug back in the USB dongle, "simultaneous output" should still be selected if I selected it previously.) Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-21-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460857] New: Request - "simultaneous output" should be shown as option by default if > 1 outputs
https://bugs.kde.org/show_bug.cgi?id=460857 Bug ID: 460857 Summary: Request - "simultaneous output" should be shown as option by default if > 1 outputs Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY In prior versions of KDE, "simultaneous output" to multiple devices could only be enabled by system settings. (I don't see it any longer - is it gone?) If there are more than 1 outputs, please add "Simultaneous Output" as an option in the system tray menu by default. It does not need to be selected, just be present. It's a useful option and shouldn't be buried. Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-21-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460856] New: Request - keyboard shortcut mappings for different devices
https://bugs.kde.org/show_bug.cgi?id=460856 Bug ID: 460856 Summary: Request - keyboard shortcut mappings for different devices Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY Please add the ability to map devices to keyboard shortcuts. I'd like to be able to switch between speakers and headset without having to go to system tray. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-21-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Manufacturer: MSI Product Name: MS-7978 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460657] New: Settings - should be able to disable a microphone without disabling the audio output of the same card
https://bugs.kde.org/show_bug.cgi?id=460657 Bug ID: 460657 Summary: Settings - should be able to disable a microphone without disabling the audio output of the same card 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: k...@flavor8.com Target Milestone: --- SUMMARY Under System Settings > Audio, it's not possible to disable a microphone without also disabling the audio output that it's associated with. See attached screenshot; I would like to eliminate "Microphone (USB Audio Device Mono)" as an option from the system tray audio widget; however, doing so ALSO eliminates "Speakers (USB Audio Device Stereo)", which is incorrect. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460655] New: Request - better ergonomics around multiple audio devices
https://bugs.kde.org/show_bug.cgi?id=460655 Bug ID: 460655 Summary: Request - better ergonomics around multiple audio devices 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: k...@flavor8.com Target Milestone: --- SUMMARY I have: a) A bluetooth headset, with its own USB dongle b) A soundbar on the bottom of my monitor, which shows up as a USB device Sometimes I'll remove the headset's USB dongle and use it with my laptop, when working from a coffee shop. Switching between outputs from the icon in the system tray works. It's fine. It's just not very ergonomic. Requests (I can split into separate tickets if they are viable): a) Allow keyboard shortcuts to be mapped to allow switching between devices. b) Make "simultaneous output" a _default_ option (not necessarily selected, but at least present in the device menu) when there is more than one output device. (Right now, you have to find it in the settings and enable it.) c) Don't switch away from "simultaneous output" if a device becomes no longer present. (E.g. when I take the USB dongle for my headset to the coffee shop, or even on vacation, when I get back home and plug back in the USB dongle, "simultaneous output" should still be selected.) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460548] Language setting is overridden by Formats:Region setting
https://bugs.kde.org/show_bug.cgi?id=460548 --- Comment #2 from Reuben --- Created attachment 152905 --> https://bugs.kde.org/attachment.cgi?id=152905&action=edit settings -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460548] Language setting is overridden by Formats:Region setting
https://bugs.kde.org/show_bug.cgi?id=460548 --- Comment #1 from Reuben --- Created attachment 152904 --> https://bugs.kde.org/attachment.cgi?id=152904&action=edit settings -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460548] New: Language setting is overridden by Formats:Region setting
https://bugs.kde.org/show_bug.cgi?id=460548 Bug ID: 460548 Summary: Language setting is overridden by Formats:Region setting 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: k...@flavor8.com Target Milestone: --- Created attachment 152903 --> https://bugs.kde.org/attachment.cgi?id=152903&action=edit settings SUMMARY Under Regional Settings, there is a) Language and b) Formats. Language should control...language. However, language is controlled by Formats: Region. STEPS TO REPRODUCE 1. Set Format: Region to es_CR (Costa Rica) 2. Set Language to: American English 3. Restart your session 4. Result: the KDE UI is localized to Spanish, despite the Language setting having been specified as English Please remember: Region is not equivalent to Language. OBSERVED RESULT Setting Language to English is ignored if Region has a different "default" language. EXPECTED RESULT Language should be independently settable from Region. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION $LANG gets set to es_CR in this case. If LANG is supposed to represent language, shouldn't it track...Language? Screenshots showing issue attached. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459706] Driver manager pops up small terminal to perform sudo
https://bugs.kde.org/show_bug.cgi?id=459706 --- Comment #2 from Reuben --- Interesting. Is this a component the KDE team have looked at adopting and improving? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459706] New: Driver manager pops up small terminal to perform sudo
https://bugs.kde.org/show_bug.cgi?id=459706 Bug ID: 459706 Summary: Driver manager pops up small terminal to perform sudo Classification: Applications Product: systemsettings Version: 5.24.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com Target Milestone: --- When opening driver manager from system settings, a terminal is used to ask for the sudo password. This is bad UX and arguably a bad security practice (since users should not be "trained" to enter their password into any random window that appears). Further, the terminal is xterm rather than konsole or the system default terminal, and thus is likely to have relatively poor styling on high resolution monitors. It's very easy to miss. Finally (this is more of a wishlist) the UX around pressing a button in system settings to launch driver manager is poor. It would be nice if the UI was inline, and required sudo when the user interacted with it. Surely the fact of drivers being used is visible to non-root users? STEPS TO REPRODUCE 1. system settings 2. driver manager 3. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459564] New: Dell XPS 13 "pseudo" volume keys don't work in KDE
https://bugs.kde.org/show_bug.cgi?id=459564 Bug ID: 459564 Summary: Dell XPS 13 "pseudo" volume keys don't work in KDE 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: k...@flavor8.com Target Milestone: --- Created attachment 152368 --> https://bugs.kde.org/attachment.cgi?id=152368&action=edit The pseudo keys SUMMARY I have a Dell XPS 13 which has pseudo function keys. All of them work in KDE except for the volume up / down and mute. When I press them, there is no change to the volume, whether I have headphones plugged in or not. If I go into shortcuts and attempt to map the keys to the volume events as custom shortcuts (on the theory that they are producing odd key event), I get a message saying that they are already mapped (i.e. so they are producing the right keyboard events). I unfortunately can't buy somebody one of these machines to debug with, but happy to provide any additional logs as needed. Output of xev when pressing each of the keys is below. ``` KeyPress event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67346182, (-335,199), root:(536,724), state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67346303, (-335,199), root:(536,724), state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67348292, (-335,199), root:(536,724), state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67348437, (-335,199), root:(536,724), state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67351308, (-335,199), root:(536,724), state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 39, synthetic NO, window 0x721, root 0x79f, subw 0x0, time 67351478, (-335,199), root:(536,724), state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435690] [Wayland] Kickoff, Krunner, and other applets open in the wrong place
https://bugs.kde.org/show_bug.cgi?id=435690 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458898] New: Inline filesystem operation progress bars
https://bugs.kde.org/show_bug.cgi?id=458898 Bug ID: 458898 Summary: Inline filesystem operation progress bars Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@flavor8.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY On one of my systems, the OS notifications that pop up for filesystem notifications no longer appear. I have no idea about whether an operation has finished or not. Request: make this inline to dolphin, perhaps in addition to OS notifications. Take inspiration from Chrome or Firefox's handling of downloads, so that there's a clickable icon in the UI that shows a list of in progress operations on click or hover. (If there is one already, it's not obvious enough.) Ideally the icon would itself show some status, e.g. would be a pie that's filled based on the percentage of completion across all operations. STEPS TO REPRODUCE 1. Do significant filesystem operations (copy, move, etc) 2. Somehow misconfigure your system so that OS notifications don't pop up for dolphin OBSERVED RESULT User is confused as to whether the operation has completed EXPECTED RESULT There should be somewhere obvious within Dolphin to get at any in progress operations SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.0-47 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458897] New: Add copy button to "About this sytem"
https://bugs.kde.org/show_bug.cgi?id=458897 Bug ID: 458897 Summary: Add copy button to "About this sytem" Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com Target Milestone: --- SUMMARY KDE bug filing requires that system info be filled in. You can't even highlight and manually copy the labels in this panel; can we make it easier for bug reporters and just add a "copy info" button to populate the clipboard with what a bug report needs, in terms of versions? STEPS TO REPRODUCE 1. About > System 2. Try to get info for bug report 3. OBSERVED RESULT Difficult EXPECTED RESULT Easy SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.0-47 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458896] New: Scrolling while a file is in rename mode should not toggle rename mode off
https://bugs.kde.org/show_bug.cgi?id=458896 Bug ID: 458896 Summary: Scrolling while a file is in rename mode should not toggle rename mode off Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@flavor8.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If a file is in rename mode (f2), it should not toggle out of rename until a submit or cancel event. Scrolling is neither, and should not toggle the file out of rename. STEPS TO REPRODUCE 1. Highlight a file, click f2 2. Scroll the pane so that the file goes out of view OBSERVED RESULT Any in progress name changes are cancelled, and the file name is reverted EXPECTED RESULT File should still be in rename mode when you scroll back up to bring it into view SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.0-47 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458895] New: Dragging and dropping into an expanded tree node (folder) should drop the file into that folder
https://bugs.kde.org/show_bug.cgi?id=458895 Bug ID: 458895 Summary: Dragging and dropping into an expanded tree node (folder) should drop the file into that folder Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@flavor8.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open split view 2. Open tree view 3. Open a folder 4. Drag a file from the other pane and drop somewhere into the expanded tree node OBSERVED RESULT The file is copied to the parent folder _unless_ the drop is precisely on the name of the folder (rather than the expanded tree node area) EXPECTED RESULT File should target the expanded folder as long as the drop is somewhere within the expanded tree node area SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.0-47 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 458348] New: Desktop calendar widget not showing both decade and year
https://bugs.kde.org/show_bug.cgi?id=458348 Bug ID: 458348 Summary: Desktop calendar widget not showing both decade and year Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Created attachment 151618 --> https://bugs.kde.org/attachment.cgi?id=151618&action=edit missing digit Please see attached. The date format doesn't match what is actually rendered. This is a recent regression. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457600] Krunner can order AppStream results higher than apps and KCMs
https://bugs.kde.org/show_bug.cgi?id=457600 --- Comment #4 from Reuben --- Ironically enough, searching "ouse" bring "Mouse (settings)" to the top of the list, and doesn't find "Mousetrap". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447120] Lockups when configuring kwin [wayland]
https://bugs.kde.org/show_bug.cgi?id=447120 --- Comment #2 from Reuben --- Sorry, I don't remember. You could close this one out. I'll try again with Wayland after the next ubuntu release. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457600] Krunner results should be ranked by relevance
https://bugs.kde.org/show_bug.cgi?id=457600 --- Comment #2 from Reuben --- OK - then how about: "the ranking of results is wrong". It's hard to represent that it's more relevant to show a minor uninstalled game that has a subword match vs showing a settings section that is an exact match. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457600] New: Krunner results should be ranked by relevance
https://bugs.kde.org/show_bug.cgi?id=457600 Bug ID: 457600 Summary: Krunner results should be ranked by relevance Product: krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: alexander.loh...@gmx.de Target Milestone: --- Created attachment 151167 --> https://bugs.kde.org/attachment.cgi?id=151167&action=edit screenshot SUMMARY Exact matches should bubble to the top. Further, uninstalled applications should probably never be the first option. STEPS TO REPRODUCE 1. Search "mouse" OBSERVED RESULT 1. Mousetrap (uninstalled, probably quite a rarely installed package) is first option; "mouse" (settings) is 3rd down EXPECTED RESULT 1. "Mouse" settings should be first SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455785] Discover locking up doing upgrades
https://bugs.kde.org/show_bug.cgi?id=455785 --- Comment #4 from Reuben --- Created attachment 150092 --> https://bugs.kde.org/attachment.cgi?id=150092&action=edit startup errors -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455785] Discover locking up doing upgrades
https://bugs.kde.org/show_bug.cgi?id=455785 --- Comment #3 from Reuben --- Created attachment 150091 --> https://bugs.kde.org/attachment.cgi?id=150091&action=edit pkmon -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455785] New: Discover locking up doing upgrades
https://bugs.kde.org/show_bug.cgi?id=455785 Bug ID: 455785 Summary: Discover locking up doing upgrades Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- Created attachment 150048 --> https://bugs.kde.org/attachment.cgi?id=150048&action=edit screenshot of issue SUMMARY This has now happened to me twice. Discover locks up during upgrades. There are no details of what it's blocked on in the UI (this would be a useful improvement.) STEPS TO REPRODUCE 1. Unknown. See attached screenshot. I suspect the issue has to do with the packages listed in the top section. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453556] New: Left handed mouse reset to right handed after screen unlock
https://bugs.kde.org/show_bug.cgi?id=453556 Bug ID: 453556 Summary: Left handed mouse reset to right handed after screen unlock Product: kscreenlocker Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set mouse (trackball) to left handed 2. Lock screen; unlock screen OBSERVED RESULT Mouse is right handed, despite "left" still being checked in kcontrol EXPECTED RESULT Mouse buttons should be stable SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453546] New: KDE crash when login to wayland for the first time after upgrade
https://bugs.kde.org/show_bug.cgi?id=453546 Bug ID: 453546 Summary: KDE crash when login to wayland for the first time after upgrade Product: plasmashell Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@flavor8.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-27-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Upgraded to 22.04 Opened a wayland session to see if it was working better than it had before Hard crash, cannot do anything The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140247690111424) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140247690111424) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140247690111424, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f8df9f74476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f8df9f5a7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f8dfa416ba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f8df85f33e4 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f8df85f411a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f8dfa6777b8 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f8dfa69913b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f8dfa63e74b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f8ddd43507f in qt_plugin_instance () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kscreen/KSC_KWayland.so #16 0x7f8dfa635a1f in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f8ddeaeab2f in KScreen::BackendManager::loadBackendPlugin(QPluginLoader*, QString const&, QMap const&) () at /lib/x86_64-linux-gnu/libKF5Screen.so.7 #18 0x7f8ddeaefd8e in KScreen::BackendManager::loadBackendInProcess(QString const&) () at /lib/x86_64-linux-gnu/libKF5Screen.so.7 #19 0x7f8ddeaf03e3 in () at /lib/x86_64-linux-gnu/libKF5Screen.so.7 #20 0x7f8ddeaf7ce6 in KScreen::GetConfigOperation::start() () at /lib/x86_64-linux-gnu/libKF5Screen.so.7 #21 0x7f8dfa66d40e in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f8dfb336713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f8dfa63fe2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f8dfa642f17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f8dfa699a57 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f8df8a1bd1b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f8df8a706f8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f8df8a193c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f8dfa6990a8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f8dfa63e74b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f8dfa646ce4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x5621c007cdce in () #33 0x7f8df9f5bd90 in __libc_start_call_main (main=main@entry=0x5621c007bf70, argc=argc@entry=1, argv=argv@entry=0x7ffc1cabb9e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #34 0x7f8df9f5be40 in __libc_start_main_impl (main=0x5621c007bf70, argc=1, argv=0x7ffc1cabb9e8, init=, fini=, rtld_fini=, stack_end=0x7ffc1cabb9d8) at ../csu/libc-start.c:392 #35 0x5621c007cef5 in () [Inferior 1 (process 1706) detached] Possible duplicates by query: bug 453544, bug 453125, bug 451976, bug 451124, bug 451114. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 313170] Allow selecting which X screen is active
https://bugs.kde.org/show_bug.cgi?id=313170 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447636] Android 11: scoped storage does not allow to share the root of the filesystem
https://bugs.kde.org/show_bug.cgi?id=447636 Reuben changed: What|Removed |Added CC||maxxxreu...@gmail.com --- Comment #1 from Reuben --- I face the same issue. Was previously able to select root folder of my phone as mount point, but it doesn't allow anymore in Android 11.0.5.1 on a OnePlus 7T running OxygenOS. Kdeconnect app version: 1.19.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447403] Feature request - show which repo an install is coming from
https://bugs.kde.org/show_bug.cgi?id=447403 Reuben changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #2 from Reuben --- Ah, I see it. Then could we change this to: "Request: move source above the description in the discover package details"? Rationale: it's important to know if a PPA is giving you a core package. Description could easily push source below the fold, as of course could the reviews. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 447795] option "use for playlist and folder names" in FileName Format string replacement breaks rename folder
https://bugs.kde.org/show_bug.cgi?id=447795 --- Comment #4 from Reuben --- fixed in git version -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 447798] crash on "rewrite tags" when album frame is shown in file list
https://bugs.kde.org/show_bug.cgi?id=447798 --- Comment #3 from Reuben --- Fixed in git version -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 447795] option "use for playlist and folder names" in FileName Format string replacement breaks rename folder
https://bugs.kde.org/show_bug.cgi?id=447795 --- Comment #3 from Reuben --- Thanks a lot Urs, I'll check this as soon as possible Reuben On Sun, Jan 2, 2022 at 11:31 AM Urs Fleisch wrote: > https://bugs.kde.org/show_bug.cgi?id=447795 > > --- Comment #2 from Urs Fleisch --- > Thank you very much for reporting this bug. I have fixed it in version > git20220102, which can be found in > https://sourceforge.net/projects/kid3/files/kid3/development/. Could you > please > test if it works for you? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 447798] New: crash on "rewrite tags" when album frame is shown in file list
https://bugs.kde.org/show_bug.cgi?id=447798 Bug ID: 447798 Summary: crash on "rewrite tags" when album frame is shown in file list Product: kid3 Version: 3.9.x Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: reuben.ka...@gmail.com Target Milestone: --- Application: kid3 (3.9.0) Qt Version: 5.15.2 Frameworks Version: 5.89.0 Operating System: Linux 5.14.13-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: 1.Open an album in kid3 2.in file list, add Album frame. 3.Select all files. 4. RMB menu - select "Rewrite Tags" -- crash The crash can be reproduced every time. -- Backtrace: Application: Kid3 (kid3), signal: Segmentation fault [KCrash Handler] #4 0x0020 in () #5 0x7f2916c06bc1 in () at /usr/lib/kid3/plugins/libtaglibmetadata.so #6 0x7f293f2be2e8 in TaggedFileSystemModel::data(QModelIndex const&, int) const () at /usr/lib/kid3/libkid3-core.so #7 0x7f293df115a9 in QSortFilterProxyModel::data(QModelIndex const&, int) const () at /usr/lib/libQt5Core.so.5 #8 0x7f293ed140ba in QStyledItemDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5 #9 0x7f293ed17c9b in QStyledItemDelegate::sizeHint(QStyleOptionViewItem const&, QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5 #10 0x7f293ed639cd in QTreeView::indexRowSizeHint(QModelIndex const&) const () at /usr/lib/libQt5Widgets.so.5 #11 0x7f293ed63bb2 in QTreeViewPrivate::itemHeight(int) const () at /usr/lib/libQt5Widgets.so.5 #12 0x7f293ed58e9b in QTreeView::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f293df6742f in () at /usr/lib/libQt5Core.so.5 #14 0x7f293def35ca in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #15 0x7f293f27607c in FileProxyModel::onFileModificationChanged(QModelIndex const&, bool) () at /usr/lib/kid3/libkid3-core.so #16 0x7f293df673e3 in () at /usr/lib/libQt5Core.so.5 #17 0x7f293f2d3f38 in TaggedFileSystemModel::fileModificationChanged(QModelIndex const&, bool) () at /usr/lib/kid3/libkid3-core.so #18 0x7f2916bf6fde in () at /usr/lib/kid3/plugins/libtaglibmetadata.so #19 0x7f293f2896ab in Kid3Application::saveDirectory() () at /usr/lib/kid3/libkid3-core.so #20 0x7f293f2d1fcc in () at /usr/lib/kid3/libkid3-core.so #21 0x7f293f2d3b6b in Kid3Application::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/kid3/libkid3-core.so #22 0x7f2933e43c9e in () at /usr/lib/libQt5Qml.so.5 #23 0x7f2933d1ddd7 in () at /usr/lib/libQt5Qml.so.5 #24 0x7f2933d20f6b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5 #25 0x7f2933d3e0c0 in () at /usr/lib/libQt5Qml.so.5 #26 0x7f2933d40dbf in () at /usr/lib/libQt5Qml.so.5 #27 0x7f2933cd3ed9 in () at /usr/lib/libQt5Qml.so.5 #28 0x7f2933cd4bc0 in () at /usr/lib/libQt5Qml.so.5 #29 0x7f2933d3e0c0 in () at /usr/lib/libQt5Qml.so.5 #30 0x7f2933d40dbf in () at /usr/lib/libQt5Qml.so.5 #31 0x7f2933cd3ed9 in () at /usr/lib/libQt5Qml.so.5 #32 0x7f2933d258ef in () at /usr/lib/libQt5Qml.so.5 #33 0x7f293df673e3 in () at /usr/lib/libQt5Core.so.5 #34 0x7f2933ec7dee in QQmlTimer::event(QEvent*) () at /usr/lib/libQt5Qml.so.5 #35 0x7f293ea8c1a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #36 0x55df87d4dd60 in () #37 0x7f293df3689a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #38 0x7f293df37399 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #39 0x7f293df7db88 in () at /usr/lib/libQt5Core.so.5 #40 0x7f293c8ff52c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #41 0x7f293c9537b9 in () at /usr/lib/libglib-2.0.so.0 #42 0x7f293c8fcc11 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #43 0x7f293df81a8a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #44 0x7f293df2ea9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #45 0x7f293df3a2c7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #46 0x55df87d43591 in () #47 0x7f293dafcb25 in __libc_start_main () at /usr/lib/libc.so.6 #48 0x55df87d43a5e in _start () [Inferior 1 (process 60549) detached] Report to https://bugs.kde.org/SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_
[kid3] [Bug 447795] option "use for playlist and folder names" in FileName Format string replacement breaks rename folder
https://bugs.kde.org/show_bug.cgi?id=447795 Reuben changed: What|Removed |Added Version|unspecified |3.9.x -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 447795] New: option "use for playlist and folder names" in FileName Format string replacement breaks rename folder
https://bugs.kde.org/show_bug.cgi?id=447795
Bug ID: 447795
Summary: option "use for playlist and folder names" in FileName
Format string replacement breaks rename folder
Product: kid3
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: uflei...@users.sourceforge.net
Reporter: reuben.ka...@gmail.com
Target Milestone: ---
SUMMARY
***
option "use for playlist and folder names" in FileName Format string
replacement breaks rename folder functionality
***
STEPS TO REPRODUCE
1. set option "use for playlist and folder names" in FileName Format string
replacement (it is by ddefault now it seems)
2. check there is string replacement "/" to "-"
3. try to rename folder with option %{artist}/%y - %{album}
OBSERVED RESULT
folder is renamed to %{artist}-%y - %{album}
EXPECTED RESULT
folder is renamed to %{artist}/%y - %{album}
replacement should apply inside the tokens, not to the whole string.
SOFTWARE/OS VERSIONS
Version 3.9.0
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
KDE Frameworks
Version 5.89.0
Qt Version:
Version 5.15.2 (built against 5.15.2)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 447168] System tray in vertical mode does not wrap the menu indicator vertically
https://bugs.kde.org/show_bug.cgi?id=447168 --- Comment #4 from Reuben --- Created attachment 144818 --> https://bugs.kde.org/attachment.cgi?id=144818&action=edit vertical Good tip - so it does look like there is a vertical form factor available which does the right thing. Is there a way to force a desktop widget to a particular form factor? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447404] New: Log in to plasma-x; log out to lightdm; log in to plasma-wayland -- keyboard/mouse freeze
https://bugs.kde.org/show_bug.cgi?id=447404 Bug ID: 447404 Summary: Log in to plasma-x; log out to lightdm; log in to plasma-wayland -- keyboard/mouse freeze Product: kwin Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- 1) From lightdm, log into plasma / x session 2) Krunner, logout 3) In lightdm, switch session to plasma / wayland & login 4) The desktop comes up, but the keyboard/mouse are unresponsive. Pressing the power button on my laptop brings up the KDE power-off menu, so something is still alive and listening, but whatever is in charge of listening for user events has crashed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447328] File browse dialog crash under some applications (e.g. chrome)
https://bugs.kde.org/show_bug.cgi?id=447328 --- Comment #1 from Reuben --- This appears to have magically fixed itself after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447403] New: Feature request - show which repo an install is coming from
https://bugs.kde.org/show_bug.cgi?id=447403 Bug ID: 447403 Summary: Feature request - show which repo an install is coming from Product: Discover Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@flavor8.com CC: aleix...@kde.org Target Milestone: --- PPAs are for better or worse widespread. (To my understanding) if a PPA were to be compromised, an attacker could introduce packages outside of the core scope of the PPA (e.g. somebody could introduce a backdoored version of systemd via a pipewire PPA). For this reason, it'd be useful if Discover shows which repo a package update is coming from, to give the user a chance to see something unusual. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447328] New: File browse dialog crash under some applications (e.g. chrome)
https://bugs.kde.org/show_bug.cgi?id=447328 Bug ID: 447328 Summary: File browse dialog crash under some applications (e.g. chrome) Product: kwin Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Using wayland: File browse dialog doesn't show under chrome. It does work for firefox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447161] 3 separate entries for "kwin" under shortcuts
https://bugs.kde.org/show_bug.cgi?id=447161 Reuben changed: What|Removed |Added Version|unspecified |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447163] Applications abruptly killed under wayland, can't restart
https://bugs.kde.org/show_bug.cgi?id=447163 Reuben changed: What|Removed |Added Version|unspecified |5.22.5 --- Comment #2 from Reuben --- This appears to have been fixed in 5.23.4 (pending a full day's testing without it happening). However, the version I was encountering it on is the one shipped with kubuntu 21.10, so you may want to push a patch down to 5.22 given that there are another 4 months before kubuntu users will get the fix (without using backports), given that it's a showstopper to using wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447280] New: Cut/paste under wayland is hit and miss
https://bugs.kde.org/show_bug.cgi?id=447280 Bug ID: 447280 Summary: Cut/paste under wayland is hit and miss Product: kwin Version: 5.23.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- I particularly notice this in IntelliJ, where I'm constantly cutting & pasting when refactoring code. It works perhaps 80% of the time, but in the remaining 20% the clipboard content goes missing. This is specifically associated with running under wayland, as IntelliJ cut/paste is rock solid under X. I will update this ticket if I noticed it under other applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447285] New: Quick flicker/render of different display when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=447285 Bug ID: 447285 Summary: Quick flicker/render of different display when switching virtual desktops Product: kwin Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Setup (under wayland): 1) External monitor, 4k, enabled/primary, 150% scaling 2) Laptop monitor, 1920, enabled, 100% scaling; laptop lid closed When I switch virtual desktops, there's a flicker showing the laptop's desktop on the external monitor. If I disable the laptop monitor, the flicker stops happening. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447173] New: [wayland] Switching source on external monitor is unrecoverable
https://bugs.kde.org/show_bug.cgi?id=447173 Bug ID: 447173 Summary: [wayland] Switching source on external monitor is unrecoverable Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Using wayland, with external 4k monitor attached to laptop. Set display as: a) External monitor primary b) Laptop monitor enabled=false [This is a continued attempt at holy grail configuration of the laptop as a desktop.] In the source menu of the monitor, switch from HDMI1 to HDMI2 to check on another computer's output. Then switch back to HDMI1. Expected: * Display reinitializes Bug: * Black screen which is unrecoverable from; even opening laptop lid doesn't do anything (because of aforementioned display config) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447163] Applications abruptly killed under wayland, can't restart
https://bugs.kde.org/show_bug.cgi?id=447163 --- Comment #1 from Reuben --- This is repeatable. Running under lightdm this time (previously under sddm) it brought up the KDE crash handler, which showed that plasmashell had exited unexpectedly (IIRC error 1826). This had the result of crashing most of my applications; terminator was still present but wouldn't accept input. I could bring up krunner but couldn't type into it either. Please let me know where to find relevant logs and I can try again. Version: 4:5.22.5-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447168] System tray in vertical mode does not wrap the menu indicator vertically
https://bugs.kde.org/show_bug.cgi?id=447168 --- Comment #2 from Reuben --- 4:5.22.5-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447168] New: System tray in vertical mode does not wrap the menu indicator vertically
https://bugs.kde.org/show_bug.cgi?id=447168 Bug ID: 447168 Summary: System tray in vertical mode does not wrap the menu indicator vertically Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Created attachment 144642 --> https://bugs.kde.org/attachment.cgi?id=144642&action=edit systray screenshot 1. Add system tray as a widget to the desktop 2. Resize vertically EXPECTED Should be able to resize to 1 column wide CURRENT BEHAVIOR Systray menu icon won't wrap -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447167] New: Cannot launch krunner with meta (without manual workaround)
https://bugs.kde.org/show_bug.cgi?id=447167 Bug ID: 447167 Summary: Cannot launch krunner with meta (without manual workaround) Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Binding Alt+f1 to any of the application launchers is enough to get meta to launch them. However, this doesn't work with krunner. There is a workaround, which is to run: kwriteconfig5 --file kwinrc --group ModifierOnlyShortcuts --key Meta "org.kde.krunner,/App,,toggleDisplay" Please a) allow meta to be associated with krunner as a shortcut via the UI; b) perhaps more generally provide a way in shortcuts for "meta" to be _the_ shortcut, without needing the alt+f1 workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447163] New: Applications abruptly killed under wayland, can't restart
https://bugs.kde.org/show_bug.cgi?id=447163 Bug ID: 447163 Summary: Applications abruptly killed under wayland, can't restart Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@flavor8.com Target Milestone: --- Hard to reproduce wayland bug. Not sure where to find appropriate log. I was using chrome/intellij on separate virtual desktops. While typing in intellij, it was abruptly terminated. When I try to restart it, I get the following (which leads me to believe that something in wayland crashed): Start Failed Failed to initialize graphics environment java.awt.AWTError: Can't connect to X11 window server using ':1' as the value of the DISPLAY variable. at java.desktop/sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at java.desktop/sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:104) When I attempt to restart chrome, I get (less usefully): “google-chrome” terminated by signal SIGTRAP (Trace or breakpoint trap) Other apps remained open or can be started (firefox, terminator). -- You are receiving this mail because: You are watching all bug changes.
