Stops logging after .xsession-errors grows large

Bug #162991 reported by era
2
Affects Status Importance Assigned to Milestone
gdm
In Progress
Unknown
gdm (Debian)
Confirmed
Unknown
gdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gdm

When programs are running under a gdm-managed session, it redirects their standard output and standard error to ${HOME}/.xsession-errors of the user running the session. However, it will stop logging to this file once it grows too large for gdm's taste, making it basically impossible to do routine X client troubleshooting after you've kept your session open for a few days (depending somewhat on how chatty your X clients are, of course).

It would be nice if there was a way at least to redirect error messages to a volatile location even after this happens, such as a local socket; or perhaps more usefully, the other way around: make /dev/gdm-errors (or whatever) contain the current log, and copy it to .xsession-errors as before, up to the cut-off point.

Changed in gdm:
status: Unknown → Confirmed
Changed in gdm:
status: Unknown → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.