Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bug: when uninstalling fcitx, permissions on mime database get set to wrong ones
Date: Fri, 29 Apr 2022 04:12:55 +0200	[thread overview]
Message-ID: <20220429021255.W_1gzaREplxXN6MlFNfDug6-8IJIlmhlhY2db2cu_uo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4455@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Closed issue by etosan on void-packages repository

https://github.com/void-linux/void-packages/issues/4455

Description:
### System

* xuname:  `Void 4.18.16_2 x86_64 GenuineIntel uptodate rFF`

* package:  `fcitx-4.2.9.6_3`

### Expected behavior

Everything works.

### Actual behavior

I guess it's called "mime database" or something. Well those things under  `/usr/share/mime` get fucked up permissions breaking almost all gtk apps (I guess gtk is unable to read meta info about icon theme or something).

Error message produced by affected apps is completely useless and off the mark:
`Gtk:ERROR:gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png:  bla bla (gdk-pixbuf-error-quark, 3)`

Reinstalling this gem `xbps-install fcitx` fixes it. I guess there might be error in uninstall trigger? 
Even then, umask of `xbps-remove` invoking user is pretty standard:
```
: umask                               
u=rwx,g=rx,o=rx
```
### Steps to reproduce the behavior

  - install fcitx
  - remove fcitx
  - watch world burn

           reply	other threads:[~2022-04-29  2:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-4455@inbox.vuxu.org>]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220429021255.W_1gzaREplxXN6MlFNfDug6-8IJIlmhlhY2db2cu_uo@z \
    --to=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).