Created attachment 5260 [details]
report.bug.xz

for the record, I had recently upgraded a Mga4.1 Gnome-only install on the same system to cauldron, and it still booted fine after the last time it was updated, on June 24th

Created attachment 5261 [details]
journalctl -b with Nouveau

After installing the 32bit GnomeLiveCD on the same NVidia system (from Live mode with Nouveau), and after fixing the GRUB2 bootloader, on reboot it hangs after giving the root password and adding a user.

I don't have time to add the journalctl -b log for that boot, now, I'll try to attach it tonight.
(However, I did see a very similar line to the only "(EE)" one I saw before)

CC: (none) => tmb
Hardware: x86_64 => All
Summary: 5a1: Can't boot into Gnome after Gnome-only install with 64bits classical iso => 5a1: Can't boot into Gnome after Gnome-only install (classical and install from Live session)
Source RPM: drakx-installer-stage2 => (none)

Similar here, journal is attachment 5265 [details]

See also bug 13633

Created attachment 5267 [details]
M5A1i586-Gnome-HD8330GPU

Journal file with several kills and restarts of X. Probably simply not able to handle 3D requirements. This machine won't run Cinnamon, but does do Mate.

CC: (none) => gm4nzg

I had the same hang after the user screen on an Intel machine with on-board graphics.

I logged into tty2 as root and ran systemctl restart prefdm.service and the Gnome3 desktop came up without issue.

On reboot it was fine without further problems.

CC: (none) => zen25000

Same problem on an Intel system with all Desktops installed, I only didn't notice earlier because I used KDM there instead of GDM, which I only tried last night.

Jul 21 22:46:47 DenkBlok3Cauldron5a1 gdm-Xorg-:0[30944]: (EE) systemd-logind: failed to get session: No such file or directory

