Bug 1936182

Summary: Ulauncher extensions crash with Gdk error
Product: [Fedora] Fedora Reporter: Sebastien Wains <swa>
Component: ulauncherAssignee: Artem <ego.cordatus>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: ego.cordatus, swa, troy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ulauncher-5.11.0-4.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-26 00:41:34 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:
Attachments:
Description Flags
extension crash error message none

Description Sebastien Wains 2021-03-07 12:50:15 UTC 
Created attachment 1761269 [details]
extension crash error message

Description of problem:


Version-Release number of selected component (if applicable):

Ulauncher 5.10.0 fedora build
Fedora 34 i3 spin

How reproducible:

Always

Steps to Reproduce:
1. start ulauncher
2. enable an extension (for example https://github.com/Ulauncher/ulauncher-emoji)
3. extension crashes

Actual results:

2021-03-07 13:31:28,097 | ERROR | ulauncher.api.server.ExtensionRunner: _run_process() | Extension "com.github.ulauncher.ulauncher-emoji" failed with an error: ImportError: Requiring namespace 'Gdk' version '3.0', but '4.0' is already loaded

Expected results:

No crash

Additional info:
Comment 1 Artem 2021-03-07 19:49:35 UTC 
Hello Sebastien. This sounds like should reported upstream. What do you think?
https://github.com/Ulauncher/Ulauncher/issues
Comment 2 Troy Curtis 2021-07-10 01:05:22 UTC 
So I submitted a PR upstream back in March, but it has been stalled since it seems the main author may have lost interest or is unavailable for some reason?  Another main contributor has started a fork to keep momentum going https://github.com/friday/Ulauncher-Revived but I wonder if we could maybe add a patch to the package until the upstream gets resolved? If that sounds like a reasonable approach I can prep the package patch and submit a PR in pagure.

Let me know!
Comment 3 Troy Curtis 2021-07-21 03:15:55 UTC 
Submitted PR in dist-git https://src.fedoraproject.org/rpms/ulauncher/pull-request/1
Comment 4 Fedora Update System 2021-07-21 07:52:09 UTC 
FEDORA-2021-04232c822c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-04232c822c
Comment 5 Fedora Update System 2021-07-22 01:10:25 UTC 
FEDORA-2021-04232c822c has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-04232c822c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-04232c822c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2021-07-23 01:13:23 UTC 
FEDORA-2021-4f1065115a has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4f1065115a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4f1065115a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2021-07-26 00:41:34 UTC 
FEDORA-2021-4f1065115a has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.