[yakuake] [Bug 485069] Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 Andrew Ammerlaan changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485069] Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 --- Comment #1 from Andrew Ammerlaan --- Screen recording exceeds file size limit, so please download it from here instead: https://drive.google.com/file/d/13GDeljPf1S0Nkb-bh8-Dfc_EEIhluVPD/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485069] New: Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen
https://bugs.kde.org/show_bug.cgi?id=485069 Bug ID: 485069 Summary: Yakuake Wayland Plasma 6: window size wrong when closed on a smaller screen Classification: Applications Product: yakuake Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- SUMMARY In a multi screen setup the yakuake window will have half the size it should on the bigger screen if it was closed on the smaller screen. If the yakuake window is closed on the bigger screen there is no problem, if the yakuake window is *not* closed on the smaller screen there is also no problem. Wayland is affected, X11 was not tested. STEPS TO REPRODUCE 1. Have a multi-screen setup with different resolutions 2. Open yakuake on the smaller monitor, and close it with F12 3. Now open yakuake on the bigger monitor with F12 OBSERVED RESULT Half the window is shown, the rest of the window is gone/invisible/missing. EXPECTED RESULT We see the whole window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.15 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION See attached screen recording -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484238] New: kcm_sddm: sets empty CursorSize= resulting in invisible cursor at login
https://bugs.kde.org/show_bug.cgi?id=484238 Bug ID: 484238 Summary: kcm_sddm: sets empty CursorSize= resulting in invisible cursor at login Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_sddm Assignee: plasma-b...@kde.org Reporter: andrewammerl...@gentoo.org CC: k...@david-redondo.de, k...@davidedmundson.co.uk Target Milestone: --- SUMMARY Synchronizing Plasma settings to SDDM results in an invisible cursor in SDDM (wayland mode): STEPS TO REPRODUCE 1. Set some cursor size in plasma settings 2. Synchronize to SDDM 3. Restart OBSERVED RESULT We get: CursorSize= in /etc/sddm.conf.d/kde_settings.conf EXPECTED RESULT We should get: CursorSize=24 in /etc/sddm.conf.d/kde_settings.conf SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION Manually specifying the correct cursor size resolves the invisible cursor problem. A second related bug is probably that an empty setting should be considered invalid. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456696] "QSocketNotifier: Can only be used with threads started with QThread" everywhere
https://bugs.kde.org/show_bug.cgi?id=456696 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448216] User friendly names should be used for HDMI/DP devices
https://bugs.kde.org/show_bug.cgi?id=448216 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449263] Laptop screen not controllable when hdmi DDC monitor is plugged in
https://bugs.kde.org/show_bug.cgi?id=449263 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 446437] Applet misleadingly says "no vaults have been set up" instead of a real error message when kded module wasn't loaded is or crashing
https://bugs.kde.org/show_bug.cgi?id=446437 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467326] New: sddm-kcm should also synchronize CursorSize
https://bugs.kde.org/show_bug.cgi?id=467326 Bug ID: 467326 Summary: sddm-kcm should also synchronize CursorSize Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: andrewammerl...@gentoo.org CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY I was trying out the native wayland support in SDDM git and found that the cursor looked way to big. The problem was easily fixable by setting 'CursorSize=24' in sddm.conf.d. However, this should probably be synchronized as well when the user presses the "Apply Plasma Settings" button. STEPS TO REPRODUCE 1. Upgrade to sddm-git 2. Switch sddm to wayland with 'DisplayServer=wayland' 3. Synchronize settings from plasma OBSERVED RESULT Currently synchronizing the Plasma settings to sddm gives me this kde_settings.conf: [Autologin] Relogin=false Session= User= [General] HaltCommand=systemctl shutdown Numlock=on RebootCommand=systemctl reboot [Theme] Current=breeze CursorTheme=breeze_cursors Font=Noto Sans [GOOG],10,-1,5,50,0,0,0,0,0,Regular [Users] MaximumUid=65000 MinimumUid=1000 [X11] ServerArguments=-dpi 0 EXPECTED RESULT The CursorSize setting is also synchronized automatically, leading to a uniform cursor size when logging in and loading a Plasma session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 6.3.0_rc1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415286] KWin compositing makes Proton fullscreen games freeze after alt + tab
https://bugs.kde.org/show_bug.cgi?id=415286 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org --- Comment #16 from Andrew Ammerlaan --- > The issue is caused by setting KWin to always keep window thumbnails, not > just for shown windows. This problem is still present, and on wayland this setting is missing from the compositor settings so the solution might not be immediately obvious. However, switching to an X session, changing this setting, and then switching back to wayland does actually fix the problem. So somehow even though the setting is not show in wayland it does actually have an effect on wayland sessions (possibly because the proton games are running in Xwayland?). This might be a reason to unhide the setting in wayland sessions (See also Bug 446709) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461915] VRR enable/disable requires full modeset on i915 devices
https://bugs.kde.org/show_bug.cgi?id=461915 Andrew Ammerlaan changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/drm/intel/-/issues/7542 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461915] New: VRR enable/disable requires full modeset on i915 devices
https://bugs.kde.org/show_bug.cgi?id=461915 Bug ID: 461915 Summary: VRR enable/disable requires full modeset on i915 devices Classification: Plasma Product: kwin Version: 5.26.3 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- SUMMARY While Adaptive Sync worked fine with my AMD card, it does not on my Intel Arc card. After some debugging and help from the folks over at the i915 bug tracker, we found that the root of the problem is that amdgpu allows for enabling/disabling VRR on the fly, while i915 requires a full modeset to toggle this setting. Even when the "Adaptive Sync" setting is set to "Always" it does not work. It appears that kwin does not enable VRR immediately when it enables the monitor. While the "Automatic" setting might prove difficult with the i915 driver because of this requirement, it should be possible to get the "Always" setting working on i915 devices by enabling VRR immediately when enabling the monitor. Triggering a full modeset when changing the setting from "Never" to "Always" or the other way around would also be required. To fix the VRR behaviour when set to "Automatic" a full modeset would be required every time a full screen application is started or stopped. This might not be desirable, and therefore maybe a helpful pop-up note explaining that the "Automatic" setting does not currently work with i915 is a better idea. STEPS TO REPRODUCE 1. Start wayland session 2. Enable VRR 3. Start full screen application OBSERVED RESULT No syncing of the refresh rate EXPECTED RESULT The refresh rate of the monitor is synchronized to the content SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux, kernel 6.1.0-rc5 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION See also: https://gitlab.freedesktop.org/drm/intel/-/issues/7542 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] iGPU multi-monitor: Part of screen missing on secondary (integrated) GPU
https://bugs.kde.org/show_bug.cgi?id=461743 Andrew Ammerlaan changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #6 from Andrew Ammerlaan --- (In reply to Andrew Ammerlaan from comment #5) > (In reply to Zamundaaa from comment #4) > > Thanks for looking into it > > I'll move this bug report over to the kernel bug tracker. Never mind, the i915 upstream bug reporting instructions asked to test with the latest "drm-tip" of the kernel. Which I did, and the problem is now gone. So I guess it was indeed a kernel level bug, but it has already been fixed. Thanks again for your help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] iGPU multi-monitor: Part of screen missing on secondary (integrated) GPU
https://bugs.kde.org/show_bug.cgi?id=461743 --- Comment #5 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #4) > There's a ton of > > kwin_core: Provided presentation timestamp is invalid > in the log. As presentation times are always wrong I suspect we're looking > at a kernel bug. Thanks for looking into it I'll move this bug report over to the kernel bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] iGPU multi-monitor: Part of screen missing on secondary (integrated) GPU
https://bugs.kde.org/show_bug.cgi?id=461743 --- Comment #3 from Andrew Ammerlaan --- Created attachment 153697 --> https://bugs.kde.org/attachment.cgi?id=153697=edit wayland session log with QT_LOGGING_RULES=kwin_*.debug=true;kwin_libinput.debug=false (In reply to Zamundaaa from comment #2) > KWin no longer logs to a file but uses journald if available. You can get > the log of the current boot with > > journalctl --user-unit plasma-kwin_wayland --boot 0 Thanks! Full log with debugging variables QT_LOGGING_RULES=kwin_*.debug=true;kwin_libinput.debug=false attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] iGPU multi-monitor: Part of screen missing on secondary (integrated) GPU
https://bugs.kde.org/show_bug.cgi?id=461743 Andrew Ammerlaan changed: What|Removed |Added Summary|iGPU multi-monitor: Part of |iGPU multi-monitor: Part of |screen missing on secondary |screen missing on secondary |(integrated GPU)|(integrated) GPU -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] iGPU multi-monitor: Part of screen missing on secondary (integrated GPU)
https://bugs.kde.org/show_bug.cgi?id=461743 Andrew Ammerlaan changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #1 from Andrew Ammerlaan --- I was attaching a wayland session log, but I discovered that it was empty. Has the location of these log files changed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461743] New: iGPU multi-monitor: Part of screen missing on secondary (integrated GPU)
https://bugs.kde.org/show_bug.cgi?id=461743 Bug ID: 461743 Summary: iGPU multi-monitor: Part of screen missing on secondary (integrated GPU) Classification: Plasma Product: kwin Version: 5.26.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- Created attachment 153696 --> https://bugs.kde.org/attachment.cgi?id=153696=edit iGPU connected monitor on 1440x900@75 SUMMARY I recently replaced my (AMD) GPU with an Intel Arc. Unfortunately my motherboard does not like booting from it for weird reasons. This means I am (still) stuck using the integrated GPU as boot GPU and therefore require the dual-GPU multi-monitor feature. Though this used to work fine with the AMD dGPU + Intel iGPU combination, the Intel dGPU + Intel iGPU combination is producing a weird screen artefact on the monitors connected to the iGPU (see attached photo). SDDM (which runs in X on the iGPU) renders fine. The mouse does actually move over the missing black area, and I can even interact with buttons which are hidden by the black part. If I cycle through the supported resolutions the black area changes, and for specific resolutions even goes away. The problem is not with the monitor, cable, or output. I tested a different cable with a different monitor, on a DV-D instead of VGA output and got the exact same result. This might be a mesa rendering bug instead of a kwin bug? There is also a separate issue where kscreen/kwin sometimes does not list all supported resolutions/refresh rates for monitors connected to the Intel dGPU (e.g. 80, 100, 144 is missing, 60 is the highest option). However. I have not yet found the exact conditions that produce that bug, and it feels more like a kernel level problem so it might not be relevant here. STEPS TO REPRODUCE 1. Enable Multi-Monitor in BIOS on a Intel dGPu, Intel iGPU system 2. Connect a display to the dGPU and iGPU 3. Start a wayland session OBSERVED RESULT The bottom part of the monitors connected to the iGPU is "hidden" by a weird black part. EXPECTED RESULT The full display is visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (kernel 6.0.8, mesa 22.2.3) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Intel i9-9900KS UHD Graphics 630 (CFL GT2) + Intel Arc A770 Graphics (DG2) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460810] Accessing sftp remote file system sometimes causes "Internal Error"
https://bugs.kde.org/show_bug.cgi?id=460810 Andrew Ammerlaan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460810] Accessing sftp remote file system sometimes causes "Internal Error"
https://bugs.kde.org/show_bug.cgi?id=460810 --- Comment #5 from Andrew Ammerlaan --- Created attachment 153213 --> https://bugs.kde.org/attachment.cgi?id=153213=edit sshd debug log So I also checked the server side debug log, but it doesn't show any obvious failure message. What I did notice is that kio-sftp seems to be opening a bunch of new connections regularly, on different ports. Is it supposed to do that? Can it not just use a single connection? Perhaps it runs out of ports to use and then fails to make a new connection? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460810] Accessing sftp remote file system sometimes causes "Internal Error"
https://bugs.kde.org/show_bug.cgi?id=460810 --- Comment #4 from Andrew Ammerlaan --- Created attachment 153194 --> https://bugs.kde.org/attachment.cgi?id=153194=edit sshd config (In reply to Harald Sitter from comment #3) > Sounds a bit like the server just closed the connection at some point. Any > interesting configuration there? It does, though I don't really understand why. The configuration is not particularly interesting, it is more or less a standard configuration allowing only user key-based login (no passwords, no root login). Some forwarding and some ClientAlive options are enabled. Some env vars are accepted. Nothing very unusual I think, I've never had similar problems with other applications. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460810] Accessing sftp remote file system sometimes causes "Internal Error"
https://bugs.kde.org/show_bug.cgi?id=460810 --- Comment #2 from Andrew Ammerlaan --- Created attachment 153193 --> https://bugs.kde.org/attachment.cgi?id=153193=edit debug log (In reply to Harald Sitter from comment #1) > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves/ > Debugging_kio_sftp Thanks! These environment variables helped me get a proper log, which I attached. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 460810] New: Accessing sftp remote file system sometimes causes "Internal Error"
https://bugs.kde.org/show_bug.cgi?id=460810 Bug ID: 460810 Summary: Accessing sftp remote file system sometimes causes "Internal Error" Classification: Frameworks and Libraries Product: kio-extras Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- SUMMARY Accessing a remote file system using sftp initially works. However, after e.g. navigating into some folders, or copying some files it randomly stops working showing only "Internal Error". Sometimes going up a couple of folders fixes it, other times the only solution is to close dolphin and restart it. This has been happening for some time now. STEPS TO REPRODUCE 1. Open dolphin 2. Open a sftp remote file system 3. Interact with the file system a bit, copy some files, open some folders OBSERVED RESULT kf.kio.core: "Internal Error\nPlease send a full bug report at https://bugs.kde.org\nsftp://andrew@/the/folder/i/am/trying/to/access". EXPECTED RESULT I can reliably navigate and interact with my remote file system. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.9, kernel version 6.0.2 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I would be willing to debug this a bit further, but so far I've not been able to get kio to tell me anything more specific than "Internal Error". Possible related: https://bugs.kde.org/show_bug.cgi?id=295299 though this bug is ancient and marked as resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org --- Comment #31 from Andrew Ammerlaan --- What is interesting to me is that when only using a controller, the screen eventually turns off but it does not lock. I.e. controller input seems to prevent the "Lock screen automatically --> After X" setting from triggering but not the "Screen Energy Saving" setting. Do these two settings use different methods for checking input activity? Plasma 5.25.5 (wayland), frameworks 5.98.0, Qt 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 Andrew Ammerlaan changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #5 from Andrew Ammerlaan --- I just gave wayland a try again, but yakuake still has this issue for me. QT_QPA_PLATFORM=xcb is required to get yakuake to work the same as on x11. I dug a bit deeper into it and the root of the problem seems to be in the "Use Open/Retract action to focus window" setting, disabling this setting fixes the problem. With the setting enabled this bug occurs on wayland but not on x11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457851] Wayland: Screen corruption in full screen applications on secondary iGPU
https://bugs.kde.org/show_bug.cgi?id=457851 --- Comment #6 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #5) > Most likely the problem is caused by one of your GPUs not supporting > explicit modifiers. Can you test if that MR fixes it? Yes! It fixes the problem. Thanks for the very quick fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457851] Wayland: Screen corruption in full screen applications on secondary iGPU
https://bugs.kde.org/show_bug.cgi?id=457851 --- Comment #3 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #2) > Does this also happen with KWIN_DRM_NO_DIRECT_SCANOUT=1 set? It does not. With this variable in env fullscreen on wayland works just fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457851] Wayland: Screen corruption in full screen applications on secondary iGPU
https://bugs.kde.org/show_bug.cgi?id=457851 --- Comment #1 from Andrew Ammerlaan --- Created attachment 151303 --> https://bugs.kde.org/attachment.cgi?id=151303=edit wayland session log with QT_LOGGING_RULES=kwin_*.debug=true;kwin_libinput.debug=false -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=457851 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457851] New: Wayland: Screen corruption in full screen applications on secondary iGPU
https://bugs.kde.org/show_bug.cgi?id=457851 Bug ID: 457851 Summary: Wayland: Screen corruption in full screen applications on secondary iGPU Product: kwin Version: 5.25.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrewammerl...@gentoo.org CC: xaver.h...@gmail.com Target Milestone: --- SUMMARY Applications that go into full screen mode are not rendered correctly if the window is on a display connected to the secondary integrated Intel GPU. The screen gets corrupted, weird lines and colours all over, I would make a screenshot but the window looks fine in the screenshot. Full screen does work when the window is on a display connected to the primary AMD GPU. Most, but not all, applications are affected. Konsole works fine in full screen, VLC and Firefox do not. STEPS TO REPRODUCE 1. Start Plasma Wayland session 2. Open VLC 3. Press F11 to make the window full screen OBSERVED RESULT Screen is corrupted and unusable. EXPECTED RESULT The display shows the window in full screen mode without any screen corruption SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux running kernel 5.19.1 with mesa 22.1.6 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION See also Bug 433107 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode (need to restart Dolphin, plug and unplug device, etc)
https://bugs.kde.org/show_bug.cgi?id=336397 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #37 from Andrew Ammerlaan --- (In reply to Andrew Ammerlaan from comment #30) > Apparently I had a secondary hard > drive failure that happened to coincide with me running this debug script. > Made all the more confusing by that the debug LED that turned on at boot was > the one for the GPU. Replaced the faulty HDD, upgraded to 5.25.1. And indeed everything is working again. Thanks for your work on this! The bug that I briefly mentioned earlier where the screen gets corrupted when an application is full screen on a monitor connected to the iGPU is still present, but I'll open a new bug for that later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #30 from Andrew Ammerlaan --- (In reply to Andrew Ammerlaan from comment #29) > For some reason my computer is acting very 'weird' after running this script > and rebooting. It's very slow to start up now, and the system POST is no > longer displayed on the screen. Never mind about this, it is unrelated. Apparently I had a secondary hard drive failure that happened to coincide with me running this debug script. Made all the more confusing by that the debug LED that turned on at boot was the one for the GPU. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #29 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #13) > So (In reply to VesperLlama from comment #10) > > New dmesg-drm-debug.log > now contains messages about commits failing with EINVAL (-22), but still > nothing about the reason for it, or the expected messages about it. > > (In reply to Tony Stipanic from comment #11) > I will try to get useful logs and attach it asap. > Please do! I don't know how much logging NVidia does, but it may yield > useful information either way. > > @Andrew Ammerlaan if you also run the script from comment #3 that might help > as well. > > Some general things you could all try is using the environment variables > (one by one) > KWIN_DRM_USE_MODIFIERS=0 > KWIN_DRM_PREFER_COLOR_DEPTH=24 > KWIN_DRM_NO_AMS=1 I uploaded the logs from the debug script, plus the same logs with the environment variables you suggested. For some reason my computer is acting very 'weird' after running this script and rebooting. It's very slow to start up now, and the system POST is no longer displayed on the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #28 from Andrew Ammerlaan --- Created attachment 149857 --> https://bugs.kde.org/attachment.cgi?id=149857=edit dmesg, USE_MODIFIERS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #27 from Andrew Ammerlaan --- Created attachment 149856 --> https://bugs.kde.org/attachment.cgi?id=149856=edit kwin debug log, USE_MODIFIERS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #26 from Andrew Ammerlaan --- Created attachment 149855 --> https://bugs.kde.org/attachment.cgi?id=149855=edit dmesg, PREFER_COLOR_DEPTH -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #25 from Andrew Ammerlaan --- Created attachment 149854 --> https://bugs.kde.org/attachment.cgi?id=149854=edit kwin debug log, PREFER_COLOR_DEPTH -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #24 from Andrew Ammerlaan --- Created attachment 149853 --> https://bugs.kde.org/attachment.cgi?id=149853=edit dmesg, NO_AMS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #23 from Andrew Ammerlaan --- Created attachment 149852 --> https://bugs.kde.org/attachment.cgi?id=149852=edit kwin debug log, NO_AMS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #22 from Andrew Ammerlaan --- Created attachment 149851 --> https://bugs.kde.org/attachment.cgi?id=149851=edit dmesg, no extra env vars -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #21 from Andrew Ammerlaan --- Created attachment 149850 --> https://bugs.kde.org/attachment.cgi?id=149850=edit kwin debug log, no extra env vars -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #44 from Andrew Ammerlaan --- In version 5.25 this is broken again. After login the monitor connected to the AMDGPU turns itself off, and the monitor connected to the iGPU continues to display the SDDM login screen. If I switch to a tty and back I get a black screen on all monitors but the mouse is now visible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417575] Spectacle thinks that OBS Studio and VokoscreenNG screen recorders are not installed but they are
https://bugs.kde.org/show_bug.cgi?id=417575 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 --- Comment #3 from Andrew Ammerlaan --- (In reply to Oded Arbel from comment #2) > Recently there were various changes to how Yakuake handles opening and > closing on Wayland and X11 - can you please check if this is still an issue? Still an issue with version 21.08.3, "QT_QPA_PLATFORM=xcb yakuake" works as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #43 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #42) > The commit is only in git master / upcoming 5.23 Alrighty, I see, I'll wait a bit more then and test again later :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #41 from Andrew Ammerlaan --- Created attachment 141519 --> https://bugs.kde.org/attachment.cgi?id=141519=edit wayland-session-log-kwin-5.22.5 After upgrading to version 5.22.5 this is sadly still not quite working (though it was working earlier when I tested the MR). The monitor connected to the AMDGPU works and one of the monitors on the iGPU (the right one). But the others still continue to show the SDDM screen after logging in. Wayland log attached. I'm seeing a bunch of these: kwin_core: Provided presentation timestamp is invalid: 154666 (current: 154675) kwin_wayland_drm: Atomic request failed to commit: Invalid argument kwin_wayland_drm: Atomic test commit failed. Aborting present. Furthermore, the issue where the monitor on the AMDGPU turns black for about a second or two after logging in is back :( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #39 from Andrew Ammerlaan --- (In reply to Zamundaaa from comment #38) > Could you check if the monitor still turns off on login now? I added a > commit that might resolve that Perfect, it works flawlessly now. There's a very nice transition from sddm to black to a fade-in of the splash screen, it is the same on all monitors! Thank you very much for your efforts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #36 from Andrew Ammerlaan --- (In reply to Andrew Ammerlaan from comment #35) > And one other small thing I noticed is that after hotunplugging and > hotplugging one of the monitors the widgets and taskbar on that monitor are > gone (i.a.w. it detects it as if it were a new monitor and it doesn't > restore the settings) After looking at the logs, it appears that it detects the hotplugged monitor (HDMI-A-2-HKC-TV) multiple times instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #35 from Andrew Ammerlaan --- And one other small thing I noticed is that after hotunplugging and hotplugging one of the monitors the widgets and taskbar on that monitor are gone (i.a.w. it detects it as if it were a new monitor and it doesn't restore the settings) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #34 from Andrew Ammerlaan --- Created attachment 140219 --> https://bugs.kde.org/attachment.cgi?id=140219=edit wayland-session-log (patch applied) Awesome, now it works! The monitor connected to the AMDGPU does still go to black before eventually showing the splash screen. It stays black for about a second (the other monitors are already showing the splash screen at this stage). Hot(un)plugging works. However, when hotunplugging a monitor all windows are moved to the monitor connected to the AMDGPU (which is marked as the "primary" monitor, i.e. monitor 1). And when hotplugging a monitor all windows are moved to the monitor that just connected. (But maybe this behaviour is intentional?) There is also Bug 438508 which is possibly related since it only occurs when using iGPU multimonitor. If I recall correctly, it didn't happen when I tested yesterday, but it is happening now so perhaps it is maybe related to these changes? Thank you for working on this! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Attachment #140194|text/plain |application/x-tar mime type|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #32 from Andrew Ammerlaan --- Created attachment 140194 --> https://bugs.kde.org/attachment.cgi?id=140194=edit wayland session log after applying the patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #31 from Andrew Ammerlaan --- Created attachment 140193 --> https://bugs.kde.org/attachment.cgi?id=140193=edit wayland session log before applying patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #30 from Andrew Ammerlaan --- We're getting close, Without the patch I get a working display on the monitor connected to the AMDGPU, and on *one* of the monitors connected to the iGPU (the one that was problematic before, but that might be a coincidence). With the patch I get a working display on *all* monitors connected to the iGPU. However, the monitor connected to the AMDGPU stays black. If I go to the Display Settings the monitor is there. If I disabled and enable this monitor, all of the displays hang/freeze but I do see the desktop pop up on that monitor before it freezes and the screen corrupts. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #28 from Andrew Ammerlaan --- Created attachment 140080 --> https://bugs.kde.org/attachment.cgi?id=140080=edit wayland-session-log (In reply to Zamundaaa from comment #27) > crash should be fixed (at least it works with vkms) Yes the crash is fixed now, Thanks. After applying the patch from your Merge Request I get a proper display on one of the monitors connected to the iGPU, the other two continue to display the SDDM screen. The monitor connected to the AMDGPU (DVI-D-1) turns black. I can move my mouse onto those monitors, and they are properly shown in Display Settings (correct configuration and correct resolution etc). I see some "Invalid argument" in the logs, so perhaps that is the cause. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #25 from Andrew Ammerlaan --- Created attachment 140018 --> https://bugs.kde.org/attachment.cgi?id=140018=edit kwin_wayland backtrace (In reply to Zamundaaa from comment #24) > KWin crashes, apparently when starting to render. Can you provide a > backtrace? Here's the backtrace, I hope it is helpful -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #23 from Andrew Ammerlaan --- Created attachment 140013 --> https://bugs.kde.org/attachment.cgi?id=140013=edit wayland-session-log (In reply to Zamundaaa from comment #22) > Patches the merge request depend on have been merged now, and I updated the > merge request to the new code. Could you test it again? It should in theory > work the same but it would be good to make sure. After upgrading to the latest live version wayland is refusing to start (both with and without the patch from your Merge Request). The screen flashes fast and frequently, and eventually returns to SDDM (does not matter if the port that was problematic before is connected or not). Wayland session log is attached. X does still work though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438508] New: wayland, iGPU multi-monitor: right click menu displaced to edge of monitor
https://bugs.kde.org/show_bug.cgi?id=438508 Bug ID: 438508 Summary: wayland, iGPU multi-monitor: right click menu displaced to edge of monitor Product: kwin Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andrewammerl...@gentoo.org Target Milestone: --- SUMMARY Right clicking in e.g. konsole makes the right click menu show up near the screen edge instead of at the cursor location. - This appears to occur for a lot of KDE applications, but not for GTK applications, some Qt applications appear unaffected as well (e.g. SciDaVis) - Launching e.g. konsole with QT_QPA_PLATFORM=xcb fixes the issue. - The right click menus of the desktop/plasmashell are not effected, nor the right click menu's of the window title bar. This only occurs when right clicking *inside* the application. (e.g. right click the konsole titlebar: normal, right click inside the konsole window: menu is all the way on the edge of the screen) - It only occurs in wayland - It only occurs on my PC which is using the iGPU multi-monitor feature (i.a.w. the output ports of the integrated Intel GPU are used as well as the output ports of the dedicated GPU). It does not occur on my laptop which has only the Intel GPU. STEPS TO REPRODUCE 1. Start wayland session on a computer with iGPU multi monitor enabled 2. Start any KDE application (e.g. konsole, dolphin, kile, kate) 3. Right click anywhere inside the appliction OBSERVED RESULT The right click menu pops up on the right edge of the active monitor EXPECTED RESULT The right click menu pops up at the cursor position, as it does for all other applications. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.12.6 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Attachment #137515|0 |1 is obsolete|| --- Comment #20 from Andrew Ammerlaan --- Created attachment 137532 --> https://bugs.kde.org/attachment.cgi?id=137532=edit wayland session log (patch applied) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #19 from Andrew Ammerlaan --- Good News! You're patch works! I am writing this in a fully functioning wayland session. All monitors now work as expected. There seems to be a small issue on shutdown which may or may not be related. Sometimes the monitors connected to the iGPU retain their contents after the session has quit and the shutdown process has started. Some services fail to stop (e.g. bluetooth), which indicates to me that the session might be (partially) re-spawning when it shouldn't. But this could very well be an unrelated issue. Anyway with your patch my setup works with wayland! Looks like I will finally be able to join the rest of the world in the future that is wayland :D Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Attachment #137512|0 |1 is obsolete|| --- Comment #17 from Andrew Ammerlaan --- Created attachment 137515 --> https://bugs.kde.org/attachment.cgi?id=137515=edit wayland session log (patch applied) (In reply to Zamundaaa from comment #16) > Yes, very useful. https://invent.kde.org/plasma/kwin/-/merge_requests/847 > should fix that Awesome, this indeed fixed it :) However, the original issue is not quite fixed yet (though there is definitely some progress with this patch). If I apply the patch the problem becomes sort of inverted. Now the monitors connected to the iGPU work just fine (even the problematic port!). However, the monitors connected to the AMDGPU turn off after logging in. The kscreen config window does detect and display them correctly and they are marked as enabled (though the monitor itself says "No Signal"). If I disable and enable those monitors in the kscreen config window, they do turn on but the desktop completely freezes shortly afterwards. Without the patch the original behaviour described in the first comment is restored (AMDGPU monitors work, but iGPU monitors display SDDM screen). I don't have a coredump this time because there is no crash, though I have attached the wayland session log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Attachment #137498|0 |1 is obsolete|| --- Comment #15 from Andrew Ammerlaan --- Created attachment 137512 --> https://bugs.kde.org/attachment.cgi?id=137512=edit wayland session log (patch applied) I hope this is useful -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #14 from Andrew Ammerlaan --- Created attachment 137511 --> https://bugs.kde.org/attachment.cgi?id=137511=edit SIGSEGV backtrace kwin_wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #12 from Andrew Ammerlaan --- I just tested without the patch, and then it still crashes. So the problem does not seem to be with the patch necessarily but with some other change in the live git version. Perhaps I just got unlucky and synced it while it was in a broken state. I'm not sure how I could test this more properly, any suggestions? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #11 from Andrew Ammerlaan --- Created attachment 137498 --> https://bugs.kde.org/attachment.cgi?id=137498=edit wayland log with the patch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #10 from Andrew Ammerlaan --- To apply the patch successfully I had to use the latest version from git (for kwin and some other packages). The patch does not apply to the 5.21.4 release. After upgrading and applying the patch, a X11 session still works. However, now wayland does not work at all, it just flashes the screen a bit on the monitors connected to the AMDGPU and then crashes. The monitors on the iGPU continue to display the SDDM screen, now this happens irrespective of whether the problematic port is connected or not. I am not sure if the problem is with the patch from the Merge Request, or with the upgrade to the latest version from git. The log doesn't seem to show anything helpful, but I'll attach it anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU/AMDGPU multi-monitor keeps displaying the SDDM screen if iGPU-DisplayPort is connected
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Summary|Wayland: iGPU multi-monitor |Wayland: iGPU/AMDGPU |keeps displaying the SDDM |multi-monitor keeps |screen |displaying the SDDM screen ||if iGPU-DisplayPort is ||connected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #6 from Andrew Ammerlaan --- By (un)plugging some of the monitors I found something interesting. The problem is with HDMI-1-2(which contrary to what the name suggests is a DisplayPort), if this iGPU-port is connected I run into the problem I described. - If this port is not connected everything works fine (2 remaining on the iGPU, 4 total). - If I move the monitor that was connected to this port, to a port on the AMDGPU everything is also fine (same total number of monitors, 5) - If I remove one of the other monitors connected to the iGPU, I still have the same problem. - If I remove all monitors connected to the iGPU, but leave only this port connected, I still have the same problem. - If I connect a different monitor to this port, I still have the same problem (therefore, it is not specific to that monitor, it is the port) I don't know if this is related, but I've had other issues with this specific port as well. If this port is connected *and* the iGPU is the boot-GPU (no matter what other things are connected) the system POST is not displayed at all, and the BIOS and Grub are inaccessible. In this situation the monitors only start showing something once the linux kernel takes over the framebuffer. And for some reason the naming of the ports on the iGPU is all messed up (and has been for as long as I had this computer), DisplayPort is named HDMI-1-2, VGA is named DP-1-5, DVI is named HDMI-1-3 but that is probably a kernel thing and unrelated. I should add that this port is connected through a DisplayPort to HDMI adapter, since I do not have a DisplayPort capable monitor I cannot test without it. So whenever I say that this port 'is connected' it is implied that this is through this converter. That being said, this port works just fine in X, so there is still some bug here. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] New: Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 Bug ID: 433171 Summary: Yakuake Opens, but does not close under wayland Product: yakuake Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: andrewammerl...@riseup.net Target Milestone: --- SUMMARY When running a wayland session, yakuake does not close when pressing F12. If it has not yet been opened, it does open correctly when pressing F12. It works just fine when running with Xorg. STEPS TO REPRODUCE 1. Start yakuake 2. Press F12, window opens 3. Press F12 again, window does not close OBSERVED RESULT Window does not close upon pressing F12 after it has been opened. EXPECTED RESULT Yakuake closes again when pressing F12, just like it does in a Xorg session SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-gentoo OS Type: 64-bit Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Radeon RX 590 Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #4 from Andrew Ammerlaan --- Small correction, I got: [] [] [ AMDGPU2] [] [] _ ___ ][][ ] ][][ ] iGPU2][ AMDGPU1 ][iGPU3 ] ][][ ] ][][___] [] [] [ iGPU1 ] [] [] My previous sketch had iGPU1 twice, which is of course wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #3 from Andrew Ammerlaan --- Created attachment 135852 --> https://bugs.kde.org/attachment.cgi?id=135852=edit wayland session log with env variables -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 --- Comment #2 from Andrew Ammerlaan --- I re-tested with the environment variables you suggested, and also recompiled, kwin, kscreen and libinput with the debug symbols. This time it did not crash when trying to change the resolution. However, there was no visible effect of changing the resolution on the monitors connected to the iGPU. It did crash when I tried to enable a monitor connected to the iGPU that I had previously disabled. However, this time it did respawn. Something I noticed now, that I did not notice last time, is that the monitor configuration is not what the kscreen configuration window says it is. I set it to: [] [] [ AMDGPU2] [] [] _ ___ ][][ ] ][][ ] iGPU1][ AMDGPU1 ][iGPU2 ] ][][ ] ][][___] [] [] [ iGPU3 ] [] [] But got instead: [] [] [ AMDGPU2] [] [] _ ___ ][][ ] ][][ ] iGPU3][ AMDGPU1 ][iGPU1 ] ][][ ] ][][___] [] [] [ iGPU1 ] [] [] Disabling a monitor connected to the iGPU has no effect on what is shown on the monitor, it does however prevent the mouse from moving onto that monitor. However the monitor that is set as disabled is not the monitor onto which the mouse can no longer move. E.g. disabling iGPU1, prevents the mouse from moving onto iGPU2. However, the mouse can actually still move onto iGPU1. To me it looks like the monitors are somehow mixed up, the information that is shown about each monitor is correct (e.g. name, resolution, refresh rate). However, applying operations, such as disabling or moving, to that monitor in the configuration window will actually apply these operations to a different monitor. I will attach the new log, something that caught my eye is this: kwin_wayland_drm: Atomic request failed to commit: Invalid argument and this: kwin_wayland_drm: Atomic request failed to commit: Permission denied The log is littered with these. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 433107] Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net, ||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 433107] New: Wayland: iGPU multi-monitor keeps displaying the SDDM screen
https://bugs.kde.org/show_bug.cgi?id=433107 Bug ID: 433107 Summary: Wayland: iGPU multi-monitor keeps displaying the SDDM screen Product: KScreen Version: 5.21.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: andrewammerl...@riseup.net Target Milestone: --- Created attachment 135787 --> https://bugs.kde.org/attachment.cgi?id=135787=edit wayland session log SUMMARY After upgrading to 5.21.0 monitors connected to the iGPU are detected (yay) (bug 417323), but all they display is the SDDM screen which stayed there after login. The cursor is visible, I can move windows onto those monitors, but the SDDM screen still gets displayed over them so they are not visible. Rearranging the monitors works, but still the SDDM screen is displayed on top of everything else (including the taskbar etc). Trying to change the resolution makes *everything* crash (kwin, plasmashell, xwayland, etc.) without re-spawning. STEPS TO REPRODUCE 1. Start wayland session with monitor connected to one of the iGPU's ports OBSERVED RESULT The SDDM screen stays visible on the monitors connected to the iGPU, monitors connected to the AMDGPU work fine. I cannot interact with this screen, nor can I see anything that is put below it. EXPECTED RESULT The monitors connected to the iGPU work the same as those connected to the AMDGPU. The SDDM screen is replaced by the splash screen and eventually the desktop. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-gentoo OS Type: 64-bit Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Radeon RX 590 Series ADDITIONAL INFORMATION ~/.local/share/sddm/wayland-session.log attached as requested. How do I obtain the backtrace of kwin_wayland? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 417323] iGPU multi-monitor support missing
https://bugs.kde.org/show_bug.cgi?id=417323 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net --- Comment #5 from Andrew Ammerlaan --- After upgrading to 5.21.0 monitors connected to the iGPU are detected (yay), but all they display is the SDDM screen which stayed there after login. The cursor is visible, I can move windows onto those monitors, but the SDDM screen still gets displayed over them so they are not visible. Rearranging the monitors works, but still the SDDM screen is displayed on top of everything else (including the taskbar etc). Trying to change the resolution makes *everything* crash (kwin, plasmashell, xwayland, etc.) without re-spawning. Operating System: Gentoo Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-gentoo OS Type: 64-bit Graphics Platform: X11 (I reverted back to X for now) Processors: 12 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Radeon RX 590 Series -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433013] New System Monitor in 5.21 crashes on startup in KSysGuard::CGroupDataModel::update()
https://bugs.kde.org/show_bug.cgi?id=433013 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 431994] per display ddcutil brightness control with -DHAVE_DDCUTIL
https://bugs.kde.org/show_bug.cgi?id=431994 --- Comment #1 from Andrew Ammerlaan --- Tried this on another device (a laptop), it works but if an external monitor is connected it is no longer possible to control the brightness of the internal laptop screen. Which is slightly annoying, because now I can control the brightness of either the laptop screen or the external screen but not both. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 431994] New: per display ddcutil brightness control with -DHAVE_DDCUTIL
https://bugs.kde.org/show_bug.cgi?id=431994 Bug ID: 431994 Summary: per display ddcutil brightness control with -DHAVE_DDCUTIL Product: Powerdevil Version: 5.20.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrewammerl...@riseup.net Target Milestone: --- SUMMARY I'm having some problems with the brightness control of my displays. And I'm pretty sure the reason is that one of my displays supports DDC communication and one does not. After some testing and reading I discovered that the brightness control seems to control all monitors at once, and since one of the displays does not support DDC communication the brightness control fails completely. One display is a Wacom One drawing tablet which I need for (online) teaching. This particular display does not have any buttons or anything to control the brightness, the only way to control this is using ddcutil. It would be awesome if we could have brightness control on a per display basis, which would solve my issue and let me control the brightness of this display without having to use the terminal. STEPS TO REPRODUCE 1. install ddcutil 2. Compile powerdevil with -DHAVE_DDCUTIL 3. reboot OBSERVED RESULT No brightness slider in the plasma Battery and Brightness applet EXPECTED RESULT A brightness slider for each display that supports DDC communication. (and obviously no slider for displays that do not.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.10.9 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413203] Some notifications don't disappear after timeout
https://bugs.kde.org/show_bug.cgi?id=413203 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net --- Comment #1 from Andrew Ammerlaan --- I have the same problem, this happens for me with notifications from KDE Connect, and with notifications from Firefox (Whatsapp Web). Other notifications do disappear after the timeout. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427677] New: Feature Req: allow setting window position relative to specific screen
https://bugs.kde.org/show_bug.cgi?id=427677 Bug ID: 427677 Summary: Feature Req: allow setting window position relative to specific screen Product: kwin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: andrewammerl...@riseup.net Target Milestone: --- SUMMARY We can already set window rules for the (absolute) position of a window in the whole X screen, we can also set a specific screen a window should be on. What we cannot (yet) do is set a specific position on a specific screen for a window. This is useful on setups with a varying monitor configuration, e.g. laptops that sometimes have a external monitor plugged in. If this external monitor is set to be left of or above the internal monitor, the physical position of the upper left corner (0,0) of the X screen will be changed, and therefore the windows with position rules will be put into a different position than if the external monitor were not connected. What I suggest is adding e.g. a drop down menu to the 'Position' rule, where the user can select e.g, the following options: - Absolute (which is the current behaviour) - Monitor/Screen 0 (e.g. if the position is set to 960,0 the window will be halfway the first monitor if it is Full HD) - Monitor/Screen 1 - etc ... I imagine that in the background this would work by determining first the position of the monitor the window should be on, and then adding on top of this the user specified (relative) position which would give the (absolute) position the window should be at. E.g. I want window foo to be on screen 2 (the third monitor) which is at position 3520x0, I want the window to be 200 pixels from the left side of the monitor. Now I would have to set the position of the window to 3720x0, and it will only work in this specific monitor configuration. What I suggest is allowing the user to set the position to '200x0 on screen 2' instead. In the background the absolute position would be calculated by getting the position of screen 2 (3520x0) and adding the user specified position (200x0) to get (3720x0) which would then be where the window will be positioned. The advantage of this is that this will still work as intended if the position of screen 2 is changed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.8.14-gentoo KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427677] Feature Req: allow setting window position relative to specific screen
https://bugs.kde.org/show_bug.cgi?id=427677 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 415749] When selecting multiple scan areas only first area gets scanned ("Automatic Document Feeder")
https://bugs.kde.org/show_bug.cgi?id=415749 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net --- Comment #1 from Andrew Ammerlaan --- I think I encountered the same (or at least very similar) issue with my Brother MFC-j5320dw on Gentoo Linux. When the "Preview before saving" feature in the settings is enabled, and while trying to scan multiple documents (Using the automatic document feeder), only the first document will get scanned. After the first document has been scanned and after pressing the save button, the rest of the documents will just get pulled through. Disabling the "Preview before saving" feature fixes the issue, and makes the scanner scan multiple documents as expected using the ADF. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420368] Microphone input ports not named correctly
https://bugs.kde.org/show_bug.cgi?id=420368 Andrew Ammerlaan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Andrew Ammerlaan --- Fixed after upgrade to 5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420368] Microphone input ports not named correctly
https://bugs.kde.org/show_bug.cgi?id=420368 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420368] Microphone input ports not named correctly
https://bugs.kde.org/show_bug.cgi?id=420368 --- Comment #2 from Andrew Ammerlaan --- Created attachment 127737 --> https://bugs.kde.org/attachment.cgi?id=127737=edit Nothing displayed if input is set to Line In -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420368] Microphone input ports not named correctly
https://bugs.kde.org/show_bug.cgi?id=420368 --- Comment #1 from Andrew Ammerlaan --- Created attachment 127736 --> https://bugs.kde.org/attachment.cgi?id=127736=edit pavucontrol shows labels correctly -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420368] New: Microphone input ports not named correctly
https://bugs.kde.org/show_bug.cgi?id=420368 Bug ID: 420368 Summary: Microphone input ports not named correctly Product: systemsettings Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: now...@gmail.com Reporter: andrewammerl...@riseup.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127735 --> https://bugs.kde.org/attachment.cgi?id=127735=edit screenshot of systemsettings SUMMARY My PC audio card has three input ports (Rear Microphone, Front Microphone and Line In). However, systemsettings shows only 2, and they are labelled incorrectly. (See screenshot) Pavucontrol does show all three. (see next screenshot) Now this is where it gets interesting: - If I set the input to 'Front microphone' in pavucontrol, Systemsettings will (incorrectly) tell me it is set to 'Rear microphone' - If I set the input to 'Rear microphone' in pavucontrol, Systemsettings will (incorrectly) tell me it is set to 'Line In' - If I set the input to 'Line In' in pavucontrol, Systemsettings will not show anything in that field. (see third screenshot) It looks like the labels of the inputs are all displaced by 1 (which makes me think that it might be an array index problem). The plasma volume control applet has the exact same behaviour. (it and systemsettings show the same (wrong) label for the set input). For the output devices I have the 'Line Out' and the 'Headphones' ports. Pavucontol shows me a drop-down menu where I can select this, KDE systemsettings does not. (presumably because it automatically switches to headphones if it is plugged in, so a menu to manually select this would not be useful?) My hunch is that the drop-down menu where you can select the input port tries to skip the 'Front microphone' entry similar to how it skips the 'Headphones' entry. Which works fine on my laptop, which has only 2 input ports (built in microphone, and the microphone jack) and thus has nothing to select, but somehow messes up the input port labels on my PC which has 3 input ports. STEPS TO REPRODUCE 1. Have 3 input ports on computer 2. Start plasma 3. Open systemsettings and go the the audio section OBSERVED RESULT Labels of input ports are displaced by 1: 'Front Microphone' is displayed as 'Rear Microphone' 'Rear Microphone' is displayed as 'Line In' 'Line In' is not displayed EXPECTED RESULT Labels in selection drop down box are correct: 'Front Microphone' is displayed as 'Front Microphone' 'Rear Microphone' is displayed as 'Rear Microphone' 'Line In' is displayed as 'Line In' SOFTWARE/OS VERSIONS Linux: 5.6.5-gentoo KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 414322] Yakuake wont show with dual monitor setup stacked on top of each other
https://bugs.kde.org/show_bug.cgi?id=414322 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389845] FN keys for screen brightness no longer work
https://bugs.kde.org/show_bug.cgi?id=389845 --- Comment #1 from Andrew Ammerlaan <andrewammerl...@riseup.net> --- Same problem on gentoo linux: kernel: 4.15.1-gentoo; amd64 GPU: AMD Radeon HD 7670M SDDM version 0.17.0 Ddcutil version 0.8.6 acpid version 2.0.28 xorg-server version 1.19.6 xf86-video-ati version 7.10.0 I can add more info upon request -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389845] FN keys for screen brightness no longer work
https://bugs.kde.org/show_bug.cgi?id=389845 Andrew Ammerlaan <andrewammerl...@riseup.net> changed: What|Removed |Added CC||andrewammerl...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
