[00:08] <asac> white: can you reproduce that anywhere?
[00:09] <asac> the security focus thing only mentions IE
[00:09] <asac> oh below there is
[00:09] <asac> not sure what it means :/
[00:12] <asac> white: if you can make something up for testing, feel free to
[00:12] <asac> ,9
[01:01] <white> asac: you're sure MFSA 2008-53 doesn't affect xulrunner?
[08:50] <asac> white: yes. that and https://bugzilla.mozilla.org/show_bug.cgi?id=459906#c38
[08:51] <asac> hmm ... without bugzilla account i cant show you ... but not important in this case. its sessionstore which is a browser/ feature (like i said above ;))
[08:54] <BUGabundo> good morning asac
[08:56] <asac> BUGabundo: hey
[08:57] <asac> white: even more its nothing 1.8.0 branch actually has ;)
[08:57] <asac> (session restore was invented for ffox 2)
[11:26] <asac> [reed]: trick needed: what kind of search flags do i have to set to see all bugs that have approval1.8.1.next* ?
[11:26] <asac> [reed]: (e.g. i want ...next? and ..next+) ;)
[12:22] <asac> [reed]: i think i have it. thanks
[12:32] <asac> @time
[14:53] <fta2> asac, how come my url has not be shortened in identi.ca? I used the web site directly.
[14:54] <fta2> and i selected one of the free services
[14:59] <asac> fta2: the website only shortens when there is a need to shorten ;)
[14:59] <asac> e.g. when your line would exceed 140
[16:18] <fta2> oh
[16:38] <fta2> ff with an authenticated proxy is a nightmare. zillions of popups asking for a password *and* providing no reason
[16:39] <asac> fta2: at startup right?
[16:39] <asac> e.g. multiple tabs fighting for a proxy authentication ;)?
[16:40] <fta2> yep, and when each addon wants to check for update
[16:41] <asac> there is a bug for that ... i am sure ,)
[16:41] <fta2> this is under xp but i guess it's the same on all arches
[16:41] <asac> its even linked from launchpad ;9
[16:41] <asac> yes its known
[16:41] <asac> i always thought that the "no reason" thing was due to our xul split
[16:41] <asac> but seems its not
[16:41] <asac> makes me happy
[16:42] <asac> so ... transition done
[16:42] <asac> lets see how many build failures will fall down on me now :(
[16:43] <fta2> how could we do the python xpcom transition? the current package comes from xul 1.8
[16:43] <asac> fta2: does anyone depend on python xpcom?
[16:43] <fta2> i need one from 1.9 or 1.9.1 for openkomodo
[16:44] <asac> what is python xpcom?
[16:44] <asac> the binding so you can run python components in-process of firefox/xulrunner?
[16:44] <asac> i think so, right?
[16:44] <fta2> i guess so
[16:44] <asac> fta2: atm it doesnt work, right?
[16:45] <asac> e.g. we still get this python error in error console?
[16:45] <fta2> we disabled it in 1.9bsomething
[16:45] <asac> fta2: well its still in there her:
[16:45] <fta2> well, maybe not
[16:45] <asac> /usr/lib/xulrunner-<IP_ADDRESS>/components/libpyloader.so
[16:45] <asac> /usr/lib/xulrunner-<IP_ADDRESS>/components/pyabout.py
[16:46] <asac> /usr/lib/xulrunner-<IP_ADDRESS>/libpyxpcom.so
[16:46] <asac> ... anyway. i think the problem is that libpyxpcom.so isnt found
[16:46] <asac> so we need a glue fix here ... i guess
[16:46] <asac> fta2: does the py xpcom code actually still exist in trunk?
[16:50] <asac> if so, i know what to do
[17:03] <fta2> please fix it in 1.9.1 first, then I'll merge in 1.9.2
[17:03] <fta2> i have to run
[17:43] <plun> hello.. fta or asac around ?
[17:45] <plun> super breakage with a clean install
[17:45] <plun> nm-applet: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory
[17:45] <plun> FF3.0 broken... and a bunch of other packages..
[17:46] <plun> FF3.1 Ok but libplds4  ???  what package does it come from ?
[17:52] <plun> Well... found it and its Xulrunner as I can see...
[17:52] <plun> a mess...
[17:52] <plun> http://ubuntu.pastebin.com/m16a5b2f4
[19:45] <Lns> fta: Hey, LaserJock wanted me to ping you re: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/269188 and a possible SRU for Hardy, would that be possible?
[19:46] <fta> asac, ^^ from plun, i guess you need to rebuild xul and nm-applet
[19:46] <fta> Lns, iirc, it's just nss, not firefox, right?
[19:46] <Lns> fta: I guess so - nspr
[19:47] <fta> yep, nspr, not nss.
[19:47] <Lns> I just saw the comment from "LP Janitor" that it was fixed in jaunty
[19:47] <Lns> I cant test it as all my sites are hardy
[19:47] <fta> Lns, could you confirmed that it fixes the bug in jaunty before we start an SRU for hardy?
[19:48] <fta> argh
[19:48] <fta> not even a VM ?
[19:48] <Lns> no :( but im sure i can call on someone(s) to test
[19:50] <fta> there's also my ppa, you can just dl the nspr debs for hardy, they have the fix
[19:51] <Lns> oh!
[19:52] <Lns> fta: url me :)
[19:52] <Lns> fta: if I used the packages from your PPA on Hardy and tested, would that be enough for an SRU request?
[19:55] <fta> yes
[19:55]  * fta hopes asac will not complain :P
[19:56] <Lns> well i'll call on the LTSP/Edubuntu people I know to test as well so we dont do anything without verifying completely
[20:00] <Lns> Im going to reboot myself and then upgrade, i'll bb in a bit
[20:11] <fta> Lns, don't use my ppa completely, just my nspr so we know for sure it's it.
[20:12] <Lns> fta: ugh.. ok this is what i just updated: http://logicalnetworking.net/other/nsprupdate.png
[20:12] <Lns> good thing i got a screenie ;)
[20:13] <Lns> is that ok, or should i downgrade anything?
[20:14] <fta> you got just that?
[20:14] <fta> dpkg -l | grep fta
[20:14] <fta> (i sign all my packages with ~ftaX)
[20:15] <Lns> libnspr4-0d libnss3-0d libnss3-1d libpng12-0 pastebinit is what i upgraded to just now
[20:16] <fta> please downgrade at least nss.  png and pastebinit are not important as they are unrelated
[20:18] <Lns> ok
[20:31] <Lns> fta: ok i think im good now, downgraded libnss stuff to <IP_ADDRESS>-0ubuntu<IP_ADDRESS>
[20:31] <Lns> but libnspr4-0d and libnspr4-dev are your ppa versions
[20:32] <fta> good
[20:33] <Lns> and just locked libnss3-0d (and 1d) versions. i think thats it right?
[20:34] <fta> it is
[20:34] <Lns> awesome, thanks fta - mucho appreciado!
[20:37] <Lns> hrm..locking versions in synaptic doesnt reflect in apt-get :(
[20:39] <Lns> fta, can i safely remove your PPA after upgrading nspr?
[20:39] <Lns> i cant recall some of the more involved apt situations
[20:43] <fta> yep, no problem.
[20:43] <Lns> fta: thx
[21:47] <Lns> fta: FYI, I've posted this wiki to the LTSP lists so people can test. Im hoping to get a lot of tests done and get back to you for an SRU asap. http://lns.wikidot.com/nsprupdate
[21:48] <fta> Lns, ok
[22:32] <BUGabundo> fta asac my FF3.1 lost most/all file asociation!
[22:36] <asac> Lns: what is your plan?
[22:39] <asac> fta: whats the issue for plun?
[22:47] <BUGabundo> asac: ping
[22:48] <BUGabundo> does alt+NUM work for you with FF?
 hello.. fta or asac around ?
 super breakage with a clean install
 nm-applet: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory
 FF3.0 broken... and a bunch of other packages..
 FF3.1 Ok but libplds4  ???  what package does it come from ?
 Well... found it and its Xulrunner as I can see...
 a mess...
 http://ubuntu.pastebin.com/m16a5b2f4
[22:49] <fta> asac, ^^
[22:49] <asac> @time
[22:50] <asac> @time
[22:50] <BUGabundo> asac: still having trouble with your ISP
[22:50] <asac> yeah ;)
[22:50] <asac> obviously
[22:53] <asac> fta: what was the problem above?
[22:54] <fta> asac, donno. you have all i have.
[22:54] <asac> fta: sure but you lead the discussion ;)
[22:54] <asac> hehe
[22:54] <asac> ok i see ... so probably the entropy fix of nspr
[22:55] <BUGabundo> mine is pidgin! keeps crashing
[22:55] <fta> $ ldd /usr/lib/xulrunner-<IP_ADDRESS>/xulrunner-bin | grep plds4
[22:55] <fta>         libplds4.so.0d => /usr/lib/libplds4.so.0d (0xb7f37000)
[22:55] <fta> asac, .0d is still there?
[22:55] <asac> fta: plun? i dont know what issues he has
[22:55] <asac> fta: for me it sounds a bit like he has rotten old things
[22:56] <fta> fta@ix:~ $ ldd /usr/lib/xulrunner-<IP_ADDRESS>/xulrunner-bin | grep plds4
[22:56] <fta>         libplds4.so.0d => /usr/lib/libplds4.so.0d (0xb802d000)
[22:56] <fta> that's mine
[22:56] <asac> true
[22:56] <asac> and i have:
[22:56] <asac> $ ls -l /usr/lib/libplds4.so.0d
[22:56] <asac> lrwxrwxrwx 1 root root 11 2009-01-11 13:59 /usr/lib/libplds4.so.0d -> libplds4.so
[22:56] <asac> after the transition
[22:57] <fta> oh, right
[22:57] <asac> the relinking is done in maintainer scripts
[22:57] <asac> maybe that failed for him?
[22:57] <asac> oh
[22:57] <asac> i think he tried to upgrade
[22:57] <asac> that failed ... and the upgrade-abort case left him with bad links maybe?
[22:57] <fta> let's see. i bet he started a thread
[22:57] <fta> he said "super breakage with a clean install" btw
[22:58] <asac> http://ubuntu.pastebin.com/m16a5b2f4
[22:58] <asac> thats his error message
[22:58] <asac> you see what the root cause there is?
[22:58] <asac> yeah
[22:58] <asac> clean install
[22:58] <asac> how?
[22:58] <asac> ;)
[22:59] <asac> the error is an upgrade error i guess
[23:03] <Lns> asac: my plan is to test fta's PPA nspr package for Hardy to see if my issue with >3 LTSP terminals launching a FF3 session doesnt lag due to lack of entropy
[23:04] <asac> Lns: ok. let us know
[23:04] <Lns> asac: will do for sure
[23:05] <asac> fta: why is there no single word about where the random thing was fixed? was that an upstrewam commit?
[23:06] <fta> asac, it's in changelog, but it was indeed committed upstream, so no tweak in our packaging for that
[23:06] <asac> Lns:  you dont need to visit -testing to coordinate an SUR
[23:06] <asac> you need to go through us ;)
[23:06] <asac> anyway, if that package fixes it for you we probably need to do a backport of the patch
[23:07] <asac> fta: right. i meant "why is there no single word in changelog about the where" ;)
[23:07] <asac> fixed upstream: or something would have been nice ;)
[23:07] <asac> but all fine
[23:07] <asac> the bug has the upstream link
[23:07] <Lns> asac: ok, i know where you live (on irc) ;)
[23:08] <asac> Lns: if you drop a confirm comment in bug and ask for hardy SRU i will probably see and do ti
[23:08] <asac> e.g. nominate, backport, release
[23:08] <fta> asac, it's the topmost entry, i thought it was obvious
[23:09] <Lns> asac: ok, cool. I'll do that after getting at least 2 hardy-based confirmations from either my own sites or me+other LTSPers
[23:09] <asac> fta: sure
[23:09] <asac> Lns: thanks
[23:10] <Lns> asac: np, thank you guys for the fix(es) :) much appreciated by all of us LTSP net admins
[23:12] <asac> fta: found any thread from plun? you think he will come back?
[23:12] <fta> nope, none
[23:12] <fta> i guess he'll come back
[23:12] <asac> hehe ;)
[23:13] <asac> not sure ... maybe he is one of those that just reinstall ;)
[23:13] <asac> #
[23:13] <asac> Setting up xulrunner-1.9 (<IP_ADDRESS>+nobinonly-0ubuntu1) ...
[23:13] <asac> #
[23:13] <asac> /usr/lib/xulrunner-<IP_ADDRESS>/xulrunner-bin: error while loading shared libraries: libplds4.so.0d: cannot open shared object file: No such file or directory
[23:14] <asac> #
[23:14] <asac> dpkg: error processing xulrunner-1.9 (--configure):
[23:14] <asac> fta: are we running anything in postinst?
[23:15] <asac> hmm. --gre-version
[23:15] <asac> fta: you really think that --gre-version is a good thing to do?
[23:16] <fta> yes, works well
[23:16] <fta> whhat is the problem?
[23:16] <asac> not sure
[23:16] <asac> have the feeling that postinst happens after links have been removed, but before they have been reinstantiated?
[23:17] <fta> lol
[23:17] <fta> did I do that?
[23:17] <fta> --gre-version is not meant to be used in the xul package
[23:17] <asac> fta: yes
[23:17] <fta> it's for pkgs depending on xul
[23:17] <asac> you use it there
[23:17] <fta> damn
[23:17] <asac> fta: but even on higher packages it could happen i think
[23:18] <asac> maybe its the way i reshuffle stuff
[23:18] <asac> i do half in preinst ... the other half in postinst
[23:18] <fta> well, at postinst, xul should already work
[23:19] <fta> no one complained with 1.9.1/2, it's the same code
[23:19] <asac> fta: not if nspr postinst is run after it i think
[23:19] <asac> hmm
[23:19] <asac> right
[23:19] <asac> it should
[23:20] <asac> preinst moves stuff away
[23:20] <asac> then unpack happens and all should be fine
[23:20] <asac> only then .postinst stuff is called
[23:21] <asac> fta: ok ... so postinst.in should get XUL_VERSION=@XUL_BRANCH@ i guess
[23:21] <asac> (regardless of whether thats the issue at all)
[23:21] <asac> fta: oh.
[23:21] <fta> postinst.in of what ? xul ?
[23:21] <asac> the --gre-version is in debian/xulrunner-1.9-gnome-support.postinst
[23:21] <asac> also in debian/xulrunner-1.9.postinst.in
[23:24] <asac> so the transition catched two bogus packages
[23:24] <asac> seahorse-plugins and epiphany-extensions failed everywhere
[23:25] <asac> hmm
[23:25] <asac> http://launchpadlibrarian.net/21134821/buildlog_ubuntu-jaunty-lpia.epiphany-extensions_2.24.1-0ubuntu2_FAILEDTOBUILD.txt.gz
[23:25] <asac> epiphany-browser-dev: Depends: epiphany-gecko (>= 2.24.1-1ubuntu4) but it is not going to be installed
[23:25] <asac> why isnt that dependency wait?
[23:28] <asac> probably a soyuz bug... given back to builders
[23:30] <Lns> asac: fta: !!! https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/269188/comments/18 =) =) =)
[23:31] <Lns> That is soooo awesome =)
[23:31] <fta> excellent
[23:33] <asac> targetted bug
[23:34] <Lns> thanks asac
[23:38] <asac> fta: does ~fta PPA already have native notifications?
[23:38] <asac> for 1.9.2
[23:38] <fta> hm, no
[23:39] <fta> next batch
[23:39] <asac> k
[23:39] <fta> i do that ~ twice a week
[23:39] <asac> yeah. thought you already did it
[23:40] <asac> (thats why)
[23:48] <fta> upgrading to oo3
[23:49] <asac> yeah me too
[23:49] <fta> 6.8Mb/s
[23:49] <asac> fta: maybe you could just do a bzr bd --builder='debuild -S -sd' on current head and push it ;)?
[23:49] <fta> i hope it will be faster soon, i just signed for an upgrade to 18Mbps
[23:49] <asac> hehe
[23:50] <asac> but arent 6.8M/s  already more than 24?
[23:50] <fta> asac, if you want it that hard, i can just push it, it's all automatic
[23:50] <fta> Mbps
[23:50]  * asac is brave
[23:51] <fta> Mbit/s not MByte/s
[23:51] <asac> so ooo 3 looks exactly like 2.4 for me ;)
[23:51] <asac> oh there is a zoom handle
[23:51] <asac> thats nice
[23:52] <asac> but has visual glitches ;)
[23:52] <Lns> darn, i was hoping they'd implement the ribbon bar =p~
[23:52] <asac> maybe they have
[23:52] <asac> ;)
[23:52] <asac> me looking at ooo is similar to my mom looking at ubuntu feisty vs. hardy ... "oh the background is different" ;)
[23:53] <Lns> haha
[23:53] <fta> asac, did you test that your libnotify stuff at least builds ?
[23:53] <Lns> i love that about so many oss projects..even major revisions stick to their UI roots, which is really nice for the user
[23:54] <Lns> Ok, i'm off to test out the nspr fix - wish me luck!
[23:55] <fta> well, still as ugly as before
[23:57] <asac> fta: yes
[23:57] <asac> fta: just push
[23:57] <asac> fta: the code is already in current snapshot
[23:57] <asac> just new packaging required
[23:57] <asac> fta: i tested that it builds and that it works if -gnome-support is installed and that it falls back to "normal" when its not installed


