anaconda no progress bar, root or user icons visible

[antikythera]

Has anyone else come across the issue as follows:

1. Start anaconda, set region and language.
2. Set Partitions and Network options etc. okay and then click to proceed.
3. When the partitioning actually starts and you get the warning to set root and user before proceeding nothing else apart from that warning and the help button displays.

The buttons are still there and I managed to get the screens to enter root and user account information successfully by moving the cursor around their rough locations in F20. they just aren't showing. neither is the progress bar.

When the root and user options as well as the progress bar eventually show at the 'configuring initramfs' stage of the install has been reached. Then anaconda performed as normal again.

I found this behaviour on the F21 Beta MATE-Compiz 32-bit spin released today. Running from DVD+RW which passed ISO download checksum and media check after burning.

The attached screenshot was grabbed after I set the user accounts up.

[bbfuller]

Yes, I got that as well. Installing from a Live KDE CD.

I was installing in a quiet environment though and could hear the hard disk chattering away so I just waited and the password screen came up at the very end.

[antikythera]

thanks for the feedback. I've just checked on bugzilla and I can't find it listed after using the search tool. so I'll open a ticket about it.

Edit - Bug ID 1160484

[AdamW]

It's a known bug that is listed in the Common Bugs.

https://fedoraproject.org/wiki/Commo...display-update
https://bugzilla.redhat.com/bugzilla...cgi?id=1142862
https://bugzilla.redhat.com/bugzilla...cgi?id=1103496

[antikythera]

Okay sorry for duplicating then. I did read common bugs list and search but obviously not with matching terms. Some of the bug report headings are not very explanatory. Also no reference to MATE just KDE.

The installer did not freeze though. It carried on installing before eventually redrawing the missing dialogues.

Edit - replied to question about install environment. There was no MATE live ISO before this current beta release.

[AdamW]

Yes, that's what the common bugs note says

It's interesting you saw it with MATE, though. Most of the reports so far have been with KDE, and that's certainly where I've seen it.

[antikythera]

I'd rather it wasn't interesting as I'm sure you would too. However if it means it prevents going down a wrong path with KDE Live ISO specific investigations I hope my report has helped in that sense.

Apart from that hiccup in anaconda, the MATE-Compiz Live ISO rendered normally for the menus, applications and control panel windows I played with prior to install and so has the physical installation since. I'm using it now as per normal.

[antikythera]

A workaround for MATE-Compiz I have found and submitted this evening:

https://bugzilla.redhat.com/show_bug.cgi?id=1103496#c54

I've identified a solution based on comments about Adwaita in post #52 by Matthais.

The MATE-Compiz spin uses BlueMenta by default and what seems to be DMZ pointer scheme. However Adwaita controls and pointer scheme are on present as well. So I tried the following method and have found it worked on both attempts tonight.

1. Open the System menu from the top panel and then Control Center.
2. Open Appearance.
3. Click 'Customize' under the list of themes.
4. Change 'Controls' to Adwaita and do the same for pointer.
5. Close 'Customize Theme', 'Appearance Preferences' and 'Control Center' to return to the desktop.

Then fire up Anaconda via the 'Install to Hard Drive' icon.

I hope the above helps. Even if it is added to common bugs list as a workaround for now. If the same is possible in KDE it should have a similar outcome.

These theme changes are only to fix the display problems manifesting in anaconda. when you restart your computer and boot from the actual installation you will find it back with the BlueMenta controls and MATE pointer scheme.

[antikythera]

This issue has now become a potential release blocker unfortunately:

Discussed at today's blocker review meeting [1]. Accepted as a blocker. This
is a conditional violation of the Final Data Corruption criterion since it
creates the opportunity of data loss to the user (by making them think the
install has hung and the user restarts the machine mid-install). [2]

The decision to whether this must be fixed or at least just documented will
depend on how much we see it in future composes testing. We should certainly do
as much as we can (e.g. fix the spinners) to make this happen as little as
possible.

https://bugzilla.redhat.com/show_bug.cgi?id=1103496

[antikythera]

Solved for MATE-Compiz. Updated mate-themes package in TC2 (available in stable updates repository for Beta-4) fixes spinner.