https://bugs.kde.org/show_bug.cgi?id=437226
Luuk Pook changed:
What|Removed |Added
CC||luukp...@gmail.com
--- Comment #11 from Luuk Pook
https://bugs.kde.org/show_bug.cgi?id=437226
Nate Graham changed:
What|Removed |Added
Summary|login script doesn't show: |login script disappears
|cannot
https://bugs.kde.org/show_bug.cgi?id=437226
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #3 from Chef Niko ---
Sorry, I don't know how to answer your question. I'm not familiar with how
systemd works.
It looks like the login scripts aren't running. My log file isn't being updated
at all when I log in, but when I run my script m
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #4 from Nate Graham ---
If you don't know, you're not using it, as it's an opt-in thing.
Unfortunately (or fortunately?) this KCM was rewritten in Plasma 5.22, and 5.21
is not going to get any more bugfix releases, so even if we went back t
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #5 from Nicolas Fella ---
> If you don't know, you're not using it, as it's an opt-in thing.
technically the distro can opt in and at least Fedora does. To be sure run
"kreadconfig5 --file startkderc --group General --key systemdBoot"
FWIW
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #6 from Nate Graham ---
(This is true, but the reporter is using Kubuntu, which to my knowledge has not
opted in)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #7 from Chef Niko ---
Thank you for the additional information! I ran the command mentioned, and got
a blank return... so I guess that's a no to using systemd startup feature.
Konsole Output:
($) ~: kreadconfig5 --file startkderc --group Ge
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #8 from Nate Graham ---
Kubuntu has the 5.22 beta available via their own methods, in fact:
https://kubuntu.org/news/plasma-5-22-beta-available-for-testing/
So you could either upgrade your system using that, or try KDE Neon Testing or
Unst
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #9 from Chef Niko ---
Thank you for the additional information... and point taken. :)
I tried the neon testing addition live image, and it looks much better. When I
closed and re-opened the settings window, the script showed up correctly.
https://bugs.kde.org/show_bug.cgi?id=437226
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=437226
thenujan changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=437226
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=437226
Nate Graham changed:
What|Removed |Added
Resolution|FIXED |---
Summary|login script disappears
https://bugs.kde.org/show_bug.cgi?id=437226
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #13 from Nicolas Fella ---
I can't think of a good reason why .config/autostart would be a file and I'm a
bit hesitant to add a workaround without understanding how we ended up in that
state
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=437226
--- Comment #14 from Luuk Pook ---
That's fair. I don't know why it was there, the file was empty as well. Guess
we could wait for more reports and instruct to check whether autostart is a
file or folder. If it does turn out to be the issue multiple tim
17 matches
Mail list logo
