This may happen on some graphical cards' models, but do not worry — the installation process is still going on despite the animation issue.
This issue may happen if the installation is performed on the Virtual Machine or on the disk which has no partition table. Please try again and chose the option "Clear the whole disk" or "Custom partitions setup".
The proprietary graphical drivers should be installed using the 'The VideoCard setup' utility (console comand: XFdrake). You should wait patiently for the utility to finish its work and for the reboot request. For the simple NVidia non-hybrid system owners (not NVidia+Intel) there is an alternate way: just install the package x11-driver-video-nvidia-current. This option is also useful in case when the XFdrake says your system is the hybrid one while it is not.
In most cases the XFdrake utility ('The VideoCard setup') will install the hybrid drivers automatically. But there is an issue on the hybrid systems when ROSA won't switch to the discrete card automatically. To lunch the setup utility on such hybrid systems please use the commands 'primusrun' or 'optirun'. For example, 'primusrun glxinfo|grep OpenGL' will print the OpenGL version which corresponds to the driver version (free or proprietary)/ Do not forget that Mesa is a free driver.
Try to enable the old acceleration mode for the Intel cards by installing the package x11-driver-video-intel-config-uxa and rebooting.
You may find alternate drivers packages in ROSA repos for the following cards: Mediatek MT7630E - dkms-mt7630e Realtek RTL8812AU - dkms-rtl8812au Realtek RTL8723BE, RTL8723AE, RTL8192CE, RTL8192SE, RTL8192DE, RTL8188EE, RTL8192EE, RTL8821AE - dkms-rtlwifi_new Realtek RTL8101/2/6E - dkms-r8101 Realtek RTL8168*/8111* - dkms-r8168
By default for Broadcom cards ROSA uses wl driver, but you may also try the b43 driver: install the package b43-firmware, delete the package dkms-broadcom-wl and reboot
Run alsamixer in console, press F6 to choose your card and setup the levels. OR Run pavucontrol and choose right in/out devices
Some Hewlett Packard printers require proprietary drivers to work correctly. To install them you just need to connect the device, wait for the auto-initialization and then run the console command 'hp-plugin'
To have the dual boot (i.e. latest versions of Windows and ROSA9) to work correctly on the same machine we recommend to switch off the "fast startup" feature of Windows. That feature is identical to the sleeping mode of ROSA, so we try not to touch the partitions with "sleeping" Windows because we don't want to brake it. To switch off the Windows just run the following command with the root privileges: 'powercfg -h off'
To force mount the NTFS disk run the following: # ntfsfix /dev/<NTFS_partition>(sda, sdb)
This can happen because of the "fast startup" feature of Windows, or due to the incorrect switch off of the Windows OS by the user, which act coincided with the GRUB/kernel updates in ROSA. The ROSA bootloader won't mount the partition/disk containing errors or the partition containing the hibernated Windows. To fix the problem do the following; mount the NTFS disk in the Dolphin filemanager run in the console: # update-grub2
Your desktop settings were damaged somehow (did you switched off the system correctly?) Run 'krunner alt+F2' and enter the command 'kde4-reset'. You desktop settings will be reset to default.
In order to make "bibliography database" service work in LibreOffice, you should install LibreOffice Base ({pkg|libreoffice-base}} package) and OpenJDK. To save space, we have removed these packages from ROSA Desktop Fresh installation image.
Your RPM base is possibly damaged. To restore it run from the root: rpm-restore
You have been activated the ROSA freeze mode. Deactivate it.
Run from the Firefox menu: 'settings-applications-content type-language' and add your language
Please install the LibreOffice Base (package libreoffice-base) and OpenJDK since it is not included into ROSA installation ISO because of the space saving reasons
Install libreoffice-openclipart package.