Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] appmenu-gtk-module: missing schema file
Date: Fri, 15 Dec 2023 07:27:49 +0100	[thread overview]
Message-ID: <20231215062749.IgOv4jEUy75i9Av0zC-WwfhgoEZACCD-7JhJyVqdwvc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34419@inbox.vuxu.org>

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

Closed issue by HiPhish on void-packages repository

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

Description:
### System

* xuname: `Void 5.15.6_1 x86_64 AuthenticAMD notuptodate rrmFFF`
* package:
  * `appmenu-gtk-module-0.7.6_1`
  * `appmenu-gtk3-module-0.7.6_1`

### Expected behavior
The GTK module should work.

### Actual behavior
The module does not work, starting an application prints the following to standard output:

```
$ gimp
(gimp:20057): GLib-GIO-ERROR **: 01:13:46.321: Settings schema 'org.appmenu.gtk-module' is not installed
```

Manually adding the schema file from the upstream repository to `/usr/share/glib-2.0/schemas/` and then executing `sudo glib-compile-schemas` fixes the issue.

I don't know much about XBPS, but from this I figure that the schema file should be copied over as part of the installation process and that the schema compilation needs to be carried out. If someone can point me in the right direction I could give a try fixing the build script.

      parent reply	other threads:[~2023-12-15  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 15:27 [ISSUE] " HiPhish
2022-02-19  7:55 ` dtreffenstaedt
2022-06-18  2:13 ` github-actions
2022-06-18 12:20 ` HiPhish
2023-12-14 20:58 ` NinjaCowboy
2023-12-15  6:27 ` sgn [this message]

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=20231215062749.IgOv4jEUy75i9Av0zC-WwfhgoEZACCD-7JhJyVqdwvc@z \
    --to=sgn@users.noreply.github.com \
    --cc=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).