Bug 4318

Summary: 'qemu -full-screen' kills dual monitor setup
Product: Mageia Reporter: Herbert Poetzl <herbert>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: herbert, marja11
Version: CauldronKeywords: NEEDINFO, Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: qemu-0.15.1-2.mga2.src.rpm CVE:
Status comment:
Attachments: screenshot of the dual head setup after qemu-kvm --full-screen

Description Herbert Poetzl 2012-01-28 15:16:02 CET
Description of problem:
starting qemu -full-screen

Version-Release number of selected component (if applicable):
qemu-0.15.1-2.mga2.x86_64
gnome-shell-3.3.4-1.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. get a dual head setup (spanning two screens)
2. start qemu -full-screen
3. exit qemu (CTRL-ALT-2, then quit)


http://vserver.13thfloor.at/Stuff/MAGEIA/BUGS/qemu_fullscreen_before.png
http://vserver.13thfloor.at/Stuff/MAGEIA/BUGS/qemu_fullscreen.png
http://vserver.13thfloor.at/Stuff/MAGEIA/BUGS/qemu_fullscreen_after.png
Comment 1 Manuel Hiebel 2012-01-30 01:18:25 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => misc

Comment 2 Michael Scherer 2012-01-30 09:17:59 CET
This bug lacks some important information :
- what kind of setup do you have ( from a hardware point of view ) ?
- what driver is used ?
- does it occurs with another windows manager ?
- what does xorg logs say ?

And what do you mean exactly by kill dual monitor setup ? From what I can infer from screenshot, the issue is either "there is a black point" or "I have just one screen".

According to https://bugzilla.redhat.com/show_bug.cgi?id=523296 , the issue is likely not in qemu, but in SDL or X.
Comment 3 Herbert Poetzl 2012-01-30 18:01:33 CET
(In reply to comment #2)
> This bug lacks some important information :
> - what kind of setup do you have ( from a hardware point of view ) ?
 - ATI Technologies Inc RV670PRO [Radeon HD 3850]
 - two monitors (DVI-0, 1920x1080 on the right, and, DVI-1,  1680x1050 on the left)

> - what driver is used ?
 Module radeon: vendor="X.Org Foundation"
 compiled for 1.11.2, module version = 6.14.3

> - does it occurs with another windows manager ?
 there is another window manager for gnome3?

> - what does xorg logs say ?
 nothing special, will upload Xorg.0.log as attachment

> And what do you mean exactly by kill dual monitor setup? 
 the dual screen setup reverts to single screen (the left one) during qemu -full-screen 
 (different resolution usually) and back to the correct resolution on exit/quit, but the
 desktop then has shrinked to one display and the right monitor goes to sleep.

> From what I can infer from screenshot, the issue is either "there is a black point" 
> or "I have just one screen".
 just one screen it is

> According to https://bugzilla.redhat.com/show_bug.cgi?id=523296 , the issue is
> likely not in qemu, but in SDL or X.
 could be, will test with some code then ...
Comment 4 Herbert Poetzl 2012-02-29 12:14:16 CET
just verified, issue is still present in Mageia2 Beta1 (and in latest Cauldron)

the secondary screen(s) is(are) turned off and not reactivated when leaving fullscreen.
a crude work around is to open the  'Displays' settings and manually turn the other 
screen(s) back on again.

CC: (none) => herbert

Comment 5 Herbert Poetzl 2012-03-26 23:50:07 CEST
Created attachment 1864 [details]
screenshot of the dual head setup after qemu-kvm --full-screen

the issue got worse with latest Cauldron, the desktop gets messed up now as well.
the screenshot shows the remaining (primary) head with the default gradient background.
note the black area which covers part of the background.
Comment 6 Marja Van Waes 2012-05-26 13:05:54 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 7 Marja Van Waes 2012-07-06 15:06:21 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
Marja Van Waes 2012-07-12 00:12:50 CEST

CC: (none) => marja11
Assignee: misc => bugsquad

Comment 8 Marja Van Waes 2012-08-04 13:22:23 CEST
2x no reply, closing as old.

Feel free to reopen when needed and tell for which version(s) of Mageia this bug is still valid

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