[plasmashell] [Bug 482222] When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave
https://bugs.kde.org/show_bug.cgi?id=48 --- Comment #4 from Naxdy --- Just as an FYI: At least the "selection rectangle being drawn indefinitely" bug seems to have been fixed in 6.0.3. The only bug that I still experience is edit mode being activated randomly when performing multi-finger touch gestures. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 --- Comment #8 from Naxdy --- It varies. NixOS uses the XDG_DATA_DIRS env variable to specify where to look for "stuff". On my system, this evaluates to a rather long list of paths. Notable inclusions are these two: /etc/profiles/per-user/naxdy/share and /run/current-system/sw/share These two house symlinks to files from packages that are installed for my user, and system wide respectively. As for Spectacle's desktop file, a symlink is placed in /run/current-system/sw/share/applications/org.kde.spectacle.desktop (since it's installed system-wide), but the actual path of the desktop file is /nix/store/pxwfzb8l76scjk7pcxi69ncxypbij0d3-spectacle-24.02.1/share/applications/org.kde.spectacle.desktop The actual path is changing very often, hence the symlink to /run/current-system/... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 --- Comment #6 from Naxdy --- Additional info: When attempting to delete an application from System Settings' shortcuts page, the "global shortcuts service" dies, and I am left with the following in my journal: Mar 29 10:23:24 nxwiwin systemsettings[6641]: org.kde.kcm_keys: "Error while calling cleanUp of componentorg.kde.spectacle.desktop" Mar 29 10:23:24 nxwiwin systemsettings[6641]: org.kde.kcm_keys: "org.freedesktop.DBus.Error.UnknownObject" "No such object path '/component/org_kde_spectacle_desktop'" (Wayland FYI) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682
--- Comment #5 from Naxdy ---
I've been able to confirm that simply commenting out this line (
https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/47/diffs?view=inline#014186ddf2dd1aa75709115400e25e06ba6e2d47_260_262
) fixes the issues on NixOS. Both shortcuts resetting and the glitchy behavior
of duplicate entries being present.
It seems that either component->uniqueName() is not correctly resolving to the
.desktop file's name, or that
QStandardPaths::locate(QStandardPaths::GenericDataLocation,
QLatin1String("kglobalaccel/") + component->uniqueName()).isEmpty()
is not looking in the right place for desktop files.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Naxdy changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Naxdy --- This happens regardless of the contents of ~/.config/kglobalshortcutsrc Before my last reproduction, I nuked that file completely and had it be regenerated by the system, same result. Also reproduced it on a system that was completely clean, same result. (also NixOS FYI) FWIW: aloisw from the NixOS Matrix suspects this MR to be the likely culprit: https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/47 I'm inclined to agree, since on NixOS, the actual location of .desktop files is ever changing, so I don't think this logic can be safely applied here. I think the most sensible thing in this situation would be for NixOS to manually patch out this behavior to make it fit the distro's needs, but what is your opinion? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] New: Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Bug ID: 484682 Summary: Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically Classification: Applications Product: systemsettings Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: k...@david-redondo.de Target Milestone: --- SUMMARY >From 6.0.2 -> 6.0.3, global shortcut functionality has more or less broken down on my systems, at least when it comes to configuring them. I noticed that, at least for Spectacle, the shortcuts are reset to their factory defaults upon every single sign in. Additionally, modifying a shortcut may (or may not) lead to two Spectacles appearing in system settings (see attachment). STEPS TO REPRODUCE 1. Log in to Plasma 6.0.3 session (Wayland) 2. Open System Settings 3. Navigate to Input & Output -> Keyboard -> Shortcuts 4. Select Spectacle 5. Choose a new custom shortcut for "Capture Rectangular Region" (I used Meta+Shift+S and reassigned the default shortcut, but I've observed the same behavior with different combinations) 6. Apply 7. Attempt to use the newly (re-)defined shortcut immediately. OBSERVED RESULT The (re-)defined shortcut may or may not work. Signing out and signing in again sees all shortcuts reset to factory default. After relogging and opening System Settings shortcuts, there may be (or may not be) two entries for Spectacle present. EXPECTED RESULT The (re-)defined shortcut is assigned immediately, and continues to function between sessions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION This could be an upstream bug in NixOS, well at least it feels like the sort of thing that could be introduced there, but I couldn't see any significant changes from the nixpkgs side of things. Would be great if someone on a different distro could confirm this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482035] [6.0] Scrolling is done at a lower framerate than the monitor's
https://bugs.kde.org/show_bug.cgi?id=482035 --- Comment #6 from Naxdy --- Interestingly, my wife (same mouse) doesn't have this issue, at least not to the same extent (it's still present, but weaker). Could be monitor related perhaps? She's on a 2560x1080 monitor @144Hz, I'm on a 7680x2160 monitor @120Hz, both her and me are at 100% scaling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 --- Comment #23 from Naxdy --- For those still having this issue and waiting for a fix, you can work around this under Wayland, by manually creating a window rule for KWin. To do this, open up System Settings, then navigate to Window Management -> Window Rules and click on "Add New". For description, enter anything you want, like "clipboard workaround". For "Window class (application)" put "plasmashell org.kde.plasmashell" (exactly like this, without quotes), and select "Exact Match". Leave "Window types" as "Normal Window". Then, at the bottom click on "Add Property". Search for "Initial placement" and set this to "Force" and "Under Mouse". This will cause all windows spawned by plasmashell to appear under your mouse cursor, this includes the clipboard, but also any "configure" windows you might open, e.g. by clicking to configure a widget. Remember to remove this rule whenever the issue is fixed on KDE side though (unless you're fine with any plasmashell window appearing under your cursor, which you very well might be). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484252] Emoji Selector is incredibly laggy
https://bugs.kde.org/show_bug.cgi?id=484252 --- Comment #3 from Naxdy --- Saw it on the upstream report, happy to hear it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484252] New: Emoji Selector is incredibly laggy
https://bugs.kde.org/show_bug.cgi?id=484252 Bug ID: 484252 Summary: Emoji Selector is incredibly laggy Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net Target Milestone: 1.0 SUMMARY Since the port to qt6, the emoji selector UI has become incredibly laggy when resizing the window or searching, making the app very frustrating to use. STEPS TO REPRODUCE 1. Open emoji selector 2. Resize the window, or type to search for an emoji OBSERVED RESULT The UI, while functional, is notably slow to respond to user input EXPECTED RESULT The UI responds to user-input in real time SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 --- Comment #22 from Naxdy --- Pretty sure it was meant to say 24.02.1, went ahead and changed it. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 Naxdy changed: What|Removed |Added Version Fixed In|24.0.1 |24.02.1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482035] [6.0] Scrolling is done at a lower framerate than the monitor's
https://bugs.kde.org/show_bug.cgi?id=482035 --- Comment #5 from Naxdy --- Here's my mouse output from lsusb: Bus 003 Device 002: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 [unknown] bDeviceSubClass 0 [unknown] bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x046d Logitech, Inc. idProduct 0xc08b G502 SE HERO Gaming Mouse bcdDevice 27.03 iManufacturer 1 Logitech iProduct2 G502 HERO SE iSerial 3 0A89324E3937 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x003b bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 U127.03_B0010 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 67 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 [unknown] bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 151 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0014 1x 20 bytes bInterval 1 Device Status: 0x (Bus Powered) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 --- Comment #14 from Naxdy --- Does there already exist a bug report for the present windows effect then, or should I open a separate one for that? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482035] [6.0] Scrolling is done at a lower framerate than the monitor's
https://bugs.kde.org/show_bug.cgi?id=482035 --- Comment #3 from Naxdy --- Sadly I don't have a way to measure it, but I was able to capture the behavior on video. The file is too large to be uploaded here, so I've put it on my cloud: https://cloud.polskalemon.com/s/DkFnPSdPxT79Dk5 Note that, obviously, this only makes sense to watch on a 120Hz (or more) monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 Naxdy changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from Naxdy --- If my caveman eye is to be trusted, I'd say the overview effect now plays at (or very close to) my monitor's actual refresh rate (120Hz). However, the present windows effect still looks a little sluggish to me. I'd say maybe around 80-90 fps? It's hard to say, since the frame counter happily reports 120Hz, even though that's very obviously not what's being displayed, weird. It's definitely improved though, I'll say that much. As for any other places, these are the two effects I use most. I haven't noticed it on any other ones (e.g. switching desktops with Meta+Ctrl+Right/Left is perfectly smooth at 120Hz). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] All windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #53 from Naxdy --- A live USB should be sufficient for this I think, no? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] All windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #51 from Naxdy --- Honestly, I'm not sure. The issue I've had disappeared with 6.0.0. We'd need more people that can reproduce it to say for sure. Does it also happen for you on a clean install? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] All windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #49 from Naxdy --- @eifr, if you have any unreachable windows, you can right-click them in your task manager -> more -> move, and they will be glued to your mouse cursor. Note that this doesn't work for grouped windows (you'll need to ungroup them first) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 --- Comment #19 from Naxdy --- Cherrypicked 1b309ee3d56f1aaed08d636b20490d9af10f21c1 into my installation and it does indeed solve the problem. Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482037] (CRASH) Unable to delete incidents
https://bugs.kde.org/show_bug.cgi?id=482037 Naxdy changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Naxdy --- Not a bug anymore since 6.0.1, so I'm guessing it was some frameworks / library issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 --- Comment #7 from Naxdy --- Actually, scratch that. The behavior *did* change, in that the FPS counter now doesn't drop to around 60ish anymore. However, the animations still play at a notably lower frame rate than everything else (e.g. moving windows manually). I wonder if this could be related to Bug 482035 ? Could be a Qt bug perhaps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 Naxdy changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Naxdy --- Same for me, same animations are still affected. Behavior doesn't seem to have changed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479347] Allow setting notification sounds on a per-application basis for apps that don't use per-event notification settings
https://bugs.kde.org/show_bug.cgi?id=479347 --- Comment #2 from Naxdy --- Yeah, that's the idea. Cool, I'll have a look whenever I have the time! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 --- Comment #4 from Naxdy --- As discussed on Matrix, this issue seems to require an external monitor (=the sole monitor?) to power off fully (=become disconnected) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 Naxdy changed: What|Removed |Added Summary|Context menu (when |Context menu (when |right-clicking on the |right-clicking on the |desktop) appears in a |desktop) appears in a |separate window after |separate window after |monitor restart |external monitor restart -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482287] Spectacle screen recording region outline is offset from selected area in the presence of a panel on the left or on top
https://bugs.kde.org/show_bug.cgi?id=482287 Naxdy changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Naxdy --- Can confirm with top panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459774] Make "resident" notifications the default.
https://bugs.kde.org/show_bug.cgi?id=459774 Naxdy changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #19 from Naxdy --- See https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2178 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Naxdy changed: What|Removed |Added Version|5.93.0 |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 --- Comment #10 from Naxdy --- Don't know about the others, but I for one haven't touched X11 since 5.27 ¯\_(ツ)_/¯ -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482407] New: When using a top panel, spectacle's screen recording outline is offset to the bottom and visible in the recording
https://bugs.kde.org/show_bug.cgi?id=482407 Bug ID: 482407 Summary: When using a top panel, spectacle's screen recording outline is offset to the bottom and visible in the recording Classification: Applications Product: Spectacle Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: xna...@hydra-development.net CC: k...@david-redondo.de Target Milestone: --- Created attachment 166400 --> https://bugs.kde.org/attachment.cgi?id=166400=edit Demonstration SUMMARY When using a top panel, spectacle's screen recording outline is offset to the bottom and visible in the recording STEPS TO REPRODUCE 1. Add a top panel (fixed) 2. Record in rectangular region mode using spectacle OBSERVED RESULT The dotted line is offset to the bottom when the recording starts, and is visible in the recording. EXPECTED RESULT The dotted line stays in place where the initial rectangle was drawn and doesn't show up in the recording SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Naxdy changed: What|Removed |Added Version|5.93.0 |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482390] Clipboard no longer displays application name
https://bugs.kde.org/show_bug.cgi?id=482390 Naxdy changed: What|Removed |Added Platform|Other |NixOS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482390] Clipboard no longer displays application name
https://bugs.kde.org/show_bug.cgi?id=482390 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482390] New: Clipboard no longer displays application name
https://bugs.kde.org/show_bug.cgi?id=482390 Bug ID: 482390 Summary: Clipboard no longer displays application name Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net Target Milestone: 1.0 SUMMARY The clipboard history popup no longer displays its application name. STEPS TO REPRODUCE 1. Open clipboard history using Meta+V OBSERVED RESULT The text at the top of the window reads "- Clipboard Items" EXPECTED RESULT The text at the top of the window reads "%1 - Clipboard Items" where %1 is the application display name. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION See https://invent.kde.org/plasma/plasma-workspace/-/blob/master/klipper/klipperpopup.cpp?ref_type=heads#L108 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482389] New: Clipboard shows an unreasonable amount of characters in a single line
https://bugs.kde.org/show_bug.cgi?id=482389 Bug ID: 482389 Summary: Clipboard shows an unreasonable amount of characters in a single line Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net Target Milestone: 1.0 Created attachment 166399 --> https://bugs.kde.org/attachment.cgi?id=166399=edit Screenshot of the history popup SUMMARY The clipboard history popup shows an unreasonable amount of characters in a single line. When copying a long line of text (e.g. a link with trackers in it), the history window assumes an absurd horizontal size. STEPS TO REPRODUCE 1. Copy a long link 2. Open clipboard history with Meta+V OBSERVED RESULT The clipboard history displays a large amount of characters in one line, causing the window to assume a significant horizontal size. EXPECTED RESULT EITHER: The clipboard history wraps the text before truncating it; OR: The clipboard history truncates the text much earlier SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482190] (6.0) Under Wayland with fractional scaling enabled, cursor is the wrong size when over xwayland windows that are scaled by themselves
https://bugs.kde.org/show_bug.cgi?id=482190 Naxdy changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #6 from Naxdy --- Figured out that this was related to `xsettingsd` not being present on the system. Some distros don't install this automatically apparently when installing KDE. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 --- Comment #14 from Naxdy --- scale factor 200%, screen resolution 3840x2400, cursor size 24 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 Naxdy changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #11 from Naxdy --- Switched to the Breeze theme (black), but I can still reproduce the issue unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482190] (6.0) Under Wayland with fractional scaling enabled, cursor is the wrong size when over xwayland windows that are scaled by themselves
https://bugs.kde.org/show_bug.cgi?id=482190 Naxdy changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Naxdy --- This happens with the default Breeze (black) cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 --- Comment #9 from Naxdy --- I use Vimix cursors: https://github.com/vinceliuice/Vimix-cursors -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482222] New: (6.0) When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave
https://bugs.kde.org/show_bug.cgi?id=48 Bug ID: 48 Summary: (6.0) When using a touchscreen, using multi-finger touch gestures causes the desktop to misbehave Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When using a touchscreen, using multi-finger touch gestures causes the desktop to always "lock" a drag operation (I don't know how else to describe it). This results in the selection box being drawn perpetually on the desktop, with no way to get rid of it (save for restarting plasmashell). STEPS TO REPRODUCE 0. Be on a touchscreen device 1. Ensure you have more than 1 virtual desktop 2. Switch back and forth between your virtual desktops using the 3-finger-swipe gesture on your touchscreen. Repeat this for about ~6 times 3. Draw a selection rectangle on your desktop using your touch screen OBSERVED RESULT The selection rectangle stays in place even after the drag operation has finished. Using a traditional mouse causes the selection rectangle to follow it permanently. EXPECTED RESULT The selection rectangle disappears after the drag operation is completed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407667] Clicking on an expired notification in the history should launch or focus the app that sent it
https://bugs.kde.org/show_bug.cgi?id=407667 Naxdy changed: What|Removed |Added CC||xna...@hydra-development.ne ||t --- Comment #12 from Naxdy --- FYI: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2178 Not sure why it wasn't auto linked here -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] (6.0) Context menu (when right-clicking on the desktop) appears in a separate window after monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 Naxdy changed: What|Removed |Added Summary|(6.0) Context menu (when|(6.0) Context menu (when |right-clicking on the |right-clicking on the |panel) appears in a |desktop) appears in a |separate window after |separate window after |monitor restart |monitor restart -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] (6.0) Context menu (when right-clicking on the panel) appears in a separate window after monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 Naxdy changed: What|Removed |Added Summary|(6.0) Context menu (when|(6.0) Context menu (when |right-clicking on the |right-clicking on the |panel) appears in a |panel) appears in a |separate window under |separate window after |certain circumstances |monitor restart -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] (6.0) Context menu (when right-clicking on the panel) appears in a separate window under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=482185 Naxdy changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Naxdy --- Found the cause of the bug, it happens when the monitor is turned off! As such, here are the steps to reproduce: STEPS TO REPRODUCE 0. Confirm right-click context menu is working correctly, by focusing a window, then right clicking on the desktop. 1. Lock your session and turn off your monitor with ESC. Wait ~10 seconds. 2. Log back in to your session 3. Focus a window and right-click the on the desktop. OBSERVED RESULT The context menu opens in a separate Wayland window EXPECTED RESULT The context menu opens at the mouse cursor, not in a separate window ADDITIONAL INFORMATION A `plasmashell --replace` fixes the issue until the next time the monitor turns off. This is on a single-monitor setup FYI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #7 from Naxdy --- Though I don't have a razer device, I can confirm that this issue only seems to pop up for me after a long while of inactivity on my machine (i.e. leaving it powered up over night). Rebooting solves it until the next period of inactivity. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482191] (6.0) Middle clicking on a window no longer closes it
https://bugs.kde.org/show_bug.cgi?id=482191 --- Comment #3 from Naxdy --- I mean, middle-click-to-close is a pretty universal standard that works literally everywhere. Browser tabs, dolphin tabs, konsole tabs, yakuake tabs, etc. I don't see any reason why it shouldn't be the default, personally. But even if you wanted to move away from it in desktop effects for whatever reason, I'd at least expect the behavior to be consistent across the board. As I said, currently it's implemented in the overview effect, but not in present windows, which just feels extremely odd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482190] (6.0) Under Wayland with fractional scaling enabled, cursor is the wrong size when over xwayland windows that are scaled by themselves
https://bugs.kde.org/show_bug.cgi?id=482190 --- Comment #2 from Naxdy --- VSCodium and Slack present this issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482191] (6.0) Middle clicking on a window no longer closes it
https://bugs.kde.org/show_bug.cgi?id=482191 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482191] New: (6.0) Middle clicking on a window no longer closes it
https://bugs.kde.org/show_bug.cgi?id=482191 Bug ID: 482191 Summary: (6.0) Middle clicking on a window no longer closes it Classification: Plasma Product: kwin Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY While in the present windows effect, middle clicking it with a mouse wheel no longer closes it. (it still works in the overview effect however) STEPS TO REPRODUCE 1. Trigger present windows effect 2. Middle click on any window EXPECTED RESULT Window closes OBSERVED RESULT pure and utter sadness (window does not close) SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467061] XWayland apps have a slightly blurry mouse cursor when using scaling
https://bugs.kde.org/show_bug.cgi?id=467061 Naxdy changed: What|Removed |Added Status|RESOLVED|REOPENED CC||xna...@hydra-development.ne ||t Resolution|FIXED |--- --- Comment #7 from Naxdy --- I'm able to reproduce this issue in NixOS using Plasma 6.0. Not fixed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482190] New: (6.0) Under Wayland with fractional scaling enabled, cursor is the wrong size when over xwayland windows that are scaled by themselves
https://bugs.kde.org/show_bug.cgi?id=482190 Bug ID: 482190 Summary: (6.0) Under Wayland with fractional scaling enabled, cursor is the wrong size when over xwayland windows that are scaled by themselves Classification: Plasma Product: kwin Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY The mouse cursor assumes its original unscaled size whenever it is over an XWayland window that is scaled by itself under fractional scaling. STEPS TO REPRODUCE 1. Enable fractional scaling (legacy X11 apps should be scaled by themselves) 2. Move mouse cursor over an XWayland window OBSERVED RESULT Mouse cursor assumes unscaled size EXPECTED RESULT Mouse cursor remains scaled SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 --- Comment #5 from Naxdy --- Happens for me on multiple machines (AMD 7900 XTX, AMD integrated GPU, Intel integrated GPU), so I think a driver issue is unlikely. Could be NixOS related perhaps? Would be a very weird bug to be introduced by packaging however. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 --- Comment #3 from Naxdy --- Happens for me on multiple devices, both multi and single monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] [6.0] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 --- Comment #2 from Naxdy --- AMD RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] (6.0) Context menu (when right-clicking on the panel) appears in a separate window under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=482185 Naxdy changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Naxdy --- Not sure how to reliably reproduce this yet, I will update this report with more info as I uncover it. However, I felt it pertinent to make the initial report in case someone else has more info on this. I'm immediately setting this to NEEDSMOREINFO for this reason. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] New: (6.0) Context menu (when right-clicking on the panel) appears in a separate window under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=482185 Bug ID: 482185 Summary: (6.0) Context menu (when right-clicking on the panel) appears in a separate window under certain circumstances Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY I have a panel at the bottom set to auto-hide that only contains an icons-only task manager, and a panel at the top that contains a bunch of widgets. Just now, I've noticed that right-clicking the top panel (doesn't matter if on empty space, or on a widget) causes the context menu to appear in a separate wayland window at the center of the screen. This does not happen for the bottom panel. Not sure how to reliably reproduce this yet, I will update this report with more info as I uncover it. However, I felt it pertinent to make the initial report in case someone else has more info on this. I'm immediately setting this to NEEDSMOREINFO for this reason. STEPS TO REPRODUCE Unclear :( SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #1 from Naxdy --- When I rebooted a while back it stopped for a bit, but it's back now. So it may take a while after opening a session until it shows up? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 --- Comment #3 from Naxdy --- Journal output (probably not useful) Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: VA-API version 1.20.0 Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: Trying to open /run/opengl-driver/lib/dri/radeonsi_drv_video.so Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: Found init function __vaDriverInit_1_20 Feb 29 21:12:05 nxnix spectacle[1161952]: libva info: va_openDriver() returns 0 Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: Display initialized Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: API version 1 . 20 Feb 29 21:12:05 nxnix spectacle[1161952]: kpipewire_record_logging: VAAPI: Mesa Gallium driver 24.0.1 for AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 16.0.6, DRM 3.57, 6.7.6-zen1) in use for device "/dev/dri/renderD128" Feb 29 21:12:05 nxnix spectacle[1161952]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 --- Comment #2 from Naxdy --- Created attachment 166216 --> https://bugs.kde.org/attachment.cgi?id=166216=edit Bug showcase -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] New: Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 Bug ID: 482077 Summary: Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals" Classification: Plasma Product: kwin Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY Since 6.0, kwin_wayland floods my user journal with QObject::startTimer: Timers cannot have negative intervals whenever I move the mouse cursor. STEPS TO REPRODUCE 1. Open user journal with `journalctl --user --follow` 2. Move mouse OBSERVED RESULT kwin_wayland floods the user journal EXPECTED RESULT kwin_wayland does not flood the user journal SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] New: Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Bug ID: 482076 Summary: Clipboard no longer appears under mouse cursor Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net Target Milestone: 1.0 SUMMARY Since at least 6.0, the clipboard no longer appears under the mouse cursor when brought up with Meta+V, but instead appears in the center of the screen. STEPS TO REPRODUCE 1. Bring up clipboard history with Meta+V OBSERVED RESULT Clipboard history appears at the center of the screen EXPECTED RESULT Clipboard history appears under mouse cursor SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482037] (CRASH) Unable to delete incidents
https://bugs.kde.org/show_bug.cgi?id=482037 --- Comment #1 from Naxdy --- Possibly a bug in Kirigami, since the file in question hasn't really changed in 24.02 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482037] New: (CRASH) Unable to delete incidents
https://bugs.kde.org/show_bug.cgi?id=482037 Bug ID: 482037 Summary: (CRASH) Unable to delete incidents Classification: Applications Product: Merkuro Version: 24.02.0 Platform: NixOS OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: xna...@hydra-development.net CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Since 24.02, Merkuro Calendar locks up when attempting to delete an incident with the following message (console is flooded with it): qrc:/DeleteIncidencePage.qml:41:5: QML ColumnLayout: Layout polish loop detected for QQuickColumnLayout(0x4de4680, parent=0x9b676e0, geometry=0,0 0x184). Aborting after two iterations. STEPS TO REPRODUCE 1. Create an event (non-recurring) 2. Right click and attempt to delete it OBSERVED RESULT Application locks up EXPECTED RESULT Application does NOT lock up SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482035] [6.0] Scrolling is done at a lower framerate than the monitor's
https://bugs.kde.org/show_bug.cgi?id=482035 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 482035] New: [6.0] Scrolling is done at a lower framerate than the monitor's
https://bugs.kde.org/show_bug.cgi?id=482035 Bug ID: 482035 Summary: [6.0] Scrolling is done at a lower framerate than the monitor's Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.249.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: xna...@hydra-development.net CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY Not sure if this is the right place for this, but since 6.0, all scroll components in KDE apps scroll at a lower framerate than that of the monitor's. Note that this only applies to scrolling with the scroll wheel, manually dragging the scroll bar using the mouse cursor scrolls just fine at the monitor's frame rate. STEPS TO REPRODUCE 1. Be on a 120Hz (or higher frame rate) monitor 2. Open System Settings 3. Resize the window such that the left panel becomes scrollable 4. Scroll the left panel using your mouse's scroll wheel OBSERVED RESULT The contents scroll at sub 120Hz EXPECTED RESULT The contents scroll at 120Hz SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] [6.0] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 Naxdy changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] New: [6.0] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 Bug ID: 482034 Summary: [6.0] Some animations are not playing at the monitor's refresh rate Classification: Plasma Product: kwin Version: 5.93.0 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY Since 6.0, some animations are not playing at the monitor's refresh rate. My monitor is 120Hz, but some animations very clearly play at a lower framerate (if I had to guess, I'd say around 60Hz). Affected animations that I've encountered thus far are: - Present windows - Desktop overview (meta + W) If it matters, my monitor has a pretty high resolution of 7680x2160 STEPS TO REPRODUCE 1. Be on a monitor with at least 120Hz refresh rate 2. Play one of the animations listed above OBSERVED RESULT The animation plays at a lower framerate than 120Hz EXPECTED RESULT The animation plays at 120Hz (assuming the hardware is capable enough) SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482019] New: When in rectangular capture mode, UI disappears after starting to annotate image
https://bugs.kde.org/show_bug.cgi?id=482019 Bug ID: 482019 Summary: When in rectangular capture mode, UI disappears after starting to annotate image Classification: Applications Product: Spectacle Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: xna...@hydra-development.net CC: k...@david-redondo.de Target Milestone: --- SUMMARY Since 24.02, launching Spectacle in rectangular region mode and beginning to annotate the picture causes the UI to disappear in an unrecoverable manner. STEPS TO REPRODUCE 1. Open Spectacle in rectangular region mode (via keyboard shortcut) 2. Drag out any region on the screen 3. Begin to annotate (e.g. use the highlight marker to highlight something) OBSERVED RESULT Spectacle's UI disappears and doesn't return, even upon finishing to annotate EXPECTED RESULT EITHER: Spectacle's UI disappears while annotating, and then returns; OR: Spectacle's UI never disappears SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This happened fairly recently, I remember at least rc1 not having this problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480281] (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device
https://bugs.kde.org/show_bug.cgi?id=480281 --- Comment #6 from Naxdy --- Sorry for the long wait. Had a chance to test it on GNOME, and there it works for me as well. Not a surprise though, given that GNOME enforces CSDs, and when used under the plasma mobile shell (which also has CSDs enabled for GTK apps) it also works. I'll wait until Plasma 6 is out and re-test in both the mobile shell and regular plasma shell, and report back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 --- Comment #15 from Naxdy --- If you're on a distro that allows you to backport the libraries you need (e.g. NixOS), the packages you need are: plasma-integration, kio, kio-extras. With these, qt6 apps have functioning global menus in Plasma 5. If not, just wait for Plasma 6 release, which is guaranteed to fix this issue anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480281] (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device
https://bugs.kde.org/show_bug.cgi?id=480281 --- Comment #5 from Naxdy --- Could be upstream GTK then, I will switch my device over to GNOME this weekend and report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480281] (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device
https://bugs.kde.org/show_bug.cgi?id=480281 --- Comment #3 from Naxdy --- Do you also get "Tried to map a popup with a non-top most parent" in your log? As a side note, this only affects GTK apps running under native Wayland. If I force them to run under Xwayland (via GDK_BACKEND=x11), this issue does not present itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480281] (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device
https://bugs.kde.org/show_bug.cgi?id=480281 --- Comment #1 from Naxdy --- Uploaded a demo of the bug using a mouse: https://cloud.polskalemon.com/s/teHtPcLJzxdJH68 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480281] New: (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device
https://bugs.kde.org/show_bug.cgi?id=480281 Bug ID: 480281 Summary: (Wayland) GTK Appmenus exhibit erratic / incorrect behavior on tablet device Classification: Plasma Product: kwin Version: 5.27.10 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY Not sure, if this is even a kwin bug, or something else. But on my tablet device, when logged into the regular Plasma (Wayland) session, the appmenu of most GTK apps is broken in an awkward way, in that no matter where the appmenu is clicked, the click is always registered on the leftmost item. This is not a huge issue when using a mouse, as hovering over a different item will select it, but when using the touchscreen, this essentially renders GTK appmenus completely unusable (there is a way to focus the correct item with some wizard-like finger movements, but it's incredibly unintuitive and cumbersome). Note that this issue does NOT appear when window decorations are disabled via: [org.kde.kdecoration2] NoPlugin=true As is the default for the mobile session (thus, in the mobile session, these appmenus work just fine). When messing around with the appmenu, the affected app (I used gscan2pdf) spams this in the user journal: Jan 24 17:42:43 nxtab ..gscan2pdf-wra[4552]: Tried to map a popup with a non-top most parent STEPS TO REPRODUCE Sorry, no idea. I'd say get a Microsoft Surface Go 3, install Plasma on it, and give it a try, but this doesn't seem viable. Disabling the touch screen, changing screen orientation, and display scaling doesn't affect this issue however. The only thing that "fixes" it, is disabling window decorations entirely and forcing GTK apps to use CSDs. OBSERVED RESULT Appmenu click is always registered in the top left corner first (presumably) EXPECTED RESULT Appmenu click is registered at the position of the mouse cursor / touch SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Since this may be difficult to reproduce due to potentially being hardware specific, I'm happy to test any patches or config changes thrown my way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479362] Flatpak apps' notifications are no longer interactive
https://bugs.kde.org/show_bug.cgi?id=479362 Naxdy changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Naxdy --- Yeah, pretty confident to label this an issue with the flatpak versions or flatpak itself. System rollback preserves the issue, so pretty confident nothing on KDE side messed this up. Perhaps there's something KDE can do to fix this? Not sure. Either way, I just moved to the native versions of these apps to restore full functionality. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479362] Flatpak apps' notifications are no longer interactive
https://bugs.kde.org/show_bug.cgi?id=479362 --- Comment #2 from Naxdy --- Another update: Seems that this is exclusive to Flatpak apps. When I install these apps' native counterpart, notifications appear to work correctly and are interactive. I do have desktop portals installed and configured correctly. I'm assuming an update of some flatpak runtime triggered this, as if I rollback my main system installation (including flatpak itself, but not the flatpaks or runtimes) to a few months back, the issue persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479362] Flatpak apps' notifications are no longer interactive
https://bugs.kde.org/show_bug.cgi?id=479362 Naxdy changed: What|Removed |Added Summary|Certain Electron apps' |Flatpak apps' notifications |notifications are no longer |are no longer interactive |interactive | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479362] Certain Electron apps' notifications are no longer interactive
https://bugs.kde.org/show_bug.cgi?id=479362 --- Comment #1 from Naxdy --- Update: Element is also affected by this, so I'm leaning towards this being an issue that affects all Electron apps. Since it also affects apps with older Electron versions that were working before (like Discord), I'm strongly leaning towards something on the KDE side having broken this recently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479362] New: Certain Electron apps' notifications are no longer interactive
https://bugs.kde.org/show_bug.cgi?id=479362 Bug ID: 479362 Summary: Certain Electron apps' notifications are no longer interactive Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY Since at least 5.27.10, certain Electron apps' notifications are no longer interactive. For example, usually when e.g. Discord sends a notification (due to message received), that notification popup is clickable and causes Discord to navigate to the message sent. However, this is no longer the case, and clicking the notification does nothing. Same goes for Slack. However, Slack notifications also exhibit the behavior that the app icon has disappeared, and in its place is the regular KDE/Plasma icon. STEPS TO REPRODUCE 1. Receive a notification from an affected Electron app (Discord, Slack, perhaps others) 2. Click the notification popup as it appears OBSERVED RESULT Notification popup disappears EXPECTED RESULT Notification popup disappears *and* the app responds to the popup having been clicked (response may vary, but is commonly navigation to the part of the app that initiated the notification) SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS Unstable (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Slack and Discord stopped working at different times for me, so this *may* be a downstream issue. Though I run both in flatpak, so who knows. Would be great if someone could confirm if any work was done on the KDE side of things the past couple minor versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479347] New: Wishlist: Allow setting notification sounds on a per-application basis
https://bugs.kde.org/show_bug.cgi?id=479347 Bug ID: 479347 Summary: Wishlist: Allow setting notification sounds on a per-application basis Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY Currently, it is only possible to customize notification sounds for applications that correctly export all of their individual notification events (essentially only KDE apps). For other apps, there are still "some" settings that can be customized, but these are limited to where and how notifications appear. The problem is, many third-party apps do not properly respect KDE's "do not disturb" mode, which results in these apps still playing their own notification sound (which goes against the idea of DND), but no popup showing up. A possible workaround here would be to disable notification sounds in these apps altogether, and set a new custom notification sound in system settings (which would then be properly disabled upon entering DND mode), but for this the functionality is currently lacking. Therefore, I propose to add the ability to "add" a notification sound to any app's notifications, even if that app does not export its notifications in detail. Without any other change, this would result in the app's own notification sound and the custom one playing at the same time, so of course the idea here would be to disable the app's own sound in its settings first. I'd have a look at implementing this myself as well, but wanted to gather some feedback first if this is something that might be considered for upstreaming. -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 476401] New: Kalendarac notifications no longer direct towards event
https://bugs.kde.org/show_bug.cgi?id=476401 Bug ID: 476401 Summary: Kalendarac notifications no longer direct towards event Classification: Applications Product: Merkuro Version: 23.08.2 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: xna...@hydra-development.net CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Since the rebrand from "Kalendar" to "Merkuro", kalendarac no longer functions when directly clicking on a reminder notification (i.e. invoking its default behavior). Previously it would open Kalendar if not already opened, and if already opened, it would redirect to the event that produced the notification. STEPS TO REPRODUCE 1. Create an event in Merkuro with a reminder 2. Wait for the reminder to occur 3. Click on the reminder notification to invoke its default behavior OBSERVED RESULT The notification disappears, but nothing else happens. EXPECTED RESULT Merkuro opens if not already open. If already open, Merkuro navigates to the event belonging to the notification SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 475826] New: Cannot modify google groupware calendars
https://bugs.kde.org/show_bug.cgi?id=475826 Bug ID: 475826 Summary: Cannot modify google groupware calendars Classification: Applications Product: Merkuro Version: 23.08.1 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: xna...@hydra-development.net CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Since at least 23.08.1, it is impossible to refresh or modify Google groupware calendars. STEPS TO REPRODUCE 1. Add a Google groupware calendar under Settings -> Configure Merkuro Calendar -> Accounts 2. Attempt to modify the newly added account OBSERVED RESULT Nothing happens EXPECTED RESULT A window appears, allowing one to configure the created resource SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 474301] Plasma 6 Feature Request/Proposal: Adaptive titlebar color
https://bugs.kde.org/show_bug.cgi?id=474301 --- Comment #4 from Naxdy --- So, I managed to hack something together that sorta works, but to be honest... I don't like it lol I thought it would make apps look a bit more integrated if the title bar was made to look flush with the app, but it just ends up looking more out of place imo, especially when using a lot of electron apps. Honestly I prefer the default color on every title bar. This plus the fact that it requires work on 3 repos (kwin + kdecoration + breeze) makes it kinda not worth for me to continue work on this. Oh well, it was a learning experience! :p -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 474301] Plasma 6 Feature Request/Proposal: Adaptive titlebar color
https://bugs.kde.org/show_bug.cgi?id=474301 --- Comment #2 from Naxdy --- I think that heuristically deriving the window title bar color from the window's contents is not much different than heuristically deriving the accent color from the current wallpaper (which can also be animated, or set to change over time via slideshow). But fair enough, then at the very least I know I won't have to bother upstreaming it if I ever do manage to find the time to work on this (which would've been a bit of a headache seeing as it involves at least 3 repos from what I can glean thus far). Thanks anyway for taking the time. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 474301] New: Plasma 6 Feature Request/Proposal: Adaptive titlebar color
https://bugs.kde.org/show_bug.cgi?id=474301 Bug ID: 474301 Summary: Plasma 6 Feature Request/Proposal: Adaptive titlebar color Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: xna...@hydra-development.net CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- REQUEST With the design teams' ongoing effort to push the "CSD but not CSD" look in native Breeze apps (which I personally am a huge fan of), it makes sense to try to apply this to as many other applications as possible. Nowadays, many applications use flat single colors near the header bar, which makes them ideal candidates for a single-color title bar / window frame like we already have. The request therefore is to make the window title bar dynamically set its color based on the window's contents near the top edge, to create as seamless a transition from window contents to SSD's as possible. PROPOSAL To determine the color for the title bar, I suggest the following approach: 1. Scan the topmost row of pixels of a window's contents 2a. If > 50% of those pixels are of the same color, set the title bar to that color. 2b. If <= 50% of those pixels are of the same color, leave the title bar alone, it will be the color specified in the color scheme. Clearly, this would require the window manager somehow talk to the window decoration, either to submit the topmost row of pixels (so that the window decoration can perform the check), or to submit the color that it should set itself to (here, the window manager would perform the check). Like any other titlebar customizations, this feature should be toggleable in system settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473772] New: Upon XWayland crash, X windows are offset slightly to the top and global menu ceases to function
https://bugs.kde.org/show_bug.cgi?id=473772 Bug ID: 473772 Summary: Upon XWayland crash, X windows are offset slightly to the top and global menu ceases to function Classification: Plasma Product: kwin Version: 5.27.7 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY When in Wayland and XWayland crashes or is killed, newly started X windows are offset slightly to the top. This results in the top UI elements being hidden behind the title bar, and an awkward empty space appearing at the bottom between the shadow and the window contents, and global menu no longer works. Note that this issue can be somewhat worked around by setting the window to borderless. STEPS TO REPRODUCE 1. Log in to Plasma Wayland 2. Start at least 1 X window 3. Brutally murder XWayland by killing its process 4. Open another X window OBSERVED RESULT The newly opened X window contents are offset slightly to the top, and global menu is no longer functional for that window EXPECTED RESULT The window contents appear the same as before, and global menu is functional SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #33 from Naxdy --- Yes, for wayland GTK apps I get global menu in the app, but not in the global panel. For XWayland GTK apps, I get it not in the app, but in the global panel. For qt6 apps I don't get a menu anywhere, but that's a completely different issue (which has already been reported). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Naxdy changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #31 from Naxdy --- For me, global menu is still in the GTK3 apps, not in the global menu bar... This is on Plasma 5.27.6 & GTK 3.24.37. I'm reopening this, hoping for some more info. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #29 from Naxdy --- @Fushan can you elaborate on this? Global menu is still not working for me in GTK (wayland) apps. Or is this a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 --- Comment #35 from Naxdy --- +1 for disabling blur ootb until this is fixed. More and more distros are moving to Wayland as the default for KDE (including big ones like Fedora), and while yes, they can choose to disable it themselves, many probably will not do that, and shipping a clearly broken feature is just going to reinforce the "KDE is buggy" stereotype, that has taken us a very long time to get rid of. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=459468 --- Comment #25 from Naxdy --- @Andres did you confirm that the flatpak apps in question have read access to ~/.icons and/or /usr/share/icons (or wherever your cursor theme is located), and that their XCursor search path isn't being overwritten using an environment variable? You can use Flatseal to check this, or KDE's built-in permissions system in System Settings -> Applications -> Flatpak Permission Settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472407] Walyand: Screencasting causes KWin to take up 100% of a single CPU core
https://bugs.kde.org/show_bug.cgi?id=472407 --- Comment #1 from Naxdy --- Also, possibly related to: https://bugs.kde.org/show_bug.cgi?id=467574 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472407] Walyand: Screencasting causes KWin to take up 100% of a single CPU core
https://bugs.kde.org/show_bug.cgi?id=472407 Naxdy changed: What|Removed |Added Keywords||regression, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472407] New: Walyand: Screencasting causes KWin to take up 100% of a single CPU core
https://bugs.kde.org/show_bug.cgi?id=472407 Bug ID: 472407 Summary: Walyand: Screencasting causes KWin to take up 100% of a single CPU core Classification: Plasma Product: kwin Version: 5.27.6 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY The commit https://invent.kde.org/plasma/kwin/-/commit/23806d31e23d2ef2bc8344114feb6d27364cdc01 has introduced a regression that can be observed on my system that manifests itself as KWin taking up 100% of a single CPU core (and dropping frames) when screencasting. Reverting the mentioned commit has completely resolved the issue for me. STEPS TO REPRODUCE 0. Log in to Plasma Wayland session 1. Begin screencasting (I used rectangular region which is scheduled for 6.0, but fullscreen produced the same issue for me - I used OBS to test this) OBSERVED RESULT KWin takes up 100% of a singe CPU core (thread), mouse movement is choppy, and journalctl --user shows KWin is struggling with frame drops. EXPECTED RESULT Screencasting is smooth, does not impact desktop usage, and does not take 100% of a single CPU core. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459468] Certain Xwayland apps do not respect third-party cursor theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=459468 Naxdy changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #23 from Naxdy --- Quick update: After some deliberation I've found that the apps that still had the adwaita cursor theme on my Nix install were all flatpak apps that didn't have proper read permissions for the ~/.icons folder. Granting them permissions solved the issue. I'm going to go ahead and close this for now, feel free to reopen if anyone has an issue with a non-flatpak app, or a flatpak app that does have the proper permissions set. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472041] New: Wayland: Clicking the "View Mode" button while the window is unfocused makes the context menu appear in its own window
https://bugs.kde.org/show_bug.cgi?id=472041 Bug ID: 472041 Summary: Wayland: Clicking the "View Mode" button while the window is unfocused makes the context menu appear in its own window Classification: Applications Product: okular Version: 23.04.1 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: xna...@hydra-development.net Target Milestone: --- SUMMARY While on wayland and when the window is unfocused, clicking the "View Mode" button in Okular makes the context menu appear in its own window. STEPS TO REPRODUCE 0. Log in to plasma wayland session 1. Open Okular 2. Open a document in Okular 3. Unfocus the window (click on a different window) 4. Click the "View Mode" button in Okular OBSERVED RESULT The context menu appears in its own window EXPECTED RESULT Okular is focused and the context menu appears next to the cursor SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
