Bug 1559 - screen rotation impossible
Summary: screen rotation impossible
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 1
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2011-06-03 18:29 CEST by Yann Allain
Modified: 2012-11-06 11:33 CET (History)
4 users (show)

See Also:
Source RPM: x11-server
CVE:
Status comment:


Attachments

Description Yann Allain 2011-06-03 18:29:41 CEST
Description of problem : I can't rotate my screen by three ways 

Version-Release number of selected component (if applicable):

How reproducible: everytime

Hardware graphic card nvidia 9800 GTX+, screen Hanns-G HG281D, resolution 1920x1200.

Steps to Reproduce:
1. by nvidia settings :
nvidia-settings
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 287 error_code 2 request_code 155 minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

2. by : xrandr -o right
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (RANDR)
  Minor opcode of failed request:  2 (RRSetScreenConfig)
  Value in failed request:  0x780
  Serial number of failed request:  14
  Current serial number in output stream:  14

Note : that command worked on mandriva 2010.2
3. by configuration du système / affichage et moniteur / taille et orientation  no effect.
Comment 1 Cédric Bortolussi 2011-08-31 19:33:20 CEST
Same by me on i586.
Known bug and patchable.

https://bugzilla.redhat.com/show_bug.cgi?id=710958
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/740933
http://patchwork.freedesktop.org/patch/5427/

Would be cool to have a build of patched x11-server-xorg.
Could triage assign this bug to xserver maintainer?

CC: (none) => cedbor

Cédric Bortolussi 2011-08-31 19:43:50 CEST

Keywords: (none) => PATCH
Hardware: x86_64 => All

Comment 2 Yann Allain 2011-09-01 12:14:15 CEST
+1 for a patched xorg.
Thanks in advance.
Cédric Bortolussi 2011-09-07 18:50:57 CEST

Target Milestone: --- => Mageia 1
Source RPM: (none) => x11-server

Manuel Hiebel 2011-09-10 14:13:40 CEST

CC: (none) => fundawang, thierry.vignaud

Comment 3 Samuel Verschelde 2011-10-01 01:40:04 CEST
Assigning to maintainer now that our maintainer's database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

This bug report comes with a patch, can we envision an update to Mageia 1?

CC: (none) => stormi
Assignee: bugsquad => thierry.vignaud

Comment 4 Cédric Bortolussi 2012-01-05 16:38:23 CET
I'm disappointed : the build pushed today fixes security issues (which is good oc), but maintainer forgot to include this patch :-(
What's more, i made a local build with rotation enabled some weeks ago, and now i have to do the trick again...
Any clue if it could be included before 1.11/mageia 2?

thx in advance
Comment 5 Samuel Verschelde 2012-03-20 23:08:07 CET
Thierry, any chance this patch would be included (if still useful)? If you agree I can ask one of my apprentices to do it in svn.
Comment 6 Marja Van Waes 2012-07-06 15:05:22 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 7 Manuel Hiebel 2012-11-05 16:53:17 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 8 Yann Allain 2012-11-05 20:41:27 CET
Bug fixed pn Mageia 2
Comment 9 Thierry Vignaud 2012-11-06 11:33:47 CET
Let's close then as Mga1 is EOL.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.