[06:53] <pitti> Good morning
[06:58] <pitti> robru: that's psivaa's email about symlinks?
[08:23] <damianatorrpm> Hello
[08:25] <damianatorrpm> @larsu funktioniert auch mit installierten Schemas nicht, gesettings-qt ist trunk direkt mit bzr runtergeldaen, allerdings muss ich dazu sagen, unter suse nicht ubuntu...
[08:25] <meetingology> damianatorrpm: Error: "larsu" is not a valid command.
[08:53] <larsu> damianatorrpm: sorry, I was afk making some tea :)
[08:54] <larsu> damianatorrpm: so you're not running gnome then?
[08:54] <larsu> damianatorrpm: how are you using the schema? You need to run glib-compile-schemas after installing it
[08:57] <damianatorrpm> Yes I'm running gnome at the moment. sudo glib-compile-schemas /usr/share/glib-2.0/schemas is of course done
[08:58] <damianatorrpm> but the same problem is also with standard key's like org.gnome.whatever
[08:58] <damianatorrpm> in dconf-editor I can correctly see and edit any key
[08:58] <larsu> damianatorrpm: do you have the same problem with the gsettings command line tool?
[08:59] <larsu> gsettings get org.gnome.deskotp.interface gtk-theme
[09:01] <damianatorrpm> larsu: I'm 99% certain that  gsettings get org.gnome.deskotp.interface gtk-theme works properly. Today I have meeting in the office and am not at home so I will try this evening,
[09:03] <Laney> hey there
[09:03] <larsu> Laney: morning
[09:03] <seb128> good morning desktopers!
[09:04] <seb128> hey Laney, larsu
[09:04] <larsu> damianatorrpm: please do, and also try with the keys that you installed. If that doesn't work, it's likely that something's wrong with your schema
[09:04] <seb128> Laney, e-d-s migrated
[09:05] <Laney> yes, I got a lot of emails \o/
[09:05] <seb128> \o/
[09:05] <seb128> pitti is going to be happy
[09:05] <Laney> all those exciting new bugs to discover
[09:05] <seb128> right
[09:05] <Laney> :P
[09:05]  * pitti waves hello to the crowd
[09:06] <seb128> speaking of bugs, I don't get why I'm the only one seeing telepathy-mission-control sigabrt at every login
[09:06] <crowd> hello pitti!
[09:06] <pitti> oh nice! that means upstream merge proposals should now  be unblocked, I'll re-run a few
[09:06] <seb128> hey pitti, wie gehts?
[09:06]  * pitti hugs the cloud^Wcroud^Wlarsu
[09:06] <pitti> seb128: gut, danke! und dir?
[09:06] <larsu> lol
[09:06] <seb128> gut auch, danke!
[09:06] <pitti> seb128: "auch gut"
[09:06] <seb128> ah, danke ;-)
[09:07]  * larsu wonders when we can finally switch the official language of this channel to German
[09:07] <larsu> now that seb128 is almost there...
[09:07] <seb128> :-p
[09:08] <seb128> so I debugged that telepathy sigabrt I see at every greeter use, found quite some issues
[09:08] <seb128> the first one is what is creating the bug
[09:08] <seb128> [   61.537359] type=1400 audit(1385628593.901:86): apparmor="DENIED" operation="mkdir" parent=3888 profile="/usr/lib/telepathy/mission-control-5" name="/var/lib/lightdm/.local/share/telepathy/"
[09:08] <seb128> do you guys see that in your dmesg as well?
[09:08] <seb128> dmesg | grep DENIED
[09:08] <seb128> I don't get why you wouldn't...
[09:09] <psivaa> pitti: yea, i *think robru's ping was about my email
[09:09] <seb128> then mission control has a bug where it reuse a GError without setting it to NULL in between, which is in the codepath for when that dir is not writable
[09:09] <Laney> no denied here
[09:09] <seb128> Laney, is the dir existing for you?
[09:09] <Laney> yeah
[09:10] <seb128> ok, that would explain it
[09:10] <Laney> nod
[09:10] <seb128> if you remove it and go the greater, do you get the deny?
[09:10] <seb128> I wonder if my apparmor config is different somehow
[09:10] <seb128> or if you guys just happened to have the directory created at some point and staying there since
[09:11] <Laney> it got recreated
[09:11] <seb128> shrug
[09:12] <seb128> why is apparmor stopping that for me and not for you :/
[09:12] <Laney> maybe one of us messed with the policies
[09:12] <seb128> I didn't afaik
[09:12] <seb128> and I'm the special case it seems, nobody else mentioned that issue
[09:14] <Laney> that's what I did
[09:14] <Laney> oops
[09:14] <Laney> was scrolled up
[09:15] <seb128> hum, my /etc/apparmor.d/usr.lib.telepathy has
[09:15] <seb128>     owner /var/lib/gdm/.local/share/telepathy/                  rw,
[09:15] <seb128>     owner /var/lib/gdm/.local/share/telepathy/mission-control/  rw,
[09:15] <seb128>     owner /var/lib/gdm/.local/share/telepathy/mission-control/* rwk,
[09:15] <seb128>
[09:15] <seb128> no lightdm entries
[09:16] <seb128> I though HOME was not working out of /home without changing the tunables
[09:16] <seb128> I guess I need jdstrand, that's going to be for next week with thanksgiving
[09:21] <seb128> some days I hate trusty
[09:21] <Noskcaj> Does anyone have time to try and see what's wrong with the extensions in https://code.launchpad.net/~noskcaj/ubuntu/trusty/gthumb/3.2.5/+merge/196783
[09:21] <seb128> lightdm/xorg are screwed on user switching
[09:21] <didrocks> seb128: frusty! ;)
[09:21] <larsu> frusty fahr?
[09:21] <seb128> didrocks, yeah, wth
[09:21] <seb128> Xorg hits a sigabrt with "no display found" error
[09:21] <seb128> lightdm or something gets confused
[09:22] <seb128> and I get a blank screen/vt over vt7/my session when that happens
[09:22] <didrocks> urgh, doesn't sound good
[09:22] <seb128> I can see the cursor changing shape
[09:22] <seb128> but I can't get back the pixels
[09:22] <seb128> going to vt, restarting compiz or another wm doesn't work
[09:22] <seb128> just need to reboot
[09:23] <larsu> so this just happens sometimes, not all of the time?
[09:23] <seb128> robert_ancell said he can reproduce on trusty and seems an xorg error
[09:23] <larsu> we should just drop xorg
[09:23] <seb128> larsu, right, seems a timing issue, between lightdm and xorg
[09:23] <seb128> haha
[09:23] <seb128> anyway, I figured out why I get the telepathy issue
[09:24] <seb128> Laney, do you have gnome-online-account installed ?
[09:24] <seb128> looking at my bootcharts, it does
[09:24] <seb128> lightdm -> unity-greeter -> indicator-datetime -> e-d-s -> goa -> telepathy
[09:24] <Laney> Noskcaj: not sure if anyone here is going to know particularly; we don't ship gthumb
[09:24] <seb128> the indicator should probably not init/use e-d-s at all on the greeter profile, I'm going to bug charles about that
[09:25] <Laney> no, it's not
[09:25] <seb128> the issue stopped after I uninstalled "gnome-online-account"
[09:25] <seb128> ok, that explains then
[09:25] <seb128> btw in the category
[09:25] <seb128> "larsu told you so"
[09:25] <Noskcaj> Laney, ok. I was just a recommendation from dholbach. Xubuntu still does, and no one can fix this
[09:26] <seb128> nomination is bug #1255719
[09:26] <ubot2> Launchpad bug 1255719 in indicator-sync (Ubuntu) "Upstart job keeps respawing indicator-sync on the greeter" [High,New] https://launchpad.net/bugs/1255719
[09:26] <Laney> Noskcaj: check NEWS and so on to find out if they were dropped by upstream
[09:26] <seb128> larsu, ^ I was thinking about you when I filed this one :p
[09:26] <Laney> Noskcaj: also see where they were coming from in the previous package
[09:26] <seb128> larsu, I couldn't troll ted though, those slackers are off eating turkey
[09:28] <larsu> seb128: I will enjoy this moment in silence :)
[09:28] <Laney> ooh, my PS4 is "dispatching soon"
[09:28] <seb128> larsu, ;-)
[09:28] <larsu> thanksgiving?
[09:28] <seb128> Laney, oh, you got one of those?
[09:28]  * Laney will be "sick" tomorrow
[09:28] <seb128> larsu, yes
[09:28]  * seb128 slaps Laney
[09:28] <Laney> yep!
[09:28] <Laney> haha
[09:28] <larsu> lol
[09:28] <seb128> PS4> WANT
[09:28] <seb128> Laney, give it to me!
[09:28] <Laney> go to a midnight launch tonight
[09:29] <seb128> pretty please?
[09:29] <seb128> (being nice is supposed to work :p)
[09:29] <seb128> yeah, so I can get a cold and really be sick with a PS4 tomorrow? :p
[09:29] <Laney> ok I'll get right on that
[09:29] <Laney> sounds like a winning plan to me
[09:29] <seb128> haha
[09:30] <seb128> I would have bought one already, if it was reading PS3 games, but it doesn't :/
[09:30] <larsu> Laney: shouldn't be too hard this time of year. Just get into a subway and touch all the handles
[09:30] <seb128> my PS3 is having some issues, it tends to freeze/lock
[09:30] <Laney> yeah I skipped PS3 so that's not a problem for me except that I would have bought GTA
[09:30] <seb128> I'm not sure if I should buy a PS3 slim to replace it or go with a PS4
[09:31] <Laney> guessing those ps3s are quite cheap now
[09:31] <seb128> seems like there is almost no game available for it atm :/
[09:31] <Laney> oh, still not so much
[09:32] <seb128> ~200€
[09:38] <seb128> larsu, I think your o-s change has a bug, I'm getting gedit to segfault sometimes since yesterday
[09:39] <seb128> gdk_window_has_native: assertion 'GDK_IS_WINDOW (window)' failed
[09:41] <larsu> oh
[09:41] <larsu> do you have a stacktrace?
[09:43] <sil2100> seb128: hello! :)
[09:43] <seb128> larsu, let me install the dbg (and makes sure it's not the GTK update, but I doubt it)
[09:43] <seb128> sil2100, hey, what's up?
[09:44] <ogra_> oha ! my clock is right after switching languages back and forth on the phone ...
[09:44] <seb128> ogra_, hey ... weird, does it persist after a reboot?
[09:44] <ogra_> no more AM/PM
[09:44] <seb128> or is that a one time workaround?
[09:45] <ogra_> it only happens after a reboot ... and then stays that way
[09:45] <sil2100> seb128: do you think you'll have time for a quick preNEW review of lp:unity-voice today? :)
[09:45] <ogra_> i assume we dont update ~/.pam-environment on upgrades ?
[09:45] <seb128> sil2100, you already pinged about that yesterday, I can have a try, still dealing with some other issues
[09:45] <seb128> sil2100, if that's really urgent maybe didrocks can help you?
[09:45] <seb128> ogra_, what upgrades have to do with the user config?
[09:46] <ogra_> so that my manual setting/unsetting/setting actually added something there
[09:46] <didrocks> seb128: it's not, I just want to MIR it later on
[09:46] <didrocks> so that mterry isn't the only one having to MIR everything :)
[09:46] <seb128> didrocks, well, I got 4 pings in a day for it now so I start wondering
[09:46] <ogra_> seb128, well, if we add a setting the user needs to get it with a proper value on upgrade
[09:47] <seb128> ogra_, I don't understand what that has to do with upgrades
[09:47] <ogra_> if my ~/.pam-enviroment was missing a var and key ...
[09:47] <didrocks> seb128: I think as the CI system was down for some some days, upstreams want to get their code released :p
[09:47] <seb128> didrocks, gotcha, anyway it's on my todo
[09:47] <seb128> no need to ping more :p
[09:47] <didrocks> thanks seb128 :)
[09:47] <seb128> yw!
[09:48] <seb128> ogra_, it's good now, even after a reboot?
[09:48] <seb128> ogra_, that bug doesn't make sense to me
[09:48] <ogra_> seb128, if there is a fix thats based on the user having a sprecific var with a specific setting, it should not be needed that the user has to set/unset something in the settings app to get the fix
[09:48] <ogra_> seb128, yes, it seems to persist
[09:48] <seb128> ogra_, right, it should not, but days only have 24 hours
[09:49] <seb128> there is a limit on how much we can get done in a day
[09:49] <ogra_> seb128, sure, i'm just trying to identify the reason of the bug
[09:50] <seb128> ogra_, I guess you picked your locale in the setting at a time where we were setting the language only and no lctime and such
[09:50] <ogra_> right
[09:50] <seb128> so your user config was incomplete
[09:50] <ogra_> thats what i mean ... ~/.pam_environment just stayed that way
[09:50] <seb128> we could try to tweak pam configs on upgrades
[09:50] <ogra_> right
[09:50] <seb128> but well, imho that's not worth the efforts atm
[09:51] <seb128> only early adapter are running touch, and it's easy to go in settings and pick your language again
[09:51] <ogra_> well, most of our users will do OTA upgrades and not reinstall all the time
[09:51] <seb128> right
[09:51] <seb128> our current users are technical enough to be able to workaround it
[09:51] <ogra_> well, i wasnt
[09:51] <ogra_> it bothered me for several weeks and i only worked around it by accident
[09:52] <seb128> well, you just fixed it no? ;-)
[09:52] <seb128> I guess it's part of being an early adopter
[09:52] <ogra_> heh, k
[09:52] <seb128> don't get me wrong, I would like to fix all bugs and all weird cases
[09:53] <seb128> but we just can't justify spending that amonth of efforts on the experience for early adapter updating
[09:53] <seb128> we need to focus on making the product good
[09:53] <seb128> those would started very early might have to deal with some upgrade issues
[09:54] <seb128> but the other alternative is to spend a ridiculous amonth of efforts for a few users and put us behind for the important work
[09:54] <ogra_> well, we should at least have some hooks prepared for such cases ... they will likely also happen on released images at some point
[09:54] <seb128> right
[09:54] <seb128> there is a lot of things we should have
[09:54] <ogra_> surely not urgent right now
[09:54] <ogra_> but something we should at least have a plan for before release
[09:55] <seb128> we have the migration tool didrocks wrote, it's working
[09:55] <ogra_> it didnt in my case :)
[09:55] <seb128> it just requires somebody to actual write the migration code for that case, if you want to handle it
[09:55] <seb128> well, somebody needs to write a script that migrate the config
[09:56] <seb128> it's not rocket science, but it's touch pam config and has possibility to create real issues at login
[09:56] <seb128> so it needs some thinking and testing
[09:56] <ogra_> rihgt
[09:56] <seb128> if you want to do it and send a patch, please do
[09:56] <ogra_> *right even
[09:56] <seb128> but it's just not enough of an issue atm to make the top of my list
[10:00]  * Laney builds new glib
[10:00] <Laney> (muhahaha)
[10:01] <seb128> ;-)
[10:01] <seb128> shrug
[10:01] <seb128> Laney, your e-d-s ppa somewhat made my system unhappy :/
[10:01] <seb128> well I installed that transition back then
[10:01] <Laney> which part?
[10:01] <Laney> the goa bit?
[10:01] <seb128> but trusty doesn't resolve it
[10:01] <seb128> yes
[10:02] <seb128> it removed empathy and I can't install it back
[10:02] <Laney> it's probably diverged somewhat from the archive now
[10:02] <Laney> you should ppa-purge it
[10:02] <seb128>  empathy : Dépend: libgoa-1.0-0 (>= 3.5.1) mais ne sera pas installé
[10:02] <Laney> if that can handle transitions
[10:02] <seb128> shrug
[10:02] <seb128> I've a libgoa-1.0-0b
[10:03] <Laney> yes, the goa transition
[10:03] <Laney> which isn't in archive
[10:03] <seb128> blocked on webkit?
[10:03] <Laney> yeah
[10:03] <Laney> there might be a working qemu/arm64 now though
[10:03] <Laney> https://launchpad.net/ubuntu/+source/qemu/1.6.0+dfsg-2ubuntu3
[10:04] <Laney> will try it later
[10:05] <seb128> $ sudo apt-get instarusty libevolution/trusty evolution-data-server/trusty libgoa-1.0-common/trusty  libgoa-1.0-0b- evolution-plugins/trusty gnome-control-center/trusty unity-scope-gdrive/trusty unity-lens-photos/trusty gir1.2-gdata-0.0/trusty gir1.2-goa-1.0/trusty
[10:05] <seb128> that fixes it
[10:05]  * seb128 doesn't trust ppa purge, just do stuff by hand
[10:06] <ogra_> seb128, i have truned bug 1255530 into a wishlist bug for session-migration and closed the indicator-datetime task
[10:06] <ubot2> Launchpad bug 1255530 in session-migration (Ubuntu) "/home/phablet/.pam_environment does not get updated on OTA upgrades" [Wishlist,New] https://launchpad.net/bugs/1255530
[10:06] <seb128> ogra_, thanks
[10:06] <Laney> yeah that seemed to mess up with reverting the transition here
[10:09] <Laney> for once aptitude was useful in doing that
[10:09] <Laney> like the third option was to downgrade everything to trusty
[10:53] <seb128> larsu, do you want to fix update-manager for the box/scaling issue?
[10:53] <seb128> or should I have a look?
[10:55] <larsu> seb128: I had planned to do it. I'm working in the theme right now though, so if you have time or want to do it, I'd be happy if you did
[10:55] <seb128> larsu, I'm having a look
[11:26] <seb128> larsu, https://code.launchpad.net/~seb128/update-manager/box-use-vertical-space/+merge/197042 fixes the update-manager issue for me
[11:26] <seb128> oh, speaking of update-manager
[11:26] <seb128> hey mvo ;-)
[11:26] <seb128> on that note, lunch time, bbiab
[11:27] <larsu> seb128: are you setting that expand property on a box?
[11:27] <larsu> seb128: ah nvm, enjoy lunch!
[11:40]  * Laney installs new glib packages
[11:40]  * Laney watches PC catch on fire
[11:44] <mvo> seb128: hey! just saw your MP
[11:45] <mlankhorst> didrocks: ping?
[11:46] <seb128> mvo, hey, how are you?
[11:46] <didrocks> mlankhorst: pong
[11:46] <seb128> larsu, yes, seems to work
[11:47] <mlankhorst> didrocks: I was porting pointer barriers to unity-2d, but I noticed that it believes it should create a pointer barrier at 0x0, stretching to 0x0
[11:47]  * seb128 sends some water in Laney's direction
[11:47] <mlankhorst> which somehow works on raring xserver
[11:47] <seb128> Laney, how is the world seen from a new glib?
[11:47] <mlankhorst> but fails with the new pointer barrier implementation
[11:48] <Laney> I didn't restart my session yet because it's building webkitgtk/arm64, but nothing blew up so far
[11:48] <seb128> mlankhorst, what do you mean "ported pointer barriers to unity-2d"?
[11:48] <Laney> downloading a trusty iso to put it in there
[11:48] <seb128> Laney, good
[11:48] <Laney> let me scp it to people and you ca... oh wait, i386
[11:48] <didrocks> mlankhorst: this is for precise I guess?
[11:48] <mlankhorst> didrocks: yes :)
[11:49] <seb128> Laney, ;-)
[11:49] <seb128> Laney, if you push the vcs somewhere I'm happy to test build/install it
[11:49] <Laney> easily fixed!
[11:49] <Laney> s'already building
[11:49] <mlankhorst> seb128: saucy xserver has the upstream pointer barrier abi
[11:50] <mlankhorst> so if i want to backport saucy xserver to precise the pointer barrier implementation of unity and unity-2d need to be changed at runtime
[11:51] <didrocks> mlankhorst: maybe the unity8 guys have some code for that, and can be backported to unity2d
[11:51] <mlankhorst> didrocks: I already ported it
[11:51] <mlankhorst> but I don't see why the pointer barrier is created with 0x0 0x0
[11:51] <didrocks> Kaleo: do you remember? ^
[11:52] <mlankhorst> it's on the s-lts-backport ppa
[11:52] <seb128> mlankhorst, ok, I was not sure if you were adding the feature (e.g if unity-2d has it, it was not feature complete compared to 3d)
[11:52] <mlankhorst> if unity-2d didn't have pointer barriers I wouldn't spend the effort on it :P
[11:52] <Kaleo> didrocks, unity 2D has it, not unity8
[11:54] <didrocks> Kaleo: I think his question was:
[11:54] <didrocks> "why the pointer barrier is created with 0x0 0x0 "
[11:54] <mlankhorst> yeah
[11:55] <mlankhorst> if I look at shell/Shell.qml p2: Qt.point(x, declarativeView.screen.geometry.y + declarativeView.screen.geometry.height)
[11:55] <mlankhorst> p1: Qt.point(x, declarativeView.screen.geometry.y)
[11:56] <mlankhorst> so I'm guessing declarativeView.screen.geometry.height = 0
[11:59] <Kaleo> didrocks, mlankhorst dunno
[11:59] <Kaleo> didrocks, mlankhorst: better ask greyback or Saviq
[12:03] <greyback> mlankhorst: would suspect libunity-2d-private/src/screeninfo.h isn't getting the screen geometry correctly
[12:06] <greyback> mlankhorst: else that piece of qml is being called before the screen geometry has been fetched - and isn't updated when the screen geometry is then corrected
[12:07] <mlankhorst> that would seem likely
[12:13] <mlankhorst>  yeah
[12:14] <mlankhorst> calling xrandr afterwards causes it to create barriers again with more reasonable x/y coordinates
[12:15] <davmor2> seb128: don't know if you can point me in the right direction with this one.  I updated my Saucy Laptop yesterday and now even though the only keybord I have installed is English(UK) it seems to be a US layout
[12:15] <seb128> davmor2, no idea, what's the difference between both?
[12:15] <seb128> I though they were both qwerty
[12:16] <davmor2> seb128: @ becames ", shift 2 becomes @
[12:16] <seb128> davmor2, what is the indicator in the panel saying?
[12:16] <seb128> is that persistant accross reboots?
[12:16] <davmor2> seb128: yeap
[12:17] <Laney> deb http://people.canonical.com/~laney/package-junkyard ./
[12:17] <Laney> ^ glib
[12:20] <mlankhorst> oh wait, floats, grr :P
[12:21] <seb128> Laney, desrt: you guys are boring, I like that!
[12:22] <seb128> (new glib installed, restarted session, no visible change)
[12:23] <Laney> good good
[12:23] <davmor2> seb128: http://ubuntuone.com/7I0RGTAaCn1z9pZOpgsjpT So here I clicked on the indicator and opened the keyboard layout but that isn't what I have :)
[12:23] <seb128> davmor2, is gnome-settings-daemon running?
[12:24] <mlankhorst> ok looks like a printf error, sigh
[12:24] <mlankhorst> back to square 0
[12:26] <davmor2> seb128: running ps aux | grep gnome-settings-daemon I have listed /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper  and nothing else
[12:26] <seb128> davmor2, that's your issue I guess
[12:27] <seb128> davmor2, do you have any apport file for it or an error in .cache/upstart/gnome-settings-daemon.log ?
[12:28] <davmor2> seb128: http://paste.ubuntu.com/6489263
[12:28] <davmor2> seb128: I'll check it now
[12:28] <seb128> davmor2, do you use an nvidia card/driver?
[12:28] <davmor2> seb128: I do
[12:28] <seb128> davmor2, is your machine an optimus one?.
[12:28] <davmor2> seb128: it is
[12:28] <seb128> davmor2, talk to tseliot, that's a known issue with nvidia drivers/optimus
[12:28] <seb128> davmor2, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254
[12:28] <ubot2> Launchpad bug 1224254 in xserver-xorg-video-modesetting (Ubuntu) "xrandr Xerrors with the nvidia binary drivers" [Medium,Triaged]
[12:29] <davmor2> seb128: thanks
[12:29] <seb128> davmor2, uw
[12:29] <seb128> yw
[12:29] <seb128> davmor2, gsettings set org.gnome.settings-daemon.plugins.xrandr active false
[12:30] <seb128> davmor2, that should workaround it (it might make your monitors config wrong though, if that's the case use the nvidia tool I guess)
[12:30] <davmor2> seb128: thanks
[12:30] <seb128> yw
[12:33] <davmor2> seb128: Yay work around worked I have me @'s back  it makes it much easier to send emails now :)  Thanks again :)
[12:34] <seb128> davmor2, yw!
[12:34] <seb128> davmor2, what did you change btw? I'm curious why that just started...
[12:34] <seb128> davmor2, new nvidia drivers?
[12:35] <davmor2> Let me have a look at the update history and see what got installed
[12:37] <seb128> davmor2, one other option is that you did use the monitor configuration tool and got a configuration written and that g-s-d started to try to apply it (where you had none before and it was not trying to apply changes)
[12:37] <Laney> glib is up ...
[12:37] <seb128> davmor2, you can try re-enabling the key and deleting .config/monitors.xml
[12:39] <davmor2> seb128: only xorg change seems to be xserver-xorg-glamoregl
[12:39] <seb128> davmor2, what's the timestamp of .config/monitors.xml ?
[12:39] <Laney> desrt: ↑, should make you happy :-)
[12:40] <davmor2> seb128: no such file or directory
[12:42] <seb128> davmor2, hum, ok, so probably nvidia/optimus by itself then... not sure when that just started being buggy for you
[12:42] <seb128> Laney, WAIT
[12:42] <davmor2> Laney: if glib is up, does that automatically mean that flippant is on the rise too?
[12:42] <seb128> ;-)
[12:42] <Laney> haha, you can't scare me with that
[12:42] <Laney> there's HOURS to put a britney block in yet :P
[12:43] <seb128> hehe
[12:43] <seb128> well, no issue so far and I restarted my session
[12:43] <seb128> so looks good
[12:44] <Laney> davmor2: flippant took a hit on the news, but loquacious is riding its coat tails
[12:44] <davmor2> Laney: as long as sarcasm isn't in decline I don't care :D
[12:50] <mlankhorst> didrocks/greyback/Kaleo: turns out that something in kapplication probably already calls XGetEventData, so XGetEventData call was failing in my handler
[12:50] <mlankhorst> which caused the event to be dorpped
[12:51] <greyback> mlankhorst: that's annoying
[12:51] <mlankhorst> yeah, at least new pointer barriers work now :)
[12:51] <seb128> shrug
[12:52] <seb128> Laney, new glib is buggy, put a block please
[12:52] <seb128> Laney, desrt, larsu: with glib 2.39 I can't change indicator-power settings (e.g display % in panel, in the indicator menu), it displays those on start
[12:53] <seb128> g_simple_action_set_state: assertion 'state_type != NULL' failed
[12:53] <seb128> desrt, larsu, Laney: http://paste.ubuntu.com/6489372/
[12:54] <seb128> works fine if I LD_PRELOAD the 2.38 libgio
[12:57]  * larsu takes a look
[12:59] <Laney> true, seems a change in glib causes this
[13:03] <larsu> hm, this might be it? https://git.gnome.org/browse/glib/commit/?id=83869120bba2aa745a1b23fb415ab0eddd6f9327
[13:05] <Laney> Is the bug that you're not giving the type when constructing the GSimpleAction?
[13:06] <larsu> Laney: yep, just found that in indicator-power
[13:06] <Laney> nod
[13:06] <larsu> it's g_settings_binding something to the state of an action that was not created with g_simple_action_new_stateful
[13:07] <Laney> Isn't it that you're using g_simple_action_new(..., NULL) instead of the type there?
[13:07] <Laney> oh, maybe not
[13:07]  * Laney gets it
[13:07] <larsu> no, the second argument to that function is the activation parameter
[13:07] <Laney> yeah
[13:07] <larsu> I'll have a patch up in a bit, this doesn't seem hard
[13:08]  * larsu compiles glib
[13:08] <Laney> no need
[13:08] <Laney> deb http://people.canonical.com/~laney/package-junkyard ./
[13:08] <larsu> ah, thanks :)
[13:08] <seb128> or get the debs from https://launchpad.net/ubuntu/+source/glib2.0/2.39.1-0ubuntu1/+build/5277767
[13:09] <Laney> yeah if you like downloading stuff :P
[13:13] <larsu> I wonder why charles didn't just use a gsettingsaction
[13:17] <apw> seb128, a fun one for you: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1255970
[13:17] <ubot2> Launchpad bug 1255970 in gnome-screensaver (Ubuntu) "multi-monitor: when the screen saver self-engages only the focused screen is visually protected" [Undecided,New]
[13:18] <seb128> apw, can you reproduce? I had that once like a month ago and couldn't reproduce it after that :/
[13:19] <apw> seb128, if you hand-engage the screensaver with C-A-l it changes behaviour
[13:20] <apw> seb128, but if you reboot and let it lock by itself it seems reproducible
[13:20] <apw> (as someone who manually locks most of the time that is why it took me so long work out how it occurred)
[13:20] <seb128> apw, ok, that would explain why I couldn't reproduce, I usually lock by suspending/closing lid/manual action
[13:21] <seb128> never by timeout
[13:21] <seb128> apw, thanks!
[13:21] <apw> yeah timeout seems to be the key
[13:21] <apw> and only timeout any other seems to fix it somehow
[13:23] <larsu> seb128: https://code.launchpad.net/~larsu/indicator-power/use-gsettings-actions/+merge/197066
[13:27] <seb128> larsu, looking
[13:27] <seb128> larsu, do you know why charles did it the complex way rather than the simple one?
[13:28] <larsu> seb128: probably because he didn't know about g_settings_create_action when he wrote this, or that function didn't exists back then. I'll ask him for a review when he's up
[13:29] <seb128> larsu, it's thanksgiving, he's off until next week (like most americans)
[13:29] <larsu> ah, right :-/
[13:29] <seb128> larsu, I'm testing it, codes looks fine to me... do you want a second review from e.g desrt or Laney before having it approved? (I don't want to wait for next week since new glib got uploaded)
[13:30] <larsu> Laney: ^
[13:30] <larsu> sure
[13:32] <Laney> It looks sensible to me but let's wait for desrt's ack
[13:32] <Laney> he should be along quite soon
[13:33] <seb128> larsu, do you want a bug report for the record/discussion with charles next week?
[13:35] <larsu> seb128: I can also just send him an email
[13:35] <larsu> hm, but I guess bug is better for everyone to look at
[13:36] <seb128> larsu, right, let me do that
[13:40] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1255981
[13:40] <ubot2> Launchpad bug 1255981 in indicator-power (Ubuntu) "Indicator options stopped working with glib 2.39.1" [Undecided,New]
[13:40] <larsu> seb128: thanks, I'll link the branch
[13:40] <seb128> larsu, danke
[14:08] <desrt> woh
[14:08] <desrt> new GLib is up?
[14:08] <seb128> desrt, good morning!
[14:09] <desrt> good morning
[14:09] <desrt> warning: pre-coffee
[14:09] <seb128> desrt, no worry, I've no ping/question/trolls for you today ;-)
[14:09]  * desrt saw something about a review a bit up
[14:10] <seb128> desrt, oh, right, that's a small/easy one, if you want to have a look for larsu (charles is off due to thanksgiving)
[14:12] <larsu> desrt: morning! Please drink coffee first ;)  https://code.launchpad.net/~larsu/indicator-power/use-gsettings-actions/+merge/197066
[14:13] <larsu> desrt: new glib broke the old code because you commited a patch that enforces the type of the state
[14:13] <desrt> erm
[14:13] <desrt> shouldn't you call g_settings_action_new()?
[14:13] <larsu> bah
[14:13] <desrt> sorry.  i'll get on that coffee :)
[14:13]  * desrt forgot that it's not friday yet
[14:14] <larsu> it's always Friday somewhere in the world!
[14:14] <desrt> speaking of g_settings_action_new(), though, did you take a look at your other favourite bug in the world?
[14:14] <desrt> larsu: that's actually not true.....
[14:14] <larsu> I saw it, but didn't have time to have a look yet
[14:15] <desrt> it's evil
[14:15] <larsu> that's what I figured. How did you end up doing it? varargs macro?
[14:15]  * desrt uses a varargs macro trick to implement default arguments
[14:15] <larsu> right
[14:15] <desrt> #define a(x,y,...) func(x,y)
[14:15] <desrt> #define func(...) a(__VA_ARGS__,NULL)
[14:16] <desrt> if you give two args to func() then they become x,y
[14:16] <desrt> if you get one arg, then it becomes x and NULL becomes y
[14:16] <larsu> and it doesn't error out anymore if you give the wrong number of args
[14:16] <desrt> well
[14:16] <larsu> well, it does, but it'll be hard to read
[14:16]  * sil2100 looks at seb128 from behind the corner
[14:16] <desrt> if you give 3 then it will ignore the rest, ya
[14:16] <desrt> but i don't think there is too much concern there
[14:17] <seb128> sil2100, shrug, sorry I've too much to do I'm not going to do that review, please find another archive admin
[14:17]  * sil2100 hides behind the corner again
[14:17] <larsu> desrt: won't gcc warn when you give 3 args?
[14:17] <larsu> ah wait, you never define a
[14:17] <desrt> larsu: no.  the macro takes (...)
[14:17] <larsu> that'll work. but ugh, that's evil
[14:17] <seb128> sil2100, sorry, but I've it on my todolist, no need of 5 pings in 24 hours, that's adding stress for no good reason
[14:17] <desrt> larsu: it gets worse
[14:18] <larsu> desrt: but it gets expanded to a(x,y,NULL)
[14:18] <desrt> larsu: we're going to break ABI at some point in the future
[14:18] <seb128> sil2100, either it's a top priority must drop everything to do it and say it (didrocks said it's not the case) or just stop nagging for a few days
[14:18] <desrt> larsu: that's where the second macro(x,y,...) comes in
[14:18] <desrt> the NULL ends up in the ... and gets ignored
[14:18] <sil2100> Sure, sorry for nagging
[14:19] <seb128> sil2100, no worry, thanks for understanding
[14:19] <larsu> desrt: break abi because you'll drop the version that takes a length?
[14:19] <desrt> yup
[14:20] <desrt> larsu: the way the macros work is that a mere recompile will cause everyone who was passing a length to g_variant_get_string() to stop doing so
[14:20] <desrt> so then we can silently remove the second arg to that function after a while
[14:20] <desrt> lots of code will be out there that pass NULL
[14:20] <larsu> hm, so compile errors everywhere
[14:20] <desrt> but second arguments are ignored -- a fact that we use a lot in glib
[14:21] <desrt> my code auditing shows that very few people actually call this function with non-NULL second arg anyway...
[14:21] <larsu> but there will be this one case that prevents seb128 from logging in one morning
[14:21] <desrt> we have a stepped escalation plan in the bug :)
[14:22] <desrt> first comes the critical... then the assert that can be turned off... then the hard break
[14:23] <desrt> anyway... the proposal is pretty wild.  needs reviews.
[14:23] <larsu> I'll have a look when I get some time
[14:23] <seb128> doesn't like the sound of those changes
[14:23]  * larsu was waiting for that exact phrase :)
[14:24] <seb128> there is no such thing than "time before it's fine to change an ABI in an incompatible way"
[14:25] <seb128> if you claim to be ABI stable
[14:25] <desrt> oh seb.  you're so oldschool.
[14:25] <larsu> he's cute, isn't he?
[14:25]  * larsu hides
[14:26] <larsu> desrt: but really, seb has a point. We should just make it glib 3.0
[14:26] <desrt> seb128: speaking seriously, though, there's a single user of this feature in gnome
[14:26] <desrt> in gtk
[14:26] <seb128> somebody out there, in some business, is having a software from 15 years ago they need and which is no maintained anymore and they are going to be unhappy
[14:26] <seb128> well, that one user could be NASA and it could be an app in a space shuttle that used to run fine for 15 years
[14:26] <desrt> seb128: my point is that nobody uses this second parameter
[14:26] <seb128> you never knows
[14:26] <desrt> that's why people hate it so much
[14:26]  * larsu resists being pedantic and pointing out that this function is only 5ish years old
[14:26] <seb128> you don't know
[14:27] <seb128> larsu, ;-)
[14:27] <larsu> desrt: what's speaking against only doing step (1)?
[14:27] <seb128> larsu, I'm more arguing with the philosophy of "nobody is using it, it's probably fine to make an incompatible change"
[14:27] <desrt> larsu: the sheer ugliness of the interim
[14:27] <larsu> meh
[14:27] <larsu> sheer ugliness if what we have now
[14:34] <desrt> hmm
[14:34] <desrt> there's some people not passing NULL as the second argument
[14:34] <desrt> ....they're passing 0
[14:38] <larsu> how!?
[14:38] <larsu> why?
[14:38] <larsu> wtf?
[14:47] <larsu> seb128: do you still have the issue with the small file chooser?
[14:47] <seb128> larsu, yes
[14:47] <seb128> larsu, I've opened https://bugzilla.gnome.org/show_bug.cgi?id=712288 with details
[14:47] <ubot2> Gnome bug 712288 in GtkFileChooser "The default dimension of the fileselectors are a bit small" [Normal,Unconfirmed]
[14:48] <seb128> larsu, but basically it's by directory, so "mkdir /tmp/gtkfswth; gedit /tmp/gtkfswth/larsu; ctrl-S"
[14:48] <larsu> seb128: I get (740, 607)
[14:49] <seb128> larsu, what's your screen resolution?
[14:49] <larsu> seb128: same thing when I do that
[14:49] <larsu> seb128: 1366x768
[14:49] <seb128> larsu, I guess that's ok, 626 for 1920 is a bit small
[14:49] <seb128> larsu, well, anyway, not a blocker for the update
[14:50] <seb128> larsu, feel free to not spend time on that, it's a small annoyance, we can still look at it later/see how many users get annoyed by it
[14:50] <larsu> seb128: okay.
[14:50] <desrt> larsu: NULL == 0
[14:50] <seb128> larsu, seems like we are going to push to the ppa once the overlay-scrollbar merge is in?
[14:50] <larsu> seb128: the theme issue is a small fix - turns out the gedit problems I was seeing went away with 3.10.5
[14:50] <seb128> larsu, oh, you still had the theme issues as well
[14:51] <seb128> larsu, is 3.10.5 screwing up the g-c-c geometry?
[14:51] <seb128> larsu, e.g do we need https://git.gnome.org/browse/gnome-control-center/commit/?id=d54b8864abc8b69042db73df562b2cfc84714a69 ?
[14:51] <desrt> a teacher once told me that NULL might not be equal to zero and therefore you should never do if(ptr) but always if(ptr!=NULL)
[14:51] <larsu> seb128: I'm building it right now -- or trying to... a patch doesn't apply :)
[14:51] <desrt> that teacher was an idiot
[14:51] <larsu> desrt: I know, but I've never ever seen anyone use 0 instead of NULL
[14:52] <desrt> larsu: i do if i'm lazy :)
[14:52] <larsu> ugh
[14:52] <larsu> stop being lazy!
[14:52] <desrt> like writing a real quick program and i don't want to include stddef
[14:52] <desrt> if god intended for us to use NULL he would have made it a language feature
[14:52] <larsu> you write programs that don't include glib.h? :P
[14:53] <desrt> larsu: ya.  sometimes they use <gio/gio.h> instead
[14:53] <larsu> s/god/k&c/ ?
[14:53] <desrt> k&r
[14:53] <larsu> ya.
[14:53] <desrt> how did they call it in the matrix?
[14:53] <desrt> the architect?
[14:53] <larsu> I think so, yes
[15:18] <seb128> attente, hey, are you there?
[15:19] <attente> seb128, yep
[15:19] <seb128> attente, can you join #ubuntu-app-devel ?
[15:44] <larsu> seb128: ya, we need to apply the patch. Also, I'm seeing theming issues again now that it's installed :-/
[15:44] <seb128> :-(
[15:45] <seb128> larsu, I need to check if that patch makes it still look ok with gtk 3.8
[15:45] <larsu> I wonder why I didn't see those when running from the build dir ...
[15:45]  * seb128 hates it when gtk update forces you to patch apps to look as they use to look
[15:46] <seb128> sil2100,
[15:46] <seb128> ./tests/autopilot/unity_voice/__init__.py: LGPL (v3 or later)
[15:46] <larsu> ugh, right. But I don't see why it shouldn't work
[15:46] <seb128> sil2100, that needs to be reflected in the changelog
[15:46] <seb128> sil2100, ./tests/autopilot/setup.py: GPL (v3 or later) as well (the "or later")
[15:50] <sil2100> seb128: yes, that's  the one part I prepared a fix for, the branch is ready - I missed the setup.py one though, thanks!
[15:50] <sil2100> seb128: thank you for the review \o/
[15:53] <seb128> sil2100, yw
[15:53] <seb128> sil2100, cf #ubuntu-touch as well, the libdev is missing depends
[15:53] <seb128> larsu, sorry, got sidetracked... what doesn't work? can I help in some way?
[15:55] <larsu> seb128: I have black backgrounds in gedit and devhelp
[15:55] <larsu> I'm trying to find out why right now. I hope it's not something that got fixed in the apps
[15:55] <seb128> larsu, do you get any error on the command line?
[15:56] <seb128> larsu, I don't get that with 3.10.4 in gedit (and 3.10.5 shouldn't have any theming change)
[15:56] <larsu> seb128: this is with the universal background disabled in the theme
[15:57] <larsu> seb128: which makes the info bars work
[15:57] <seb128> oh, ok :/
[16:00] <larsu> seb128: running gedit against my locally built gtk 3.10 works :/
[16:00] <larsu> so... one of our patches?!
[16:00]  * larsu is confused
[16:01] <seb128> larsu, is one of those loading overlay-scrollbars and not the other one?
[16:01] <seb128> larsu, we had bugs about that in the past... (just saying)
[16:02] <larsu> seb128: you are a genious!
[16:02] <larsu> that's it
[16:02] <seb128> larsu, https://bugs.launchpad.net/overlay-scrollbar/+bug/1096907
[16:02] <ubot2> Launchpad bug 1096907 in overlay-scrollbar "Scrollbars cause GTK rendering issues with specific combinations of widgets and themes" [Undecided,New]
[16:02] <seb128> larsu, ;-)
[16:05] <ogra_> hmm
[16:05]  * ogra_ notices that he shouldnt have checked the closk before 12 for 24h time :P
[16:05] <ogra_> seems the time is still 12h format ... but the AM/PM is gone
[16:06] <seb128> ogra_, :-(
[16:06] <ogra_> yeah
[16:06] <larsu> seb128: thanks. Just when I thought I was done with o-s :-/
[16:06] <ogra_> i guess we still miss a variable
[16:06] <larsu> I think we should just drop them
[16:06] <seb128> larsu, I was about to make a comment about how much you must be loving the o-s right now
[16:07]  * seb128 hugs larsu
[16:07]  * ogra_ guesses they can be drtopped once we switched to unity8
[16:07] <seb128> ogra_, or reimplemented for qt :p
[16:09] <ogra_> lol
[16:09] <ogra_> i doubt thats necessary
[16:12] <larsu> seb128, desrt: surely we can live with that, right? http://i.imgur.com/CLufvB2.png
[16:12] <larsu> this happens in all themes btw
[16:13] <didrocks> larsu: no one will notice
[16:13] <desrt> including adwaita?
[16:13] <desrt> looks pretty bad...
[16:13] <didrocks> if only it was aubergine :)
[16:14] <larsu> desrt: yes. It doesn't happen without overlay-scrollbars
[16:14] <larsu> lol
[16:14] <desrt> ...
[16:14] <ochosi> yeah, the overlay scrollbar issue is quite bad
[16:14] <desrt> i don't get it
[16:14] <ochosi> themes need an ubuntu-specific patch...
[16:14] <desrt> how the hell does overlay scrollbars have anything to do with that?
[16:14] <ochosi> in xubuntu we carry one for our themes that we don't ship in other distros
[16:14] <larsu> ochosi: they do?
[16:14] <ochosi> well they mess with the background
[16:14]  * desrt sobs
[16:15] <ochosi> if you're interested, i can dig up our patch
[16:15]  * desrt wants to float larsu down a river of beer
[16:15] <larsu> ochosi: does it look like this: * { background-color: @bg_color }
[16:15] <desrt> ...with seb paying...
[16:15] <ochosi> yeah, pretty much
[16:15] <ochosi> but that breaks nautilus and some background stuff
[16:15] <ochosi> just not very nice code...
[16:15] <larsu> ochosi: that's what I thought. I just removed that because it messes with other stuff
[16:15] <ochosi> imo the overlay-scrollbars should be fixed, finally
[16:15] <larsu> like GtkInfoBars in 3.10
[16:15] <ochosi> it has been like that for ages now...
[16:15] <larsu> ochosi: s/fixeds/removed
[16:16] <ochosi> well, whatever option
[16:16] <ochosi> we're not shipping this stuff in xubuntu, i just get annoyed cause we still get bugreports about this kind of stuff :/
[16:16] <larsu> desrt: thanks :)
[16:16] <desrt> larsu: you're definitely on the icecream list in... uh... february
[16:17] <larsu> desrt: February is the best time for ice cream
[16:17] <ochosi> larsu: if there are changes to that, please feel free to ping me...
[16:17] <ochosi> i'd really love to drop that silly patch...
[16:17] <larsu> ochosi: will do
[16:17] <ochosi> thanks larsu!
[16:18] <larsu> seb128: ^^ so ... GktInfoBar or working theme? It's your choice! :P
[16:19] <seb128> larsu, can't we away by tweaking the infobar bg in the theme?
[16:20] <seb128> desrt, I would gladly pay as much beer as larsu wants to drink, but I wouldn't feel good, the guy drinks like one every second day
[16:20] <desrt> marga: hey... tending to dconf bugs lately... are you still working on the NFS native backend?
[16:20] <larsu> seb128: no, that's what my talk with Company the other day was about
[16:21] <seb128> larsu, what is so special about infobars?
[16:22] <seb128> larsu, forget about the infobars and the theme, that's not a blocker and we can get cimi to look at it for us
[16:22] <seb128> larsu, you did the work for porting the o-s, he can do the theme tweaking
[16:22] <larsu> seb128: nothing, they're just the first ones to experience the problem.
[16:23] <larsu> seb128: this is an issue with o-s
[16:23] <larsu> it happens in every theme
[16:23] <seb128> larsu, right, but it's not a new one
[16:23] <larsu> true
[16:23] <seb128> I want to get that LTS out with minimal changes
[16:23] <seb128> I don't want somebody to spend a week updating the theme
[16:24] <larsu> right
[16:24] <larsu> I'll upload the theme patch anyway
[16:24] <seb128> larsu, thanks
[16:24] <larsu> seb128: it's up to you of you want to apply it or not
[16:24] <seb128> larsu, seems like we should be good for the ppa then?
[16:25] <seb128> larsu, I think I'm going to do a first iteration without it, infobar looking backgroundless is less annoying that your screenshot's bug
[16:26] <larsu> seb128: I agree. PPA sounds good. Let me push the last fix (update to 3.5 and removing a patch)
[16:26] <seb128> larsu, btw, that bug is https://bugs.launchpad.net/overlay-scrollbar/+bug/1059374
[16:26] <ubot2> Launchpad bug 1059374 in overlay-scrollbar (Ubuntu) "Using Adwaita, many widgets are drawn with a solid black background" [Low,Triaged]
[16:26] <larsu> seb128: yes, because Adwaita doesn't have that hack in it
[16:28] <seb128> larsu, xim has a similar bug and got fixed with https://bug682395.bugzilla-attachments.gnome.org/attachment.cgi?id=225450
[16:28] <seb128> larsu, I wonder if the scrollbar issue is similar
[16:30] <larsu> seb128: ah, I can have a look for that. The overlay widget definitely needs to be native (that's the fix I made), but maybe the module accidentally turns the other ones native as well
[16:30] <larsu> seb128: push into ~larsu/gtk/3.10
[16:30] <larsu> do I need to prepare anything else for the ppa?
[16:30] <seb128> larsu, no, I'm going to take it from there, thanks!
[16:31] <seb128> larsu, o-s does   xid = GDK_WINDOW_XID (gtk_widget_get_window (widget));
[16:31] <seb128> not sure if that's an issue
[16:31] <larsu> ya, just saw this as well
[16:31] <larsu> I'm trying to get rid of it right now
[16:31] <larsu> thanks for the pointer to that patch!
[16:31] <seb128> larsu, thanks, let me know how it goes
[16:31] <seb128> yw ;-)
[16:33] <attente> chrisccoulson, hey
[16:34] <attente> i'm having trouble using bzr get-orig-source on firefox trunk
[16:35] <attente> it seems to download everything but fails at the tarball packing stage
[16:49] <larsu> seb128: that doesn't seem to help :(
[16:50] <seb128> larsu, :-(
[16:50] <seb128> that's annoying :/
[16:57] <ogra_> seb128, so copying the output from locale on my desktop into .pam_environment on my grouper makes it properly show 17:57 on boot on the lock screen ... and as soon as the panel clock comes up it goes to 05:57
[16:57] <ogra_> so still the same issue :/
[16:57] <seb128> ogra_, seems it's not an environment issue then
[16:57] <ogra_> just no AM/PM anymore
[16:57] <seb128> rather something in the qml widget they use
[16:58] <ogra_> i guess the environment does not get handed over to upstart
[16:58] <ogra_> iirc the indicators are all upstart session jobs now
[16:58] <seb128> ogra_, you can easily check
[16:58] <seb128> ogra_, string /proc/$(pidof unity8)/environ | grep LC
[16:58] <seb128> strings*
[16:59] <ogra_> initctl list-env shows them proper
[16:59] <seb128> well your description suggests it's right
[16:59] <ogra_> letzs see what proc says
[16:59] <seb128> then overwritten
[16:59] <seb128> so probably not an env issue
[17:00] <ogra_> grr ... no "strings" command on the image
[17:00] <seb128> ogra_, you can try to grep directly
[17:01] <ogra_> well, i pulled it to my desktop
[17:01] <ogra_> looks fine too
[17:01] <seb128> yeah, that's what I though, if the initial state is fine, the environment is fine
[17:01] <seb128> seems like an unity8 issue
[17:01] <seb128> they have a custom component for that
[17:01] <seb128> which seems buggy
[17:02] <ogra_> ah
[17:07] <robru> sil2100, when you get back tell me what needs to be done with unity-voice and i'll do it.
[17:07] <seb128> larsu, ok, gtk and o-s with the patch (since it didn't got merged yet) pushed to the ppa, the build is starting on some hours, we should have packages ready to test tomorrow morning (I'm going to follow up on my previous "status update email" then)
[17:07] <seb128> on that note, I'm away for exercice
[17:07] <seb128> bbl
[17:08] <larsu> seb128: enjoy!
[17:08] <seb128> larsu, danke ;-)
[17:09] <seb128> larsu, btw, I know you get pinged every direction, do you know what happened with the timestamp/messaging menu issue from rsalveti?
[17:09] <seb128> larsu, is that something on the indicator side? did you guys get to debug it?
[17:11] <seb128> larsu, unping, just found the bug and your comment saying that the data is correct so the issue is on the unity side
[17:11] <larsu> seb128: yep, I investigated it this morning when I got rsalveti's logs
[17:12] <seb128> larsu, seems like you had yet another of those crazy days, you should call is a day now and go for some beer or exercice or walk or something ;-)
[17:12] <seb128> on that note, exercice here!
[17:12] <seb128> bbl
[17:13] <larsu> seb128: yep, meeting with a friend in a bit :) Enjoy, and thanks for your help!
[17:13] <seb128> larsu, thanks, have fun, see you tomorrow ;-)
[17:34] <mvo> seb128: hi, I'm a bit sick today (a nasty cold) but otherwise I'm good. just merged your patch, I guess its fine if I upload it now?
[17:51] <seb128> mvo, hey, sure it is, thanks!
[17:51] <seb128> mvo, I hope you get better!
[17:52] <mvo> thanks, its already (slowly) getting better, aspirin ftw :)
[17:52] <seb128> mvo, some schnaps and some sleep should help there ;-)
[17:52] <mvo> haha
[17:52] <mvo> that is my second option :)
[17:53] <ogra_> seb128, filed bug 1256061 .... not sure what to do as next steps :)
[17:53] <ubot2> Launchpad bug 1256061 in unity8 (Ubuntu) "clock forcefully switches from 24h to 12h AM/PM format once the panel clock is loaded" [Undecided,New] https://launchpad.net/bugs/1256061
[17:53] <seb128> ogra_, get Saviq or some unity8 guy to debug/fix it ;-)
[17:53] <ogra_> heh
[17:54] <ogra_> he is so loaded with stuff already ...
[17:56] <ogra_> phew ... and bug 1256062
[17:56] <ubot2> Launchpad bug 1256062 in session-migration (Ubuntu) "session-migration needs to be handled by upstart session" [Undecided,New] https://launchpad.net/bugs/1256062
[17:57] <ogra_> thats enough bugs for a day
[17:57] <seb128> ogra_, let's see, maybe larsu is done next week with the stuff he was working on and can help you having a look to that time format issue, he knows that code a bit I think
[17:58] <ogra_> seb128, great ... i dont think its overly urgent ...
[17:58] <ogra_> but something we should have fixed by release
[17:58] <seb128> right, that's why I said next week
[17:58] <ogra_> yeah
[17:58] <ogra_> or next month ... as it fits
[17:58] <seb128> right, let's see how things go
[20:06] <sil2100> robru: sure, give me a moment :)
[20:26] <sil2100> robru: actually, I see Pete fixed the other issue, and I have prepared a branch for fixing the copyright things already - could you review?
[20:26] <sil2100> robru: I'll just lp-propose it now
[20:26] <robru> sil2100, of course
[20:28] <sil2100> robru: https://code.launchpad.net/~ubuntu-unity/unity-voice/packaging_fixes/+merge/197115
[20:28] <sil2100> robru: thanks!
[20:28] <sil2100> robru: I pushed it to ~ubuntu-unity so that we can all edit it if needed
[20:29] <robru> sil2100, approved
[20:30] <sil2100> robru: \o/ Thanks ;) We'll still probably have to re-poke seb128 or someone to make sure the fixes are right, but it's not top-priority I guess
[20:31] <robru> sil2100, well i was told to release this two days ago, so it's already quite late...
[20:31] <sil2100> Ah... sadly, Sebastien was busy, so hm, maybe we could find some other archive admin to preNEW it in the meantime?
[20:32] <robru> sil2100, do you know of anybody? last time I tried to do this, nobody knew what a preNEW even meant. apparently that's something specifc to daily-release and not all archive admins are familiar.
[20:32] <sil2100> The whitelist is updated, so it's just a ACK from an admin required and you can publish then
[20:33] <sil2100> robru: sadly no one specific comes into my mind - usually you can poke some archive admin and just say to look at the packaging as if he was reviewing it during NEWing
[20:33] <sil2100> robru: so, looking at the packaging if it's ok to release into the archive - and if yes, simply give you a green light
[20:33] <sil2100> robru: the whitelist is updated so all we need is a thumbs up from archive admins, and you can then push the publish button ;)
[20:34] <robru> sil2100, ok
[20:34] <robru> sil2100, https://launchpad.net/~ubuntu-archive/+members#active who of these would be awake now? considering americans are off and europeans are nearing EOD...
[20:35] <sil2100> Ah, crap, right... the US guys are off, hmm
[20:36] <robru> sil2100, oh, stgraber is canadian! ;-)
[20:36] <sil2100> !
[20:36] <sil2100> Ok, so we have our victim!
[20:37] <robru> sil2100, apparently infinity is also canadian.... hmmm not a bad representation on the archive team ;-)
[20:38] <robru> sil2100, i'm in #ubuntu-release now
[21:41] <seb128> Laney, glib made gtk build unhappy
[21:41] <seb128> https://launchpadlibrarian.net/157838364/buildlog_ubuntu-trusty-i386.gtk%2B3.0_3.10.5-0ubuntu1~build1.1_FAILEDTOBUILD.txt.gz
[21:42] <seb128> GLib-GIO:ERROR:/build/buildd/glib2.0-2.39.1/./gio/gtestdbus.c:618:start_daemon: assertion failed (error == NULL): Failed to execute child process "dbus-daemon" (No such file or directory) (g-exec-error-quark, 8)
[21:45] <seb128> robru, hey, I read you email, no real recommandation... wait on Debian or build an Ubuntu version with changes,turning off tests and subscribe sponsors
[21:48] <seb128> larsu, ^ just as a fyi, gtk didn't build in the ppa because of the glib issue I mentioned to Laney
[21:50] <larsu> seb128: thanks. Anything I  can do to help?
[21:51] <seb128> larsu, no, it's probably just a depends to add to glib, but that's a topic for tomorrow
[21:51] <larsu> ya
[21:51] <larsu> I'm off for tonight anyway
[21:51] <seb128> yeah, me too
[21:51] <larsu> good night!
[21:51] <seb128> I was about to go
[21:51] <seb128> night
[21:52] <seb128> larsu, you too, see you tomorrow ;-)
[23:47] <ochosi> robert_ancell: hey, i started to observe a problem with lightdm and light-locker recently and i'm wondering whether it could be a regression. after starting my computer/session, logging out and back in, i can't lock the session anymore. also dm-tool doesn't work. there's no error, lightdm simply doesn't respond it seems (switch-to-greeter also doesn't work)
[23:47] <robert_ancell> ochosi, what does the log say?
[23:48] <ochosi> robert_ancell: strangely enough nothing
[23:48] <ochosi> and it seems to be quite reproducible
[23:48] <robert_ancell> is the daemon still running?
[23:48] <ochosi> light-locker you mean?
[23:48] <ochosi> yeah
[23:49] <ochosi> that one is running
[23:49] <ochosi> but i think it has nothing to do with light-locker, as it also doesn't work with dm-tool
[23:49] <ochosi> after starting the session the first time, everything is fine, only the second time it's borked
[23:50] <ali1234> o/
[23:50] <ochosi> robert_ancell: ali1234 is also testing this lightdm/light-locker problem ^
[23:50] <robert_ancell> ochosi, I mean the lightdm daemon
[23:51] <ochosi> hm, let me quickly check...
[23:51] <robert_ancell> just as a sanity check :)
[23:51] <robert_ancell> can you paste the lightdm.log after you use dm-tool?
[23:51] <ochosi> lightdm is still running
[23:51] <ochosi> ok, one sec
[23:53] <ochosi> robert_ancell: this is twice or thrice dm-tool lock: http://dpaste.com/1486619/
[23:53] <ali1234> ok, this time light-locker was definitely running. exact same result
[23:54] <ochosi> so yeah, actually there are two issues
[23:54] <ochosi> not sure whether they are connected
[23:54] <robert_ancell> ochosi, is this trusty?
[23:54] <ochosi> robert_ancell: no, saucy
[23:54] <robert_ancell> This is the relavant line: [+943.62s] DEBUG: Process 3209 terminated with signal 6
[23:55] <ochosi> lightdm1.8.4
[23:55] <ali1234> yes, the xserver on :1 fails to start
[23:55] <ochosi> hm
[23:55] <robert_ancell> It's the X server crashing when lightdm tries to start a greeter
[23:55] <ali1234> i have Xorg logs...
[23:55] <ochosi> weird, why would it crash?
[23:55] <robert_ancell> We've been seeing it more in lightdm 1.9 / trusty
[23:55] <ochosi> ok
[23:55] <ochosi> so you're aware of this already?
[23:55] <robert_ancell> In trusty it quits with a "no screens found" error
[23:55] <robert_ancell> just been seeing it this week
[23:55] <ochosi> :/
[23:55] <robert_ancell> But hadn't seen it in saucy
[23:55] <ochosi> ok, well then at least i know it's not in light-locker..
[23:56] <ali1234> (21:14:50) ali1234: this is when it works: http://paste.ubuntu.com/6491291/
[23:56] <ali1234> (21:14:57) ali1234: this is when it doesn't:http://paste.ubuntu.com/6491290/
[23:56] <robert_ancell> ochosi, could you file a bug with how to reproduce?
[23:56] <robert_ancell> I need to get someone who knows X better to diagnose
[23:56] <ali1234> basically, login, logout, login, lock screen (any method) -> Xorg fails to start on :1
[23:57] <ochosi> yeah
[23:57] <robert_ancell> yeah, we were doing - login, logout, login, switch to guest
[23:57] <ochosi> i can do it tomorrow, it's kinda late here and i just returned from a party... :)
[23:57] <ochosi> yeah, that's the same
[23:57] <ali1234> (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
[23:57] <ochosi> switch-to-greeter also seems to produce the same result
[23:57] <robert_ancell> yeah, X log shows same error
[23:57] <ali1234> "sudo service lightdm" restart clears the error until you login, logout, login again
[23:58] <ochosi> brb
[23:58] <ali1234> so does this affect ubuntu-desktop too?
[23:59] <robert_ancell> ali1234, yes
[23:59] <ali1234> well, at least it's not my patches then :)
[23:59] <robert_ancell> :)