When I run journalctl -f, I see this warning periodically:
kwin_core: Cannot grant a token to KWin::ClientConnection(0x5cdf8ac278d0)
I have few issues for few weeks and I think that warning is core of all these issues?
First is krdpserver keeps showing me dialog asking me if I want to allow it to access my desktop. But the dialog crashes immediately before I click on any of its buttons.
Second is my browser is unable to remember logins. I have to re login everywhere.
I’m just guessing the cause of these 2 is that warning as it says it’s token related issue.
Hi! To help folks best guide you, could you please provide your basic system information from the Info Center app? The Copy Details button is the easiest way to get that ready to paste in:
Ah sorry, I forgot
OS Version: KDE Neon 6.3
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
I also have laptop with amdgpu but I don’t see have all above issues on it.
Is your session Wayland or X11?
Since you’re on KDE Neon (which is rolling-release for KDE stuff), make sure you’re fully updated.
A lot of KWin/krdpserver and Wayland-related bugs are actively being patched.
It’s on wayland. And I believe it’s latest.
I update almost daily, and last update was probably 2 days ago. And I had this for like a week? I’ll check if it has more updates.
For what it’s worth, it looks like the journal message that you’re seeing has its own bug report filed in the KDE Bugtracking System: 500393 – kwin_wayland logs logs error messages to the journal kwin_core: Cannot grant a token to KWin::ClientConnection
I see periodic bursts of that message in my own system journal, but no corresponding user-visible issues that I’m aware of so I’m unsure what issue it’s indicating.
There are a couple of open reports for KRdp crashes - the one here might be what you’re experiencing, but checking the journal messages for krdpserver when it crashes might help confirm that: 501229 – krdpserver segfaults when trying to connect
I’d guess that the journal message from KWin - the display server / window manager - is pretty unlikely to be related to Brave Browser saving passwords. That might come down to the brave-keyring package, which if I remember correctly, is installed separately by Brave and could have its own issues?
I thought brave was also misbehaving because all of them started around same time. Brave just got fixed itself yesterday, weird, but at least logging it works now.
Seeing the same when trying to connect using KRDC with Windows 11 remote host:
kwi 18 17:03:57 hostx krdc[31121]: KRDC: Unable to connect
kwi 18 17:03:57 hostx kwin_wayland[1746]: kwin_core: Cannot grant a token to KWin::ClientConnect
ion(0x556fc3d262b0)
$ kinfo
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.14.2-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-8100 CPU @ 3.60GHz
Memory: 3.5 GiB of RAM
Graphics Processor 1: Intel® UHD Graphics 630
$ krdc --version
krdc 24.12.3
QThreadStorage: Thread 0x5602a27834e0 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x5602a27834e0 exited after QThreadStorage 1 destroyed
QThreadStorage: Thread 0x5602a27834e0 exited after QThreadStorage 0 destroyed
These QThreadStorage (…) messages should not be there I guess…
That being said @Zamundaaa states in his comment that
This is not an error, it’s a harmless warning.
so I think we should look elsewhere for reasons of our problems.
1 Like
