http://bugzilla.novell.com/show_bug.cgi?id=607055
http://bugzilla.novell.com/show_bug.cgi?id=607055#c2
--- Comment #2 from Reinhard Max
i can't clearly understand to your severity/priority changes ..
If some minor functionality of an application was broken for so many years without anyone complaining about it there doesn't seem to be a high demand or expectation for it to be working and hence fixing it has much lower priority than e.g. bugs in the main functionality of packages or security issues.
i always thought, that if something doesn't work as expected, it's a bug and it should be fixed.
Yes, but because we can't fix everything at once, we have to prioritize things.
i gave you a clear and straightforward resolution in #591834.
Just adding that vncconfig tool won't do the trick, because the tool is speciffic to tigervnc and won't work with tightvnc (of which we only use the viewer, BTW) or the XF4VNC server. Instantly switching to tigervnc is not an option either, because we've put quite some bug fixes and additional features into our tightvnc package, which means I'll have to do a lot of testing and probably forward porting of our patches when switching to some other vnc implementation, for which I don't have the time at this point in the release cycle. And even if I'd try to do the change now, the release managers of openSUSE probably won't accept it at this point, because the risk is too high to break things elsewhere.
so once more again: vnc subsystem in opensuse is *obsolete* until we will use tightvnc 1.3* ..
We *are* using tightvnc 1.3.9 since 2007 and there is no point in upgrading to the recently released 1.3.10 version, because the Unix code is identical to 1.3.9, only the Windows part was changed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.