Bug 1310063 - imsettings-switch runs ibus-daemon on GNOME in Fedora 24
Summary: imsettings-switch runs ibus-daemon on GNOME in Fedora 24
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: imsettings
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 11:07 UTC by fujiwara
Modified: 2016-02-23 02:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-23 02:11:50 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
.cache/imsettings/log (1.84 KB, text/plain)
2016-02-19 11:07 UTC, fujiwara 		no flags Details
View All

Description fujiwara 2016-02-19 11:07:09 UTC 
Created attachment 1128514 [details]
.cache/imsettings/log

When I check ibus-daemon's process on GNOME in Fedora 24, it always runs with the owned panel.

% ps -ef | grep ibus-daemon
fujiwara  7967  4964  0 19:38 ?        00:00:00 /usr/bin/ibus-daemon -r --xim

I expect 'ibus-daemon --panel disable' is running on GNOME.
gnome-shell runs ibus-daemon correctly but it seems imsettings-switch restart ibus-daemon.

GNOME environment variables are set on gnome-shell:

% env | grep -i gnome
DESKTOP_SESSION=gnome-xorg
GDMSESSION=gnome-xorg
XDG_SESSION_DESKTOP=gnome-xorg
XDG_CURRENT_DESKTOP=GNOME

So when I run imsettings-target-checker.sh by manual, it returns 0 correctly.

But if I run 'imsettings-switch -n -q -x', imsettings-target-checker.sh returns 1 because it cannot get the enviroment variables of GDMSESSION and DESKTOP_SESSION.

BTW, I'd recomment XDG_CURRENT_DESKTOP instead of DESKTOP_SESSION.

I attached .cache/imsettings/log too.
Comment 1 fujiwara 2016-02-19 11:08:33 UTC 
This problem happens in both GNOME Xorg and GNOME Wayland in Fedora 24.
Comment 2 Akira TAGOH 2016-02-23 02:11:50 UTC 
Fixed in imsettings-1.7.0-1.fc24.
Note You need to log in before you can comment on or make changes to this bug.