Installed F21 BETA 4 from USB stick on Lenovo x61 using "nomodeset" to avoid install hangs. Then installed a bunch of packages in a console window. Rebooted and did first log in to cinnamon (which is software emulated due to basic graphics install). The initial setup screens for language and keyboard seemed fine. However the wifi setup screen does not appear to have any exit path! I entered a wifi network password, and it seems to have connected, but there is no visible "next", "proceed", or "finish" button. How do I get past this screen???
Seems that initial-setup isn't in sync with cinnamom, or there is a general issue with wifi and initial-setup. I suggest to pass the wifi setup in i-s and do it later in cinnamon itself. It's to late to change something for release, we're are in release freeze, means most common packages wouldn't be be updated before release.
I used ctrl-alt-fn to get a console window and did a full yum update. After rebooting and logging in again to cinnamon, I was presented again with the initial setup screens which worked fine. Screen navigation buttons showed up fine after doing updates.
good, seems that latest updates fixes the issue. If you have time please confirm that with latest TC2 release. http://alt.fedoraproject.org/pub/alt/stage/21_TC2/
This is still a problem with TC2.iso. Installing Cinnamon without doing all F21 updates will cause a user logging into Cinnamon for the first time to get stuck in the initial setup screens with no apparent way to exit. This time I had already logged in as one user with gnome and had already set up wifi. After making another user account and installing Cinnamon and logging in as the 2nd user, I got stuck in the "Connect Your Online Accounts" screen. No "previous" or "skip" buttons were visible. Again, after using ctl-alt-fn and doing all updates from console screen, rebooting and attempting to log in (for first time) again, all the buttons were visible in the initial set up screens.
Also, this does NOT seem related to emulated or accelerated Cinnamon graphics. I had removed the "nomodeset" from the boot lines (that was necessary to get the install to work). Still didn't show any buttons on the initial login screens...
Reassigned to initial-setup
Are you sure you are stuck in Initial Setup and not in Gnome Initial setup ? Initial setup looks like this: https://m4rtink.fedorapeople.org/anaconda/screenshots/help/help_is.png Gnome Initial Setup looks like this: http://blogs.gnome.org/mclasen/files/2014/03/gis-language.png
Sorry for the sloppy language. The problem shows up in Gnome Initial Setup (according to the screenshots you posted). However, when I'm using Gnome the buttons appear and everything is OK. When I use Cinnamon with a new user login -- before doing full system yum update -- then Gnome Initial setup has no navigation buttons. Since the updates appear to fix the problem, the only issue is probably the specific set of components that will appear together in the F21 distribution.
Created attachment 959896 [details] blacklist gnome-initial-setup I don't see any point to running gnome-initial-setup in cinnamon and intend to blacklist it from xdg autostart unless anyone can see any negatives.
I'm pretty shure that it was a bug in gtk3 itself, which is fixed with latest gtk3 update. We had a lot of bugs in the last 2 month where gtk3-3.14 breaks gui stuff in different applications. TC2 comes with gtk3-3.14.4-1.fc21, but the fixed version is gtk3-3.14.5-1.fc21 @ Bill Can you please test only updating gtk3?
I think when I installed Cinnamon, it might have also updated gtk3. In any case, I already have gtk3-3.14.5-1.fc21 installed without doing any system wide updates -- and the "missing buttons" problem still happens.
nemo-extensions-2.4.x-2.fc21, cjs-2.4.1-1.fc21, cinnamon-translations-2.4.2-1.fc21, muffin-2.4.2-1.fc21, nemo-2.4.3-1.fc21, cinnamon-session-2.4.1-3.fc21, cinnamon-desktop-2.4.2-1.fc21, cinnamon-2.4.4-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/cjs-2.4.1-1.fc21,cinnamon-translations-2.4.2-1.fc21,muffin-2.4.2-1.fc21,nemo-2.4.3-1.fc21,cinnamon-session-2.4.1-3.fc21,cinnamon-desktop-2.4.2-1.fc21,nemo-extensions-2.4.x-2.fc21,cinnamon-2.4.4-1.fc21
nemo-extensions-2.4.x-2.fc21, cjs-2.4.1-1.fc21, cinnamon-translations-2.4.2-1.fc21, muffin-2.4.2-1.fc21, cinnamon-session-2.4.1-3.fc21, cinnamon-desktop-2.4.2-1.fc21, nemo-2.4.4-1.fc21, cinnamon-control-center-2.4.2-1.fc21, cinnamon-2.4.5-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.