Bug 1726215

Summary: ibus does not work from my Toolbox container
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: debarshir, i18n-bugs, pwu, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-04 03:47:52 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 2019-07-02 10:51:18 UTC
Description of problem:
Current IMEs do not work for apps run from a Toolbox container.

How reproducible:
100%

Steps to Reproduce:
1.
$ sudo dnf install toolbox
$ toolbox create
$ toolbox enter
⬢$ sudo dnf install gedit
⬢$ gedit
2. try to use ibus in gedit running from container

Actual results:
IME can't be used (though Gnome Shell Input Source shows selected IME)

Expected results:
ibus should work

Additional info:
Maybe needs some dbus help.

Comment 1 Jens Petersen 2019-07-02 15:11:18 UTC
A workaround for now is:

⬢$ IME=kkc
⬢$ sudo dnf install ibus-$IME
⬢$ ibus-daemon -d
⬢$ ibus engine $IME
⬢$ gedit

But that is not really acceptable of course.

Comment 2 Peng Wu 2019-07-03 08:41:21 UTC
I tried toolbox with Fedora 30 image, on Fedora 30 workstation,
gedit works fine with ibus.

I dunno whether this is related with Fedora Silverblue.

Comment 3 Jens Petersen 2019-07-03 08:53:59 UTC
Yes, so seems this is a Silverblue specific issue.

(Similarly under Silverblue, PackageKit-command-not-found doesn't work but it does in Workstation.)

Comment 4 Jens Petersen 2019-07-03 11:18:13 UTC
Well then on from a fresh updated SB30 install - I can't reproduce either.
So in fact this seems to be local issue with my toolbox/use environment presumably.
I am not sure how to track it down though

Comment 5 Jens Petersen 2019-09-04 03:47:52 UTC
Closing this out since I can't reproduce anymore