Description of problem: Clean network install and first user login has the Mageia Welcome pop up with a black screen, no task bar or right mouse click menu Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. clean install 2, reboot and wait full 7 minutes for hardware detection to complete 3. log into user account. Reproducible: Steps to Reproduce:
*** Bug 17634 has been marked as a duplicate of this bug. ***
Blocks: (none) => 17523Assignee: bugsquad => mageia
Confirming I've seen the same in several existing cauldron Plasma5s, so *not* after the first boot after installing, but after some updates last week. In all of them, starting Plasma5 from sddm once wasn't enough, I had to stop my session with alt+ctrl+ del and start a new one. (Side note: according to loginctl, the first user session kept closing forever.. should alt+ctrl-del have completely closed it?) The updates I ran when I came back from Fosdem fixed the issue, at least on this laptop: now the first time I start Plasma5 it comes up fine.
CC: (none) => marja11
Adding 6dev1 on the whiteboard, because current QA isos seem to have the issue, too
Whiteboard: (none) => 6dev1
(In reply to Marja van Waes from comment #2) > Confirming I've seen the same in several existing cauldron Plasma5s, so > *not* after the first boot after installing, but after some updates last > week. Agreed, Just create a test account, say junk. It will have the same problem(s). > In all of them, starting Plasma5 from sddm once wasn't enough, I had to stop > my session with alt+ctrl+ del and start a new one. > > (Side note: according to loginctl, the first user session kept closing > forever.. should alt+ctrl-del have completely closed it?) Have noticed using a root terminal to pkill -u user_here followed by a pkill -9 -u user_here gives be a better chance of next login working correctly. My KillUserProcesses=yes change in /etc/systemd/logind.conf has not helped.
(In reply to Marja van Waes from comment #2) > > The updates I ran when I came back from Fosdem fixed the issue, at least on > this laptop: now the first time I start Plasma5 it comes up fine. Forget that, it may have been just luck. When I started this laptop today, it happened again :-(
Is this bug still valid for the released 6dev1 isos (or fully updated cauldron)?
Keywords: (none) => 6dev1Whiteboard: 6dev1 => (none)
(In reply to Marja van Waes from comment #6) > Is this bug still valid for the released 6dev1 isos (or fully updated > cauldron)? I'll have no real time to test it for the next week or so. I keep a summary list of my bug reports. On each iso release I try to go through the list and verify if they are fixed regardless if marked resolved here. This bug is in my current list of 98 to be tested. My plan is I'll change mga6: to 6dn: if test fails on each new iso release. Hopefully that should cut down on "bug still valid" messages. :)
Tried two different new accounts and a few logins. Problem appears to fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED