[01:18] RAOF, bryce, jasoncwarner_ I just did a dist-upgrade, reboot, and got some odd results [01:18] specifically a dialog with entries such as ... [01:18] none of the selected modes were compatible with the possible modes: [01:18] Trying modes for CRTC 63 [01:18] CRTC 63: trying mode 1680x1050@60Hz with output at 1680x945@60Hz (pass 0) [01:18] CRTC 63: trying mode 1280x1024@75Hz with output at 1680x945@60Hz (pass 0) [01:18] CRTC 63: trying mode 1280x1024@60Hz with output at 1680x945@60Hz (pass 0) [01:18] CRTC 63: trying mode 1152x864@75Hz with output at 1680x945@60Hz (pass 0) [01:18] CRTC 63: trying mode 1024x768@75Hz with output at 1680x945@60Hz (pass 0) [01:19] CRTC 63: trying mode 1024x768@60Hz with output at 1680x945@60Hz (pass 0) [01:19] etc... [01:19] thoughts? [01:20] rickspencer3, got a screenshot of that? [01:20] bryce, yah [01:20] hold on [01:21] http://ubuntuone.com/4NrVvia6dF1BSjHJ08pyxG [01:21] bryce, ^ [01:21] "Could not locate object" [01:21] bryce, try again, it wasn't done syncing [01:22] ok there we go [01:22] hum, mysterious. Can you look at your processes and see what process owns that dialog? [01:22] bryce, er, I closed it [01:22] ah [01:22] I can restart and try it again [01:22] * bryce googles [01:23] bryce, for some reason I seem to recall I used to get 1900 pixels across [01:23] rickspencer3, my guess is that it belongs to gnome-settings-daemon [01:23] but now get 1680 [01:23] hmmmm [01:24] rickspencer3, as a test, you could move aside ~/.config/monitors.xml and relogin and see if the dialog goes away [01:24] ok [01:24] bryce give me 5 mimnutes? [01:25] sure [01:25] I'm getting pinged on another channel :/ [01:25] * bryce grabs new coffee [01:33] hi bryce === SaMOOrai is now known as Samoorai [01:33] rickspencer3, hi [01:34] bryce, I moved that config file out of the way [01:34] rebooted [01:34] and no dialog [01:34] * bryce nods [01:34] rickspencer3, silly gnome [01:34] my feeling that I got gypped out of some screen resolution seems like a fantasy, though [01:34] since my windows seem to be the correct size [01:34] ish [01:35] rickspencer3, just a stale monitor.xml file apparently [01:35] bryce, how does that happen? part of the dist-upgrade? should we not fix that? [01:35] rickspencer3, no idea; maybe seb128 knows a bug report on it [01:36] rickspencer3, if you want to shoot me all your files I can investigate in more depth. [01:37] rickspencer3, dmesg, xrandr, monitors.xml, Xorg.0.log, xorg.conf [01:37] bryce, if I ubuntu-bug xorg will you get the files you need? [01:38] rickspencer3, yep [01:38] ok [01:38] I'll subscribe you when it's donw [01:38] done, even [01:39] rickspencer3, you're on -intel right? [01:39] bryce, correct [01:39] i965, iirc [01:42] rickspencer3, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1138315 [01:42] Launchpad bug 1138315 in gnome-settings-daemon "Could not apply the stored configuration for monitors" [Low,New] [01:42] bryce [01:42] urk, I already logged this bug [01:42] no prob, I can just dupe [01:43] sometimes helpful to have the extra sets of log files [01:44] bryce, bug #1145689 [01:44] Launchpad bug 1145689 in xorg (Ubuntu) "error dialog due to problems monitors.xml file after dist-upgrade" [Undecided,New] https://launchpad.net/bugs/1145689 [01:45] thanks bryce [01:45] rickspencer3, looks like seb's already aware of the bug [01:46] ack [01:46] rickspencer3, oh, also if you still have the monitors.xml can you tack that onto the bug? [01:46] yes [01:47] bryce, done [01:48] rickspencer3, perfect. [01:48] thanks bryce [01:48] ttyt! [01:59] rickspencer3, so looking at all the logs, everything looks kosher on the X end of things. I see this is a little hybrid dell box. By chance have you had it plugged into a different monitor or projector recently? [01:59] hi bryce [01:59] nope, have not changed monitors [01:59] intriguing [02:00] * bryce studies further [02:00] hey bryce I need to step away [02:00] will be back tomorrow for UDS [02:01] rickspencer3, ok cya [02:02] rickspencer3, I'll probably leave the bug to seb128, but will poke through stuff and see if I can find out what caused this [02:06] * Samoorai rebooting entire virtual network aka host reboot.. bbiab (3 vms, 1 host all GRRRR!) [04:10] what's the deal with the i386 builders? [04:10] uploaded 14 hours ago and still waiting? [04:13] desrt: welcome to the world of PPAs, where firefox/chromium dailies screw up the world :) [04:14] except this time it looks like private jobs of some sort that are doing it.. [06:34] How many .au folk are going to be showing up for UDS. [06:34] ? [06:36] g'day mate [06:38] RAOF: Unlikely. It's 10pm - 4am. I just got over jet lag from the sprint :P [06:39] Good morning [06:43] I might make it for the last session, at 6am [07:00] good morning [07:00] Morning didrocks [07:00] I like how lightning talks are still planned in, it's not the same! [07:03] hey duflu [07:15] morning all [07:26] hey dpm [07:26] morning didrocks [08:56] good morning [08:58] hey chrisccoulson [08:58] oh, today is going to be fun [08:58] i have a sad panda this morning [08:58] it's locked up twice already :/ [08:58] hi didrocks [09:03] hey [09:03] * Laney shivers [09:03] cold this morning [09:04] i've not looked outside [09:04] hey Laney [09:04] * chrisccoulson has the curtains closed [09:04] fog [09:04] greyness - you know, the usual [09:04] hey didrocks [09:04] how goes? [09:05] good, thanks. yourself? [09:06] can't complain [09:06] hoping the bike shop will call me today to tell me my new bike is ready to test ride ;-) [09:10] hey desktopers [09:10] hey didrocks chrisccoulson Laney, how are you? [09:10] catching up on my daily -devel backlog :P [09:10] I did some shuffling on the UDS schedule, please check and let me know if there is any conflict or missing session [09:10] hey seb128! [09:11] didrocks, lut ;-) [09:56] bonjour seb128 et didrocks, comment allez-vous? [09:56] hey laney [09:56] pitti: ça va bien, et toi? [09:57] pitti: super que tu ais commenté comment générer la documentation pygi sur g+ :) [09:57] didrocks: je suis trés hereux que le printemps est arrivé! [09:57] I already forgot what the sun looked like [09:57] pitti: ah? le printemps était là hier (16°C, soleil). Aujourd'hui, il est un peu moins présent… :( [09:58] il fait encore froid, mais il fait beau [09:59] didrocks: s/g+/blog/ :) [09:59] didrocks: yeah, I got reminded by the side-thread on u-devel@ about developer APIs [09:59] pitti: trop de sources d'informations :) [09:59] didrocks: en effet.. [10:00] pitti, salut, ca va bien, et toi ? [10:00] pitti, ici il fait beau mais ils ont prévu le retour des nuages demain :-( [10:01] seb128: je suis curieux comment UDS va foctionner aujourd'hui :) [10:01] pitti, j'espère que ca va bien marcher === vrruiz_ is now known as rvr_ [10:34] pitti, hum, do you know about bugs with your recent pygobject update? [10:34] gi/overrides/__init__.py", line 35, in __setitem__ [10:34] raise KeyError('You have tried to modify the registry outside of the overrides module. This is not allowed') [10:34] seb128: not yet; I had it blocked from propagation until all teh autopkgtests ran [10:34] (gedit:16285): libpeas-WARNING **: Error loading plugin 'codecomment' [10:34] pitti, gedit does that to me today [10:34] hm, which plugin do I need for this? [10:35] codecomment I guess :p [10:35] gedit-plugins: /usr/lib/gedit/plugins/codecomment.py [10:35] pitti: did you ask for it to be unblocked? [10:35] Laney: yes, infinity did that [10:36] ah, yeah [10:36] just wondering if it was on request [10:36] seb128: ah, can reproduce [10:36] pitti, great [10:36] pitti, want a bug report? [10:36] yes, please [10:36] pitti, bugzilla or launchpad? [10:37] seb128: as you wish; perhaps LP, I'll forward it then [10:37] ah, I think I know what's wrong [10:39] pitti, https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1146567 [10:39] Launchpad bug 1146567 in pygobject "gedit's "codecomment" raises a KeyError since the recent update" [Undecided,New] [10:39] seb128: merci [10:39] pitti, merci à toi ! ;-) [10:41] seb128: je suis desolé, je vais le corriger maintenant [10:42] pitti, pas de soucis, merci ;-) [10:42] seb128, ping [10:42] ara, hey [10:42] ara, how are you? [10:42] seb128, good, thanks! yourself? [10:42] I guess busy busy :) [10:43] I'm good thanks [10:43] is there any free slots in the client track for this: https://blueprints.launchpad.net/checkbox/+spec/client-1303-new-checkbox-core-plainbox [10:43] yeah, always busy, especially this week with UDS ;-) [10:43] it is a tool both used in the client and the server, so, technically, it could fit both [10:43] maybe in that case is better suited for foundations? [10:44] ara, I can put it in the foundations slot today at 16utc or 18:15 utc [10:44] ara, which one do you prefer? [10:45] 16utc would be best, thanks! [10:47] ara, yw [10:47] ara, hum, is there any way you could move that blueprint to "ubuntu"? [10:47] seb128, we could try. is that important? [10:47] ara, it's against the checkbox product [10:47] ara, the scheduler doesn't list it since it's not an ubuntu spec [10:48] ara, https://blueprints.launchpad.net/checkbox/+spec/client-1303-new-checkbox-core-plainbox/+retarget [10:48] ara, that url should allow you to do it [10:48] seb128, done, thanks! [10:48] ara, thanks you! [11:21] ara, ok, you are on schedule, foundations 1 - 16:00: http://summit.ubuntu.com/uds-1303/2013-03-05/display [11:21] seb128, great, thanks a lot! [11:21] yw ;-) [11:29] Hi people. === hema is now known as Guest60788 [11:30] I am an old user of Ubuntu desktop. [11:30] thougt of using ubuntu 12 now. [11:30] has canonical stopped shipping the CD's ? [11:31] yes [11:31] oh :( sad of that. [11:31] the only way is to download? [11:32] Unless you find some local unofficial distributor, I believe so [11:32] uh... okay... [11:32] thanks Max.. [11:39] seb128: fixed pygobject uploaded === MacSlow is now known as MacSlow|lunch [12:58] pitti, danke === MacSlow|lunch is now known as MacSlow [13:26] so, libcmis breaks horribly on its tests on armhf when compiled with gcc-4.7, so I just tried to make it build on gcc 4.6, which works except that I cant use that as 4.6 is in universe by now and I need libcmis is main. Whats the proper way to proceed? [13:27] can I only file a bug and wait for gcc to get its act together? [13:27] seb128: ^^ [13:28] Sweetshark, open a bug, against gcc-4.7, with the details [13:28] then ping doko, promise him some free beers if needed [13:29] or just build-depends on gcc-4.6, wait for that to show in component mismatch and doko will probably find you :p [13:43] hmm, no doko on IRC ... [13:46] perhaps if you break something he'll appear [13:46] kinda like beetlejuice [13:46] Hey folks. === rickspencer3_ is now known as rickspencer3 [13:52] good morning hackers [13:52] hey desrt [13:52] czajkowski: does https://bugs.launchpad.net/ubuntu/+source/gcc-4.7/+bug/1146903 count? [13:52] Launchpad bug 1146903 in gcc-4.7 "gcc-4.7 causes libcmis FTBFS on armhf, regression against 4.6" [Undecided,New] [13:53] * Sweetshark waves at desrt. [13:53] Sweetshark: as long as you dont break LP today I'm all happy [13:54] czajkowski: ah, we (libreoffice) decided to break lp no more than once a week to give it some time for rest and regroup ... [13:54] if you wake wgrant up, be it on your head :) [13:55] seb128: lots of packages! [13:55] seb128: too bad the builders are so slow lately :( [13:55] seb128: good morning, btw :) [13:56] desrt, hey, yeah, I noticed some builder backlog recently as well [13:57] seb128: i checked last night after coming back home and before sleeping.... some jobs you submitted were still waiting after 14 hours [13:58] i386 seems particularly bad [13:58] https://launchpad.net/builders [13:58] 28 builders working for i386 [13:58] sounds like I should throw some libreoffice over the fence. [13:58] not sure how many we had yesterday [13:58] but it seems like it's catching up [13:59] Sweetshark: step away from the button, son [14:00] yeah, unity delay wasn't that bad this morning [14:00] maybe just sticking to the lets-bury-the-builders-for-feature-freeze tradition ? [14:00] finished late, but was ok [14:00] seb128: so there are 7 packages here [14:00] there was supposed to be 8 [14:00] but i can't remember what the 8th one was :) [14:00] which one is missing? [14:00] * desrt counted them out to larsu last night... [14:01] larsu: systemd-shim, systemd, g-s-d, g-c-c, indicator-datetime, polkit-policies, ubuntu-system-service [14:01] what is missing? [14:02] There's now link from uds.ubuntu.com to http://summit.ubuntu.com ... [14:03] seb128: which buildds are cauing you pain ? [14:03] oh well. maybe i counted wrong [14:03] happy UDS, everyone! [14:03] happy UDS desrt :) [14:04] the audio compression hurts :( [14:04] one benefit of online sessions ... I can drink beer/cider _during_ the sessions! [14:04] BigWhale: you'll find straight gin to be more effective for some sessions [14:05] default web browser selection, for example [14:05] yeah for Xorg/Mir session [14:05] :D [14:06] seb128: wow, he pronounced your name right! I can't do that. [14:06] (plenary) [14:06] jcastro, no he didn't :p [14:07] jcastro, you don't pronounce the "r" :p [14:07] oh, well it sounded way better than when I try it [14:07] there's a plenary? [14:08] kenvandine: http://summit.ubuntu.com/uds-1303/meeting/21601/introduction/ [14:08] have you click on the link in the schedule? :p [14:08] no mterry has well, skipping plenary! :) [14:08] as* [14:08] charles: hey. this pthread linking issue is causing jenkins to reject my branch [14:08] plz fix :) [14:08] i didn't see that anywhere... === tkamppeter_ is now known as tkamppeter [14:17] etherpad seems to not really scale, isn't it? [14:17] \o/ gobby [14:17] back to gobby ! [14:17] hah [14:17] :) [14:17] i logged into gobby.ubuntu.com the other day, didn't realise it was still up [14:24] seb128: can you take a look at these when convenient? https://code.launchpad.net/~attente/gtk/no-menu-proxy/+merge/151568 and https://code.launchpad.net/~attente/gtk/gtk2-no-menu-proxy/+merge/151619 [14:25] it seemed like the desktop-ppa's gtks still had the menu proxy patch [14:26] attente, hey, will do, but maybe not today, we have UDS today (started half an hour ago) [14:26] attente, hey, we had those patches in the ppa, but those version got deprecated by new uploads to raring [14:26] like indicator-appmenu got a landing with the hud splitted [14:26] seb128: ah.. no wonder [14:26] am I the only one to see a red bar progressing where we have the duration on youtube normally? [14:26] we need to rebase on that [14:27] didrocks: mine just says En direct, no red bar progress (it's at the end) [14:27] didrocks, I see a red bar but not progressing [14:27] didrocks: i see the red bar [14:28] seb128: it was at the beginning at the start of the show [14:28] * didrocks wonders what will happen when (soon), the red bar will reach the end [14:28] haha [14:28] perhaps there is some buffering and you can pause, skip ahead, etc? [14:28] ie. maube you're not watching direct right now? [14:28] maybe, I just hope this won't cut at some point [14:28] attente, can you rebase you indicator-appmenu branch on the current trunk? will make easier to get updates in the ppa again [14:29] attente, I will try to get back the gtk patches back in there this week as well [14:29] attente: lp:indicator-appmenu, I'll review as seen as I see a merge request [14:29] argh, I can't type today [14:29] seb128, cyphermox sure [14:30] attente, thanks [14:30] attente, how is the testing work going? things will be easier once we can land the new source in the archive [14:31] seb128: i only managed to write a few tests combining autopilot and atspi, i got a bit blocked because one of the tests is strangely failing [14:32] attente, the autopilot tests? [14:33] didrocks, cyphermox: how much testing for the new menus do you require for the thing to land? [14:33] alesage, yes [14:33] seb128: attente: tests included in the merge for new stuff, tests passing [14:33] seb128: I would say that we get basic coverage: ensuring the menu is exported, opening a menu, acting on something, ensuring it's act [14:33] alesage: for one of the tests, the behaviour differs when i do it manually vs using autopilot [14:34] I mean, all the autopilot stuff, to go along with any new tests to verify the new functionality [14:34] cyphermox, didrocks: thanks [14:34] cyphermox: thanks [14:35] attente, is this in the unity-gtk-module trunk? [14:35] alesage: yes [14:35] attente ok [14:36] alesage, the failing test is the tests.GeditTestCase.test_file_new, but i commented out the assertions that cause it to fail [14:36] attente ok I'll have a look [14:36] thanks === m_conley_away is now known as m_conley [15:27] jbicha: heya! what's the gdm fallback session? it's unrelated to the gnome-fallback-session, right? [15:27] ah craperola === alex_abreu is now known as alex-abreu [15:56] attente: hey. why didn't you land the indicator-appmenu changes yet? [15:56] the PPA version of the package keeps falling behind... [15:58] desrt: working on it... [15:58] attente: looks like your merge proposal includes a copy of hudmenumodelcollector.c ? [16:00] desrt: yes [16:00] is that on purpose? [16:01] i'm not really following what you mean... [16:01] the diff at the bottom of the page here: https://code.launchpad.net/~attente/indicator-appmenu/indicator-appmenu/+merge/143531 [16:02] vs. current trunk it adds back a copy of hudmenumodelcollector.c [16:02] i think that's probably a mistake [16:03] i think your branch ended up on both sides of the hud-removal work... [16:03] i'd almost just start over again.... something has gone very badly here [16:03] yeah... you're right [16:04] i did the merge and it kept the old file [16:04] just take the good parts of the diff (ie: the actual work, plus the tests) and start over [16:04] push a new branch and merge-request it [16:04] bzr has made a complete mess of this branch... i fear to imagine what might happen if you tried to merge this into trunk at this point [16:06] sure, thanks desrt [16:07] attente: push it into the same merge request though, with `bzr push --overwrite` [16:10] seb128: maybe we could get an updated gtk3.7 in the PPA dropping the menu proxy patch? === s9iper1_ is now known as s9iper1 [16:14] seb128: or please add me to the desktop team :) [16:27] jbicha: hey :) [16:31] highvoltage: aloha [16:37] desrt, I plan to get the gtk2/gtk3/indicator-appmenu updated in the ppa again soon, I was waiting on the indicator-appmenu patch to be rebased and for the new gtk to be out [16:38] bonus point if jbicha updates gtk2 first in raring [16:38] ;-) [16:38] last time he overwrote my ppa version the new day by uploading the new version, rebased on debian, in raring [16:40] seb128: I saw there was another gtk2 update ;) [16:40] jbicha, right, want to do it? ;-) [16:42] seb128: can you add me to desktop team? [16:43] desrt, no [16:43] ok [16:43] desrt, that team gives upload rights for GNOME to the archive [16:43] desrt, it needs +1 from 3 members and official ack from the DBM [16:44] desrt, maybe you can use your ppa? I can do ppa copies from launchpad so it would be easier to move them to the desktop ppa from yours [16:45] seb128: not this time, I'm a bit busy this week & I don't need it for gnome-themes-standard like happened last time [16:45] like it would be one click to copy your ppa over [16:45] seb128: i don't really have anything specific i want to do right now if you have a plan for gtk... [16:45] jbicha, ok [16:45] i just wanted to stop bothering you in the future [16:45] desrt, if you are interested in packaging and do enough you can join the team, but I doubt that's the case [16:45] desrt, just use your ppa and ping me for copies [16:46] k [16:46] copy is a click away [16:57] seb128: well, copy after looking over a *verrrryyyyy* long list of ppa owners :) [16:57] Laney, how was the rolling release session? any outcome? [16:58] yeah, I followed the end as well, but I don't see any outcome :) [16:58] didrocks, right, still better than doing the packaging and upload :p [16:58] There was a reasonable level of support for keeping Raring but no decision [16:58] based on the fact that this is what was planned for [16:58] seb128: if you compare lazyness-wise, right ;) [16:58] Laney, with Canonical resources allocated for security and SRUs? [16:58] the OEM (System 76) were pretty against that as a lot of their users like to get new stuff [16:58] seb128: possibly, yeah [16:59] k [16:59] interesting [16:59] as in planning properly to do this rolilng thing afterwards [16:59] * seb128 hates doing SRUs for nonLTS versions [16:59] * seb128 wants to stop that [17:00] I got fed up with quantal SRUs, that's eating days and a good part doesn't get verified at the end [17:00] well I guess we could find a middle ground and we low on SRUs [17:00] just do the security work [17:01] right [17:04] It's more of a doing what we promised to do and what people (including some OEMs apparently) have based their time/business on [17:05] even if it's not working we need to give the right amount of time for people to adjust [17:06] I'm fine doing a release, as long as it's not a maintenance time sink [17:06] but well, we never gave garanties on the number of SRUs we do [17:06] indeed [17:06] we didn't do the whole gnome point release for Quantal for example [17:06] so there's already some precedent there [17:06] right [17:06] we tend to not do it in nonLTS cycles for a while [17:07] we don't have the resources for it [17:07] yeah [17:07] we'll see [17:17] seb128: can you CC me if you email people about the maliit stuff? [17:17] AFAIK the patches went upstream [17:18] Laney, ok, will do, thanks [17:18] as in murray pushed them all so there's no fork any more [17:18] well, once they release [17:24] Laney, what about the UI? nemo was it? [17:24] I think they use nemo currently but the target is the maliit keyboard [17:24] nemo is the N9 one [17:24] http://www.murrayc.com/permalink/2013/03/04/maliit-keyboard-improvements/ [17:25] ok [17:25] is any of those qt5? [17:25] yeah nemo is [17:25] err, they both are* [17:25] ok [17:25] in trunk, not raring AFAIK [17:27] Laney, I see, thanks for the blogpost link and the details ;) [17:27] np [17:28] http://lists.maliit.org/pipermail/maliit-announce-maliit.org/2013-February/000026.html "Our main focus will be the master branch where we will drop support for Qt 4 and only focus on Qt 5 quite soon. This branch is intended for anybody who wants or needs to keep using Maliit with Qt 4. " [18:56] seb128, qml-friends is in sourceNEW... when you get a chance for a review :) [18:56]