ibus still broken

[Bill Davidsen]

Craig White wrote:
> On Fri, 2009-10-02 at 16:51 -0600, Stuart McGraw wrote:
>> On 10/02/2009 03:08 PM, Bill Davidsen wrote:
>>>> yum downgrade ibus-libs
>>>> yum update
>>>>
>>>> Hope this helps
>>>>
>>> I believe that Stuart's problem is that once you break ibus it will never dig 
>>> its way out using only the 'upgrade' command, since something appears 
>>> half-updated. I did successful upgrades on a number of system after the problem, 
>>> but on the two systems which had an initial problem a simple upgrade fails. I 
>>> will try downgrading and see if that helps. One system will not do networking 
>>> since the upgrade failed, so I'm not sure what's up with that, it just broken.
>> I "rpm -e" all my ibus* and anthy packages, then reinstalled the
>> old versions from my f11 dvd repo.  I still have the same problem.
>> I also notice that the ibus desktop icon is still the "new" icon
>> (the one that appeared after I'd done the updates), not the icon
>> which was present after my original f11 install which I think
>> looked different.  So it seems that some unrevertible changes
>> have been made.  
> ----
> I'm just not buying Bill's concept of breaking and never digging out.
> 
That's your choice, I think Tait Clarridge hit the method to downgrade first, 
then rerun the upgrade. In another forum (chat room) someone said that the yum 
'clean' had been used, then upgrade succeeded in fixing the system.

Both of those suggestions indicate that "using only the 'upgrade' command" isn't 
the way to get things sane again. If it worked for you, fine, but I still put 
Tait's suggestion in my tricks folder, seems a robust thing to do, rather than 
repeating the unsuccessful upgrade.

> It's easy enough as user to '$ mv ~/.ibus ~/.ibus-bak' and restart ibus
> to create brand new settings (right click on ibus icon in system tray
> and choose 'Restart')
> 
> and if your did this 'rpm -e' WITHOUT resorting to anything radical such
> as '--nodeps' then if you create the new settings file as per above, it
> should be back to where it was when you first installed it.
> 
> Likewise, if you did not do anything like '--nodeps' you should be able
> to bring it up to date simply by doing 'yum update' and if that fails,
> you should show us the text of where/how it failed.
> 
> Craig
> 
> 


-- 
Bill Davidsen <davidsen at tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot