Bug 985057 - tigervnc server module broken yet again
tigervnc server module broken yet again
Product: Fedora
Classification: Fedora
Component: tigervnc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tim Waugh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-07-16 12:48 EDT by Jonathan Kamens
Modified: 2013-07-17 08:11 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-17 08:11:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jonathan Kamens 2013-07-16 12:48:08 EDT
[    57.836] (EE) Failed to load /usr/lib64/xorg/modules/extensions/libvnc.so: /usr/lib64/xorg/modules/extensions/libvnc.so: undefined symbol: key_is_down

I've lost count of how many times this module has been broken by updates.

When combined with bug 848943, which was filed almost a year ago but still has not been fixed, the two bugs together frequently render my system inaccessible remotely at exactly the times when I can't do anything about it, i.e., when I'm away from my desktop which is exactly why I need to access it remotely.

Can't anything to be done to prevent X server updates from being pushed that break tigervnc, or tigervnc updates from being pushed that are incompatible with the currently available X server?
Comment 1 Tim Waugh 2013-07-17 05:21:13 EDT
You haven't included the n-v-r so I can't be sure, but I think you are looking at a test update which has been unpushed.

What does 'rpm -q tigervnc' say?
Comment 2 Jonathan Kamens 2013-07-17 08:11:05 EDT
It appears you are correct: yum distro-sync solved the problem.

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