https://bugs.kde.org/show_bug.cgi?id=474273
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=474273
--- Comment #7 from Nate Graham ---
It has indeed tripped me up in the past. :) One thing I could see us doing is
making `plasmashell --replace` run the systemctl command if you're using the
systemd boot process. Let's track that at Bug 474995.
--
https://bugs.kde.org/show_bug.cgi?id=474273
--- Comment #6 from Michael Reilly ---
(In reply to Nate Graham from comment #5)
> Awesome. That's the supported way to restart plasma, so I'd recommend doing
> that instead of what you were doing before.
Practically speaking, using `kstart5
https://bugs.kde.org/show_bug.cgi?id=474273
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=474273
--- Comment #4 from Michael Reilly ---
(In reply to Nate Graham from comment #3)
> Thanks. Does the problem happen if you restart plasmashell using `systemctl
> restart --user plasma-plasmashell.service` instead?
The problem does not happen when I use
https://bugs.kde.org/show_bug.cgi?id=474273
--- Comment #3 from Nate Graham ---
Thanks. Does the problem happen if you restart plasmashell using `systemctl
restart --user plasma-plasmashell.service` instead?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474273
--- Comment #2 from Michael Reilly ---
(In reply to Nate Graham from comment #1)
> How exactly did you quit and relaunch plasma? What command did you use?
Sorry about the long delay in response, I seem to have not received a
notification. You can
https://bugs.kde.org/show_bug.cgi?id=474273
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Resolution|---
