Bug 985057

Summary:	tigervnc server module broken yet again
Product:	[Fedora] Fedora	Reporter:	Jonathan Kamens <jik>
Component:	tigervnc	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bphinz, jik, twaugh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-17 12:11:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonathan Kamens 2013-07-16 16:48:08 UTC

[    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 09:21:13 UTC

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 12:11:05 UTC

It appears you are correct: yum distro-sync solved the problem.