[09:10] <royaflash> salam dostan
[09:12] <royaflash> kasy darmorede file ~/.profile chizi midone ?
[11:11] <marandi> salam bache ha , in jaee ke azash service migiram open vpn ro ra endakhte faghat hich file ee baraye config connection o authentication o injoor chiza nadade , rahe hali hast baraye config e client ?!
[11:30] <marandi> agha bikhiale openvpn shodim yeki komak kone in https ro run konam :( !
[13:14] <ubuntu1> salaam
[13:14] <ubuntu1> in error yani chi?
[13:14] <ubuntu1> dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
[13:18] <ubuntu1> ?
[13:20] <melissa12> ubuntu1: mikhasti chizi ro install koni ke in erroro dad?
[13:20] <ubuntu1> bale
[13:21] <melissa12> sudo dpkg --configure -a   ro bezan
[13:21] <melissa12> badesh apt-get install kon
[13:21] <ubuntu1> zadam , in chi kaar mikone daghighan?
[13:23] <kouhyar> az koja befahmam moshakhsat matherboardam chiye?
[13:25] <melissa12> ubuntu1: in command yani to hameye packagaye jadideto ba dpkg confugure koni
[13:34] <ubuntu1> man DC boodam
 age kaci javaab nadade
[13:34] <ubuntu1> man fek konam
[13:35] <ubuntu1> baaa nasbe hardinfo mitoonid befahmid
[13:35] <ubuntu1>   <kouhyar>  sudo apt-get  install hardinfo
[13:43] <melissa12> kouhyar: dmidecode ham momkene be dardet bokhore.
[13:56] <kouhyar> be nazareton kodom ok tare ono anjam bedam?
[14:05] <ubuntu1> cpu-g am be soorate geraphici ye etelaati az motherboard mide
[14:05] <ubuntu1> sudo add-apt-repository ppa:cpug-devs/ppa  Then update and install via 2 commands:  sudo apt-get update  sudo apt-get install cpu-g
[14:06] <kouhyar> hardinfo ino nasb kardam kodom damet garm bebinam ba in mitonam bebinam chiye moshakhsatesh
[14:07] <kouhyar> mikham bius amo updeat konam
[14:08] <kouhyar> moshkelam ine ke vagti restart ya laptabamo khamosh roshan mikonam ubuntu bala nemiyad
[14:09] <kouhyar> hich erroriyam nemide man fek konam az bius ya hardam bashe
[14:11] <kouhyar> dostan ke gerftan moshkelamo dar in mored etlaati daran mamnun misham komakam konan
[14:14] <ubuntu1> linuxet roo vm nasbe ?
[14:16] <kouhyar_> vm chiye dg?
[14:17] <kouhyar_> nemidonam
[14:18] <ubuntu1> hichi virtual machine
[14:20] <kouhyar_> na man partishen bandi ke kardam ye partishene joda bara vindows 8 doros kardam yekiyam bara ubuntu
[14:21] <kouhyar_> yani 2ta system amel daram
[14:23] <kouhyar_> motasefane ba windows ham hamin moshkel bazi vagta pish miyad ke system bala nemiyad
[19:40] <saaber> درود
[19:40] <philipballew> hello Ubuntu people!
[19:41] <saaber> بات جدیده؟
[19:41] <saaber> !ubuntu
[19:42] <dingdangdong> philipballew: Hello Ubuntu guy!
[19:43] <philipballew> dingdangdong, whats up!
[19:44] <philipballew> greetings saaber as well
[19:44] <saaber> درود ما چی کم از هلو داشت!
[19:44] <philipballew> How is life today wherever you are?
[19:45] <saaber> philipballew: Hello mister :)
[19:46] <philipballew> saaber, I do not speak much farsi. Sorry. But I figured I should join here and make more Ubuntu friends.
[19:47] <saaber> philipballew: i'm glad you are here, you can count on these guys,  they are very friendly! my english is super bad :D
[19:48] <philipballew> saaber, I forgive you. So where do you live?
[19:50] <saaber> philipballew: I live on Earth at present :)
[19:51] <philipballew> saaber, I see. I am currently trying to escape Earth. Do you know how?
[19:52] <saaber> philipballew: no but i try to find a way!
[19:52] <philipballew> saaber, If you are ever in California, come and say hello
[19:53] <saaber> philipballew: oh that's far far away from me!
[19:53] <philipballew> saaber, where on earth are you then?
[19:55] <saaber> philipballew: Tehran my friend :)
[19:56] <dingdangdong> philipballew: wassup in Ca?
[19:56] <philipballew> saaber, oh cool! I have never been there. I'd love to go one day.
[19:57] <philipballew> dingdangdong, Life is good.It is sunny and warm. How is life wherever you are?
[19:58] <dingdangdong> philipballew: says hello
[19:58] <dingdangdong> philipballew: not sunny though, here being late at night
[19:58] <philipballew> dingdangdong, yes. Hello! did you to see my post on the planet today?
[19:59] <philipballew> You should join the fun dingdangdong
[19:59] <dingdangdong> philipballew: mm, nope. but I promise I will, only if you provide us, the ubuntu.ir users with a link! ;)
[19:59] <philipballew> http://philipballew.wordpress.com/2013/04/03/showcase-the-diversity-of-the-ubuntu-community/
[19:59] <philipballew> dingdangdong, ^
[20:04] <philipballew> dingdangdong, Does that seem like a good idea?
[20:04] <dingdangdong> philipballew: yeah good one. only if other ubuntu users are not as lazy as myself.
[20:05] <philipballew> dingdangdong, exactly. I need to find some people who want to help out.
[20:07] <philipballew> dingdangdong, If you do it, I will send one back though.
[20:09] <dingdangdong> philipballew: lol it's not about that
[20:09] <dingdangdong> philipballew: but the best thing next would be what Jan has commented on your blog
[20:09] <dingdangdong> philipballew: letting people know. I'm sure there are many users who would willingly participate
[20:10] <philipballew> dingdangdong, yeah,I sent out a link to the Loco Contacts and told them to send off to there loco's
[20:10] <dingdangdong> philipballew: also, if you may  send a post card back , do mention it in your post. could work as an incentive ;)
[20:11] <philipballew> dingdangdong, good point. Assuming I do not get so many I can not afford to send some back, I would love to send more back.


