You are not logged in.
Been using that combo for awhile, after today's update and rebooting plasma comes up fine but i3 doesn't seem to start. When selecting i3 at boot it works fine for some reason. Nothing different turns up in journalctl or X11 logs....
Last edited by ngoonee (2022-06-15 12:03:22)
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
What (WM) does start and is the running Xorg log of current date?
(You might end up running plasma on wayland)
Have you tried to run i3 in that session (i3 --replace)?
Offline
What (WM) does start and is the running Xorg log of current date?
(You might end up running plasma on wayland)Have you tried to run i3 in that session (i3 --replace)?
Plasma starts, and I've confirmed it to be on X11 rather than Wayland (various methods, including checking $DISPLAY, running xprop, etc.).
i3 --replace gives
15/06/22 14:18:55 - ERROR: Another window manager seems to be running (X error 10)Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
If by "today's update" you mean Plasma 5.25, systemd boot is turned on by default which doesn't support using other window managers than kwin. You'll have to disable it if you want to keep doing so.
Offline
If by "today's update" you mean Plasma 5.25, systemd boot is turned on by default which doesn't support using other window managers than kwin. You'll have to disable it if you want to keep doing so.
Ah yes that should be it, that just dropped into [testing] (which, kicking myself, I should have mentioned from the start! Haven't had to report an issue in awhile). Thanks!
EDIT: After testing that's not it, I was using grub and still am (not like a system update would change that for me on Arch). Not entirely sure how systemd boot connects to plasmashell as well, and can't yet seem to find any documentation on 5.25 making changes in that regard?
EDIT2: okay I got it, it wasn't systemd-boot bootloader, but the systemdBoot setting. Using the kwriteconfig5 line with false worked. I'm a bit uncomfortable not knowing what file was edited though, but at least its still the 'old' behaviour. Time to read a bit more about what kwriteconfig5 is actually doing on Arch.
For the record, I did:-
kwriteconfig5 --file startkderc --group General --key systemdBoot falseEDIT3: So after some sleuthing it turns out the user startkderc is in ~/.config. KDE has way too many file locations (and seems to use most/all of them).... This file didn't exist before I ran the above command, even.
Last edited by ngoonee (2022-06-16 02:39:12)
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline