Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1413598 - (fltk-rebase) [REBASE] Update fltk to 1.3.4 for tigervnc
[REBASE] Update fltk to 1.3.4 for tigervnc
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: fltk (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jan Grulich
Desktop QE
: Rebase
Depends On:
Blocks: tigervnc-rebase 1393395
  Show dependency treegraph
 
Reported: 2017-01-16 08:25 EST by Jan Grulich
Modified: 2017-08-01 16:50 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 16:50:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2000 normal SHIPPED_LIVE Moderate: tigervnc and fltk security, bug fix, and enhancement update 2017-08-01 14:33:08 EDT

  None (edit)
Description Jan Grulich 2017-01-16 08:25:44 EST
Description of problem:
Tigervnc requires fltk in version 1.3.3, while we still ship some 1.3.x snapshot. To be sure we have everything what tigervnc needs I would like to update it to 1.3.4, which is the latest stable version of 1.3. It doesn't seem to be used by anything else besides tigervnc so it should be safe to update it and even if it would be heavily used, then updating to recent stable version is way better than having some random snapshot.
Comment 1 Jan Grulich 2017-01-16 08:26:53 EST
PS: I have no problem with doing the rebase myself altogether with tigervnc.
Comment 3 Jan Grulich 2017-02-22 03:55:53 EST
Fltk has been updated in RHEL 7.4 branch.
Comment 6 errata-xmlrpc 2017-08-01 16:50:05 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2000

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