[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 --- Comment #27 from Jan Keith Darunday --- (In reply to Nate Graham from comment #26) > Where did ~/.config/plasma-workspace/env/kwin_env.sh come from? Did you > create it and populate it, or did your distro do that? Ah, It's been a while but I believe I put it there myself. I'm not sure about others that had egl set in their kwinrc though. It worked well for me and I feel like I've had a more stable fps when I had it enabled until it stopped working at 5.23. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 Jan Keith Darunday changed: What|Removed |Added Version|5.23.2 |5.25.5 --- Comment #25 from Jan Keith Darunday --- I have retested this on both 5.25.4 and 5.25.5, and I can observe the same bug. Running kwin_x11 --replace in the terminal shows me the ff. error whenever I try to enable compositing using Alt+Shift+F12: kwin_scene_opengl: Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()" This does not happen when I comment out KWIN_OPENGL_INTERFACE=egl in my ~/.config/plasma-workspace/env/kwin_env.sh file Operating System: Arch Linux KDE Plasma Version: 5.25.4 and 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.6-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 Jan Keith Darunday changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Product|plasmashell |kwin Component|general |egl Target Milestone|1.0 |--- Version|5.23.0 |5.23.2 --- Comment #20 from Jan Keith Darunday --- Let's not call disabling egl a fix since it's just a workaround. Someone might skim through and accidentally mark this as resolved. The issue remains with kwin 5.23.2. Also noting here that the 'product' field of this bug seems to be wrongly set to plasmashell instead of kwin so that might cause this to be assigned to the wrong person. Not sure if I should update it. Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.13-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 --- Comment #12 from Jan Keith Darunday --- To follow up on my previous comment: I downgraded to kwin 5.23.0 and it had the same bug. Last kwin version that worked for me was 5.22.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 Jan Keith Darunday changed: What|Removed |Added CC||jkcdarun...@gmail.com --- Comment #11 from Jan Keith Darunday --- I'm not sure if this is directly related but I have a similar issue that occured after upgrading to 5.23.1. The same error appears but I can use my system without compositing. It also only happens when I set KWIN_OPENGL_INTERFACE=egl. When this environment variable is unset, kwin compositing works fine. However, the egl option significantly reduces stutters for me and it has been working well until my last upgrade so I would prefer it to work. Operating System: Arch Linux KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.13-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439123] Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 --- Comment #1 from Jan Keith Darunday --- Created attachment 139642 --> https://bugs.kde.org/attachment.cgi?id=139642=edit Screenshot showing what happens when you shift+delete in th old system monitor -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439123] New: Shift+Delete for sending SIGKILL does not work
https://bugs.kde.org/show_bug.cgi?id=439123 Bug ID: 439123 Summary: Shift+Delete for sending SIGKILL does not work Product: plasma-systemmonitor Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jkcdarun...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In the original system monitor, selecting a process and pressing shift+delete (instead of just delete) shows a window confirming the killing of the process (not just SIGTERM). In the new system monitor, the support for sending SIGTERM for delete was recently added but the support for shift+delete for sending SIGKILL wasn't causing a feature regression between the old and new system monitor. STEPS TO REPRODUCE 1. Go to plasma-systemmonitor 2. Go to processes 3. Select a process 4. Press delete (works) and then ok 5. Press shift+delete (does nothing) OBSERVED RESULT Pressing delete and accepting the popup sends SIGTERM Pressing shift+delete does nothing EXPECTED RESULT Pressing shift+delete should show a force kill popup saying that it will "immediately and forcibly kill" the process in bold then send a SIGKILL when accepted SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.12-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Attached screenshot shows pressing delete and shift+delete in the old system monitor. Both Delete and Shift+Delete also work for KSysguard -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 435985] VNC via SSH tunnel always asks for password even though public key authentication is set-up
https://bugs.kde.org/show_bug.cgi?id=435985 --- Comment #2 from Jan Keith Darunday --- Created attachment 137801 --> https://bugs.kde.org/attachment.cgi?id=137801=edit Video showing that I can SSH using public key but krdc won't Hi, I have the same setup. My local ~/.ssh/id_rsa.pub is in the authorized_keys of the remote server so I'm currently able to do passwordless SSH. I've attached a video showing that I can do passwordless SSH using the SSH command while KRDC still asks for a password when connecting to the same server. Note that I added vpnserver.test.com in my /etc/hosts so that I don't have to disclose the server IP but connecting via IP and the correct hostname shows the same error. I'm also able to do local tunneling via ssh -R 5901:127.0.0.1:5901 and successfully connect to localhost:5901 using KRDC so I can confirm that there isn't an issue with the tunneling. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 435985] New: VNC via SSH tunnel always asks for password even though public key authentication is set-up
https://bugs.kde.org/show_bug.cgi?id=435985 Bug ID: 435985 Summary: VNC via SSH tunnel always asks for password even though public key authentication is set-up Product: krdc Version: 21.03.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: jkcdarun...@gmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY When connecting to a VNC server via SSH tunnel, KRDC always asks for password authentication (PW auth is already discouraged and disabled by default in most distros) even though I'm using public key authentication. STEPS TO REPRODUCE 1. Create connection to an SSH server that has a running VNC server by enabling SSH tunneling 2. Connect OBSERVED RESULT * A password popup appears * Pressing okay with any password throws: "Error authenticating with password: Access denied for 'password'. Authentication that can continue: publickey" * Pressing cancel cancels the connection EXPECTED RESULT It should not ask for a password and continue if my publickey is authorized to connect. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.15-zen1-2-zen OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Same result even if I check/uncheck options like "Don't copy passwords from supported password managers" and "Remember password (KWallet)" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435728] Cursor is oversized and pixelated when using 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=435728 --- Comment #4 from Jan Keith Darunday --- If it's the scaling, is there perhaps a way to disable it only for the cursor so I can use size 36 or 48 instead without the scaling? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435728] Cursor is oversized and pixelated when using 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=435728 --- Comment #3 from Jan Keith Darunday --- Created attachment 137621 --> https://bugs.kde.org/attachment.cgi?id=137621=edit Camera picture of how it actually displays on my screen Here is a picture of it. The cursor is larger than the button in real life. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435728] Cursor is oversized and pixelated when using 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=435728 --- Comment #2 from Jan Keith Darunday --- Created attachment 137620 --> https://bugs.kde.org/attachment.cgi?id=137620=edit Screenshot showing normal-sized non-pixelated cursor on screenshots Hi, taking a screenshot with spectacle shows an unpixelated and normal-sized cursor instead. I also notice that the cursor is in the wrong position compared to what's on my screen. In this screenshot, the cursor on my screen is actually around the Size: 36 selector at the bottom part of the window but spectacle saves it as if the cursor is outside the window. I'll follow up with a camera photo of my screen showing how the cursor appears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435728] New: Cursor is oversized and pixelated when using 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=435728 Bug ID: 435728 Summary: Cursor is oversized and pixelated when using 150% scale on Wayland Product: kwin Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jkcdarun...@gmail.com Target Milestone: --- SUMMARY Cursor is oversized and pixelated when using 150% scale on Wayland STEPS TO REPRODUCE 1. On Wayland, switch to 150% scale OBSERVED RESULT Cursor is oversized and pixelated. Taking a screenshot shows a normal-sized cursor instead (as you would see it from X11) EXPECTED RESULT Cursor should be the same as in an X11 session. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.13-zen1-1-zen OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I've observed this in 5.20 as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435727] New: When switching from X11 to Wayland both at 150% scale, the desktop layout breaks and the widgets and fonts are scaled too big
https://bugs.kde.org/show_bug.cgi?id=435727 Bug ID: 435727 Summary: When switching from X11 to Wayland both at 150% scale, the desktop layout breaks and the widgets and fonts are scaled too big Product: plasmashell Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: jkcdarun...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 137601 --> https://bugs.kde.org/attachment.cgi?id=137601=edit Side by side comparison between X11 and wayland sessions SUMMARY When switching from X11 to Wayland both at 150% scale, the desktop layout is ruined and the widgets and font are scaled too big. STEPS TO REPRODUCE 1. In X11, set scale to 150% 2. Add several widgets stacked vertically at the right part of your desktop 3. Logout, switch to Wayland, and set scale to 150% (This will cause all windows to scale in a blurry manner, so we relogin to fix it) 4. Logout and login again to a Wayland session OBSERVED RESULT The widget positions break apart (as if they were wrapping around). The fonts and widgets on the desktop are too big as well compared to X11. All other apps have correct font sizes. EXPECTED RESULT The widgets should look the same as in X11 with no changes in layout, widget size, and font size. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.13-zen1-1-zen OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I've been experiencing this since I first tried KDE with Wayland (can confirm that this bug happens with at least 5.20 and 5.21 beta). I have never seen this work properly so far. I have tried this on a new user and with other types of widgets, same issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 Jan Keith Darunday changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Jan Keith Darunday --- Hi, I can no longer replicate this in 5.21 beta. Marking this as resolved. Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.13-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432438] Custom shortcut for keyboard input no longer works after updating to 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432438 --- Comment #2 from Jan Keith Darunday --- (In reply to Andrey from comment #1) > Hi Jan, > are you using layout's variants? > Just wanted to make sure you don't suffer from Bug 432367 which might be > related. Hi Andrey, I'm using the English (US) Colemak through fcitx and I haven't noticed any keys typing the wrong character. Same issue happens even if I disable fcitx. I also have another custom shortcut created with Global Shortcut > Command/URL which is bound to Meta + A and it's working fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432438] New: Custom shortcut for keyboard input no longer works after updating to 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432438 Bug ID: 432438 Summary: Custom shortcut for keyboard input no longer works after updating to 5.21 beta Product: plasmashell Version: 5.20.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jkcdarun...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The global shortcut for keyboard input no longer works after updating to 5.21 beta. This is currently important to me as the backtick is bound to Yakuake. However, from my observation this not only affects backtick and is a more general issue as creating a shortcut to type hello when pressing Ctrl + Shift + T does not work as well. STEPS TO REPRODUCE 1. Go to System Settings > Shortcuts > Custom Shortcuts 2. Create a new Keyboard Input shortcut (Edit > New > Global Shortcuts > Send Keyboard Input) and name it Backtick 3. Go to trigger and set trigger to Meta + ` (backtick) 4. Set action to type in a backtick (`) 5. Press apply 6. On any window (QT and non-QT), press Meta + ` OBSERVED RESULT Pressing Meta + ` does not insert a backtick EXPECTED RESULT Pressing Meta + ` should insert a backtick SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.11-arch1-1 OS Type: 64-bit ADDITIONAL INFORMATION This does not seem to be specific to backtick as creating a shortcut to type hello when pressing Ctrl + Shift + T did not work as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 Jan Keith Darunday changed: What|Removed |Added Version|5.17.90 |5.18.90 --- Comment #6 from Jan Keith Darunday --- >load on the external monitor This should be "load only on the external monitor" Note that in the above, eDP1 is the laptop screen and DP1 is the external monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 --- Comment #5 from Jan Keith Darunday --- Hi, just an update for this: I'm still experiencing this issue on both KDE Plasma 5.18.5 (LTS) and 5.18.90 (Beta). I have also found the ff. workaround: By default SDDM displays the greeter on both screens. Logging in to KDE (X11) with this default setting triggers this issue. However, one day, I was trying to make SDDM load on the external monitor as the laptop screen can be too bright at night and it made the issue no longer occur. What I did was add the ff. to /usr/share/sddm/scripts/Xsetup to turn off the laptop monitor in SDDM: ``` xrandr | egrep -i '^DP1 connected' && xrandr --output eDP1 --off && xrandr --output DP1 --auto --primary ``` Note that the issue occurs again if I remove this and return to the default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 --- Comment #3 from Jan Keith Darunday --- (In reply to Nate Graham from comment #2) > Any chance you could try this again in the Plasma 5.18 beta? See > https://www.reddit.com/r/kde/comments/epkjlo/ > plasma_518_lts_beta_more_convenient_and_with_long/fejwivz/ > ?utm_source=share_medium=web2x Hi, I just tried this with Plasma 5.17.90 with my existing user and with a newly-created user, the same issue occurs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 Jan Keith Darunday changed: What|Removed |Added CC||jkcdarun...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 --- Comment #1 from Jan Keith Darunday --- Created attachment 125106 --> https://bugs.kde.org/attachment.cgi?id=125106=edit `journalctl --user --boot=0` right after booting to improper desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416226] New: Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary
https://bugs.kde.org/show_bug.cgi?id=416226 Bug ID: 416226 Summary: Logging in/out and restarting with external monitor as primary makes whole desktop act as secondary screen instead of primary Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: jkcdarun...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 125105 --> https://bugs.kde.org/attachment.cgi?id=125105=edit Screenshot of desktop after login/logout SUMMARY Logging in and out and restarting on dual display (with external display as primary) makes whole desktop act as secondary screen instead of primary (screen with default blue background without taskbar/panel). STEPS TO REPRODUCE 1. Have both Laptop Screen and External Display connected 2. Disable laptop screen and set external display as primary display output 3. Change wallpaper and/or add a widget somewhere 3. Logout and login again (or restart) OBSERVED RESULT - Desktop wallpaper is reset KDE Plasma default (Blue) - Bottom panel is no longer available - I can still add widgets etc. - Manually restarting plasma in konsole (launched through alt+f1) using `kquitapp5 plasmashell && kstart5 plasmashell` returns desktop to normal EXPECTED RESULT - I should see the same wallpaper/widgets/desktop as I had before restart SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.4.11-arch1-1 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Logs from `journalctl --user --boot=0` show the message `kscreen_backend_launcher[1031]: kscreen.xrandr: RRSetOutputPrimary New primary: 68` a second after `plasmashell[1026]` messages start to appear. My assumption is that kscreen launches too late and plasmashell detects both my screen (with the laptop screen set as primary) as it starts up. Note that I'm running on an SSD which could be a factor why plasmashell launches faster than kscreen. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=360072 Jan Keith Darunday <jkcdarun...@gmail.com> changed: What|Removed |Added CC||jkcdarun...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
