The community release of the International Standards Organization (.iso) file for the upgrade to or installation of the 64-bit, openSUSE, Leap, 42.2, Linux operating system appears to have actually taken place sometime during the morning of November 16, 2016, Eastern Standard Time; sorry, my earlier posting of the community release date for openSUSE Leap 42.2 was incorrect. During that same day in a process which began with that downloaded .iso file I upgraded my 64-bit, openSUSE, Leap, Linux operating system from version 42.1 to version 42.2 of it. Afterward gratefully the VirtualBox Guest Additions of sharing both a file and the contents of my computer-“clipboard” memory between my host, 64-bit, Windows 10 Home Edition and my guest, 64-bit, openSUSE, Leap, 42.2, Linux operating systems via Oracle Virtual “Machine” (VM) VirtualBox were able to be continued! In copying and “pasting” the text from a file in the text editor KWrite in the openSUSE system to the LibreOffice text editor Writer in the Windows-10 system I found it was important to first save the Writer document containing the text to be transferred in the 8-bit Uniform Transformation Format (UTF-8) encoding, which matched the encoding used in KWrite in the openSUSE, Linux operating system; in a transfer of text via the computer “clipboard” in the reverse direction from Writer to KWrite, I found the matching of the encodings in those two text editors to not be so critically important.–Nevertheless when the encodings in open documents in those two text editors were each UTF-8 and the Writer document had previously been saved in that encoding, the copying and “pasting” of text between those two text editors via the computer “clipboard” gratefully worked well. In the openSUSE system in these tests I used the Lightweight, X Windows System, version 11 (X11), Desktop Environment (LXDE), which appears to be a smaller version of the K Desktop Environment (KDE). Thanks to all of you who kindly worked on the procedure for upgrading from version 42.1 to version 42.2 of the 64-bit, openSUSE, Leap, Linux operating system to make that upgrade work so very well regarding the continuation of both these two functions of the VirtualBox Guest Additions and user groups within Yet another Software Tool 2’s (YaST2’s) User and Group Management!
Now I discuss some other interesting things I noted regarding this upgrade of the 64-bit, openSUSE, Leap, Linux operating system. I had openSUSE Leap 42.1 as one of my installed Virtual “Machines” (VMs) in VirtualBox. To begin the execution of the installation software on that DVD-R I found that it was insufficient to have my upgrade installation DVD-R in my computer’s DVD drive and click on VirtualBox’s “Start.” No, that just started the process of “booting” VirtualBox or my computer into openSUSE Leap 42.1. To instead have VirtualBox execute the installation program on that DVD-R, in VirtualBox I clicked on “Settings,” then on “System,” and then clicked on an upward-pointing arrow beside “Optical” to have my optical drive moved up to the top of the list in the “boot” order above “Hard Disk;” then I clicked on an “OK” software “button.” Then clicking on VirtualBox’s “Start” began the execution of the computer program on the openSUSE DVD-R for the purpose of either installing openSUSE Leap 42.2 or upgrading to it. After I completed this upgrade I returned to VirtualBox’s “Settings,” “System” to return the “boot” order to “Hard Drive” first and “Optical” second by clicking on an upward-pointing arrow beside “Hard Disk” and clicking on the software “OK” “button.”
As a part of this upgrade my installed version of the Linux kernel was updated from 4.1.34-33-default to 4.4.27-2-default. In the past I usually upgraded or made a so-called “clean” (not an upgrade) installation of openSUSE offline from an installation, Recordable Digital Video Disc (DVD-R) after “burning” the .iso image onto a DVD-R for such an upgrade or installation. This meant that afterward I probably updated some installed, openSUSE software packages while online somewhere where a fast Internet service was available free of charge to me. I remember only once performing such an upgrade while online via one or more commands. But in this most-recently completed upgrade of openSUSE I executed the openSUSE installation program from a so-produced DVD-R while online where a fast Internet service was available free of charge to me. And as such I found that this combined, upgrade-and-software-update process actually used a combination of offline and online methods.
This time I chose to read some of the online release notes on https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.2/#upgrade on the Internet for performing an upgrade of openSUSE. My 64-bit, Inspiron-15, 3521 Dell notebook computer uses a Synaptics touchpad. Those release notes included the statement reading, “The Synaptics X driver is no longer supported by GNOME” (GNU’s Not Unix [GNU] Object Model Environment). In openSUSE I have been using the Lightweight X Windows System, version 11 (X11), Desktop Environment (LXDE) and the K Desktop Environment (KDE). So without having read those release notes as carefully enough, perhaps it wasn’t necessary for me to uninstall the software package xf86-input-synaptics in openSUSE Leap 42.1 before upgrading it to openSUSE Leap 42.2; nevertheless, as recommended for the GNOME, I did so by entering the command “sudo zypper rm xf86-input-synaptics” followed by my pressing of the “Enter” key on my computer’s keyboard and then entering my root-user password. I entered those commands in the computer program LXTerminal in the LXDE in openSUSE Leap 42.1. But afterward surprisingly my computer’s touchpad continued to work well in openSUSE Leap 42.1! So because of that I just guess that openSUSE Leap 42.1 might have its own, non-firmware, software package installed at that time for the operation of my computer’s touchpad.
The command “uname -m” gave x86_64 for my computer’s “architecture.” So the part of the release notes on https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.2/#upgrade having to do with the AArch64 computer “architecture did not apply to my computer.
Sometime after selecting “Upgrade” I read something about the “non-oss” repository being non-free. But I also read that the non-oss repository is for computer programs like Flashplayer, Java, et cetera, which I recognized as including some computer programs which are available free of charge to the public. So for at least this reason I accepted the installation of a non-oss repository in my openSUSE Leap 42.2 installation.
After I accepted or agreed to a second, perhaps openSUSE license agreement and clicked on probably a software “button” labeled “Next,” I noticed an apparent rotating action within a small, mostly white-colored disc on my computer screen. In my host, Windows-10 operating system I opened the Windows Task Manager and found that data were being obtained from a “Network” by VirtualBox. Perhaps what occurred inside VirtualBox, such as the openSUSE upgrade software on my openSUSE upgrade DVD-R that was being executed at the time, might have been directly hidden to Windows 10. So I presume that during that time some data were being downloaded from the Internet as part of my openSUSE upgrade procedure. After that process was apparently completed, the next screen to appear contained a list of major actions to be performed regarding various kinds of computer software during the subsequent upgrade procedure. My agreeing to all of those actions and continuing in the upgrade process resulted in 2,740 software packages to be updated, 279 new software packages to be installed, and 125 software packages to be removed. After I clicked on the software “button” labeled “Start Update” and clicked on a tab I think labeled “Details,” I noticed that lots of downloading was taking place.—Unless the term downloading was then being used loosely for copying files from the installation DVD-R to my computer’s hard-disk drive, this could have meant that some files were being downloaded from the Internet.
After those actions were completed I was informed: “Package updates have been found in these additional repositories:”
“…openSUSE-Leap-42.2-Oss….”
“…openSUSE-Leap-42.2-Non-Oss…”
“Start the software manager to check and install these updates?”
I then clicked on a check box beside “Show package updates” and subsequently found at least one python software package, one guile software package, and lots of texlive-… software packages with green-colored check marks beside them. I clicked on the “Accept” software “button,” another “Accept” “button” for an Adobe license agreement, and on a “Continue” “button” to accept software changes needed to accommodate some software dependencies. This resulted in 1,923 more software packages being downloaded probably from the Internet and installed. In support of this hypothesis of those packages being downloaded from the Internet, I did not hear my computer’s DVD drive spinning during such downloading and installing, as would have otherwise been the case if the necessary files would have been obtained from my installation DVD-R instead of from the Internet. Among the files or software packages being downloaded and installed I found wine-gecko, baloo-core, fcitx-config-kde4, gnumeric, and choqok in some of their names, which were not software packages with names beginning with “texlive.” So I guess to keep the size of the installation .iso such that “burning” its image onto a DVD-R would not overfill one, single-layer, 4.7-GigaByte (GB) DVD-R, some software packages, particularly many Teχ Live software packages may not have been included in the openSUSE, .iso, installation-and-upgrade file so that updates to those software packages were being obtained from the Internet while my computer was still online.
In limited use since my most recent upgrade to 64-bit openSUSE Leap 42.2 Linux I have so far tested a few things and gratefully found them to work well in the LXDE. For a fictitious LaTeχ-coded file with a name of the form MyLaTeXFile.tex in the computer program LXTerminal I entered the commands:
pdflatex MyLaTeXFile.tex (twice)
bibtex MyLaTeXFile (twice)
pdflatex MyLaTeXFile.tex (twice)
with a previously prepared file with a name of the form MyLaTeXFile.bib containing references to books and one or more Internet Web pages.
The openSUSE text editors Kate and KWrite appeared to work in openSUSE Leap 42.2. While online in openSUSE Leap 42.2 I could reach three Web pages in the Mozilla Firefox Web browser. With the computer program Okular I could see the contents of the file with a name of the form MyLaTeXFile.pdf produced by executions of the above pdflatex and bibtex commands. My regular and root-user passwords in openSUSE Leap were transferred properly from version 42.1 to version 42.2 of it. My openSUSE /home folder, which is probably on a partition on my virtual “hard drive” separate from my installation of the openSUSE Leap 42.2 operating system, appears to have been left undisturbed in the upgrade from version 42.1 to 42.2 of openSUSE Leap. My desktop shortcuts from openSUSE Leap 42.1 are still present on the desktop of openSUSE Leap 42.2 in the LXDE. Gratefully I can use the Konqueror file manager in version 42.2 as I could in version 42.1 of 64-bit openSUSE Leap.
So far in limited use of my installation of the 64-bit, openSUSE, Leap, 42.2, Linux operating system the only problem, but one which can easily be avoided, that I noticed in openSUSE Leap 42.2 was that at the login screen for openSUSE 42.2 I saw my name, rather than my chosen, openSUSE user name being displayed. Instead choosing “Other” and then entering my openSUSE user name and regular openSUSE password resulted in a PolicyKit error being reported to me which I think was something to the effect that that user name had already been used or assigned.—But nevertheless, via that “route” using “Other” and my openSUSE user name I could still enter the LXDE of openSUSE 42.2! So this PolicyKit error in my case was not consequential toward entering openSUSE Leap 42.2’s LXDE.
After having looked at the release notes before making this upgrade of openSUSE I wonder if some of my past problems in upgrading or installing previous versions of openSUSE could have been avoided by my reading and following some instructions in such release notes, if they were available at those times, before upgrading or installing openSUSE. Overall I am very pleased that gratefully this upgrade of 64-bit, openSUSE Leap from version 42.1 to version 42.2 of it worked very well for me! Thanks, all of you developers!—Put together you appear to have performed your tasks very well! And thanks for providing this upgrade free of charge to the world!