Bug 2211941

Summary:

Please update Argos to latest from GitHub

Product:

[Fedora] Fedora

Reporter:

Alex Corcoles <alexcorcoles>

Component:

gnome-shell-extension-argos

Assignee:

Michel Alexandre Salim <michel>

Status:

CLOSED ERRATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

CC:

abuse, agerstmayr, alexcorcoles, evergara444, fgarciad, michel

Target Milestone:

---

Keywords:

Desktop, Regression, Upgrades

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

gnome-shell-extension-argos-3^20230404gite2d68ea-1.fc38

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2023-07-07 01:28:59 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Patch to update the package	none

Description Alex Corcoles 2023-06-02 16:43:11 UTC

Hi,

The RPM doesn't seem to work. If I install the latest source from GitHub (commit e2d68), the first example on their README works.

Cheers,

Álex

Reproducible: Always

Steps to Reproduce:
1. Install the package gnome-shell-extension-argos
2. Log off and log in
3. Open the extensions app
Actual Results:  
You get "this extension is incompatible with the current GNOME version".

Expected Results:  
Working extension.

Comment 1 Alex Corcoles 2023-06-02 17:12:40 UTC

Created attachment 1968627 [details]
Patch to update the package

After building the Fedora source with this patch, it works.

Comment 2 Fedora Update System 2023-07-06 15:03:43 UTC

FEDORA-2023-f9ac7e719a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f9ac7e719a

Comment 3 Fedora Update System 2023-07-07 01:28:59 UTC

FEDORA-2023-f9ac7e719a has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.