On Mon, 2015-04-13 at 04:52 -0400, Felix Miata wrote: > Adam Williamson composed on 2015-04-13 00:18 (UTC-0700): > > > On Sun, 2015-04-12 at 14:23 -0400, Felix Miata wrote: > > > > Start by providing your display model number and attaching > > > /var/log/Xorg.0.log . > > > Note /var/log/Xorg.0.log is not wanted > > Not wanted by who? Bug reports, anyone. The reason I didn't just say 'doesn't exist' is because if your system is old enough you'll still have the file, with a log from the last boot before GDM switched over to sending the messages to the journal. But that file is very unlikely to be of any interest to anyone. > > Workstation / GNOME; GNOME directs X log messages to the journal, > > so > > attach the output of journalctl -b . > > > Other desktops still use Xorg.0.log, I believe - at least, KDE > > does. > > I wasn't aware any DEs had direct impact on Xorg.0.log content. It's > a log > from the XOrg server, not any DE. ??? > OTOH, what happens in the server affects what happens in the DE. > *Not* wanted > doesn't make sense if diagnostics from the server are of possible > use. The thing that spawns the X server decides where it should send its logs; when you use GDM + GNOME, at least, the X log messages are directed to the journal. I think it's probably the case that this is tied to the login manager not the desktop, so when you use GDM, whatever desktop you log into, the messages go to the journal - but I wasn't 100% sure so I fudged it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
