Bug 1832098

Summary: Due to socket path changes ibus not working in Wayland for qt4 apps
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: ibus-qtAssignee: fujiwara <tfujiwar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 34CC: i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ibus-qt-1.3.3-30.fc34 ibus-qt-1.3.3-30.fc33 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-27 00:31:10 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:

Description Jens Petersen 2020-05-06 05:24:20 UTC
Description of problem:
Due to changes in socket path for Wayland,
ibus input does not work for qt4 apps under Wayland in Fedora 32.

https://github.com/ibus/ibus-qt/pull/5

Version-Release number of selected component (if applicable):
ibus-qt-1.3.3-22.fc31

How reproducible:
100%

Comment 1 Fedora Program Management 2021-04-29 17:15:05 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 fujiwara 2021-05-11 07:18:12 UTC
Sorry, I forgot to fix this.
We still have a little time before EOL.

Comment 3 Jens Petersen 2021-05-17 05:56:21 UTC
Is F33 okay?

Comment 4 Fedora Update System 2021-05-18 08:47:38 UTC
FEDORA-2021-86893ea231 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-86893ea231

Comment 5 Fedora Update System 2021-05-19 02:20:10 UTC
FEDORA-2021-86893ea231 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-86893ea231`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-86893ea231

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-05-19 02:29:28 UTC
FEDORA-2021-426c2064fa has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-426c2064fa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-426c2064fa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2021-05-27 00:31:10 UTC
FEDORA-2021-86893ea231 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2021-05-27 01:04:34 UTC
FEDORA-2021-426c2064fa has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.