[00:28] <littlegirl> Hey there, I've gotten no response in #kubuntu or #ubuntu-doc so perhaps one of you may be interested. The https://wiki.kubuntu.org/Kubuntu/ContactUs page was last edited over 3 years ago and seems to be outdated.
[00:49] <Riddell> littlegirl: yes many of our wiki pages are outdates
[00:49] <Riddell> feel free to update them
[00:50] <littlegirl> Riddell: Who would know the up-to-date information so that I can put accurate info into the page?
[00:51] <Riddell> ask here if you are unsure what to say although it's late in European night so you might not get a quick response
[00:51] <littlegirl> Riddell: Are you in charge of Kubuntu documentation?
[00:52] <Riddell> littlegirl: in what context?  Darkwing writes most of the kubuntu-docs package
[00:53] <littlegirl> Riddell: I'm not sure. I guess I'd like to find out who to contact about being part of the Kubuntu documentation team. I'll ask in #ubuntu-doc. (:
[00:53] <Riddell> littlegirl: that'll be Darkwing
[00:54] <Riddell> littlegirl: David Wonderly david.wonderly @ kubuntu.org
[00:54] <Riddell> and tidying up our wiki pages would be a lovely first contribution :)
[00:55] <littlegirl> Riddell: Thanks. I'll get in touch with him. I've already tidied up some of the Ubuntu wiki pages in the past, but became frustrated because the documentation team preferred discussing changes to doing them, and I'm a doer. (:
[00:55] <Riddell> you'll find Kubuntu more do-ing in general :)
[00:56] <Riddell> however I'm away for the next few days, others will be around but if you don't get a response here just ask on the kubuntu-devel mailing list
[00:57] <littlegirl> Riddell: Good to know. I'll definitely get in touch with him. I think they'll appreciate what I can do since I'm a highly energetic, motivated person and just need to be given the ability to do things and pointed in the right direction. (:
[00:57] <littlegirl> I'll wait to hear from him. It's not a problem. (:
[00:57] <ScottK> littlegirl: For Kubuntu wiki pages, no need to wait.  Go for it.
[00:58] <littlegirl> ScottK: Will do. (:
[00:58] <ScottK> Ask questions here if you have them, but please be patient.
[00:58] <Riddell> yeah I don't think Darkwing has been around for a few days so don't wait on him
[00:58] <littlegirl> ScottK: I'll try. (:
[00:58] <littlegirl> Riddell: Okay, although I'd love to hear from him at some point as to exactly what he'd like of me. (:
[01:04] <ScottK> littlegirl: It's more important for you to find what you'd like to contribute.  If we try to drive your contribution, it won't last.  You need to find what scratches your contribution itch and do it.
[01:05] <Riddell> littlegirl: nixternal is also a guy who's done bits on wiki pages in the past so might be handy to ask
[01:09] <littlegirl> ScottK: Okay, not a problem.
[01:09] <littlegirl> Riddell: Do you have an email address for him as well?
[01:09] <ScottK> littlegirl: I think it's nixternal @ kubuntu.org.
[01:11] <littlegirl> ScottK: Thanks! I'll fire off an email to him, too. (:
[02:00] <apachelogger> nixternal: oh meh
[02:00] <apachelogger> nixternal: I shall look at their code then
[02:01] <apachelogger> cuz it aint not making no friggin sense and they did not bother to comment it because they probably also did not know and simply copynpasted that entire thing
[02:01] <apachelogger> which explains the lack of structure and proper en_us and proper everything
[03:53] <littlegirl> I'm not sure if you two (Riddell and ScottK) are still awake in here, but this is what I do to a page: https://wiki.kubuntu.org/Kubuntu/ContactUs#preview - you probably need to view the history of the page to see the difference. (:
[03:54] <littlegirl> Whoops - that should have been https://wiki.kubuntu.org/Kubuntu/ContactUs
[03:56] <ScottK> littlegirl: Seems good.
[03:57] <littlegirl> ScottK: Thanks. I just wanted both of you to know that I won't do anything malicious, but really do want to help. (:
[03:57] <Darkwing> Hey guys
[03:57] <ScottK> littlegirl: Sounds great.  We can use all the help we can get.
[03:57] <littlegirl> Hey there, I think you're the one I should be talking to. (:
[03:57] <ScottK> Darkwing: meet littlegirl.
[03:57] <ScottK> littlegirl: meet Darkwing.
[03:57] <littlegirl> LOL
[03:58] <Darkwing> Sorry I have been gone... Laptop stolen and I lost 100% of everything :(
[03:58] <littlegirl> Darkwing, I'm interested in helping with Kubuntu documentation. (:
[03:58] <Darkwing> hey littlegirl
[03:58] <ScottK> Darkwing: littlegirl wants to help on docs and wiki.
[03:58] <Darkwing> WHOOT!!!!!!!!!!!!!!!!!!!!!!!!!
[03:58] <littlegirl> Oh gosh, that's awful!
[03:58] <littlegirl> Darkwing: I hope you got it back, or got a replacement!
[03:58] <Darkwing> No, hard drive was encrypted so that's good.
[03:59] <Darkwing> I got a replacement thanks to ebay
[03:59] <littlegirl> I've helped with the Ubuntu wiki in the past, but got kind of frustrated with the ubunto-doc mailing list's interest in talking about things rather than doing things, so I kind of faded into the sunset. (:
[03:59] <littlegirl> Oh, good - I'm glad. (:
[04:00] <Darkwing> littlegirl: You going to be around tomorrow?
[04:00] <Darkwing> or rather... in about 16 hours? I'm GMT -0800
[04:00] <littlegirl> I've written and maintained a mostly linux blog (more of a web page, really) for years now, and written most of the content for the help pages of the WoaS wiki, and you're welcome to check any or all of that out to see what I can do. (:
[04:00] <littlegirl> Yep!
[04:01] <littlegirl> I'm on New York time. (:
[04:01] <Darkwing> Ok, I'm in San Diego
[04:02] <littlegirl> Blog: http://mostlylinux.wordpress.com WoaS wiki: http://sourceforge.net/projects/stickwiki/ BoaS (my version of WoaS that I redesigned and wrote more help pages for): http://bookonastick.wordpress.com/
[04:03] <littlegirl> And I'm always open to suggestion - like if you decide I'm too wordy or too stiff in my wording or anything else, I can work on it to make it better. (:
[04:03] <littlegirl> Also, I use Kubuntu, and have for years, so I'm comfortable in it. But although I can tinker around in Bash and JavaScript, I don't code in C or C++ or Python or anything, so I don't do any Kubuntu development.
[04:06] <Darkwing> Neither do I... That's why I do Docs and other such projects :D
[04:06] <Darkwing> You know HTML?
[04:06] <littlegirl> Yep, and CSS.
[04:07] <Darkwing> XML should be a streach then.
[04:07] <littlegirl> HTML was my first love. (:
[04:07] <Darkwing> shouldn't
[04:07] <Darkwing> Someone after my own heart.
[04:07] <littlegirl> hehe
[04:07] <Darkwing> HTML5?
[04:07] <littlegirl> Not sure. I just kind of read how to do whatever it is I need to know how to do and then use it. (:
[04:07] <littlegirl> I ask Google for a lot of help. (:
[04:08] <littlegirl> If you need me to know it, I could go check what's different about it and see if there's anything I need to learn.
[04:08] <Darkwing> Okay, well, XML and DocBook is what we use.
[04:08] <littlegirl> Ooooh, I don't know DocBook, and I hear that's a bit of a learning curve, right?
[04:09] <Darkwing> Not really.
[04:09] <littlegirl> I also don't know XML, but you seem confident that that won't be hard. (:
[04:09] <Darkwing> It's all tags like HTML. Trust me, you'll pick it up quick.
[04:09] <littlegirl> Ah, that doesn't sound bad. Is there a simple guide and maybe a cheat sheet for looking things up quickly after getting through the guide?
[04:10] <ScottK> It'll mostly be pretty obvious if you look at existing text.
[04:10] <Darkwing> ScottK: +1
[04:10] <Darkwing> littlegirl: I'll be on a bit later tonight and I'll be shoving a lit tomorrow.
[04:10] <ScottK> If you start with edits based on updating content it's easy enough to pick up the structure as you.
[04:11] <Darkwing> lit == lot
[04:11] <littlegirl> Ah, okay, that sounds pretty good. That's kind of how I do everything anyway - or at least how I got into everything (like HTML and JavaScript) to begin with. (:
[04:11] <littlegirl> Darkwing: What's shoving a lit?
[04:11] <Darkwing> shoving a lot
[04:12] <Darkwing> March 22nd is the doc freeze.
[04:12] <littlegirl> Darkwing: By the way, in case you missed it since you logged in after I wrote it, I just edited https://wiki.kubuntu.org/Kubuntu/ContactUs and brought it up to date, so you can see something recent I've done. ("
[04:13] <littlegirl> Oh! Well, I'd be happy to go over any docs you need help with. I'm good with grammar and spelling and read very quickly, so I can probably devour huge swaths of text and make sure it's good. (:
[04:13] <Darkwing> Oh this is going to be cool.
[04:14] <Darkwing> What's your schedule like tomorrow?
[04:14] <littlegirl> Darkwing: I'm available whenever you like, and I'm disabled and stay home, so my schedule is flexible. (:
[04:14] <Darkwing> littlegirl: sounds good. I'm always logged in so, I'll ping you when I get on tomorrow.
[04:15] <littlegirl> Darkwing: Okay, that sounds good, too. You said in about 16 hours?
[04:15] <Darkwing> prolly noonish my time... 3p your time.
[04:15] <littlegirl> Darkwing: Okay, I'll be on. (:
[04:15] <Darkwing> Sweet. :)
[04:16] <Darkwing> I need to finish getting stuff installed on my laptop.
[04:16] <littlegirl> It was good meeting you. (:
[04:16] <Darkwing> I'm Dave BTW
[04:16] <littlegirl> Okay, and thanks to ScottK and Riddell, too. (:
[04:16] <littlegirl> Darkwing: Ah, nice to meet you, Dave. I just go by Little Girl everywhere online. (:
[04:16] <Darkwing> Awesome.
[04:16]  * Darkwing departs for a few
[04:17] <littlegirl> Okay, good night, all. See you tomorrow. (:
[07:46] <jalcine> Wow, that update to Qt 4.8 threw off so much of my MOC code.
[08:09] <soee> hi
[08:10] <soee> do you know maybe if gwenview offers opacity effect ?
[08:12] <jussi> soee: in what way? editing photos?
[08:13] <soee> jussi, yes i just want to change image opacity
[08:13] <jussi> oooh, agateau! I just got gwenview to crash on precise. youll have a bug in a moment.
[08:14] <soee> works fine for me here :)
[08:14] <jussi> soee: I dont think so, Ive not seen it. (although thats not a confirmation)
[08:14] <soee> there is option to cut image so i thought that there will be opacity setting or something likne that
[08:15] <jussi> yeah, as I said, I havent seen one, but that doesnt mean there isnt one. (asking in #kubuntu would probably be a better place than here anyway)
[08:23] <Tm_T> soee: Gwenview is image viewer/manager, not editor, so it doesn't have much editing tools (:
[08:23] <soee> (:)
[09:41] <Riddell> gooten tag
[09:43] <brestows> are  you  wecomed ?
[09:43] <brestows> *welcomed
[09:44] <Riddell> oh hi brestows, did you get 4.8.1 tested?
[09:44] <brestows> Riddell: yes,  last night
[09:45] <Riddell> brestows: can you comment on https://wiki.kubuntu.org/Kubuntu/Ninjas/Packaging
[09:45] <Riddell> under "PPA Testing KDE 4.8.1 Precise"
[10:54] <agateau> Riddell: hi! if Zanshin 0.2.1 package from https://launchpad.net/~agateau/+archive/ppa/+packages looks good enough, can you upload it?
[11:12] <brestows> Riddell:  I will write the commentary, as soon as I analyse the updating results in detail
[12:20] <BluesKaj> Hi all
[12:47] <shadeslayer> ScottK: weird, clicking on notifications works just fine here
[12:48] <shadeslayer> ( in KTelepathy)
[13:12] <ScottK> shadeslayer: How about in plasma-netbook?
[13:13] <shadeslayer> uhh, not sure
[13:13] <shadeslayer> lemme check
[13:13] <ScottK> Sure.
[13:14] <shadeslayer> wfm
[13:18] <shadeslayer> ScottK: what does /usr/share/dbus-1/services/org.freedesktop.Telepathy.Client.KTp.Approver.service say ?
[13:18] <shadeslayer> and then the output of : qdbus org.kde.kded /kded org.kde.kded.loadModule ktp_approver
[13:18] <shadeslayer> oh, maybe I should mention that I'm using XMPP here, not AIM
[13:24] <starbuck> hello, i had an error with kubuntu backports upgrade to KDE 4.8
[13:24] <starbuck>  /var/cache/apt/archives/plasma-widgets-workspace_4%3a4.8.0b-0ubuntu1~oneiric1~ppa5_amd64.deb
[13:24] <starbuck> E: Sub-process /usr/bin/dpkg returned an error code (1)
[13:26] <ScottK> shadeslayer: Need to go get the netbook.  I'll let you know in a few.
[13:26] <shadeslayer> ok
[13:26] <shadeslayer> starbuck: Battlestar galactica fan ? :P
[13:27] <starbuck> haha, not really, never seen any episode...
[13:27] <starbuck> so does anyone know where this comes from?
[13:27] <shadeslayer> heh, what a coincidence then ...
[13:27] <yofel> starbuck: that's not enough from the error message
[13:27] <shadeslayer> starbuck: can you post more of the backlog?
[13:27] <yofel> or rather that piece is mmissing the actual error
[13:27] <shadeslayer> pastebin if it exceeds more than 3-4 lines
[13:29] <starbuck> it seems that some 4.8 packages "replace" 4.7.3 packages, but Ubuntu features 4.7.4 packages and these replace causes are now ignored for that package? i was able to fix it by apt -f install and then dist-upgrade again
[13:39] <ScottK> shadeslayer: http://paste.ubuntu.com/871434/
[13:39] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdepim] Philip Muškovac * 197 * debian/ (patches/0002-Fix-mem-leak.patch changelog patches/series) and 0002-Fix-mem-leak.patch from upstream KDE/4.8 branch
[13:39] <shadeslayer> looks good ...
[13:39] <ScottK> $ qdbus org.kde.kded /kded org.kde.kded.loadModule ktp_approver
[13:39] <ScottK> true
[13:40] <ScottK> shadeslayer: Please send me a highlight.
[13:40] <shadeslayer> ScottK: ok
[13:40] <ScottK> Today it works.
[13:40] <ScottK> Meh.
[13:40] <shadeslayer> ScottK: everything looks good, I'll have to investigate a bit deeper
[13:40] <shadeslayer> ...
[13:40] <ScottK> Oh, lost track.
[13:41] <ScottK> Quassel works.
[13:41] <shadeslayer> okay
[13:41] <ScottK> Still didn't make KDE Telepathy work.
[13:41] <shadeslayer> ScottK: can you check if the approver is running in the kded dialog thingy
[13:41] <shadeslayer> launch by typing "kded" in krunner
[13:41] <ScottK> OK.
[13:42] <ScottK> BTW, why does KDE Telepathy authentication handler have to access my wallet three times.
[13:42] <ScottK> Seems ineffecient.
[13:43] <shadeslayer> possibly because it has so many modules? Again, doesn't happen here
[13:44] <shadeslayer> ^ Speculating there, no proof that it actually does it
[13:44] <ScottK> Telepathy integration module is the only telepathy thing that shows up there.
[13:45] <shadeslayer> yeah, that's the one
[13:45] <ScottK> shadeslayer: Do you let stuff have access to the wallet once or do you approve it forever?
[13:45] <ScottK> If the later, you've no way of knowing.
[13:45] <shadeslayer> oh oh
[13:45] <shadeslayer> I also have a Instant Messaging approver
[13:45] <shadeslayer> ScottK: latter
[13:46] <ScottK> So you wouldn't see the multiple requests.
[13:46] <ScottK> Yeah, I have the IM approver too
[13:46] <ScottK> shadeslayer: Do AIM?
[13:46] <shadeslayer> nope, how long does it take to make a account?
[13:47] <ScottK> Not long
[13:47] <shadeslayer> give me 10 mins
[13:47] <ScottK> Of course I made mine in about 1996, so who knows.
[13:47] <shadeslayer> Uhh, I have no AIM entry in my account list btw ( When creating a account in ktp )
[13:47] <shadeslayer> gah
[13:47] <shadeslayer> it's called AOL, first entry
[13:48] <ScottK> Yeah.  That's what the A stands for.
[13:48] <shadeslayer> heh, I rarely hear of AOL these days
[13:48] <ScottK> Nor does anyone.
[13:48] <ScottK> My dad still uses it.
[13:49] <shadeslayer> iirc I had a friend who was interning at AOL about a year ago
[13:50] <ScottK> BTW, "Telepathy Contact List" is totally going to confuse people.  Not that "Kopete" is much better, but at least current users are used to it.
[13:52] <shadeslayer> ScottK: the usecase is more like : Click Plasmoid in the system tray and it brings up the contact list
[13:52] <shadeslayer> ScottK: email addy?
[13:52] <shadeslayer> for some AIM fails to connect on ktp
[14:01] <ScottK> shadeslayer: So "I want to IM someone".  What do I click on?
[14:02] <shadeslayer> ScottK: double click any contact
[14:02] <shadeslayer> should start a new text window
[14:03] <shadeslayer> ScottK: uh, question, how did you add your AIM account? I keep getting certificate errors
[14:03] <ScottK> Add account -> other -> AIM something or other.
[14:04] <shadeslayer> right, any special settings?
[14:04] <ScottK> Nope.  First and only thing I've done with KDE Telepathy.
[14:04] <shadeslayer> heh
[14:06] <shadeslayer> \o.
[14:06] <shadeslayer> \o/
[14:06] <rbelem> i've been using kde telepathy since the packages were announced
[14:06] <shadeslayer> figured it out
[14:06] <rbelem> no issues
[14:06] <rbelem> i use with three google accounts and one facebook
[14:06] <shadeslayer> ScottK: could you ping me?
[14:06] <shadeslayer> on AIM
[14:19] <ScottK> shadeslayer: In other news, did you see me pings re your digikam build?  http://paste.debian.net/158699/
[14:20] <shadeslayer> yes, I saw that when I was at college
[14:20] <shadeslayer> ffffuuuuuuuu
[14:22] <ScottK> Give me a diff for that, I'll apply it and resume the build.
[14:24] <shadeslayer> ScottK: 2 potential fixes for that, make digikam use the libkipi that we pull in or patch digikam's internal libkipi
[14:24] <shadeslayer> I'm inclined towards the former
[14:24]  * ScottK too
[14:24] <shadeslayer> okay, I'll dive into the icky CMake file then
[14:29] <shadeslayer> ScottK: http://mail.kde.org/pipermail/kde-telepathy/2011-June/002159.html << Possibly relevant discussion
[14:31] <shadeslayer> I'll brb
[14:31] <ScottK> shadeslayer: It does seem so.
[15:10] <shadeslayer> ScottK: hmm, okay, I don't see anything about internal kipi libraries being used
[15:10] <ScottK> Dunno.
[15:11] <shadeslayer> there's nothing related to internal kipi libs in CMakeLists.txt
[15:13] <shadeslayer> wtf
[15:14] <shadeslayer> oh, wrong build log
[15:14] <shadeslayer> @_@
[15:22] <shadeslayer> ScottK: http://paste.kde.org/434330/raw
[15:22] <shadeslayer> just replace kubuntu_fix_arm_build with that
[15:26] <ScottK> Building
[15:28] <shadeslayer> :)
[15:37] <BluesKaj> hey ScottK , shadeslayer, so far, so good, with kde 4.8.1 :)
[15:37] <shadeslayer> yay
[15:38] <ScottK> Riddell: ^^^
[16:38] <ScottK> yofel_: New kdepim tarball.
[17:05] <shadeslayer> ScottK: digikam update?
[17:05]  * ScottK looks
[17:06] <ScottK> asploded.
[17:06] <shadeslayer> uh
[17:06] <shadeslayer> is that uploaded or exploded?   Yes it is.
[17:09] <ScottK> OK
[17:11] <shadeslayer> yofel_: do you remember how we set up ARM stuff before?
[17:25] <shadeslayer> finally, https://wiki.kubuntu.org/shadeslayer/KubuntuDevApplication
[17:25] <shadeslayer> :D
[17:25] <shadeslayer> Riddell: yofel_ ^
[18:29] <CIA-42> [lp:~kubuntu-packagers/kubuntu-packaging/kdepim] Philip Muškovac * 198 * debian/ (4 files in 2 dirs) use new tarball and drop patches again
[18:36] <yofel_> shadeslayer: now send a mail to the ML and schedule a dev meeting
[18:36] <shadeslayer> yofel: will do
[18:36] <shadeslayer> sec
[18:36] <yofel> and thanks to reminding me re MOTU ^^
[18:37] <shadeslayer> yofel: http://people.ubuntu.com/~rohangarg/scripts/compress.sh
[18:37] <shadeslayer> :D
[18:37] <shadeslayer> yofel: also, I found something interesting, qemubuilder
[18:37] <shadeslayer> !info qemubuilder
[18:38] <yofel> hm
[18:38]  * yofel looks
[18:39]  * yofel installs
[18:39] <shadeslayer> :D
[18:39] <shadeslayer> setup instructions here : http://yoush.homelinux.org:8079/tech/setting-up-armel-qemubuilder
[18:50] <shadeslayer> yofel: which kernel are you using btw?
[18:51] <yofel> natty one
[18:51] <shadeslayer> O_O
[18:51] <shadeslayer> is that the only one available?
[18:52] <yofel> well, the wiki page still links to the lucid one, and natty is newest that still worked for me
[19:11] <yofel> shadeslayer: doesn't work http://paste.kde.org/434510
[19:12] <shadeslayer> 0.o
[19:12] <shadeslayer> give me a couple of minutes, I'm still setting up
[19:13] <yofel> shadeslayer: ignore me
[19:13] <yofel> $ qemu-system-arm
[19:13] <yofel> The program 'qemu-system-arm' is currently not installed.  You can install it by typing:
[19:13] <yofel> sudo apt-get install qemu-system
[19:13] <yofel> -.-
[19:13] <shadeslayer> heh
[19:19] <yofel> hm, now it's emulating the wrong cpu I think
[19:19] <yofel> pl181: Unexpected FIFO write
[19:22] <shadeslayer> yofel: grab this : http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux/linux-image-3.2.0-18-omap_3.2.0-18.28_armhf.deb , extract the deb and use the kernel in /boot/
[19:22] <shadeslayer> I wonder if ARCH=armhf is supported
[19:23] <shadeslayer> ( in qemu )
[19:33] <shadeslayer> Your architecture armhf does not seem to be supported
[19:33] <shadeslayer> hah
[19:44] <shadeslayer> yofel: did it work?
[19:50] <yofel> shadeslayer: not quite
[19:51] <yofel> I tried telling it to use a specific cpu, but now it tells me:
[19:51] <yofel> qemu-system-arm: -cpu cortex-a8: invalid option
[19:52] <shadeslayer> brr
[19:55] <yofel> k, I did it wrong
[19:55] <yofel> now I get a bit further before failing
[19:55] <shadeslayer> I'm a bit concerned about this tho " ... -append root=/dev/sda quiet init=/pbuilder-run ... "
[19:57] <shadeslayer> yofel: how do you sepcify the CPU type?
[19:58] <yofel> edited qemubuilder.c and rebuilt
[19:58] <shadeslayer> @_@
[19:59] <yofel> options are hardcoded
[19:59] <shadeslayer> what does it use by default?
[19:59] <yofel> the default - which isn't what we want it seems
[19:59] <shadeslayer> oh
[20:00] <yofel> blow qemubuilder.c line 309 add:
[20:00] <yofel>   0       argv[argc++]="-cpu";
[20:00] <yofel>   1       argv[argc++]="cortex-a8";
[20:00] <yofel> *below
[20:00] <yofel> - numbers at the beginning, that was vim
[20:02]  * yofel gives up on it for  today
[20:04] <shadeslayer> I'm still stuck on   forking qemu: qemu-system-arm -nodefaults -nographic -M versatilepb -m 1024 -kernel extracted_deb/boot/vmlinuz-3.2.0-18-omap -drive file=/home/shadeslayer/ubuntu/arm/base.qemu,index=0,media=disk,cache=writeback -drive file=/home/shadeslayer/ubuntu/arm/build/qemu.18091.dev,index=1,media=disk,cache=writeback -append root=/dev/sda quiet init=/pbuilder-run console=ttyAMA0,115200n8 -serial stdio -net user -net nic
[20:05] <shadeslayer> no idea why ...
[20:05] <yofel> !testers
[20:05] <yofel> !ninjas
[20:05] <shadeslayer> whut whut
[20:05] <yofel> 4.8.1 for oneiric finished building in ninjas
[20:05] <yofel> needs testing
[20:05] <shadeslayer> ah, don't have oneiric
[20:05]  * ScottK doesn't run PPA packages on his oneiric system.
[20:13] <ScottK> shadeslayer: You should talk about non-Kubuntu stuff in your application if you really want that to be a MOTU application too.
[20:14] <shadeslayer> ScottK: yeah, will update it before I send it for MOTU
[20:14] <ScottK> shadeslayer: Then I'd change the intro in the meantime then.
[20:14] <shadeslayer> ok
[20:28] <Riddell> evening
[20:30] <Riddell> agateau: I'm away until Friday so can't look at zanshin until then
[20:49] <shadeslayer> yofel: there's something seriously wrong with qemubuilder ...
[20:50] <shadeslayer> anyway, I'm off to sleep
[20:50] <shadeslayer> night
[21:46] <ScottK> 4.8.1 is released.
[21:46] <ScottK> yofel: Can you make the PPA packages public?
[21:46] <ScottK> Someone needs to upload to Precise too.
[21:48] <yofel> ScottK: I don't see the release annoucement mail yet
[21:48] <ScottK> It's on packager
[21:49] <ScottK> I think that's plenty good enough for our purposes.
[21:50] <yofel> that's the page update mail, not the release mail
[21:52] <Riddell> I just copy them over on the day of release
[21:52] <Riddell> since it takes time to do the copying and then testing that and ages to build it in the archive
[21:52] <Riddell> then I announce when sebas changes the kde.org pages
[21:53] <yofel> k, then I'll do the copying in a bit an upload kdelibs and meta
[21:54] <Riddell> we are already linked from http://kde.org/info/4.8.1.php
[21:56] <ScottK> Yep.  That's what was on packagers.
[21:56] <ScottK> yofel: It's constructively released at that point.  The packages are no longer private, so there's no reason to hold back.
[21:56] <yofel> well, ack, then
[21:56] <yofel> let's see...
[22:06] <yofel> oneiric copied
[22:06] <yofel> now to l10n
[22:08] <soee> hmm is there some ppa with gimp for precise ?
[22:08] <Riddell> soee -> #ubuntu
[22:08] <yofel> -> #ubuntu+1
[22:09] <soee> :)


[00:00] <mikodo> *upgrading testing  I meant
[00:06] <Unit193> amd64 (64bit): http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82111/testcases/1310/results and i386 (32bit): http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82112/testcases/1310/results
[00:06] <Unit193> You can choose whichever you'd prefer, or have installed already.
[00:06] <mikodo> Another question. What I am downloading is http://xubuntu.org/getxubuntu/  Should I just then update and upgrade it, then dist-upgrade it?
[00:09] <Unit193> Testcase should say, but  apt-get dist-upgrade  won't get you to the next release,  do-release-upgrade -d  (or whatever the testcase says) will though.
[00:10] <mikodo> Oh, what the ...! Should I be upgrading from Trusty or Xubuntu +1
[00:10] <Unit193> You upgrade from trusty to utopic.
[00:11] <mikodo> Unit193, Right on the apt-get release-upgrade. Thanks, for clarification on the trusty to utopic question.
[00:12] <Unit193> Sure, though  apt-get release-upgrade  isn't a command.
[00:12] <mikodo> I will check out the proper command. Thx
[00:30] <GridCube> elfy said the net upgrades where the recommended tests to do
[00:34] <mikodo> GridCube,  Do you have a link quickly available for me to get it from. Obviously, I am new to this
[00:35] <GridCube> mikodo, for 32 bit http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82112/testcases/1310/results
[00:36] <mikodo> Thanks.
[00:42] <mikodo> Just as Unit193 linked. :) Following links, is really slow with everything because of Transmission download.
[00:59] <bluesabre> good evening night owls
[00:59] <Unit193> It's only 9. :P
[01:00] <bluesabre> its late-ish
[01:00] <bluesabre> ~
[01:00] <bluesabre> xnox: thanks for taking a look... good news is that I have no idea why that happens, so that won't be fixed for utopic
[01:02] <Unit193> And he had a comment about feh too.
[01:09] <bluesabre> didn't see that one
[01:11] <Unit193> /lastlog in #xubuntu
[01:17] <bluesabre> ah, cool
[02:19]  * bluesabre adds changelog to http://pad.ubuntu.com/FinalReleaseNotes
[02:46] <bluesabre> knome, ochosi, forestpiskie: added changelog... maybe it will help for highlights
[05:11] <Unit193> FWIW, LP does have the bugs feature, but it's slow as heck and can barely hold the Open Source claim.
[06:45] <dkessel> good morning
[06:45] <dkessel> we have new images ready for testing :)
[06:47] <elfy> bah
[06:59] <elfy> knome: dragging bugs to the result form \o/
[07:10] <elfy> !team | new images landed - seeing more than me on the results would make for a happy elfy - so if you've time in the next 24 hours to do one - thanks :)
[07:15] <elfy> bluesabre: thanks for changelog on pad
[07:18] <elfy> I'll try and spend some time on that today - really don't want to rush tomorrow :)
[08:25] <ochosi> morning everyone
[08:25] <ochosi> just caught up on the meeting's notes
[09:56] <ochosi> bluesabre: are you gonna be around on the upcoming weekend?
[09:57] <ochosi> that, plus, what are your thoughts on last night's settling on lp over trello?
[09:57] <bluesabre> ochosi: I'll be in Ohio Saturday, probably around on Sunday
[09:57] <ochosi> what i'd like to do is a V planning session
[09:57] <ochosi> so we can set up blueprints asap
[09:58] <knome> elfy, it works? nice
[09:58] <bluesabre> I think lp is probably for the better... trello is nice, but its harder to get a clear picture of sectioned todo/doing/done
[09:58] <bluesabre> (for each team, that is)
[09:59] <ochosi> ok, good
[09:59] <knome> updated the processes page with the important translations
[09:59] <ochosi> just wanted to know whether there were any concerns from your side
[09:59] <bluesabre> none here
[09:59] <ochosi> knome: thanks, nice!
[09:59] <bluesabre> I'd be in favor of doing a blueprints sprint on sunday
[09:59] <ochosi> ok cool
[09:59] <ochosi> let's aim for that then
[09:59] <bluesabre> alrighty
[10:00] <ochosi> could send an email to team leads about that
[10:01] <ochosi> btw, has anyone heard from micahg in the "recent" past?
[10:01] <knome> no
[10:01] <knome> at least i haven't
[10:02] <bluesabre> he added me on linkedin a few weeks ago
[10:03] <knome> huhu
[10:21] <brainwash> bluesabre: did you ping the sru team? xfce4-weather-plugin is still stuck in -proposed
[10:22] <brainwash> furthermore, are you going to backport the fix to precise?
[10:23] <bluesabre> there is not really a way to backport the fix... but we might be able to backport the new plugin.  Completely different APIs and code since precise
[10:23] <bluesabre> but yeah, I intend to
[10:24] <brainwash> "Is there an update coming for precise? A locally built package with the same patches works on my system."
[10:24] <brainwash> last comment
[10:24] <brainwash> bug 1377612
[10:25] <brainwash> wait.. maybe he isn't talking about the version in precise
[10:25] <bluesabre> yeah, the version in precise is broken
[10:25] <bluesabre> it probably has been for a very, very long time
[10:28] <bluesabre> brainwash: pinged SRU team
[10:28] <brainwash> thanks
[10:37] <knome> 6 months support left for precise.. is it worth it?
[10:37] <knome> and does it send the right signal
[12:20] <jjfrv8> should I not be seeing the new Power Manager Plugin on my panel after an upgrade?
[12:46] <ochosi> jjfrv8: no, the plugin has to be added to the panel manually
[12:46] <ochosi> those who go trusty -> utopic keep indicator-power
[12:46] <elfy> hi ochosi
[12:46] <ochosi> hey elfy
[12:47] <jjfrv8> ok, thanks.
[12:47] <jjfrv8> I'm going to do a clean install on my laptop tonight to see if the screen dimming thing is upgrade-related or U-related.
[12:53] <knome> ochosi, is that in the release notes?
[12:57] <ochosi> knome: might not be there yet, will add it in
[13:08] <ochosi> ok, added
[13:08] <elfy> I'll try to spend a bit of time on those later today
[13:52] <slickymasterWork> ochosi, on Sunday at what time?
[13:53] <ochosi> just during the day
[13:53] <ochosi> since we're in different timezones
[14:04] <slickymasterWork> ok, hopefully not to early in the morning. I'm not what you might call a early bird :P
[14:05] <slickymasterWork> and I have a friend's wedding on saturday
[14:11] <ochosi> sure, no, i think it'll be spread out all over the day, depending on when people pop in
[14:38] <slickymasterWork> good
[15:14] <elfy> ochosi: should be about off and on all day sunday
[15:14] <ochosi> elfy: sounds good
[15:14] <ochosi> thought some early coordination might be good, especially with dev and testing in mind
[15:15] <ochosi> so that you know which areas are going to be worked on in advance and we can set up a clearer scheule
[15:15] <ochosi> schedule
[15:15] <elfy> yep
[15:15] <elfy> mostly what I need to do is work with *dev* so I'm able to set schedule with what might be happening
[15:16] <elfy> dkessel: I don't know if you've used trello and have an account - but I use it to deal with qa, so you're going to need to be able to use it
[15:17] <elfy> just doing a couple of hardware 64bit tests - as long as all is the same I'll be happy
[15:25] <dkessel> elfy: hmm yup I had an account to coordinate QA stuff with balloons - I just need to recover my login then I guess ;)
[15:26] <elfy> okey doke - once you're sorted let me know the trello name and I'll add you
[18:42] <elfy> started the web page release notes from the pad - sure it'll not be right ;)
[18:43] <knome> huhu
[18:43]  * knome looks
[18:43] <dkessel> hey knome
[18:43] <knome> hey dkessel
[18:44] <elfy> wasn't sure what to do with the changelog - that'll definitely want looking at
[18:44] <knome> yeah... maybe we should just drop it from the announcement and keep in the notes
[18:44] <knome> i guess you still have it in the pad?
[18:45] <elfy> knome: yea pad is still all there
[18:45] <elfy> might be daft - not silly :D
[18:45] <knome> ok
[18:46] <knome> do we have a release notes page on the wiki ready?
[18:47] <elfy> nope
[18:47] <knome> oki
[18:48] <knome> https://wiki.ubuntu.com/UtopicUnicorn/ReleaseNotes/Xubuntu
[18:48] <knome> now we do
[18:49] <elfy> knome: agreed with changelog - just on release notes I think
[18:50] <knome> hmm, wait
[18:50] <knome> shouldn't we be pointing to the xubuntu download page
[18:50] <knome> not the cdimage server?
[18:50] <elfy> guess so
[18:50] <elfy> I've not done anything with urls yet on either
[18:51] <GridCube> elfy, i tried to test yesterday but it failed to me :(
[18:51] <elfy> re changelog - perhaps keep removals/additions on the webpage
[18:51] <elfy> GridCube: I saw that - thanks for doing it anyway - got more than me on there now ;)
[18:52] <GridCube> P: great
[18:52] <elfy> also re changelog - keep some of it on the website - default setting changes for example
[18:53] <knome> ok, i'll back out of the website/wiki so others can poke them :)
[18:53] <knome> the wiki page is an almost straight copy of the b2 notes, so you'd might want to double-check that
[18:53] <elfy> knome: I'll not poke the website - don't know why I'd even do that lol
[18:54] <elfy> knome: I'll poke about with the wiki this evening
[18:54] <knome> worksforme ;)
[19:37] <elfy> knome: consider that poked
[19:39] <elfy> respins shortly ...
[19:42] <knome> yay
[19:44] <knome> http://en.wikipedia.org/wiki/Karelian_hot_pot
[19:44] <knome> today's dinner
[19:45] <knome> hmm, probably more appropriate for -offtopic, but whatever :P
[19:45] <elfy> lol
[19:45] <elfy> food is ontopic ...
[19:48]  * drc wonders if unicorn is an aceptable substitute for pork/beef/lamb?   Then it might be ontopic.
[19:52] <drc> looks like respins are up
[19:53] <drc> This going to be a "rename" for release tomorrow?
[19:53] <dkessel> what is the record for "number of respins on last day before release"?
[20:16] <knome> so, as far as we know now, release is targeted at middayish (UTC-4)
[20:16] <knome> who's going to be around then?
[20:18] <elfy> utc -4
[20:18] <elfy> mmm
[20:18] <knome> that converts to 16ish UTC :P
[20:18] <elfy> oh
[20:19] <elfy> right - I should be unless something odd happens
[20:20] <knome> ok, good
[20:20] <knome> i should also be around about that time
[20:20] <knome> just good to have a backup
[20:20] <elfy> yea
[20:22] <knome> and always better if both are around, so we can iron out the last bits if needed
[20:22] <elfy> yep
[20:22] <elfy> I guess bluesabre will be at work
[20:23] <elfy> not sure if ochosi will be about
[20:24] <elfy> I'll get some smoketests done in vms for the respins - looking at what's left tomorrow am
[20:25] <elfy> but I'm happy as long as they boot/install to mark ready
[20:40] <drc> well, weather report works...again.
[20:54] <Unit193> bluesabre, ochosi: Whichever I'm supposed to ping, https://launchpad.net/~unit193/+archive/ubuntu/xfce/+packages?field.name_filter=xfda
[21:00] <Unit193> Hmm, new hamster too, do we care about that one? :P
[21:06] <genii> What... is the XFCE getting a new rodent??
[21:21] <CajunTechie> Hey folks, what is the chan for the loco teams?
[21:24] <genii> CajunTechie: I'd hazard a guess it's #ubuntu-locoteams :)
[21:25] <CajunTechie> Oh yeah, I guess that kind of makes sense, huh genii? lol Thanks!
[21:25] <genii> np
[21:50] <Unit193> genii: xfce4-hamster-plugin is some strange plugin, not sure if it's really that useful to most people. :P
[21:51] <genii> Ah, OK
[22:09] <ochosi> Unit193: thanks, copying in process


[12:02] <head_victim> Evening all, Membership board meeting about to begin
[12:02] <cjohnston> morning
[12:02] <Pendulum> hiya :)
[12:02] <cyphermox> hey
[12:03] <micahg> hi
[12:03] <cyphermox> #startmeeting 1200 UTC Ubuntu Membership Board
[12:03] <meetingology> Meeting started Wed Jul 25 12:03:46 2012 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[12:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[12:04] <cyphermox> Hello and welcome to the Ubuntu Membership Review Board for the 1200 UTC meeting for July 25, 2012. The wiki page for the Review Board is available here: https://wiki.ubuntu.com/Membership/Boards
[12:04] <cyphermox> We will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off.
[12:04] <cyphermox> The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).
[12:04] <cyphermox> Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.
[12:04] <cyphermox> During this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.
[12:04] <cyphermox> When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the sum of those numbers is positive, then the applicant is now an official Ubuntu member! (feel free congratulate them!)
[12:05] <cyphermox> #voters cyphermox Pendulum head_victim micahg Destine
[12:05] <meetingology> Current voters: Destine Pendulum cyphermox head_victim micahg
[12:05] <cyphermox> Now, with any further ado, lets get started with the first applicant...
[12:06] <cyphermox> #subtopic Howard Chan
[12:06] <cyphermox> #link https://launchpad.net/~smartboyhw
[12:06] <cyphermox> #link https://wiki.ubuntu.com/smartboyhw
[12:06] <cyphermox> smartboyhw: please introduce yourself :)
[12:08] <cyphermox> smartboyhw: you around?
[12:11] <head_victim> Hmm appears absent
[12:12] <cyphermox> yup
[12:12] <Destine> any other applicant?
[12:12] <cyphermox> s9iper1 doesn't appear to be on either, sadly
[12:12] <smartboyhw> Hi
[12:12] <smartboyhw> Sorry, can't get it work
[12:12] <head_victim> Working now :)
[12:13] <smartboyhw> I'm a Ubuntu tester, helped in Alpha 2 and Daily Builds, I'm a real advanced user of Ubuntu, so Hello
[12:13] <Destine> smartboyhw, good, nice to meet you.
[12:13] <smartboyhw> When I mean Alpha 2 builds I mean 12.10
[12:14] <Destine> smartboyhw, yes, please go on.
[12:14] <smartboyhw> What should I say, then
[12:14] <smartboyhw> I am really looking forward to help the Ubuntu community
[12:14] <smartboyhw> Testing new builds and get the ISO's free of bugs
[12:15] <head_victim> smartboyhw: so my first question, how long have you been testing Ubuntu for and what aspect of testing have your contributed to?
[12:16] <head_victim> Your LP profile doesn't show a lot of bug activity so curious to learn more about testing
[12:16] <smartboyhw> I've been testing it since the first builds of 12.10 and I test about ISOs
[12:16] <smartboyhw> Try to see if there's any bug
[12:16] <smartboyhw> In the ISO QA Tracker
[12:17] <smartboyhw> I can provide a email that proves I
[12:17] <Destine> smartboyhw, i don't really see any bugs you reported through LP.
[12:17] <smartboyhw> The problem is, I don't find any bugs
[12:17] <smartboyhw> Strange, but I always got it no problem
[12:18] <Destine> smartboyhw, so despite the testing, what else do you do to contribute?
[12:18] <smartboyhw> I translated a few lines for Ubuntu
[12:18] <smartboyhw> Got some Karma
[12:18] <smartboyhw> In Traditional Chinese (Hong Kong)
[12:19] <head_victim> smartboyhw: is there anyone in the testing community that can vouch for your "significant and sustained contribution to Ubuntu" as required by the membership application?
[12:20] <smartboyhw> Here I don't know, but Nicholas Skaggs, the leader of ubuntu iso testing, ca n prove
[12:20] <smartboyhw> I have an e-mail
[12:20] <smartboyhw> Want that?
[12:21] <Destine> smartboyhw, can you please invite him here?
[12:21] <cyphermox> balloons: ?
[12:21] <cyphermox> ^
[12:22] <smartboyhw> Er, I don't know, I need to send an e-mail
[12:22] <smartboyhw> Which he may not see till sometime
[12:23] <smartboyhw> Maybe I really should send the email that proved I've contributed in the ISO testing of 12.10 Alpha 2
[12:23] <smartboyhw> To you guys
[12:24] <Destine> smartboyhw, we lookd for sustained contributions, no single email can prove that.
[12:24] <head_victim> smartboyhw: the problem we have is without being involved in QA ourselves we have no way to judge your contribution. We're thinking we should ask you to reapply next month with some signed testimonials of other QA testors that could state your level and length of involvement.
[12:24] <smartboyhw> WHAT???
[12:25] <Pendulum> smartboyhw: as a guideline, we generally look for a minimum 6 month involvement
[12:25] <Pendulum> smartboyhw: why do you want to be an Ubuntu member?
[12:25] <smartboyhw> I want to contribute more to the community
[12:25] <smartboyhw> Helping out
[12:25] <Destine> smartboyhw, ubuntu member is a reward.
[12:25] <smartboyhw> And I really wish to be a good Ubuntu comtributor
[12:25] <cyphermox> smartboyhw: What we're looking for is really *sustained and significant* contribution to Ubuntu; which is given as a kind of recognition of having done things in the community; you don't need it to contribute :)
[12:25] <head_victim> smartboyhw: Ubuntu membership is recognition of significant and sustained contributions, it's not permission to contribute. The contribution comes first.
[12:26] <smartboyhw> I know that is a reward
[12:26] <Destine> smartboyhw, to those who have already contributed enough.
[12:26] <smartboyhw> I think I had
[12:27] <Destine> smartboyhw, you did contribute, but not enough.
[12:27] <smartboyhw> Why?
[12:27] <cyphermox> smartboyhw: we think you should come back once you've done a bit more; and it would help a lot if you also had people who can vouch for what you
[12:27] <cyphermox> you've done
[12:28] <cyphermox> also, have you spoken and gotten involved with a LoCo team in your location?
[12:28] <smartboyhw> I have applied to join, but I think the team's dead
[12:28] <Pendulum> smartboyhw: we think you're doing good contributions, but you haven't being doing work for a sustained time period. We also look for testimonials from people you've worked with.
[12:28] <cyphermox> fair enough
[12:28] <smartboyhw> The HongKong LoCo Team
[12:28] <cyphermox> smartboyhw: reviving the team is one of the things you might want to try.
[12:29] <smartboyhw> Yeah, but I didn't get apporval to join from the leader
[12:29] <smartboyhw> So I can't revive
[12:29] <smartboyhw> I want to, but....
[12:29] <smartboyhw> The team leader didn't reply
[12:29] <Destine> smartboyhw, you might want to contact other members in the LoCo.
[12:29] <smartboyhw> Requested to join in Launchpad
[12:30] <cyphermox> I see
[12:30] <smartboyhw> Poor me, I'm crying now
[12:30] <smartboyhw> No one to support me, no Loco Team
[12:30] <cyphermox> have you only done the request to join or have you also sent an email, they might have missed the launchpad email
[12:30] <Pendulum> smartboyhw: if you really can't find the people who are already members of the LoCo, you may want to talk to the LoCo Council to see if they can help you at all.
[12:31] <smartboyhw> Okay, thanks
[12:31] <cyphermox> it's all good -- we appreciate the work you've done; we just think you should keep doing more and come back in a little while
[12:31] <smartboyhw> The question: How little while?
[12:31] <Destine> smartboyhw, maybe you can send me a email, i happen to know people who are involved in HK.
[12:32] <smartboyhw> What's your e-mail?
[12:32] <cyphermox> it depends. keep working on ISO testing for the release, then after release may be a good time; for instance if other iso testers or Nicholas can vouch for the work.
[12:33] <smartboyhw> Yeah, I'll be back after Final release
[12:33] <smartboyhw> Wait for me
[12:33] <smartboyhw> I failed
[12:34] <cyphermox> just don't hesitate to contribute where you can; iso testing isn't necessarily the only thing you may want to touch :)
[12:34] <Destine> smartboyhw, you are always welcome.
[12:34] <cyphermox> asking for help and asking people to write testimonials on your wiki page is always good, too
[12:34] <smartboyhw> Yeah, if Nicholas didn't get me a testimonial, I'll be dead
[12:34] <head_victim> smartboyhw: I had a bit of alook around, you might be able to join in with some locals - http://ubuntu.opensource.hk/
[12:35] <cyphermox> We still don't have any other applicants online, so let's wrap this up.
[12:35] <cyphermox> #endmeeting
[12:35] <meetingology> Meeting ended Wed Jul 25 12:35:18 2012 UTC.
[12:35] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-12.03.moin.txt
[12:35] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-12.03.html
[12:35] <smartboyhw> leave
[15:00]  * slangasek waves
[15:00]  * stgraber waves
[15:00]  * barry o/
[15:00]  * xnox is here =)
[15:01] <slangasek> #startmeeting
[15:01] <meetingology> Meeting started Wed Jul 25 15:01:35 2012 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:01] <slangasek> #topic lightning round
[15:01] <slangasek> $ echo $(shuf -e barry doko stgraber jodh ev bdmurray slangasek ogra infinity cjwatson xnox stokachu)
[15:01] <slangasek> barry slangasek infinity stgraber xnox ogra doko jodh cjwatson ev bdmurray stokachu
[15:01] <barry> win!
[15:02] <barry> bug 1020980; worked a bit on the pykde4 port for py3; mostly working on the xapian py3 port using both cython and swig.  not going so well - fighting many problems at all layers.  todo: probably time to move on.  done.
[15:04] <slangasek>  * last week: lots of work on UEFI at the plugfest
[15:04] <slangasek>  * this week: new upload of efilinux package, fixing bugs identified through UEFI interop testing; playing email catchup; A3 steering
[15:04] <slangasek> (done)
[15:04] <slangasek> no infinity, so stgraber:
[15:05] <stgraber> - Containers
[15:05] <stgraber>  - updated python binding for getkeys(), made set_config_item and get_config_item more clever
[15:05] <stgraber>  - implemented network config API (Container.network[index].key)
[15:05] <stgraber> - Networking
[15:05] <stgraber>  - Submitted IPv6 testing scripts to QA
[15:05] <stgraber>  - Found an isc-dhcp bug during alpha3 testing (apparmor preventing isc-dhcp-server from starting), fixed in time for a3
[15:05] <stgraber> - 12.04.1
[15:05] <stgraber>  - 12.04.1 team meeting and minutes
[15:05] <stgraber>  - Went through all the targeted/milestoned bugs for 12.04.1, updated status based on comments and queue status.
[15:05] <stgraber>  - Verified a bunch of SRUs.
[15:05] <stgraber>  - Uploaded a few more SRUs for bugs targeted to the point release (libxslt, sysvinit, krb5, resolvconf)
[15:06] <stgraber> - Image based system
[15:06] <stgraber>  - Started working on a proof of concept for foundations-q-image-based-updates
[15:06] <stgraber> - Queuebot
[15:06] <stgraber>  - Implemented packageset tracking in queuebot.
[15:06] <stgraber>  - Implemented per-channel filters, allowing packageset/queue/tracker notifications for flavours to be sent to their channel.
[15:06] <stgraber>  - Some performance and resource consumption improvements.
[15:06] <stgraber> - Other
[15:06] <stgraber>  - Alpha 3
[15:06] <stgraber>  - Bugfixes to sru-report to stop crashing on private bugs.
[15:06] <stgraber>  - Some ARB app review, the app showdown made the ARB New queue reach 140 packages... Still 50 to review...
[15:06] <stgraber> - TODO this week
[15:06] <stgraber>  - Continue the work on 12.04.1.
[15:06] <stgraber>  - Get a working proof of concept for foundations-q-image-based-updates allowing booting from multiple wubi images with a shared /home.
[15:06] <stgraber> (DONE)
[15:07] <xnox> * re-uploaded mdadm SRU, pending re-review from slangasek
[15:07] <xnox> * finished LUKS encryption design with mpt
[15:07] <xnox> * good progress on manual RAID design with mpt (last remaining design item)
[15:07] <xnox> * see Ubiquity Specification linked from https://wiki.ubuntu.com/Ubiquity
[15:07] <xnox> * Automatic LVM support merge into Ubiquity.
[15:07] <xnox> * Automatic Full-Disk encryption is almost ready locally, will
[15:07] <xnox>   make a merge proposal soon (coding/design done, testing/finding
[15:07] <xnox>   bugs now)
[15:07] <xnox> * Increased available limits on HpCloud for my account.
[15:07] <xnox> * Created a basic juju charm for Luca's cloud-scripts for full-archive rebuilds.
[15:07] <xnox> * I will be running ubuntu full archive rebuild probably this weekend.
[15:07] <xnox> * After that the small plan is to run:
[15:07] <xnox> - rebuild, upload the debs into a temprorary archive & rebuild
[15:07] <xnox>   the temporary archive using it's debs, to exercise the rebuild
[15:07] <xnox>   code
[15:07] <xnox> - rebuild with clang
[15:07] <xnox> - rebuild with python3.3 (if available)
[15:07] <xnox> * Went do debconf & delivered sponsors thank you bag to England:
[15:07] <slangasek> xnox: yep, re-reviewing on my list for this week
[15:07] <xnox> - awesome talks about ARM, multi-arch, clang, d-i & partman
[15:08] <xnox> - good discussions about archive rebuilds with wookey,doko
[15:08] <xnox> - progress on mdadm SRU, thanks to slangasek and infinity
[15:08] <xnox> slangasek: ;-) it will make stgraber happy if it gets accepted.
[15:08] <stgraber> I'm sure I'm not the only one being concerned that you own 10% of the 12.04.1 bugs ;)
[15:09] <slangasek> heh
[15:09] <ogra_> .. ?
[15:09] <xnox> ..
[15:09] <ogra_> done:
[15:09] <ogra_> * made arm server alternate work ... (sadly the switch to squashfs broke them again)
[15:09] <ogra_> * dug around in netinst breakage, at least these images work fine
[15:09] <ogra_> * repeated image tests of all arm images i have HW for (everything but mx5)
[15:09] <ogra_> todo:
[15:09] <ogra_> * QA sprint next week
[15:09] <ogra_> * fix remaining image and flash-kernel issues like:
[15:09] <ogra_> * bug 1028905
[15:09] <ogra_> * bug 746137
[15:09] <ogra_> * bug 1026780
[15:09] <ogra_> ..
[15:10] <jodh> For infinity (if he reads the scrollback now ;)...
[15:10] <jodh>
[15:10] <jodh> в Ўв Җв ғв •в •в һв Ңв Ҙв Ҹв Һв һв Ғв —в һв ұв Җв Һв һв Ғв һв ‘в Ӣв Ҙв Үв Җв —в ‘в Өв ‘в ӯв ‘в үв ұ
[15:10] <jodh> в Җв Җв Өв Җв ғв Үв •в үв …в ‘в ҷв Җв •в ғв ҡв ‘в үв һв Җв Һв ‘в —в Ҡв Ғв Үв Ҡв Һв Ғв һв Ҡв •в қв Ңв ҷв ‘в Һв ‘в —в Ҡв Ғв Үв Ҡв Һв Ғв һв Ҡв •в қв Җв қв •в әв Җв ”в ”в ©в Җв ҷв •в қв ‘в Ё
[15:10] <jodh> в Җв Җв Өв Җв үв Ғв қв Җв қв •в әв Җв Һв ‘в —в Ҡв Ғв Үв Ҡв Һв ‘в Җв Ғв қв ҷв Җв ҷв ‘в Һв ‘в —в Ҡв Ғв Үв Ҡв Һв ‘в Җв ҷв ғв Ҙв Һв Җв Қв ‘в Һв Һв Ғв ӣв ‘в Һв Ё
[15:10] <jodh> в Җв Җв Өв Җв қв ‘в ӯв һв Җв Һв һв Ғв ӣв ‘в Һв ұ
[15:10] <jodh> в Җв Җв Җв Җв Өв Җв Қв •в ҷв Ҡв Ӣв Ҫв Җв ‘в қв Ҙв Қв Җв “в Ғв қв ҷв Үв Ҡв қв ӣв Җв һв •в Җв “в Ғв қв ҷв Үв ‘в Җв ‘в қв Ҙв Қв Җв үв “в Ғв қв ӣв ‘в Һв Ё
[15:10] <jodh> в Җв Җв Җв Җв Өв Җв “в Ғв қв ҷв Үв ‘в Җв Ҹв һв —в Ғв үв ‘в ҷв Җв ҡв •в ғв Һв Ё
[15:10] <slangasek> infinity's not on the channel... :)
[15:10] <jodh> в Җв Җв Җв Җв Өв Җв үв •в қв Һв Ҡв ҷв ‘в —в Җв —в ‘в Өв ‘в ӯв ‘в үв Җв Һв үв ‘в қв Ғв —в Ҡв •в Һв Ё
[15:10] <jodh> в Җв Җв Җв Җв Өв Җв Ғв ҷв ҷв Җв Қв ‘в һв Ғв Өв “в ‘в Ғв ҷв ‘в —в Ё
[15:10] <slangasek> also: ahhhwhat
[15:10] <jodh> в Җв Җв Өв Җв ғв Ҙв ӣв Җв ”в Ұв ҙв ”в Ӯв ¶в ұв Җв үв •в қв һв Ҡв қв Ҙв Ҡв қв ӣв Җв Ҡв қв §в ‘в Һв һв Ҡв ӣв Ғв һв Ҡв •в қв Һв Ё
[15:10] <jodh> в Ўв Җв Қв Ҡв Һв үв ұв Җв •в қв Җв “в •в Үв Ҡв ҷв Ғв Ҫв Җв һв Ҙв ‘в Һв ҷв Ғв Ҫв Ё
[15:10] <jodh> бЈ«
[15:10] <jodh>
[15:11] <jodh> For those that don't do "tetris" (tm) ...
[15:11] <jodh>
[15:11] <jodh> * boot/upstart: stateful re-exec:
[15:11] <jodh>   - blocked object serialisation/deserialisation now 99% done.
[15:11] <slangasek> oh, braille
[15:11] <jodh>   - can now serialise and deserialise dbus messages.
[15:11] <jodh>   - next stages:
[15:11] <jodh>     - modify enum handling to handle enum changes.
[15:11] <jodh>     - handle ptraced jobs.
[15:11] <jodh>     - consider re-exec scenarios.
[15:11] <jodh>     - add meta-header.
[15:11] <jodh>   - bug 980917: continuing investigations.
[15:11] <jodh> * misc: on holiday Tuesday.
[15:11] <jodh> бЈ«
[15:11] <jodh>
[15:11] <jodh> slangasek: hence the scrollback comment ;)
[15:11] <slangasek> jodh: no, he's not connected to the channel
[15:12] <slangasek> so he won't have scrollback to see it in :)
[15:12] <jodh> oh well - he'll have to read it on irclogs :)
[15:12] <ogra_> poor boy missing all the barille fun
[15:12] <bdmurray> wrote a test case for SRU of bug 1006633 for precise and realized code was wrong
[15:12] <bdmurray> wrote and tested a new fix for bug 1006633 for quantal and precise
[15:12] <bdmurray> wrote, tested and uploaded a fix for bug 1007637 regarding blocking package installation failures
[15:12] <bdmurray> setup rls-mgr and qa team reports on cranberry as ubuntureports
[15:12] <bdmurray> removed code to create reports being made by arsenal from the ubuntu-reports branch
[15:12] <bdmurray> patch pilot
[15:12] <bdmurray> uploaded kerneloops that disables it due to crashers when trying to run the daemon
[15:12] <bdmurray> fixed gnuplot scripts that run on lillypilly and create pkgstats graphs
[15:12] <bdmurray> modify ultimate debian database code to mark same title bugs as duplicates
[15:13] <slangasek> yay test cases :)
[15:13] <slangasek> does "ubuntureports" mean urls are changing?
[15:14] <bdmurray> slangasek: no, just a different user that multiple people can su to and emails regarding cronjobs
[15:14] <slangasek> ok
[15:14] <slangasek> (done)?
[15:14] <bdmurray> yes, done
[15:15] <slangasek> stokachu: hi, anything to add this week?
[15:16] <slangasek> sounds like no
[15:16] <slangasek> moving on
[15:16] <slangasek> [TOPIC] 12.04.1
[15:16] <slangasek> stgraber: you have the floor :)
[15:16] <stgraber> yay!
[15:16] <stgraber> Full bug list can be found at: https://bugs.launchpad.net/ubuntu/precise/+bugs?field.milestone%3Alist=49926
[15:16] <stgraber> I went through the upload queue and updated the status of these bugs to In-progress so that I can get a better idea of what's going on.
[15:16] <stgraber> The biggest foundation-related SRU currently in the queue is mdadm, fixing one critical bug and 7 others but it's quite large and hasn't been reviewed yet.
[15:16] <stgraber> The list below is for any remaining foundation-related issue that's not marked "In progress" (waiting in unapproved) or "Fix commited" (currently in -proposed).
[15:16] <stgraber> We went from 33 bugs in last week's meeting down to 16 this week (granted, marking all of xnox's as in-progress helped quite a bit ;)!
[15:17] <stgraber> so, now to what's left to do:
[15:17] <stgraber> Package management: bug 1017001, bug 926340, bug 924079
[15:17] <stgraber> the first one is assigned to mvo but he's having a hard time trying to reproduce it, so not much progress was done on it
[15:18]  * slangasek nods
[15:18] <stgraber> Filesystem bugs: bug 978012
[15:18] <stgraber> this one was in the queue last week IIRC but isn't anymore, what happened?
[15:18] <stgraber> xnox: ?
[15:18] <xnox> this one, infinity rejected the upload. and said that he will discuss it with me tomorrow.
[15:18] <stgraber> ok
[15:19] <stgraber> Installer: bug 991982 (private, assigned to me), bug 484252, bug 946406, bug 966480, bug 987411
[15:19] <slangasek> bdmurray: are we much closer to being able to have apt clone attachments stay around again?  probably too late to do any good for bug #1017001 in .1, but seems the shortest path to getting that fixed regardless
[15:19] <stgraber> and bug 992061
[15:20] <stgraber> if we can't have bug 1017001 fixed for .1, we really should have a way to get apt-clones of these systems at least. I'm expecting quite a few of them to hit that failure as people start upgrading
[15:20] <bdmurray> slangasek: I think it is in the -proposed queue
[15:21] <slangasek> ah
[15:21] <stgraber> the casper bugs are quite racy, I spent most of Monday trying to reproduce them without much luck... asked for some more details but at this pace it seems less and less likely to be fixed for the point release
[15:21] <slangasek> bdmurray: apport/2.0.1-0ubuntu12?
[15:22] <bdmurray> slangasek: no, actually not as it needs a new apt-clone too
[15:22] <slangasek> bdmurray: ok
[15:22] <slangasek> bdmurray: can you make that a priority for this week?
[15:22] <bdmurray> slangasek: yes
[15:23] <slangasek> ta
[15:23] <stgraber> Boot: bug 980917
[15:23] <stgraber> Multi-arch (being worked on by stokachu and arges): bug 977947, bug 977952, bug 932860, bug 859600
[15:23] <stgraber> waiting on rdepends rebuild for these
[15:23] <stgraber> Other core packages: bug 523896
[15:24] <stgraber> on that list, the following bugs are currently unassigned (assigned to the team): bug 924079, bug 992061, bug 523896
[15:24] <bdmurray> slangasek: actually its update-manager and apt-clone that need uploading and there is currently an update-manager in precise-proposed that needs verifying
[15:24] <slangasek> can anyone here help with that update-manager verification?
[15:25] <slangasek> stgraber: when does the freeze for .1 go into effect?  End of the month?
[15:25] <stgraber> slangasek: 2nd of August
[15:26] <slangasek> ah, a thursday freeze :)
[15:26] <jibel_> bdmurray, u-m bug number that need verification ?
[15:26] <slangasek> so we have just over a week for uploads
[15:26] <bdmurray> jibel_: bug 1002956
[15:26] <jibel_> ta
[15:26] <slangasek> stgraber: I think the bugs that are not yet assigned to anyone need to be un-milestoned then
[15:26] <bdmurray> jibel_: and bug 979661 though it has no specific test case
[15:26] <slangasek> I don't think it's realistic that they're going to get fixes in the next week
[15:27] <stgraber> jibel_: the other bug in that SRU is a race condition, so not really verifyable, regression testing is good enough for that (I'd count the test of bug 1002956 as regression testing for bug 979661)
[15:27] <jibel_> ok, I'll do the verification
[15:28] <bdmurray> jibel_: great, thanks!
[15:28] <stgraber> slangasek: usb-creator was fixed in quantal, I'll assign it to me to look for a cherry-pick.
[15:28] <slangasek> stgraber: ah, great
[15:29] <stgraber> slangasek: the two others, I'll bump to .2 as they seem rather annoying and at least the shadow bug has been hitting quite a lot of people
[15:29] <slangasek> sorry, I assumed it was not-fixed-in-quantal, like most of the ones remaining
[15:29] <slangasek> yes, that sounds good
[15:29] <slangasek> as for the rest of the bugs... if you have a .1 bug assigned to you, please get the fix in BEFORE next Thursday
[15:30] <slangasek> or speak up now if you think you're not going to make that deadline
[15:30] <xnox> slangasek: is this deadline for: upload, accepted, or copied into -updates?
[15:30] <stgraber> upload, ideally accepted
[15:31] <jodh> slangasek: no guarantees on a fix for bug 980917 at this stage. I'll keep prodding though.
[15:31] <slangasek> yes - and definitely not the last
[15:31] <stgraber> we have an extra couple of weeks for veriyfying the fixes and getting them to -updates after that
[15:31] <slangasek> jodh: understood
[15:31] <xnox> well. I don't know what's up with e2fsprogs. mdadm bugs should be ok.
[15:32]  * slangasek nods
[15:32] <stgraber> I have two bugs that won't make it by next Thursday but that's on purpose as these will be pushed through -security at the last minute
[15:33] <slangasek> stgraber: anything else?
[15:34] <xnox> slangasek: i am guessing these deadlines are for stuff on the cd, e.g. do we have any multi-arch bugs pending from stokachu ?
[15:34] <slangasek> yes, these are the deadlines for images
[15:34] <slangasek> I think the multiarch bugs are the ones stgraber already covered
[15:34] <stgraber> slangasek: nope, that's it for 12.04.1
[15:35] <slangasek> stgraber: great, thanks for the update!
[15:35] <slangasek> [TOPIC] Bugs
[15:35] <slangasek> bdmurray: how about in quantal?
[15:35] <stgraber> slangasek: right, 4 multi-arch bugs are still pending, starting to wonder if they'll make it at all (still no rdepends rebuild test) ...
[15:36] <xnox> stgraber: hmm.. i have a cloud to do rdepends rebuild. What is needed? can be done very quickly.
[15:36] <bdmurray> bug 1022629 and 1024861 look like a recurrance of bug 541595
[15:37] <stgraber> xnox: rdepends rebuild using the packages in bugs 977947, 977952, 932860, 859600 (so, the usual, uploading the new library, waiting for it to build+publish, then upload no-change-rebuilds of all the rdepends and check that they still all build)
[15:38] <xnox> stgraber: ok. I can do that.
[15:38] <slangasek> xnox: thanks :)
[15:38] <xnox> nice smallish rebuild test with a small amount of packages (as in, not the whole archive ;-) just a bit of it )
[15:38] <stgraber> xnox: cool. If you do, let arges and stokachu know so you don't end up duplicating the work :)
[15:39] <slangasek> bdmurray: the logs in bug #1024861 don't give much to go on
[15:40] <slangasek> nor does bug #1022629, really
[15:40] <bdmurray> slangasek: what more do we need?  I suspect there are a lot of these
[15:40] <slangasek> bdmurray: well, the dpkg term log just looks truncated to me
[15:41] <slangasek> though maybe I'm just wishing it were truncated
[15:41] <bdmurray> well apport does truncate it to the last activity
[15:42] <slangasek> so I suspect that we may only be seeing logs from a "cleanup" run after some other failure
[15:42] <slangasek> and that we might need to know the nature of the original failure to understand the bug
[15:42] <bdmurray> okay, I'll ask for /var/log/apt/term.log then
[15:43] <slangasek> great, thanks
[15:43] <slangasek> anything else?
[15:44] <bdmurray> nope, things are getting resolved pretty quickly
[15:44] <slangasek> excellent :)
[15:44] <slangasek> [TOPIC] AOB
[15:45] <slangasek> going once...
[15:45] <slangasek> #endmeeting
[15:45] <meetingology> Meeting ended Wed Jul 25 15:45:52 2012 UTC.
[15:45] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-15.01.moin.txt
[15:45] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-15.01.html
[15:45] <slangasek> thanks all!
[15:45] <barry> thanks!
[15:45] <stgraber> thanks!
[15:46] <jodh> thanks!
[15:46] <xnox> cheers
[15:46] <ogra_> thanks !
[20:07] <phillw> #startmeeting Lubuntu Weekly Meeting
[20:07] <meetingology> Meeting started Wed Jul 25 20:07:43 2012 UTC.  The chair is phillw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:07] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[20:08] <phillw> hi, can we have a show of hands as to who is here
[20:08] <gilir> o/
[20:08] <Unit193> \o/
[20:09] <phillw> hmm, should be a short meeting, then!
[20:09] <gilir> :-)
[20:09] <phillw> #topic Update from Julien for 12.10
[20:10] <phillw> Can you bring us up to date on 12.10, please gilir
[20:10] <gilir> let me 1 min to find the link :)
[20:10] <phillw> np
[20:11] <gilir> https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha3#Lubuntu
[20:11] <gilir> so, most of the features have landed between A2 and A3
[20:12] <gilir> session manager had big modifications, but it should behave like the old one
[20:12] <gilir> as long as you don't enable the new features in the conf file, it should be just the same
[20:13] <gilir> the plan is to test them in this cycle, and build a nice GUI for the next cycle, to expose the new features
[20:14] <gilir> with this, pcmanfm was updated, and should be more stable now
[20:14] <gilir> this is 2 main changes that need to be tested
[20:14] <phillw> thanks, is there any documentation for the session manager?
[20:15] <gilir> there is also an update of the artwork (smaller than previous update)
[20:15] <gilir> there is a desktop.conf.example file in the package
[20:15] <phillw> thanks
[20:15] <gilir> you can also find it in lxde git
[20:16] <gilir> http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxsession;a=blob;f=data/desktop.conf.example;h=5d6bbbb9eee697a9200792f39793d854243c0833;hb=HEAD
[20:17] <gilir> except for the icons theme which is coming, the A3 should be close to the final release for the features
[20:17] <gilir> any questions ?
[20:17] <phillw> it's looking really good :)
[20:19] <phillw> #topic Update from QA Testing.
[20:19] <phillw> The good news is that there are no show-stopper bugs in the A3
[20:19] <gilir> cool :-)
[20:20] <phillw> http://iso.qa.ubuntu.com/qatracker/milestones/226/builds has the list of niggles found by the testers.
[20:20] <phillw> Just waiting on Lars to complete the suite for AMD64 + Mac
[20:21] <phillw> It was a curtailed test period (again), but we're good for a3 release :)
[20:21] <phillw> for the record, the bugs found are:
[20:21] <phillw> bug 1007674
[20:22] <phillw> bug 1009896
[20:22] <phillw> bug 967308
[20:23] <gilir> there is still a big oversize for every ISO, I'm not sure what is the real cause
[20:23] <gilir> the slideshow was not uploaded yet, but most of the changes are already done and ready for upload
[20:23] <phillw> Hmm, it does cause issues for the testers for powerpc. But they seem to have adapted.
[20:24] <phillw> does powerpc still have both browsers installed?
[20:24] <gilir> phillw, probably, but the change is done, just need to be uploaded
[20:25] <gilir> I can do it just after A3
[20:25] <phillw> okies, not sure how much over sized they currently are.
[20:25] <gilir> sorry, I was a bit late on this one :-(
[20:25] <phillw> it's okay. I know that the 'main' archs have to take priority of your scarce time.
[20:26] <phillw> It does rather seem that Lubuntu will be the only one flying the flag for PPC macs from now on. (So, no presuure then :P ).
[20:27] <gilir> :-)
[20:27] <phillw> kubuntu may do one, if they have time. Xubuntu are not doing & I think Ubuntu is too 'big' for powerpc computers
[20:28] <phillw> To have only a couple of niggles at A3 is a testament to the hard work of the dev team. You've produced a nice stable system again :)
[20:29] <phillw> I'd also like to note that the testers have, once again, been outstanding in getting bugs reported & following them up with more information when requested.
[20:30] <phillw> #topic Any Other Business
[20:30] <phillw> Unit193: you did mention something in the -ot channel. Do you want to repeat it here?
[20:31] <Unit193> They were going to sync all the access lists flags, so where some ops have +r and some don't, all would or would not.
[20:31] <Unit193> There was also syncing with launchpad goups.
[20:31] <Unit193> groups.
[20:33] <phillw> anyone else have something to raise?
[20:34] <phillw> #endmeeting
[20:34] <meetingology> Meeting ended Wed Jul 25 20:34:10 2012 UTC.
[20:34] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-20.07.moin.txt
[20:34] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-25-20.07.html
[20:34] <gilir> thanks phillw :-)
[20:34] <phillw> Thanks for making the time gilir - much appreciated.
[20:34] <Unit193> Danke.
[20:34] <Unit193> And I wonder what I forgot so far...
[20:35] <phillw> he he, gilir is it okay to schedule a meeting just before Beta 1 goes out in the wild?
[20:36] <Unit193> Also, if you wouldn't mind updating the Fridge calendar?


