> I had originally similar thoughts, but after many unsuccessful attempts > to get the actual Xorg failure logged somewhere, I eventually gave up > (e.g. param lines in sesman.ini to pass -logfile and its argument). If > you could help me find a solution to that, I could try to get it to > give me an error message ...
What happens if you add -logfile xorg.log to params (and restart sesman)? It should then create the log file either in ~/.local/shared/xorg.log or ~/xorg.log or /var/log/xorg.log. If it doesn't, I'm somewhat surprised… Some random questions: * Is your Xorg binary suid root? * Do you have policykit? * What's in /etc/X11/Xwrapper.config ? -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Maintainer LPIC-3 Linux Enterprise Professional (Security)
signature.asc
Description: PGP signature
