Bug 33177

Comprueba si es la version del kernel 6.6.28 el systema que no puedes entrar. Si es así, prueba a desconectar el cabre de red. Luego inicia el sistema y prueba a entrar sin conectar el cabre Luego trabaja sin conectar el cable. Si todo funciona bien conecta el cable y espera a que se congele (ocurre a los pocos minutos). Y comenta
Posible fallo https://bugs.mageia.org/show_bug.cgi?id=33157

CC: (none) => ricardalfe

(In reply to Ricard Alfe from comment #1)
> Comprueba si es la version del kernel 6.6.28 el systema que no puedes
> entrar. Si es así, prueba a desconectar el cabre de red. Luego inicia el
> sistema y prueba a entrar sin conectar el cabre Luego trabaja sin conectar
> el cable. Si todo funciona bien conecta el cable y espera a que se congele
> (ocurre a los pocos minutos). Y comenta
> Posible fallo https://bugs.mageia.org/show_bug.cgi?id=33157

Check if the system you cannot enter is kernel version 6.6.28. If so, try disconnecting the mains cable. Then start the system and try to enter without connecting the cable. Then it works without connecting the cable. If everything works well, connect the cable and wait for it to freeze (it happens after a few minutes). and comment
Possible failure https://bugs.mageia.org/show_bug.cgi?id=33157 

Sorry I copied the google translation wrong

Reinstalling is still working. But since the bug showed up after the system had had a new installation and had been working for almost a month, it is a bit early to say it was solved.The situation is certain different from that of id 33157.

Bill, please post the output of
 $ inxi -MSG
to summarise the problem system.

That other bug commented about the network cable; Ricard's comment 2 mentions "the mains cable", presuming a laptop.
@Ricard: did you really mean the power cable?

The kernel version might matter: my own kernel-desktop-6.6.28-1.mga9.x86_64 arrived on 23rd April. You suggest that the system in question worked for a time. Can you confirm this?

And, at boot time, choose the previous kernel to see what happens.

CC: (none) => lewyssmith

Unfortunately I am 3000 miles away from the machine at present and since the machine was needed to do work with, I reinstalled Mageia 9 onto a new partition (I always keep two for reinstallation if needed)

It now works. However, when the old home  files were reinstalled into the user space, The same problem reappeared. so it seems that there is some problem in the user config that tirggered the problem. What it is/was is still mysterious.
But it is working now on the new partition, and It is hard to test the old partition out some more since the machine is needed to do actual work.

But what says that is not the full answer is a) that it did it with both sddm and lightdm, and it also did it when I installed a new test user.

Something has been made very fragile  in X in Mageia 9.

Note also that I have no problem with network cable (It is a laptop and only uses wireless) or with power cable.

(In reply to w unruh from comment #5)
> I reinstalled Mageia 9 onto a new partition
> It now works. However, when the old home  files were reinstalled into the
> user space, The same problem reappeared. so it seems that there is some
> problem in the user config that tirggered the problem. What it is/was is
> still mysterious.
This is important. When and if you are able, perhaps try the 'new' HOME (as installed & working) in the 'old' HOME directory. Repeat: if & when.

It is 120GB.
Originally we had two homes. The one installed with the installation of 
Mageia, /home/d and the other (115G) located in /local/home/d  .
/home/d worked. /local/home/d did not. (changed the home directory in 
/etc/passwd). At that point confusion followed, trying to figure out what 
happened. At one point I made two users with the same uid ( since 
/local/home/d had the same uid as the ser d had in the new instalation. Then 
the fog of much confusion followed. At one point we had a working system with
the bootup directory being /home/d, while $HOME was /usr/d. while pwd gave 
/local/home/d.  (how that
could happen I have no idea.). Anyway, we finally pointed /home/d as a link to
/local/home/d, abd it worked. We have no idea what we did to make it work.(It
is not helped by the fact that the computer was at my son's, and we could onl
communicate by phone, and  had to give him detailed instructions, and was also
temporarily bereft of the family car so could not drive to his place.)

So, at present both the originally installed home directory ( usually at /home/d
and the present Mageia 8 home, on /local/home/d, which is linked by /home/d pointint to /local/home/d work properly.
So I too would like toknow what wolved it. Sorry:

Thank you for your successful manipulations (although the mention of Mageia 8 is uncomfortable).
I think this has got too convoluted to pursue.
(In reply to Lewis Smith from comment #4)
> The kernel version might matter: my own kernel-desktop-6.6.28-1.mga9.x86_64
> arrived on 23rd April. You suggest that the system in question worked for a
> time. Can you confirm this?
> And, at boot time, choose the previous kernel to see what happens.
It is now too late to try this.

Closing, but you can re-open the bug if & when you can get back to the non-working system, and answer the questions.

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