Description of problem: Started occurring after system s/w update June 1 2019: "Preparing... ############################################# 1/12: kernel-desktop-4.14.121-1.mga6" Version-Release number of selected component (if applicable): See above How reproducible: Steps to Reproduce: 1. Do Mga6 s/w update available June 1 2019: "Preparing... ########################################### 1/12: kernel-desktop-4.14.121-1.mga6" 2. Boot system and login one user 3. Log single user out. 4. Login Greeter fails to re-appear. Have to reboot. N.B. Can Switch/login to 2nd user and then flip back to 1st user.
After step 3, please switch to a console (alt+ctrl+f2), login as root and then run "journalctl -b> journal.txt", "gzip journal.txt". Reboot, and attach journal.txt.gz to this bug report.
CC: (none) => davidwhodgins
> ...switch to a console (alt+ctrl+f2), No can do! As I said in 4. above, I have to force a reboot (Alt+Ctl+PrtScr+B),as system (black screen) does not respond to any Alt+Ctl+F...
P.S. Just tried the 'logout sole user' on HP Probook 450 with Mga6.1 - no problem. However, that is using 4.14.122-desktop-1.mga6 kernel whereas this desktop is still on 4.14.121-desktop-1.mga6 (and urpmi reports "Packages up to date"...). Also checked on ThinkPad 11e: No 'logout sole user' problem, either with 4.14.119-desktop-1.mga6 kernel or after update to 4.14.121-desktop-1.mga6 kernel.
(In reply to Dave Hodgins from comment #1) > After step 3, please switch to a console (alt+ctrl+f2), login as root and > then run "journalctl -b> journal.txt", "gzip journal.txt". > > Reboot, and attach journal.txt.gz to this bug report. (In reply to Maurice Batey from comment #2) > > ...switch to a console (alt+ctrl+f2), > > No can do! As I said in 4. above, I have to force a reboot > (Alt+Ctl+PrtScr+B),as > system (black screen) does not respond to any Alt+Ctl+F... After the forced reboot, as root journalctl -b -1 > journal.txt would have given you the logs from when the system froze. You've probably rebooted more often now. If you rebooted 4 times, you'd need to run journalctl -b -4 > journal.txt Please change the number in the command to the real amount of reboots.
CC: (none) => marja11
> ...change the number in the command to the real amount of reboots. Have lost track of how many reboots since the problem appeared! Anyway, I have tried: journalctl -b -x > journal.txt with x=5,4,3,2,1 but could find no journal.txt file... What to try next?
(In reply to Maurice Batey from comment #5) > > ...change the number in the command to the real amount of reboots. > > Have lost track of how many reboots since the problem appeared! > > Anyway, I have tried: > > journalctl -b -x > journal.txt > > with x=5,4,3,2,1 but could find no journal.txt file... > > What to try next? Do you see any output when you run, as root, e.g.: journalctl -b -5 If there is no output at all, then try whether this gives output: journalctl -a If that doesn't give any output, either, then I'm wondering whether your system got corrupted by force rebooting (or did you first use the other magic keys? the order I do usually use is "R S E I U B", but I think most others use a slightly different order.
[root@pc18 ~]# journalctl -a -- Logs begin at Sun 2018-09-16 12:48:58 BST, end at Wed 2019-06-05 18:27:55 BST. -- Sep 16 12:48:58 localhost systemd[17469]: Reached target Paths. Sep 16 12:48:58 localhost systemd[17469]: Reached target Timers. Sep 16 12:48:58 localhost systemd[17469]: Listening on Sound System. Sep 16 12:48:58 localhost systemd[17469]: Reached target Sockets. Sep 16 12:48:58 localhost systemd[17469]: Reached target Basic System. Sep 16 12:48:58 localhost systemd[17469]: Starting GnuPG private key agent... Sep 16 12:48:59 localhost gpg-agent[17475]: gpg-agent[17475]: directory '/home/live/.gnupg' created Sep 16 12:48:59 localhost gpg-agent[17475]: gpg-agent[17475]: directory '/home/live/.gnupg/private-keys-v1.d' created Sep 16 12:48:59 localhost gpg-agent[17475]: gpg-agent[17476]: gpg-agent (GnuPG) 2.1.21-3.1.mga6 started Sep 16 12:48:59 localhost systemd[17469]: Started GnuPG private key agent. Sep 16 12:48:59 localhost systemd[17469]: Reached target Default. Sep 16 12:48:59 localhost systemd[17469]: Startup finished in 118ms. Sep 16 12:48:59 localhost systemd[17469]: Stopped target Default. Sep 16 12:48:59 localhost systemd[17469]: Stopping GnuPG private key agent... Sep 16 12:48:59 localhost gpg-agent[17475]: gpg-agent[17476]: SIGTERM received - shutting down ... Sep 16 12:48:59 localhost gpg-agent[17475]: gpg-agent[17476]: gpg-agent (GnuPG) 2.1.21-3.1.mga6 stopped Sep 16 12:48:59 localhost systemd[17469]: Stopped GnuPG private key agent. Sep 16 12:48:59 localhost systemd[17469]: Stopped target Basic System. Sep 16 12:48:59 localhost systemd[17469]: Stopped target Sockets. Sep 16 12:48:59 localhost systemd[17469]: Closed Sound System. lines 1-21
(In reply to Maurice Batey from comment #7) > [root@pc18 ~]# journalctl -a > -- Logs begin at Sun 2018-09-16 12:48:58 BST, end at Wed 2019-06-05 18:27:55 > BST. -- > Sep 16 12:48:58 localhost systemd[17469]: Reached target Paths. <snip> > Sep 16 12:48:59 localhost systemd[17469]: Closed Sound System. > lines 1-21 That looks bad, no logs at all, apart from a few lines from 9 months ago. You might want to try whether an "upgrade install" with a Mageia 6 network iso fixes all the issues you have with Mageia 6 on this computer
Keywords: (none) => NEEDINFOEver confirmed: 1 => 0Status: NEW => UNCONFIRMED
Not on my 'production' 6.1 install! As I said, I can manage by switching users instead of just logging User A off. Hopefully it won't be long before I can switch over to the Mageia-7 Release... But it is rather odd that even then when I log sole user A off the Login Greeter does not re-appear, though it does if I 'switch user'.
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
CC: (none) => ouaurelienResolution: (none) => OLDStatus: UNCONFIRMED => RESOLVED
Of course - it's time is up! :-)