Bug 2035023 - workrave gnome applet extension incompatible due to old workrave version
Summary: workrave gnome applet extension incompatible due to old workrave version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: workrave
Version: 35
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Lukas Zapletal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-22 18:15 UTC by Erik M Jacobs
Modified: 2022-01-18 01:55 UTC (History)
4 users (show)

Fixed In Version: workrave-1.10.49-1.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-18 01:55:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Erik M Jacobs 2021-12-22 18:15:57 UTC 
Description of problem:
The workrave applet extension reports that it is incompatible.

Version-Release number of selected component (if applicable):
workrave-1.10.45-2.fc35.x86_64

Note that 1.10.48 is the current version and includes a fix for this issue:
https://github.com/rcaelers/workrave/issues/370
Comment 1 Fedora Update System 2022-01-09 14:05:56 UTC 
FEDORA-2022-8ac5c5c5d5 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ac5c5c5d5
Comment 2 Fedora Update System 2022-01-10 01:46:34 UTC 
FEDORA-2022-8ac5c5c5d5 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8ac5c5c5d5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8ac5c5c5d5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2022-01-18 01:55:26 UTC 
FEDORA-2022-8ac5c5c5d5 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.