[02:23] <jamesh> robert_ancell_: I'm not sure if you'll run into it yourself, but snapd-glib really doesn't like running in an app linked to libjson-c due to symbol conflicts with libjson-glib
[02:24] <robert_ancell> jamesh, oh really?
[02:25] <robert_ancell> Do you know which symbols?
[02:25] <jamesh> robert_ancell_: if you ever run into weird errors where json_object_get_type() is returning something it couldn't possibly be, check if the right one is being called
[02:27] <jamesh> in snapd-glib, I was hitting a line "if (json_node_get_value_type (node) != JSON_TYPE_OBJECT) {" where get_value_type() was returning the GType for JsonObject, but JSON_TYPE_OBJECT was returning 0
[02:28] <jamesh> and adding some debug prints caused the app to crash (since the two json_object_get_type functions take different arguments)
[02:29] <jamesh> I don't think there is anything you can realistically do about it though.
[02:38] <robert_ancell> jamesh, is this because snapd-glib is linking to one version and the app using snapd-glib is linking to another?
[02:38] <jamesh> robert_ancell: yeah.  The old version of Pulse Audio in xenial was linking to libjson-c
[02:39] <robert_ancell> oh, libjson-c and libjson-glib. I missed  that.
[02:39] <jamesh> so when it dlopened a module linking to libsnapd-glib, the libjson-c symbols took precedence
[02:39] <robert_ancell> Right, there's probably no solution if both libraries are using the same symbols :/
[02:39] <robert_ancell> Unless there's some linking flags to fix this.
[02:40] <robert_ancell> Is libjson-c deprecateD?
[02:40] <jamesh> robert_ancell: lucky for me, this had caused problems for other GNOME apps linking to libpulse, so they switched to an internal json parser library
[02:40] <jamesh> so I ended up backporting that
[02:40] <robert_ancell> nice.
[02:41] <jamesh> libjson-c isn't associated with GNOME or any other big project.  I think it still makes releases
[05:43] <vicky> jbicha: Okay.. I already filed a bug https://gitlab.gnome.org/GNOME/gdm/issues/507
[05:43] <gitbot> GNOME issue 507 in gdm "gdm3 login screen is blank and does not show greeter" [2. Needs Information, Opened]
[07:00] <oSoMoN> good morning desktoppers
[08:54] <marcustomlinson> morning oSoMoN
[09:17] <marcustomlinson> oSoMoN: I noticed that chromium's drm is a little broke. Is this known?
[09:17] <marcustomlinson> Widevine is detected here but I get a DRM_NO_KEY_SYSTEM error: https://bitmovin.com/demos/drm
[09:20] <marcustomlinson> oh it might be that I've downloaded the wrong version of widevine
[09:21] <marcustomlinson> do you know how to determine which version is for your chrome?
[09:30] <oSoMoN> good morning marcustomlinson
[09:31] <oSoMoN> I'd recommend downloading the chrome deb matching the version number of chromium, and extracting libwidevinecdm.so from there
[09:49] <marcustomlinson> Ok cool I’ll try that sometime today
[09:49] <marcustomlinson> thx
[10:04] <marcustomlinson> oSoMoN: I assume there are legal implications to us shipping widevine in our snap?
[10:07] <oSoMoN> yes, basically we can't do that
[14:13] <JanC> chromium can't download it itself?
[14:22] <oSoMoN> JanC, if you're referring to widevine, there's no built-in mechanism in chromium to download and enable it like there is in firefox
[18:22] <Laney> moin
[18:23] <Trevinho> hey Laaaney
[18:23] <Laney> yo Trevinho
[18:46] <oSoMoN> hey Laney, Trevinho
[18:46] <Trevinho> hey oSoMoN
[18:53] <Laney> o/ oSoMoN