KDE/Plasma
the windows/Super L keyboard key is permanently bound to the application menu regardless of what app menu is being used and there’s no obvious way to unbind it
in my case the windows/Super L key is not bound to anything in settings > shortcuts or settings > custom shortcuts
that other user with the exact issue, had installed the wrong drivers… and its not a messed up config, since it didnt work with the test user too…
try switching kernels;
also provide output from:
inxi -G && mhwd -l -li
Inside ~/.config/kwinrc look for
[ModifierOnlyShortcuts]
Meta=
then comment it and see if it unbind the Meta key.
Has anyone experienced blackish Dolphin icon in the Dashboard menu with Breeze theme instead of blue one? How can i change one to regular blue?
I have the same problem.
My extended screen does not work anymore with KDE Plasma.
At login I see both screens, and the only the main screen is usable.
This is my hardware:
inxi -F
System:
Host: legion5 Kernel: 6.0.6-1-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.26.2 Distro: Manjaro Linux
Machine:
Type: Laptop System: LENOVO product: 82JU v: Legion 5 15ACH6H
Mobo: LENOVO model: LNVNB161216
UEFI: LENOVO v:
Battery:
ID-1: BAT0 charge: 80.2 Wh (97.0%) condition: 82.7/80.0 Wh (103.4%)
CPU:
Info: 6-core model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64
type: MT MCP cache: L2: 3 MiB
Speed (MHz): avg: 1406 min/max: 1200/4280 cores: 1: 1457 2: 1200 3: 1200
4: 1200 5: 1200 6: 3300 7: 1197 8: 1200 9: 1197 10: 1200 11: 1266 12: 1264
Graphics:
Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia
v: 520.56.06
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.4 driver: N/A
resolution: 1: 1920x1080~120Hz 2: N/A
API: OpenGL v: 4.6.0 NVIDIA 520.56.06 renderer: NVIDIA GeForce RTX 3060
Laptop GPU/PCIe/SSE2
Is there a way to diagnose this problem?
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
Enabling the second screen did not help. All screens go black and then the revert back to the single screen.
My kernels are already at 5.15. Been staying there kind of the whole time until the update. When I had the issue I tried upgrading to 6.0, and 5.19 and downgrading to 5.10, since I figure it might have been that. Nothing works still.
Here’s my results:
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
v: kernel
Device-2: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-3: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: amdgpu
unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu resolution:
1: 1920x1080~60Hz 2: 1920x1080~60Hz 3: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 22.2.1 renderer: AMD Radeon RX 6800 XT (navi21
LLVM 14.0.6 DRM 3.42 5.15.76-1-MANJARO)
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
> 0000:03:00.0 (0300:1002:73bf) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:0c:00.0 (0300:1002:15d8) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:07:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
network-r8168 2016.04.20 true PCI
EDIT:
Oh I tried the command for mhwd again, although it didn’t work, I realized the reason why it isn’t, is that the command isn’t switching to the proprietary drivers. I keep getting the free one. I also looked at the GUI checkbox in case I could change it there, but they’re kinda unclickable,
Yubico Authenticator doesn’t show the codes.
I’ve tried:
sudo systemctl start pcscd
sudo systemctl enable pcscd
My Yubikey is ok.
ykman info
Device type: YubiKey 5 NFC
Serial number: 9264957
Firmware version: 5.1.2
Form factor: Keychain (USB-A)
Enabled USB interfaces: OTP, FIDO, CCID
NFC transport is enabled.
Applications USB NFC
FIDO2 Enabled Enabled
OTP Enabled Enabled
FIDO U2F Enabled Enabled
OATH Enabled Enabled
YubiHSM Auth Not available Not available
OpenPGP Enabled Enabled
PIV Enabled Disabled
Downgrade yubikey-manager to 4.09.-1 and is works fine.
It seems it is bug.
One (very minor) problem I’ve found with this is that XScreenSaver’s GL Slideshow no longer displays any of the chosen images.
This is due to the new version of Perl throwing a fatal error when attempting to use syswrite() on a UTF8 filehandle.
I’ve raised a bug up-stream, but I have found a workaround:
Edit /usr/lib/xscreensaver/xscreensaver-getimage-file and comment out lines 1552 and 1553. This makes it work again, though I don’t know if there are any other implications to doing this.
When will we get Gnome 43 though?
you have amd and installed the proper drivers, there are no proprietary drivers available for you…
switch to wayland, but first install this:
sudo pacman -S plasma-wayland-session
log out and select wayland in the lower left corner and see if it helped…
but be warned, wayland can be buggy…
Just tried it. It would show me the login screen, but once I try to login with wayland selected at the bottom left, I’d get a black screen then my pc restarts again. So I can’t really login with it.
EDIT: Never mind.
I had to change the kernel to 6.0, so it’s now working.
Thank you so much!
EDIT2:
Well technically the icons are back up with Kernels 6.0 & 6.1. I tried 5.19 in case, but that doesn’t work. So there’s only 6.0 and 6.1.
However, with those settings, my third monitor does shows up, but it’s kinda non-functional. The mouse doesn’t show up. But when right clicking, the right click window shows up albeit kinda laggy. Even with that right click though, the mouse wouldn’t show up.
Update on Manjaro KDE breaks my Looking Glass setup. The performance is reduced from 160+ fps to 70 fps at best. The diagonal tearing is present in the video output. The author of Looking Glass in the discussion said this is not an issue with Looking Glass itself.
Did you try 5.19 kernel?
yes wayland is not ready yet and without wayland, all monitors are working?
KDE Plasma x11 here. The update went smoothly, but I’ve noticed a new issue with VirtualBox: whenever I run my guest OS, it always opens fixed-size as 640x480 (or 800x600) px and doesn’t auto-size to its window as it used to. The (temporary) solution is to have Guest Additions installed, then open a terminal in your guest OS and run sudo VBoxClient --vmsvga and your auto-sized feature will start to work again. Any ideas how to keep this setting and avoid typing that every time in a terminal? Could be just another nvidia issue that may be fixed with the next release…
Another issue is that when I had my VirtualBox running, for some reason, I couldn’t open Manjaro’s System Settings and my mouse’s speed reduced by approx. 50%. Anyone else experienced this?
Sadly, the entire Manjaro KDE experience became bitter after the KDE Plasma update to 5.25. I wish I knew this earlier, when I was still at 5.24:
Same issue with the external display: external display doesn’t work after waking up from sleep, the laptop screen is blinking. Deleting ~/.local/share/kscreen doesn’t help.
Eventually I can enable the external screen by choosing “Unify outputs” in the display options.
So i’m having some random issues with sound after this update… Pulse (?!) keeps complaining about i/o errors when I use the volume icon with my mouse wheel… Sound adjusts up and down, I get sound… but logs give errors whenever I adjust up or down (fast), single adjusts does not trigger error, but 20% adjusts give the errormsg.
Errormsg in question:
pipewire-pulse[2561]: mod.protocol-pulse: client 0x55e33ee0ed60 [libcanberra]: ERROR command:18 (PLAY_SAMPLE) tag:514 error:25 (Input/output error)
Sound also sometimes cuts and needs a reboot to recover… No idea what triggers that…
Sound is via USB-DAC, Bus 003 Device 005: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
I see pulse being mentioned and ALSA in the logs… But pretty sure I swapped to PipeWire about 4 or 5 releases ago, why is pulse back?
ov. 05 20:48:22 x kernel: usb 3-4: new full-speed USB device number 6 using xhci_hcd
nov. 05 20:48:22 x kernel: usb 3-4: New USB device found, idVendor=0d8c, idProduct=000c, bcdDevice= 1.00
nov. 05 20:48:22 x kernel: usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
nov. 05 20:48:22 x kernel: usb 3-4: Product: C-Media USB Headphone Set
nov. 05 20:48:23 x kernel: input: C-Media USB Headphone Set as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:0a:00.3/usb3/3-4/3-4:1.2/0003:0D8C:000C.000D/input/input29
nov. 05 20:48:23 x mtp-probe[4471]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:0a:00.3/usb3/3-4"
nov. 05 20:48:23 x mtp-probe[4471]: bus: 3, device: 6 was not an MTP device
nov. 05 20:48:23 x kernel: hid-generic 0003:0D8C:000C.000D: input,hidraw0: USB HID v1.00 Device [C-Media USB Headphone Set ] on usb-0000:0a:00.3-4/input2
nov. 05 20:48:23 x mtp-probe[4503]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:0a:00.3/usb3/3-4"
nov. 05 20:48:23 x mtp-probe[4503]: bus: 3, device: 6 was not an MTP device
nov. 05 20:48:23 x pipewire-media-session[2269]: spa.alsa: The decibel volume range for element 'PCM' (-9999999 dB - -6 dB) has negative maximum. Disabling the decibel range.
nov. 05 20:48:23 x pipewire-media-session[2269]: spa.alsa: The decibel volume range for element 'PCM' (-9999999 dB - -6 dB) has negative maximum. Disabling the decibel range.
nov. 05 20:48:23 x pipewire-media-session[2269]: spa.alsa: The decibel volume range for element 'PCM' (-9999999 dB - -6 dB) has negative maximum. Disabling the decibel range.
nov. 05 20:48:23 x pipewire-media-session[2269]: spa.alsa: The decibel volume range for element 'PCM' (-9999999 dB - -6 dB) has negative maximum. Disabling the decibel range.
nov. 05 20:48:23 x pipewire-media-session[2269]: spa.alsa: The decibel volume range for element 'PCM' (-9999999 dB - -6 dB) has negative maximum. Disabling the decibel range.
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "auto_null"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "auto_null"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SOURCE@"
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "@DEFAULT_SOURCE@"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0"
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x systemsettings[3168]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x plasmashell[2162]: org.kde.plasma.pulseaudio: No object for name "alsa_output.usb-0d8c_C-Media_USB_Headphone_Set-00.pro-output-0.monitor"
nov. 05 20:48:23 x systemsettings[3168]: file:///usr/share/kpackage/kcms/kcm_pulseaudio/contents/ui/DeviceListItem.qml:65: TypeError: Cannot read property 'description' of undefined
nov. 05 20:48:23 x systemsettings[3168]: file:///usr/share/kpackage/kcms/kcm_pulseaudio/contents/ui/CardListItem.qml:16: TypeError: Cannot read property 'width' of null
Come to think of it, this behaviour was exactly why I swapped over to pipewire… Ho hum.
Edit:
So it seems I still have manjaro-pipewire installed, and no manjaro-pulseaudio, just me not reading the logs correctly… Sooo it maybe isn’t pulseaudio being the problem? Swapped sessionmgr to Wireplumber as suggested in this thread. Issue with error when changing volume in 10%+ increments still remains tho.
Server Name: PulseAudio (on PipeWire 0.3.59)
maybe you have some pulse leftovers, post output from:
pacman -Qs pulse
and you also using pipewire-media-session, you should switch to wireplumber, its better:
sudo pacman -S wireplumber
reboot
Thanks for the info. It seems that rebuilding my current kernel solved the problem.