[08:08] <tortik> Hi all. I'm getting updates via ubuntu customization kit for a fresh-installed lubuntu 12.04. So 3 months ago I get ~150mb updates but now only ~73mb. Is it possible or I done something wrong?  I do the same steps always. UCK unpacks OS, run console and I write 'apt-get upgrade' then I get packages from the cache...
[08:49] <testman> Hi. I installed "quadrapassel" from repo on fully updated x86 Lubuntu, but it wont start. Says it got X Window error "BADGlxContext". Please help.
[08:58] <testman> Anyone?
[09:39] <testman> Anyone even here?
[11:46] <BWMerlin> Is it possible to fully run wayland under/on Lubuntu
[13:53] <Viper187> morning
[13:54] <Viper187> I just built a new machine and was planning to install lubuntu 64-bit. Problem is I get no reposnse from keyboard or mouse beyond the text boot menu where you choose whether to install or test. I tried both. Same thing.
[13:54] <Viper187> I tried the Ubuntu 10.04 disc though, and it works fine
[14:16] <holstein> Viper187: interesting
[14:16] <holstein> Viper187: USB devices?
[14:17] <Viper187> yes
[14:18] <holstein> Viper187: do other USB devices fail?
[14:18] <Viper187> Thos eare th eonly usb devices connected. They're working fine in the copy of 10.04 I just installed
[14:19] <holstein> Viper187: i understaing that 10.04 is supporting your devices.. do other USB devices fail in 12.04 or 12.10?
[14:19] <Viper187> both
[14:19] <holstein> Viper187: what i would want to determine is, what exactly is not supported
[14:20] <holstein> Viper187: sounds to me like what you are describing is that the support for your USB controller has been dropped from the kernel
[14:20] <Viper187> only USB devices I use are keyboard and mouse. I tried both lubuntu discs. 12.04 and 12.10, both 64-bit
[14:20] <Viper187> interesting
[14:20] <holstein> Viper187: i would try other USB devices to be certain
[14:20] <holstein> Viper187: USB sticks.. anything
[14:21] <holstein> Viper187: then, i would see if there are backports that support your hardware which will add modules to the 12.04/12.10 kernel
[14:21] <Viper187> The lubuntu desktop also went apeshit over my NIC too, but again 10.04 liked it fine.
[14:22] <Viper187> it kept saying disconnected over and over
[14:22] <holstein> Viper187: this is an official support channel, so please watch the language
[14:22] <holstein> you can also try the main ubuntu live, or xubuntu.. i think you will find that these issues are more with hardware support and the kernel
[14:23] <holstein> likely any recent, moder linux distro will have the same issues with your hardware
[14:23] <holstein> you can then look to the larger ubuntu community for hardware support via a backport, and use LXDE or lubuntu with those "fixes"
[14:23] <Viper187> goodie
[14:24] <holstein> or, just use 10.04
[14:25] <Viper187> kind if strange the old software works on the new AM3+ motherboard, but the new kernal wouldn't
[14:26] <holstein> Viper187: yeah? all support cannot roll forward.. things need to be dropped, otherwise the kernel would just keep growing larger
[14:26] <holstein> Viper187: you can always build your own kernel, as ubuntu does, which would provide support for whatever you need..
[18:19] <StephenS> I am on kubuntu
[18:19] <StephenS> lol
[18:39] <Myrtti> StephenS: congratulations?
[18:39] <StephenS> nah IM on cinnamon
[18:40] <StephenS> which works on lubuntu somehow
[18:40] <StephenS> dunno what is happening but when I logout my PC it says lubuntu .....
[19:55] <tortik> How to remove unnecessary languages in Lubuntu 12.04?
[19:55] <tortik> *unneeded
[20:58] <heoyea> search lanuage and delete
[21:04] <cerebrate> from synaptic
[21:04] <cerebrate> if you have it
[21:04] <cerebrate> i hope synaptic comes with ubuntu still
[21:07] <Unit193> dpkg -l | grep language-pack  then you can sudo apt-get purge whatever one that isn't yours.   Now, this is all fairly moot as he's long gone.
[21:23] <phillw> cerebrate: I think it was removed in ubuntu, lubuntu still has it.
[21:23] <phillw> I've had to look at re-writing some of the generic wiki pages so that they do not rely on the use of synbaptics.
[21:23] <phillw> *Synaptics*
[21:24] <Unit193> You mean synaptic?
[21:27] <phillw> Unit193: Synaptic Package Manager


