#glib — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #glib, aggregated by home.social.
-
My adventures of writing GTK programs in Rust took a turn this this time.
https://gitlab.com/guystreeter/rgdbus-server
is a server and client example of using glib's D-Bus interface in Rust. I discovered a few things that haven't been implemented, but was generally successful.
#glib #Rustlang #programming -
Finally got my YouTube live chat API client library working with the peel C++ bindings generator for #GLib / #GObject. I built a small coroutine task abstraction that makes working with GLib-style async functions much cleaner.
Still a lot more work to do to with caching/refreshing OAuth tokens and processing of messages, but hopefully I can get a prototype libpurple plugin (the ultimate goal) working fairly soon
-
NOW? NOW?? NOW!?!? NOW "we" think they're #GLIB !!!?? #FUCKING.GLIB !!!??
RE: https://bsky.app/profile/did:plc:aonrplpou355iyrtvtimbj2q/post/3mh2yn42ywt2z -
Looks like it's a problem with the XDG Template directory being set to the home directory, and it now just recurses and recurses and recurses and gets FAR too busy.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118444#38
Specifically, it's about `$HOME/` not being recognised as the home directory because of the trailing slash.
https://gitlab.gnome.org/GNOME/glib/-/issues/3811
So either edit your config as per the Debian comment, or wait for your distro to release the fix.
-
Looks like it's a problem with the XDG Template directory being set to the home directory, and it now just recurses and recurses and recurses and gets FAR too busy.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118444#38
Specifically, it's about `$HOME/` not being recognised as the home directory because of the trailing slash.
https://gitlab.gnome.org/GNOME/glib/-/issues/3811
So either edit your config as per the Debian comment, or wait for your distro to release the fix.
-
Looks like it's a problem with the XDG Template directory being set to the home directory, and it now just recurses and recurses and recurses and gets FAR too busy.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118444#38
Specifically, it's about `$HOME/` not being recognised as the home directory because of the trailing slash.
https://gitlab.gnome.org/GNOME/glib/-/issues/3811
So either edit your config as per the Debian comment, or wait for your distro to release the fix.
-
Looks like it's a problem with the XDG Template directory being set to the home directory, and it now just recurses and recurses and recurses and gets FAR too busy.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118444#38
Specifically, it's about `$HOME/` not being recognised as the home directory because of the trailing slash.
https://gitlab.gnome.org/GNOME/glib/-/issues/3811
So either edit your config as per the Debian comment, or wait for your distro to release the fix.
-
Looks like it's a problem with the XDG Template directory being set to the home directory, and it now just recurses and recurses and recurses and gets FAR too busy.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118444#38
Specifically, it's about `$HOME/` not being recognised as the home directory because of the trailing slash.
https://gitlab.gnome.org/GNOME/glib/-/issues/3811
So either edit your config as per the Debian comment, or wait for your distro to release the fix.
-
#DailyBird 🤖
Glossy Ibis (Plegadis falcinellus), 8th May 2024
es: Morito Común, fr: Ibis Falcinelle
Cape Henlopen State Park, The Glade, Delaware
Lenapehoking (Lenni-Lenape) & Pocomoke-Assateague traditional territory
Canon EOS R5, Canon RF 200-800mm f/6.3-9 + 1.4x teleconverter @ 1120mm, 20% crop, 1/400s, f/14, ISO 1250
#Birds #GlossyIbis #GLIB #BirdOfTheDay #HopeIsTheThingWithFeathers #DescribeYourImages -
#DailyBird 🤖
Glossy Ibis (Plegadis falcinellus), 8th May 2024
es: Morito Común, fr: Ibis Falcinelle
Cape Henlopen State Park, The Glade, Delaware
Lenapehoking (Lenni-Lenape) & Pocomoke-Assateague traditional territory
Canon EOS R5, Canon RF 200-800mm f/6.3-9 + 1.4x teleconverter @ 1120mm, 20% crop, 1/400s, f/14, ISO 1250
#Birds #GlossyIbis #GLIB #BirdOfTheDay #HopeIsTheThingWithFeathers #DescribeYourImages -
#DailyBird 🤖
Glossy Ibis (Plegadis falcinellus), 8th May 2024
es: Morito Común, fr: Ibis Falcinelle
Cape Henlopen State Park, The Glade, Delaware
Lenapehoking (Lenni-Lenape) & Pocomoke-Assateague traditional territory
Canon EOS R5, Canon RF 200-800mm f/6.3-9 + 1.4x teleconverter @ 1120mm, 20% crop, 1/400s, f/14, ISO 1250
#Birds #GlossyIbis #GLIB #BirdOfTheDay #HopeIsTheThingWithFeathers #DescribeYourImages -
#DailyBird 🤖
Glossy Ibis (Plegadis falcinellus), 8th May 2024
es: Morito Común, fr: Ibis Falcinelle
Cape Henlopen State Park, The Glade, Delaware
Lenapehoking (Lenni-Lenape) & Pocomoke-Assateague traditional territory
Canon EOS R5, Canon RF 200-800mm f/6.3-9 + 1.4x teleconverter @ 1120mm, 20% crop, 1/400s, f/14, ISO 1250
#Birds #GlossyIbis #GLIB #BirdOfTheDay #HopeIsTheThingWithFeathers #DescribeYourImages -
#DailyBird 🤖
Glossy Ibis (Plegadis falcinellus), 8th May 2024
es: Morito Común, fr: Ibis Falcinelle
Cape Henlopen State Park, The Glade, Delaware
Lenapehoking (Lenni-Lenape) & Pocomoke-Assateague traditional territory
Canon EOS R5, Canon RF 200-800mm f/6.3-9 + 1.4x teleconverter @ 1120mm, 20% crop, 1/400s, f/14, ISO 1250
#Birds #GlossyIbis #GLIB #BirdOfTheDay #HopeIsTheThingWithFeathers #DescribeYourImages -
First a bit of context for the GLib project, which is comprised of three main parts: GLib, GObject and GIO. #GLib contains things you'd generally get from a standard library, #GObject defines the OOP semantics (methods/properties/signals, inheritance, etc), and #GIO provides reasonably high-level APIs for everything from sockets and files to D-Bus and Gio.DesktopAppInfo.
-
First a bit of context for the GLib project, which is comprised of three main parts: GLib, GObject and GIO. #GLib contains things you'd generally get from a standard library, #GObject defines the OOP semantics (methods/properties/signals, inheritance, etc), and #GIO provides reasonably high-level APIs for everything from sockets and files to D-Bus and Gio.DesktopAppInfo.
-
First a bit of context for the GLib project, which is comprised of three main parts: GLib, GObject and GIO. #GLib contains things you'd generally get from a standard library, #GObject defines the OOP semantics (methods/properties/signals, inheritance, etc), and #GIO provides reasonably high-level APIs for everything from sockets and files to D-Bus and Gio.DesktopAppInfo.
-
First a bit of context for the GLib project, which is comprised of three main parts: GLib, GObject and GIO. #GLib contains things you'd generally get from a standard library, #GObject defines the OOP semantics (methods/properties/signals, inheritance, etc), and #GIO provides reasonably high-level APIs for everything from sockets and files to D-Bus and Gio.DesktopAppInfo.
-
First a bit of context for the GLib project, which is comprised of three main parts: GLib, GObject and GIO. #GLib contains things you'd generally get from a standard library, #GObject defines the OOP semantics (methods/properties/signals, inheritance, etc), and #GIO provides reasonably high-level APIs for everything from sockets and files to D-Bus and Gio.DesktopAppInfo.
-
Well that's something new. Must be a circular dependency between glib-2.82.4,2 and gobject-introspection@bootstrap, but I'm not entirely sure which port to file a bug against; I suspect gobject-introspection.
-
Well that's something new. Must be a circular dependency between glib-2.82.4,2 and gobject-introspection@bootstrap, but I'm not entirely sure which port to file a bug against; I suspect gobject-introspection.
-
Well that's something new. Must be a circular dependency between glib-2.82.4,2 and gobject-introspection@bootstrap, but I'm not entirely sure which port to file a bug against; I suspect gobject-introspection.
-
Well that's something new. Must be a circular dependency between glib-2.82.4,2 and gobject-introspection@bootstrap, but I'm not entirely sure which port to file a bug against; I suspect gobject-introspection.
-
Well that's something new. Must be a circular dependency between glib-2.82.4,2 and gobject-introspection@bootstrap, but I'm not entirely sure which port to file a bug against; I suspect gobject-introspection.
-
I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…
-
I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…
-
I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…
-
I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…
-
I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Play FlappyBird, but written in #vala !
https://gitlab.com/nda-cunh/flappyvala
Using only #SFML and #glib as dependencies.
The code is object oriented and a very good example for a non-gtk Vala app. Check it out! -
Play FlappyBird, but written in #vala !
https://gitlab.com/nda-cunh/flappyvala
Using only #SFML and #glib as dependencies.
The code is object oriented and a very good example for a non-gtk Vala app. Check it out! -
Play FlappyBird, but written in #vala !
https://gitlab.com/nda-cunh/flappyvala
Using only #SFML and #glib as dependencies.
The code is object oriented and a very good example for a non-gtk Vala app. Check it out! -
Play FlappyBird, but written in #vala !
https://gitlab.com/nda-cunh/flappyvala
Using only #SFML and #glib as dependencies.
The code is object oriented and a very good example for a non-gtk Vala app. Check it out! -
Play FlappyBird, but written in #vala !
https://gitlab.com/nda-cunh/flappyvala
Using only #SFML and #glib as dependencies.
The code is object oriented and a very good example for a non-gtk Vala app. Check it out! -
CW: old cat yells about packaging and cross-compiling
Feels like I got into shaving a whole herd of yaks when I just wanted to access NetworkManager over D-Bus from Python on a certain embedded system. :neocat_laugh_sweat:
* The only non-deprecated, non-systemd way to do that (short of handwriting a client library) seems to be python-gobject and introspection.
* The #Buildroot packages for python-gobject and gobject introspection are marked as glibc-only, but I'm using musl. And I know they work on Alpine just fine.
* The GLib, gobject-introspection, and python-object versions in Buildroot are very old. And Alpine actually dropped a musl-compatibility patch with the most recent gobject-introspection version. So… update time.
* The #GLib build process changed and now requires a bootstrap step to support introspection.
* Turns out… Bootstrap or not, introspection isn't supported when cross-compiling. :neocat_scream_stare:
We'll see where it goes from here, the gobject-introspection package in Buildroot does some wild things with Qemu to work around a similar limitation. And there are some somewhat recent changes related to cross-compiling upstream. :neocat_think: -
CW: old cat yells about packaging and cross-compiling
Feels like I got into shaving a whole herd of yaks when I just wanted to access NetworkManager over D-Bus from Python on a certain embedded system. :neocat_laugh_sweat:
* The only non-deprecated, non-systemd way to do that (short of handwriting a client library) seems to be python-gobject and introspection.
* The #Buildroot packages for python-gobject and gobject introspection are marked as glibc-only, but I'm using musl. And I know they work on Alpine just fine.
* The GLib, gobject-introspection, and python-object versions in Buildroot are very old. And Alpine actually dropped a musl-compatibility patch with the most recent gobject-introspection version. So… update time.
* The #GLib build process changed and now requires a bootstrap step to support introspection.
* Turns out… Bootstrap or not, introspection isn't supported when cross-compiling. :neocat_scream_stare:
We'll see where it goes from here, the gobject-introspection package in Buildroot does some wild things with Qemu to work around a similar limitation. And there are some somewhat recent changes related to cross-compiling upstream. :neocat_think:
