From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#22707: IBus relies on possibly outdated ~/.cache/ibus/bus/registry Date: Tue, 16 Feb 2016 20:36:47 +0100 Message-ID: <87bn7g5tww.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39033) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVlRl-0002YN-E3 for bug-guix@gnu.org; Tue, 16 Feb 2016 14:38:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVlRi-0008Kg-63 for bug-guix@gnu.org; Tue, 16 Feb 2016 14:38:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:39734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVlRi-0008Kc-30 for bug-guix@gnu.org; Tue, 16 Feb 2016 14:38:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aVlRh-0001Xd-Uq for bug-guix@gnu.org; Tue, 16 Feb 2016 14:38:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38455) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVlQg-0002Mt-4L for bug-guix@gnu.org; Tue, 16 Feb 2016 14:36:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVlQc-00085M-Rs for bug-guix@gnu.org; Tue, 16 Feb 2016 14:36:58 -0500 Received: from sender163-mail.zoho.com ([74.201.84.163]:25385) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVlQc-00085A-Jr for bug-guix@gnu.org; Tue, 16 Feb 2016 14:36:54 -0500 List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: 22707@debbugs.gnu.org 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