[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #37 from Prajna Sariputra --- (In reply to Katharina Fey from comment #36) > As far as I can tell (at least on my system) there's no "workspace overview" > (the one) screen edge corner. Previously it was easy for me to move > windows across workspace grid with just my mouse, now that's not possible > anymore without also using my keyboard That's bug 478137, which will be fixed when Plasma 6.1 comes out. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 458336] Krfb crashes after some time on Wayland/PipeWire
https://bugs.kde.org/show_bug.cgi?id=458336 Prajna Sariputra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Prajna Sariputra --- krfb-virtualmonitor did manage to last more than 30mins this time it seems, so yeah seems fixed now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #28 from Prajna Sariputra --- > When pressing 'Meta+W' to get overview, pressing it again simply enters 'W' > in the search. You'll probably want to file a different bug report for that, it's certainly not intentional. Also, there are two different shortcuts that can get you to the overview, one is "Toggle Overview" and the other is "Cycle through Overview and Grid View", the first one defaults to Meta+W and the other defaults to Meta+Tab. Only the second one will behave as Niccolò described (press once to open overview, press again to switch to grid view). -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 --- Comment #4 from Prajna Sariputra --- Oh, if you're using KDE Connect and you're stopping the remote control session via the system tray icon then I think that's actually a problem from the KDE Connect side, I don't think it has support for automatically restarting the remote control session if the user stopped it manually at the moment, so KDE Connect will just try (and fail) to use the old cancelled session, and you won't see a notification or permissions dialog until you restart kdeconnectd and try using remote input again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #25 from Prajna Sariputra --- > what if, when you start dragging a window, the effect automatically switches > to the desktop grid so that it's easier to drop in to another desktop? (and, > why would you be drag-and-dropping a window on the Overview anyway, without > the desktop bar?) While that would improve the usefulness of the overview with a grid of desktops, it would still be missing the ability of switching virtual desktops with just the mouse, especially since for hot corners and edges triggering the effect twice to get to the grid doesn't work, and assigning the hot corner to the grid rather than the overview (only possible in 6.1) means that the KRunner powered search isn't accessible. While there are of course other ways of using just the mouse to switch desktops (pager widget, scrolling on the desktop background if that's enabled, assigning the grid to a different corner/edge), what I loved about the Plasma 5 overview is that it was a one stop shop for everything: app launching, app switching, desktop switching, moving apps between desktops, and everything else KRunner can do, instead of having to go to the other separate places to do these things (Kickoff, Alt+Tab app switcher, task manager widget, pager widget, grid effect). Also, the reason I'm using a grid of desktops (2 rows, 3 columns in my case) instead of having them all in one row/column is that with wraparound enabled it only takes me 2 touchpad gestures (or switch to left/right/up/down desktop shortcut) at most to get from one desktop to any other one of the 6, and 3 of the desktops are always accessible with just one gesture/shortcut. If the 2D gestures support comes in then that would make all the desktops accessible with just one gesture with my grid setup. > and what is supposed to happen, after dropping it? Will the grid remain open? > will the overview be shown again? with the same VD focused or the one where > the window was dropped? Currently if the desktop bar is visible dragging and dropping a window into another virtual desktop will not change the current VD (say if you're in VD1 and you drop a window to VD3 then the overview would stay at VD1), so to maintain that sort of behavior after dropping a window the overview should be shown again at the same VD the user started at. That would have a disadvantage of a lot of stuff moving around on screen all the time if someone has say 4 windows in one VD and wants to move all of them into other VDs though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482847] New: Additional mouse button bindings no longer work since commit bf1ce854748bfd2433c336a9ee972883cb8617ab
https://bugs.kde.org/show_bug.cgi?id=482847
Bug ID: 482847
Summary: Additional mouse button bindings no longer work since
commit bf1ce854748bfd2433c336a9ee972883cb8617ab
Classification: Plasma
Product: kwin
Version: master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: input
Assignee: kwin-bugs-n...@kde.org
Reporter: putr...@gmail.com
Target Milestone: ---
SUMMARY
With Plasma 6.1 from git master, I noticed that the bindings I have set up for
the additional buttons on my mouse no longer work, they just end up doing the
default action bound to them. In my case the buttons are recognized by libinput
as `BTN_EXTRA (276)` and `BTN_SIDE (275)`.
If I revert the part of commit bf1ce854748bfd2433c336a9ee972883cb8617ab (Make
it possible to build KWin without libxcb) that applies to the buttonrebinds
plugin then the bindings work again, and reverting KWin to the commit before
that also works.
In the system logs, these messages appeared when I pressed the mouse buttons
(two of these messages appear for every button press):
> kwin_wayland[42047]: kwin_buttonrebinds: Could not convert
> QKeySequence("Meta+G") syms: QList(285212743) to keycode
> kwin_wayland[42047]: kwin_buttonrebinds: Could not convert
> QKeySequence("Meta+G") syms: QList(285212743) to keycode
> kwin_wayland[42047]: kwin_buttonrebinds: Could not convert
> QKeySequence("Alt+F1") syms: QList(150994992) to keycode
> kwin_wayland[42047]: kwin_buttonrebinds: Could not convert
> QKeySequence("Alt+F1") syms: QList(150994992) to keycode
STEPS TO REPRODUCE
1. Have a mouse with extra buttons that can be configured via the "Re-bind
Additional Mouse Buttons..." page in the Mouse KCM (mine is just a random
"gaming" mouse I picked up in a nearby store, with two side buttons)
2. Set up a binding for one of those mouse buttons (I used Meta+G and Alt+F1
for the desktop grid and app launcher)
3. Press the mouse button with the binding
OBSERVED RESULT
The button acts as if no binding was set and just performs the default action
(for me the buttons act like forward and back buttons of some sort out of the
box).
EXPECTED RESULT
The keyboard shortcut bound to the button should be triggered.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-arch1-1 (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=476161 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481808] Clicking "Sleep" on the lockscreen makes it also display a failed login attempt
https://bugs.kde.org/show_bug.cgi?id=481808 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481857] Clicking on the top right corner of the screen no longer hits the close button for maximized windows
https://bugs.kde.org/show_bug.cgi?id=481857 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481857] New: Clicking on the top right corner of the screen no longer hits the close button for maximized windows
https://bugs.kde.org/show_bug.cgi?id=481857 Bug ID: 481857 Summary: Clicking on the top right corner of the screen no longer hits the close button for maximized windows Classification: Plasma Product: Breeze Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- SUMMARY With Breeze and KDecoration from the Plasma/6.0 branch, if a window is maximized moving the cursor to the top right corner of the screen quickly and clicking no longer closes the window. This makes closing maximized windows with the mouse less convenient since accurate positioning of the cursor is now required instead of being able to take advantage of Fitts' law. This is happening since https://invent.kde.org/plasma/kdecoration/-/merge_requests/56 and https://invent.kde.org/plasma/breeze/-/merge_requests/416 were merged. The master branch is not affected since the MRs were only applied for 6.0. STEPS TO REPRODUCE 1. Build Breeze and KDecoration from the Plasma/6.0 branch 2. Open a window and maximize it 3. Move the cursor to the top right corner of the screen 4. Click OBSERVED RESULT The maximised window is not closed, and the close button on the titlebar is not highlighted. EXPECTED RESULT The maximised window is closed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476655] Clicking on windows/desktops in the new overview/grid effect no longer works after a remote desktop/input connection is started on Wayland
https://bugs.kde.org/show_bug.cgi?id=476655 Prajna Sariputra changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from Prajna Sariputra --- Huh, just tested this again and apparently it got fixed somehow at some point? Now I have Qt 6.6.2, KWin at f349d8e13274e34afcd4b52c43abb3f134ed6cca and xdg-desktop-portal-kde at 05d0873850b75ee8a045b9a56791acfffd1342ab, from git master, compiled sometime on 19 Feb. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481188] Spectacle hangs when trying to start a second recording
https://bugs.kde.org/show_bug.cgi?id=481188 Prajna Sariputra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||putr...@gmail.com Latest Commit||https://invent.kde.org/grap ||hics/spectacle/-/commit/dcf ||2c08cdd312d1e9b4a91b03c004a ||05c378af2b Version Fixed In||24.02 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479058] Spectacle becomes unresponsive and has to be terminated when screen recording entire screen
https://bugs.kde.org/show_bug.cgi?id=479058 Prajna Sariputra changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||24.02 Latest Commit||https://invent.kde.org/grap ||hics/spectacle/-/commit/dcf ||2c08cdd312d1e9b4a91b03c004a ||05c378af2b --- Comment #6 from Prajna Sariputra --- Recording now works reliably for me on bleeding edge Plasma 6 compiled from source, and after doing a git bisect it appears that the commit that fixes the problem is dcf2c08cdd312d1e9b4a91b03c004a05c378af2b (recording: Do not leak node ids), I tried reverting it on top of the master and release/24.02 branches and the issue (Spectacle crashing after second recording) came back in both cases. That commit didn't make it in time for RC2, but it has been backported for 24.02 so it should be fixed by the final release. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481390] Recording H.264 doesn't work
https://bugs.kde.org/show_bug.cgi?id=481390 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #2 from Prajna Sariputra --- I have bleeding edge Plasma 6 compiled from source (so Plasma 6.1 Dev from about two days ago), and I can reproduce the issue of the Apply button not being enabled after changing the recording format, but the setting still got saved (even by just clicking Ok and not changing any other setting), and both recording a rectangular region as well as stopping it by clicking on the red recording icon on the panel works too. The H.264 recording does appear broken in my case (due to Spectacle/KPipeWire not using my GPU's hardware encoding properly), but I've already filed bug 478868 for that. Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 680M + AMD Radeon RX 6650M -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481450] New: The "Reset" and "Defaults" buttons does not work properly if either or both of the duration settings are set to custom
https://bugs.kde.org/show_bug.cgi?id=481450 Bug ID: 481450 Summary: The "Reset" and "Defaults" buttons does not work properly if either or both of the duration settings are set to custom Classification: Plasma Product: kscreenlocker Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com Target Milestone: --- Created attachment 165881 --> https://bugs.kde.org/attachment.cgi?id=165881=edit Recording demonstrating the bug SUMMARY With the updated screen locker KCM since https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/175, if I set either of the duration options to a custom value, neither the Reset nor the Default buttons appear to work visually, the comboboxes will still show the custom value. Fortunately this is just a visual bug, switching to another KCM and coming back makes the values appear as expected. STEPS TO REPRODUCE 1. Open the screen locking KCM 2. Set either the "Lock screen automatically" or "Delay before password required" times to a custom value 3. Click Defaults or Reset OBSERVED RESULT The custom value entered does not appear to be reset properly. EXPECTED RESULT The custom value should be reset. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Prajna Sariputra changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #81 from Prajna Sariputra --- Yes, Plasma 6 has it as Nate said in the comment right before yours, and as noted in the "Version Fixed In" field of the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479058] Spectacle becomes unresponsive and has to be terminated when screen recording entire screen
https://bugs.kde.org/show_bug.cgi?id=479058 --- Comment #5 from Prajna Sariputra --- Another bug report has been filed about Spectacle freezing only when a second recording is started: https://bugs.kde.org/show_bug.cgi?id=481188 Not sure if that bug should be marked as duplicate of this one or if this bug should be closed since the original description no longer describes the current situation. Also, when running Spectacle in a terminal I see these error messages appearing after the end of the first recording, might have something to do with why the second recording fails? *** pw_stream_destroy called from wrong context, check thread and locking: Not in loop *** impl_ext_end_proxy called from wrong context, check thread and locking: Not in loop 'pthread_equal(impl->thread, thread_id)' failed at ../pipewire/spa/plugins/support/loop.c:363 loop_leave() -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 216947] Notifications disappear too fast
https://bugs.kde.org/show_bug.cgi?id=216947 Prajna Sariputra changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||putr...@gmail.com --- Comment #4 from Prajna Sariputra --- With KDE Plasma 6 from git master at least (and Plasma 5.27 as well I'm pretty sure) there is a setting to change how quickly the notification popups disappear, and hovering the mouse cursor over the notification will also keep it from disappearing until either the close button is clicked or the mouse is moved away from the notification, in which case the timer until the notification disappears resets, so I think this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478638] Discover crashes after resizing
https://bugs.kde.org/show_bug.cgi?id=478638 Prajna Sariputra changed: What|Removed |Added CC||fi...@tutanota.com --- Comment #13 from Prajna Sariputra --- *** Bug 480975 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 480975] Discover 6.0 crashes when switching from "compact / mobile" view to "expanded" view
https://bugs.kde.org/show_bug.cgi?id=480975 Prajna Sariputra changed: What|Removed |Added Status|REPORTED|RESOLVED CC||putr...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Prajna Sariputra --- *** This bug has been marked as a duplicate of bug 478638 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479058] Spectacle becomes unresponsive and has to be terminated when screen recording entire screen
https://bugs.kde.org/show_bug.cgi?id=479058 --- Comment #4 from Prajna Sariputra --- Can confirm that recording always works the first time now (even full screen), and that the second time always causes Spectacle to freeze, regardless of the type. In my case I'm on Arch Linux, but with git master Plasma and Spectacle. Spectacle is at commit 74f1bbba31ac58123591343d5ab32e7b6e1ae888, KPipeWire is at commit 530cbc35edcaab0e0ca01b2dabc0adb881d7eda0 and KWin is at commit 909d83419cda17d5bd5f6d9acc4c507e6fe6b27c. KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-arch1-2 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 480931] New: Power menu only shows an option to log out on postmarketOS Plasma Mobile nightly
https://bugs.kde.org/show_bug.cgi?id=480931 Bug ID: 480931 Summary: Power menu only shows an option to log out on postmarketOS Plasma Mobile nightly Classification: Plasma Product: plasma-mobile Version: unspecified Platform: postmarketOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-mobile-bugs-n...@kde.org Reporter: putr...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY After installing the latest pmOS Plasma Mobile edge image into a microSD card, setting up the nightly repo and then upgrading, the power menu (both when accessed via quick settings and by holding the power button) now only shows an option to log out or cancel, so powering off or rebooting appears to longer be possible via the GUI. I assume this is due to https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3823, which changed the logout greeter to only show the action initially selected by the user instead of always showing all the options and just preselecting one of them. STEPS TO REPRODUCE 1. Set up postmarketOS edge (I did this on a PinePhone) 2. Upgrade to Plasma Mobile nightly packages as per https://wiki.postmarketos.org/wiki/Nightly 3. Try to reboot or shut down the device OBSERVED RESULT The shut down and reboot options are missing in the power menu. EXPECTED RESULT The shut down and reboot options should still be available in the power menu. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480435] Remote Desktop session restore does not work after xdg-desktop-portal-kde is restarted
https://bugs.kde.org/show_bug.cgi?id=480435 Prajna Sariputra changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Prajna Sariputra --- Forgot I filed a bug report for this already, oops *** This bug has been marked as a duplicate of bug 480235 *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 Prajna Sariputra changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Prajna Sariputra --- *** Bug 480435 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448234] Usage of Qt SVG renderer causes some 3rd-party app icons to be mis-rendered
https://bugs.kde.org/show_bug.cgi?id=448234 --- Comment #20 from Prajna Sariputra --- This blog post has more info on the improvements Qt 6.7 brings: https://www.qt.io/blog/qt-svg-not-so-1.2-tiny-any-more In short the goal still isn't to support the full SVG 1.1 or 2.0 standard, just for the "useful and common elements", but it does show that Qt is now open to expanding beyond the tiny SVG standard for the bits that people use in practice. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476655] Clicking on windows/desktops in the new overview/grid effect no longer works after a remote desktop/input connection is started on Wayland
https://bugs.kde.org/show_bug.cgi?id=476655 --- Comment #5 from Prajna Sariputra --- I just tested a freshly updated KDE Neon Unstable QEMU/libvirt VM, and I can reproduce this bug there too by using the KDE Connect app on the host to move the mouse in the VM. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476655] Clicking on windows/desktops in the new overview/grid effect no longer works after a remote desktop/input connection is started on Wayland
https://bugs.kde.org/show_bug.cgi?id=476655 --- Comment #4 from Prajna Sariputra --- It's still happening for me with Plasma and KDE Conmect from git master. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480410] "Remote control requested" dialog lacks some spacing
https://bugs.kde.org/show_bug.cgi?id=480410 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #2 from Prajna Sariputra --- That seems like it might be a Qt 6.7 specific issue, I also have git master stuff but with Qt 6.6.1 and the dialog looks fine for me. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480412] "Remote control requested" dialog from KDE Connect doesn't show source of the request
https://bugs.kde.org/show_bug.cgi?id=480412 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #2 from Prajna Sariputra --- The reported app name depends on how kdeconnectd is started, if it was via the autostart .desktop file then it works fine, if it's started via a DBus call (for example by running `kdeconnect-cli --refresh` after killing kdeconnectd) then no app name is shown like in the screenshot, and if it's manually run via say Konsole then the dialog will say that Konsole is making the request. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480435] Remote Desktop session restore does not work after xdg-desktop-portal-kde is restarted
https://bugs.kde.org/show_bug.cgi?id=480435 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480432] Unchecking "Allow restoring on future sessions" in RemoteDesktop does not work
https://bugs.kde.org/show_bug.cgi?id=480432 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467302] "Force virtual keyboard to be visible" function that bypasses input event filtering
https://bugs.kde.org/show_bug.cgi?id=467302 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467209] Clicking "Virtual keyboard" button doesn't make virtual keyboard show up; you have to tap it with a touchscreen
https://bugs.kde.org/show_bug.cgi?id=467209 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479445] Maliit Keyboard not working properly
https://bugs.kde.org/show_bug.cgi?id=479445 Prajna Sariputra changed: What|Removed |Added CC|putr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 362542] Does not inhibit suspend when a file transfer is in progress
https://bugs.kde.org/show_bug.cgi?id=362542 Prajna Sariputra changed: What|Removed |Added CC||ahmed@tutanota.com --- Comment #6 from Prajna Sariputra --- *** Bug 466704 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466704] Dolphin does not inhibit suspend during copying or moving files
https://bugs.kde.org/show_bug.cgi?id=466704 Prajna Sariputra changed: What|Removed |Added Resolution|--- |DUPLICATE CC||putr...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Prajna Sariputra --- *** This bug has been marked as a duplicate of bug 362542 *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] New: Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 Bug ID: 480235 Summary: Persistence in the remote desktop portal does not work across reboots Classification: Plasma Product: xdg-desktop-portal-kde Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY I tried to add support in KDE Connect's remote input plugin for the new persistence feature in v2 of the remote desktop portal protocol in https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/639. While it works if I restart the KDE Connect daemon (I just get the notification instead of the permission request dialog), the token appears to be invalidated after a reboot, so the permissions prompt appears again. If I try the same patched KDE Connect in a GNOME 45.2 Wayland session the restore token does persist across reboots, which leads me to suspect that the issue is in the KDE portal. STEPS TO REPRODUCE 1. Build KDE Connect with the aforementioned MR 2. Try to use remote input from another connected device 3. Accept the remote control permission request with persistence enabled 4. Reboot 5. Try step 2 again OBSERVED RESULT The permission dialog appears again. EXPECTED RESULT The remote control request should be granted immediately, with just a notification appearing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.6.10-arch1-1 (64-bit) Graphics Platform: Wayland XDG Desktop Portal: 1.18.2 ADDITIONAL INFORMATION https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/265 is also needed for the patched KDE Connect to work, since it only requests control of input devices and doesn't need the screens. Alternatively another app that also supports v2 of the remote desktop portal might exhibit the same issue, but I don't know of any such app at the moment. Also, as per the portal documentation (https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.RemoteDesktop.html) the restore token is supposed to be invalidated after each use and a new one issued in the Start call's response, but both the GNOME and KDE portals appear to just use the same token anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480127] How about not storing clipboard history in RAM?
https://bugs.kde.org/show_bug.cgi?id=480127 --- Comment #3 from Prajna Sariputra --- I should have clarified that the performance improvements haven't been merged yet, so you won't see the effects of that for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480127] How about not storing clipboard history in RAM?
https://bugs.kde.org/show_bug.cgi?id=480127 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- There is actually some performance improvements on the way, which when complete will allow images at least to not be fully stored in RAM, just the metadata and thumbnail: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2502 In theory I guess that system could even be extended to create "thumbnails" for long text stuff and just load that instead of the whole text and/or use some sort of compression, but then I wonder how common it is for people to copy long bits of text often enough for it to matter, like for reference I happen to have a document with like 120 pages of text and about 63000 words, and that's apparently about 700KB of data, so even if you had 100 such documents in text form sitting in your clipboard history that's just 70MB of data. Plus, trying to save RAM for text stuff might just slow down the search function, so it might not even be an improvement in the end. As for a warning about the RAM usage with larger history size limits, Konsole already has something similar with its scrollback limit setting (in the profile settings), so there is at least precedent for it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476536] New overview/grid animation does not feel as precise when using touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=476536 --- Comment #5 from Prajna Sariputra --- The issue with the desktop switching animation in the overview was noted in the merge request discussion (https://invent.kde.org/plasma/kwin/-/merge_requests/4621#note_804254), Niccolò said that the fix for that would be more complex. So, I'd say it would be better to open a new bug report to focus on that animation specifically, given the apparent difference between it and the rest of the overview/grid effect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 --- Comment #10 from Prajna Sariputra --- Spoke too soon, forgot about the fact that the order the screen sharing apps are started can change things (as I noted back in comment 2, oops), and after starting OBS, closing it and then starting Krfb the issue cropped up with Krfb again. Firefox meanwhile still seems to manage to avoid the issue somehow, in fact even after I managed to reproduce the issue with OBS and Krfb, starting a screen sharing session in Firefox and then stopping it seems to make KWin behave sanely with both OBS and Krfb again, this time in the same session, without reboots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 Prajna Sariputra changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #9 from Prajna Sariputra --- Unfortunately the issue still persists with KWin at commit 9f10d5d79fe21c63989e41c1184f895c5464ab2b from git master for me with OBS Studio, although interestingly now Krfb (23.08.4 from the Arch repos) no longer causes the problem, unlike in Plasma 5.27.10, so the situation has improved but the issue is not quite fixed yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479558] krfb-virtualmonitor causes kwin_wayland to crash
https://bugs.kde.org/show_bug.cgi?id=479558 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479445] Maliit Keyboard not working properly
https://bugs.kde.org/show_bug.cgi?id=479445 Prajna Sariputra changed: What|Removed |Added Component|general |virtual-keyboard Product|kde |kwin CC||putr...@gmail.com Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Version|unspecified |master -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 478936] Unable to bind / use the calculator key in plasma 6
https://bugs.kde.org/show_bug.cgi?id=478936 Prajna Sariputra changed: What|Removed |Added CC||seastl...@gmail.com --- Comment #2 from Prajna Sariputra --- *** Bug 478283 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 478283] Calculator key not detected on Wayland
https://bugs.kde.org/show_bug.cgi?id=478283 Prajna Sariputra changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Prajna Sariputra --- *** This bug has been marked as a duplicate of bug 478936 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 479138] Plasma 6 Beta 2 - Resizing Discover window to mobile layout causes it to crash.
https://bugs.kde.org/show_bug.cgi?id=479138 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 479058] Spectacle becomes unresponsive and has to be terminated when screen recording entire screen
https://bugs.kde.org/show_bug.cgi?id=479058 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- In my case if the first thing I do after starting Spectacle is record the whole screen then it just freezes and crashes after a second or two, but if the first thing I do is record a window or rectangular region instead then recording the whole screen works afterwards. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478951] Xwayland apps are not minimized when its entry in the task manager is clicked
https://bugs.kde.org/show_bug.cgi?id=478951 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479013] New: KDE Connect keeps asking for permission for the first time remote input is used on Wayland for each boot
https://bugs.kde.org/show_bug.cgi?id=479013 Bug ID: 479013 Summary: KDE Connect keeps asking for permission for the first time remote input is used on Wayland for each boot Classification: Applications Product: kdeconnect Version: 24.01.85 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: putr...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY On Wayland, KDE Connect uses the remote desktop XDG portal to implement the remote input functionality, however this means that the first time remote input is used for each boot the user has to be physically near the system to accept the permissions dialog that appears (or use a separate wireless input device). In the past the KDE portal implementation had a path to allow skipping the dialog for non sandboxed apps like KDE Connect, but it has been removed since https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/223, so apps have to be updated to use the new version of the remote desktop portal (https://github.com/flatpak/xdg-desktop-portal/pull/1004) to enable support for persistence. STEPS TO REPRODUCE 1. Use KDE Plasma and KDE Connect on Wayland 2. Try the remote input function from a remote device OBSERVED RESULT On every boot KDE Connect asks for permission to control the system. EXPECTED RESULT KDE Connect should only request permission once, and then it should be able to keep the permission if the user allowed it. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478948] Panel no longer defloats correctly
https://bugs.kde.org/show_bug.cgi?id=478948 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478948] New: Panel no longer defloats correctly
https://bugs.kde.org/show_bug.cgi?id=478948 Bug ID: 478948 Summary: Panel no longer defloats correctly Classification: Plasma Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 164408 --> https://bugs.kde.org/attachment.cgi?id=164408=edit Recording of how a bottom panel defloats now SUMMARY With latest git master everything, the panel no longer defloats correctly on my system. A bottom panel just moves towards the bottom left, a right panel moves towards the top right, and a top panel as well as a left panel moves towards the top left. A git bisect returns commit 6feb67b9fd1148634c022a87062c20a7955c1ac9 (Let the compositor size space filling panels) in plasma-workspace as the first bad commit, and reverting that commit on top of master fixes the issue for me. STEPS TO REPRODUCE 1. Update to latest git master 2. Have a floating panel (at least bottom or top) 3. Open and maximise a window or move it so it touches the panel OBSERVED RESULT The panel does not defloat correctly. EXPECTED RESULT The panel defloats correctly. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 478868] KPipeWire's H.264 encoding outputs broken video on an integrated + discrete AMD GPU system
https://bugs.kde.org/show_bug.cgi?id=478868 --- Comment #1 from Prajna Sariputra --- Created attachment 164357 --> https://bugs.kde.org/attachment.cgi?id=164357=edit Recording output if KPipeWire is patched to use the integrated GPU With the integrated GPU I can make out bits of Konsole as well as my wallpaper in the recording, all I'm doing in the recording is switching virtual desktops. Also, the way I made KPipeWire use the integrated GPU is just by making it select the second device it sees instead of the first one, so definitely a hack and not upstreamable. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 478868] New: KPipeWire's H.264 encoding outputs broken video on an integrated + discrete AMD GPU system
https://bugs.kde.org/show_bug.cgi?id=478868 Bug ID: 478868 Summary: KPipeWire's H.264 encoding outputs broken video on an integrated + discrete AMD GPU system Classification: Frameworks and Libraries Product: KPipeWire Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: putr...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 164356 --> https://bugs.kde.org/attachment.cgi?id=164356=edit Recording output if H264 is selected in Spectacle SUMMARY My laptop has both an integrated AMD GPU as well as a discrete AMD GPU, and the display is connected to the integrated GPU. Both GPUs support VAAPI, and use the same driver, however the discrete GPU is listed first in lspci, and the discrete GPU is both /dev/dri/card1 and /dev/dri/renderD128, while the integrated/primary GPU is /dev/dri/card2 as well as /dev/dri/renderD129. This means that KPipeWire will see the discrete GPU first and use that for hardware encoding, and not only does that result in higher power usage as well as slowing down startup of apps using KPipeWire to record video (like Spectacle, see bug 476866), it also seems to cause the video output to be corrupt, with nothing from the original source visible in the recording. If I modify KPipeWire's code to instead select the integrated GPU, the output recording is slightly better in that I can make out some bits of the original source, but it is still unusably corrupt. I am filing this under KPipeWire since krdp is also affected when I tried it (the video on the client looks the same as the Spectacle recordings), and in that case it is a bigger problem since krdp only supports H.264. STEPS TO REPRODUCE 1. Have a laptop with both an AMD integrated GPU and an AMD discrete GPU 2. Open Spectacle 3. Change its output format to H.264 4. Try to record the screen/region OBSERVED RESULT The output recording appears corrupt. EXPECTED RESULT The output recording matches what was recorded. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 680M + AMD Radeon RX 6650M Graphics Driver: Mesa 23.3.1 ADDITIONAL INFORMATION When recording with either GPU, Spectacle shows this message in its terminal output: [h264_vaapi @ 0x7fc31824cac0] Driver does not support some wanted packed headers (wanted 0xd, found 0x1). When recording with the integrated GPU, additional messages like these appear: EE ../mesa-23.3.1/src/gallium/drivers/radeonsi/radeon_vcn_enc_1_2.c:1224 radeon_enc_encode_params UVD - DCC surfaces not supported. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup, slowing it down and using extra energy
https://bugs.kde.org/show_bug.cgi?id=476866 --- Comment #7 from Prajna Sariputra --- Okay, I just found the bit of code that decides which device to use for hardware encoding (https://invent.kde.org/plasma/kpipewire/-/blob/master/src/vaapiutils.cpp?ref_type=heads#L34), KPipeWire just gets the list of DRM devices and picks the first render device from the list, that says it supports H.264 VAAPI, which in my case is /dev/dri/renderD128, the discrete/secondary GPU. So, I tried adding a hack to make the code pick the second device it finds, which is /dev/dri/renderD129, the integrated GPU, and recompiled KPipeWire (do I also need to recompile Spectacle or anything else?). With that, Spectacle starts noticeably quicker, and recording also starts as soon as I click the button, even when VP9 is selected as the format, whereas before the recording only starts like 3s after I click the button. However, it turns out that even when using the integrated GPU for encoding the video output is still corrupted, but it's a different sort of corrupt, with the discrete GPU I can make nothing out of the source at all, but with the integrated GPU I can see bits of the source. I'll file a new bug report for the corruption with more details. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup, slowing it down and using extra energy
https://bugs.kde.org/show_bug.cgi?id=476866 --- Comment #6 from Prajna Sariputra --- Something I forgot to mention here is that with the H.264 format selected the video output is also garbled as a result. I just assumed that it's just because using the discrete/non-primary GPU for encoding has some differences compared to using the integrated/primary GPU for encoding, and it's also not a big deal for Spectacle since it defaults to VP9 encoding (which no AMD or NVIDIA GPU supports anyway), but I gave krdp a try recently and the output there is broken too, and unlike Spectacle it only supports H.264 due to the RDP protocol, so it's a bigger problem there since it means I can't use it at all. So, am I correct in the assumption that the best way to make sure the video output works is to not pick the secondary GPU, or should I file a separate bug report for the garbled video output due to the multi GPU setup? For what it's worth it's definitely not impossible to use the discrete/secondary GPU for hardware VAAPI encoding, OBS can do it for example. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478753] New: No sensors are functional in both the system monitor app and widgets
https://bugs.kde.org/show_bug.cgi?id=478753 Bug ID: 478753 Summary: No sensors are functional in both the system monitor app and widgets Classification: Applications Product: plasma-systemmonitor Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: putr...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 164304 --> https://bugs.kde.org/attachment.cgi?id=164304=edit Screenshot of the broken system monitor and the empty list of sensors in a KDE Neon Unstable VM SUMMARY After updating to today's git master, the system monitor app only shows blank circles, boxes and graphs, and system monitor widgets just show the configure button. If edit mode is enabled in the app's edit mode, it says "This page is missing some sensors and will not display correctly." at the top, and the list of available sensors is completely empty (so not even things like CPU usage appear). Resetting the system monitor app's settings by deleting `~/.config/plasma-systemmonitorrc` does not fix the problem. I am getting this issue on both my Arch Linux + kdesrc-build setup as well as in a KDE Neon Unstable VM (installed with an older ISO but updated today). STEPS TO REPRODUCE 1. Update to the latest git master 2. Open the System Monitor app OBSERVED RESULT The only thing working properly is the application and process list views. EXPECTED RESULT All the sensors like CPU, RAM and so on should be working. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.6.7-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION In the system logs I see ksystemstats reporting warnings like `kf.i18n: KLocalizedString: Domain is not set for this string, translation will not work. Please see https://api.kde.org/frameworks/ki18n/html/prg_guide.html msgid: "Fan %1" msgid_plural: "" msgctxt: "@title %1 is a number"`, but no other relevant warnings/errors that I can see. On my Arch system the plasma-ksystemstats service gets killed by systemd after some time due to the start operation timing out, but that doesn't happen in the Neon Unstable VM. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478753] No sensors are functional in both the system monitor app and widgets
https://bugs.kde.org/show_bug.cgi?id=478753 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478741] ksystemstats daemon.cpp:32:10: fatal error: 'ksystemstatsadaptor.h' file not found
https://bugs.kde.org/show_bug.cgi?id=478741 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- For what it's worth starting from a previously working ksystemstats and updating to latest git master still compiles, but no sensors at all are working. Clearing the build folder for ksystemstats (and libksysguard, not sure if that matters) resulted in the same ksystemstatsadaptor.h file not found error. I'm on Arch Linux, using kdesrc-build to compile Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478746] Can no longer drag entire desktops in desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=478746 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 478283] Calculator key not detected on Wayland
https://bugs.kde.org/show_bug.cgi?id=478283 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- I have an HP Omen 16-n laptop, which also has a calculator button on the keyboard, and it too no longer works in Plasma 6 (from kdesrc-build, so git master). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466948] A way to show the virtual keyboard manually, without necessarily using a touch device
https://bugs.kde.org/show_bug.cgi?id=466948 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478321] Trackpad gesture to change desktops skips more than one desktop
https://bugs.kde.org/show_bug.cgi?id=478321 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Version|unspecified |5.90.0 Product|kde |kwin Component|general |Gestures -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478124] White background in the system monitor
https://bugs.kde.org/show_bug.cgi?id=478124 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478137] Desktop grid is not available as an option for screen edges/corners
https://bugs.kde.org/show_bug.cgi?id=478137 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 --- Comment #1 from Prajna Sariputra --- *being effectively equivalent to present windows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478137] New: Desktop grid is not available as an option for screen edges/corners
https://bugs.kde.org/show_bug.cgi?id=478137 Bug ID: 478137 Summary: Desktop grid is not available as an option for screen edges/corners Classification: Plasma Product: kwin Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: putr...@gmail.com Target Milestone: --- SUMMARY Currently, the desktop grid is not available as a possible action/effect to trigger when touching a screen edge or corner. In Plasma 5.27 this wasn't a big deal since the overview effect is in the list and allows moving windows between desktops as well as switching to desktops, but with Plasma 6 the overview effect is far less useful for people with more than one row and column of desktops (being effectively equivalent to present desktops in that case). As per bug 477942 the desktop grid effect is explicitly recommended too for those with such virtual desktop setups. A mitigating factor is that it's still possible to access the grid by triggering the edge/corner twice if the overview is enabled for those, but having to flick the cursor twice seems like a problem when it comes to avoiding carpal tunnel syndrome and the like. STEPS TO REPRODUCE 1. Open the screen edges KCM 2. Try to assign the desktop grid to one of the screen edges or corners OBSERVED RESULT The desktop grid is not present as one of the options. EXPECTED RESULT The desktop grid can be selected for the edge/corner. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION The list of options for each screen edge/corner is getting rather unwieldy, so maybe adding yet another option to it isn't a good idea without redesigning it somehow. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477864] Pressing the Print Screen button causes too many Spectacle windows, which eventually causes KWin to crash
https://bugs.kde.org/show_bug.cgi?id=477864 Prajna Sariputra changed: What|Removed |Added CC||k...@david-redondo.de, ||putr...@gmail.com Version|unspecified |git-master Assignee|unassigned-b...@kde.org |noaha...@gmail.com Product|kde |Spectacle Component|general |General --- Comment #2 from Prajna Sariputra --- After following the given reproduction steps I can also get KWin to crash if I hold down the print screen key for a bit. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468657] Aborted due to failure (While pulling ... from remote flathub: opcode set-read-source: Opening content object ...: Opening content object ...: Couldn't find file object '...')
https://bugs.kde.org/show_bug.cgi?id=468657 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 476532] Spacebar doesn't always pause/play anymore
https://bugs.kde.org/show_bug.cgi?id=476532 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478079] Plasma System Monitor reporting incorrect CPU usage for applications
https://bugs.kde.org/show_bug.cgi?id=478079 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478083] The transparency of the panel changes abruptly when playing the "overview" or "desktop grid" effect
https://bugs.kde.org/show_bug.cgi?id=478083 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- Specifically it's the blur effect that's not getting applied in time and/or smoothly, disabling it works around the bug (although naturally it doesn't look as good). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477961] Cannot save as JPEG after updating to KDE 6 beta
https://bugs.kde.org/show_bug.cgi?id=477961 --- Comment #6 from Prajna Sariputra --- Oh, so it seems that the thing adding .jfif in my case to ~/.local/share/mime/globs2 is `~/local/share/mime/packages/x-wine-extension-jfif.xml`, deleting that and running `update-mime-database ~/.local/share/mime` fixes the problem for me. So, I guess something ends up using only the user's database instead of overlaying it on top of the system's database? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477961] Cannot save as JPEG after updating to KDE 6 beta
https://bugs.kde.org/show_bug.cgi?id=477961 --- Comment #5 from Prajna Sariputra --- The `grep image/jpeg /usr/share/mime/globs2` command returns: 50:image/jpeg:*.jfif 50:image/jpeg:*.jpeg 50:image/jpeg:*.jpe 50:image/jpeg:*.jpg The `grep image/jpeg ~/.local/share/mime/globs2` command returns: 50:image/jpeg:*.jfif I'm also on Arch Linux for what it's worth. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478032] Focus doesn't follow mouse over window title bars under Wayland.
https://bugs.kde.org/show_bug.cgi?id=478032 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 477976] system-monitor incorrectly reports CPU usage as 0% when it is close to 100%
https://bugs.kde.org/show_bug.cgi?id=477976 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477961] Cannot save as JPEG after updating to KDE 6 beta
https://bugs.kde.org/show_bug.cgi?id=477961 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- This doesn't seem to be a problem specific to Spectacle, I tried using Kolourpaint (from kdesrc-build) to save to a JPEG file and it too showed the same behaviour with showing JFIF as the file extension, and naturally saving doesn't actually work like that either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477912] Cpu/case fan speed sensors are not available anymore
https://bugs.kde.org/show_bug.cgi?id=477912 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477942] The overview effect is useless with gridded desktops
https://bugs.kde.org/show_bug.cgi?id=477942 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 477902] Breeze themed cursor changes to a generic one when hovering over Qt5 apps, and also some other apps.
https://bugs.kde.org/show_bug.cgi?id=477902 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #2 from Prajna Sariputra --- I'm also experiencing this with git master Plasma 6 Wayland from kdesrc-build on top of Arch Linux, and for me the cursor size for Qt5 apps is also wrong. In my case either the instructions in https://wiki.archlinux.org/title/Cursor_themes#XDG_specification or setting `XCURSOR_THEME=breeze_cursors` works around the problem, and setting `XCURSOR_SIZE` works around the cursor size problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387455] Column view in Dolphin
https://bugs.kde.org/show_bug.cgi?id=387455 --- Comment #8 from Prajna Sariputra --- Well as usual the problem is that no one willing and able to do it has stepped up to the plate, and as mentioned before it's not exactly trivial to do, as per Nate from several years ago in https://bugs.kde.org/show_bug.cgi?id=290747#c45: > For everybody who wants this feature back: we understand, and in fact agree > with you! Column view is sorely missed. The problem is technical, not > ideological. This part of Dolphin was rewritten 5 years ago in such a manner > that made Column view unmaintainable/unimplementable. That's not an > insurmountable barrier to overcome, but overcome it does need to be if we are > to get a new column view. Patches are always welcome! If you really want someone to get to this feature and are willing to chip in monetarily for it then there is the sponsored work section in the KDE forums: https://discuss.kde.org/c/development/sponsored-work/31 That said, I do wonder if the technical situation has changed at all these days, since that comment was from 2017. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477839] Cube effect is not working
https://bugs.kde.org/show_bug.cgi?id=477839 --- Comment #5 from Prajna Sariputra --- I have both the `plasma-meta` and `kde-applications-meta` packages installed from the Arch stable repos (so I have most if not all of Qt5 KDE Plasma and Gear), and not a single component is reported as depending on qt5-quick3d, even optionally. The kdeplasma-addons package in Arch's kde-unstable repo (which is where the cube effect resides) also does not mention qt6-quick3d as a dependency (optional or otherwise), and I also don't see it mentioned as a new dependency in the Plasma 6 release notes (https://community.kde.org/Plasma/Plasma_6.0_Release_notes). So, the cube effect is likely the first instance of KDE software requiring QtQuick3D. Do newly required Qt components like that count as a "new dependency" that should be mentioned in the release notes, or are packagers just supposed to notice that it's needed when compiling the package? I thought it was addressed already early on as per this comment in the MR that added the effect: https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/188#note_480691 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477839] Cube effect is not working
https://bugs.kde.org/show_bug.cgi?id=477839 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #3 from Prajna Sariputra --- Does any error appear in the system logs when the shortcut is invoked? Note that QtQuick3D needs to be installed for the effect to work. For what it's worth it works fine on my Plasma 6 kdesrc-build setup on top of Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477796] No way to get to the KDE Connect main window from the tray icon
https://bugs.kde.org/show_bug.cgi?id=477796 Prajna Sariputra changed: What|Removed |Added Ever confirmed|0 |1 CC||putr...@gmail.com Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #2 from Prajna Sariputra --- Bug 476389 is about the plasmoid/tray icon not appearing at all in Plasma 6, this one is about the plasmoid not having an option/button to open the app (the `kdeconnect-app` executable, which has some additional features not available in the plasmoid) instead of just the KCM/settings window, which is still the case for now. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477496] Konsole "New tab" command from the panel opens a new window
https://bugs.kde.org/show_bug.cgi?id=477496 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- I'm seeing this with Konsole 23.08.3 from the Arch Linux repos as well, so this seems to be a relatively old problem. Enabling the "Run all Konsole windows in a single process" option in Konsole's settings makes the problem go away though. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 475794] Pre-configured System Monitor widgets added to desktop appear as generic "System Monitor Sensor" widgets
https://bugs.kde.org/show_bug.cgi?id=475794 Prajna Sariputra changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- *** This bug has been marked as a duplicate of bug 47 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476666] Widgets based on System Monitor Sensor are all broken out of the box
https://bugs.kde.org/show_bug.cgi?id=47 Prajna Sariputra changed: What|Removed |Added CC||er...@armbruster-online.de --- Comment #4 from Prajna Sariputra --- *** Bug 475794 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476508] [kdesrc-build Plasma 6] Screen locker doesn't show the password entry prompt
https://bugs.kde.org/show_bug.cgi?id=476508 Prajna Sariputra changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #6 from Prajna Sariputra --- It's been working for me ever since I copied over the PAM config from GNOME, so I guess this isn't really a problem assuming distros sort it out properly when they package Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476389] Missing KDE Connect icon in System Tray
https://bugs.kde.org/show_bug.cgi?id=476389 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476814] Clock widget time zones button can't open specific systemsettings page
https://bugs.kde.org/show_bug.cgi?id=476814 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- I was able to reproduce this in my Neon Unstable VM, but the problem went away after an update (if updating via Discover or running `pkcon update` doesn't work try running `sudo apt dist-upgrade` instead). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476897] The name org.kde.spectacle was not provided by any .service files
https://bugs.kde.org/show_bug.cgi?id=476897 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #1 from Prajna Sariputra --- It seems that Spectacle's D-Bus service name has changed from org.kde.Spectacle to org.kde.spectacle, with a difference in case. This should not be a problem once Plasma 6 is properly released and packaged by distros, and for a dev setup you can either run the `~/kde/build/plasma-workspace/login-sessions/install-sessions.sh` script (if you've done this already it needs to be rerun if new D-Bus stuff is added) or copy the `~/kde/usr/share/dbus-1/services/org.kde.spectacle.service` file to the `~/.local/share/dbus-1/services` folder if you want to avoid messing with system files. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup, slowing it down and using extra energy
https://bugs.kde.org/show_bug.cgi?id=476866 --- Comment #5 from Prajna Sariputra --- To clarify, that delay for vainfo only happens with --display drm, with the x11 and wayland display options it's pretty much instant. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup, slowing it down and using extra energy
https://bugs.kde.org/show_bug.cgi?id=476866 --- Comment #3 from Prajna Sariputra --- For what it's worth vainfo has 3 options for the --display command line option it has, which are wayland, x11 and drm. The wayland (default) and x11 options both return the integrated GPU, but the drm option returns the discrete GPU (and also has that same delay where the discrete GPU needs to wake up first). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup and uses it for recording
https://bugs.kde.org/show_bug.cgi?id=476866 --- Comment #1 from Prajna Sariputra --- By "above mentioned quirk" in the reproduce steps I meant the thing about the discrete GPU coming before the integrated one in the additional information section, oops. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] Spectacle turns on the discrete GPU on a multi-GPU laptop on startup and uses it for recording
https://bugs.kde.org/show_bug.cgi?id=476866 Prajna Sariputra changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476866] New: Spectacle turns on the discrete GPU on a multi-GPU laptop on startup and uses it for recording
https://bugs.kde.org/show_bug.cgi?id=476866 Bug ID: 476866 Summary: Spectacle turns on the discrete GPU on a multi-GPU laptop on startup and uses it for recording Classification: Applications Product: Spectacle Version: git-master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: putr...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY I noticed that Spectacle from kdesrc-build starts significantly slower than 23.08.3 from the Arch repos. Looking at the terminal output and system logs, the difference appears to be that Spectacle now turns on the discrete GPU of my laptop on startup, which takes a couple of seconds if it was inactive previously. If I make sure that the discrete GPU is on already, then Spectacle starts about as fast as it did in 23.08.3. In addition to slowing down startup, it uses more power as well, not only because the discrete GPU would be woken up unnecessarily if all I wanted was to take a screenshot, but also because if I were to pick H.264 for the hardware encoding support the discrete GPU ends up getting used instead of the integrated one. STEPS TO REPRODUCE 1. Have a laptop with switchable graphics (possibly with the above mentioned quirk?) 2. Start Spectacle OBSERVED RESULT It starts slower than with 23.08.3, unless I turn on the discrete GPU first by running glxgears or whatever on it. Screen recording with the H.264 codec also uses the discrete GPU instead of the integrated one. EXPECTED RESULT Spectacle starts about as fast as it did with 23.08.3, and uses the integrated GPU for encoding if H.264 is selected. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.81.0 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.6.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon 680M + AMD Radeon RX 6650M Laptop Model: HP Omen 16-n (n0067AX) ADDITIONAL INFORMATION My system is a bit odd in that in `lspci` the discrete GPU comes before the integrated one (the former is 03:00.0, while the latter is 09:00.0), and /dev/dri/card0 and /dev/dri/renderD128 also both point to the discrete GPU rather than the integrated one. Just about everything else appears to know which one the integrated GPU is and uses that by default though (including vainfo). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Prajna Sariputra changed: What|Removed |Added CC|putr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476533] [kdesrc-build Plasma 6] Pressing Esc no longer turns off the screen when locked
https://bugs.kde.org/show_bug.cgi?id=476533 --- Comment #4 from Prajna Sariputra --- I filed https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/176 to get rid of the evidently broken connect call and just turn off the screen directly. No idea what would happen on a system without DPMS support though. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 462824] Built-from-source sessions installed via install-sessions.sh still use host system's KAuth helpers and DBus services
https://bugs.kde.org/show_bug.cgi?id=462824 --- Comment #3 from Prajna Sariputra --- In the upstream dbus-daemon session.conf file, `` is placed above all of the `session.d` type stuff, so the `/opt/kde-dbus-scripts/services` part that is added by `install-sessions.sh` will be below the standard (system and user) directories. This means that for a system that has KDE Plasma installed both through the distro as well as kdesrc-build dbus-daemon will pick the version installed through the distro rather than the one provided by kdesrc-build, as per the documentation (https://dbus.freedesktop.org/doc/dbus-daemon.1.html). So, I wonder if upstream D-Bus could be convinced to change the defaults to also allow the additional config files to add service directories above the standard ones, especially for the session bus given that anything malicious can just drop stuff in ~/.local/share/dbus-1/services without needing any special privileges like what I'm doing already. They do clearly intend for the local config files to be able to override the defaults anyway, so I guess it's possible that they just didn't think of our use case when they wrote those defaults. On the other hand, the default system bus service directories are all under /usr or /lib, which would be protected for immutable systems, so getting upstream to allow us to override those would probably be more of an uphill battle, and if that isn't resolved then we'd still need a proper solution like the linked 1715 MR. Notably the KAuth helpers fall into the system services category (and in fact all but one of the system services I see in my kdesrc-build setup are KAuth stuff). But then again, if just fixing the problem for the session bus/services would be an improvement Jade seems to have another possible solution in the linked MR, which is to run the D-Bus session instance with a special config file that includes but also overrides the system defaults, including the directories problem. I might bring it up with upstream D-Bus at some point, unless someone can point out any glaring problems with that proposal which I missed. -- You are receiving this mail because: You are watching all bug changes.
