GNU bug report logs - #22707
IBus relies on possibly outdated ~/.cache/ibus/bus/registry

Previous Next

To reply to this bug, email your comments to 22707 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: bug-guix <at> gnu.org
Subject: IBus relies on possibly outdated ~/.cache/ibus/bus/registry
Date: Tue, 16 Feb 2016 20:36:47 +0100

I have an annoying little problem with IBus.  IBus creates a binary
registry in ~/.cache/ibus/bus on first start(?) which contains the full
paths to store items such as

    /gnu/store/k3r...-ibus-1.5.11/libexec/ibus-dconf

The problem is that when updating the “ibus” package this registry is
invalid, but never invalidated or regenerated.  IBus will continue to
use the paths in the registry — even after they have disappeared after
“guix gc”.  This results in an unhelpful error when starting
“ibus-setup”:

    Can not execute default config program

This is because it tries to run “$oldstoreitem/libexec/ibus-dconf”,
which has been removed by garbage collection.

The “.cache” directory is not part of the profile, of course, so we
cannot automatically rebuild it.  Looking at the code it seems that IBus
first looks for a system registry, but this registry cannot be right as
the user may have installed additional IBus input methods and the system
registry (wherever that may be) is not writeable.

Should we prevent a registry in the “.cache” directory to be used and
try to make IBus look for a registry that could be generated as part of
generating a new profile generation?

~~ Ricardo

Message #8 received at 22707 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 22707 <at> debbugs.gnu.org
Subject: Re: bug#22707: IBus relies on possibly outdated
 ~/.cache/ibus/bus/registry
Date: Wed, 24 Feb 2016 22:36:17 +0100

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> I have an annoying little problem with IBus.  IBus creates a binary
> registry in ~/.cache/ibus/bus on first start(?) which contains the full
> paths to store items such as
>
>     /gnu/store/k3r...-ibus-1.5.11/libexec/ibus-dconf

GIMP has a similar problem for files in ~/.gimp-2.8, though it seems to
automatically regenerate them or something.

> Should we prevent a registry in the “.cache” directory to be used and
> try to make IBus look for a registry that could be generated as part of
> generating a new profile generation?

Either that or we change the IBus code to detect stale caches and get
rid of them.  This might even be acceptable upstream.  WDYT?

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.