Bug 10358

Summary: Desktop background tiled after screen resolution change
Product: Mageia Reporter: bozonius <bozonius>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: enhancement    
Priority: Normal CC: bozonius
Version: 3   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description bozonius 2013-05-30 05:49:56 CEST
Description of problem:
Aesthetic only; low priority obviously.  After switching screen "resolutions" in VirtualBox, the desktop background (LXDE) appears tiled rather than properly stretched or resized.  Please see http://picpaste.com/m3desktop-aX2R4mw3.png.

Version-Release number of selected component (if applicable):
M3 LXDE 3.5
Virtualbox 4.2.12 OSE (as included with M3)

How reproducible:
Uncertain.  Not anxious to reproduce it, but will try if anyone is interested.

Steps to Reproduce:
1.  Start Mageia 3 in VBox using the desktop (not fullscreen) mode.
2.  Login to LXDE
3.  Switch to fullscreen mode in VBox

Note that AutoResize Guest Display is selected under machine options in Vbox guest.

Reproducible: 

Steps to Reproduce:
Comment 1 bozonius 2013-06-01 22:17:23 CEST
Changing from lightdm to lxdm seems to correct this and my sound problems (#10356).   At any rate, it appears that lightdm does not work well at all in my VirtualBox VM.  I have not tested it on real hardware.
Comment 2 bozonius 2013-06-04 01:07:42 CEST
My conclusions in #10356 comment 2 are not correct.  I was not assessing this problem thoroughly enough, basing my conclusions on only a few variations and little repetition (mostly due to my own schedule).

I set up a VM for testing M3 separately from the VM I use for my actual work on projects, etc.  This test VM is a virgin install with LXDE only (from Mageia-3-i586-DVD.iso). I did not install any other desktops.

Using this VM instead of my working VM, I was able to ascertain behavior patterns.  What I am noticing -- and this seems to be consistent -- is that cold booting in full screen mode to the lxdm/lxde greeter corrupts the screen display.  Note that I do not log in or modify anything in the system.  Warm booting does not do this; the screen will display correctly.  Also, warm or cold booting the VM in Window mode to the lxdm/lxde greeter does not corrupt the screen.

I performed this test just now about 10 times for each configuration (thankfully, my hardware is fast).  I would say I have performed these tests adequately to make this conclusion so far.

PCLinuxOS LXDE spin uses gdm, and that distro has never given me problems like this.  Since both PCL and Mga are kind of "sister" distros in a sense, I may try gdm as a test, as well as lightdm.

I am not sure if/how sounds is or is not affected by the chosen login or display manager.  One problem is that it seems to take a day or more for audio loss to occur, so testing various combinations may take some time.

I am posting this remark in both bugs.
Comment 3 bozonius 2013-06-16 23:32:33 CEST
I may have detected a potential cause of these video problems:  vboxvideo module is not being loaded at all.   This could explain why the monitor seems to be 1600x1200, which is larger than my actual 1280x1040 monitor; note that I do not have this particular video problem in any of my other dozen or so VMs.

I still believe there is a SLIGHT chance this is impacting audio, but I have not had time to test this.  If it is related, it might be some kind of corruption of X11 memory resources.

CC: (none) => bozonius

Comment 4 Marja Van Waes 2015-03-31 16:06:58 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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