[02:23] <G-Kar> Is there a way to turn off the screen saver in 11.04? It keeps locking up the computer forcing a hard reboot
[02:25] <Unit193> G-Kar: Menu > Settings > Settings Manager
[02:28] <G-Kar> thanxs
[02:30] <G-Kar> I've another question. Does v11.04 run on a k6-2 (i486) cpu?
[02:31] <bazhang> G-Kar, doubt any recent distro will
[02:32] <G-Kar> yea; kinda what I thought. Even 10.04 has some problems with it
[02:34] <Unit193> LTS might
[03:25] <autif> I lost my sound, I am not sure why - may be after an upgrade. I executed "bash alsa-info.sh --stdout" as mentioned in https://help.ubuntu.com/community/SoundTroubleshootingProcedure step 3 (step 1 really). and my versions dont sync - The output I have is - Driver version:     1.0.23, Library version:    <IP_ADDRESS>, Utilities version:  <IP_ADDRESS> - So what can I do to get my sound back?
[03:32] <Josesordo> hi all
[03:40] <autif> !hi
[08:27] <ac001> does anyone know how to disable clicking on a laptop touchpad?
[08:27] <ac001> it's driving me nuts and I can't find a setting in the mouse control panel
[08:34] <knome> ac001, have you tried gsynaptics
[09:04] <MK``> I disabled it via the gnome mouse settings thing, I don't believe the default xfce mouse settings thing has an option for it heh
[11:59] <dmesg> Hi there, I just installed xubuntu but I have no idea how to connect my bluetooth mouse to it, any pointers?
[12:13] <xubuntu502> hi, im just installing the 11.04 Xubuntu and i must say i dont realy like the combined news section in the taskbar. but if i remove it, are there still the volume contro and network manager tools as fallback?
[14:47] <FreeHCK> hi, people!
[14:47] <FreeHCK> can somebody help me?
[14:48] <FreeHCK> i have a problem with system tray on xfce4-panel - it's very small...
[14:48] <FreeHCK> now i have 8 elements there, and ninth element is not visible.
[14:50] <FreeHCK> as a variant, i can make to be smaller icons in tray, but i want tray to be larger...
[14:51] <FreeHCK> hm... sorry, it was bug. now im seeing all 9 elements.
[15:01] <LetsGo67> Hello room!  i used to be a fan of Xubuntu, but then it became bloated.  Why?
[17:43] <gnarlygroundhog> Hi. What is the space requirement for Xubuntu Natty Narwhal?
[17:44] <zenrox> pretty much the same as ubuntu
[17:45] <gnarlygroundhog> Hm. Ok. I had noticed on Xubuntu's get page it listed this: "To install Xubuntu, you need 2.0 GB of free space on your hard disk."
[17:45] <gnarlygroundhog> Ubuntu Natty requires 4.4GB so it confused me..
[17:45] <drc> http://www.xubuntu.org/get
[17:45] <zenrox> ya xubuntu uses a lot from natty as the under the hood stuff
[17:46] <Sysi> gnarlygroundhog: how much do you got?
[18:11] <gnarlygroundhog> Only 3.8GB. Having to use USB drives until my hard drive arrives.
[19:15] <ryan-c> okay
[19:16] <ryan-c> my xfce keyboard shortcuts stopped working again :'(
[19:16] <ryan-c> wtf
[19:39] <Icanhasnicknamen> Hello, could anyone help me with an issue?
[19:39] <Icanhasnicknamen> hello? anyone online?
[19:40] <Unit193> !ask | Icanhasnicknamen
[19:40] <Icanhasnicknamen> Ok, sorry.
[19:41] <Icanhasnicknamen> My audio worked fine, until, well, now. It stopped definitely, and I don't know what else to try. I'm running version 11.04
[19:43] <Unit193> Icanhasnicknamen: What has changed? You checked all the settings in the volume manager?
[19:43] <Icanhasnicknamen> Well, there is only one sound channel (Master), and it is not muted.
[19:43] <Icanhasnicknamen> However, I have absolutely no audio...
[19:44] <Icanhasnicknamen> Btw, I will post lshw info
[19:44] <Icanhasnicknamen> http://paste.ubuntu.com/604186/
[19:46] <Unit193> Have you done any updates?
[19:47] <Icanhasnicknamen> Well, I installed oss4 package yesterday... could it be?
[19:47] <Icanhasnicknamen> I removed it btw, thinking he was the culprit
[19:50] <Unit193> You may have to change it so things are back to using alsa (I'm not really a audio guy) and:
[19:50] <Unit193> !audio
[19:52] <Icanhasnicknamen> That's the problem. I don't know how to restore stuff.
[19:52] <Icanhasnicknamen> My sound card is detected, but cannot work.
[19:53] <Icanhasnicknamen> http://paste.ubuntu.com/604191/
[19:53] <Icanhasnicknamen> Check out, I tried to modprobe him and this happens.
[19:55] <Unit193> In your gurb menu, do you have another kernel option? You could try that... (Or wait for one of the audio people to come back)
[19:56] <Icanhasnicknamen> Ok, I'll give a shot. Thanks for the help anyway =)
[21:40] <bc81> hi there.  my xubuntu installlation doesn't have an option to suspend, all i have is [Log Out] [Restart] [Shutdown].. where do i find the suspend option?
[21:44] <likemindead> Should be the session menu, top right (by default), bc81.
[21:50] <bc81> !panels
[21:51] <bc81> thanks, likemindead..i must have messed something up.  is there a command to reset panel to default as like ubuntu?
[21:57] <likemindead> What version of Xubuntu?
[21:59] <likemindead> Try Settings > Panels | Add new session menu?
[22:05] <hotquac> <3 xfce
[22:05] <hotquac> it's so snappy compared to the pig known as KDE
[22:05] <hotquac> and Unity can suck it
[22:06] <Liv-> <3 xfce ^^
[22:06] <hotquac> :D
[22:07] <Sysi> i'm gonna try gnome3, rumours tell it's nice with keyboard
[22:09] <Liv-> I'm still a noob... started with this last january hehe
[22:09] <Liv-> and I'm already loving it
[22:10] <drc> bc81: I <think> that RENAMING /home/<WHATEVER>/.config/xfce4/panel and restarting X (or reboot) should work...if it doesn't, just put the original ...../panel back <should> undo the change.
[22:10] <bc81> drc: thanks ill try that..you know how to restart x from the terminal?
[22:10] <drc> bc81: startx should work
[22:10] <bc81> k
[22:23] <Liv-> I can't make monochrome tray icons work. I've installed a few and nothing happened... :/
[22:27] <drc> Liv-: Define  "make monochrome icons work" ?
[22:31] <Liv-> I've installed different ones (like ubuntu-mono-dark and the whole faenza set) but they don't seem to change (the tray icons I mean)
[22:31] <Liv-> I've installed them through synaptic
[22:32] <Liv-> maybe it's just because they don't work? or do I need to do something else...?
[22:32] <drc> Liv-: Are you talkinig about the indicator-plugin or the Notification Area?
[22:33] <Liv-> the notification area, where the clock, volume control, etc icons are
[22:33] <Sysi> relogin
[22:33] <drc> What Sysi said :)
[22:36] <Liv-> mmh... I've tried that before and nothing happened...
[22:36] <Liv-> BUT...
[22:36] <Liv-> I've installed others this afternoon
[22:37] <Liv-> ok, I'll try again
[22:41] <Liv-> oh well
[22:41] <Liv-> nothing happened
[22:42] <Liv-> does not matter
[22:42] <Liv-> thanks you both anyway :)
[22:42] <drc> Liv-: I think the Notification Area Icons are different from normal iconq
[22:42] <drc> icons
[22:43] <Sysi> they're still going with icon theme
[22:43] <Liv-> maybe it's just that some icons won't change, I don't know
[22:43] <drc> The icon set has to have them in the set to show  up, otherwise they use a default icon.
[22:44] <drc> Liv-: What irc client are you using?
[22:45] <Liv-> xchat 2.8.8
[22:45] <drc> Ok
[22:45] <Liv-> the maverick default
[22:45] <Liv-> why?
[22:45] <tilleyrw> Why is my xubuntu desktop dull and boring versus Windows or MacOS which has clear and sharp borders & colors?
[22:45] <tilleyrw> I have the latest nVidia drivers installed.
[22:45] <drc> Liv-:  Try this...choose the elementary icon set...check out the icon (a bubble with the X in it)
[22:46] <tilleyrw> It's not the icon sets.  My screen UI is simply "fuzzy" with indistinct borders and soft fuzzy colors.
[22:47] <drc> Liv-:   The Notification Area icon is an X...Change the icon set to Tango, tie normal icon changes, but the NA icon does not.
[22:47] <Liv-> I had elementary xubuntu dark before and the chat icon is always an orange X that says "chat" in very small white letters
[22:48] <drc> The Same with pidgin, the normal icon is onething, but the notification icon is something else...
[22:48] <Liv-> whatever theme I choose, the chat icon is always the same
[22:48] <tilleyrw> Even my text in chat is fuzzy with indistinct boundaries.
[22:48] <Liv-> same with pidgin but that's another thing...
[22:48] <tilleyrw> I'm searching settings now.
[22:48] <drc> Liv-: in both the menu and the NA?
[22:49] <Liv-> yes, except with the elementary set
[22:49] <Liv-> which shows the white bubble as you said
[22:49] <Liv-> in the menu
[22:50] <tilleyrw> To whom are you chatting, Liv / drc?
[22:50] <tilleyrw> Who here can help me with a video interface issue?  I think the vid drivers aren't precise on my box.
[22:51] <drc> My point is...I <think> the Menu/Desktop and the NA icons are distict entities (may one is 25px and the others are 32...as an example), so if the icon set you change to does not have the NA subset, it will display a default icon.
[22:51] <drc> tilleyrw: not you
[22:51] <Liv-> seems they are different indeed
[22:52] <Liv-> for example if I want to change pidgin's NA icon I need to do something else (which requires root permission I think)
[22:53] <drc> Liv-: It could...I've never been that interested to find out (or am lazy, one or the other)
[22:54] <Liv-> hehe don't worry, I can live with that :)
[22:55] <drc> tilleyrw: As for fonts, have you looked at Menu>Settings>Settings Manager>Appearence>Fonts?
[22:56] <drc> tilleyrw: I use 1) Enable Anti-aliasing, 2) Hinting = Full and 3) Sub-pixel order = RGB, and my fonts are very precise
[22:57] <drc> tilleyrw: You do know it's considered rude to initiate a PM without asking, don't you?
[22:59] <drc> tilleyrw: I also replace the default (Droid?) with DejaVu Sans Book.
[23:01] <drc> tilleyrw: Also, look at Menu>Settings>Settings Manager>Windows Manager Tweaks and turn off Compositor and see if that helps
[23:05] <tilleyrw> Where are Font adjustments?  I don't see a Fonts module.
[23:06] <drc> tilleyrw: Menu>Settins>Settings Manager>Appearence> Fonts
[23:06] <tilleyrw> Thank you kind friend.
[23:06] <drc> np :)
[23:07] <drc> If these Don't help, you might make sure that your running your monitors native resolution (whatever that is)
[23:08] <drc> tilleyrw: You do know it's considered rude to initiate a PM without asking, don't you? Redux.
[23:10] <drc> tilleyrw: Besides, asking question in the channel allows others to follow the converstion and either learn or add their ideas.
[23:10] <Liv-> tilleyrw: have you tried setting the hinting to "none"?
[23:10] <drc> And sometime correct the advisor when then make an error :(
[23:10] <Liv-> if I put "ful" as you said, it looks awful in my monitor
[23:11] <Liv-> *full
[23:12] <drc> Yup...it depends on the card/monitor/eyes :)  YMMV as they say.
[23:13] <drc> Pupply Play Time...back later
[23:15] <tilleyrw> How do I change my maximum screen resolution?  I need 1280x1024.  The largest in the menu is 1024x768.
[23:21] <tilleyrw> How can I change my max screen res if the size isn't listed?  My max says 1024x768 when I need 1280x1024.
[23:21] <Liv-> maybe you can't change it to a larger resolution than that
[23:22] <Liv-> or maybe yes, through the terminal... but I don't know any commands for that
[23:23] <tilleyrw> I'll try editing x.conf.
[23:23] <tilleyrw> It may be a driver thing though.  :(
[23:23] <Liv-> maybe :/
[23:25] <hotquac> it's probably a driver thing


[00:17] <RAOF> I'm *sure* I've added close() to drm_fd_handler before...
[00:43] <RAOF> Interesting: http://kentonv.github.com/capnproto/index.html
[01:57] <duflu> kgunn: Isn't your day long enough already? :)
[03:01] <duflu> robert_ancell: Can we please have milestones and code on the same series? https://launchpad.net/mir
[03:01] <duflu> ... one way or the other
[03:04] <robert_ancell> duflu, as kgunn said, Launchpad won't let us delete the 13.05 milestone. I did manage to delete the 14.04 series by moving the milestone
[03:06] <robert_ancell> duflu, I've set the 13.05 milestone to inactive, so that seems to workaround LP being confused
[03:06] <robert_ancell> duflu, solved?
[03:07] <duflu> robert_ancell: OK, ta. Still need an active milestone > 0.0.2 to link our Fix Committed bugs to
[03:07] <robert_ancell> duflu, ok, I'll open a 0.0.3
[03:08] <robert_ancell> duflu, done
[03:08] <robert_ancell> brb
[05:10] <tvoss> RAOF, cap'n'proto is indeed interesting, but I have had difficulties figuring out if it's done, yet
[05:13] <smspillaz> tvoss: oh yeah, I was going to mention that one to you
[05:13] <smspillaz> saw it on reddit the other day
[05:33] <RAOF> tvoss: It's not done yet.
[05:33] <tvoss> RAOF, that's what I thought, too. However, it looks pretty promising. Do we know the author?
[05:34] <RAOF> I don't, except that he's also the primary author of Google Protobuf
[06:11] <RAOF> racarr: There doesn't seem to be anything in the EGL specification that prohibits the behaviour your inprocess-egl patch introduces (which is good ☺). I'll check that it doesn't indirectly break something.
[06:26] <tvoss> RAOF, do we have a video of racarr's in process egl work, yet?
[06:31] <RAOF> tvoss: not afaik
[08:24] <duflu> mmrazik: Looks like Mir no longer needs -DMIR_DISABLE_INPUT=ON for clang. And we're about to remove that option too. Can we update CI?
[08:25] <mmrazik> duflu: sure. removing it....
[08:26] <duflu> mmrazik: Thanks
[08:26] <mmrazik> duflu: done
[08:26]  * tvoss thinks that the CI jobs should do twitter, too :)
[08:27] <duflu> Well, CI output is useful. Twitter is not usually used for useful things...
[08:27] <duflu> I suppose it could be
[08:28] <tvoss> duflu, but given jenkins' karma on launchpad, it might be considered a conscious being, and nowadays it's tweeto ergo sum :)
[08:28] <duflu> Codito ergo sum
[08:28] <tvoss> duflu, ;9
[08:29] <tvoss> probaro ergo sum
[08:29] <smspillaz> duflu: thanks for updating the other mps :)
[08:30] <duflu> smspillaz: No problem. Accurate MPs and bugs are useful
[08:30] <smspillaz> alan_g: tvoss: question about unique_ptr. Is doing something like std::unique_ptr <Derived> d (new Derived); std::unique_ptr <Base> b (d); known to work ?
[08:31] <tvoss> smspillaz, at least, d would need to be moved to b
[08:31] <smspillaz> tvoss: does that need to happen explicitly? eg std::move () ?
[08:32] <alan_g> smspillaz: give or take a std::move, yes
[08:32] <smspillaz> I'm getting this weird problem where even if I do std::unique_ptr <Derived> d (new Derived); std::unique_ptr <Base> const &b (d); seems to not work either and tries to just move it
[08:32] <smspillaz> which fails
[08:33] <tvoss> smspillaz, yes, a move has to be explicit
[08:33] <tvoss> smspillaz, it would need to be std::unique_ptr <Base> b(std::move(d));
[08:33] <smspillaz> hm
[08:34] <smspillaz> well, I guess my main problem at the moment is that I can't take a const ref either, and I thought it was something to do with the fact that moving wasn't supported
[08:35] <smspillaz> hmm, seems to work if I use std::move although that certainly feels wrong
[08:38] <RAOF> Why does that feel wrong?
[08:39] <smspillaz> std::unique_ptr <MockFoo> mock;
[08:39] <smspillaz> * set some expectations
[08:40] <smspillaz> bar (std::move (mock)) <- expects a std::unique_ptr <Foo> const &
[08:40] <smspillaz> * how do you set more expectations ?
[08:40] <smspillaz> the function wants a non-owning reference to the pointer, yet you have to give it the whole pointer
[08:42] <RAOF> Start with a std::shared_ptr<MockFoo>?
[08:42] <RAOF> I mean, if you're going to hand references out to it, it's not a unique_ptr.
[08:43] <RAOF> Oh, whoops.
[08:43] <duflu> Surely that's why you can only "swap" unique_ptrs. If you could assign them (or even copy by initializer), they'd no longer be unique
[08:43] <smspillaz> RAOF: well, I don't want shared *ownership*
[08:43] <smspillaz> duflu: you can move them
[08:43] <smspillaz> which is effectively like swapping
[08:43] <duflu> Fairy nuff
[08:43] <smspillaz> the point is that I don't want to copy or move it
[08:43] <smspillaz> I want to give a reference to its base
[08:44] <RAOF> Get a raw pointer out of it and send that?
[08:44] <duflu> RAOF: That's violating the uniqueness too
[08:44] <smspillaz> duflu: I want a const &
[08:44] <alan_g> smspillaz: a reference to base is spelt "Base const&" not "std::unique_ptr <Base> const &"
[08:45] <smspillaz> alan_g: reference to the unique pointer to the base
[08:45] <smspillaz> so I should be able to go from
[08:45] <smspillaz> std::unique_ptr <Derived> d (new Derived)
[08:45] <smspillaz> to std::unique_ptr <Base> const &b
[08:46] <smspillaz> because you can do that with shared pointers and it doesn't give out any new ownership
[08:46] <alan_g> smspillaz: not within the language rules - smart pointers to different types cannont be covarient
[08:46]  * smspillaz wonders why it worked with boost
[08:46] <alan_g> or contravarient
[08:46] <smspillaz> ... probably because there was an implicit copy
[08:50] <alan_g> smspillaz: c++03 doesn't have move semantics
[09:20] <alan_g> alf_: Looking at enable-inprocess-egl again got me wondering how(if) we are managing dependencies on bespoke mesa. Should we be ensuring that mesa patches are in the ppa before landing branches that need them?
[09:23] <alf_> alan_g: I would say the other way around, since mesa depends on the mir API and there is a chance it won't build if we land the mesa change first
[09:24] <alf_> alan_g: (depends on the details of the change, of course)
[09:24] <alan_g> alf_: Yeah. Why can't things be simple. ;)
[09:26]  * alan_g wishes for one big source tree with everything in it . (That also builds quickly.)
[10:00] <duflu> Hey lp:omniverse doesn't exist yet ;)
[10:18] <smspillaz> alan_g: hmm, I guess the best option then is to just pass the object by const reference
[10:18] <smspillaz> and don't make any functions that want a reference to the object a const ref to the unique_ptr
[10:18]  * smspillaz wishes C++ had rust-like pointers
[11:27] <tvoss> alan_g, ping
[11:30] <alan_g> tvoss: pong
[12:46] <kgunn> alf_: reading you control loop thread again...was thinking, would rotate be an event? (think phone/tablet)
[12:47] <kgunn> alf_: its sort of like a display reconfig event
[12:48] <kgunn> anyway....more arguments/use cases for your idea
[12:49] <alf_> kgunn: thanks, it could be... it depends on how we need to react to it. Perhaps it is just part of the reconfiguration process as you said, but I haven't thought this through.
[15:10] <kdub> morning
[15:10] <tvoss> kdub, good morning :)
[15:11] <alan_g|tea> kdub: morning
[15:11]  * alan_g remembers to change nick
[15:53] <alf_> status: Thinking about main loop, working on a main loop prototype (see message in mir-devel thread), reviewing
[15:57] <kdub> oh yeah, statuses! your nexus 4's now work :) working still on the framebuffer native window type, improving things in the core as I go
[15:58] <kdub> so if something weird now happens on the nexus4, file a bug about it (in case its been getting a pass on funny functionality until now)
[15:59] <tvoss> kdub, \o/
[16:04] <alf_> kdub: now that you mention it, using the latest lp:mir I don't get any screen updates on the nexus 4 :/ I see only the first frame
[16:06] <alf_> kdub: I will file a bug
[16:06] <kdub> alf_, thats a good bug :) let me see  if i can reproduce
[16:06] <kdub> alf_, if you remember, put the version of the phablet image you're using
[16:07] <alf_> kdub: hmm, perhaps I should update to the latest image first and try again?
[16:08] <kdub> alf_, the other thing is, make sure surfaceflinger is not running... its very aggressive about restarting
[16:13] <kgunn> kdub: not if you rename it :)
[16:13] <kgunn> its your trick....and fool proof
[16:14] <alan_g> status: reviewing, trying to understand enough bits to spike "hardware cursor"
[16:19] <racarr> Morning
[16:28] <alf_> alan_g: @hardware cursor, anything I can help with?
[16:29] <alan_g> alf_: can we hangout in the morning?
[16:29] <alf_> alan_g: sure
[16:49] <racarr> alan_g: Pushed some updates to receive-input-in-client (r622, r623)
[16:49] <kdub> alf_, i just tried with ubuntu-touch-image 56 (latest build i could find) and lp:mir. seems ok to me
[16:50] <alan_g> racarr: looking...
[16:54] <kdub> alf_, actually, i see render_surfaces being weird, but the server seems ok to me. i'll file a bug on that
[16:54] <racarr> kdub: Processed your comments on inprocess-egl will wok on them later today (maybe we can talk some about names, etc...)
[16:55] <kdub> racarr, sure, before you set down to change the names, lets figure out what they should be... its annoying to change 2x
[16:55]  * kdub has been wanting to improve 'inprocess egl' as a name for a while
[16:55] <kdub> all egl is in a process! :P
[16:56] <racarr> Except for the great cosmic background EGL that surrounds and binds us all
[16:56] <racarr> (All praise *3 quick bows*)
[16:58] <alan_g|EOD> Goodbye all!
[16:58] <racarr> Good Evening :)
[17:01] <kgunn> evnin'
[17:02] <alf_> alan_g|EOD: goodbye
[17:02] <alf_> kdub: I am still getting the problem with latest image, will check more tomorrow
[17:04] <kdub> racarr, with input enabled on android, do these errors look sensible for the state of the code? https://pastebin.canonical.com/88338/
[17:54] <racarr> kdub: Those errors are pretty good yeah
[17:55] <racarr> I want to work on reporting for droidinput but it's
[17:55] <racarr> difficult
[17:55] <racarr> We need a different pattern
[17:55] <racarr> the Reporter interface for say EventHub alone
[17:55] <racarr> would have like
[17:55] <racarr> 40 methods
[17:57] <racarr> status: Doing a final self review round, etc on receive-input-in-client
[17:57] <racarr> so hopefully it can land this afternoon?
[18:06] <racarr> Can someone approve https://code.launchpad.net/~robertcarr/mir/dedupe-null-input-managers/+merge/156645
[18:07] <racarr> so I can approve https://code.launchpad.net/~robertcarr/mir/remove-mir-disable-input/+merge/156696
[18:07] <racarr> so I can avoid
[18:07] <racarr> merging it in to remove-mir-disable-input
[18:07] <racarr> or a merge conflict later
[18:07] <racarr> well not a conflict actually
[18:07] <racarr> just something we have to remember to fix XD
[18:18]  * kdub is unaware of a rule that you can't tick to approve, granted all the review comments are addressed and you have an approve with no blocking reviews
[18:23] <kdub> surfaceflinger's rendering portions sometimes looks like a big switch statement based on hwc version
[19:18] <kgunn> kdub: was just thinking about yesterday - you were wanting to look into resize
[19:18] <kgunn> i was looking at the bp for mir-phone-iteration-0
[19:19] <kgunn> seems duflu is doing "client  initiated maximize/fullscreen"
[19:19] <kgunn> might want to ping him or g+ hangout w him later and see what he's up to exactly
[19:20] <kdub> kgunn, one can be a dependency of the other
[19:20] <kdub> i'd imagine that task is more negotiating the request over ipc
[19:21] <kdub> and then the other half is doing the allocation/deallocation on the server side
[19:21] <kgunn> kdub: agreed its a subset...just worthy of a 2 minute chat
[19:24] <kdub> kgunn, sure.. maybe before the mir2 meeting?
[19:31] <kgunn> kdub: might be early for him
[20:46] <kdub> i kinda want to write a doc explaining the sometimes-annoying display infrastructure that android has... should that go in our doc/ folder or somewhere else?
[20:50] <kgunn> our docs, in so far as our implementation accounts for it
[20:54] <thomi> Hi everyone... Is there an alternative to switching to VT1 to run mir? That's reasonably difficult to automate in a jenkins slave
[20:54] <thomi> if I don't care that my X session will die afterwards, is there some other way?
[21:02] <robert_ancell> kgunn, are you meeting today?
[21:45] <kgunn> kdub: is this that hybris branch https://code.launchpad.net/~rocket-scientists/aal+/ubuntu-platform-api_replace_hybris_hardcoded_path
[21:46] <kdub> kgunn, https://code.launchpad.net/~kdub/aal+/shared-pthread-poc
[21:46] <kgunn> kdub: thanks...
[21:46] <kdub> but we shouldn't be pointing people to it i think, its not really production quality
[21:47] <kdub> in public docs, i'd say
[21:47] <kgunn> kdub: right...i was going to pester pat's team :) just needed the stick to poke with
[22:21] <RAOF> racarr: Ok, EGL. Are you sure that all your changes are necessary? Specifically - the change to src/egl/main/egldriver.c seems both unnecessary and results in a leak.
[22:25] <RAOF> racarr: Alternatively, could you point me to code that I could test in-process-egl against?
[23:12] <RAOF> Ok. The fact that our unit-tests now terminate part-way through more often than not is getting annoying.
[23:14] <kdub> RAOF, what unit tests?
[23:14] <RAOF> The unit-tests binary.
[23:15] <kdub> sure :) i mean, which test, within the unit-tests binary is causing trouble?
[23:16] <RAOF> It's not deterministic; it often crashes between ‘[[23:16] <RAOF> I suspect this might be related to why clang-built unit-tests die immediately.
[23:17] <kdub> hmm, very strange... i haven't seen that behavior on android (yet)
[23:17] <RAOF> It's almost certainly going to be something thread related.
[23:19] <RAOF> And, obviously, gtest makes it hard to find because it's a sub-process dying
[23:22] <RAOF> After I finish addressing these merge reviews I'll see if I can hunt down why clang-built unittests die, and whether fixing that fixes this annoyance.