Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: GNOME 3.12 Puts The X.Org Log In The Systemd Journal

  1. #1
    Join Date
    Jan 2007
    Posts
    14,359

    Default GNOME 3.12 Puts The X.Org Log In The Systemd Journal

    Phoronix: GNOME 3.12 Puts The X.Org Log In The Systemd Journal

    A useful tip shared by X.Org input expert Peter Hutterer is that with today's GNOME 3.12 release the GNOME Display Manager is no longer writing X.Org Server logs to the file but is being stored within systemd's journal...

    http://www.phoronix.com/vr.php?view=MTY0NDQ

  2. #2
    Join Date
    Jun 2009
    Posts
    1,103

    Default

    trollfest in 3 2 ...

  3. #3
    Join Date
    Oct 2010
    Posts
    417

    Default

    Quote Originally Posted by Peter Hutterer
    Previously the server kept only a single backup log file around, so if you restarted twice after a crash, the log was gone. With the journal it's now easy to extract the log file from that crash five restarts ago. It's almost like the future is already here.
    Probably what I like most about this. While it doesn't happen often, sometimes there's that "oops" moment when you restart after a crash and realise you've just wiped the log you needed to troubleshoot your problem. If you know you only rebooted 'n' times since the crash, you can use 'journalctl -b -n /usr/bin/Xorg' (where n is an integer) to find all Xorg logs for that boot. Handy.
    Last edited by Nobu; 03-27-2014 at 01:26 AM.

  4. #4
    Join Date
    Sep 2011
    Posts
    23

    Default

    Quote Originally Posted by Nobu View Post
    Probably what I like most about this. While it doesn't happen often, sometimes there's that "oops" moment when you restart after a crash and realise you've just wiped the log you needed to troubleshoot your problem. If you know you only rebooted 'n' times since the crash, you can use 'journalctl -b -n /usr/bin/Xorg' (where n is an integer) to find all Xorg logs for that boot. Handy.
    I don't remember how many times I rebooted, but it was a friday or monday and full moon.. is there an option for journalctl to find that? I think it is a valid use case and such option needs to be added.
    And I always restart everything 3-4 times after a crash. And debugging crash that happened 3 years ago on another xorg/drivers is my hobby ))
    Last edited by Stellarwind; 03-27-2014 at 02:50 AM.

  5. #5
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    521

    Default

    Quote Originally Posted by Stellarwind View Post
    I don't remember how many times I rebooted, but it was a friday or monday and full moon.. is there an option for journalctl to find that? I think it is a valid use case and such option needs to be added.
    And I always restart everything 3-4 times after a crash. And debugging crash that happened 3 years ago on another xorg/drivers is my hobby ))
    Well now you can centralize all logs and configure that for all. Why keep logs from other stuff longer and discard the ones from xorg sooner?

  6. #6
    Join Date
    Sep 2012
    Posts
    650

    Default

    Quote Originally Posted by Stellarwind View Post
    I don't remember how many times I rebooted, but it was a friday or monday and full moon.. is there an option for journalctl to find that? I think it is a valid use case and such option needs to be added.
    And I always restart everything 3-4 times after a crash. And debugging crash that happened 3 years ago on another xorg/drivers is my hobby ))
    As a matter of fact, you can, as systemd logs keep the timestamp of the log (and you can search by that), and you can rotate/backup log databases as you see fit (if you want to keep longer log history). You can compute separately all friday and monday that happened at full moons, cycle in you backup logs, and find all unsuccessful termination of xorg on said days.

    Funny how your stupid and snarky example is actually feasible without too much effort.

  7. #7
    Join Date
    Nov 2011
    Posts
    351

    Default

    I don't understand. Is systemd a requirement for Gnome now or what? My educated guess would be no, since Gentoo still can run it, but I'm a bit confused.

  8. #8
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,860

    Default

    Quote Originally Posted by garegin View Post
    I don't understand. Is systemd a requirement for Gnome now or what? My educated guess would be no, since Gentoo still can run it, but I'm a bit confused.
    Its If-else'd. If systemd & logind are available then Gnome prefers them. If they are not they fallback to the traditional code paths.

  9. #9
    Join Date
    Mar 2009
    Posts
    84

    Default

    usually the first place to look to clues for the failure is generally the /var/log/Xorg.0.log file. If it was one restart ago, /etc/X11/Xorg.1.log.
    This is wrong. Xorg.1.log is the log for DISPLAY=:1. You were probably thinking of Xorg.0.log.old.

  10. #10
    Join Date
    Apr 2010
    Posts
    706

    Default

    Quote Originally Posted by garegin View Post
    I don't understand. Is systemd a requirement for Gnome now or what? My educated guess would be no, since Gentoo still can run it, but I'm a bit confused.
    Not a hard requirement, no. But with every Gnome release, it uses more and more systemd functionality - and since very few Gnome developers are using distros that don't run systemd, the non-systemd code paths don't get anywhere near as much testing.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •