=== prth|away is now known as prth === prth is now known as prth|away [09:05] darkxst, I'll try and get the slideshow done tomorrow, i'll be away till tuesday after that [09:06] Noskcaj, ok, thanks! [11:01] Hello .. gnome-weather does not start .. it reports: http://paste.debian.net/plain/123953 [11:02] I guess it should be rebuild against last libgweather [11:07] l3on, was that from -staging? [11:45] darkxst, yep [13:54] hi all [15:27] l3on, hi, i can reproduce this libgweather problem, same thing with gnome-clocks and gnome-weather, no idea why though yet [15:27] ricotz, gnome-clocks here works fine. [15:28] seems like a gtkbuilder problem [15:28] l3on, try to add a new clock [15:28] ricotz, uh ok, confirmed... [15:29] gtkbuilder somehow cant instantiate GWeatherLocationEntry objects defined in the ui files [15:30] l3on, maybe you like to dig into it a bit further [15:31] darkxst, just for references, this is some g-i problem ^ === prth is now known as prth|away [15:56] ricotz, $ python -c 'from gi.repository.GWeather import LocationEntry' && echo ok [15:56] py seems work fine [15:59] even gjs $ gjs -c "imports.gi.GWeather.LocationEntry || print('fail')" [16:11] boh.. have to go.. bye! :) === prth is now known as prth|away [23:31] So I've hit a bug in 14.10 and not quite sure where to report it [23:32] Starting a few gtk apps leads to an immediate crash and a message that says "Attempt to unlock mutex that was not locked" [23:33] It seems like the issue might have been fixed upstream already, since a bit of searching around lead me to this fix: https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec [23:34] But I'm not sure when/if that's going to filter through to 14.10 [23:34] Any advice on which tracker these kinds of issues should be reported to? [23:35] Seems like the issue has been reported against a few specific projects that are affected, e.g. pyrenamer [23:36] ...but I'm also hitting it in a closed-source 3rd party app, Stata, and unless it gets patched at the glib/gtk level project-specific fixes won't help with that