(In reply to Simon Parsons from comment #5)
> Created attachment 5267 [details]
> M5A1i586-Gnome-HD8330GPU
>
your log also contains:
Jul 07 19:44:56 localhost gdm-Xorg-:0[958]: (EE) systemd-logind: failed to get session: No such file or directory

(In reply to claire robinson from comment #4)
> Similar here, journal is attachment 5265 [details]
your log does, too:
Jul 07 13:11:29 localhost gdm-Xorg-:0[865]: (EE) systemd-logind: failed to get session: No such file or directory

Summary: 5a1: Can't boot into Gnome after Gnome-only install (classical and install from Live session) => 5a1: GDM fails; (EE) systemd-logind: failed to get session: No such file or directory
Source RPM: (none) => gdm

(In reply to Barry Jackson from comment #6)
> I had the same hang after the user screen on an Intel machine with on-board
> graphics.
> 
> I logged into tty2 as root and ran systemctl restart prefdm.service and the
> Gnome3 desktop came up without issue.
> 

Do you still have that install, Barry?
If so, do you mind checking whether youu had the same gdm-Xorg error before restarting prefdm.service, the one about
(EE) systemd-logind: failed to get session: No such file or directory

FWIW, I think the error message is more interesting now with an updated systemd (not yet pushed in cauldron... but soon). In my logs I see:

Jul 22 00:53:23 jimmy gdm-Xorg-:0[3707]: (EE) systemd-logind: failed to get session: PID 3707 does not belong to any known session


So it's referring to itself, but this doesn't seem to be a fatal error here, so thus I think this is a bit of a red herring regarding where the actual issue lies....

Barry's solution works here: after getting
Jul 22 10:54:43 DenkBlok3Cauldron5a1 gdm-Xorg-:0[14772]: (EE) systemd-logind: failed to get session: No such file or directory
and restarting prefdm.service, everything works fine.

I forgot to try whether it's still fine after reboot

(In reply to Marja van Waes from comment #10)
> Barry's solution works here: after getting
> Jul 22 10:54:43 DenkBlok3Cauldron5a1 gdm-Xorg-:0[14772]: (EE)
> systemd-logind: failed to get session: No such file or directory
> and restarting prefdm.service, everything works fine.
> 
> I forgot to try whether it's still fine after reboot

It was fine, I booted fine into Gnome, but the error was still there:
Jul 22 11:06:07 DenkBlok3Cauldron5a1 gdm-Xorg-:0[23132]: (EE) systemd-logind: failed to get session: No such file or directory

So Colin is right about the red herring :-(

(In reply to Marja van Waes from comment #11)

> 
> So Colin is right about the red herring :-(

So the summary of this bug is wrong, but I don't know what to change it to.

jul 05 22:19:37 localhost gnome-session[1272]: (gnome-shell:1308): Gjs-WARNING **: JS ERROR: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found

Both show this. Is your Cauldron fully up to date? I added this require to gnome-shell in Cauldron (some time ago.. more than 1 week).

(In reply to Olav Vitters from comment #13)
> jul 05 22:19:37 localhost gnome-session[1272]: (gnome-shell:1308):
> Gjs-WARNING **: JS ERROR: Error: Requiring Caribou, version none: Typelib
> file for namespace 'Caribou' (any version) not found
> 
> Both show this. Is your Cauldron fully up to date? I added this require to
> gnome-shell in Cauldron (some time ago.. more than 1 week).

well, those log files are from two weeks ago :-)

Anyway:
[root@DenkBlok3Cauldron5a1 marja]# journalctl -a | grep Caribou
[root@DenkBlok3Cauldron5a1 marja]# journalctl -a | grep Gjs-WARNING
[root@DenkBlok3Cauldron5a1 marja]#

Created attachment 5304 [details]
journalctl -a | grep WARNING | grep gnome-session

journalctl -a | grep WARNING | grep gnome-session
does give output, though.

Don't know whether there is anything useful in it. I can't compare the warnings against before and after logging in with GDM started to work fine, now, sorry

Can I have a newer log file? Would be nice to see the log after restarting prefdm (so log contains at least 1 non-working gdm and a working one). I'll do the comparison.

Oops, commenting at same time as logs are attached is not a good idea! :P

Created attachment 5336 [details]
journalctl -b of failing GDM + succeeding restart of dm.service

hit this issue again on reboot, after installing the Mageia5-alpha2-LiveCD-Gnome (i586)

restarting prefdm.service solved the problem again.

I did that ± 14.40h local time, so the part before that in the attached file is from the fail

@ Olav

I can provide the journalctl -a output, too, from the same time, if you think that is useful

Aug 10 14:29:18 localhost /usr/bin/dbus-launch[2636]: gnome-session-is-accelerated: llvmpipe detected.
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: GsmSessionSave: Failed to create directory /var/lib/gdm/.config/gnome-session/saved-session: Permission denied
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: GsmSessionSave: could not create directory for saved session: /var/lib/gdm/.config/gnome-session/saved-session
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: Unable to find required component 'gnome-shell'
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: GsmSessionSave: Failed to create directory /var/lib/gdm/.config/gnome-session/saved-session: Permission denied
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: Unable to find required component 'gnome-settings-daemon'
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: GsmSessionSave: Failed to create directory /var/lib/gdm/.config/gnome-session/saved-session: Permission denied
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: GsmSessionSave: could not create directory for saved session: /var/lib/gdm/.config/gnome-session/saved-session
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: Unable to find required component 'gnome-shell'
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: GsmSessionSave: Failed to create directory /var/lib/gdm/.config/gnome-session/saved-session: Permission denied
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: Unable to find required component 'gnome-settings-daemon'
Aug 10 14:29:18 localhost gnome-session[2636]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Aug 10 14:29:18 localhost gnome-session[2636]: gnome-session[2636]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Aug 10 14:29:18 localhost gnome-session[2636]: Entering running state



Permission problems with /var/lib/gdm, cannot even find gnome-shell. Wtf. I think something is running during boot that interferes with /var and maybe /usr or something. Colin??

CC: (none) => mageia

Same problem here after installing the 5alpha2 Gnome Live 32bits *DVD* from Live mode.

leuhmanu didn't have this when installing the same isos from live mode, so it is maybe related to what hardware is used?

(In reply to Marja van Waes from comment #22)
> leuhmanu didn't have this when installing the same isos from live mode, so
> it is maybe related to what hardware is used?

I've had this bug on those systems:
https://wiki.mageia.org/en/User:Marja/QA/Hardware#Lenovo_3000J_Series
https://wiki.mageia.org/en/User:Marja/QA/Hardware#NVidia_system_from_Alternate
(the lspcidrake -v output is from other installs on those systems)

Setting it to release blocker, because of all the users who won't dare to (or on't understand how to) give a command in a text terminal: for them this can't be fixed after install.

Severity: normal => critical
Priority: Normal => release_blocker

Saw it again with a 5beta1 install from a LiveDVD (Gnome), on again different hardware https://wiki.mageia.org/en/User:Marja/QA/Hardware#Lenovo_ThinkPad_L530 

Brian found an easier workaround: just rebooting lets Gnome come up fine

Whiteboard: 5alpha1, 5alpha2 => 5alpha1, 5alpha2, 5beta1

Is it still valid on Mageia 5 beta 3?

CC: (none) => remi

(In reply to Rémi Verschelde from comment #26)
> Is it still valid on Mageia 5 beta 3?

Not for a classical, Gnome only install: GDM works fine.

I'll try with an install from a Live medium, too

fine after a Live install, too, so closing

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

Feel free to reopen if needed, though, I just noticed that today's tests were on a different system than the three where I've seen this bug :-/

I just experienced this issue too. It happens after a LiveDVD install, so I'm guessing it might be related to the setting of the root password and creation of the main user at the first boot, maybe it doesn't behave too well with GDM/GNOME afterwards?

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

Possibly also the l10n fix bug 14476

It was reported there with the previous fix (not current fix yet) that gdm failed to start on the first reboot but subsequent boots went ok.

Fail whale too after a 5beta3.4 GNOME LiveCD install. Note that in both comment 30 and now, mageiawelcome shows up on top of the fail whale, so it seems the desktop is somehow started.

The mouse cursor is not displayed, but it works too.

Works fine after a reboot, as noted previously.

I confirm the exact same failure for me on Mageia5 B3 Rd4 Gnome live DVD install :

on first reboot, after giving name and password, gnome-session failure, black screen if I enter logout, no ttys usable (black screen with a small strip on top of screen of mageai5 wallpaper).

on second reboot, everything fine including french localisation and azerty keyboard.

CC: (none) => olchal

No fail whale after a classical install using the i586 DVD, so I guess the issue is Live-specific (so actually this is maybe not the same issue as comment 0, should it be moved to another bug report?).

Hi guys,

at fosdem I found out that if your composite extension is disabled (check-out xorg.conf), then you cannot log into gnome (bug confirmed by the gnome guys nearby me).

May this bug be related?

cheers,
chris.

CC: (none) => dirteat

Created attachment 5925 [details]
journal output tail

Booting into live mode from a USB stick on real h/w I see a similar problem.
When GDM log-in should appear, the "Oh No - Something..." dialog appears.
The end of the journal is attached. (Ignore the root login at the end)
Graphics are on-board Intel.

If I understand this correctly, the issue of this bug is that after an installation from a GNOME Live, on first boot, it brings up an UI asking you to set a root password and create a regular user account.  After completing that, it should start GDM, but that fails.  Subsequent attempts to start GDM (via the prefdm service) or reboot the system work correctly.  From Comment 30, Comment 31, and Comment 33, it sounds like this issue is still valid.

Reports of fail whales would be an unrelated issue and should not be discussed on this bug report.

I have no knowledge how all this are implemented; but my comment was about that it *might* be due to the composite extension "feature".

For instance, if the X driver used during the install is Vesa and has no composite extension, that may trigger the first fail, while a reboot or restart X will bring the dedicated X driver with composite on. Someone knowing more how the live stuff works may confirm/reject that interpretation.

cheers.

The live medias always uses dedicated X drivers. it's only the classical installer that relies on fbdev/vesa during install.

I wonder if the fixes for wrong lang/keyboard is the one screwing us this time

I confirm that this bug is still valid in latest Live Gnome DVD 64 bits :

- first reboot : Oops ...
- 2nd reboot : OK

(Live ISO second build 16 March 2015 , Mageia-5-RC-LiveDVD-GNOME-x86_64-DVD)

I would guess that the screen where you set the root password and user account after Live install also uses regular X drivers.

For future reference, the fail whale issue has been reported as Bug 15468.  I guess Olivier is not seeing this issue.

Closing this bug as the initial report (comment 0) has already been fixed. For the fail whale reported from comment 30 onward, please see bug 15468.

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