[00:00] * robert_ancell heads to lunch, be back in 30-60 [00:01] i can report a bug, but what do you want me to reproduce with? trusty, ubuntu-desktop in virtualbox (assuming i can?) [00:03] ali1234: that would be great, i'm not in a good mindset anymore now to write something that makes sense.. [00:03] also... maybe we're only seeing it now because of my patches, which change the RetainPermanent stuff in lightdm-gtk-greeter, xfwm4, and xfdesktop [00:03] think i'll head to bed and look at this again tomorrow [00:03] makes more sense [00:03] ali1234: i'm not using your patches atm [00:03] ah yes, good point [00:03] and i had that issue way before you started working on this [00:04] s/that/these/ [00:04] i'll do some tests with clean isos in virtualbox [00:04] so you're certainly not to blame ;) [00:04] cool [00:04] i'll check in again tomorrow [00:04] night everyone! [00:51] well, it didn't happen with trusty daily in virtualbox [00:54] ali1234, oh really? I could reproduce it reliably in trusty yesterday [00:54] i reproduced it with the guest session [00:54] seb128 said that downgrading to 1.8 seemed to make the problem go away [00:54] ali1234, but not lock screen? [00:54] it's put a greeter on top of my user session :/ [00:55] i couldn't reproduce it by login, logout, login, lock [00:55] that sounds bad! [00:55] switched to virtualbox console and the display has gone completely mad [00:56] i didn't install the guest drivers either [00:56] lightdm just bombed out and sent me back to the login screen [00:57] i'm not convinced this is the same issue. i'm going to try on real hardware [01:29] actually now i think about it, what i saw in virtualbox sounds like what someone else described with trusty [01:29] and from looking at it, it looks like two xservers are fighting for the same framebuffer [01:30] so a theory: on saucy the second x server simply fails to load because the first one owns the framebuffer. on trusty it somehow gets past that and they fight... [01:30] or perhaps the result is X server implementation specific [01:34] ah... again, i can only reproduce with the guest session [01:35] and the result is the same: intel x server fails to start due to permission error [01:37] it seems like locking the screen on unity/trusty does not create a second X server instance. i only have Xorg.1.log and not Xorg.1.log.old [01:38] robert_ancell: what package do you want me to report it against? [01:38] ali1234, mark it against lightdm and I'll also mark it against xorg [01:40] "the problem cannot be reported. this is not an official ubuntu package..." [01:40] i just installed from the daily iso... [01:41] on the console: cat: /etc/lightdm/lightdm.conf: No such file or directory [01:45] i did touch /etc/lightdm/lightdm.conf and now the report is uploading.... [01:48] bug 1256150 [01:48] Launchpad bug 1256150 in lightdm (Ubuntu) "Xorg guest session fails to start if the user has logged out and logged in again" [Undecided,New] https://launchpad.net/bugs/1256150 [02:01] ali1234, thanks! [02:02] "log out" has now stopped working completely [02:03] ! [02:03] I have to go, but I will have a look next week at this [02:03] i'm going to wipe this install for trusty/xubuntu now, the bug should still be easily reproducable there, and i need to test a bunch of things [02:04] ah... log out just took 4 minutes for no reason... [07:23] Good morning [07:25] hello [07:32] morning [08:06] GM all :) [08:07] larsu: how are you :) [08:32] damianatorrpm: good morning. I'm good thanks. How are you? [08:33] good morning desktopers [08:33] damianatorrpm: I saw your emails. Do you get any other output on stdout? [08:38] larsu: Thanks. I'm fine too, it's Friday :-) [08:39] larsu: no other stdout output. I also started QtCreator from terminal to see for any more output, nada. I also tried qmlscene and run the main.qml [08:39] larsu: stii no difference. [08:40] *still [08:43] damianatorrpm: hm, I'm starting to run out of ideas :-/ [08:43] larsu: Can I show you via teamviewer? [08:45] damianatorrpm: never used that. Do they have a linux version? [08:46] larsu: yes :) .deb for 64 and 32 bit Ubuntu as well as .rpm for suse and fedora http://www.teamviewer.com/en/download/linux.aspx [08:46] larsu: It's free of charge for personal use and works *always* [08:46] :) === jhernand1z is now known as jhernandez [08:47] and is not free software :P (I'll install it, give me a sec) [08:48] larsu: really appreciated. Thanks [09:02] morning [09:02] hi Laney, how's it going? [09:02] pretty good, happy to have made it to friday ;-) [09:02] you? [09:04] same same :) [09:07] what's this dbus-daemon thing? [09:09] Laney: ps4 on the way? ;) [09:09] delivered 10:04-11:04 :D [09:10] ;) [09:11] didrocks: did you go out for a midnight launch? ;-) [09:11] Laney: no, I don't plan to buy it before a year at least [09:12] oho [09:12] I want games I'm interested in on the platform first ;) [09:12] like watch dogs [09:12] fair enough [09:20] back [09:20] front [09:21] Laney, ogra_, hey, happy friday ;-) [09:21] same to you :) [09:21] hey seb128 [09:21] Laney, how are you? [09:23] Laney, you made rb unhappy, no music today :-( [09:23] does banshee work? :-) [09:24] lol [09:24] (good thanks) [09:24] do I look like I use GTK2 apps still? [09:24] that is one sexy GTK2 app [09:24] you are so old fashion... ;-) [09:25] (but yeah, banshee works ;-) [09:25] (you did that on purpose to made people use banshee, admit it!) [09:25] :-) [09:25] anyway, I saw the bug, hopefully we can get a fix today [09:26] we should get that i-power fix out too [09:26] yeah [09:26] hum, glib migrated to trusty [09:27] (it hadn't yesterday due to libffi but infinity fixed that) [09:27] Laney, btw did you see my ping about GTK build? [09:27] yes [09:27] want to understand what changed there [09:27] ok [09:27] just making sure it didn't get lost in the backlog [09:28] it seems suboptimal if we have to make glib-dev depends on dbus [09:28] I don't see any changes in that code in glib [09:29] hum, maybe GTK started used something in glib that was not used before? [09:29] checking that [09:32] speaking about indicator-power [09:32] larsu, did you ever get desrt to +1 or -1 your action change? [09:33] ah, I think it's a new Ubuntu patch [09:33] gtk-object-tests-run-under-local-environment calls g_test_dbus_up() [09:34] oh [09:35] which uses dbus-daemon, but that's nothing new [09:35] so I'd probably add the BD [09:35] that seems wrong though [09:35] if glib provides an api [09:35] it should bring with it what is needed for the api to work [09:36] or handle the case where the depends are missing... [09:38] it would be quite heavy though http://162.213.35.4/search?weighted=1&q=g_test_dbus_up [09:40] the indicators use dbus-test-runner so b-d on it, and that brings in dbus [09:40] yeah [09:40] but yeah, options are [09:40] 1- add a dbus depends to libglib2.0-dev [09:40] 2- workaround it by adding a dbus b-d to packages using that api [09:40] dbus-x11 [09:41] seb128: he said he needed to drink coffee first. And then he didn't ever look at it [09:41] I'll ping him again today [09:41] 3- split the glib files out in a new binary which has the depends [09:41] larsu, thanks [09:41] I don't like any of the 3 options :/ [09:42] but I guess the b-d is the less annoying one [09:42] same [09:42] maybe glib could improve its message in that case, but it's quite obvious currently anyway [09:42] let's do a ppa upload with dbus-x11 b-d [09:42] k, ta [09:43] thanks for looking at it! [09:43] xnox: Do you have some time to help out on those libtimezonemap reviews? [09:44] I feel bad for not looking at them sooner, but I honestly have never looked at this code before [09:44] kind of got dumped in it there really [09:44] yeah. i should review them. they do look good. [09:44] he seems to have done 1 commit per change-ish [09:44] so I'll take some of them and cherry-pick them [10:02] omg bzr-gtk went away? [10:03] yes, in saucy [10:04] guess the fact that I only just noticed says something :P [10:04] it needed porting to the new version of something and nobody wanted to do the work iirc [11:03] desrt, wake up, I need you :p [11:09] desrt, n-m is having an issue similar to rhythmbox, http://paste.ubuntu.com/6493541/ [11:09] desrt, I'm going to have a look at reverting this glib commit [11:09] Laney, ^ or do you want to do that? [11:11] seb128: go ahead, would be good to confirm it actually does fix things before uploading it though [11:12] Laney, right, I'm not going to upload glib without testing, no worry [11:12] I'm going to wait for desrt to be up, but I can as well start testing building/running it [11:12] seems unsafe anyway if we've discovered two applications in the first day [11:12] they might want to rethink it upstream [11:12] right === MacSlow is now known as MacSlow|lunch [12:15] shrug [12:15] GTK build still not happy :/ [12:15] https://launchpadlibrarian.net/157877308/buildlog_ubuntu-trusty-i386.gtk%2B3.0_3.10.5-0ubuntu1~build1.3_FAILEDTOBUILD.txt.gz [12:15] /properties/GtkColorChooserDialog: [12:15] (/build/buildd/gtk+3.0-3.10.5/debian/build/shared/testsuite/gtk/.libs/lt-object:20493): GLib-GIO-ERROR **: No GSettings schemas are installed on the system [12:15] FAIL [12:16] I guess it's looking in the system location, not the source [12:16] larsu, ^ [12:20] brb, session restart with glib and the constructore change reverted [12:26] xnox: reviewed a few of the changes, left some for you [12:27] seb128: so, you know this lightdm/guest session bug... apparently it went away when you downgraded lightdm to 1.8? but i can reproduce it in saucy, which uses 1.8.4 [12:27] ali1234, hey, weird ... it's rock solid for me with 1.8.4 [12:28] ali1234, it maybe is a timing issue and I just happen to be one side of the timing issue with 1.9 and on the other side with 1.8 [12:28] we reproduced it in saucy not with guest session, but with the screen lock dialog, which xubuntu opens on :1, causing an identical problem [12:28] it's not a timing issue, lightdm actually tells Xorg to run on the wrong VT [12:28] ok [12:28] is that the same one? [12:29] well, maybe, maybe not [12:29] but it's reproducable the exact same way [12:29] if you've logged out and logged in, and then ask lightdm to start a display on :1, it will attempt to start it on VT7, which is already used by :0 [12:29] in trusty I get xorg hitting a "no screen found" error [12:30] the result depends on driver. you get no screen found with intel [12:30] with others, you get two xorgs on the same VT and they fight each other [12:30] right, I'm using intel [12:30] right [12:30] for me it's like a get a vt over my xorg [12:30] but checking lightdm logs, it's explicitly telling Xorg to use the wrong VT [12:30] e.g my vt7 is blank, but I can move the cursor and see it change shape where there are windows from my session [12:30] ok, good [12:30] seems like a bug for robert_ancell to fix then [12:31] ali1234, thanks for figuring that out! [12:31] alreday reported. he's the one who told me you said 1.8 fixes it [12:31] well, it does for me [12:31] perhaps it handles guest and "lock" slightly different [12:31] could be [12:31] and only one got fixed [12:31] what I do is [12:31] - log in [12:31] - log out [12:31] - log in [12:31] - start a guest from indicator-session [12:32] that works in saucy [12:32] but screws my session with 1.9 [12:32] i haven't tried that on saucy, what we do is same: log in, log out, log in, lock screen with light-locker (that tries to start :1 and does exactly the same thing in saucy and trusty) [12:33] guest session also does it in trusty, but never tested that in saucy cos we didn't know that was also an issue at the time [12:33] ok [12:35] ali1234, yeah, I can confirm that in the log I sent to robert_ancell [12:36] DEBUG: Launching process 4073: /usr/bin/X -core :1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch [12:36] well, let's see if resolving that issue fixes things for the different scenarios [12:36] yeah. bug 1256150 btw [12:36] Launchpad bug 1256150 in xorg (Ubuntu) "Xorg guest session fails to start if the user has logged out and logged in again" [High,Confirmed] https://launchpad.net/bugs/1256150 [12:38] right, I saw it in my bug emails box this morning === MacSlow|lunch is now known as MacSlow [13:09] seb128: seems related to my patch for https://bugzilla.gnome.org/show_bug.cgi?id=711715 [13:09] Gnome bug 711715 in general "gtk object tests: run under local environment" [Normal,New] [13:09] seb128: (sorry, I was out for lunch) [13:10] larsu, no worry, I tested the hack debian is doing [13:10] larsu, https://launchpadlibrarian.net/157881868/gtk%2B3.0_3.10.5-0ubuntu1~build1.3_3.10.5-0ubuntu1~build2.diff.gz [13:11] larsu, tested -> I'm testing rather (it's building) [13:14] seb128: ya that'll probably work. I'm waiting for desrt to tell me how to do it properly for the tests === psivaa is now known as psivaa-lunch [13:16] larsu, I hope desrt has coffee before looking at IRC, seems there is a stack of questions queued for him today [13:18] seb128: he should move to a better time zone [13:19] we have the best tz and the best cities, no reason to not come ;-) [13:20] hehe :) [13:22] larsu, btw Cimi reviewed on overlay-scrollbar changes and just pinged me on #ubuntu-devel, I asked him to join here/on a channel where you are as well [13:22] larsu, seems like he picked another channel... [13:48] hello hackers!! [13:48] seb128: et tu, n-m? [13:48] desrt, hey, how are you? [13:49] okay [13:49] i got coffee beside me :) [13:49] desrt, should I revert the 2 commits from dan? just 1? just comment the g_error? [13:49] i'd do both [13:49] I did that [13:49] just wanted to check with you before uploading [13:50] though it refuses to build on amd64 in the ppa [13:50] sigh [13:50] FAIL: gwakeup [13:50] FAIL: gwakeup-fallback [13:50] looks like we have the "hud-service eating my RAM" issue back again in 13.10. [13:50] but of course no details in the build log [13:50] popey, talk to pete-woods on #ubuntu-touch [13:50] seb128: that seems highly suspicious [13:50] bug 1253593 [13:50] Launchpad bug 1253593 in hud (Ubuntu) "hud memory usage grows over time" [Undecided,Confirmed] https://launchpad.net/bugs/1253593 [13:50] ok [13:50] popey, wrong channel [13:50] seb128: considering your reverts are in libgobject [13:50] this is on the desktop though ☻ [13:51] popey, you want ted or pete, ted is off for thanksgiving [13:51] not phone. [13:51] seb128: and the gwakeup test doesn't link against that [13:51] desrt, right, so maybe another reason/something with the ppa [13:51] desrt, https://launchpadlibrarian.net/157875681/glib2.0_2.39.1-0ubuntu1_2.39.1-0ubuntu2~build1.diff.gz [13:51] seb128: maybe a new kernel version? wouldn't be the first time this testcase found a kernel bug... [13:51] desrt, can you sanity check? (ignore the "git" file in there) [13:52] +++static inline gboolean [13:52] desrt, well, it's basically reverting those 2 commits [13:52] you said SANITY? ;) [13:52] lol [13:52] desrt, yeah, not a lot to check, that are the 2 upstream commits [13:52] desrt, you saw the pastebin in the backlog (from nm) [13:52] ? [13:53] desrt, can you upstream that one as well? [13:53] no [13:53] got it [13:53] cool [13:53] the good news is that these projects were legit buggy/leaking [13:53] and now we find out about it [13:54] * desrt files a bug for the other danw [14:01] seb128: of course everyone in USA is on their 5-day eatfest/buyfest [14:01] desrt, oh, right [14:01] that includes both danw and dcbw, i guess [14:01] desrt, well, anyway with the revert that can wait [14:01] kinda curious about this gwakeup issue [14:03] the irony builds [14:03] the last person to touch this file.... you guessed it.... danw [14:04] (in fairness, though, dcbw wrote the offending code) [14:04] seems like a running joke [14:04] ;) [14:04] didrocks: the joke started last night [14:04] desrt: yeah, seb128 told me :) [14:04] with your bug report? [14:04] with seb seeing rhythmbox crashes [14:05] yep [14:05] and who wrote the libsoup code [14:05] :) [14:13] larsu, gtk 3.10 built in the ppa \o/ [14:14] seb128: yay! [14:14] everyone: ^ new gtk in the desktop team ppa if you want to give it a try [14:16] exciting! [14:17] I'm going to follow up on the list with that and the list of known issue [14:17] glib with the gobject constructor restriction reverted uploaded to trusty as well [14:17] would be nice if people could grab it/test in half an hour when it's built [14:18] didrocks: ^ that should fix nm on the touch image === psivaa-lunch is now known as psivaa [14:24] bbiab [14:26] bumpy ride [14:26] i bet seb's appetite for a taste of gtk 3.12 has subsided [14:27] desrt: morning! [14:27] larsu: hi :) [14:27] you finally put o-s to bed? [14:27] ah, such fun [14:27] desrt: let me know when you had coffee. I have two things for ya [14:27] larsu: i'm coffeed [14:27] desrt: no... [14:27] I tried hard! [14:27] desrt: https://code.launchpad.net/~larsu/indicator-power/use-gsettings-actions/+merge/197066 [14:28] oh. that. [14:28] i forgot to actually comment on that [14:28] i see lots of red. oddly enough, that means that i'm in a good mood. [14:28] is it okay? [14:29] my mind is blown by how bad this code was before [14:29] what in the hell.... [14:30] desrt: ya, we found it because of the non-stateful actions that had their state set later on [14:30] thanks for putting that check into gio ;) [14:30] which was only possible if using g_object_set()... [14:30] ...which you were ;) [14:30] I? [14:30] the collective 'you' [14:30] who wrote this? [14:30] * larsu is innocent! [14:30] charels [14:31] * desrt shakes fist [14:31] charles_: if you're using my APIs and you ever find yourself having to do something so ugly again, please talk to me about it :) [14:31] well, binding the settings isn't that ugly [14:31] the gvalue shuffling... [14:32] that is, definitely [14:32] i'm actually trying to understand what the old code is doing. don't see it yet. [14:32] okay. got it. [14:32] the binding is directly manipulating the state of the action from the outside [14:32] yes [14:32] you're right... it's not actually _that_ bad [14:33] it's very reasonable if you don't know about GSettingsAction [14:33] and about GAction... [14:33] ha, yeah :( [14:33] the API very much has a 'state comes from within' feel about it [14:34] well, simpleaction goes against that [14:34] and if you're used to using that.... [14:34] ya... strictly speaking, if implementing a simpleaction (as this code is doing) then it's legit to say that the binding is part of the implementation itself [14:34] as it is here... [14:34] * desrt always perceives bindings as something outside of an object [14:35] I agree, it should have triggered the smelly code detector [14:35] my complaint, specifically: GAction::state is readonly and the binding is modifying the state of a GACtion [14:35] but... it's also a GSimpleAction, so hey... [14:35] yeah [14:35] thanks for having a second look [14:35] so why do you keep the action around? [14:36] I don't know [14:36] it's charles' code, I didn't want to mess too much with it [14:36] there's almost nothing that you can meaningfully do with a gsettingsaction beyond adding it to the map [14:36] but he's on tg holiday [14:37] commented [14:37] in summary: i want to see more red :) [14:37] there is more code to be cut, but please let's fix the bug first [14:38] I know what you'll say now. [14:38] "You'll never get around to removing that anyway" [14:38] also: it will take you less than 5 minutes to do what i asked [14:38] and most of those 5 minutes will consist of tapping your 'd' key in a very satisfying way [14:39] well, there are other actions kept around as well [14:39] anyway, I'll have a look of you do me a second favor and have a look at how I install the schema in https://bugzilla.gnome.org/show_bug.cgi?id=711715 [14:39] Gnome bug 711715 in general "gtk object tests: run under local environment" [Normal,New] [14:39] it's causing problems on the builders [14:40] but I didn't want to fix it because you probably have a very specific opinion on that [14:40] * desrt has no idea what he's looking at [14:40] * desrt becomes curious [14:40] i guess this is some fallout from your gtk 3.10 work? [14:40] desrt: yes. Running the tests in the session didn't work [14:41] because schemas were missing if you didn't have 3.10 installed [14:41] ahhhh [14:41] i'm very surprised that gnome-continuous didn't pick that up [14:41] same problem on the builders [14:41] because its using installed tests [14:41] it's [14:41] right. [14:41] probably also because it doesn't do clean rebuilds [14:42] so even if it did 'make check' it would have a system image there [14:42] desrt, glib built on amd64 on the buildders, I'm going to do another ppa upload with VERBOSE=1 just to see [14:42] seb128: blame the kernel!! [14:42] seb128 is back! [14:42] larsu, yeah ;-) [14:42] seb128: good news, giving only GtkPaned a background fixes the theme issues [14:42] damn that colonel [14:42] but I don't know if there are more [14:42] so testing is in order [14:42] larsu, \o/ [14:43] $(GLIB_COMPILE_SCHEMAS) $(top_srcdir)/gtk --targetdir=$(builddir) [14:43] oh man... [14:43] Laney, please test https://launchpad.net/ubuntu/+source/glib2.0/2.39.1-0ubuntu2/+build/5281151 [14:43] Laney, thanks ;-) [14:43] larsu: strictly speaking, this is no longer valid.... [14:43] * seb128 doesn't want to be the one who screwed glib on a friday evening [14:43] seb128: anything in particular? [14:43] desrt: why not? [14:43] what's you issue with it? [14:43] *your [14:43] larsu: gsettings now assumes the xml will be in the same directory as gschemas.compiled, so this will break out-of-tree [14:43] Laney, just make sure rhythmbox & sessions are working on amd64 (I tested on i386) [14:44] ok, sec [14:44] but it only breaks if you call _get_description() or _get_summary() in the testcase [14:44] which i assume you're not [14:44] desrt: so ... --target-dir is now useless? [14:44] Laney, thanks [14:44] larsu: i was going to remove it... that's why i mention it [14:44] i stopped using it from the glib testcases [14:44] maybe i'll keep it around if others use it, though [14:45] no, please remove it [14:45] larsu: as long as you're not looking at summary/description, you're in the clear... [14:45]