The current .xsession-errors is just the combined stdout/stderr of all
the processes running in the session. This just matches the legacy
behaviour. The display manager doesn't know about each process so it
can't do any timestamping on them. The trend seems to be for the init
system (upstart / syst
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088343
Title:
pl
They're not coming from the server, but directly from the apps running
on the user session. Since the login manager is starting the user
session, it could be possible to route stderr to some external app for
adding the timestamps..
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
It looks like at least some of the entries are already timestamped, here
is an example
2012-12-09 06:28:26,041 - softwarecenter.ui.gtk3.app - INFO - software-
center-agent finished with status 0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
