Your message dated Wed, 26 Feb 2025 14:05:46 -0700
with message-id <[email protected]>
and subject line Closing 1098950
has caused the Debian Bug report #1098950,
regarding libglib2.0-bin: glib-compile-schemas does not seem to update gettings
schema
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1098950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098950
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libglib2.0-bin
Version: 2.83.3-2
Severity: important
Dear Maintainer,
I am attempting to add a schema to my program, however, after running
glib-compile-schemas, the schema is not added, causing my program to
crash. I tested the schema with --strict and --dry-run, and glib-
compile-schemas does not abort, so I do not think there is an error in
my schema.
I am atttaching the terminal output below.
Please forgive me if there is a PEBPAK issue, however I believe I ruled
that out.
chris@SpaceballstheX2100:~/dev/gtk-meshtastic-client$ cat
/usr/share/glib-2.0/schemas/org.kop316.meshtastic.gschema.xml
<?xml version="1.0" encoding="UTF-8"?>
<schemalist gettext-domain="gtk-meshtastic-client">
<schema id="org.kop316.meshtastic" path="/org/kop316/meshtastic/">
<key name="print-packets" type="b">
<default>false</default>
<summary>Print Packets</summary>
<description>Print all packets in stdout.</description>
</key>
<key name="log-packets" type="b">
<default>false</default>
<summary>Log Packets</summary>
<description>Log all packets into the
$XDG_CONFIG_HOME/gtk_meshtastic_client/</description>
</key>
<key name="return-sends-message" type="b">
<default>false</default>
<summary>Enter key sends the message</summary>
<description>Whether pressing Enter key sends the
message</description>
</key>
<key name="gps" type="b">
<default>false</default>
<summary>Create a GPS Socket</summary>
<description>Whether to create a GPS Socket</description>
</key>
<key name="quit-if-connected" type="b">
<default>true</default>
<summary>Quit if Connected</summary>
<description>Whether to quit if the Window is closed and you are
connected</description>
</key>
</schema>
</schemalist>
chris@SpaceballstheX2100:~/dev/gtk-meshtastic-client$ sudo
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas --strict --dry-
run
/usr/share/glib-2.0/schemas
chris@SpaceballstheX2100:~/dev/gtk-meshtastic-client$ sudo
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas --strict
/usr/share/glib-2.0/schemas
chris@SpaceballstheX2100:~/dev/gtk-meshtastic-client$ gsettings list-
keys org.kop316.meshtastic
log-packets
print-packets
quit-if-connected
return-sends-message
test
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libglib2.0-bin depends on:
ii libc6 2.40-7
ii libelf1t64 0.192-4
ii libglib2.0-0t64 2.83.3-2
ii libglib2.0-data 2.83.3-2
libglib2.0-bin recommends no packages.
libglib2.0-bin suggests no packages.
-- no debconf information
--
Respectfully,
Chris Talbot
--- End Message ---
--- Begin Message ---
My apoligies,
This was in fact a PEBAC issue.
If anyone sees this in the future:
gsettings looks in all of the directories in $XDG_DATA_DIRS/glib-
2.0/schemas for gsettings. /usr/local/share is before /usr/share, and I
had installed gsettings in there, and it took precedent over
/usr/share.
Once that was fixed, the settings were fine.
--
Respectfully,
Chris Talbot
--- End Message ---
