Bug 25668 - log timestamps would be nice
Summary: log timestamps would be nice
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.4 (2008.09)
Hardware: All All
: medium enhancement
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 02:11 UTC by Adrian von Bidder
Modified: 2010-06-07 13:33 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Adrian von Bidder 2009-12-16 02:11:44 UTC
Heyho!

Timestamps in Xorg's log output would be nice (or the possibility to log to syslog instead of file)

Some patches have already been written (I've not found it here, though, possibly my search skills are lacking)
	https://bugs.launchpad.net/bugs/285787

(to correlate log output with the intel -- kernel or X, not sure -- driver's tendency to suddenly blank the display under 2.6.32.  Haven't further investigated this yet.)

cheers
-- vbi
Comment 1 Peter Hutterer 2009-12-16 17:02:44 UTC
On Wed, Dec 16, 2009 at 02:11:44AM -0800, bugzilla-daemon@freedesktop.org wrote:
> Some patches have already been written (I've not found it here, though,
> possibly my search skills are lacking)
>         https://bugs.launchpad.net/bugs/285787

if patches are already written please push the respective authors and/or
package maintainers to get the patches upstream. This site has a bit of
information on why this is a good idea:
http://fedoraproject.org/wiki/PackageMaintainers/WhyUpstream
(the site is Fedora-specific but the information applies to all distros)
Comment 2 Matej Cepl 2010-06-07 12:24:57 UTC
a) this looks very much like a duplicate of bug 26180
b) there is now http://cgit.freedesktop.org/xorg/xserver/commit/?id=d2322b6309bf15a45002b42e7e6ba3d6b5bfa932 ... it is probably not perfect, but I guess this bug is ready for closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.