This is upon installing with a traditional, non-Live iso, correct?

If so, then please attach

                  /root/drakx/report.bug.xz 

and attach journal.txt that is the result of running, as root:
   
                  journalctl -ab1 > journal.txt



However, if you used a Live iso, then please attach journal1.txt and journal2.txt that are the result of:

       journalctl -ab1 > journal1.txt && journalctl -ab2 > journal2.txt

Keywords: (none) => 6sta2
CC: (none) => kde, mageiatools, marja11

It concerns a classical ISO installation.
When do I take these reports:
the  "/root/drakx/report.bug.xz" straight after installation
the "journalctl -ab1 > journal.txt" before or after the first MCC run?

(In reply to Herman Viaene from comment #2)
> It concerns a classical ISO installation.
> When do I take these reports:
> the  "/root/drakx/report.bug.xz" straight after installation

Before you install to the same root partition again. If you don't do a fresh install, that file will stay there forever.

> the "journalctl -ab1 > journal.txt" before or after the first MCC run?

I understood that you always run MCC after booting your new install for the _first_ time.

It doesn't matter whether you've rebooted 10 times since then, if you run that command, only the journal from the first time booting into your fresh install until shutting it down will end up in journal.txt.
("journalctl -ab2" is for the 2nd boot until its shutdown, "journalctl -ab8" for the 8th boot, "journalctl -ab" for current and ""journalctl -ab-5" for 5 boots ago)


If you have to redo everything, then run 

       journalctl -ab > journal.txt 

right after step 5 from the steps to reproduce

Thanks :-)

Created attachment 8871 [details]
Installation report

Created attachment 8872 [details]
journal after run of MCC

I've only had a fast look at the journal.

After you start MCC, right before drakconnect gets started, there is

jan 18 09:41:30 localhost plasmashell[2506]: file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
jan 18 09:41:30 localhost plasmashell[2506]: QXcbConnection: XCB error: 2 (BadValue), sequence: 12606, resource id: 73400324, major code: 141 (Unknown), minor code: 3

I don't know whether that can cause the problems you got, but KDE team will know, assigning to them.

It is weird that this only happens upon the first boot after installing Mageia, though... or is that because you never run drakconnect from MCC after consequent boots?

Assignee: bugsquad => kde

@Marja
To your last sentence: this can be a bit different from other people's way of doing. I HAVE to run drakconnect after the first boot, because the Intel 3160 Wifi is not recognized during installation, otherwise I would not have an internet connection.
I guess not many people run drakconnect a second time once they got the internet connection set up. I just booted the laptop to M6 again to the installation I did two days ago, ran drakconnect from MCC, but now no problem appears anymore (I ran updates from MCC). This has been the same behavior quite consistently over the various classical sta iso's up to now.

This is a duplicate of bug 19088, sorry for not checking earlier.

*** Bug 19088 has been marked as a duplicate of this bug. ***

This is happening in each and every sta2 ISO since then, classical and live alike.

Trying to narrow down the problem did the following:
Plugged in a RAlink USB Wifi device. This one is recognized during installation. Made a fresh install on a new partition of an M6-rc Plasma desktop. Configured the Wifi during installation (it mentions at the end "there is a problem....", but never mind). Reboot after completing the installation to the Plasma desktop, and now I cannot provoke the problem with MCC and the desktop becoming quite unusable.
That makes me suspect that in the cases the following is going on: the Wifi is configured at the first reboot, and that involves defining a fully defined host name i.s.o. the localhost.localdomain. This results always in a warning to login/logout to avoid host name problems, which I up to now never did (anyone???). My guess is that Plasma now does have problems with it, and as reported, the problem disappears after logging in again.
So, this might not be a real bug, but it might be worthwile to address the issue somewhere to the users?

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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

After rereading this,

Now nonfree firmwares for Intel WiFi device can be used by Classic Install iso since Mageia 8.

More, testing a new install Mageia 8 from classic ISO, I can use MCC to configure wifi after installation and Plasma behave normally.

CC: (none) => ouaurelien

(In reply to Aurelien Oudelet from comment #13)
> After rereading this,
> 
> Now nonfree firmwares for Intel WiFi device can be used by Classic Install
> iso since Mageia 8.
> 
> More, testing a new install Mageia 8 from classic ISO, I can use MCC to
> configure wifi after installation and Plasma behave normally.

Keep in mind you can not use wifi during install to add online repositories.
It works after install, but not during, which is needed for upgrading.

CC: (none) => davidwhodgins

Tried a new install, and can confirm this problem did not appear anymore. So I agree on the resolved status.