Re: Screen resolutions
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@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Mon, 2015-04-13 at 10:18 +0100, Russel Winder wrote: journalctl -b creates a seemingly infinite amount of data. I guess I should curtail or filter this somehow. I am not really up on journalctl, I'm afraid I wimped out and run rsyslng so logcheck and logwatch still work. -b gives all the log messages from the current boot, so exactly how much there is depends on how long you leave the system running. It's not really *that* huge when you stick it in a file, and some kernel messages may be useful when debugging this sort of thing as well as the X messages, so I figured I'd just mention the command. But something like | grep gdm-x-session should find the X logs. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
Adam Williamson composed on 2015-04-13 18:02 (UTC-0700): 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 How old is old?... 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. What exactly does journalctl -b extract that is better than what an Xorg.0.log contains? I see you've been tweeking https://fedoraproject.org/wiki/How_to_debug_Xorg_problems but I don't see an explanation of non-interest in the traditional log. 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 None of my Fedora installations include Gnome or GDM. (All have compositing disabled regardless of GPU and CPU power.) 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. I get that the powers in control decided there shall be a massive paradigm shift from X troubleshooting tradition dating back into a previous century (the precise reasons for which as yet have escaped my discovery), converting the wealth of help files Google will be offering up in the years to come into obfuscation of appropriate assistance. That change apparently has yet to fully manifest. Some installations here have had KDM replaced by SDDM. On those with SDDM I've been unable to get a configuration equivalent to KDM configuration, so I use startx or xinit directly to start KDE on those. On those that still have KDM, I'm more likely to be using startx than a login manager anyway. I cannot recall having seen an Xorg.0.log not created freshly on X exit on any of them in recent weeks, if ever. IOW, I have many Xorg.0.log files created in recent weeks, days and hours by Fedora. Surely others do too. What I'd really like to see is what makes the rigamarole of using journalctl to extract X diagnostic info from a binary blob produce better troubleshooting and diagnostic info better than the tradition of automatic creation in human readable format copyable using simple and memorable instructions from anything that can access the filesystem containing it. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
Adam Williamson composed on 2015-04-13 21:18 (UTC-0700): I don't see the need to rehash tired arguments about journald here. It's not really relevant to the simple question of where to find the logs in what situation. I wasn't looking for any rehash. I never saw any explanation why Xorg logging would be added to the bblob, so if anyone has an URL pointer, I'd like to have a looksee. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Mon, 2015-04-13 at 22:13 -0400, Felix Miata wrote: Adam Williamson composed on 2015-04-13 18:02 (UTC-0700): 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 How old is old?... Whenever it switched over. I don't remember. 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. What exactly does journalctl -b extract that is better than what an Xorg.0.log contains? I see you've been tweeking https://fedoraproject.org/wiki/How_to_debug_Xorg_problemsbut I don't see an explanation of non-interest in the traditional log. I don't think you understood what I wrote. The messages for a given boot will *either* be in Xorg.0.log *or* in the journal. They'll never be in both. On some systems (some login managers) the X logs are now written to the journal, *not* to Xorg.0.log. One other systems they are still in Xorg.0.log. 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. I get that the powers in control decided there shall be a massive paradigm shift from X troubleshooting tradition dating back into a previous century (the precise reasons for which as yet have escaped my discovery), This is an overstatement. Some log lines were in one place. Now they're in another. Stuff moves around, this is a thing that happens. People generally deal with it, they have brains and stuff. Some installations here have had KDM replaced by SDDM. On those with SDDM I've been unable to get a configuration equivalent to KDM configuration, so I use startx or xinit directly to start KDE on those. On those that still have KDM, I'm more likely to be using startx than a login manager anyway. I cannot recall having seen an Xorg.0.log not created freshly on X exit on any of them in recent weeks, if ever. Like I said, it happens on GNOME / Workstation. Since you don't have any Workstation / GNOME installs, of course you don't have any cases where the X logs are in the journal. IOW, I have many Xorg.0.log files created in recent weeks, days and hours by Fedora. Surely others do too. I didn't say anything else... What I'd really like to see is what makes the rigamarole of using journalctl to extract X diagnostic info from a binary blob produce better troubleshooting and diagnostic info better than the tradition of automatic creation in human readable format copyable using simple and memorable instructions from anything that can access the filesystem containing it. I don't see the need to rehash tired arguments about journald here. It's not really relevant to the simple question of where to find the logs in what situation. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
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? (and may not exist) if you use I have noticed this to be true on occasion, but rarely use any DE other than KDE, and cannot recall the last time it did not get created. 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 wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Sun, 2015-04-12 at 14:23 -0400, Felix Miata wrote: Russel Winder composed on 2015-04-12 16:05 (UTC+0100): https://bugzilla.redhat.com/show_bug.cgi?id=1211058 I am still not enmtirely sure what constitutes a really good initial report, so try and get people to tell me what further information is needed… Start by providing your display model number and attaching /var/log/Xorg.0.log . Note /var/log/Xorg.0.log is not wanted (and may not exist) if you use 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. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Mon, 2015-04-13 at 00:18 -0700, Adam Williamson wrote: On Sun, 2015-04-12 at 14:23 -0400, Felix Miata wrote: Russel Winder composed on 2015-04-12 16:05 (UTC+0100): https://bugzilla.redhat.com/show_bug.cgi?id=1211058 I am still not enmtirely sure what constitutes a really good initial report, so try and get people to tell me what further information is needed… Start by providing your display model number and attaching /var/log/Xorg.0.log . Note /var/log/Xorg.0.log is not wanted (and may not exist) if you use Workstation / GNOME; GNOME directs X log messages to the journal, so attach the output of journalctl -b . As far as I can tell Xorg.0.log is no longer created by Rawhide, it used to be until 2015-04-01, but not any longer. I wonder what changed? journalctl -b creates a seemingly infinite amount of data. I guess I should curtail or filter this somehow. I am not really up on journalctl, I'm afraid I wimped out and run rsyslng so logcheck and logwatch still work. Other desktops still use Xorg.0.log, I believe - at least, KDE does. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- Russel. = Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.win...@ekiga.net 41 Buckmaster Road m:+44 7770 465 077 xmpp:rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
Russel Winder composed on 2015-04-13 10:18 (UTC+0100): As far as I can tell Xorg.0.log is no longer created by Rawhide, it used to be until 2015-04-01, but not any longer. I wonder what changed? Nothing apparent here yet, but with KDE. Timestamp on /var/log/Xorg.0.log is about 20 minutes ago with 4.0.0.rc6 on Rawhide host big41 upgraded last on 8 April. journalctl -b creates a seemingly infinite amount of data. I guess I should curtail or filter this somehow. I am not really up on journalctl https://fedoraproject.org/wiki/How_to_debug_Xorg_problems explains the complications of using journalctl for X diagnosis. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Wed, 2015-04-08 at 09:52 -0500, Michael Cronenworth wrote: On 04/08/2015 09:31 AM, Russel Winder wrote: My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? I see the same problem with my ASUS ultrabook that has the same resolution screen. I haven't debugged it but either the i915 module (kernel) or Xorg driver is not providing the correct modes. This issue has been around for a while. You won't want 16:10 modes as 2560x1440 is a 16:9 resolution. Please open a bug report. I'll CC on it. I made a first pitch at: https://bugzilla.redhat.com/show_bug.cgi?id=1211058 I am still not enmtirely sure what constitutes a really good initial report, so try and get people to tell me what further information is needed… -- Russel. = Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.win...@ekiga.net 41 Buckmaster Road m:+44 7770 465 077 xmpp:rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
Russel Winder composed on 2015-04-12 16:05 (UTC+0100): https://bugzilla.redhat.com/show_bug.cgi?id=1211058 I am still not enmtirely sure what constitutes a really good initial report, so try and get people to tell me what further information is needed⦠Start by providing your display model number and attaching /var/log/Xorg.0.log . https://fedoraproject.org/wiki/How_to_debug_Xorg_problems lists things that should be included. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Screen resolutions
My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? -- Russel. = Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.win...@ekiga.net 41 Buckmaster Road m:+44 7770 465 077 xmpp:rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On 04/08/2015 09:31 AM, Russel Winder wrote: My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? I see the same problem with my ASUS ultrabook that has the same resolution screen. I haven't debugged it but either the i915 module (kernel) or Xorg driver is not providing the correct modes. This issue has been around for a while. You won't want 16:10 modes as 2560x1440 is a 16:9 resolution. Please open a bug report. I'll CC on it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
Hi, my My Lenovo X1 3rd gen accurately lists the Displays native resolution on Fedora 22 alpha (2560 * 1440 16:9) (other than that it only lists some 4:3 and one 5:4 resolutions though) don't know what happened to your Setup though. Fred On Wed, Apr 8, 2015 at 4:31 PM, Russel Winder rus...@winder.org.uk wrote: My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? -- Russel. = Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.win...@ekiga.net 41 Buckmaster Road m:+44 7770 465 077 xmpp:rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Frederik Berg Schwedenstr. 16 13357 Berlin +49 151 / 55290291 +49 30 / 53045749 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Screen resolutions
On Wed, 2015-04-08 at 15:31 +0100, Russel Winder wrote: My Lenovo X1 has the 2560 x 1440 screen. When running Debian Sid/GNOME, the displays settings dialogue shows all the possible resolutions with the 16:10, 16:9, 5:4 and 4:3 aspect rations. When running Fedora Rawhide/GNOME the same dialogue shows only the native resolution and 4:3 aspect ration resolutions. As far as I am aware this is both of them out of the box in that I have not knowingly fiddled with anything. Is this to be expected (I hope not as I want 16:9 and 16:10 resolutions available), or have I failed to do something during Fedora Rawhide/GNOME setup that has led to this? I'm not sure, but sid has 3.14 while Rawhide has 3.16, which could be significant. sid's kernel is also a lot older, I think. desktop@ may have a better idea about this one. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
