Bug ID 964149
Summary invalid DECLARED bug
Classification openSUSE
Product openSUSE Tumbleweed
Version 2015*
Hardware x86-64
OS openSUSE 42.1
Status NEW
Severity Major
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter misi@ship.hu
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Egbert Eich 2016-01-28 19:47:15 UTC WROTE:

"You are still using the NVIDIA binary driver although you are using
Tumbleweed. I guess, you should have deinstalled it before you switched from
13.2 to TW.

Point is, there is no NVIDIA driver for TW. Using a driver for Leap or 13.2
will most likely lead to issues and this is what you might be seeing here.

Your best option would be to deinstall the NVIDIA driver.

There are some hints on:
https://en.opensuse.org/SDB:NVIDIA_drivers#Easy_way_to_get_NVIDIA_drivers
how to do this.

Since the configuration you are using is not supported, closing as INVALID."

Grrrrrrrrrrrrrrrrrrrrrrr.

I updated from 13.2 to Tumbleweed. The program let me to do it: zypper dup
worked via repository change. Nobody warns me: do this, do that... and what is
supported.
After this I did ONLY such things as the official updates AND install
recommended nvidia driver.
If the legacy xdm would not exist and work the whole system would be a 
catastrophe. It is an (almost fully) WORKING SYSTEM. Was, before upgrade.
I MUST use hardware accelerated nvidia driver and it is a valid option for
OpenSuSE, mo�reover it is a vendor-launched proprietary driver.

You should test the
vnc/ssvnc ---> Xvnc/x11vnc ---> xdm-kdm(or,switched)ssdm ---> other desktop
applications ---> graphical programs combination-chain. The workflow should be
transparent in ideal case.

YOU let me to do this and declared it invalid? It is an incorrect behavior. You
deteriorate my system... then fix it.
What can I do? Throw out the whole system, hardware and software?
You should TEST thoroughly a distribution BEFORE launch instead develop a
system AFTER official launch. It is tragic. If I can not think before what the
circumstances would result, the the configuration will be simply not
supported...


You are receiving this mail because: