Created attachment 6303 [details]
lightdm logs from 2nd boot

If it's ok on 2nd boot, it might be because the /usr/share/mga/backgrounds/default.jpg symlink would be broken on the first boot, and then /etc/X11/xinit.d/01mga-bg-res fixes it on the first boot.

CC: (none) => rverschelde

Mate install is the same but only once plymouth is activated. Previously booted the mate install without "splash quiet" kernel options due to bug 15666 and it displayed the background image on the first boot. 

Adding the kernels options now causes the grey background on the mate install across several boots so far.

CC: (none) => tarakbumba, tmb

I just did a fresh install of mga5 April 17 using the boot.iso I installed Mate with Lightdm, no background image, only a black screen, login & Mate worked fine.
I saw /usr/share/mga/backgrounds/default.jpg listed but what is the default.jpg? 

Each reboot it would continue to have a black screen for login until I added my own. I added my own background image in place of the default.jpg

CC: (none) => saptech

Didn't manage to reproduce this with x86_64 install from boot-nonfree.iso a few days ago.

FWIW, I've never seen this in my many installs of the Cinnamon desktop, which defaults to using LightDM.

CC: (none) => mageia

Valid 5 final first build. Mate install from classic DVD 32.

Summary: Lightdm has no background image on first boot just plain grey - XFCE install => Lightdm has no background image on first boot just plain grey - XFCE & MATE

