Comment 22 for bug 1613027

There have been some developments with this problem so I thought I should
post the latest news.

Firstly, I have reported the problem as directed above to the people concerned
and the netdev team twice, but there has been no response.

Secondly, I managed to narrow down the cause of the problem in the codeline
only to then discover that its a known issue. A suggested patch to fix
the problem was rejected with the expectation that applications would
have to be changed to handle the new kernel network code.

Further details may be viewed here:- https://patchwork.ozlabs.org/patch/618164/

<begin rant> No doubt the sentiments expressed in the post are valid, but they
seem rather inflexible and harsh to me given that the failing applications were
working. Ultimately if an application is not changed, users will be stuck. In
my case its no network scanner. Seems crazy to me when a simple change will
resolve the problem. <end rant>

The application in point here (bug 1613027) is the Epson network plugin.

Unfortunately Epson or the authoring 3rd party do not publish the source code
and my efforts through Epson support to try to raise the issue or trace the
origin of the network plugin have been fruitless.

So for anyone experiencing the problem here, and it looks like there is at least
one, what to do...

1. Do nothing and only have a usb scanner.
2. Download the Linux kernel source code every time there is a new release
    and apply the suggested patch yourself.
3. Override the system 'listen' function with 'dlsym' whenever the
    network plugin is invoked. This is what I have done.
    To this end I have created a repository on my
    git home page here:- https://github.com/mr-headwind/ListenOverride
    This should only be viewed as a temporary workaround, but given the
    circumstances I suspect it may be permanent.

Regards.
Tony