http://bugzilla.novell.com/show_bug.cgi?id=607055 http://bugzilla.novell.com/show_bug.cgi?id=607055#c Reinhard Max changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Severity|Normal |Minor -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=607055 http://bugzilla.novell.com/show_bug.cgi?id=607055#c2 --- Comment #2 from Reinhard Max 2010-05-19 15:13:12 CEST --- (In reply to comment #1)

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.

http://bugzilla.novell.com/show_bug.cgi?id=607055 http://bugzilla.novell.com/show_bug.cgi?id=607055#c3 --- Comment #3 from Daniel Pecka 2010-05-26 13:58:53 UTC --- btw. not working clipboard is pretty annoying ;) so just for to be sure that this bug won't be forgotten, i'm increasing severity .. regards, daniel -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=607055 http://bugzilla.novell.com/show_bug.cgi?id=607055#c5 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |X.Org Product|openSUSE 11.2 |openSUSE 11.3 --- Comment #5 from Stefan Dirsch 2010-08-14 16:09:44 UTC --- Moving to 11.3. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=607055 https://bugzilla.novell.com/show_bug.cgi?id=607055#c7 --- Comment #7 from Daniel Pecka 2010-11-19 08:07:03 UTC --- no, it is not .. it's a reasonable proposal. and don't tell me, taht we won't change in 11.4 tightvnc -> tigervnc .. regards -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=607055 https://bugzilla.novell.com/show_bug.cgi?id=607055#c9 Daniel Pecka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FEATURE | --- Comment #9 from Daniel Pecka 2010-11-19 12:22:57 UTC --- oh bloody hell guys: ad.resizing) don't know where did you get that, but tightvnc *DOESN'T have RANDR extension so at least here it can't resize. tigervnc has. ad.others) i listed in several bugreports several despicable ways of how tightvnc acts .. isn't just not working clipboard and ugly memory leak (consumptions) enough ?? i'm using actually Xvnc from fedora's tigertvnc package just simply by putting it like this into my $PATH:

ls -la /usr/bin/Xvnc* lrwxrwxrwx 1 root root 11 2010-09-02 20:12 /usr/bin/Xvnc -> Xvnc.fedora -rwxr-xr-x 1 root root 2332368 2010-08-26 13:55 /usr/bin/Xvnc.fedora -rwxr-xr-x 1 root root 1914288 2010-08-19 17:37 /usr/bin/Xvnc.suse

ldd `which Xvnc` linux-vdso.so.1 => (0x00007fffc9bff000) libz.so.1 => /lib64/libz.so.1 (0x00007fdefb399000) libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fdefafea000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fdefade6000) libXfont.so.1 => /usr/lib64/libXfont.so.1 (0x00007fdefaba8000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fdefa9a4000) libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fdefa742000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fdefa53c000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fdefa1fc000) librt.so.1 => /lib64/librt.so.1 (0x00007fdef9ff3000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fdef9ce9000) libm.so.6 => /lib64/libm.so.6 (0x00007fdef9a92000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fdef987c000) libc.so.6 => /lib64/libc.so.6 (0x00007fdef951c000) /lib64/ld-linux-x86-64.so.2 (0x00007fdefb5af000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fdef9293000) libfontenc.so.1 => /usr/lib64/libfontenc.so.1 (0x00007fdef908b000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fdef8e6e000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdef8c51000

ls -l /home/dpecka/bin/vncconfig lrwxrwxrwx 1 dpecka users 42 2010-08-26 15:56 /home/dpecka/bin/vncconfig -> /home/dpecka/chroot_test/usr/bin/vncconfig

IIRC i just installed with rpm (with -nodeps --root=/home/dpecka/chroot_test/ options) fedora's package, checked that newly linkded usr/bin/Xvnc with ldd and it was all .. there is NO real reason to keep tightvnc in distro. i'm using it on many hosts (xen, kvm, whichever else) and it just works pretty nice without *any additional customizing .. regartds, daniel ps. i reopened this bug because keeping tightvnc in distro just means, that we have not still working clipboard content -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=607055 https://bugzilla.novell.com/show_bug.cgi?id=607055#c11 --- Comment #11 from Reinhard Max 2010-11-19 17:31:27 CET --- Yes, thanks for the input. That's the kind of hands-on experience with TigerVNC I was after. Had you told us that earlier and in a different tone... But when I am shouted at in such a way, that definitely doesn't increase the chance that I could be bothered to actually do the work of switching over to yet another still young VNC fork, even if it includes a few features we currently don't have. So, yes, we will consider moving over, but no, it will not be top priority. And BTW, there are tigervnc packages somewhere in the build service that you can install if you don't like tightvnc as it is. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.