Hey,
I made another scan through my journal and saw, that kglobalaccel is not
the source of the 2 min break. At least for myself I seen the 2min breaks in
logs
comes from at-spi2-core [1].
At least the analyses of my logs are telling me that the restarting and failure
of kglobalaccel is done
Hey,
You are right, It is also not fixed for me.
I'm not sure how this complete thing is handled. For me it seems like systemd
is taking care about restarting, properly because kglobalaccel does not stop
with exit code 0.
Dez 29 22:48:12 xxx systemd[1]: Stopping Session 3 of user Me
Dez 29 22:4
Hi,
> Well this patch will only been active after restart, as the current service is
> not restarted if you update the package, because it is a user process. User
> processes are not restarted when upgrading the corresponding package. So you
> should give it another try restarting your computer.
Hey,
> After the update:
>
> ...
> Setting up libkf5globalaccel5:amd64 (5.77.0-3) ...
> Setting up libkf5kiogui5:amd64 (5.77.0-3) ...
> Setting up libkf5globalaccelprivate5:amd64 (5.77.0-3) ...
> Setting up libkf5globalaccel-bin (5.77.0-3) ...
> ... and further packages ...
Well this patch will
Thank you!
That's what I call fast - impressive!
> With the link you proposed and follow to the bugreport
> https://bugs.kde.org/show_bug.cgi?id=429415 I've seen
> that there is a proposed patch.
You're right, I probably should have noted that as well.
Unfortunately, the problem does not seem to
Hey,
I see this issue for a while already but never found time to search for a
bugreport/solution. With the link you proposed and follow to the bugreport
https://bugs.kde.org/show_bug.cgi?id=429415 I've seen that there is a proposed
patch. I included this patch in 5.77.0-3, hopefully this makes
6 matches
Mail list logo
