SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Over the years I grew quite fond of it, you could always rely on it to do it's job.
For 14.1 there's a slackbuild that works fine, but I'm wondering if anything changed in X.org and whatnot that breaks compatibility with the, old by now, TightVNC 1.3.10.
It's available on SBo's master branch (which is prepping for a 14.2 release). Not sure if it works, but I know all but a few programs are building on -current, so it is likely this is working too.
I was able to build tightvnc this morning on Current + Multilib from the SBo files.
I've not tested it but I do see that tightvnc version 1.x.x is more-or-less 'abandonware' ( 1.3.10 has not been updated since 2006 according to https://en.wikipedia.org/wiki/TigerVNC )
I don't use VNC much any more now but as Eric said, TigerVNC is already available in the Current extra/ Directory.
You're not OK with tigervnc in Slackware's /extra section? TigerVNC is the successor of tightvnc.
I'm aware of TigerVNC, but when I tried it I found it terrible. It's a matter of catastrophic first impression that keeps you away from something for good. Can't remember what exactly bothered me so much, but I'm guessing that I began the evaluation thinking it is a drop-in replacement for TightVNC (à la MariaDB).
It's available on SBo's master branch (which is prepping for a 14.2 release). Not sure if it works, but I know all but a few programs are building on -current, so it is likely this is working too.
I'm aware of TigerVNC, but when I tried it I found it terrible. It's a matter of catastrophic first impression that keeps you away from something for good. Can't remember what exactly bothered me so much, but I'm guessing that I began the evaluation thinking it is a drop-in replacement for TightVNC (à la MariaDB).
FWIW, in the last two years I've used the tigervnc package from Eric Hameleers repository, which works very nicely (thanks, Mr Hameleers )
TigerVNC was a bit unusable in the time after their switch to FLTK as the graphical toolkit. But all the bugs and quirks have been ironed out and it is currently a well-behaving and well-performing VNC server and client. It will be part of Slackware 14.2 (it's in slackware-current).
I wonder what you mean by "I found it terrible" if it is just a remote viewer app... and it IS a drop-in replacement for TightVNC. You should try it again.
I'm using extra/tigervnc-1.6.0 from -current (14.2RC) to "phone home" while traveling for work. Other that RTFM, its easy to set up, other than a bit of a glitch with my dynamic DNS service, port forwarding, and security. Performance is ok from various hotels (as good as their crappy internet allows...). Access is seamless either from linux or my work Win7 laptop. Heck, if I can get it to work...anyone can.
The only issues I have are:
TigerVNC used KDE by default, instead of current user desktop (XFCE). Easy enough fix in ~/.vnc
TigerVNC kills pulseaudio server when shut down. I've posted a query about this on another thread.
For anyone with HiDPI vncserver -> StdDPI vncviewer issues under xfce4.
I missed the /extra/tigervnc note and did not install fltk.
When opening vncviewer on a StdDPI system, everything worked functionally but with very large {icons, fonts, window trim, panels, notifications, et al}.
After fltk was installed on the HiDPI server, scaling worked flawlessly even with a pre-fltk, 1.5.0 viewer on 14.1.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.