[11:31] <jamespage> marcoceppi, hey - is it possible to re-trigger the review queue tests for https://code.launchpad.net/~cjwatson/charms/trusty/ubuntu-repository-cache/xz-indexes/+merge/277880 ?
[11:31] <jamespage> cjwatson asked me to look on Friday, but the test failures had been dropped due to archiving of older results I think
[13:19] <marcoceppi> jamespage: restarted, but the results do disappear after a few days, but they are premenantly recorded here: http://reports.vapour.ws/charm-test-details/charm-bundle-test-parent-3650
[13:21] <marcoceppi> jamespage: it looks like the tests need to be fixed to use the better format of amulet.sentry['service'][0] instead of hard-coding '/0'
[13:51] <jamespage> marcoceppi,
[13:51] <jamespage> ack
[14:10] <stub> marcoceppi: Is all-machines.log or equivalent available anymore from CI runs? I can't see a link to them any more.
[14:27] <marcoceppi> stub: they should be
[14:27] <marcoceppi> stub: where are you looking?
[14:28] <jose> arosales, marcoceppi: hey guys, wanted to check everything was going good wrt tasks?
[14:48] <stub> marcoceppi: http://review.juju.solutions/review/2370 - just a link to jenkins logs
[14:51] <marcoceppi> stub: yes, this is a known deficiency. THe results still get logged to the vapour.ws site
[14:52] <marcoceppi> stub: http://reports.vapour.ws/all-bundle-and-charm-results/cassandra
[14:52] <marcoceppi> http://reports.vapour.ws/charm-test-details/charm-bundle-test-parent-3785
[15:00] <stub> marcoceppi: ahh, ta.
[16:00] <roadmr> hey juju folks :) what's a good way to get the last X lines of log from a unit? juju ssh $UNIT_ID sudo cat /var/log/juju/unit-$UNIT_TAG.log feels kludgy, and juju debug-log -i $UNIT_ID --limit=100 -n 100 can block if there are less than 100 lines in the log file :(
[16:21] <jrwren> charmers: any advice on these failure? http://juju-ci.vapour.ws:8080/job/charm-bundle-test-lxc/1534/console from http://review.juju.solutions/review/2357  I recall something about broken test env on that day. If no advice, can you please rerun those tests, assuming env is fixed?
[16:37] <bloodearnest> reactive question: where do I put my layer's unit tests, and do I run them in the layer, or in the built charm?
[16:38] <lazypower> bloodearnest: unit tests belong in the unit_tests directory in the layer, and should be runnable by both the layer and the built charm for completeness
[16:39] <tvansteenburgh> jrwren: i queued another test on lxc
[16:39] <bloodearnest> lazypower, right. Is there a standard place to put test dependencies in the layer?
[16:40] <lazypower> bloodearnest: so far i've seen a lot of use of tox to isolate all that in a venv
[16:41] <bloodearnest> lazypower, right, that's what I would do for a normal charm. Unsure about how different layers would combine the setup/running of their unit_tests in the built charm
[16:42] <lazypower> yeah, the files being overriden by the top layer that generates the built charm will be the holder of any overriden files
[16:42] <bloodearnest> lazypower, where will <layer>/unit_tests/* end up in the built charm dir structure?
[16:42] <lazypower> that dir will, yes
[16:42] <lazypower> but if there is say a <layer>/unit_tests/01-thing.py  in both layers
[16:42] <lazypower> the top most layer will override the 01-thing.py in the lower layer
[16:42] <bloodearnest> right
[16:47] <lazypower> bloodearnest - might also be worth the effort to ping the list with that question, and shake out some outliers that have thought but haven't asked yet
[16:47] <jrwren> tvansteenburgh: thanks.
[16:49] <bloodearnest> lazypower, by default, I assume charm build will merge all non-special directories in the final output?
[16:50] <bloodearnest> where special I guess = reactive, maybe hooks?
[16:54] <lazypower> bloodearnest, when merging, it still overwrites unless its metadata.yaml or config.yaml
[16:57] <bloodearnest> lazypower, ack
[17:22] <jose> marcoceppi: ping re: PSA
[17:23] <marcoceppi> jose: yes
[17:23] <jose> marcoceppi: is there currently a list of charms that are holding that hardcoded pattern? if so, is it public? I'd like to go in and fix some of those if possible
[17:23] <jose> or do some MPs
[17:24] <marcoceppi> not yet, we may be producing one for work with code-in
[17:24] <jose> oh awesome
[20:16] <asanjar> kwmonroe: sorry pal, i thought you had it
[20:16] <kwmonroe> no worries asanjar -- i was building myself out of sparktc github.. pre-built bins are fine by me!
[20:47] <tvansteenburgh> jrwren: almost http://reports.vapour.ws/charm-test-details/charm-bundle-test-parent-3834
[20:48] <jrwren> tvansteenburgh: thanks for the notice. *grumble* at it failing still :)
[21:17] <stokachu> so for actions.yaml the example schema https://jujucharms.com/docs/1.25/authors-charm-actions shows the use of compression.type=gzip, how does juju know that those properties are mapped to kind and quality?
[21:18] <stokachu> and what is the format for defining both the compression kind and quality, is it compession.type=gzip,0?
[21:41] <marcoceppi> stokachu: that's example fail
[21:42] <marcoceppi> stokachu: it should be compression.kind=gzip in the example
[21:51] <stokachu> marcoceppi: ah!
[21:51] <stokachu> now that makes sense
[21:52] <cory_fu> Hey, so I have a proposal for charm layers that I'd like to get feedback on.
[21:52] <marcoceppi> cory_fu: shoot
[21:53] <cory_fu> We'd been recommending base, runtime, etc. layers use yaml files for config options.  But this could lead to a lot of small yaml files with various names.  So I was thinking instead we could have an "options" section in layer.yaml
[21:54] <cory_fu> So you'd have layer.yaml contain: includes: ['layer:apache-php']; options: apache: packages: [...]
[21:54] <marcoceppi> cory_fu: oh, I like that, then what every key under option would be automatically prefixed?
[21:54] <cory_fu> Instead of having a separate apache.yaml
[21:54] <stokachu> created a PR https://github.com/juju/docs/pull/751 for that doc fix
[21:54] <cory_fu> Automatically prefixed?
[21:55] <marcoceppi> cory_fu: well, my thought was layers that presented options would provide jsonschema in them so that it'd be explicit
[21:56] <marcoceppi> ie, apache-php layer would define the schema which it supported
[21:56]  * marcoceppi strawmans
[21:56] <cory_fu> That sounds intriguing.  What would that look like?
[21:57] <cory_fu> Charm-tools could do the validation, then, at build time, too
[21:57] <marcoceppi> cory_fu: right
[21:59] <stokachu> heres my ghost charm using the latest wheelhouse support https://jujucharms.com/u/adam-stokes/ghost/trusty/8
[21:59] <marcoceppi> bleh, the apache-php layer doesn't quite fit the mold, but almost done
[21:59] <stokachu> went from 334 files to 72 \o/
[21:59] <marcoceppi> cory_fu: give me 10 min, otp
[22:00] <stokachu> though im not sure why the revisions aren't being updated to match what is in bzr
[22:29] <cory_fu> marcoceppi: Still otp?
[22:29] <marcoceppi> yes
[22:29] <cory_fu> kk
[22:31] <cory_fu> stokachu: Revisions on jujucharms.com don't match bzr revisions because the charm revision tracks number of times ingested, which happens at periodic intervals and could include many bzr revs
[22:32] <cory_fu> Once we have `juju publish`, the charm revs will make a lot more sense, since it will track how many times you ran `juju publish`
[22:52] <marcoceppi> cory_fu: https://gist.github.com/marcoceppi/ca36655cb917b16d0681
[22:52] <marcoceppi> something like that?
[22:53] <marcoceppi> cory_fu: actually, just updated it
[22:56] <cory_fu> marcoceppi: I like that a lot
[22:56] <cory_fu> I also like that Alot
[22:56] <marcoceppi> I hug Alot
[22:57] <marcoceppi> cory_fu: the "parent" key would just be the layer name. I'm not sure how this would work for the sites key other than make sites an open-ended object
[22:57] <marcoceppi> and maybe replace "provides" with "defines" as provides is used in the charm ecosystem
[22:57] <marcoceppi> best not to conflate the two
[22:57] <cory_fu> Agreed on the last bit
[22:57] <adam_g> ERROR error checking if provisioned: subprocess encountered error code 1   <- is there any way to get debug info on the subprocess failure ?
[22:58] <cory_fu> jsonschema doesn't have support for validated lists?
[22:58] <marcoceppi> cory_fu: no idea
[22:58] <marcoceppi> cory_fu: apparently it does
[23:00] <marcoceppi> cory_fu: since we already use jsonschema for actions.yaml it'd be great to keep that pattern going with this and maybe convince core that config.yaml should move to it as well ;)
[23:00] <cory_fu> Agreed
[23:00] <marcoceppi> cory_fu: either way, I like the idea. It gives better visibility into the layer and provides a build time lint for validation, +1
[23:07] <cory_fu> marcoceppi: Can you point me to an example of how jsonschema is used to use definitions in actions.yaml to validate params (or a similar example)?
[23:08] <marcoceppi> cory_fu: you mean the golang libraries, or how it looks as an implementation?
[23:08] <cory_fu> How it looks as an implementation
[23:08] <marcoceppi> cory_fu: the apache-plugin charm would be a good start ;)
[23:09] <cory_fu> Specifically, I'm wondering how the action.yaml contents are used as / injected into a schema
[23:09] <marcoceppi> cory_fu: they are the schema, each parent item defines a params and that params is the schema
[23:09] <marcoceppi> we'd remove the parent key (action name) and just have a schema, more or less what's in the gist
[23:10] <marcoceppi> cory_fu: O
[23:10] <marcoceppi> cory_fu: I'd imagine this would come into play eventuall, https://pypi.python.org/pypi/jsonschema but maybe I'm not understanding the question
[23:11] <cory_fu> So, looking at the example in that last link, the contents of "properties" is what we'd be filling in, right?
[23:11] <marcoceppi> cory_fu: no, not quite
[23:11] <cory_fu> So I guess we can just wrap it in {'type': 'object', 'properties': schema}
[23:12] <stokachu> cory_fu: ah ok
[23:12] <marcoceppi> cory_fu: let me try to produce a quick py example
[23:16] <cory_fu> marcoceppi: Alas, I have to run, but send me the pastebin when you have it done.  I think I'm seeing it now, but I'm not certain
[23:37] <marcoceppi> cory_fu: I wrote my thoughts at the bottom of the gist: https://gist.github.com/marcoceppi/ad318d081e3b30857819
[23:40] <marcoceppi> cory_fu: if you'd like I can open an issue on charm-tools to discuss further


[15:47] <mhall119> AlanBell: ping
[15:48] <AlanBell> o/
[15:48] <mhall119> AlanBell: is there any way to have a "private" pad on the current pad.ubuntu.com?
[15:48] <nigelb> probably not.
[15:48] <nigelb> we could hash the url to make it not guessable though.
[15:49] <AlanBell> I might have broken the team functionality
[15:49] <AlanBell> never really understood how that was supposed to work
[15:49] <nigelb> team functionality won't really wwork in this case.
[15:49] <AlanBell> if you click new pad on the front page it will give you a random url
[15:49]  * AlanBell doesn't quite know what this case is
[15:50] <mhall119> ok, we can do a random url, how could somebody discover that who isn't supposed to?
[15:50] <mhall119> is there a search or something that might reveal a private pad?
[15:50] <AlanBell> nope
[15:51] <AlanBell> I might see it during the etherpad-> etherpad-lite migration process, but apart from that it should be unguessable
[15:51] <mhall119> ok, so a random md5 hash should be sufficiently unguessable
[15:51] <AlanBell> but once someone shares it then it is out there
[15:51] <mhall119> AlanBell: we can't do that migration until after linaro connect in February
[15:51] <AlanBell> http://pad.ubuntu.com/ click the new pad button
[15:52] <mhall119> AlanBell: right,it'll be up to the people who know about it to not tell people who shouldn't
[15:52] <AlanBell> or click the create team site button and see if it does anything
[15:52] <AlanBell> oh, it won't it needs dns integration
[15:52] <AlanBell> needs to auto-create a subdomain http://pad.ubuntu.com/ep/pro-signup/
[15:52] <mhall119> hmm...
[15:53] <AlanBell> could do the migration before the linaro connect
[15:53] <AlanBell> just not during :)
[15:53] <mhall119> no, let's wait until after
[15:53] <AlanBell> fine
[15:53] <AlanBell> oh, I might have a way to do the auto login that cjohnston wanted
[15:53] <AlanBell> though it isn't a massively secure login
[15:54] <AlanBell> s/a massively/an even slightly/
[15:54] <mhall119> lol
[15:55] <AlanBell> but I don't think it matters


[00:00] <xnox> jbicha: no. i wish GNOME would accept patches I submit on bugzilla, before I show up to guadec ;-) otherwise i'd be one grumpy attendant.
[00:02] <jbicha> several GNOME modules are mostly unmaintained
[00:02] <xnox> larsu: darkxst: the ubiquity-panel, the way i test is, is stop lightdm & kill -9 X, and then from tty1: sudo start ubiquity, after changing stuff in-place in a VM..... not sure if this helps =) the highlight is old about ubiquity
[00:04] <xnox> jbicha: yeah, my point is other GNOME dev's that say "lgtm, why is this not merged?" should just commit. In Debian/Ubuntu we have NMU and/or strong team maintainership, yet the GNOME core people don't see this as a problem.
[00:04] <jbicha> GNOME upload procedures are rather different than Ubuntu's
[00:05] <jbicha> it's relatively easy to get git commit rights for everything GNOME so GNOME maintainers assume you have rights unless you tell them otherwise
[00:06] <jbicha> on the other hand, if you're not a maintainer you can get yelled at for not getting a commit reviewed on bugzilla first
[00:08] <jbicha> it's much much harder to get commit/upload rights for Debian or Ubuntu
[00:13] <jbicha> xnox: so the patches you're waiting on are for gnome-sudoku and gnome-power-manager? those are good examples of mostly unmaintained modules
[00:14] <jbicha> look in the .doap file to find out who the maintainer is and manually ping them on irc or by email
[00:16] <xnox> jbicha: that's not what gnome love / gnome goals say to do.
[00:16] <xnox> jbicha: i write a patch for gnome, not a pull request to individual person, maybe it's all should be up on github then instead.
[00:18] <jbicha> gnome-power-manager is no longer core GNOME (note that Ubuntu GNOME doesn't ship it either)
[00:24] <jbicha> nearly all of gnome-games went unmaintained when they split them into separate modules
[00:24] <jbicha> GNOME will never go full-on github because github isn't FOSS
[00:25] <jbicha> it's likely that the new "GNOME Software" app won't include support for paying money for proprietary apps
[01:16] <jbicha> attente: the indicator-keyboard tests still fail
[02:19] <sokky_> hello all, any ecrypt pros here?
[02:46] <attente> jbicha, is there an updated log? or is it the same as before?
[02:49] <jbicha> attente: I don't know http://paste.ubuntu.com/5923873/ also failed on the PPA builders but by default it doesn't give a nice log
[02:52] <attente> jbicha, thanks, yeah, that's a different problem
[03:00] <jbicha> and ibus-client-clutter needs fixing to build against ibus 1.5 http://paste.ubuntu.com/5923902/
[04:13] <pitti> Good morning
[04:24] <Mirv> good morning!
[04:30] <larsu> Good morning
[04:35] <darkxst> good afternoon!
[04:35] <darkxst> pitti, hey!
[04:35] <jbicha> attente: this is correct, right? https://launchpad.net/ubuntu/+source/ibus-client-clutter/0.0+git20090728.a936bacf-5ubuntu1
[04:36] <darkxst> pitti, would you have any idea why apt-get doesnt seem to pick up ddebs from ppa?
[04:36] <pitti> darkxst: I never tried that; do they appear in the Packages.gz index?
[04:40] <darkxst> pitti, nope
[04:40] <darkxst> pitti, although apport-retrace seems to find them mostly
[04:40] <pitti> darkxst: and a-retrace doesn't just take them from ddebs.u.c.?
[04:40] <pitti> apport just uses apt
[04:41] <pitti> well, python-apt, but that still just uses the normal package indexes
[04:41] <darkxst> pitti, gnome3 ppa
[04:41] <darkxst> those would not be on ddebs.u.c
[04:42] <pitti> ooh
[04:42] <pitti> http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/dists/saucy/main/debug/binary-amd64/Packages
[04:42] <pitti> darkxst: ^ they are there, in a /debug sub-hierarchy
[04:42] <pitti> so you need a "main/debug" series apt line in addition
[04:46] <darkxst> pitti, right! thanks
[07:07] <sil2100> Morning!
[07:08] <Mirv> sil2100: hello!
[07:17] <sil2100> Stacks seem to be a bit lazy since some days - I remember times when I woke up and had to publish/fix manually stuff, since I already had all stack results
[07:17] <sil2100> But now? I wake up and testing and building steps are still ongoing
[07:22] <sil2100> Morning didrocks !
[07:22] <sil2100> didrocks: stacks still not published, they're building and checking right now!
[07:22] <sil2100> didrocks: how's IoM? ;)
[07:23] <didrocks> hey sil2100!
[07:23] <didrocks> sil2100: foggy :p
[07:23] <didrocks> sil2100: stacks are under control? why they are not ready?
[07:23] <didrocks> like ATI machine down?
[07:24] <sil2100> Not sure, some stacks are still in the building stage (like settings), and check jobs are queued up
[07:24] <sil2100> I guess everything slowed down a bit after we enabled additional check jobs, like unity8
[07:24] <didrocks> sil2100: shouldn't
[07:24] <jibel> sil2100, ATI was donw
[07:24] <didrocks> sil2100: the tests are running on both machines, right?
[07:24] <jibel> down
[07:24] <sil2100> didrocks: hah, something's wrong with ATI
[07:25] <didrocks> ok, thanks jibel :)
[07:25] <sil2100> jibel: is it fixed now?
[07:25] <didrocks> sil2100: ensure you kill all the -head jobs please that are duplicated
[07:25] <didrocks> if it's down since saturday, we don't want to rebuild the same stacks 3 times
[07:25] <jibel> sil2100, I'm trying to bring it back but there is something strange
[07:25] <sil2100> jibel: since I see the ATI log of the current job and it doesn't seem to move
[07:25] <jibel> sil2100, since 3 or 4 days it always goes down when platform tests start
[07:26] <sil2100> hmm
[07:26] <jibel> didrocks, I restarted it saturday and yesterday
[07:26] <didrocks> robert_ancell: https://launchpad.net/~ubuntu-unity/+archive/next/+packages?field.name_filter=unity-api&field.status_filter=published&field.series_filter=
[07:27] <didrocks> jibel: urgh, so something wrong with the upstart job?
[07:27] <sil2100> jibel: I wonder what's wrong with the platform tests ;/ Could you give me a ping once ATI is unblocked again?
[07:27] <jibel> didrocks, it wouldn't freeze the whole machine
[07:28] <jibel> didrocks, it is a hardlock, machine is up, but ssh is dead and no console
[07:28] <jibel> sil2100, it's up
[07:28] <pitti> bonjour didrocks et jibel, comment allez-vous ?
[07:28] <sil2100> jibel: but could it be that something again is wrong? Since:
[07:28] <sil2100> http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/665/label=autopilot-ati/console
[07:28] <jibel> Bonjour pitti . Ça va bien et toi ?
[07:29] <sil2100> Oh, FAIL
[07:29] <didrocks> jibel: argh, not fine :/
[07:29] <pitti> jibel: je vais mieux, il ne fait plus autant chaude
[07:29] <didrocks> salut pitti!
[07:29] <jibel> sil2100, FATAL: Unable to delete script file /tmp/hudson1344923958933719703.sh means that jenkins lost contact with its slave
[07:29] <didrocks> sil2100: please publish the settings stack ASAP ;)
[07:29] <pitti> jibel: "chaud"
[07:29] <sil2100> didrocks: will do, waiting for it to finish building though!
[07:30] <sil2100> armhf is still building
[07:34] <jibel> didrocks, sil2100 , there is really something wrong, jenkins slave just died
[07:36] <jibel> sil2100, you can add unity8 to the list of tests to restart
[07:42] <sil2100> jibel: ok!
[07:43] <sil2100> didrocks: so, I assume you guys ACK the packaging changes for settings ;)?
[07:43] <sil2100> didrocks: publishing1
[07:44] <didrocks> sil2100: yep, ack! :)
[07:44] <didrocks> sil2100: thanks
[07:45] <sil2100> jibel: do you think that re-running tests for platform can cause the death of ATI machine again?
[07:45] <sil2100> jibel: since I re-ran it in the morning, so I guess it's queued up already
[07:46] <sil2100> pstolowski: welcome back! ;)
[07:46] <pstolowski> sil2100: hey!
[07:46] <jibel> sil2100, that's what I'd like to verify
[07:47] <jibel> sil2100, it just started fine
[07:48] <sil2100> jibel: indeed, so far so good
[07:48] <Mirv> didrocks: hello :) sdk packaging changes of adding devscripts to have licensecheck seems legit, can I publish?
[07:50]  * sil2100 ACKed the change himself to FTBFS
[07:50] <sil2100> ;)
[07:50] <didrocks> hey Mirv! welcome back
[07:50] <didrocks> Mirv: can you check with seb128? I'm on the IoM this week sprint, so not really available for packaging reviews :)
[07:51] <didrocks> Mirv: I trust that between you and sil2100, you'll get through it! :)
[07:52] <sil2100> seb128: morning!
[07:52] <seb128> sil2100, hey
[07:52] <sil2100> seb128: can we have your approval on http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+13.10.20130729-0ubuntu1.diff ?
[07:52] <Mirv> didrocks: thank you :) ok, have a good IoM
[07:53] <didrocks> thanks!
[07:53] <seb128> sil2100, Mirv: seems fine to me
[07:54] <sil2100> Mirv: green light!
[07:54] <sil2100> Mirv: publish ;)
[07:57] <Mirv> seb128, sil2100: thanks
[07:58] <Mirv> sil2100: and thanks for taking care of my stacks in my absence :)
[07:59] <Mirv> sil2100: any idea of those ATI unity test failures? (platform)
[08:00] <sil2100> hm, not sure
[08:00] <sil2100> Mirv: maybe let's poke upstream maybe?
[08:01] <Mirv> sil2100: the other states D-Bus problem
[08:01] <Mirv> sil2100: it's not platform upstream but normal unity autopilot tests that are failing
[08:02] <sil2100> Mirv: what I would do - I would poke unity guys (or even fill in a bug about those and inform them) and publish anyway - or re-run the tests to see it it passes the second time
[08:02] <Laney> morning!
[08:02] <seb128> Laney, hey, how are you?
[08:02] <sil2100> didrocks: sorry to bother you, but maybe on the sprint you can poke someone now - I need to be part of ~cordova-ubuntu, or one of my sub-teams has to
[08:03] <sil2100> didrocks: since I can't re-deploy webapps to fix the stack ;/
[08:03] <Laney> hey seb128, not bad thanks
[08:03] <Mirv> sil2100: rerunning, a good way to find out also if it kills the ATI machine again..
[08:03] <Laney> part of my bike got stolen over the weekend so I had to carry it two miles home, but other than that ...
[08:04] <seb128> Laney, :-(
[08:04] <sil2100> Laney: hi! Part of your bike?
[08:04] <darkxst> Laney, which part?
[08:04] <Mirv> intel succeeded fine
[08:04] <Laney> yeah
[08:04] <Laney> the front skewer
[08:04] <darkxst> just the skewer? that sounds strange!
[08:04] <Laney> it was either just to be annoying or in the hope that i'd abandon it and they could come back and take the whole thing when it was more quiet
[08:04] <Laney> those are my theories anyway
[08:05] <pitti> Laney: ugh, I'm sorry for you; that suck!
[08:05] <pitti> s
[08:05] <Laney> but instead I carried it back and the nice man in the shop gave me a new one for free the next day
[08:05] <seb128> pitti, salut, ca va bien ?
[08:07] <pitti> seb128: salut Sebastien ! oui, je vais mieux, il ne fait plus chaud
[08:07] <pitti> seb128: et toi ?
[08:07] <seb128> pitti, c'est la même chose pour moi, ça fait du bien un peu de frais
[08:08] <tkamppeter> mlankhorst, hi
[08:09] <darkxst> Laney, I would normally say zip ties can fix anything, but probably not in your case ;)
[08:09] <didrocks> sil2100: there is nobody from this team AFAIK here :/
[08:09] <sil2100> Mirv: it passed now \o/
[08:09] <Laney> darkxst: heh
[08:09] <sil2100> didrocks: :( Too bad then, I hate when they create new teams without assigning them to others
[08:09] <Laney> I have some "pinheadz" on my other bike after having a similar incident there
[08:09] <Laney> will get some for this one now too
[08:12] <Mirv> sil2100: wow, nice!
[08:14] <darkxst> Laney, so stealing skewers is regular there? here they just take the whole bike ;(
[08:15] <darkxst> and they thieves don't care about it being busy. I had one bike stolen during peak hour on one of the busiest streets in Melbourne
[08:16] <Laney> :/
[08:16] <Laney> I had two good locks on it so maybe it would have required more time/effort
[08:17] <Laney> disable bike, go away to fetch more tools, come back in middle of night to take it
[08:17] <seb128> seems like lot of efforts to steal a bike
[08:17] <darkxst> seb128, angle grinders cut through even the best locks like butter!
[08:18] <Laney> haha
[08:18] <Laney> and I guess nobody would do anything if you look confident enough
[08:26] <sil2100> seb128: so, once ibus 1.5.3 moves out of -proposed, it will be hosted officially on the image, right?
[08:26] <sil2100> s/hosted/installed
[08:26] <seb128> sil2100, correct
[08:26] <seb128> sil2100, why?
[08:27] <sil2100> seb128: ah, just asking, since unity stack failed because it was requiring libibus-1.0-5, which is in proposed still - wanted to know for sure if it will be installed by default
[08:28] <sil2100> Since there was some discussion I guess
[08:28] <seb128> sil2100, oh right ... CI doesn't build with proposed right?
[08:28] <seb128> sil2100, we are going to need an upload of unity build with ibus 1.5 to move it out of proposed though
[08:30] <sil2100> seb128: it's building with proposed, but it fails if a package is not mentioned in packages: and not installed by default - which currently is the case with the new ibus, although for the time of transition I'll fix it up
[08:30] <seb128> sil2100, ok, great
[08:30] <sil2100> seb128: so we'll have a new unity released with the new ibus
[08:30] <seb128> sil2100, excellent
[08:30] <seb128> today?
[08:30] <sil2100> seb128: I'll fix the config now and let's see how the  tests roll
[08:30] <seb128> great
[08:34] <sil2100> seb128: https://code.launchpad.net/~sil2100/cupstream2distro-config/temporary_unity_new_ibus/+merge/177333 <- can you take a quick look and approve? I'll redeploy and re-run unity stack once all other stacks are green, since unity is hogging the test machines
[08:35] <seb128> sil2100, ok, approved
[08:36] <mlankhorst> tkamppeter: did you recheck 56578 with the xserver I uploaded + a newer version of onboard?
[08:38] <sil2100> Eek!
[08:47] <tkamppeter> mlankhorst, no, how do I get the new xserver and the new onboard?
[08:47] <tkamppeter> mlankhorst, can I do this with saucy?
[08:47] <mlankhorst> yeah needs saucy.. xserver in canonical-x/x-staging, onboard bzr branch lp:onboard iirc
[08:50] <tkamppeter> mlankhorst, xserver-common and xserver-xorg-core are 2:<IP_ADDRESS>-0ubuntu0.0~ppa3 and xserver-xorg-video-intel is 2:2.21.12-0ubuntu1~ppa1. Is this correct? Then all what I need is the onboard from BZR?
[08:53] <mlankhorst> probably
[08:53] <mlankhorst> intel version doesn't matter much, it was uploaded for other reasons :)
[09:02] <tkamppeter> mlankhorst, it is unbuildable. I get
[09:02] <tkamppeter> dpkg-source: error: unrepresentable changes to source
[09:02] <tkamppeter> dpkg-buildpackage: error: dpkg-source -b onboard gave error exit status 2
[09:02] <tkamppeter> cd ..
[09:03] <mlankhorst> ignore, or build with debuild -b
[09:03] <mlankhorst> it's probably trying to include the .bzr directory if you build a source file
[09:06] <tkamppeter> mlankhorst, even after "rm -rf .bzr" I can only build with "debuild -b", but at least I can test onboard now.
[09:14] <sil2100> seb128: can I ask you for a packaging ACK before publishing? http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Phone/job/cu2d-phone-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_address-book-app_0.2+13.10.20130729-0ubuntu1.diff
[09:14] <sil2100> seb128: (it has the qtdeclarative5-ubuntu-contacts0.1 package in it)
[09:16] <seb128> sil2100, +1
[09:17] <tkamppeter> mlankhorst, onboard works principally, but right-click emulation leads to a segfault.
[09:18] <tkamppeter> mlankhorst, onboard also does not take the black theme of the desktop.
[09:19] <sil2100> seb128: thanks! Another (last) quick one: http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_webbrowser-app_0.21+13.10.20130729-0ubuntu1.diff
[09:20] <mlankhorst> tkamppeter: yeah but I only care about stuck buttons atm
[09:20] <seb128> sil2100, +1
[09:22] <sil2100> seb128: thanks!
[09:25] <mlankhorst> Laney: yikes, here they try to steal your bike by adding another lock to the bike, wait until you unlock your own then steal the bike when you go leave it unattended :/
[09:25] <tkamppeter> mlankhorst, I get no stuck button, seems to work no (typing this with onboard on touch screen)
[09:25] <Laney> mlankhorst: haha, that's quite obvious
[09:27] <mlankhorst> Laney: but unfortunately, it works..
[09:27] <Laney> why would you leave it?
[09:27] <Laney> without your lock on
[09:27] <mlankhorst> seems to be a common reaction when it happens when people are not aware of that trick
[09:28] <tkamppeter> mlankhorst, so I can do tablet mode with the only problem of a missing right button, missing screen rotation, and xbmc not working.
[09:28] <mlankhorst> tkamppeter: the only useful data point to me is... do you still get stuck buttons like that?
[09:29] <mlankhorst> and does xorg stay stable
[09:31] <tkamppeter> mlankhorst, stuck button and X stability seems to be perfect, rest are apps which are not your scope.
[09:32] <mlankhorst> ok good, so I guess the stuck button was partially caused by onboard grabbing the mouse too then..
[09:33] <mlankhorst> or w/e, maybe there is still a bug in xserver but at least there's a workaround for it..
[10:24] <tkamppeter> mlankhorst, I have updated https://bugs.freedesktop.org/show_bug.cgi?id=56578 now.
[10:25] <ubot2`> Freedesktop bug 56578 in Server/Input/Core "race condition with active/passive grabs when opening menus with touch" [Normal,Assigned]
[10:25] <sil2100> thomi: hi! You in IoM too?
[10:25] <thomi> sil2100: yup
[10:26] <sil2100> thomi: awesome! Quick question - would you mind if I proposed a new version of python-evdev to ubuntu?
[10:26] <thomi> sil2100: sure, but please make sure you don't break autopilot - what's the change needed for?
[10:27] <sil2100> thomi: the upstream developer released a new version and simply asked me to sync it with Ubuntu, so no urgent fixes
[10:28] <thomi> sil2100: cool - in the past they;ve broken API, so we need to double check that
[10:28] <thomi> it's nice that they've realised we pushed it into distro though :)
[10:28] <sil2100> thomi: right, I'll poke you about testing later, at least for some guidelines how to check if AP is still working
[10:29] <thomi> sil2100: that's easy: bzr branch lp:autopilot; cd autopilot; autopilot run autopilot
[10:29] <sil2100> Ah, thought that jsut some specific tests use evdev ;)
[10:30] <sil2100> And/or only on certain configurations
[10:30] <thomi> sil2100: yeah, you could probably just run the input tests
[10:30] <thomi> nah, we run on all cofigs
[10:30] <thomi> as long as you have write acces sto /dev/uinput
[10:30] <thomi> sil2100: feel free to ping me and I can run the tests, if you like
[10:31] <sil2100> thomi: thanks :)
[10:56] <sil2100> thomi: hi! Can you give me power over launchpad.net/python-evdev ?
[10:57] <sil2100> thomi: it would be nice to be able to edit the data, could you make me the maintainer?
[11:11] <sil2100> seb128: hmm
[11:12] <seb128> sil2100, I don't like that hmmm :p
[11:12] <sil2100> seb128: I have a question related to releasing new upstream versions of packages where we're not upstream, but which I'm a maintainer of
[11:12] <seb128> ah
[11:12] <sil2100> seb128: when releasing a new upstream version then, in the changelog, should I list all the changes that have been made inbetween versions?
[11:12] <seb128> sure, ask
[11:12] <sil2100> seb128: or just write 'New upstream version'?
[11:12] <seb128> your call
[11:12] <seb128> there is not written rules
[11:13] <seb128> I tend to list things that close a bug
[11:13] <Laney> I like to put the interesting things from NEWS
[11:13] <seb128> and interesting changes
[11:13] <sil2100> Ok ;) Thanks guys
[11:13]  * Laney tries sbuild --arch armhf u-s-s on his desktop
[11:17] <seb128> Laney, u-s-s is a small build, building on the n7 takes less than a minute
[11:17]  * seb128 usually does build there
[11:17] <seb128> it's just a bit annoying having to reinstall the build-deps when putting a new image on it
[11:17] <Laney> yeah I don't have those atm
[11:17] <Laney> thought this might be fast but it's not really
[11:18] <seb128> Laney, let me know if cross building work
[11:18] <Laney> not cross building, qemu
[11:18] <Laney> is working though
[11:18] <seb128> ah
[11:20] <Laney> I think it's slower :P
[11:22] <Laney> oh, segfaulted in the testsuite
[11:30] <Laney> ah good, that makes it more responsive
[11:30]  * Laney breathes
[11:30] <xnox> brilliant indicators are finally crashing ubiquity panel =)
[11:30]  * Laney locks Qt in the cupboard under the stairs as a punishment
[11:32] <xnox> I think i will disable ubiquity panel as a workaround for bug 1161058
[11:32] <ubot2`> Launchpad bug 1161058 in ubiquity (Ubuntu) "panel crashed with SIGSEGV in indicator_object_get_entries()" [Medium,Confirmed] https://launchpad.net/bugs/1161058
[11:42] <xnox> Right, larsu if you need any help testing / porting ubiquity's panel to new indicator stack feel free to ping me =)
[11:45] <seb128> xnox, did you read the friday discussion on the topic?
[11:46] <xnox> seb128: hm, I don't think I did. Was it here?
[11:47] <seb128> xnox, yes, short summary: larsu is working on it, he might have it done today (if IRC crazyness stops pulling him off work)
[11:47] <xnox> seb128: there is a mega plan in the back of my head to drop ubiquity-panel and drop ubiquity-dm, and instead use upstart user session to start ubiquity on login, with dash hidden / not-loaded and with a few thing pre-emptied.
[11:47] <xnox> seb128: ok. cool.
[11:56] <seb128> sil2100, how is unity looking? did you retry it yet?
[11:56] <sil2100> seb128: I did, let me look at the status
[11:58] <sil2100> seb128: it finished, but intel has a few too many failures
[11:58] <seb128> sil2100, real bugs/issues? or system flackyness?
[11:59] <sil2100> Seems like system flackyness, since ATI was fine
[11:59] <seb128> so another retry?
[12:08] <sil2100> Yes, it's running already
[12:08] <sil2100> thomi: hi! I installed the new evdev and tested the test_input_stack tests and they passed, but if you have a moment, could you also test on your machine? I pushed the package to my PPA:
[12:08] <sil2100> thomi: ppa:sil2100/testing
[12:19] <desrt> good morning freedom lovers
[12:19] <desrt> . o O ( hmm... that didn't work... )
[12:19] <desrt> PANTS OFF!
[12:24] <seb128> desrt, howdy!
[12:24] <seb128> desrt, you are trying for GUADEC? ;-)
[12:24]  * desrt invokes jdub
[12:24] <desrt> seb128: i made a present for you over the weekend
[12:25] <seb128> desrt, I noticed, thanks for working on that ;-)
[12:25] <seb128> when is next tarball due? ;-)
[12:25] <seb128> well, you need to get it merged first I guess :p
[12:25] <desrt> i think this won't be done until after guadec
[12:25] <desrt> i've been generating a whole lot of work lately that he needs to review
[12:25] <seb128> ok, I might just distro patch it if I need it
[12:25] <desrt> whether in gio, file monitors, desktop files...
[12:26] <desrt> warning: i may change the name
[12:26] <seb128> ok
[12:26] <desrt> g_file_measure_disk_usage() sounds nicer than _query_disk_usage() i think
[12:26] <seb128> well, I've enough stuff to do that I can delay that for a few weeks
[12:26] <seb128> I should probably just wait for you to land it properly
[12:29] <thomi> sil2100: sure
[12:29] <sil2100> seb128: once I get this new package I am maintaining tested, how should I proceed to get the new version into the Ubuntu queue? Who should I poke and with what?
[12:29] <sil2100> thomi: thank you!
[12:30] <seb128> sil2100, either do a merge proposal against the ubuntu:<source> vcs or open a bug with a link to the ppa, or with the package files attached to the bug, and subscribe ubuntu-sponsors
[12:31] <sil2100> seb128: thanks :)
[12:31] <seb128> yw
[12:49] <sil2100> thomi: and then as well my previous question - could you assign me as the maintainer of launchpad.net/python-evdev?
[12:50] <thomi> sure
[12:50] <thomi> sil2100: done
[12:57] <thomi> sil2100: I don't get a new python-evdev with your PPA added
[12:58] <thomi> hmmm
[12:58] <sil2100> thomi: hm, let me see!
[12:59] <thomi> sil2100: it doesn't look like it's in your PPA yet (not published anyway) - I'll try again later
[12:59] <sil2100> thomi: ah, right, amd64 still pending ;/ Sorry about that!
[12:59] <sil2100> thomi: and thanks!
[12:59] <sil2100> :)
[12:59] <thomi> no worries
[13:09] <seb128> Laney, did you hit weird gsettings missing schemas bugs happening randomly with system-settings recently?
[13:10] <seb128> GLib-GIO-ERROR **: Settings schema 'com.ubuntu.touch.system' does not contain a key named 'r'
[13:10] <seb128> just hit that (but it's not the first time, it seems to try to read random keys)
[13:16] <Laney> seb128: no
[13:16] <Laney> no idea how to trigger it?
[13:17] <seb128> it happens on start every few runs here
[13:17] <seb128> with random key names, looks like corruption
[13:17] <seb128> could be an issue with gsettings-qt
[13:18] <Laney> that one in particular comes from orientation-lock
[13:18] <Laney> I can't see how that could be a bug in system-settings
[13:18] <Laney> have you seen it on the device or desktop or both?
[13:19] <seb128> desktop
[13:19] <seb128> but I don't test on the device that much
[13:19] <seb128> I mostly do check a few specific thing, otherwise run it when I update the image just to have a look
[13:19] <Laney> same
[13:22] <czajkowski> aloha
[13:24] <czajkowski> wondering who is the developer driving scopes? question on their functioning.  each time I lauch one in the dash it's instintive for me to double click but that just makes it disapear then I go and click it again and then have to hit launch.  Is there a way to change this so that if I find it in the dash and double click it, it opens?
[13:27] <seb128> czajkowski, you want to talk to mhr3_
[13:28] <czajkowski> seb128: cheers
[13:28] <pitti> robru: hey Robert, how are you?
[13:28] <czajkowski> maybe I'm just too used to double clicking
[13:28] <pitti> robru: would you mind having a look at friend's failing autopkgtest? it's blocking other packages like the new pygobject from entering saucy
[13:58] <sil2100> thomi: if anything, the amd64 binary has been built and published!
[14:11] <seb128> Laney, larsu:
[14:11] <seb128> GLib-GIO-ERROR **: Settings schema 'org.gnome.desktop.background' does not contain a key named 'picture-u\xa8-d\xb0\xb1'
[14:11] <seb128> there is something weird with gsettings-qt :/
[14:19] <desrt> seb128: aren't you glad that resulted in an abort with a helpful error message instead of strange difficult-to-trace-down behaviour? ;)
[14:20] <seb128> desrt, don't get me started on the abort thing... ;-)
[14:20]  * seb128 is pondering storing the ringtone in a ini style file instead of gsettings just to make sure the phone app on the phone is robust
[14:21] <Laney> when did you first start seeing this behaviour?
[14:21] <seb128> since we started using gsettings
[14:22] <Laney> interesting
[14:22] <Laney> locale related?
[14:22] <seb128> dunno, why would it?
[14:23] <seb128> it's a corruption
[14:23] <desrt> seb128: there's a much easier way to ensure the app is robust: install the schema
[14:23] <seb128> it works 9 times on 10 run
[14:23] <desrt> :)
[14:23] <seb128> desrt, robust means = if your disk is corrupted, the schemas missing, etc, you still have a chance the app keep working
[14:23] <seb128> it might not
[14:24] <desrt> if disk corruption results in part of the application going missing then it's true that the application may not run properly
[14:24] <seb128> but the chance is higher when it doesn't abort just because e.g the configured ringtone schemas is missing
[14:24]  * desrt raises a glass to not having old arguments
[14:24] <seb128> ;-)
[14:24] <seb128> I told you, don't get me started on that :p
[14:24] <desrt> fair enough!
[14:25] <seb128> we have to agree on disagreeing there
[14:25] <seb128> it also annoys me that I've to make system settings depends on the phone app, which is not available in the archive yet, to be able to start it
[14:25] <seb128> I would prefer have a if(key not there) hide that ui
[14:26] <desrt> this API exists now
[14:26] <desrt> and it's fast and convenient
[14:26] <desrt> g_settings_schema_source_lookup (g_settings_schema_source_get_default (), "your.schema.name")
[14:26] <seb128> yeah, I just need to get larsu to provide a qt api in gsettings-qt
[14:27] <seb128> since I'm calling from qml
[14:27] <desrt> i think he's already doing that, no?
[14:27] <desrt> with his dont-abort-like-desrt patch
[14:27] <seb128> it doesn't abort on missing key
[14:27] <seb128> but it does on missing schemas
[14:27] <desrt> ah
[14:28]  * desrt wonders how it could ever have aborted on missing keys
[14:30] <larsu> desrt: g_settings_get_range() with a missing key aborts iirc
[14:30] <larsu> seb128: hm, when do you get this message?
[14:30] <desrt> larsu: but don't you have to enumerate the keys in the schema in the first place in order to spin up the property map?
[14:31] <desrt> ie: how is it even possible that you'd get a request coming in for a key that's not in the map?
[14:31] <seb128> larsu, that's happening in system-settings on start, once every 10 run ... seems like some sort of corruption :/
[14:31] <seb128> larsu, the code doesn't do anything special, it just use a GSettings and read one key
[14:31] <larsu> desrt: there's an api settings.schema.choice(nameofkey)
[14:31] <larsu> desrt: pass the wrong nameofkey, boom.
[14:31] <desrt> ah
[14:32] <desrt> ya... you should protect against that
[14:32] <pitti> hey larsu, wie gehts?
[14:32] <desrt> this isn't C, after all :)
[14:32] <seb128> larsu, I'm hitting it in different panels
[14:32] <desrt> pitti: hey... i wanted to ask you about your jetlag system
[14:32] <larsu> desrt: ya, that's the dont-abort-like-desrt patch
[14:32] <larsu> pitti: gut danke! How was your weekend?
[14:32] <pitti> larsu: brainmelting :)
[14:33] <larsu> seb128: weird. I'll have a look.
[14:33] <pitti> larsu: we've been to Dresden, but didn't get that much done really aside from BBQ and idling at the beach :)
[14:33] <seb128> pitti, when do you start you holidays? I though you said they were conflicting with GUADEC, must be soon?
[14:33] <pitti> seb128: yes, next week
[14:34] <larsu> pitti: ya, same here :)
[14:35] <Sweetshark> seb128: soo, can we mir lp-solve quicky? it seems to have been in main at least twice (see bug 305790) and has been on upstream version 5.5.0 since at least lucid: https://launchpad.net/ubuntu/+source/lp-solve
[14:35] <ubot2`> Launchpad bug 305790 in xom (Ubuntu Jaunty) "MIR - move to main for openoffice.org 3 build-depends" [High,Fix released] https://launchpad.net/bugs/305790
[14:36] <Sweetshark> seb128: trouble is: I am using libreoffices own copy of lp-solve and its causing all kinds of stupid dependency trouble ...
[14:36] <jbicha> desrt: how do you recommend fixing bug 1195481?
[14:36] <ubot2`> Launchpad bug 1195481 in gnome-control-center (Ubuntu) "[power]: gnome-control-center crashes if indicator-power is not installed in Unity" [Medium,New] https://launchpad.net/bugs/1195481
[14:36] <seb128> Sweetshark, check with doko or mterry maybe? but it has been in main it should be fine
[14:37] <desrt> jbicha: lots of good ways to deal with that
[14:37] <desrt> jbicha: could move the custom indicator to the indicator-power package like datetime does it
[14:38] <sil2100> seb128: \o/ Tests passed \o/
[14:38] <sil2100> seb128: can I publish unity?
[14:38] <desrt> jbicha: could move the key to g-c-c and add a dep from the indicator to g-c-c
[14:38] <seb128> sil2100, excellent, please do!
[14:38] <desrt> jbicha: could add a dep from g-c-c to the indicator
[14:38] <sil2100> seb128: we'll have it in proposed and ready for the transition
[14:38] <desrt> jbicha: could move the schema to some other package like gs-d-s and make both depend on that
[14:38] <desrt> or you could do the conditional thing i mentioned above
[14:39] <jbicha> desrt: yeah the last one is the one I'm looking for
[14:39] <desrt> that's the least-good one :p
[14:39] <desrt> but ya... might make sense in this case
[14:39] <desrt> i kinda like the datetime approach, fwiw
[14:40] <jbicha> desrt: because you're hoping gnome-control-center gets forked?
[14:40] <desrt> not because of that
[14:40] <desrt> you need to think of schemas like you think of libraries....
[14:40] <sil2100> alex-abreu: ping!
[14:40] <sil2100> alex-abreu: hi!
[14:41] <desrt> so either a) they're API or b) they're private
[14:41] <alex-abreu> sil2100, hi!
[14:41] <sil2100> alex-abreu: could you add me to ~cordova-ubuntu ?
[14:41] <desrt> having all users of the schema in the same package means that you get option (b) which is all-around nicer
[14:41] <alex-abreu> sil2100, sure
[14:41] <Sweetshark> doko, mterry: see above -- do we need to do all the redtape for getting lp-solve 5.5 into main for the third time?
[14:41] <desrt> plus... why have custom code installed (even if disabled) to deal with an indicator that's not installed?
[14:41] <sil2100> alex-abreu: since I need to fix the cu2d webapps stack and need to be part of the team to do that ;)
[14:42] <sil2100> alex-abreu: thanks!
[14:42] <alex-abreu> sil2100, done .. welcome in the team ! :)
[14:42] <sil2100> ;p
[14:42] <mterry> Sweetshark, looking
[14:43] <Sweetshark> mterry: note its still supported in main in lucid anyway with that upstream version.
[14:43] <mterry> Sweetshark, yeah.  that's fine.
[14:43] <mterry> approved  :)
[14:44]  * Sweetshark gives mterry a hug.
[14:45] <jbicha> desrt: I attached a MP to the bug which is one fix (having Unity depend on indicator-power) but bschaefer wasn't so sure that was right
[14:46] <desrt> jbicha: move the panel is your best bet, imho
[14:46] <desrt> keeping patches out of the g-c-c package and shipping override panels alongside indicators is the best way
[14:47] <jbicha> desrt: that's a lot more work though and it will mean that the Ubuntu versions will likely get outdated (but at least the UI would be more stable from release to release)
[14:49] <jbicha> also there's bug 1197662
[14:49] <ubot2`> Launchpad bug 1197647 in indicator-datetime (Ubuntu) "duplicate for #1197662 Date & Time applet in control center does not start" [High,Fix released] https://launchpad.net/bugs/1197647
[14:50] <jbicha> oops I mean bug 1187981
[14:50] <ubot2`> Launchpad bug 1187981 in gnome-control-center "symbol conflicts in libtimezonemap1" [High,New] https://launchpad.net/bugs/1187981
[14:52] <desrt> fun!
[14:52] <desrt> maybe we should fork g-c-c...
[14:53] <desrt> (why didn't we do this already?!?)
[14:54] <seb128> because it's work and nobody did it (yet), and because have 2 different g-c-c on top of 1 g-s-d is impractical
[14:54] <seb128> so it requires some thinking about g-s-d, or also forking that ... but then it starts being tricky
[14:54] <jbicha> because we can *almost* make things work without forking
[14:54] <seb128> it might be easier to just 'fork' a few panels
[15:14]  * qengho had to flip to a VT, run "startx -- :4 -ac; sleep 5; DISPLAY=:4 xterm" to bootstrap a GUI this morning.  Ouch.
[15:20] <seb128> jbicha, seems like only plasma-widget-kimpanel is missing for the ibus transition ... did you talk to the kubuntu guys about it/do you plan an upload?
[15:21] <attente> seb128, can we upload a new accountsservice?
[15:22] <seb128> attente, hey, sure, what change do you need?
[15:23] <seb128> (I don't see a new upstream version nor a pending sponsoring request)
[15:23] <attente> seb128, it's for the input sources
[15:23] <attente> it's already proposed upstream
[15:23] <seb128> do you have the bug url?
[15:23] <attente> but it's still pending
[15:23] <seb128> ok
[15:23] <attente> https://bugs.freedesktop.org/show_bug.cgi?id=63086
[15:23] <ubot2`> Freedesktop bug 63086 in general "Add KeyboardLayouts property" [Enhancement,New]
[15:23] <seb128> did you talk to Stef about it?
[15:23] <attente> yes
[15:24] <attente> i should follow up again though
[15:24] <seb128> right
[15:24] <seb128> I would prefer if he could ack the name/format before we backport it
[15:25] <seb128> so we don't build on a variable type/format that might change
[15:26] <attente> seb128, ok, sounds good
[15:26] <seb128> attente, let me know when you hear back from Stef, then we can upload
[15:27] <attente> seb128, sure
[15:27] <seb128> attente, btw ibus 1.5 is in saucy-proposed, you can ping alesage about daily landing I think (that was blocked on ibus to be available iirc?)
[15:29] <alesage> seb128, ok I'll get that job going
[15:29] <seb128> alesage, thanks ;-)
[15:29] <alesage> attente ^^
[15:51] <asac> pitti: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1203655 ... is that the bug that causes my thinkpad to not go to sleep when i close the lid?
[15:51] <ubot2`> Ubuntu bug 1203655 in upower (Ubuntu) "Hangs in pthread_join in libusb_exit" [Undecided,Confirmed]
[15:52] <asac> larsu: ^
[15:52] <asac> let me know if you want me to extract something fro debugging or so
[15:52] <larsu> asac: I think it's related (I have the same issue), but I haven't had time to verify it yet
[15:52] <pitti> asac: I don't know; could be
[15:52] <pitti> asac: my laptop suspends just fine, and larsu couldn't reproduce it yet, I don't have any other data
[15:53]  * larsu had the unsuspended-laptop-in-backpack-problem because of that
[15:53] <pitti> I suspended/resumed it a lot over the weekend
[15:53] <larsu> pitti: I didn't have it in the last couple of das either. I'll keep an eye on it, though
[15:54] <asac> i can suspend through menu
[15:54] <asac> not when closing the lid
[15:55] <asac> it just goes in heat mode
[15:55] <pitti> asac: does it suspend when you Ctrl+Alt+F1 ?
[16:15] <seb128> Laney, larsu, kenvandine: hum, are the gsettings key value supposed to update on key change?
[16:16] <seb128> I'm doing
[16:16] <seb128>     GSettings {
[16:16] <seb128>         id: soundSettings
[16:16] <seb128>         schema.id: "com.ubuntu.touch.sound"
[16:16] <seb128> ...
[16:16] <seb128>             SilentModeWarning { visible: soundSettings.silentMode }
[16:16] <seb128> but the visibility doesn't toggle when the key change
[16:17] <seb128> if I do use a prop and do "onChanged: { if (key == "silentMode") silentMode = value" it works though
[16:17] <larsu> seb128: they are supposed to and there are tests that they do...
[16:17] <seb128> hum
[16:17] <seb128> I wonder what I'm doing wrong there
[16:17] <larsu> me too :)
[16:17] <larsu> it looks totally fine to me
[16:18] <larsu> any warnings when loading the script
[16:18] <larsu> ?
[16:18] <seb128> no
[16:18] <larsu> how are you changing the visibility, with gsettings set?
[16:18] <larsu> oops, silentMode of course
[16:19] <seb128> yes
[16:19] <seb128> and it works if I do "onChanged: { if (key == "silentMode") silentMode = value
[16:19] <seb128> in my GSettings {}
[16:20] <larsu> ah, right
[16:20] <kenvandine> that doesn't work
[16:20] <larsu> and you're sure the visible thing works?
[16:24] <seb128> larsu, http://paste.ubuntu.com/5925776/
[16:24] <seb128> $ gsettings set org.gnome.desktop.background show-desktop-icons false
[16:24] <seb128> $ gsettings set org.gnome.desktop.background show-desktop-icons true
[16:24] <seb128> does it change for you dynamically?
[16:26] <seb128> larsu: the previous version doesn't reflect changes for me, that one does: http://paste.ubuntu.com/5925784/
[16:26] <seb128> kenvandine, hey, "that doesn't work" ... you confirm what I'm seeing?
[16:27] <larsu> seb128: same problem here. Definitely a bug
[16:27] <seb128> larsu, ok, let me file one
[16:27] <larsu> seb128: let me finish ubiquity first please, I've had too many distractions today already :)
[16:27] <larsu> seb128: thanks!
[16:28] <xnox> larsu: yes, please, that =)
[16:29] <kenvandine> larsu, remember it doesn't automatically bind the property
[16:30] <kenvandine> at least that is what i seem to recall
[16:30] <larsu> kenvandine: well, it should in that direction
[16:30] <larsu> kenvandine: the problem was that it didn't in the other (checking a checkbox didn't update the key)
[16:30] <kenvandine> oh right
[16:30] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1206181
[16:30] <ubot2`> Ubuntu bug 1206181 in gsettings-qt (Ubuntu) "the properties don't get updated when the key value changes" [Undecided,New]
[16:30] <kenvandine> sorry for the confusion... :)
[16:31] <larsu> seb128: thanks
[16:31] <kenvandine> that did work :)
[16:31] <larsu> kenvandine: no worries
[16:31]  * kenvandine goes back to ofono
[16:31] <kenvandine> :)
[16:31] <seb128> larsu, sorry for adding to your day IRC ping-o-load (welcome to most of our days :p)
[16:31]  * seb128 goes for some exercice
[16:32] <kenvandine> seb128, btw i am able to get those serviceNumbers from ofono-qt just fine
[16:32] <larsu> seb128: enjoy!
[16:32] <kenvandine> just fighting a little exposing it to qml
[16:32] <seb128> kenvandine, nice!
[16:32] <kenvandine> should have it ready today
[16:32] <larsu> seb128: usually it doesn't bother me, but otday was just crazy
[16:34] <seb128> larsu, yeah, I know how it is when pings don't stop and you can focus 15 min on code ;-) Anyway going for some exercice, maybe you manage to get an hour of quiet hacking :p
[17:34] <larsu> xnox: https://code.launchpad.net/~larsu/ubiquity/fix-indicators/+merge/177438
[17:52] <larsu> seb128: thanks for bringing this to my attention, it was a regression that I introduced with the c++ split. Fixed and MRed, would love a review ;)
[17:56] <seb128> larsu, great, thanks for fixing it!
[18:08] <robru> pitti, hi, yes, I can have a look. where are the failures?
[19:27] <ritz> hi , could someone look at https://bugs.launchpad.net/indicator-session/+bug/1206231
[19:27] <ubot2`> ritz: Error: ubuntu bug 1206231 not found
[19:27] <ritz> wrong channel
[19:28] <ritz> hmmm, ubuntu-security ^^^
[19:29] <sarnold> hrm, I can't load it either.
[19:30] <ritz> sarnold adding you
[19:30] <ritz> not a very high prio
[19:30] <ritz> but annoying
[19:32] <ritz> sarnold mark this as public ?
[19:46] <desrt> seb128: hey.   been following the conversation?
[19:47] <desrt> i think we should drop per-user layouts at the login screen.  they don't make sense.
[19:47] <seb128> desrt, hey, hum, no ... where was that? #gnome-hackers?
[19:47] <desrt> ya
[19:47] <desrt> ah.  you're not there.
[19:47] <seb128> (I'm not on there anymore most of the time)
[19:47] <desrt> i think we should just have one global system default
[19:48] <desrt> the idea that the keyboard layout changes after you type the username but before the password is _really_ weird
[19:48] <desrt> (and only slightly less weird if you pick the user by mouse)
[19:48] <seb128> we don't type the username
[19:48] <seb128> we don't have a username entry
[19:48] <seb128> we click on it
[19:48] <desrt> i know.  please read again :)
[19:48] <seb128> and it makes sense to type the password in the keyboard layout you use
[19:49] <desrt> right... but a computer has a keyboard attached to it, right?
[19:49] <seb128> was that discussion mostly between qwerty users?
[19:49] <desrt> one particular kind of keyboard
[19:49] <desrt> like... in your case, we have a setting on a harddisk that's physically bolted into a machine that has an azerty keyboard on top
[19:49] <seb128> I'm typing azerty on qwerty keyboard (ok, not the majority but still)
[19:49] <desrt> so why not always use azerty at the login screen?
[19:50] <seb128> what about university kind of setups?
[19:50] <seb128> or libraries
[19:50] <seb128> or internet cafés
[19:50] <desrt> maybe...
[19:52] <seb128> well, the feature is no expensive to support and is handy in some cases
[19:52] <seb128> I guess we can keep it as Ubuntu specific if upstream is not interested
[19:52] <desrt> i'm trying to decide if upstream should be interested
[19:52] <desrt> or if ubuntu should drop the feature :p
[19:52] <seb128> the cost is lost, do they just object on principle? even if it's useless for 90% of users, it's not cluttering UI or creating work...
[19:52] <desrt> do you have your system keyboard layout configured to azerty?
[19:53] <seb128> is *low*
[19:53] <seb128> yes
[19:53] <seb128> but let's say I do a guest account for dholbach because I stay at his place for a while and he's going to use my laptop
[19:53] <seb128> he doesn't know azerty
[19:54] <seb128> he's probably going to use qwerty
[19:54] <seb128> well, I don't get what's the cost/issue to just have one list of values by user there
[19:54] <seb128> it's not the most useful feature in the world
[19:54] <seb128> but the cost is low...
[19:54] <desrt> well
[19:54] <desrt> my issue with it is that we now have the list of keyboard layouts used by the user in two places
[19:54] <desrt> accountsservice and gsettings
[19:54] <desrt> and we have to keep them in sync
[19:55] <desrt> also: it's not clear how we should select the default
[19:55] <jbicha> why does gsettings need the keyboard layout if accountsservice can do it?
[19:55] <desrt> probably we don't want the user changing the layout in the session with a hotkey to change what is used at the login screen next time
[19:55] <desrt> jbicha: accountsservice doesn't do it yet... at least not upstream
[19:56] <seb128> desrt, does changing in the session change what you get in the session at next login?
[19:56] <jbicha> right but when it does...
[19:56] <seb128> desrt, for me it's simple, we have a ordered list configured in gnome-control-center
[19:56] <seb128> the first item is the default
[19:56] <desrt> seb128: i don't know.  should it?
[19:56] <seb128> on the login screen and in the session
[19:56] <seb128> no
[19:57] <desrt> these are the questions i am currently trying to think through :)
[19:57] <attente> i guess it's a backwards compatibility issue? do we remove the schema if accountsservice handles it, or keep it and sync..
[19:57] <seb128> I think we should respect the configuration and always apply defaults on fresh boot/login
[19:57] <desrt> that's not how the session side currently works
[19:57] <desrt> it remembers the one from last time
[19:57] <seb128> the cycling you do in a session is in session state
[19:57] <desrt> whic is arguably bogus...
[19:58] <seb128> well
[19:58] <seb128> depends
[19:58] <seb128> do you use "keymap by win" option
[19:58] <desrt> lol
[19:58] <seb128> most people don't use the same input method/keymap in their im client and text editor
[19:58] <seb128> you code in C/english
[19:58] <seb128> you chat in your language
[19:58] <seb128> "lol" but welcome to keymap fun ;-)
[19:59] <seb128> default state should really be whatever you defined the default, at every login
[19:59] <seb128> then users change the config according to the context
[19:59] <desrt> i think i agree
[20:58] <sarnold> ritz_: public makes sense to me
[21:07] <chrisccoulson> does somebody want to maintain a browser?
[21:07] <mdeslaur> lol
[21:07] <sarnold> oh no, I'm not falling for that
[21:07] <chrisccoulson> :)
[21:09] <mdeslaur> IT'S A TRAP!
[21:09] <chrisccoulson> i'm just going to pop in to random IRC channels this week and ask the same question
[21:24] <seb128> chrisccoulson, which one are you giving away? ;-)
[21:25] <chrisccoulson> seb128, i only have one to give away ;)
[21:25] <seb128> chrisccoulson, I saw you uploading chromium recently! :p
[21:25] <chrisccoulson> seb128, oh, i just sponsor stuff for qengho