On 03/24/2016 06:08 AM, Takashi Iwai wrote:
On Wed, 23 Mar 2016 19:56:01 +0100, Dominik Kopp wrote:
Ludwig Nussel wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
I've upgraded my tumbleweed to 20160321 (64-bit/KDE) but it fails to start KDE. (it's a Virtualbox installation for testing purposes) Now I'm just at text console - no graphical X.
The journalctl output is truncated due to text mode (at column 80?): ... plymounth is running plymounth is active on VT 7, reusing for :0 plymounth should quit after server startup X server died during startip X server for display :0 cannot be started, Quitting Plymouth without transition ...
Anyone else?
There is a known issue with 4.5 kernel: http://bugzilla.opensuse.org/show_bug.cgi?id=971907
Try to boot vbox with iomem=relaxed kernel boot option as a workaround.
I will try to clarify things a bit. The bug report is a bit terse on the details. Linux has long had a vulnerability in that a root user could read and write arbitrary locations in kernel memory. For developers debugging drivers from user space, this is a feature; however, improper use of this ability could result in dire consequences. A kernel crash would be the most-favorable result. A complete trashing of the file system could also happen. Kernel 4.5 closes this security hole. Unfortunately, the Guest Additions drivers in VirtualBox got caught in the transition as the vesafb video driver needs this access to kernel memory from user space. There are several possible ways to proceed listed from least desirable to most: 1. Turn off this new feature for all openSUSE kernels. This option is rejected as it affects all users, whereas we only need to change the kernel behavior for openSUSE instances in a VirtualBox VM. 2. Change the installation so that the kernel command line has the "iomem=relaxed" option. The objections to this are the same as #1. 3. Have the affected users manually add the iomem option. Even though inconvenient, this is the only workable solution at the moment. 4. Debug and implement the new 5.0.17 version of VB recently published by Oracle. The main intent of this change was to be able to run Guest Additions with versions of X.Org that run without root rights. Once this is working, it will again be possible to use gdm rather than lightdm for Gnome users. Implementing this solution is my current activity. Thanks for your patience, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org