Description of problem: First call of drakconf (whether configuring Wifi or repositories) makes desktop behave badly up to not being usable at all. Version-Release number of selected component (if applicable): RC of 22/7/2016, but on Plasma all RC's How reproducible: Only first call of drakconf after installation Steps to Reproduce: 1. Install RC on real hw 2. After installation reboot and open drakconf to configure Wifi (if not done during installation) or repositories 3. Configuration works OK, but after that - Plasma cannot be shutdown via menu, nor can drakconf be called again. - Mate: mouse is gone, does not come back when using Ctr-ALt-Backspace to exit X. Need to power off to get back a working desktop. The problem did not appear again after subsequent reboots.
Did a network install last night. Problem is the X server was not started. Usual indicator is the Mageia Welcome screen does not have the check box andclose button bottom right. Have seen the problem on every clean install. I just reboot out of habit. Problem has been reported in different form a few times.
@ Herman I understand you had done a classical install, and that the problem only occurred after booting into it for the first time. If that is correct, then please run, as root: journalctl -ab 1 > journal.txt and attach journal.txt to this report. @ Bit Twister In case that issue is related, do you mind giving the link to the open bug report about it?
Keywords: (none) => 6RC, NEEDINFOCC: (none) => marja11Assignee: bugsquad => thierry.vignaud
@ Marja, You understand correctly. Now when do you want this journal to be taken?
(In reply to Herman Viaene from comment #3) > @ Marja, > You understand correctly. Now when do you want this journal to be taken? If you are now logged into that install: now :-) the "1" in "journalctl -ab 1" is an argument to the "-b" option. It means the logs from the first time you booted your machine. "2" would show the second boot. "-1" last one before current, "-2" the one before last one. * So "journalctl -ab 1 > journal.txt" should contain the available logs from when you hit this bug. * However, if you're willing to reproduce it, then please do also attach your ~/.xsession-errors from right after you see those problems. * Btw, does switching to tty2 and back help? * And what is the output of lspcidrake -v | grep Card
Also it would help to know what you actually did with drakconf.
@ Marja Adding journalx86-64.txt from x86-64 Plasma installation and journali586.txt from 586 Mate installation. At the end of the file I added the output of the lspcidrake command. @ Thierry In the x86-64 installation I configured Wifi (does not work during installation for Intel 3610) In the i586 installation I configured the repositories. Note: I never use the options in the "Welcome" app, just make sure it never comes back, and I use the normal entry drakconf from the menu.
Created attachment 8288 [details] Journal first boot x86-64
Created attachment 8289 [details] Journal first boot i586
Sorry, the attachments are not from the correct command. I have to run them again.
Created attachment 8290 [details] Journal first boot x86-64 - correct one
Attachment 8288 is obsolete: 0 => 1
Created attachment 8294 [details] journali58 - correct one
Attachment 8289 is obsolete: 0 => 1
The reporter, Herman, filed a duplicate, but that report contains newer information, so closing this one. I had assigned that report to KDE team, because of the plasmashell qt5 error just before the logs from that report show drakconnect gets started *** This bug has been marked as a duplicate of bug 20119 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE