[opensuse-m17n] ibus in openSUSE 13.2: many ibus input engines can not save setting changes
Hi all: I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason. I need help, thanks. Hillwood Yang -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
Hi Hillwood, I guess configuration server (dconf) is not working correctly. Can you confirm that settings of IBus itself are saved? Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like: [general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10' [engine/anthy/common] input-mode=3 If "dconf dump" does not work, please run: $ sudo dconf update This command should be run at installation time by the post script of ibus package, but there might be some problems with that script. Fuminobu Takeyama On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
Now I can reproduce this problem. "dconf update" don't help to fix this. I noticed that there is no dconf scheme in /etc/dconf. Why? It is listed in its files list as %ghost but not copied by "make install" Fuminobu Takeyama On 2015/03/26 23:33, Fuminobu TAKEYAMA wrote:
Hi Hillwood,
I guess configuration server (dconf) is not working correctly.
Can you confirm that settings of IBus itself are saved?
Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like:
[general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10'
[engine/anthy/common] input-mode=3
If "dconf dump" does not work, please run: $ sudo dconf update
This command should be run at installation time by the post script of ibus package, but there might be some problems with that script.
Fuminobu Takeyama
On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
At Fri, 27 Mar 2015 00:48:45 +0900, Fuminobu TAKEYAMA wrote:
Now I can reproduce this problem. "dconf update" don't help to fix this.
I noticed that there is no dconf scheme in /etc/dconf. Why?
It is listed in its files list as %ghost but not copied by "make install"
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files. Why %ghost is used at all? For clearing %config attribute? Takashi
Fuminobu Takeyama
On 2015/03/26 23:33, Fuminobu TAKEYAMA wrote:
Hi Hillwood,
I guess configuration server (dconf) is not working correctly.
Can you confirm that settings of IBus itself are saved?
Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like:
[general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10'
[engine/anthy/common] input-mode=3
If "dconf dump" does not work, please run: $ sudo dconf update
This command should be run at installation time by the post script of ibus package, but there might be some problems with that script.
Fuminobu Takeyama
On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong. From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot} What is the best way? # it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus # we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus # or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
Hillwood Can you file a bug report?
Fuminobu TAKEYAMA On 2015/03/27 1:16, Takashi Iwai wrote:
At Fri, 27 Mar 2015 00:48:45 +0900, Fuminobu TAKEYAMA wrote:
Now I can reproduce this problem. "dconf update" don't help to fix this.
I noticed that there is no dconf scheme in /etc/dconf. Why?
It is listed in its files list as %ghost but not copied by "make install"
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
Takashi
Fuminobu Takeyama
On 2015/03/26 23:33, Fuminobu TAKEYAMA wrote:
Hi Hillwood,
I guess configuration server (dconf) is not working correctly.
Can you confirm that settings of IBus itself are saved?
Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like:
[general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10'
[engine/anthy/common] input-mode=3
If "dconf dump" does not work, please run: $ sudo dconf update
This command should be run at installation time by the post script of ibus package, but there might be some problems with that script.
Fuminobu Takeyama
On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
At Fri, 27 Mar 2015 02:20:11 +0900, Fuminobu TAKEYAMA wrote:
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong.
From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot}
What is the best way?
# it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus
Also remove %config from %{_sysconfdir}/dconf/db/ibus.d, too. Just keep it simple. What kind of warning do you get?
# we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus
This would break the update.
# or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
I guess this is bogus, too. Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
What kind of warning do you get? That is just "non-conffile-in-etc"
Also remove %config from %{_sysconfdir}/dconf/db/ibus.d, too. Just keep it simple. done
Then, %{_sysconfdir}/dconf/db/ibus is a file that 'dconf update' generates at %post, and "make install" does not install it. Isn't it the right case to use %ghost? The spec file from Fedora does not list %{_sysconfdir}/dconf/db/ibus in %files and removes it by %postun. The following package works fine to me. I tested by removing ibus once and then installing it again: https://build.opensuse.org/package/rdiff/home:ftake:branches:M17N/ibus?opackage=ibus&oproject=M17N&rev=6
Hillwood Thanks for your report.
Fuminobu Takeyama On 2015年03月27日 02:25, Takashi Iwai wrote:
At Fri, 27 Mar 2015 02:20:11 +0900, Fuminobu TAKEYAMA wrote:
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong.
From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot}
What is the best way?
# it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus
Also remove %config from %{_sysconfdir}/dconf/db/ibus.d, too. Just keep it simple.
What kind of warning do you get?
# we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus
This would break the update.
# or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
I guess this is bogus, too.
Takashi
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
At Sat, 28 Mar 2015 02:04:30 +0900, Fuminobu TAKEYAMA wrote:
What kind of warning do you get? That is just "non-conffile-in-etc"
Also remove %config from %{_sysconfdir}/dconf/db/ibus.d, too. Just keep it simple. done
Then, %{_sysconfdir}/dconf/db/ibus is a file that 'dconf update' generates at %post, and "make install" does not install it.
Isn't it the right case to use %ghost?
Yes, this is the case where %ghost works well. You need to create (touch) it in spec during build. But the dummy file won't be installed, just removed.
The spec file from Fedora does not list %{_sysconfdir}/dconf/db/ibus in %files and removes it by %postun.
It works, too, but %ghost is cleaner, IMO.
The following package works fine to me. I tested by removing ibus once and then installing it again: https://build.opensuse.org/package/rdiff/home:ftake:branches:M17N/ibus?opackage=ibus&oproject=M17N&rev=6
Great, thanks! Takashi
Hillwood Thanks for your report.
Fuminobu Takeyama
On 2015年03月27日 02:25, Takashi Iwai wrote:
At Fri, 27 Mar 2015 02:20:11 +0900, Fuminobu TAKEYAMA wrote:
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong.
From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot}
What is the best way?
# it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus
Also remove %config from %{_sysconfdir}/dconf/db/ibus.d, too. Just keep it simple.
What kind of warning do you get?
# we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus
This would break the update.
# or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
I guess this is bogus, too.
Takashi
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
在 2015-03-27五的 02:20 +0900，Fuminobu TAKEYAMA写道：
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong.
From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot}
What is the best way?
# it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus
# we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus # or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
Hillwood Can you file a bug report?
OK, I will report this bug. Thanks for your work! Hillwood Yang
Fuminobu TAKEYAMA
On 2015/03/27 1:16, Takashi Iwai wrote:
At Fri, 27 Mar 2015 00:48:45 +0900, Fuminobu TAKEYAMA wrote:
Now I can reproduce this problem. "dconf update" don't help to fix this.
I noticed that there is no dconf scheme in /etc/dconf. Why?
It is listed in its files list as %ghost but not copied by "make install"
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
Takashi
Fuminobu Takeyama
On 2015/03/26 23:33, Fuminobu TAKEYAMA wrote:
Hi Hillwood,
I guess configuration server (dconf) is not working correctly.
Can you confirm that settings of IBus itself are saved?
Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like:
[general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10'
[engine/anthy/common] input-mode=3
If "dconf dump" does not work, please run: $ sudo dconf update
This command should be run at installation time by the post script of ibus package, but there might be some problems with that script.
Fuminobu Takeyama
On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
在 2015-03-27五的 02:20 +0900，Fuminobu TAKEYAMA写道：
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
I expected that the %ghost file is just removed by package removal. I was wrong.
From 13.2, it seems that %ghost files are not copied into rpms anymore even though the files exist in %{buildroot}
What is the best way?
# it looks ok to make these files normal ones (but warnings) %{_sysconfdir}/dconf/db/ibus.d/00-upstream-settings %{_sysconfdir}/dconf/profile/ibus
# we do not manage this by rpm? %postun rm -f %{_sysconfdir}/dconf/db/ibus # or keep this ghost? %ghost %{_sysconfdir}/dconf/db/ibus
Hillwood Can you file a bug report?
https://bugzilla.opensuse.org/show_bug.cgi?id=924696
Fuminobu TAKEYAMA
On 2015/03/27 1:16, Takashi Iwai wrote:
At Fri, 27 Mar 2015 00:48:45 +0900, Fuminobu TAKEYAMA wrote:
Now I can reproduce this problem. "dconf update" don't help to fix this.
I noticed that there is no dconf scheme in /etc/dconf. Why?
It is listed in its files list as %ghost but not copied by "make install"
It's exactly the purpose of %ghost: the files should be removed by package removal but the package itself doesn't contain the files.
Why %ghost is used at all? For clearing %config attribute?
Takashi
Fuminobu Takeyama
On 2015/03/26 23:33, Fuminobu TAKEYAMA wrote:
Hi Hillwood,
I guess configuration server (dconf) is not working correctly.
Can you confirm that settings of IBus itself are saved?
Please try the following command: $ dconf dump /desktop/ibus/ It should print saved settings like:
[general] engines-order=['anthy', 'mozc-jp', 'skk', 'kkc', 'xkb:jp::jpn'] preload-engines=['anthy', 'mozc-jp', 'kkc', 'skk', 'xkb:jp::jpn'] version='1.5.10'
[engine/anthy/common] input-mode=3
If "dconf dump" does not work, please run: $ sudo dconf update
This command should be run at installation time by the post script of ibus package, but there might be some problems with that script.
Fuminobu Takeyama
On 2015/03/26 15:33, Hillwood Yang wrote:
Hi all:
I find a serious problem in openSUSE 13.2. If the system is new installation, many ibus input engines can not save setting changes, include ibus-pinyin, ibus-sunpinyin, ibus-libpinyin and ibus-anthy. If the system upgrade form 13.1, all ibus input engines work fine. I can't find the reason.
I need help, thanks.
Hillwood Yang
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org
participants (4)
-
Fuminobu TAKEYAMA -
hillwood -
Hillwood Yang
-
Takashi Iwai