![]() This is how a call to it could look like:ĭef install_specs(install=["pkg", main idea is that we drop our own group exclusion code and just tell DNF what to include and exclude in the transaction. ![]() In the proposed DNF API addition mhatina developed there is now a function called install_specs(), which takes two iterables of package/group/module/environment specifications, one including items to include and the other to exclude from the installation transaction. we never told DNF to install an environment, as that would pull all its groups in unconditionally, nullifying our group exclusion logic this included resolving groups belonging to the currently selected environment (if any) this was implemented by resolving all groups requested for installation to a list and then removing all excluded groups from this list (all this in DNF payload on the Anaconda side) Anaconda needs group exclusion to work, even just for the (-nobase and -nocore options for the %packages section) when the Anaconda DNF payload was first written DNF apparently did not support group exclusion in it's API Usernames I tried were and yet all listed below failed the username/password check.I'm currently working on module installation support in Anaconda and I think the new PoC API mhatina added for this can fix this issue with environments as well. As there is a definite use for having access to the command line while installing I would recommend a check that this is indeed the desired action to have while the installer is running.įurther testing of usernames failed to allow me into the terminal. Please not that in the past that tty were non GUI (tty1 was for dmesg logging for errors thrown while installing, however tty were usually available to the user to access the command line, tty7 was generally set aside as the graphical interface for the installer up through 16.x while 17.x and newer moved the graphical installer screen to tty1) and defaulted to a sh/bash or similar command shell without any username/password login. The tty2 screen is now asking for a username/password pair to access tty2 which is NOT ubuntu. It seems that for some reason in Ubuntu 18.04 Desktop the install media which I just downloaded and verified via md5, and sha256 hashes along with using the gpg signatures to validate the md5, and sha256 hashes from that you can not utilize the tty as in past installer executions. ![]() In summary, under normal circumstances, no user name or password should need to be entered when logging into 18.04 CD/DVD and Live or Persistent USB's After suspend, pressing the power button will bring you back to desktop. After logging out, a password is not asked for when logging back in. ![]() Live CD/DVD also uses Live session user for user name, it is supplied automatically. After a suspend simply pressing the power button brings you back to desktop. Grub type installers, ie mkusb also use Live session user as user and a blank password when logging back in. Syslinux type installers including Rufus, Startup Disk Creator, UNetbootin, Universal and YUMI do not use ubuntu as the default user, they use Live session user instead.įor these installers after logging out you can hit enter to log back in.Īfter a suspend simply pressing the power button brings you back to desktop. Try the USB stick on a different computer. Try a different boot disk creator program. I have previously seen this problem caused mostly by bad persistence files.Ĭheck if the problem persists with a live boot (non-persistent).Ĭonfirm there is space in the casper-rw file or partition. The last time I had this problem was after trying to move "home" from / to /home using cut and paste, (I was in a rush).Īfter using rsync to move home, the problem went away. ![]() None of the above have ever worked for me. This is an answer to a very old question. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |