Red Hat Bugzilla – Bug 514157
imsettings and ibus-gtk installed when @input-methods deselected
Last modified: 2010-08-09 16:29:55 EDT
I can test on rawhide later but it seems ibus and imsettings get
installed with F11 when one customizes and unchecks @input-methods.
This is somewhat strange: wondered if some multilib related code is
pulling in ibus-gtk or something like that?
+++ This bug was initially created as a clone of Bug #513782 +++
\"I just noticed this problem today : imsettings package is not in the Input Method group, resulting in it being installed even when input methods group is unselected during install in anaconda... thus, imsettings-start is launched when opening a new gnome session, but is useless.\"
--- Additional comment from firstname.lastname@example.org on 2009-07-27 03:33:01 EDT ---
I did a test install of F11 with @input-methods unchecked
and ibus, ibus-gtk and hence im-chooser and imsettings got
--- Additional comment from email@example.com on 2009-07-27 03:36:48 EDT ---
Created an attachment (id=355237)
default English F11 i386 install log just with Input Methods unchecked
--- Additional comment from firstname.lastname@example.org on 2009-07-27 03:53:36 EDT ---
... and nothing seems to require them.
--- Additional comment from email@example.com on 2009-07-27 04:58:27 EDT ---
Created an attachment (id=355249)
Once rawhide's working again, can you please try a rawhide install and attach /tmp/yum.log to this bug report? We should now have much better debugging capabilities for these sorts of issues (like seeing what packages are getting pulled in as requirements of others).
Since @input-methods are turned on by default, those packages were added to the package list once. I guess anaconda may re-evaluate the package list every time when modifying groups on the package custom selection. those is/was NOT in comps - imsettings and im-chooser has been added - so when @input-methods is turned off, it may be just kept there because anaconda doesn't have any kind of information what packages was added by turning on the group but relying on the group information in comps what kind of packages is included in?
Is it likely scenario?
Given that it's the case, adding all of packages to comps to get yum-groupremove working sounds not realistic to me. I hope it will be improved.
Hmm I just reproduced with F12-Beta x86_64...
*** Bug 544884 has been marked as a duplicate of this bug. ***
Hi all ! You can find extra info on the above-cited bug report. I was not aware that another bug was filed... sorry
I confirm no success with F12 Gold x86_64 DVD
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here:
Can anyone attach the information requested in comment #1?
Created attachment 406427 [details]
You mean anaconda.yum.log?
I got this with installing f13 beta without @input-methods on English locale.