Your message dated Sun, 4 Mar 2012 19:27:25 +0000
with message-id
<CAPQ4b8nh_CV7SRj_zk6vzOK8h_=d_3bhp2auazmqojfp6ul...@mail.gmail.com>
and subject line Re: Does not restore xrandr display settings on exit
has caused the Debian Bug report #497472,
regarding qemu: fullscreen mostly not visible on multi monitor desktop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
497472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497472
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu
Version: 0.9.1-10
Severity: normal
Here I use a two screen desktop of two differently sized monitors. The
default monitor is to the right of the other.
When telling qemu (or kvm) to go fullscreen, it will attempt to show it
on the default monitor (the right one). It shows mostly black there
with only a small slice of the emulated screen visible at the right
edge. The other monitor continues displaying the normal desktop.
As it appears, it creates a fullscreen window the size of the whole
desktop but doesn't place it at the desktop origin. Instead, it places
it at the default monitor origin, which happens to be the one to the
right so most of it will end off screen.
I'm not sure what the correct solution is: Either make it use the whole
X display (and maybe have it split in two) or just use the full size of
the monitor where the qemu window is currently placed. I would lean
towards the latter since there is no emulation of multiple monitors and
the emulated OS can not react to it correctly.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages qemu depends on:
ii bochsbios 2.3.7-1 BIOS for the Bochs emulator
ii libasound2 1.0.16-2 ALSA library
ii libbrlapi0.5 3.10~r3724-1+b1 braille display access via BRLTTY
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libncurses5 5.7+20090110-1 shared libraries for terminal hand
ii libsdl1.2debian 1.2.13-4 Simple DirectMedia Layer
ii openbios-sparc 1.0~alpha2+20080106-2 SPARC Open Firmware
ii openhackware 0.4.1-4 OpenFirmware emulator for PowerPC
ii proll 18-4 JavaStation PROM 2.x compatible re
ii vgabios 0.6b-1 VGA BIOS software for the Bochs an
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages qemu recommends:
ii debootstrap 1.0.10 Bootstrap a basic Debian system
ii sharutils 1:4.6.3-1 shar, unshar, uuencode, uudecode
ii vde2 2.2.2-3 Virtual Distributed Ethernet
Versions of packages qemu suggests:
pn samba <none> (no description available)
ii sudo 1.6.9p17-1 Provide limited super user privile
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.2.15-1
Hello,
Thank you for your interest in improving Debian, and sorry to keep the
bug unattended for so long. There's now an effort to review the open
bugs related with SDL packages.
I think that this has been fixed, even if indirectly, by disabling
XRandR support by default (this was released with 1.2.15-1):
http://www.libsdl.org/release/changes-1.2.html
"XRandR support is disabled by default because it causes desktop
reconfiguring. It can be enabled with the SDL_VIDEO_X11_XRANDR=1
environment variable, or by applying this patch:
http://hg.libsdl.org/SDL/raw-rev/8ec3036098df"
All of the merged bug reports do not seem to complain that the
applications don't run with several monitors at once (it would be
difficult/confusing/annoying to play most games with the screen split,
I guess), but that the displays are messed up when the application
exits, so this not-support-by-default fixes that.
So I think that it's safe to close the bug report now. Please reopen
if you still experience problems related with this, or if you think
that there should be a betteer solution.
Regards.
--- End Message ---