Red Hat Bugzilla – Bug 633226
when changing orientation of screen Xorg crashes (NVS 3100)
Last modified: 2011-05-19 09:11:24 EDT
Description of problem:
when changing orientation using display properties Xorg crashes. No matter if primary or secondary display is rotated
doesn't affect NVS 290 but only NVS 3100
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.go into gnome display properties
Created attachment 446880 [details]
sos report from abrt
(In reply to comment #1)
> Created attachment 446880 [details]
> sos report from abrt
It's weird but there are many pieces of information which are not part of the sosreport:
* your X server config file (/etc/X11/xorg.conf, if available) -- I guess there is none, right?
* X server log file (/var/log/Xorg.*.log) -- yes, even that is missing
* output of the dmesg command, and
* system log (/var/log/messages)
Please attach these logs to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
The xorg-x11-drv-nouveau rebase is now sitting in CVS, and should resolve this problem. It can't be built in brew yet however as it's pending a libdrm update.
hmm, I can again see occasional lock ups no related to screen orientation. We saw those in 6.0 beta also .. going to find the reason and the bug number
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
This field is the basis of the errata or release note for this bug. It can also be used for change logs.
The Technical Note template, known as CCFR, is as follows:
What actions or circumstances cause this bug to present.
What happens when the bug presents.
What was done to fix the bug.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.