Bug 251944 - net/x11vnc fails to listen to ipv4 since upgrade of libvncserver
Summary: net/x11vnc fails to listen to ipv4 since upgrade of libvncserver
Status: Closed DUPLICATE of bug 251837
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Dirk Meyer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-18 19:16 UTC by Emrion
Modified: 2020-12-19 14:28 UTC (History)
2 users (show)

See Also:
linimon: maintainer-feedback? (dinoex)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emrion 2020-12-18 19:16:11 UTC 
My system is: 12.1-RELEASE-p12

I've just upgraded all the packages (via pkg) and since, x11vnc can't listen in ipv4 mode.

-----
$ x11vnc -display :0 -no6 -passwdfile /home/myuser/mypasswdfile
(...)

18/12/2020 20:06:46 Error: could not obtain listening port.
18/12/2020 20:06:46 If this system is IPv6-only, use the -6 option.6 option.
-----

It's the same error for root. x11vnc can listen in ipv6, but my private network is ipv4 only.

I suspect the upgrade of libvncserver as x11vnc relies on it.
Comment 1 Emrion 2020-12-19 12:06:57 UTC 
After investigations, it appears that, despite my "pkg upgrade" command, both libvncserver and x11vnc weren't at the latest version (unless someone has corrected the problem during the European night).

libvncserver-0.9.13 and x11vnc-0.9.16_1 generate the problem I mentioned.
libvncserver-0.9.13_1 and x11vnc-0.9.16_2 work perfectly.

This bug has to be closed.
Comment 2 Emrion 2020-12-19 14:23:47 UTC 
This is a duplicate of bug #51837

*** This bug has been marked as a duplicate of bug 51837 ***
Comment 3 Emrion 2020-12-19 14:27:38 UTC 

*** This bug has been marked as a duplicate of bug 251837 ***
Comment 4 Emrion 2020-12-19 14:28:36 UTC 
(In reply to Emrion from comment #2)
Sorry, wrong PR number.