(In reply to claire robinson from comment #7)
> Valid 5 final first build. Mate install from classic DVD 32.

Still no luck when trying to reproduce this. However there's gray bg for short time before mageia bg appears.

Could you give some specs about your machine? And lightdm logs when you can see gray?

Seems there are people who can reproduce this [1] and upstream has pushed a new lightdm-gtk-greeter release [2] which should fix the issue.

However, would be nice to get some debugging data about the issue with 'allow-debugging=true' added to /etc/lightdm/lightdm-gtk-greeter.conf.

I've also updated lightdm-gtk-greeter locally to the latest version and I can commit changes to SVN if it's decided to update lightdm-gtk-greeter before mga5.

[1] https://wiki.archlinux.org/index.php/LightDM#White_screen_after_upgrading_the_GTK_greeter_to_2.0.0
[2] http://lists.freedesktop.org/archives/lightdm/2015-May/000795.html

Apologies Jani. I missed your previous request. I plan to test more tomorrow so will check it then.

I can confirm that I can reproduce this, when two screens are attached to the box.

CC: (none) => makowski.mageia

I only have one screen/monitor. I guess that's why I never managed to reproduce the issue. I'll push new lightdm-gtk-greeter to core/updates_testing after mga5 is released.

Created attachment 6731 [details]
lightdmlogs.tar.gz

Sorry for not getting back to this. I finally got around to an xfce installation again with the latest pre-final isos and can confirm the issue is still present.

Only one 19" VGA connected monitor attached here though and nouveau video if that's relevant. Resolution is 1680x1050@60Hz.

After adding allow-debugging = true (at the top of the file, underneath where it is commented there) from tty2 before completing first login after installation and rebooting the background is then black. 

Attaching lightdmlogs.tar.gz which contains the /var/log/lightdm directory after the reboot and login.

After re-commenting allow-debugging and rebooting the background has returned to grey. If I then log the user out the background is themed as it should be, but when rebooted again from there the background has returned to grey.

Created attachment 6732 [details]
journal.txt

It's maybe worth noting that when the password is entered and enter pressed, the mageia themed background displays instantly, as if it is hiding beneath the solid grey.

Attaching the journal too in case it is helpful, it should show 4 or 5 boots.

Add IN_ERRATA.

CC: (none) => shlomif
Whiteboard: MGA5TOO FOR_ERRATA => MGA5TOO IN_ERRATA

(In reply to claire robinson from comment #13)
> After adding allow-debugging = true (at the top of the file, underneath
> where it is commented there) from tty2 before completing first login after
> installation and rebooting the background is then black. 
> 

Unfortunately it was added to a wrong place so there aren't any interesting data in the logs. The correct place would have been after [greeter] line.

Cinnamon too. I'll get the debug again tmrw.

Summary: Lightdm has no background image on first boot just plain grey - XFCE & MATE => Lightdm has no background image on first boot just plain grey - XFCE, MATE & Cinnamon

Created attachment 6742 [details]
lightdmlogs2.tar.gz

confirmed debug info present in these \o/

Attachment 6731 is obsolete: 0 => 1

Pushed new lightdm-gtk-greeter [1] to core/updates_testing. Please test if it fixes background issues and doesn't cause a new ones.

[1] lightdm-gtk-greeter-2.0.1

RPMS:
lightdm-gtk-greeter-common-2.0.1-1.mga5
lightdm-gtk3-greeter-2.0.1-1.mga5

SRPMS:
lightdm-gtk-greeter-2.0.1-1.mga5

Advisory committed to svn.

CC: (none) => davidwhodgins
Whiteboard: IN_ERRATA => IN_ERRATA advisory

Testing Mageia 5 x64

I don't know whether this test is valid, because I have all Desktops & Display Managers installed (Classic). I wonder whether the bug relates to *single* desktop installs of Cinnamon | Mate | XFCE. All I got was confusion, not helped by the fact that LightDM does not seem to allow you to choose Desktops, so to try the three Desktops in question meant using MCC to change to (say) KDM to select the Desktop to try, then MCC again to revert to LightDM for next session. Et seq.

I never saw a blank background using LightDM with the 3 desktops pre-selected.
OTOH Any pre-selected desktop was basically ignored, so I never saw Cinammon or Mate from LightDM: it always threw up XFCE. Perhaps this is intentional.

[And I hit another problem that I have noticed since using Mageia 5: sometimes from some minority desktops MCC does not work from the taskbar icon nor menu, only from the command line. Another bug *if I can pin it down*].

CC: (none) => lewyssmith

That other bug does seem to be ephemeral.  It appeared briefly for one machine here, running under Mate, disappearing after a reboot.

CC: (none) => tarazed25

Adding to my Comment 22 above, Mageia 5 x64, Classic install with all Desktops & all Display Managers.

I find now that I already had the updated packages:
 lightdm-gtk-greeter-common-2.0.1-1.mga5
 lightdm-gtk3-greeter-2.0.1-1.mga5
but whether my testing was valid remains doubtful, because of LightDM always showing XFCE.

@Jani
- Does this test really demand an installation with just one of Cinnamon | Mate | XFCE ?
- Would you expect it to go unconditionally to XFCE in multi-desktop setups (which include XFCE)? Is there any way of making it go to Cinnamon or Mate?

(In reply to Lewis Smith from comment #24)
> - Would you expect it to go unconditionally to XFCE in multi-desktop setups
> (which include XFCE)? Is there any way of making it go to Cinnamon or Mate?

You should be able to select the desktop from the top menu bar in the LightDM greeter. On my system it is an icon looking like a small spanner.

(In reply to Martin Whitaker from comment #25)
> You should be able to select the desktop from the top menu bar in the
> LightDM greeter. On my system it is an icon looking like a small spanner.
Thanks a bunch; who would have thought it? I had never noticed the menu bar (one does not expect one for a Display Manager login dialogue), and the desktop list icon on the RH side is ultra-discrete. FWIW It changes its form (if you have good eyesight) according to the desktop selected.
It made re-testing with the update installed really quick.

Testing Mageia 5 x64 using the updated LightDM.

The screen background was the correct Mageia 5 one until such time as the desktop took over. So the update looks OK.

Whiteboard: IN_ERRATA advisory => IN_ERRATA advisory MGA5-64-OK

I should add that the correct result is true even after re-booting. But if the bug really is for only the first boot after installation, no-can-do.

@Philippe re Comment 11
If you can see the bug, can you try the update?

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0082.html

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