Bug 1031244 - x11vnc failed to work after recent updates [NEEDINFO]
Summary: x11vnc failed to work after recent updates
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: x11vnc
Version: el6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-16 04:18 UTC by Cecil Yen
Modified: 2020-11-30 15:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:05:48 UTC
Type: Bug
Embargoed:
pahan: needinfo?


Attachments (Terms of Use)

Description Cecil Yen 2013-11-16 04:18:43 UTC
Description of problem:
x11vnc would disconnect the client after random period of time

Version-Release number of selected component (if applicable):
x11vnc 0.9.13-8.el6.x86_64.rpm

How reproducible:
Connect the remote CentOS 6 machine via ssh and tunnel the x11vnc to localhost. VNC client would be disconnected after tens of seconds. Tried three clients on Mac, all the same. SSH and tunneling worked just fine.

Additional info:
It worked well until the most recent update. Maybe the latest Xorg update broke the compatibility.

Comment 1 Pavel Alexeev 2013-11-16 19:51:50 UTC
Please attach logs and some errors what you see.
There was not x11vnc updates long time.

Comment 2 Pavel Alexeev 2013-11-16 19:52:01 UTC
Please attach logs and some errors what you see.
There was not x11vnc updates long time.

Comment 3 Cecil Yen 2013-11-17 17:45:53 UTC
There is nothing extraordinary in stdout of x11vnc, message, or .xsession-errors. x11vnc just said the client was disconnected and the client was disconnected for no reason. It happened randomly; sometimes the session last few second or tens of seconds. I am sure ssh connection was good since regular VNC server worked fine.  Actually, x11vnc worked just fine before a system update of some Xorg packages and few other components like kernel and Nvidia driver.

Comment 4 Pavel Alexeev 2013-11-22 08:44:51 UTC
Really I have no idea how to debug it without any info. Could you please run x11vnc with -verbose key and then look at relevant messages at failure?

Comment 5 Fedora Admin XMLRPC Client 2020-04-06 19:34:31 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 6 Ben Cotton 2020-11-05 16:46:08 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 7 Ben Cotton 2020-11-30 15:05:48 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.