[Powerdevil] [Bug 480122] Turning off screen and then closing lid (for going sleep) fail to go to sleep and gives black screen
https://bugs.kde.org/show_bug.cgi?id=480122 --- Comment #11 from André M --- Searching again for this issue, I got to this topic, and the solution there finally fixed the issue for me: https://bbs.archlinux.org/viewtopic.php?id=290523 > # echo 0 > /sys/power/pm_async -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450168] First letter typed on new Overview Effect gets entered twice in Wayland
https://bugs.kde.org/show_bug.cgi?id=450168 --- Comment #11 from André M --- This is fixed for me in Plasma 6rc2. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 480122] Turning off screen and then closing lid (for going sleep) fail to go to sleep and gives black screen
https://bugs.kde.org/show_bug.cgi?id=480122 --- Comment #7 from André M --- PS: it seems to happen only when discrete gpu is turned on and/or external monitor connected. If external monitor is disconnected, dGPU is off and system is running on the Rembrandt 680M iGPU, closing lid suspends system and wakes up normally. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 480122] Turning off screen and then closing lid (for going sleep) fail to go to sleep and gives black screen
https://bugs.kde.org/show_bug.cgi?id=480122 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #6 from André M --- I see something possibly related on NixOS, but with sleep on lid close config (power settings). When closing lid even with screen on and unlocked, or screen locked, or screen off, the system attempts to go to sleep, but can't. Instead, fans accelerate, like an infinite loop. Opening the lid shows black screen with keyboard still on (i.e. system didn't sleep), and it can't wake up. sysrq (which usually works) doesn't work here, and only a hard shutdown can turn the laptop off. Putting the laptop to sleep from kickoff or lockscreen (screen on) works as usual, while a `sleep 5 && systemctl suspend` on console, followed by lockscreen + esc (to turn screen off) also presents the problem, so it looks like the issue is trying to suspend with screen off. Ryzen 6900HS m + Radeon 6850M, if it matters. `journalctl -eb -1` shows the usual stuff in the end: > systemd-logind[2144]: Lid closed. > systemd-logind[2144]: The system will suspend now! > ModemManager[20361]: [sleep-monitor-systemd] system is about to suspend > kernel: r8169 :06:00.0 enp6s0: Link is Down > systemd[1]: Starting Pre-Sleep Actions... > systemd[1]: Starting TLP suspend/resume... > systemd[1]: pre-sleep.service: Deactivated successfully. > systemd[1]: Finished Pre-Sleep Actions. > systemd[1]: Finished TLP suspend/resume. > systemd[1]: Reached target Sleep. > systemd[1]: Starting System Suspend... > systemd-sleep[97413]: Failed to lock home directories: Unknown object > '/org/freedesktop/home1'. > systemd-sleep[97413]: Performing sleep operation 'suspend'... > kernel: PM: suspend entry (s2idle) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #60 from André M --- I also see this happening in Plasma 6rc2, not only with XWayland, but also native Wayland apps. I added some logs to xdgshellwindow.cpp, and it seems the events emit QRectFs in translated coordinates, e.g.: if you have 1200p screen with 1.45x scale, it'll send a client height of 827.5862p. Eventually, this won't add up and the gaps will show. How feasible it'd be to keep physical/real dimensions everywhere (since those are always integers), and have the scale be sent to the clients just as a hint to render larger elements? i.e. move scale to the "edges" of the software -- 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 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 411489] USB (MTP) connection to Android fails if Dolphin was running before plugging in
https://bugs.kde.org/show_bug.cgi?id=411489 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot when using BTRFS filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #54 from André M ---
(In reply to tagwerk19 from comment #53)
> (In reply to André M from comment #52)
> > I've been testing the patch on NixOS on kf 5.106, and it's working great
> > across 3 reboots of a couple of mounted subvolumes.
> Can you share how you've done this? At the moment I have baloo from unstable:
>From what you said, it looks like you're on nixos stable (22.11 I suppose), and
trying unstable for specific packages; baloo itself is a kdeFrameworks, so it's
harder to override, because it gets pulled indirectly by other kde packages
when you `services.xserver.desktopManager.plasma5.enable = true`, therefore,
the best way I know would be to replace the whole plasma5Packages scope using
an overlay (it'll still trigger several recompilations, because again baloo is
an indirect dependency of several packages):
final: prev: let
nixos-unstable = import {inherit (prev) system;};
in {
plasma5Packages = nixos-unstable.plasma5Packages.overrideScope' (finalx:
prevx: let
kdeFrameworks = prevx.kdeFrameworks.overrideScope' (finaly: prevy: {
baloo = prevy.baloo.overrideAttrs (attrs: {
version = "${attrs.version}-patched";
patches =
(attrs.patches or [])
++ [
# baloo in btrfs
(final.fetchpatch {
url = "https://bugsfiles.kde.org/attachment.cgi?id=159031;;
sha256 = "sha256-hCtNXUpRhIP94f7gpwTGWWh1h/7JRRJaRASIwHWQjnY=";
})
];
});
});
in (kdeFrameworks // {inherit kdeFrameworks;}));
}
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot when using BTRFS filesystem
https://bugs.kde.org/show_bug.cgi?id=402154 --- Comment #52 from André M --- I've been testing the patch on NixOS on kf 5.106, and it's working great across 3 reboots of a couple of mounted subvolumes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #44 from André M --- Just to remark: if the Xwayland window is in maximized state, and *moved* to another screen (e.g. through Meta+Shift+Left/Right or Present Desktops effect), when it lands on the other screen, it doesn't have the gap. Unmaximizing and remaximizing makes the gap show off. So it looks like the Maximized Geometry calc when moving screens is correct, and the restore/remaximize one is wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave pixel gaps when using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #43 from André M --- Created attachment 158837 --> https://bugs.kde.org/attachment.cgi?id=158837=edit Still an issue I think this is not fixed, got the issue with this patch applied on top of 5.27.5, with the pixel NOT between the window and panel (attached screenshot). 2560x1600@145% window (there's a 2560x1440@135% screen to the right, but it shouldn't matter, right?), VLC flatpak on Xwayland. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469080] New: Kmail on flatpak doesn't use open file portal when trying to Attach file on composer
https://bugs.kde.org/show_bug.cgi?id=469080 Bug ID: 469080 Summary: Kmail on flatpak doesn't use open file portal when trying to Attach file on composer Classification: Applications Product: kmail2 Version: 5.23.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY Portal integration is working e.g. to Save an Attachment, but when composing an e-mail, trying to Attach a file to the e-mail only shows up folders which have been allowed to kontact's flatpak (e.g. through Flatseal). STEPS TO REPRODUCE 1. Don't export home/filesystem to Kontact on flatpak 2. Write an e-mail and click on Attach file OBSERVED RESULT Only allowlisted folders are shown EXPECTED RESULT XDG file portal allows to attach any folder in the system SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NixOS unstable (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105 Qt Version: 5.15.9 ADDITIONAL INFORMATION Kontact's flatpak from Flathub -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461429] Kwin (?) crashes out of nowhere
https://bugs.kde.org/show_bug.cgi?id=461429 --- Comment #11 from André M --- Ok, I managed to get a stacktrace of a "RT throttling activated" frozen kwin_wayland instance. It seems to happen inside `KWin::Placement::placeSmart` function specifically when launching _certain_ wayland windows (maybe my Signal repro just triggered it because I often use it with non-maximized/with some specific remembered geometry?). That function has a very suspicious `do/while` b;pclk, which may be causing an infinite loop here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457556] Honor high resolution scrollwheels
https://bugs.kde.org/show_bug.cgi?id=457556 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441705] Add a kwin rule to disable scaling for some wayland window
https://bugs.kde.org/show_bug.cgi?id=441705 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #4 from André M --- This would be very useful for Qemu windows as well: -display sdl,gl=on with SDL_VIDEODRIVER=wayland mouse handling and resolution detection breaks if scaling is not 100%, making this very hard to use. -display gtk,gl=on also has issues with the fractional scale. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized XWayland apps leave some pixels on the right border with fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #24 from André M --- The situation seems to have improved on Plasma 5.26.90 (5.27 beta): While moving a *xwayland window* between 2 monitors (main 2560x1600 150% with left, top panels; right 2560x1440 135% no panels), when they go to the other monitor while already maximized, they occupy the correct area on the other monitor, leaving no gaps; when unmaximizing and re-maximizing in place, the right border still leaves a couple of pixels off, showing the wallpaper or window below, as before. Either way, bottom gap is gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461429] Kwin (?) crashes out of nowhere
https://bugs.kde.org/show_bug.cgi?id=461429 --- Comment #10 from André M --- I can reproduce this consistently trying to run Signal Desktop flatpak with wayland experimental option: > flatpak run --env=SIGNAL_USE_WAYLAND=1 org.signal.Signal kwin_wayland freezes instantly. I can't switch ttys, but it responds to SysRq sequences (sysrq rk to kill terminal's proccesses doesn't work, but reisub and friends do). I can ssh to the machine, and a `pkill -9 kwin_wayland` from ssh or kdeconnect also work to bring me back to the console at the cost of losing all open applications. Trying to force recover with `/sys/kernel/debug/dri/1/amdgpu_gpu_recover` doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461429] Kwin (?) crashes out of nowhere
https://bugs.kde.org/show_bug.cgi?id=461429 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #9 from André M --- I also encountered this issue on Kwin 5.26.5 Wayland on NixOS with AMD 6000 series. In my case, I usually use the iGPU of my Ryzen 6900HX processor (Radeon 680M). The `kernel: sched: RT throttling activated` kernel line seems to mark the lock up, following a series of similar log snippets: > ... > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: kwin_wayland_drm: > Failed to create framebuffer for multi-gpu: Invalid argument > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: BlurConfig::instance > called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: ZoomConfig::instance > called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > WindowViewConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > SlidingPopupsConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > SlideConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > OverviewConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > KscreenConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > DimInactiveConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: > DesktopGridConfig::instance called after the first use - ignoring > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: OpenGL vendor > string: AMD > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: OpenGL renderer > string: AMD Radeon Graphics (rembrandt, LLVM 14.0.6, DRM > 3.49, 6.1.6) > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: OpenGL version > string: 4.6 (Core Profile) Mesa 22.3.3 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: OpenGL shading > language version string: 4.60 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Driver: >Unknown > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: GPU class: >Unknown > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: OpenGL version: >4.6 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: GLSL version: >4.60 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Mesa version: >22.3.3 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: X server version: >1.22.1 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Linux kernel > version: 6.1.6 > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Requires strict > binding:no > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: GLSL shaders: >yes > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Texture NPOT > support: yes > Jan 20 13:50:39 midichlorian kwin_wayland_wrapper[3369]: Virtual Machine: >no In this case, there was no kernel module traceback in logs, indicating it was just kwin which seems to have entered some form of infinite loop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462451] Plasma on Kwin Wayland doesn't start with virgl on qemu
https://bugs.kde.org/show_bug.cgi?id=462451 André M changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from André M --- Somehow this got fixed by itself here on NixOS, possibly by kf5.101 or some patch in the 5.26 series. Plasma Wayland starts fine now under qemu+virgl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462451] New: Plasma on Kwin Wayland doesn't start with virgl on qemu
https://bugs.kde.org/show_bug.cgi?id=462451 Bug ID: 462451 Summary: Plasma on Kwin Wayland doesn't start with virgl on qemu Classification: Plasma Product: kwin Version: 5.26.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY Plasma Wayland inside a virgl qemu VM doesn't work. We get only a black screen just with cursor (indicating kwin_wayland did get launched correctly), but plasma didn't start. With Yakuake's autostart, we can see the terminal window, and inspecting the logs, some errors like: kwin_wayland[1145]: error in client communication (pid 1278) plasmashell[1278]: [destroyed object]: error 6: invalid stride 10240 for plane 0 STEPS TO REPRODUCE 1. Install quickemu 2. quickget kdeneon user 3. quickemu --vm kdeneon-user.conf (-device virtio-vga-gl -display sdl,gl=on) 4. On the VM, go to SDDM config, switch off autologin, apply and logout 5. Login to Plasma Wayland session OBSERVED RESULT Black screen with only cursor EXPECTED RESULT Plasma Wayland session SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User 20221117-0714 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Tested with quickget/qemu on current NixOS unstable, but from qemu's small surface, I suppose it should happen when running over any distro. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized xwayland apps leave some pixels on the right border
https://bugs.kde.org/show_bug.cgi?id=459373 --- Comment #20 from André M --- Created attachment 154154 --> https://bugs.kde.org/attachment.cgi?id=154154=edit Still an issue on kwin-git a93ccbd7e74 Ok, compiled kwin-git, kdecoration-git and kwayland-git as of today, and the issue is still present, but has improved; if you compare with the previous screenshot with VLC, the bottom pixel is gone, and when in fullscreen, Xwayland apps also don't show the bug; BUT when Xwayland app is maximized, on the right side the wallpaper still can be seen; while it's maximized, editing the left panel's width makes it disappear, but as soon as unmaximizing and remaximizing the app, the bleeding shows up again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459373] Maximized xwayland apps leave some pixels on the right border
https://bugs.kde.org/show_bug.cgi?id=459373 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #15 from André M --- Created attachment 154145 --> https://bugs.kde.org/attachment.cgi?id=154145=edit Still an issue on 5.26.4 5.26.4 seem to have MR 3008. Even applying MR 3215 on top of it, maximized/fullscreen Xwayland windows still get a very noticeable bottom+right border which bleeds the wallpaper. This is with a 2560x1600 px screen with 150% scaling. My main concern is with fullscreen Xwayland games, if this would prevent direct scanout. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455444] Custom Shortcuts are gone in 5.25 on Wayland
https://bugs.kde.org/show_bug.cgi?id=455444 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 401863] baloo creates multiple entries for files residing on multi-device btrfs file systems
https://bugs.kde.org/show_bug.cgi?id=401863 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402154] Baloo reindexes everything after every reboot when using BTRFS filesystem
https://bugs.kde.org/show_bug.cgi?id=402154 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450168] First letter typed on new Overview Effect gets entered twice
https://bugs.kde.org/show_bug.cgi?id=450168 --- Comment #4 from André M --- This happens in my NixOS unstable as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450168] First letter typed on new Overview Effect gets entered twice
https://bugs.kde.org/show_bug.cgi?id=450168 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441409] [wayland] KWIN does not init GPU acceleration (resets to llvmpipe) in multi-gpu setups in case if one gpu does not support GPU acceleration
https://bugs.kde.org/show_bug.cgi?id=441409 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #2 from André M --- This also seems related to #450110 , although that mentions X11 only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 --- Comment #1 from André M --- I can confirm this issue as well, with an MSI GS63VR 7RF (i7-7700HQ + Nvidia 1060), on NixOS unstable. Interesting enough, in my case, the internal screen stays smooth, and only the external monitor gets low performance and high CPU usage. I can confirm it quantitatively by running glxgears. If the window is on the internal screen, I get ~60FPS (vsync'd). If I move the glxgears window to the external, nvidia-connected screen, it drops to ~32-36 FPS, and even the cursor gets choppy. Also, sometimes when connecting external monitor after plasma startup, something gets weird, wallpaper doesn't show up, but I can move the mouse and windows to the external screen. My current workaround is a thunderbolt3 port with a thunderbolt->HDMI adapter, which is detected as eDP, runs on iGPU, and glxgears reports 75FPS (75hz monitor) and a smooth desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452791] Black Screen When Starting Plasma (using Prime/NVIDIA on Wayland)
https://bugs.kde.org/show_bug.cgi?id=452791 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450110] [nvidia] Poor performances on second monitor with on-demand prime profile
https://bugs.kde.org/show_bug.cgi?id=450110 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452081] [wayland] left-click on tasks launchers does not launch apps, but scroll-up does
https://bugs.kde.org/show_bug.cgi?id=452081 André M changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from André M --- Not sure if caused by the recent rebuilds on nixos-unstable or the last commits to latte master, but it started to work as intended again on Wayland, so I can't reproduce this issue anymore. Thanks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452081] Wayland: left-click on launchers in dock's task manager don't launch apps, but scroll-up does
https://bugs.kde.org/show_bug.cgi?id=452081 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452081] New: Wayland: left-click on launchers in dock's task manager don't launch apps, but scroll-up does
https://bugs.kde.org/show_bug.cgi?id=452081 Bug ID: 452081 Summary: Wayland: left-click on launchers in dock's task manager don't launch apps, but scroll-up does Product: lattedock Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY I'm using Latte master on Wayland on NixOS unstable (notice this is a little different from other systems, so I hope it's not a packaging issue), with a top bar with utilities, and a bottom bar with launchers and a couple widgets. I have a weird issue: I can't launch nor activate programs by clicking on launchers. After hovering, on first left-click, I can see a darkening effect on icon, but no bounce nor app. Later clicks while still hovering don't cause this effect anymore until leaving and hovering again. Ctrl+Left-click doesn't work. Left-click on widgets on the same and other bar works and activate the respective widgets. Scrolling up over the launcher DOES launch the app though, and is my current workaround. Right-click works as intended. Tested this with a fresh user, same issue. It does not occur on X11 on the same system. Any idea what can be causing this only on Wayland? Thank you very much in advance. STEPS TO REPRODUCE 1. Launch fresh Latte master on NixOS Wayland (bottom dock with some launchers) 2. Left-click on Dolphin to try to launch it OBSERVED RESULT Icon gets darken effect on first click, then nothing, no bounce, no app launched, no darkening on new clicks until leaving and hovering again. Launcher gets properly activated if scroll-up instead. EXPECTED RESULT App gets launched, or switched on left-click SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable (reported as 22.05) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449432] Wayland: Activities panel resizes/moves active window
https://bugs.kde.org/show_bug.cgi?id=449432 André M changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED --- Comment #6 from André M --- After getting reports that this bug was also an issue in Gentoo, but that it's fixed with kf5 git, I went looking for patches which may have fixed it[1]. It seems that this is not a downstream bug, affects plasma 5.24 with kf5 5.90, but already got fixed by https://invent.kde.org/frameworks/plasma-framework/-/commit/d40d36057a0ee9fcb4badc7ff8b56844da79dfc8 and https://invent.kde.org/frameworks/plasma-framework/-/commit/b882b34d7b55975f679133ef86cfd12869e8bba5 Compiling plasma-framework 5.90 with those patches applied fixes the bug. [1] https://github.com/NixOS/nixpkgs/pull/158716#issuecomment-1034442574 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449432] Wayland: Activities panel resizes/moves active window
https://bugs.kde.org/show_bug.cgi?id=449432 --- Comment #4 from André M --- Would you have any hint on what could be causing this issue? Maybe some wrapper failing some .desktop or window class detection on the Activities/plasma panel? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449432] Wayland: Activities panel resizes/moves active window
https://bugs.kde.org/show_bug.cgi?id=449432 --- Comment #2 from André M --- plasma-framework and the rest of kf is at 5.90, self-compiled as well. Notice this is on NixOS, which is known to require some hacks, patches and wrappers to make apps and libs work with non-FSH systems, so if this bug can't be easily reproducible on other systems, this can be closed as downstream. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449432] Wayland: Activities panel resizes/moves active window
https://bugs.kde.org/show_bug.cgi?id=449432 André M changed: What|Removed |Added OS|Other |Linux CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449432] New: Wayland: Activities panel resizes/moves active window
https://bugs.kde.org/show_bug.cgi?id=449432 Bug ID: 449432 Summary: Wayland: Activities panel resizes/moves active window Product: kwin Version: 5.23.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: activities Assignee: kwin-bugs-n...@kde.org Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY On Wayland, Activities panel (Meta+Q) pushes and/or resizes active (and only active) window to the left, instead of just covering it, as the default (Breeze) Task Switcher. It also happens when switching activities through the Meta+Tab shortcut, as the panel is shown as well. Resizing windows constantly is a problem sometimes because it can re-arrange items inside, e.g. Kmail's columns are resized when window width is reduced briefly. Ideally, Activities panel should work the same as the Task switcher and as in X11, and just cover the window, leaving its geometry unchanged. STEPS TO REPRODUCE 1. On wayland, have a maximized window 2. Meta+Q to show Activities panel on the left edge OBSERVED RESULT Active window geometry is changed to avoid it overlapping with the Activities panel, resizing a maximized window or pushing an unmaximized one to the right EXPECTED RESULT Activities panel should be an overlay over the windows and desktop, as is the default Breeze Task Switcher, and windows geometry shouldn't change because of it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nixos unstable-small (shown as 22.05) KDE Plasma Version: 5.23.90 (self-compiled) KDE Frameworks Version: 5.90.0 Qt Version: 5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433709] Drop-down menus in Kate and Kwrite appear in the wrong place on Wayland Multi-Monitor and Multi-DPI
https://bugs.kde.org/show_bug.cgi?id=433709 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443968] When switching activities, sometimes a tiny "Plasma Desktop Workspace" window appears
https://bugs.kde.org/show_bug.cgi?id=443968 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #18 from André M --- This still happens for me in NixOS, Plasma 5.23.5 Wayland. The attached patch explicitly affects only X11, so not sure why this bug got closed if the initial summary states this affects Wayland. In my case, when trying to alternate between two activities with keyboard shortcut (Meta+Tab), sometimes this 1px-wide window shows up on the current activity and "cancels" the switch, bringing me back to the activity I was trying to depart from, which is very annoying. Clicking on activity pager never causes this problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435415] On NixOS, notifications, OSDs, and KRunner appear in task manager and steal focus
https://bugs.kde.org/show_bug.cgi?id=435415 André M changed: What|Removed |Added CC||andre.vma...@gmail.com --- Comment #12 from André M --- I can confirm this bug on NixOS, latest plasma5 5.22.5 & kf5.86. Interesting is that, even adding a very broad KWin rule for any type of window with Window class containing a substring of "org.kde.plasmashell" (detected properties) and forcing it to Skip taskbar and Extreme Window focus stealing prevention doesn't work, notifications still show up in taskbar and focus is stolen. Only on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 431763] Latte plasmoids lose current active window information when activity changes
https://bugs.kde.org/show_bug.cgi?id=431763 --- Comment #7 from André M --- Thank you very much for looking on it. Already tested here and everything is working smoothly now! Best regards. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 431763] Latte plasmoids lose current active window information when activity changes
https://bugs.kde.org/show_bug.cgi?id=431763
--- Comment #3 from André M ---
Created attachment 135379
--> https://bugs.kde.org/attachment.cgi?id=135379=edit
Latte layout with window-{title,appmenu}-git plasmoids
Hi, Michail, thank you very much for reaching out.
I just reproduced it on my Arch Linux testing system, fully up-to-date with
kde-unstable (but IIRC, this also happened on stable plasma).
Using latte-dock-git r4925.f27f9380-1, plasma5-applets-window-title-git
0.6.0.r18.g112a380-1 and plasma5-applets-window-appmenu-git
0.6.0.r0.g7886b78-1, and a new user with empty plasma/kde config (but some
default config upon launching plasma for the first time). I didn't add
window-buttons, due to not being able to compile it with plasma beta. I edited
the attached profile, and added a new activity.
Upon quitting Latte and relaunching it, I can see the correct Window Title and
AppMenu for e.g. a Dolphin window. As soon as I switch to the new activity
(using Meta+Tab shortcut, if it matters), and then back, I can't see the Title
anymore, only the Default activity title instead, and appmenu is empty (the
widget is there upon enabling panel edit, but no menu is shown). Closing and
relaunching Dolphin (or launching another kde app, like konsole) still don't
give me neither info. Quitting Latte and launching it again makes the info to
be shown, until first activity switch.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 431763] Latte plasmoids lose current active window information when activity changes
https://bugs.kde.org/show_bug.cgi?id=431763 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 431763] New: Latte plasmoids lose current active window information when activity changes
https://bugs.kde.org/show_bug.cgi?id=431763 Bug ID: 431763 Summary: Latte plasmoids lose current active window information when activity changes Product: lattedock Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: library Assignee: mvourla...@gmail.com Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY I have a Latte panel at the top with the Window Title, Window AppMenu and Window Buttons plasmoids. They work fine after Latte is initialized and no activity switch happened. But as soon as I change activities, they seem to not know anymore about the current activity, and even switching back to the previous activity can't get the window data on: Title shows only the (correct/current) activity name, Menu is hidden, buttons are hidden (as I've set up when no window is present). This doesn't seem to be a bug on the plasmoids themselves, since they're all affected by this, so maybe some backend/lib. Latte is master, both plasmoid's latest release and master are affected. STEPS TO REPRODUCE 1. Create a top panel, active on two activities 2. Put said plasmoids on it 3. Open a e.g Dolphin window and see the title, menu and buttons visible 4. Switch activities, open another e.g. Konsole window, no button, menu or title on the plasmoid, just the activity name 5. Switch back, still no info besides current activity name. OBSERVED RESULT Window info are gone from the three plasmoids EXPECTED RESULT Window info are properly fetched per activity, per active window. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux testing current (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Latte latest master (r4743.c4565998-1) plasma5-applets-window-title 0.6.0-1 plasma5-applets-window-appmenu 0.6.0.r36 plasma5-applets-window-buttons 0.8.1-2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430311] Intensive color selection broken as of 270d6ea3
https://bugs.kde.org/show_bug.cgi?id=430311 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430267] No option to display bold font as intense color
https://bugs.kde.org/show_bug.cgi?id=430267 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427091] Kmail gpg bad signature if From header contains non-ascii characters
https://bugs.kde.org/show_bug.cgi?id=427091 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427091] Kmail gpg bad signature if From header contains non-ascii characters
https://bugs.kde.org/show_bug.cgi?id=427091 --- Comment #1 from André M --- "To" field suffers of the same problem, making it very hard to write to contacts containing non-ascii characters in name (need to edit and normalize it before signing/sending mail). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427091] New: Kmail gpg bad signature if From header contains non-ascii characters
https://bugs.kde.org/show_bug.cgi?id=427091 Bug ID: 427091 Summary: Kmail gpg bad signature if From header contains non-ascii characters Product: kmail2 Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: andre.vma...@gmail.com Target Milestone: --- SUMMARY I was getting GPG Bad signature on my own sent messages (to my self, as a test), and also upon saving with Sign on save option set. After a lot of debugging, I could identify that if (at least) the From field contains non-ascii characters (in my case, my name), Kmail did change the field encoding **after** it got signed, giving that error on any client which would try to verify the OpenPGP/MIME attached signature. >From setting some debug options in GnuPG dialog, and created "dbgmd-1.sign" and "dbgmd-1.verify" files, I can see they differ in the former containing "From: =?UTF-8?B?QW5kcsOp?= Vitor de Lima Matos " header, while the final mail body and verify header got changed to "From: =?ISO-8859-1?Q?Andr=E9?= Vitor de Lima Matos " (the issue here then is on the "é" character). The issue doesn't happen if e.g. Subject header contains the non-ascii character, with both signed and final versions ending in the UTF-8 version. Workaround for now is to remove non-ascii characters from my identity's name. Not sure if it matters, but my Composer's charset list is set to [utf-8, iso-8859-1, us-ascii] STEPS TO REPRODUCE 1. Have given set of charset in that order in config 2. Create a new mail and set some non-ascii character in From field 3. Save/sign and/or send the email 4. See Bad signature error. OBSERVED RESULT Final email body (used to verify signature) re-encodes the From field AFTER it got signed, making signature verification fail. EXPECTED RESULT Any [re-]encoding (if needed) should be done BEFORE signing, and the body/headers should NEVER be touched after gpg signing was performed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux testing (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)
https://bugs.kde.org/show_bug.cgi?id=372116 André M changed: What|Removed |Added CC||andre.vma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
