From: Julien Lepiller <julien@lepiller.eu>
To: Mark H Weaver <mhw@netris.org>,47576@debbugs.gnu.org
Subject: bug#47576: [security] ibus-daemon launches ungrafted subprocesses
Date: Sat, 03 Apr 2021 07:29:00 -0400 [thread overview]
Message-ID: <8BEEF3C6-82DC-459A-9013-3850754DA3B2@lepiller.eu> (raw)
In-Reply-To: <874kgndds4.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Oh! That would explain why I had so much trouble fixing/updating ibus and ibus-anthy!
We should probably fix ibus so it regenerates its cache when it's a different process. It could be as simple as using a subdirectory computed from the absolute name of the ibus binary, maybe.
Le 3 avril 2021 03:31:44 GMT-04:00, Mark H Weaver <mhw@netris.org> a écrit :
>I wrote:
>> I still have no clue where the reference to that mysterious old
>version
>> (/gnu/store/a4r6q1fbfqapy5hrrxap1yg96rjgln6q-ibus-1.5.22) is coming
>> from.
>
>I found them:
>
> ~/.cache/ibus/bus/registry
> /var/lib/gdm/.cache/ibus/bus/registry
>
>On my system, those files include absolute pathnames to programs in
>/gnu/store/a4r6q1fbfqapy5hrrxap1yg96rjgln6q-ibus-1.5.22, which I
>compiled last December.
>
>That old store item has been kept safe from GC for only one reason:
>because 'ibus-daemon', along with its subprocesses, tend to be running
>whenever I run "guix gc", and "guix gc" protects store items that are
>currently in use by active processes.
>
> Mark
[-- Attachment #2: Type: text/html, Size: 1476 bytes --]
next prev parent reply other threads:[~2021-04-03 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 4:44 bug#47576: [security] ibus-daemon launches ungrafted subprocesses Mark H Weaver
2021-04-03 4:51 ` Mark H Weaver
2021-04-03 7:12 ` Mark H Weaver
2021-04-03 7:31 ` Mark H Weaver
2021-04-03 11:29 ` Julien Lepiller [this message]
2021-04-03 21:10 ` Mark H Weaver
2021-04-09 9:06 ` Ludovic Courtès
2021-04-03 13:16 ` Maxime Devos
2021-04-20 14:51 ` Ricardo Wurmus
2021-04-20 21:26 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8BEEF3C6-82DC-459A-9013-3850754DA3B2@lepiller.eu \
--to=julien@lepiller.eu \
--cc=47576@debbugs.gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).