Bug 985057 - tigervnc server module broken yet again
Summary: tigervnc server module broken yet again
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-16 16:48 UTC by Jonathan Kamens
Modified: 2013-07-17 12:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-17 12:11:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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