Description of problem:
Doing a pxe install onto a cubietruck which is a dual core Arm machine with 2GiB of ram. the progress bar never updates. if i switch to the root spoke and back it will update to the status at that point in time and not update again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
progress bar does not update
progress bar indicates how far along in the install we are
The progress works as expected on a Highbank system with 4G ram, however when it finished the "Reboot" button did not appear. When the system was manually rebooted the installation had indeed completed and booted normally.
Didn't we already have a report for this? It sounds vaguely familiar.
I'm not seeing any criteria it violates, if the install works. My inclination is -1 blocker.
Yeah, -1 beta blocker. We should of course try and fix it before final...
For the original report - does installation complete? I know it might be tricky to know when it completed but in such case, I think we are ok for Beta. Also as it is confirmed to work on the other ARM machines... -1 blocker for now, we can talk about it later.
This looks like an architecture specific GUI toolkit issue (screen redraw not working), so reassigning to GTK.
anaconda-widgets appears to use gtk3 rather than gtk+, so reassigning.
I don't have any arm hw to test this. Do you see similar screen redraw issues with other gtk apps after install ?
Discussed at 2015-04-09 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot.fedoraproject.org/fedora-meeting-2/2015-04-09/f22_beta_gono-go_meeting.2015-04-09-17.00.html . Rejected as a Beta blocker: doesn't prevent the install from running, just makes it a bit harder to see where it's up to. No criterion seems to be violated.
(In reply to Matthias Clasen from comment #7)
> I don't have any arm hw to test this. Do you see similar screen redraw
> issues with other gtk apps after install ?
it is unknown, I installed Fedora Server. so there is no X on the installed system. what would be a good test? I can install and run what is needed to see.
gtk3-devel has gtk3-demo, which has a progress bar in the Assistant demo (last step), and gtk3-widget-factory, which has activity-mode progress bars on its first page.
gtk3-demo's progress bar does not update, in gtk3-widget-factory the activity bar bellow 50% updates updates, though I tried to compare what I saw on my x86_64 machine and it was not updating on x86_64, nor was it at all readable. I will attach a screenshot of what I saw
Created attachment 1014453 [details]
gtk3-widget-factory on x86_64
Created attachment 1014469 [details]
gtk3-widget-factory on armv7hl
seen with f22 KDE x86_64 RC2 disks-restore USB (dd) to usb HD
froze installer at "Installing software 64%
Retry with DVD to usb HD using terminal "liveinst" which worked correctly
the arm screenshot looks basically as expected.
the x86-64 one looks pretty far from it. Whats going on there ? Some custom theme ?
standard theme. I am running kde. I have not tweaked anything. but I guess that is a side distraction that belongs in a different bug. should all the different activity bars update? or just the one? gtk3-demo's progress bar did not update, so it is repeatable.
Created attachment 1014929 [details]
expected gtk3-demo behavior
Created attachment 1014931 [details]
expected gtk3-widget-factory behavior
I see this in a Centrino 2 core MSI Windbox with 2 GB of memory with install of f22-live- KDE RC-3 from DVD. The same DVD in a system 76 i7 laptop with many cores shows progress all the way to completion. I think it may be related to more than 2 GB memory being required for updates to continue.
Smaller DE's seem to complete or go farther in update of XX%
As a test I also see this in a VM
It seems that the xx% progress gets farther, before stopping, in a VM with more memory assigned.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.