Description of problem: After update I got stuck at Starting command Scheduler. I tried many things recommended on the web and nothing works. I reinstall mageia without formating /home and still nothing works. I did a full reinstall and formated all partitions and still doesn't work.. I Used the network installation. I still get stuck at Starting command Scheduler Using Mageia 7 Cauldron 64bit (Non-Free and Tainted repos activated) with all updates as today Oct/17/2018 Using a Dell Latitude E6320, Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz , Intel(R) HD Graphics 3000, 6gigs Ram. Please Advice.. Regards,
Which Desktop environment and which Display manager do you use? (In reply to Ezequiel Partida from comment #0) > > After update I got stuck at Starting command Scheduler. > I suppose that should be "Starting Command Scheduler"? When you end up at that message again, please try to switch to tty2 with Ctrl+Alt+F2 Do you get a prompt? if you do get a prompt, then log in there, become root and issue the following command: systemctl list-units --type target | grep ^g What does that command return? If you don't get a prompt, then please attach /root/drakx/report.bug.xz from the root partition of that install (using e.g. a Live DVD to grab it)
CC: (none) => marja11Keywords: (none) => NEEDINFO
Hello Marja, Thank You for your help! > systemctl list-units --type target | grep ^g > Reports: getty.target loaded active active Login Prompts There is the file from /root/drakx/report.bug.xz from my dropbox (Sorry, I don't know how to attach files here if possible) https://www.dropbox.com/s/6k1el9h7k2j5zao/report.bug.xz?dl=0 I also noticed that when I rebooted sometimes it also stops at: [ 7.152130] usb 1-1-port4: unable to enumerate USB device I got in to another tty and did a systemctl list-units --type target | grep ^g but I got the same message as before. Thank You Marja
I forgot to tell you that I am using Plasma fresh install. Regards
Hi Ezequiel, For the reinstall, you've hit bug 22593. Please run, as root: systemctl set-default graphical.target and reboot. If you still don't get the graphical login screen, then you'll also need to run, again as root: systemctl enable sddm.service and systemctl start sddm.service For the original problem: If your original install was also a Plasma5 install, then you were most likely bitten by the qt5 stack update that hadn't completely landed on all mirrors. I know David Geiger informed dev ml a few hours before you filed this report that they finished updating them, but that only means those packages were all pushed to the build server, not that they all landed on all mirrors and, unfortunately, not even that they were all built successfully... at least qtwebglplugin5 wouldn't build until hours after you filed this report. Anyway, closing this report as duplicate of bug 22593 for the second issue. *** This bug has been marked as a duplicate of bug 22593 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
Forgot to say: KDE-team is pushing many more updates, the qt5 stack was only the first part! Please don't update your install until not-to-soon after there's a message in the "[dev] Qt/KF5/Plasma update"-thread that they finished them all.
Thank very much Marja I love having this "problems" since this helps me learn more about Mageia. I will wait fot the updates and continue working on my other laptopn with Mageia 6.1. Regads
> systemctl enable sddm.service > and > systemctl start sddm.service Did the trick. Thanks again.