KDE broken on multiseat setup
Hi
I have a strange problem with KDE here, that I am not able to track
alone.
I have 2 seats on the same computer, built with loginctl. Everything was
working well: KDE and other desktop or window managers (FVWM3, IceWM,
NsCDE, WindowMaker). I use X11, not wayland.
The workstation is on Sid.
Login manager is Lightdm, seat0 is on integrated intel graphic card,
seat1 is on Nvidia graphic card with nouveau driver.
Since my last update a few days ago, the KDE session start on seat0 but
can't start on seat1. Other desktop/window managers still works well on
both seat (FVWM3, IceWM, NsCDE, WindowMaker).
xsessionerrors logs from seat1 are quite interesting:
==================
Xsession: X session started for test at jeu. 29 juin 2023 19:06:33 CEST
dbus-update-activation-environment: error: unable to connect to D-Bus:
/usr/bin/dbus-launch terminated abnormally without any error message
localuser:test being added to access control list
dbus-update-activation-environment: error: unable to connect to D-Bus:
/usr/bin/dbus-launch terminated abnormally without any error message
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-test'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-test'
====================
- /usr/bin/dbus-launch relates to dbus-x11 package which was installed 2
years ago, but not anymore. Instead I use dbus-user-session package.
There is no /usr/bin/dbus-launch binary.
- With other desktop or window managers, dbus works on both seat.
- While trying to launch KDE on seat1, screen became black and the mouse
pointer appear after one minute.
- Hard killing the seat1 session with Ctrl-Alt-Backspace freeze the
desktop on seat0. I have to login again on seat1 to unfreeze seat0.
Installing previous packages version, didn't changes anything.
I've booted on previous Kernel, but it didn't changes.
KDE Wayland doesn't works at all, but it might be unrelated as I usualy
don't use KDE with Wayland.
Tested on a brand new account
Other desktop/window managers still works well on both seat (FVWM3,
IceWM, NsCDE, WindowMaker). Same behaviour with a brand new account.
I don't even know on which package I should report the bug.
Any idea ?
--
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau
(Jean-Pierre Rosnay)
Reply to: