Bug 498141
Summary: | new ibus install needs gtk immodules | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jens Petersen <petersen> |
Component: | ibus | Assignee: | Peng Huang <phuang> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | i18n-bugs, K9, mclasen, phuang, tagoh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.1.0.20090423-2.fc11 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-09 03:59:49 UTC | Type: | --- |
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
2009-04-29 04:17:25 UTC
Just confirmed this worked ok in F10 if I remove scim-bridge-gtk for example. Just confirmed this bug is reproducible in rawhide that updated on 29 Apr 09. Have you installed gtk2-immodules package btw? Could we please move im-xim.so back into the main gtk2 package? Or failing that at least have a separate subpackage for it so that ibus can require it? What do you expect ? You remove the ibus immodule, so of course ibus won't work in gtk applications anymore. How about you don't package the ibus immodule separately instead. Then that scenario (ibus, but not gtk immodule) won't happen either... Split it off into gtk2-immodule-xim (In reply to comment #5) > What do you expect? You remove the ibus immodule, so of course ibus won't work > in gtk applications anymore. It is more the other way round maybe I didn't install it :) (think people upgrading from f10 and doing "yum install ibus-anthy" - ping! totally non-working ibus). > How about you don't package the ibus immodule > separately instead. Then that scenario (ibus, but not gtk immodule) won't > happen either... Valid point, since ibus GUI requires gtk2 the idea does make some sense. However what about multilib in that case though? Our overall package management system is not so good at handling multilib unfortunately. Moving this to ibus to consider this suggestion. (In reply to comment #6) > Split it off into gtk2-immodule-xim Thanks! Huang Peng, can you please make ibus require gtk2-immodule-xim also. (In reply to comment #7) > Valid point, since ibus GUI requires gtk2 the idea does make some sense. > > However what about multilib in that case though? > Our overall package management system is not so good at handling multilib > unfortunately. > > Huang Peng, can you please make ibus require gtk2-immodule-xim also. Or is it better just to make ibus require ibus-gtk? That avoids the multilib problem and actually means we don't need xim for gtk ibus. (In reply to comment #8) > Or is it better just to make ibus require ibus-gtk? > > That avoids the multilib problem and actually means we don't need xim for gtk > ibus. How to deal KDE users? Maybe they don't like dependences on gtk. Later, maybe ibus-qt will be ready. Should we add ibus require ibus-qt also? (In reply to comment #9) > How to deal KDE users? Maybe they don't like dependences on gtk. Later, maybe > ibus-qt will be ready. Should we add ibus require ibus-qt also? Doesn't ibus require gtk currently anyway? Currently, ibus panel requires gtk. But ideally we should develop another panel on qt for KDE desktop. For this bug, I suggest we just make sure the default installation or upgrading will include ibus-gtk. We need not consider users remove the im module by self. Jens, Can we let anaconda install ibus-gtk during the upgrading? (In reply to comment #11) > Currently, ibus panel requires gtk. But ideally we should develop another panel > on qt for KDE desktop. I know but as long as the main ibus packages depend on gtk2 I don't so a problem with pulling ibus-gtk too. When the gtk code is > For this bug, I suggest we just make sure the default installation or upgrading > will include ibus-gtk. We need not consider users remove the im module by self. Problems is I don't know how to do that, unless they choose to install ibus at system upgrade time from anaconda. Otherwise I suggested ibus to require gtk2-immodules-xim but then easier to just require ibus-gtk I guess. :) > Jens, Can we let anaconda install ibus-gtk during the upgrading? We don't install ibus for upgrades in f11 by default, users will be upgraded to latest scim in f11 from f10. I meant:
> I know but as long as the main ibus packages depend on gtk2 I don't so a
> problem with pulling ibus-gtk too. When the gtk code is
as long as the main ibus packages depend on gtk2 I don't see a
problem with pulling in ibus-gtk too. If/when the gtk code is
separated we can drop that dependency from the main package at
the same time.
Actually, it just looks weird. Anyway, I added the require in ibus. I think we could close this bug now. ibus-1.1.0.20090423-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/ibus-1.1.0.20090423-2.fc11 ibus-1.1.0.20090423-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |