LightDM logs to /var/log rather than journal #26172
Labels
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
2.status: wait-for-upstream
Waiting for upstream fix (or their other action).
Comments
|
There is a I don't however see what can be done about the output of the X server :-(. |
|
It ain't pretty but hey it works 😄 diff --git a/nixos/modules/services/x11/display-managers/lightdm.nix b/nixos/modules/services/x11/display-managers/lightdm.nix
index 256bfb9ce3..57a6de5e3c 100644
--- a/nixos/modules/services/x11/display-managers/lightdm.nix
+++ b/nixos/modules/services/x11/display-managers/lightdm.nix
@@ -19,11 +19,11 @@ let
display=$(echo "$@" | xargs -n 1 | grep -P ^:\\d\$ | head -n 1 | sed s/^://)
if [ -z "$display" ]
- then additionalArgs=":0 -logfile /var/log/X.0.log"
- else additionalArgs="-logfile /var/log/X.$display.log"
+ then additionalArgs=":0 -logfile /dev/null"
+ else additionalArgs="-logfile /dev/null"
fi
- exec ${dmcfg.xserverBin} ${toString dmcfg.xserverArgs} $additionalArgs "$@"
+ exec systemd-cat ${dmcfg.xserverBin} ${toString dmcfg.xserverArgs} $additionalArgs "$@"
'';
usersConf = writeText "users.conf"
@@ -195,7 +195,7 @@ in
# lightdm relaunches itself via just `lightdm`, so needs to be on the PATH
execCmd = ''
export PATH=${lightdm}/sbin:$PATH
- exec ${lightdm}/sbin/lightdm --log-dir=/var/log --run-dir=/run
+ exec ${lightdm}/sbin/lightdm --log-dir=/var/log --run-dir=/run --debug
'';
}; |
|
Maybe |
|
@dezgeg |
|
Aha, indeed lightdm captures the stderr of the X server for its own purposes. How about |
|
Alas.. |
|
And annoyingly there doesn't seem to be a way to capture the output of the greeter process :/. |
|
I guess patching is needed then... Fortunately, I think all that's needed to remove the calls to |
|
I'm coming to a conclusion that capturing the output of the greeter as part of |
|
I opened an issue about this upstream: canonical/lightdm#34 |
timokau
added
the
2.status: wait-for-upstream
5 tasks
|
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
stale
bot
added
the
2.status: stale
|
Yes |
stale
bot
removed
the
2.status: stale
|
I marked this as stale due to inactivity. → More info |
stale
bot
added
the
2.status: stale
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
When using lightdm, the X server log goes to
/var/log/X.0.logand/var/log/x-0.log(the former is with timestamps, the latter without) and the display manager log goes to/var/log/lightdm.log. All of this should instead go to the journal. This seems to be hard-coded behaviour in lightdm (X server, lightdm). This makes debugging errors more difficult and inconsistent with other display managers.Steps to reproduce
Enable and start lightdm.
Technical details
The text was updated successfully, but these errors were encountered: