[15:57] <slangasek> good morning
[15:57]  * fader_ waves.
[15:57] <ttx> slangasek: o/
[15:57]  * fader_ is filling in for marjo today.
[15:59] <ogra> moop
[15:59] <pitti> \o
[16:00] <ScottK> o/
[16:00] <Riddell> hola
[16:01] <asac> o/
[16:01] <slangasek> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is slangasek.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-05
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-03-05
[16:01] <slangasek> [TOPIC] Actions from previous meetings
[16:01] <MootBot> New Topic:  Actions from previous meetings
[16:01]  * apw appears
[16:01] <slangasek>   * QA Team to retest Kubuntu desktop after ubiquity uploads
[16:01] <slangasek>   * slangasek to record server-lucid-ec2-ebsroot work items related to ISO testing integration
[16:01] <slangasek>   * seb128 to check on status of outstanding a3 wi for desktop-lucid-new-firefox-support-model
[16:02] <slangasek>   * davidbarth to check on budget status of dx-lucid-netbook-launcher-startup-speed
[16:02] <slangasek>   * ScottK, slangasek to review python sync/merge candidates ~Mar 12
[16:02] <fader_> slangasek: Ara has been performing some of the tests of the pairwise testing efforts.  You can check results at:
[16:02] <fader_> http://pairwise.qa.ubuntu.com
[16:02] <MootBot> LINK received:  http://pairwise.qa.ubuntu.com
[16:02] <fader_> As you can see, Kubuntu ubiquity crashes in both i386 & amd64, so we couldn't perform any of tests for Kubuntu fixes, but we could catch some
[16:02] <fader_> new bugs, confirmed others, and we have been communicating those to the installer team.
[16:03] <Riddell> it does?  how do i see that?
[16:03] <fader_> Riddell: The bugs column on the right has links to the relevant bugs in LP
[16:03] <slangasek> bug #532533?
[16:04] <slangasek> (targeted)
[16:04] <pitti> slangasek: outstanding firefox-support-model WI is done
[16:04] <slangasek> pitti: ta
[16:05] <slangasek> ebsroot> still outstanding on my end
[16:05] <pitti> startup speed budget> was quite okay until yesterday, but regressed a bit; was discussed this morning, they are investigating
[16:05] <slangasek> davidbarth: did you have a chance to check where netbook-launcher is on its bootspeed budget?
[16:05] <davidbarth> slangasek: hi; yes
[16:06] <pitti> http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100303-1.png was perfect :)
[16:06] <MootBot> LINK received:  http://people.canonical.com/~pitti/bootcharts/daniel-lucid-20100303-1.png was perfect :)
[16:06] <davidbarth> slangasek: unfortunately we don't pass; same as for desktop where gnome-panel and the rest of that inftrastructure slows us down
[16:06] <davidbarth> saw that with seb128 and didrocks and there's not much else we can do at this stage
[16:06] <pitti> yes, desktop is a lost cause due to compiz mainly
[16:07] <pitti> it's 16 s; we can make significant gains by switching to metacity; but it's not on the lucid plan any more
[16:08] <slangasek> yes, we're not concerned with desktop, only with netbook
[16:08] <slangasek> you'd better not be saying that netbook is a lost cause :)
[16:08] <davidbarth> slangasek: didrocks still has a few tricks up his sleeve to get 1s back
[16:08] <pitti> 1s! wow
[16:08] <slangasek> 1s?
[16:09] <pitti> I still know about the background caching in ubiquity (branch merge proposal pending)
[16:09] <apw> 10%
[16:09] <davidbarth> possibly, yes we're still loading some things multiple times and that may help
[16:09] <pitti> that should buy some .3 s
[16:09] <pitti> davidbarth: ah, nice
[16:10] <davidbarth> but to conclude on that, i think that goal should be marked deferred to L+1 due to the infratructure we're still using with that version of the netbook launcher
[16:10] <slangasek> what goal should be marked as deferred?  the bootspeed goal?
[16:11] <cjwatson> I'm going to do the background caching in ubiquity today
[16:12] <cjwatson> or merge didrocks' work anyway
[16:14] <slangasek> ok, I've had it clarified that the netbook-launcher is not being used as the reference for the 10s boot, so I don't think we need to spend more time discussing this
[16:15] <pitti> so, we optimized the startup and GNOME infrastructure, but not gnome-panel/compiz themselves
[16:15]  * slangasek nods
[16:15] <pitti> since they are going to be replaced in 10.10, and bringing them into the budget would mean to rewrite them from scratch
[16:15] <slangasek> [TOPIC] QA Team
[16:15] <MootBot> New Topic:  QA Team
[16:16] <fader_> Hardware testing:
[16:16] <fader_> http://people.canonical.com/~fader/hw-testing/current.html
[16:16] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:16] <fader_> Netbook:
[16:16] <fader_>  passed:   10 (77%)    failed: 1 (8%)   untested: 2 (15%)
[16:16] <fader_> Laptop:
[16:16] <fader_>  passed:   30 (100%)   failed: 0 (0%)   untested: 0 (0%)
[16:16] <fader_> Server:
[16:16] <fader_>  passed:   56 (95%)    failed: 0 (0%)   untested: 3 (5%)
[16:16] <fader_> Desktop:
[16:16] <fader_>  passed:   11 (92%)    failed: 0 (0%)   untested: 1 (8%)
[16:16] <fader_> We have also begun a round of manual tests on the laptops in the lab.
[16:16] <fader_> http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:16] <MootBot> LINK received:  http://people.canonical.com/~fader/milestones/lucid/alpha3.html
[16:16] <fader_> alexmoldovan has been a rockstar on this, going through and running checkbox interactively on them
[16:16] <fader_> Most of what we're seeing is the network manager applet missing (bug 520589)
[16:16] <fader_> He found some other webcam and audio issues yesterday that we'll make sure to get bugs in for today
[16:16] <fader_> Spec status:
[16:16] <fader_> http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:16] <fader_> marjo says "By default, all 10.04-beta1 work items are on-track."
[16:16] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-platform-qa-ubuntu-10.04-beta-1.html
[16:16] <fader_> cr3 has postponed several items to beta.
[16:16] <fader_> [that's it]
[16:17] <slangasek> bug #520589> er. icon *missing*?
[16:17] <fader_> Oh, I should add we're continuing the manual tests in the lab -- this report represents what has been done so far but there is more to go
[16:18] <fader_> slangasek: He's reporting that most of the systems simply don't have the network manager applet
[16:18] <fader_> Several do, but most do not
[16:18] <slangasek> pitti, davidbarth: do you know what this is about?  is this related to indicator-* support?
[16:19] <slangasek> fader_: testing is with alpha-3 media?
[16:19] <pitti> it's not indicator-ified; I had suspected the new theme, but the bug is much older
[16:19] <pitti> first time I hear about this problem (never saw this), I'll put it on my list to investigate
[16:19] <fader_> slangasek: He was testing with images from yesterday, so post alpha-3 builds by a few days
[16:19] <fader_> There were some troubleshooting steps listed in the bug that I've asked him to take a look at as well
[16:19] <slangasek> [ACTION] pitti to follow up on bug #520589
[16:19] <MootBot> ACTION received:  pitti to follow up on bug #520589
[16:20] <pitti> fader_: so you can replicate this? there's no duplicates or other affected persons
[16:20] <fader_> alexmoldovan: ^^ this was happening repeatably on multiple systems, correct?
[16:21] <pitti> let's discuss in the bug, to not hold up the meeting
[16:21]  * davidbarth reads back
[16:21]  * slangasek nods
[16:21] <fader_> pitti: Sounds good; my plan was to work with him on bugs he's found today
[16:21] <fader_> So we'll be sure to get as much info as possible for that one
[16:23] <slangasek> fader_: is there anything new to report regarding alpha3 tests?  (how are we doing on getting the reported bugs fixed, etc)
[16:23] <fader_> slangasek: Nothing yet, other than it looks like hibernate is working much better now
[16:23] <fader_> alexmoldovan has found some audio and webcam bugs yesterday that we'll file today
[16:23] <fader_> I'll make sure to get you the bug numbers
[16:24] <slangasek> fader_: sorry, I meant the report that rounds up all the ISO testing bugs
[16:24] <fader_> slangasek: Ah, sorry.  I don't have any info on that one, so I think we'll have to ask marjo when he's back
[16:24] <slangasek> as for http://people.canonical.com/~fader/milestones/lucid/alpha3.html, that lists bug #520589 for a number of units - did you say this is testing with daily images instead of the alpha-3 images?  I'm not sure that's appropriate
[16:25] <fader_> slangasek: Yes, it was with post-A3.  If you'd prefer we use A3 specifically for this I'd be happy to switch to that
[16:25] <slangasek> fader_: I don't see the point of doing extensive "alpha 3" testing with a random daily
[16:26] <slangasek> since apparently you're hitting random desktop bugs by doing this :)
[16:26] <fader_> slangasek: The goal here was to get manual testing more than a3-specific testing
[16:26] <fader_> slangasek: But you're right that it probably makes more sense to stick with one consistent image
[16:27] <fader_> We plan to do another round of manual testing during beta; for that I'll make sure we use the 'golden' beta image from the start so we aren't getting a random daily
[16:28] <slangasek> fader_: 530380 is targeted to beta-1 but has no assignee; who should take this? cr3?
[16:28] <slangasek> bug #530380
[16:28] <cr3> slangasek: it's on my radar, I'll assign it to myself
[16:28] <slangasek> thanks
[16:29] <slangasek> anything else on QA?
[16:29] <cr3> slangasek: I'm waiting for a branch to land before tackling it
[16:29] <fader_> slangasek: Nothing else from me
[16:29] <slangasek> [TOPIC] Server Team
[16:29] <MootBot> New Topic:  Server Team
[16:29] <slangasek> fader_: thanks
[16:29] <slangasek> ttx: hi
[16:29] <ttx> o/
[16:29] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:29] <ttx> Updated a couple minutes ago for freshness
[16:30] <jiboumans> o/
[16:30] <ttx> Beta1-milestoned bugs:
[16:30] <ttx> Only three left
[16:30] <ttx> bug 499389, assigned to zul
[16:30] <slangasek> (the UHT server report)
[16:30] <ttx> bug 519513, assigned to kirkland, in progress with upstream
[16:31] <ttx> and the munin MIR dependency, bug 526480
[16:31] <ttx> this one is blocked on MIR team review, assigned to asac
[16:31] <asac> i am downloading it now
[16:31] <ttx> asac: thanks !
[16:31] <asac> sorry
[16:31] <slangasek> ok, great :)
[16:31] <ttx> Beta1 specs progress :
[16:31] <ttx> High/Essential specs at < 40% completion
[16:31] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-ec2-ebsroot
[16:32] <ttx> 27% -- Good progress, test deliverables should be generated soon
[16:32] <ttx> soon as in "today".
[16:32] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-uec-testing
[16:32] <ttx> 29% -- Good progress, not impacted by Beta1Freeze or release process
[16:32] <ttx> some issues with the multi-network setup
[16:33] <ttx> in a UEC configuration that's not so easy to test at home.
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-daily-vcs
[16:33] <ttx> 31% -- Good progress, not impacted by Beta1Freeze or release process
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-papercuts
[16:33] <ttx> 33% -- On track (one WI per week). 43% of the target bugs fixed so far
[16:33] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-eucalyptus-merging-and-packaging
[16:33] <ttx> 33% -- On track (one WI per week)
[16:34] <ttx> Bugs affecting server, in other teams:
[16:34] <ttx> https://bugs.launchpad.net/bugs/506297
[16:34] <ttx> slangasek: are we still on track to fix that one ?
[16:34] <ttx> our servers look damn good though, now
[16:34] <slangasek> multi-network setup> is this going to be addressed in time?
[16:35] <slangasek> the plymouth fixes are later than expected, but that particular bug should shake out along with all the rest of the refactoring
[16:35] <ttx> slangasek: I hope so. The fallback plan is to use the local test rigs to do that testing
[16:35] <ttx> if we can't automate it
[16:35] <Keybuk> slangasek: I'm in a good progress with that one
[16:35] <slangasek> so there's no point in poking at it individually as long as Keybuk is still reworking plymouth's VT handling at large
[16:35] <Keybuk> will probably hack over the weekend on it
[16:36] <Keybuk> but it's good
[16:36] <ttx> https://bugs.launchpad.net/bugs/524439
[16:36] <slangasek> Keybuk: how soon do you think it will land?
[16:36] <ttx> I think cjwatson is on it
[16:36] <Keybuk> slangasek: by monday
[16:36] <slangasek> Keybuk: excellent
[16:36] <cjwatson> 524439> I have been doing little else for the last three days
[16:36] <Keybuk> it's obviously just slow to test
[16:37] <ttx> https://bugs.launchpad.net/bugs/527208 (kernel)
[16:37] <cjwatson> again, just slow to test
[16:37] <slangasek> Keybuk: is there a branch it's worth having me help test / look at yet?
[16:37] <ttx> jjohansen was hoping for a fix before EOW
[16:37] <ttx> jjohansen1: any updated status ?
[16:37] <Keybuk> slangasek: only in GIT, and I'd have to push that upstream - and it's not cleaned up yet
[16:38] <slangasek> ok
[16:38] <Keybuk> so I'd rather not, since fdo's git server only likes fast-forward pushes and stuff
[16:38]  * slangasek nods
[16:38] <slangasek> anything else on server?
[16:38] <jjohansen1> ttx:  sorry haven't tracked it down yet, working on it
[16:38] <ttx> jjohansen1: ok, thanks
[16:38] <ttx> slangasek: no.
[16:39] <slangasek> [TOPIC] Mobile Team
[16:39] <MootBot> New Topic:  Mobile Team
[16:39] <slangasek> ttx: thanks
[16:39] <slangasek> asac: hit me
[16:39]  * ogra looks up
[16:39] <asac> hard?
[16:39] <asac> :)
[16:39] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:39] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:39] <asac> so I came back on Thu, so i started the rebuild for thumb2 yesterday
[16:40] <asac> did that in a native ppa, but outcome was surprisngly good
[16:40] <ogra> nearly 1/§ done \o/
[16:40] <ogra> *1/3
[16:40] <asac> we have 86/323 (not 100% accurate)
[16:40] <ogra> nearly ...
[16:40] <ogra> rounded ...
[16:40] <slangasek> asac: hum, why in a PPA?
[16:40] <asac> packages now build there ... will get them pocket copy and proceed in similar chunks in the archive on weekend
[16:40] <ogra> ;)
[16:40] <asac> slangasek: because i dditn want to risk loads of packages coming back as ftbfs, keeping us out of sync etc.
[16:41] <asac> the ppa build worked well, so i will continue in archive
[16:41] <slangasek> ok; further chunks will be in the archive so we don't have the pocket copy overhead, great
[16:41] <slangasek> (human overhead)
[16:41] <asac> https://edge.launchpad.net/~asac/+archive/armel1/+packages
[16:41] <ogra> was just to minimize the risk
[16:41] <asac> slangasek: found that cdrkit and cdrdao ftbfs on all archs
[16:41] <slangasek> is 326 the total count of packages needing rebuild?
[16:41] <asac> so some  postitivefall out
[16:41] <asac> slangasek: yes, round about ... i think its 323
[16:41] <asac> but far less than i initially thought
[16:42] <asac> and 80 packages built within less a day on all archs ... so seems like we will get most done this weeken
[16:42] <asac> d
[16:42] <slangasek> excellent
[16:42] <asac> assuming builders will be idle with everyone else doing weekend ;)
[16:42] <ogra> well, plus possible ftbfs overhead
[16:42] <asac> so i will file the bugs on the few packages that failed everywhere
[16:43] <ogra> which will need manual intervention indeed
[16:43] <asac> we only have one or two armel specific failures there atm
[16:43] <slangasek> I see you're waiting on FFes; I'll make sure to look at those today
[16:43] <asac> thanks
[16:43] <asac> so the other big thing is openoffice "uno" investigation
[16:43] <asac> michael is working full time on that
[16:44] <asac> with ARM toolchain guys
[16:44] <asac> he is probably going for a as-long-as-required sprint really soon to UK to get that nailed down
[16:44] <asac> bug 417009
[16:45] <asac> the other issue we are investigating is qemu breakage
[16:45] <ogra> i suspect i found a workaround though
[16:45] <asac> it seems like IO goes bad after installing loads of packages (didnt see that with small package set before)
[16:45] <ogra> testing is still ongoing
[16:45] <asac> its bug 532733
[16:46] <asac> as ogra said, he might have found a workaround ... but we have to keep an eye on this
[16:46] <ogra> right
[16:46]  * slangasek nods
[16:46] <asac> ok Image Status:
[16:46] <asac> imx51 and dove in good shape
[16:46] <asac> thats good news at least ;)
[16:46] <slangasek> the rest of https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid looks self-explanatory to me; any trouble spots we should discuss?
[16:46] <asac> let me check
[16:47] <ogra> likewise ?
[16:47] <asac> bug 517300 might be something serbver team wants to keep on radar
[16:47] <asac> ack
[16:48] <asac> and bug 512959 scares me a bit because it shows that there are still bunch of issues potentially hidden in the toolchain - lets hope that doesnt cause issues elsewhere
[16:48] <slangasek> hmm, ttx is gone
[16:48] <asac> michael has submitted a patch afaict
[16:48] <slangasek> [ACTION] slangasek to follow up on bug #517300 with NCommander
[16:48] <MootBot> ACTION received:  slangasek to follow up on bug #517300 with NCommander
[16:49] <ogra> slangasek, err, with the server team rather ?
[16:49] <slangasek> right, a patch that he acknowledges is untested; I'll try to get him directed to our internal AD test setup
[16:49] <asac> slangasek: remember that NCommander cannot really spend much time on that because he has to do the openoffice stuff
[16:49] <slangasek> ogra: the server team doesn't have ARM hardware
[16:49] <asac> so dont confuse his priorities ;)
[16:49] <slangasek> the last comment says he would support the client side; do you want that part assigned to someone else?
[16:49] <ogra> slangasek, the mobile team will happily help them but i think it makes sense if they drive it as the package owner
[16:50] <ogra> slangasek, for submitting the patch upstream apparently things like copyright assignment are required etc ...
[16:50] <asac> slangasek: i think he says he will help to test
[16:50] <ogra> that should be rather handled by the team thats familiar with upstream
[16:50] <slangasek> ogra: impractical unless you're giving them root access on ARM hardware somewhere for this
[16:50] <asac> after they integrate the patch he submitted
[16:50] <asac> slangasek: thats doable
[16:50] <asac> if they dont need control over power knobs etc.
[16:50] <ogra> sure
[16:51] <slangasek> asac: also, should this really be a priority given that likewise-open is supported as a server component?  Are you expecting ARM server deployments in lucid?
[16:51] <slangasek> [ACTION] slangasek to follow up on bug #517300 with asac/ogra
[16:51] <MootBot> ACTION received:  slangasek to follow up on bug #517300 with asac/ogra
[16:51] <slangasek> there, action amended :)
[16:51] <asac> slangasek: server is an interesting market
[16:51] <ogra> we build server alternate
[16:51] <asac> slangasek: we see multi core arm things with really low power
[16:51] <ogra> we dont fully support them (yet)
[16:51] <slangasek> anything else on mobile?
[16:51] <asac> not fully supported, but we run the server image
[16:52] <asac> and having that is good.
[16:52] <asac> nope
[16:52] <asac> thanks!
[16:52] <slangasek> [TOPIC] Kernel Team
[16:52] <MootBot> New Topic:  Kernel Team
[16:52] <slangasek> asac, ogra: thanks
[16:52] <ogra> in any case we have a commitment to fix as much of main FTBFS as possible
[16:52] <ogra> thanks
[16:52] <slangasek> apw, ogasawara: hi
[16:52] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Beta-1 activity is summarised at the second URL below, with those item pushed out shown as At Risk.  Our burndown chart is at the third URL:
[16:52] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:52] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:52] <apw> [LINK] http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[16:52] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20ubuntu-10.04-beta-1
[16:52] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/canonical-kernel-team.svg
[16:52] <apw> Of the pushed out items one has now closed.  We have dropped the lenovo-sl-laptop driver as it is confirmed as not required, this closed kernel-lucid-review-of-ubuntu-delta.  The AppArmor pam update is progressing but slowly.
[16:52] <apw>
[16:52] <apw> For KMS are about ready to upload the drm 2.6.33 backport, testing is ongoing on the packaging for the transition.  Boot performance is progressing slowly, but out boot component remains on track.  The AppArmour upstreaming progresses, feeding updates into Lucid.  For suspend/resume we hav some new timeing patches applied.  Of the bugs on the list two are pending testing by users, and two remain under investigation.

[16:53] <slangasek> drm 2.6.33 backport - is that being pulled in to the main kernel package?
[16:53] <apw> yes, directly into the kerenl
[16:53] <slangasek> ok
[16:54] <apw> not a backport in the sence of lbm
[16:55] <pitti> apw: I saw the bug today, and it sounded like it'd need another patch from trunk?
[16:55] <pitti> apw: but otherwise, thanks so much for getting it so far!
[16:55] <apw> yeah i need to change that one up and find out what happened with that patch
[16:56] <slangasek> apw: "AppArmor pam update" - namespace collision?
[16:57] <apw> there is an update to pam for apparmor in testing as i understand things
[16:57] <slangasek> why does pam need an update?
[16:57] <apw> jjohansen1, ^^
[16:57] <slangasek> jjohansen1: we can take that offline
[16:57] <apw> i'd have to defer to john on that one
[16:57] <slangasek> we don't need to block the whole release meeting with my attachment to the pam package :)
[16:58] <apw> hehe :)  ok
[16:58] <cjwatson> are you guys tracking foundations-lucid-laptop-mode-tools-integration?
[16:58] <apw> i have it on my chart yes
[16:58] <jdstrand> I don't have all the details, but that should be the pam_apparmor module-- not all of pam
[16:58] <jdstrand> beyond that, I can't speak to it
[16:59] <cjwatson> apw: do you know if the remaining two WIs are likely to get done for beta-1?
[16:59] <slangasek> jdstrand: hum, haven't heard of / seen this module before?
[16:59] <apw> cjwatson, thouse two have been slipping, amit has been otherwise engaged this week
[16:59] <jdstrand> slangasek: it's new
[16:59] <slangasek> ok
[16:59] <apw> i have not heard they won't make beta-1 but i will poke the nest and make sure
[16:59] <jdstrand> well, old, but new to Ubuntu
[16:59] <cjwatson> is it safe to slip them to beta-2, or would it be safer to defer them?
[16:59] <slangasek> apw: thanks (that was going to be my next question)
[16:59] <cjwatson> (I don't really know the details)
[16:59] <apw> they look to be the only ones he has which are beta-1 metarial
[17:00] <slangasek> the WIs are weak-FF material
[17:00] <slangasek> implementing power management stuff we aren't currently doing by default
[17:00] <slangasek> so I don't want that slipping to beta-2
[17:00] <apw> slangasek, ack ...
[17:01] <slangasek> anything else on kernel?
[17:03] <slangasek> [TOPIC] Desktop Team
[17:03] <MootBot> New Topic:  Desktop Team
[17:03] <slangasek> apw: thanks
[17:03] <slangasek> pitti: hi
[17:03] <pitti> Full report with weekly summary, RC bug status, and spec status at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <pitti> executive summary of desktop status:
[17:03] <pitti>  - A few WIs moved from Alpha-3, but A3 was by and large a nice precision landing
[17:03] <pitti>  - Beta-1 has a lot of WIs at first sight, but much of it is DX integration, and a good chunk are targets of opportunity
[17:03] <pitti>  - Most pressing items right now:
[17:03] <pitti>    * Fix DRM for ATI/nouveau by DRM kernel backport (bug 507148)
[17:03] <pitti>    * Finish F-Spot image editing for non-imported images
[17:03] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:03] <pitti> ^ (that was just discussed sufficiently)
[17:03] <pitti> called out specs:
[17:03] <pitti>  - desktop-lucid-default-apps: Remaining important TODO is to get image editing into F-Spot without importing pictures (GIMP removal); Chris Halse Rogers is on it, making good progress. But this will land late and require a FFE.
[17:03] <pitti>  - desktop-lucid-startup-speed: from the desktop side we call this pretty much finished, as in "that's as far as we can get". Didier still has a pending ubiquity merge proposal for background caching, and OLS team needs to defer sync daemon startup
[17:04] <pitti> - desktop-lucid-new-firefox-support-model: Remaining one for Beta-1 is to identify extensions to be kept in archive; Chris Coulson has started in the team now and picking up this work
[17:04] <slangasek> pitti: f-spot> how late?
[17:04] <pitti> next week, I hope
[17:04] <pitti> beta-1, in either case
[17:04] <slangasek> ok
[17:04] <pitti> it's a relatively isolated feature, so it can be tested thoroughly
[17:05] <cjwatson> pitti: pending merge proposal> no he doesn't ... ;-)
[17:05] <pitti> cjwatson: rockin'!
[17:05] <pitti> that's what I get for preparing my notes before the meeting :-P
[17:05] <slangasek> heh
[17:05] <Riddell> Kubuntu?
[17:05] <pitti> slangasek: the fallback, if that turns out to be infeasible might be to put back gimp
[17:06] <pitti> slangasek: but I talked to RAOF yesterday (who joined the team now), and he's positive that it should be doable
[17:06] <pitti> Riddell: I'm done, please go ahead
[17:06] <Riddell> #
[17:06] <Riddell> KDE integration patches for Firefox merged in, waiting on upload and on MIR 531848
[17:06] <Riddell> # kdebindings now built on ARM (a workaround not a fix but good enough for now), with any luck we'll get images this afternoon
[17:06] <Riddell> # New logo still being worked on by Canonical Design Team, this'll break art freeze in a couple of places
[17:06] <Riddell> # Upgrade testing/fixing is the priority for next week
[17:06] <Riddell> #
[17:06] <Riddell> https://wiki.ubuntu.com/Kubuntu/Todo
[17:06] <slangasek> pitti: putting back gimp> surely we haven't left room on the desktop ISO for that...
[17:06] <Riddell> # Fixed milestoned bugs this week *  526488 plasmoids overlap on startup
[17:07] <ScottK> Bug #531697 has All Qt/KDE apps blocked on IA64.  It would be good to get someone to look at it.
[17:07] <Riddell> # 9 milestoned bugs marked as kubuntu http://tinyurl.com/yjybcx9
[17:07] <pitti> slangasek: yes, it'd be 6 MB; but I don't think we have to
[17:07] <ScottK> (sorry Riddell, thought you were done)
[17:07] <pitti> uh, you actually care about ia64?
[17:07] <Riddell> am now :)
[17:08] <cjwatson> problems in basic libraries on ports do tend to produce a hell of a lot of build failure mails, at least
[17:09] <ScottK> pitti: We've managed to build on all the ports archs for the last two releases.  It'd be a shame not to for the LTS.
[17:09] <slangasek> Riddell: have the design team given an ETA for this new logo?
[17:10] <Riddell> slangasek: hard to pin down these creative types, but they promised more on Monday
[17:10] <slangasek> hmm
[17:11] <Riddell> it's mainly an issue for the plymouth splash which needs to be implemented on the technical side too, but tseliot says it's not hard
[17:11] <slangasek> Riddell: when they do give you more, can you ask them for an ETA on when they'll be finished with it all? :)
[17:11] <cjwatson> Riddell: also gfxboot splash
[17:11] <cjwatson> I imagine
[17:11] <Riddell> cjwatson: yes, good point
[17:12] <Riddell> slangasek: I'll crack my whip at them
[17:13] <slangasek> thanks :)
[17:13] <ScottK> cjwatson: If we don't get the ICE for IA64 fixed we'll want to go back and consider qt4-x11 binaries and all the rdepends on IA64 for removal under the unbuildable binaries spec.
[17:14] <slangasek> ScottK: I didn't think we were doing per-arch removals?  That risks reintroducing bootstrapping headaches
[17:15] <ScottK> Depends on how far down you go.
[17:15] <ScottK> We'd consdered it just for Universe anyone on the theory Main would get fixed to build.
[17:15] <ScottK> anyone/anyway
[17:16] <slangasek> we can discuss that further offline if you think there's a need
[17:16] <slangasek> (I need to make some headway on unsupportable binaries this week, to start with...)
[17:16] <slangasek> anything else on desktop?
[17:17] <ScottK> OK
[17:18] <slangasek> [TOPIC] DX Team
[17:18] <MootBot> New Topic:  DX Team
[17:18] <slangasek> pitti, Riddell, ScottK: thanks
[17:18] <slangasek> davidbarth: hi
[17:18] <davidbarth> slangasek: hi
[17:18] <davidbarth> report at the usual place: https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:18] <davidbarth> summary for this week
[17:19] <davidbarth> gtk csd got deferred to L+1; judged too risky at this stage for an LTS
[17:19] <davidbarth> cody and seb128 did an awesome job of fixing tons of issues, but it's an lts, so...
[17:19] <slangasek> what's been deferred, precisely?  I thought the csd patches already landed
[17:19] <slangasek> is it being reverted?
[17:19] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:19] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[17:19] <pitti> yes, they got reverted
[17:20] <davidbarth> slangasek: it is reverted, yes
[17:20] <slangasek> ok
[17:20] <davidbarth> seb128 reverted the patch set
[17:20] <davidbarth> the new theme does not depend on them, so the impact should be nil
[17:21] <davidbarth> reporting on the blueprints targeted for the meeting:
[17:21] <pitti> well, the impact is that the reversion fixes a couple of bugs :)
[17:21] <davidbarth> dx-lucid-application-indicator
[17:21] <davidbarth> 2 app ports remaining: hplip (print jobs) and vino
[17:21] <slangasek> hplip, not cups?
[17:21] <pitti> cups itself doesn't have any GUI
[17:21] <pitti> that wuold be system-config-printer
[17:21] <slangasek> well, system-config-printer ties to cups, not to hplip :)
[17:21] <pitti> hplip has its own Qtish icon
[17:22] <slangasek> ok
[17:22] <davidbarth> slangasek: tracking the print job manager that does put an icon on the panel
[17:22] <davidbarth> pitti: right
[17:22] <slangasek> (yes, it does, but it's not installed by default and I never use it despite the HPness of my printer setup :)
[17:22] <davidbarth> nice to have, UI change is limited; target of opportunity has pitti said
[17:22] <davidbarth> the next one is more annoying:
[17:22] <davidbarth> dx-lucid-me-menu
[17:23] <davidbarth> missing dialog to set a custom status; implies 2 new strings and UI (screenshot / doc) change
[17:23] <pitti> davidbarth: TBH, I wouldn't waste time on it
[17:23] <davidbarth> missing about-me simplification; similar issues
[17:23] <davidbarth> pitti: yeah, but as it's listed, so i do report
[17:23] <pitti> davidbarth: wrt. me-menu, is it planned to not show the microblog input field if gwibber isn't running/you don't have twitter accounts defined?
[17:23] <davidbarth> these 2 are also nice to have items; the menu works without them, but be better
[17:24] <davidbarth> pitti: yes, that's a bug; ken indicated the api i could call to fix that
[17:25] <slangasek> davidbarth: actually, the way the application-indicator whiteboard is set up, those app porting items aren't picked up as work items at all; if you mean them to be, you need to not have a blank line before them
[17:25] <davidbarth> so on the me menu, i'll submit a finished patch next week for about-me and will fill the paperwork
[17:25] <davidbarth> slangasek: oh
[17:26] <davidbarth> slangasek: well, at least now most are DONE
[17:26]  * slangasek nods
[17:26] <davidbarth> the rest is for information on other BP:
[17:26] <davidbarth> dx-lucid-messaging-indicator
[17:26] <davidbarth> the beta-1 release completes the work on the new command items feature, with both static (.desktop based) and dynamic actions
[17:26] <davidbarth> all string changes landed
[17:26] <davidbarth> some minor UI tweaks required (arrow in menus to highlight currently running applications)
[17:27] <davidbarth> dx-lucid-indicator-sound
[17:27] <davidbarth> "output on mute" warning still being worked on; should be available next week
[17:27] <davidbarth> dx-lucid-session-menu
[17:27] <davidbarth> String changes landed (shut down -> power off) along with a set of patches for other modules that were using the same wording
[17:27] <davidbarth> dx-lucid-notifications
[17:27] <davidbarth> working on a patch for nm-applet to avoid spurious notifications when reconnecting (UbuntuBug:460144)
[17:27] <davidbarth> err, the formating is not great; it's mostly in the report
[17:28] <slangasek> is "power off" the new wording?
[17:28] <davidbarth> slangasek: indeed
[17:28] <slangasek> (gnome-session changelog said "switch off"; I haven't restarted my session since then, but if it was "switch off" I was going to have to file a buG :)
[17:28] <davidbarth> ted tracked down occurences of that in other packages
[17:28] <slangasek> because "switch off" is jarringly unfamiliar in en_US
[17:29] <slangasek> but "power off" is just fine, so no problem!
[17:29] <davidbarth> slangasek: hmm, i wouldn't be the best to comment on that ;)
[17:29] <slangasek> anything else on DX?
[17:29] <davidbarth> questions on the other blueprints?
[17:29] <slangasek> none from me
[17:29] <slangasek> [TOPIC] Foundations Team
[17:30] <MootBot> New Topic:  Foundations Team
[17:30] <slangasek> davidbarth: thanks
[17:30] <slangasek> cjwatson: 30 seconds ;)
[17:30] <cjwatson> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:30] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:30] <cjwatson> as the server team would put it, "updated a couple minutes ago for freshness" - i.e. written in a rush during the meeting
[17:30] <cjwatson> bug centres continue to be plymouth and ubiquity/kubuntu, both in hand but there are a fair few bugs related to each
[17:30] <cjwatson> gfxboot splash for new brand delivered by design team for Ubuntu, pending integration (but I believe documenters are aware of the UI freeze break)
[17:30] <cjwatson> remaining spec work is principally tidy-ups, aside from:
[17:30] <cjwatson>  * language pack removal in oem-config
[17:30] <cjwatson>  * hints file for support-timeframe-information
[17:30] <cjwatson>  * Java and X confirmation for release-collaboration-with-debian
[17:31] <cjwatson>  * most of supportable-binaries
[17:31] <cjwatson>  * kernel work in laptop-mode-tools-integration
[17:31] <cjwatson> the first of those is in hand, I gather the fourth is as well, the third I think is in sync even if not all the is are dotted and ts crossed, the second and fifth I'm unsure about
[17:31] <cjwatson> but the second isn't (I think) b1-critical
[17:32] <slangasek> third is in sync, but I haven't confirmed that there's a committment (even soft) to stay that way for release, which is what I want to sort before checking the box
[17:32] <cjwatson> indeed
[17:33] <slangasek> I think I'm pretty clear on the status here, otherwise; anyone else have questions?
[17:34] <slangasek> [TOPIC] Security Team
[17:34] <MootBot> New Topic:  Security Team
[17:34] <slangasek> cjwatson: thanks
[17:34] <slangasek> jdstrand: go go go!
[17:34] <jdstrand> o/
[17:34] <jdstrand> I may be able to make the 30 seconds
[17:34] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:34] <jdstrand> you can also see from http://people.canonical.com/~pitti/workitems/canonical-security.html that we are on track
[17:35] <jdstrand> we are committed to the essential items from the first link. of those, the only item that is left is security-lucid-libvirt-apparmor-devel, which is mine and doesn't require a FFe. I hope to get to that within the next week or two.
[17:35] <jdstrand> in terms of devel work, we are mostly in bug fixing mode
[17:36] <jdstrand> (that's it from me)
[17:36] <slangasek> great, thanks
[17:36] <slangasek> any questions for security?
[17:36] <slangasek> [LINK] MOTU
[17:36] <MootBot> LINK received:  MOTU
[17:36] <slangasek> jdstrand: thanks
[17:37] <jdstrand> sure! :)
[17:37] <slangasek> ScottK: hi, anything to say here?
[17:37] <ScottK> Looks like that's just me today
[17:37] <ScottK> ocaml transition in ongoing (waiting on the next round of syncs)
[17:37] <ScottK> Python still has me nervous.
[17:37] <ScottK> Nothing else.
[17:37] <ScottK> Any questions?
[17:38] <slangasek> don't think so
[17:38] <slangasek> python nervousness>  we still have an action to review that status next week, so
[17:39] <pitti> ScottK: I saw a ping to bug 530305 an hour ago, is there more to it?
[17:39]  * pitti will work on that now
[17:39] <ScottK> pitti: That's the current action that I know of.  Thanks.
[17:41] <slangasek> [TOPIC] AOB
[17:41] <MootBot> New Topic:  AOB
[17:41] <slangasek> anything else?
[17:41] <slangasek> #endmeeting
[17:41] <MootBot> Meeting finished at 11:41.
[17:41] <slangasek> thanks, all!
[17:41] <pitti> thanks everyone, and enjoy the weekend


[16:20] <ochosi> charlie-tca: what do you think of trying to adapt the Faenza icon-theme for natty?
[16:21] <charlie-tca> I am not familiar with it
[16:21] <ochosi> http://tiheum.deviantart.com/art/Faenza-Icons-173323228?q=boost%3Apopular+faenza&qo=2
[16:22] <ochosi> it's not yet xfce-complete, but i could do that for natty
[16:22] <ochosi> also: the folder-color would be more xubuntu-ish blue
[16:23] <charlie-tca> Are we going to keep them visible on light/dark panels?
[16:23] <ochosi> m, what exactly do you mean?
[16:24] <charlie-tca> Oh, by the way, the artwork mailing list is getting things going again.
[16:24] <ochosi> aha, didn't know there was a xubuntu-artwork mailing list
[16:24] <ochosi> if you mean: bright icons on dark panels and vice versa then yes
[16:24] <charlie-tca> Well, you know. the ones we have now kind of goes invisible on light panels now
[16:25] <ochosi> not entirely true, just select the normal elementary theme
[16:25] <charlie-tca> Those monochrome icons are really hard to see
[16:25] <charlie-tca> But, we are early enough in the cycle to look at new ones and get things worked out, right?
[16:25] <ochosi> you mean the ones in the Faenza preview?
[16:26] <ochosi> yes, that's why i'm mentioning it
[16:26] <charlie-tca> No, the elementary theme, I guess. Whatever we used in maverick
[16:26] <ochosi> a-ha. well as long as you're ok with what you see in the link i sent you...
[16:26] <ochosi> cause you can see the panel-icons in the preview as well
[16:28] <ochosi> anyway, will be afk for a while (or maybe even the rest of today) now, ping me if you decide anything in this matter
[16:29] <charlie-tca> They show up nicely there. I am hoping for something that works for accessibility in Natty. They look like they will work.
[16:29] <ochosi> well, you will get exactly what you see in this preview
[16:29] <ochosi> ;)
[16:29] <charlie-tca> I will grab them and try it, too.
[16:29] <ochosi> (i'm not going to re-invent them)
[16:29] <ochosi> sure, go ahead
[16:29] <ochosi> i think the toolbar-icons also work out pretty nicely
[16:30] <ochosi> very good contrast on bright themes
[16:30] <ochosi> (and i think we should continue with a bright theme)
[16:35] <charlie-tca> Thanks
[16:36] <charlie-tca> I would like to keep the bright theme.
[16:36] <ochosi> well, i guess i would rework it a bit for natty
[16:36] <ochosi> but we can discuss that at some point
[16:37] <ochosi> as i said, just ping me
[16:37] <charlie-tca> Okay. thanks


[00:27] <chris4585> I highly recommend lxde
[00:32] <binarymutant> which one's that?
[00:33] <binarymutant> openbox is awesome, just looked it up
[00:40] <binarymutant> tiling is better though
[00:47] <chris4585> yeah LXDE is basically openbox with pcmanfm and a panel but its setup pretty nice
[00:47] <binarymutant> I use pcmanfm too
[00:47] <binarymutant> I wish that dev would actively develop on it :/
[00:48] <chris4585> yeah, it could be better, but I just <3 nautilus
[00:48] <binarymutant> nautilus is way too big
[00:48] <binarymutant> but it does work very well
[00:49] <binarymutant> I need something like `ranger` but without the python3 dependency
[00:53] <chris4585> I like rox too
[00:53] <chris4585> its pretty lightweight
[00:53] <chris4585> but not as functional as pcmanfm
[01:03] <binarymutant> is that the one that will not no matter what just use 1 window?
[01:04] <binarymutant> or is that the one that uses libfox
[01:08] <binarymutant> rox is the one that opens multiple windows, I don't like that at all
[01:27] <kanliot> hi from johnson city
[01:28] <kanliot> and pcmanfm is releasing version 1.0 any week now
[01:28] <kanliot> it also lets you create shortcuts, which is nice
[01:45] <chris4585> uh, I'm pretty sure rox has only ever opened one window for every folder
[01:49] <chris4585> er doesn't open multiple windows
[02:08] <binarymutant> it does
[13:31] <xTEMPLARx> =]
[13:32] <xTEMPLARx> ping
[13:33] <wrst> xTEMPLARx: what up?
[13:36] <xTEMPLARx> work
[13:36] <xTEMPLARx> life
[13:36] <xTEMPLARx> all of the above?  :D
[13:42] <wrst> ha ha same here :)
[14:04] <cyberanger> similar mess here
[14:07] <wrst> cyberanger: guess i should have been bragging on the ubuntu net install in here
[14:23] <xTEMPLARx> should have?
[14:23] <xTEMPLARx> or shouldn't have?
[14:23] <xTEMPLARx> heya cyber LTNS
[14:24] <wrst> should have xTEMPLARx :)
[14:24] <xTEMPLARx> wrst:  good :D  its about time something went right for you!
[14:24] <wrst> xTEMPLARx: its actually more fun when it goes wrong!
[14:24]  * xTEMPLARx sees what you did there...
[14:25] <wrst> :)
[14:30] <xTEMPLARx> wrst:  what did you end up doing?  did you go the ubuntu server route to get a more minimal initial install?
[14:30] <xTEMPLARx> or just standard ubuntu
[14:30] <wrst> no use the net install cd, works wonders
[14:31] <xTEMPLARx> kk
[14:31] <wrst> i like installs that after the installation you get a little blinking bar asking for your username and password
[14:31] <xTEMPLARx> yup
[14:31] <xTEMPLARx> best way to keep co-workers out of your system :D
[14:32] <wrst> so this satisfies my arch itch, and also i shouldnt have a total meltdown until the scheduled six month meltdown
[14:32] <wrst> xTEMPLARx: i sadly don't get to use ubuntu at work
[14:34] <xTEMPLARx> awww :(
[14:34] <xTEMPLARx> what is it you do, again, for work?
[14:34] <wrst> supposed to be an accountant today well we shall see what the job description is :)
[14:42] <xTEMPLARx> haha
[14:42] <xTEMPLARx> welp i'm headed back home to get some rest
[15:07] <wrst> xTEMPLARx: at lunch time??
[17:20] <wrst> hello ChanServ
[17:21] <wrst> again?? really
[17:21] <wrst> hello chris4585 :)
[20:14] <wrst> cyberanger: i have determined my messing with arch has made me more capable now to mess with ubuntu :)
[21:18] <cyberanger> wrst: or at least less clueless (I dove in headfirst, the markings said 10 feet, more like 4 feet
[21:18] <pace_t_zulu> so whats the word in here
[21:18] <pace_t_zulu> we been having monthly meetings at all?
[21:20] <wrst> yep beleive it or not :)
[21:20] <wrst> cyberanger: yeah when you remove ubuntu of a lot of its fluff its nice but you still have some of the other stuff if you need to lean on it
[22:41] <cyberanger> wrst, yeah, lean distro, save the fat & grease for my five guys burger
[23:19] <wrst> yep i'm very happy so far


[00:05] <asac> fta: hmm our gnome default is broken?
[00:05] <asac> sounds like a bug
[00:06] <asac> kde doesnt have apturl in hardy - jaunty by default; in karmic they will provide it
[00:06] <aleron6> whats up guys
[00:06] <asac> for me "xdg-open apt:flashplugin-installer" works
[00:07] <asac> aleron6: no sure ;)
[00:07] <asac> not
[00:07] <fta> asac, could you please add a comment?
[00:08] <aleron6> wawt version of ubuntu you running
[00:08] <asac> fta: does that work for you too?
[00:08] <fta> yes
[00:08] <asac> k
[00:08] <asac> i can comment
[00:09] <asac> if i remember my login ;)
[00:10] <asac> fta: remind me tomorrow want to understand where the default is actually shipped
[00:11] <asac> dont see it right now
[00:11] <asac> at least not in apturl afaict
[00:15] <asac> commented ... will check hardy tomorrow
[00:15] <asac> mozclient will take a few more days i would think
[00:30] <fta> thanks
[00:31] <asac> now that i think about it, i feel like i remember someting with hardy wrt escaping of url arguments
[00:31] <asac> at least "ubuntu-bug" and apport had issues in the past
[00:31] <asac> that sound familiar
[00:53] <fta> asac, ff3.7 is red, in case you missed it
[00:53] <fta> ok, enough for today
[00:53] <fta> 'night
[00:54] <BUGabundo> night fta
[01:46] <aleron6> anybody active heah
[07:52] <eagles0513875> hey guys
[08:29] <asac> hi
[13:34] <eagles0513875> hey guys
[13:48] <eagles0513875> asac: any word on alpha 6 or is todays release of it being postponed
[14:18] <asac> eagles0513875: didnt even know that until you said
[14:18] <asac> ;)
[14:18] <asac> wouldnt be too bothered
[14:18] <asac> just normal delay because something came too late ;)
[14:18] <asac> and caused more bugs than expected
[14:18] <eagles0513875> blarg
[14:18] <eagles0513875> ahhh
[14:18] <eagles0513875> well im having problems out the rump with 5 im wondering if 6 has them fixed
[14:20] <eagles0513875> how are things looking on the extension front
[14:20] <eagles0513875> now that i finished up the wiki
[14:30] <eagles0513875> asac anything you would like me to help out with
[14:51]  * gnomefreak not really here. only here for updates and email
[14:52]  * eagles0513875 waves to gnomefreak and lets him go about his business
[14:53] <gnomefreak> eagles0513875: firegpg needs some work on rules file for clean before we can do anything. also we will not push it to Ubuntu we will push it to Debian since its not in Ubuntu. when i get back i will get with asac about it.
[14:54] <eagles0513875> if you want i can get asac to help me with it while u are gone
[14:54] <eagles0513875> *you
[15:03] <asac> eagles0513875: i will be back soon for you
[15:03] <gnomefreak> eagles0513875: he already has the diff to work on it. its not a trival fix
[15:03] <eagles0513875> ok asac
[15:03] <eagles0513875> gotcha gnomefreak
[15:03] <eagles0513875> i gotta start somewhere
[15:04] <gnomefreak> paths changed and we need to update clean in rules for them. asac can we make it a general clean instead of only looking for FireGPGCall in each path?
[15:06] <gnomefreak> it doesnt build with clean enabled :)
[15:08] <eagles0513875> O_o
[15:13] <asac> gnomefreak: we should fix upstream clean target and submit that to the author
[15:15] <gnomefreak> asac: ok sounds good but does he really care for Linux as much as windows?
[15:16] <eagles0513875> another valid question brought up by gnomefreak
[15:16] <gnomefreak> i would love a generel clean rule to find it and remove it instead of having to fix this every time he changes where FireGPGCall is moved
[15:17] <gnomefreak> we have had him fix a few things (not much) but we can email him once we figure this out <before sending this to SId>
[15:20] <gnomefreak> mostly License issue(s)
[15:46] <gnomefreak> ok first round of email done. one more round and updates
[15:46] <gnomefreak> be back
[15:50] <gnomefreak> they dropped the getmail>get all mail (or whatever it said) in tbird-3
[15:55] <gnomefreak> oh and <insert build ID into text box> doesnt work. it is not seeing the reply text box as a text box in tbird-3
[16:18] <gnomefreak> asac: do you know that n-m is showing disconnected when there is a connection? at least here it is
[16:29] <asac> gnomefreak: nm-tool output ... paste please
[16:30] <gnomefreak> ** (process:5179): WARNING **: error: could not connect to NetworkManager
[16:35] <gnomefreak> that was the only output worth showing you
[16:40] <gnomefreak> ok updated review page to list all bug numbers.
[16:46] <gnomefreak> ok im gone
[17:08] <fta2> asac, friendly reminder for the apturl bug
[17:17] <asac> i asked on -testing if someone has hardy
[17:17] <asac> or intrepid or jaunty ;)
[18:41] <fta> asac, micahg: ff3.7 still red
[18:42] <micahg> fta: I don't know how to fix this one
[18:42] <micahg> asac: I think it had to do with that patch I showed you about removing gnomevfs and gio
[21:53] <[reed]> fta: mozilla bug 512671
[22:01] <fta> [reed], i know, the idea was that i let someone else fix it ;) ok, i fixed it this time
[22:02] <[reed]> posted a patch somewhere?
[22:03] <[reed]> ah
[22:03] <[reed]> it's an ubuntu-specific thing
[22:03] <fta> [reed], is the electrolysis branch somewhat usable?
[22:04] <fta> i mean, buildable
[22:04] <[reed]> fta: I do not know.
[22:05] <fta> lol http://hg.mozilla.org/projects/electrolysis/rev/6fd4bb500d42
[22:08] <BUGabundo> asac: I sincerily hope this was just a big typo
[22:08] <BUGabundo> removing NM on updates????
[22:08] <BUGabundo> are you joking ?
[22:09] <[reed]> fta: yeah, I know we're partnering with the chromium team on the ipc stuff
[22:09] <[reed]> to develop something that we can both work
[22:09] <[reed]> s/work/use/
[22:10] <fta> makes sense, for once ;)
[22:14] <mac_v> asac: whats with NM applet failing on updates! :( is it a known issue?
[22:15] <mac_v> on recent updates , after an update... it just switches off networking
[22:50] <BUGabundo> mac_v: start NM again
[22:50] <BUGabundo> it dies on update
[22:50] <BUGabundo> very *very* bad
[22:50] <BUGabundo> even for devel cycle
[22:51] <BUGabundo> mac_v: $ sudo NetworkManager
[23:17] <asac> BUGabundo: thats fixed
[23:17] <asac> if you look in launchpad ... i didnt do the updates ;)
[23:18] <BUGabundo> so you did??
[23:18] <BUGabundo> *who
[23:18] <asac> you can see it in launchpad
[23:18]  * BUGabundo dribbles changes logs
[23:19] <asac> i didnt know that this was going to happen until it already happened ;)
[23:19] <BUGabundo>  -- Scott James Remnant<EMAIL_ADDRESS>Wed, 16 Sep 2009 20:50:31 +0100
[23:19] <BUGabundo> debian/rules: We never previously started or restarted network manager on install or upgrade, and instead flagged a reboot
[23:20] <BUGabundo> well aint that a briliant idea!
[23:20] <BUGabundo> to leave a system WITHOUT network
[23:20] <BUGabundo> DUH
[23:20] <asac> hey
[23:20] <asac> its not a big deal
[23:20] <crimsun> right, it's an alpha, we can all deal :)
[23:20] <asac> i would have preferred if he had talked to me, but if you have to touch like so many packages you cannot wait ;)
[23:21] <asac> and i understand that
[23:21] <asac> and he fixed his regressions ;) ... which is definitly good
[23:21] <BUGabundo> asac: I know how to fix it
[23:21] <BUGabundo> I wonder *how* many users got stuck
[23:22] <asac> all uploads happened in 24h or something
[23:22] <asac> so its not a big time frame ;)
[23:22] <asac> and thats how you learn how to recover from it ;)
[23:22] <asac> by stepping into these bugs
[23:22] <BUGabundo> grrr
[23:22] <fta> want a respin?
[23:22] <asac> me?
[23:23] <fta> yes
[23:23] <asac> hmm. the dailies are still in semi state. right
[23:23] <asac> why not ;)
[23:23] <asac> just network-manager package
[23:24] <asac> and jaunty is broken now ;)
[23:24] <asac> collateral damage ;)
[23:24] <fta> too late, I did the whole thing
[23:25] <asac> heh
[23:25] <asac> ok
[23:26] <asac> fta: you fixed 3.7=
[23:26] <asac> ?
[23:26] <fta> yep, broken for 2+ days
[23:26] <asac> brave
[23:27] <fta> i pasted the log 3 times, reed answered with the same bmo bug twice, so i did it
[23:28] <fta> Scott is doing nm packaging now?
[23:28] <asac> no
[23:28] <asac> he did the upstart transition uploads for everything that uses /etc/init.d
[23:29] <fta> http://paste.ubuntu.com/273140/
[23:29] <fta> lol 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6
[23:29] <fta> a snapshot with 0ubuntu6
[23:29] <asac> yes he was so kind to publish a bzr branch
[23:31] <asac> probably have to clean that up in some way
[23:32] <asac> most likely by upstreaming something sensible that auto detects whether to install upstart or old-init style things
[23:32] <asac> so it can build on jaunty again ;)
[23:32] <asac> but i am currently in the middle of pushing hard for the applet UI changes we are doing this cycle as we already are past UI freeze
[23:33] <asac> once thats out i hope i can only do bug fixing.
[23:33] <asac> and normal work ;)
[23:38] <micahg> asac: I looked at the 3.7 failure yesterday, but didn't know how to fix it
[23:39] <micahg> it turns out it was that bug I mentioned
[23:40] <fta> asac, you now have a network-manager.prerm script calling "stop network-manager || :", will that even work in jaunty?
[23:41] <fta> micahg, yep, that + a patch to rebase
[23:42] <fta> micahg, but dailies are full of surprises, you'll have your share of fixes to do ;)
[23:43] <micahg> fta: yep, I've been fixing what I can
[23:43] <fta> chromium is green, a last, too much red those past 2 weeks


[10:30] <rmg51> Morning
[11:18] <JonathanD> Morning.
[11:18] <JonathanD> no work today :D
[11:45] <waltman> no?
[11:47] <JonathanD> Nope
[11:47] <JonathanD> Home with kids.
[12:06] <waltman> ah
[13:05] <teddy-dbear> Morning peoples, dogs and turkeys
[13:13] <ChinnoDog> JonathanD: how did you get out of going to work?
[13:14] <JonathanD> I asked nicely.
[13:16] <ChinnoDog> ooh. ic.
[15:04] <waltman> I had some pre-checkup bloodletting this morning, which meant a 12 hour fast and no breakfast. So when I got into Drexel I treated myself to a bacon+egg+cheese sammich.
[15:04] <waltman> So when the meteor hits, I'll die happy. :)
[15:15] <ChinnoDog> Which meteor is hitting?
[15:15] <ChinnoDog> Oh, that one in Russia
[15:18] <waltman> The big-ass asteroid that's passing inside geosynchronous orbit.
[15:19] <ChinnoDog> ooh.  DA14
[17:16] <pleia2> there is a live video of it, but it sort of looks like watching a pong ball :)
[17:17] <ChinnoDog> I saw that video. Not very exciting.
[17:17] <pleia2> ustream.tv/nasajpl2
[17:22] <ChinnoDog> Would have been better with whooshing sounds like from star trek.
[17:25] <pleia2> except it's in space so it can't make a sound
[17:25] <waltman> shush!
[17:26] <pleia2> oh, sorry :)
[17:26] <waltman> you and your "science"
[17:26] <pleia2> let people have their suspension of disbelief
[20:30] <MutantTurkey> the paper I worked on is getting accepted to a Journal!
[20:32] <waltman> yay!
[20:33] <waltman> Are you one of the authors?
[20:40] <MutantTurkey> co-author
[20:40] <MutantTurkey> and there is definitely lots of room for more work on the project
[20:40] <waltman> nice!
[20:42] <MutantTurkey> yep!


[11:38] <bogdanteleaga> hello everybody
[11:38] <bogdanteleaga> can somebody help me with adding win2012r2 to this dropbox menu and making it work? http://postimg.org/image/to2m0mtpn/
[11:38] <bogdanteleaga> I've tried downloading the charm-zip, untarring the archive in releases/ and modifying https://github.com/juju/juju-gui/blob/develop/app/store/env/go.js#L158
[11:40] <bogdanteleaga> however I'm not sure whether: a) that's the correct place to update, b) that archiving it back and deploying it would actually create that change without going through some make steps
[12:26] <frankban> hi bogdanteleaga
[12:26] <frankban> looking
[12:33] <frankban> bogdanteleaga: I confirm that's the place to be updated to add more choices to the series drop down when uploading a local charm archive
[12:34] <bogdanteleaga> frankban: so what other steps should I do to get it up?
[12:34] <bogdanteleaga> frankban: as I said, I tried modifying that repackaging the archive and deploying the local charm
[12:35] <frankban> bogdanteleaga: do you need that now or can you wait a couple of days for a new gui release (including the charm)?
[12:35] <frankban> bogdanteleaga: or do you just need a temporary hack to get those choices in your environment?
[12:36] <bogdanteleaga> frankban: we've got a demo at the end of the week, I'd like to at least try it out if it's not that complicated
[12:36] <frankban> bogdanteleaga: in this demo, do you demonstrate the GUI deployment or do you just need an initial environment with the GUI already there and the choices for new series?
[12:38] <bogdanteleaga> frankban: we'd like to demonstrate the steps for the gui deployment, it is windows after all :P
[12:38] <bogdanteleaga> frankban: I could just deploy from the CLI and show the gui result
[12:38] <bogdanteleaga> frankban: oh, I misunderstood, sorry
[12:38] <bogdanteleaga> frankban: the second one
[12:39] <frankban> bogdanteleaga: so you can hack in the GUI unit before starting the demo, correct?
[12:39] <bogdanteleaga> frankban: yup
[12:40] <frankban> cool, so I have an idea bogdanteleaga, I am setting up a local env with quickstart right now, so that I can try while I expose it to you
[12:41] <bogdanteleaga> frankban: cool, thanks
[12:41] <frankban> bogdanteleaga: before we start, I'll try to get someone to update that list and I hope to be able to do a GUI release this week, so it's possible that at the end of the week you'll have a GUI with the new series out of the box
[12:42] <bogdanteleaga> frankban: that'd be awesome as well
[12:42] <frankban> bogdanteleaga: but if this does not happen, let's try to hack the new series in
[12:42] <bogdanteleaga> frankban: https://github.com/juju/juju/blob/master/version/supportedseries.go#L77
[12:42] <frankban> bogdanteleaga: cool thanks
[12:42] <bogdanteleaga> frankban: you should toss centos7 in there :)
[12:43] <bogdanteleaga> frankban: arch is CLI only at this point
[12:44] <frankban> bogdanteleaga: so, assuming you have an environment with the juju-gui in it
[12:44] <bogdanteleaga> we might need only win2012r2 and win2012hvr2 I'll get back to you with that one
[12:44] <bogdanteleaga> yes
[12:44] <frankban> bogdanteleaga: fir step is to "juju set juju-gui juju-gui-debug=true" so that the GUI is served via its non-minified version
[12:48] <frankban> bogdanteleaga: then we can proceed and change the file you already found in the GUI unit: "juju ssh juju-gui/0 sudo nano /var/lib/juju-gui/juju-gui/build-debug/juju-ui/store/env/go.js"
[12:49] <frankban> (replace nano with a textual editor of your choice)
[12:49] <frankban> bogdanteleaga: then refresh the GUI page very well in your browser (shift+ctrl+r usually works) and the new series should be available when dragging and dropping a zip archive
[12:53] <frankban> bogdanteleaga: I'll ping you when we have a new GUI release including this fix
[12:54] <bogdanteleaga> hmm
[12:54] <bogdanteleaga> frankban: it seems it was already there when I tried editing the file
[12:54] <bogdanteleaga> frankban: and now it's in the browser as well
[12:55] <bogdanteleaga> frankban: I could swear it wasn't there after I deployed it
[12:55] <frankban> bogdanteleaga: is this your customized local charm?
[12:55] <bogdanteleaga> frankban: yeah the one where I unpacked, modified and repacked
[12:55] <bogdanteleaga> frankban: could it be the debug flag that did it or am I just tired? :)
[12:56] <frankban> bogdanteleaga: it can be, anyway, my instructions work from scratch, without the need to deploy a local charm
[12:56] <bogdanteleaga> frankban: yup, that's true
[12:56] <frankban> bogdanteleaga: you are basically editing the files served by the GUI server running in the unit
[12:57] <bogdanteleaga> frankban: thanks a lot :)
[12:57] <bogdanteleaga> frankban: I'll get back to you later with the series that should get in
[12:57] <frankban> bogdanteleaga: that's ugly but hopefully you won;t need it by the eow
[12:57] <bogdanteleaga> frankban: I have a feeling we only want the CLI on win8, 8.1 and 7
[12:57] <frankban> bogdanteleaga: I am planning about adding all the series listed in juju-core, except for centos and arch, is that ok?
[12:58] <frankban> bogdanteleaga: so basically series: [
[12:58] <frankban>       'precise', 'quantal', 'raring', 'saucy', 'trusty', 'utopic', 'vivid',
[12:58] <frankban>       'win2012hvr2', 'win2012hv', 'win2012r2', 'win2012', 'win7', 'win8',
[12:58] <frankban>       'win81'],
[12:59] <alexpilotti> bogdanteleaga: dont forget Win10
[12:59] <alexpilotti> and win2016
[12:59] <bogdanteleaga> alexpilotti, frankban: yes, we should get those in core soon
[12:59] <alexpilotti> win10 now, as it’s publicly awailable
[12:59] <bogdanteleaga> alexpilotti: but only the server versions are for charms right?
[13:00] <alexpilotti> not really, VDI woks on client too
[13:00] <alexpilotti> AD, SQL Server, SP, etc only server of course
[13:00] <frankban> bogdanteleaga: for now, I'd keep wily and win10 out of the GUI if they are not in core yet
[13:00] <bogdanteleaga> alexpilotti: hmm, we should have some guards then somewhere to prevent faulty deployment
[13:00] <frankban> bogdanteleaga: is your demo ok with the list above?
[13:00] <bogdanteleaga> frankban: yes
[13:00] <alexpilotti> but win2016 and win2016hv are out now in TP2
[13:00] <frankban> cool
[13:01] <alexpilotti> so we should get them in now already IMO
[13:01] <urulama> alexpilotti: you guys have charms for win2016* already? we can include those series in new charmstore release this week if needed
[13:01] <bogdanteleaga> alexpilotti: we need to get them in core before gui I think
[13:02] <bogdanteleaga> urulama: there shouldn't be anything preventing the current ones from working
[13:02] <alexpilotti> urulama: yep, we run tests on them, especially hyper-v
[13:02] <urulama> bogdanteleaga: just asking if we need to add the win2016* and win10 to "unblock" you
[13:03] <urulama> alexpilotti, bogdanteleaga: so, just to verify: new series are win10, win2016 and win2016hv?
[13:04] <alexpilotti> there’s also: win2016nano
[13:04] <urulama> alexpilotti: what's that? :) the IoT thingy?
[13:04] <alexpilotti> that’s the NanoServer, Windows Server on a 300-400MB image
[13:04] <urulama> hah, ok
[13:04] <alexpilotti> we tested the Juju agent quite some time ago, but we need to run more tests
[13:05] <alexpilotti> consider that this stuff is getting rolled out publicly via technical previews (we have TP2 in April)
[13:05] <alexpilotti> and will get a final release next year
[15:09] <lazyPower> frankban: rick_h_: That JujuGui stacktrace is back again about websocket closed - http://paste.ubuntu.com/12048618/
[15:09] <lazyPower> i'm getting this consistently in CI across 2 substrates, GCE and AWS
[15:11] <frankban> lazyPower: on call, I'll look, at first sight this is something I cannot dupe on ec2. juju quickstart and juju versions?
[15:12] <lazyPower> frankban: pulling more details now, 1 sec
[15:17] <lazyPower> frankban: juju-1.24.3, juju-quickstart 2.2.0
[15:21] <frankban> lazyPower: is the error intermittent?
[15:21] <lazyPower> i've triggered it twice, running a third time to capture the output
[15:22] <frankban> lazyPower: dpkg -l python-websocket ?
[15:22] <lazyPower> ii  python-websocket     0.18.0-0ubuntu0 all             WebSocket client library for python
[15:23] <frankban> lazyPower: I have 0.18.0-2 which should be basically the same
[15:24] <frankban> so for some reason juju-core closes the ws connection
[15:24] <frankban> lazyPower: what's the output if you pass --debug to quickstart?
[15:25] <lazyPower> http://drone.dasroot.net/github.com/chuckbutler/kubernetes-juju-builder/master/c6b3dbd3e0a8f2e792bbd926eb4d4fb981398b94
[15:25] <lazyPower> not sure, but if you want to follow along at home - threaten it with developer debugging goggles, maybe it'll behave and stop stacktracing at me
[15:27] <lazyPower> its going to hand off to quickstart momentarily
[15:30] <lazyPower> if you opened your browser, it appears to have been the magic sauce to get it to behave
[15:30] <lazyPower> it just bootstrapped and completed without stacktracing me :-|
[15:30] <lazyPower> silly intermittant issues
[15:32] <frankban> lazyPower: yeah, no errors now
[15:33] <lazyPower> i'm calling schenanigans on juju
[15:34] <frankban> lazyPower: if you can add --debug to your script then maybe the next time we have more info. looking at that tracebakc, it could be anything from juju-core oddities to python-websocket issues to network disconnections
[15:34] <lazyPower> i think 1.24 had this issue in an earlier revision
[15:34] <lazyPower> it might have been a cached image problem running an older juju
[15:34] <frankban> lazyPower: that sounds like a great explanation ;-)
[15:35] <lazyPower> weird that i pulled the updated image and it still tanked, but again, its probably a caching problem
[15:35] <lazyPower> 90% of my issues are due to something being old hanging around w/ my aggressive caching strategy


[03:47] <greeter> upgraded to the latest lubuntu and it actually fixed video problems i was having :-D sweet
[03:59] <ianorlin> !yay
[04:00] <greeter> it's very nice
[04:00] <greeter> i get some weird error upon booting up, but it doesn't seem to impact system performance :-)
[10:19] <ichat> anyone here who can help me with a sound issue on my newly installed  14.04  my logitec ls150 (usb speakers) worked fine on   10.10 ... but after i finally installed a fresh 14.04  the usb speakers dont work, i dont get a volume mixer  in the menu nor in hte aplet bar...
[10:20] <ichat> the one thing on lsusb could be Bus 002 Device 004: ID 1130:1620 Tenx Technology, Inc.  ...
[10:33] <ichat> anyone able to help me find out what could be wrong with alsa or whatever is supposed to handle sound here
[10:46] <Techman> Why is pulseaudio not bundled in with lubuntu
[10:46] <Techman> pulseaudio and pulseaudio volume control is a million times better then what is shipped by default
[10:46] <raalex> yes
[10:46] <raalex> and it actually works
[10:47] <Techman> pulseaudio solves a zillion audio issues filed with lubuntu
[10:47] <raalex> everything seems to be plug and play with pulse audio
[10:47] <Techman> Exactly
[10:47] <raalex> and without it, not so much
[10:47] <Techman> and if it doesn't, just change the audio stream
[10:47] <Techman> and boom it works
[10:48] <raalex> even my extremely esoteric external usb sound card
[10:48] <Techman> I have some USB sound accessories
[10:48] <Techman> I set up pulseaudio t o automatically switch to my headphones when I plug them in
[10:49] <Techman> and switch back to PC audio when I unplug them
[13:52] <raalex> hmm, in recently installed google chrome
[13:52] <raalex> and it seems like it has set itself as default browser with no way to change it; every link outside of firefox opens in google chrome
[13:52] <raalex> even through firefox is set as the default browser
[13:53] <raalex> lubuntu 14.04, I changed firefox to the default in the "default applications of lxsession" pane
[13:54] <raalex> firefox says it's the default, and chrome says that it has no way to determine nor set the default browser
[14:18] <wxl> raalex: try using update-alternatives
[14:19] <wxl> raalex: set x-www-browser to firefox and NOTHING will complain
[14:47] <raalex> uhh
[14:47] <raalex> sweet, thanks a lot
[15:31] <wxl> raalex: np
[16:48] <chulis> wich verson of torrent comes with lubuntu?
[16:48] <wxl> chulis: depends on which version of lubuntu
[16:49] <wxl> assuming you mean latest:
[16:49] <wxl> !info transmission | chulis
[16:50] <chulis> i dont remember maybe 13
[16:51] <wxl> chulis: 13 what? lsb_release will get you the answer
[16:51] <chulis> latest 13
[16:52] <wxl> that's 13.10, or saucy
[16:52] <chulis> ok transmission
[16:52] <chulis> thanks
[16:52] <wxl> but it should be a different version in saucy
[16:52] <wxl> !info transmission saucy | chulis
[16:52] <wxl> slightly different :/
[16:55] <vjacob> HIYA
[16:56] <vjacob> sorry. lower caps now. how do I dist-upgrade from Ubuntu 12.04 LTS to Lubuntu 14.04 (LTS)?
[16:56] <wxl> vjacob: you don't. dist-upgrade is a different take on upgrade. you *CAN* sudo do-release-upgrade
[16:56] <vjacob> aah
[16:56] <wxl> vjacob: although i'm not sure if it will work between ubuntu and lubuntu
[16:56] <vjacob> anything to keep in mind before trying that out?
[16:56] <vjacob> ah
[16:57] <wxl> vjacob: you'll probably end up with lubuntu on top of ubuntu which is confusing to say the least
[16:57] <vjacob> easy enough, get the reply "No new release found"
[16:57] <genii> vjacob: If it says something like "command not found" you may need to install ubuntu-release-upgrader-core first
[16:57] <wxl> vjacob: if i were you, i'd copy your home folder somewhere else, wipe and install lubuntu, and return your home folder
[16:57] <wxl> !info ubuntu-release-upgrader-core
[16:58] <vjacob> slash etc slash lsb-release says "12.04 precise Ubuntu" though
[16:58] <vjacob> wxl, that might be an interesting idea :)
[16:58] <vjacob> not sure how practical it would be though at this point in time :)
[16:58] <wxl> you can put a space in front of that initial / and it won't be interpreted as an irc command vjacob
[16:58] <wxl> vjacob: well you don't want ubuntu, right?
[16:58] <vjacob> i'm already running lxde on the system
[16:59] <wxl> vjacob: any way you cut it, upgrading to lubuntu is going to leave you with all the ubuntu stuff
[16:59] <vjacob> so it's not a biggie, would be cleaner to go all out lubuntu yes
[16:59] <vjacob> aye
[16:59] <wxl> vjacob: yes but do you also have, say, pulseaudio?
[16:59] <wxl> vjacob: not to mention a butt load of gnome libs, unity crap, and probably *shudder* mono
[17:00] <vjacob> :) Thank you. a bunch wxl - genii
[17:00] <vjacob> + not - :)
[17:01] <vjacob> probably will switch over at some point soon
[17:02] <wxl> vjacob: the other thing you can do if you can get lubuntu installed by using ubuntu-release-upgrader-core is to wipe out all the ubuntu stuff
[17:02] <wxl> !purelxde | vjacob
[17:02] <vjacob> just for the record, I
[17:02] <vjacob> I am not seeing an ubuntu-release-upgrader-core package here
[17:03] <wxl> it's there for sure (see above)
[17:03] <wxl> although wait a minute
[17:03] <KyouReeUs4nfo> I am currently using qasmixer for volume control, are there any other LXDE alternatives for volume control from systray? volume control wasn't there for some reason and I couldn't add it from lxpanel either for some reason. It's a fresh install of 14.04 btw.
[17:03] <wxl> !info ubuntu-release-upgrader-core precise
[17:03] <wxl> ah ha
[17:03] <wxl> any other ideas on that one, genii ↑
[17:04] <vjacob> :)
[17:04] <vjacob> no bother
[17:04] <vjacob> will probably do a clean slate soon enough
[17:04] <vjacob> cheers
[17:05] <wxl> :)
[17:06] <genii> wxl: Try installing update-manager-core instead of ubuntu-release-upgrader-core  then... I think the package name changed somewhat from 12.04 through 13.10 somewhere
[17:07] <wxl> !info ubdate-manager-core precise
[17:07] <wxl> genii: nope :)
[17:07] <genii> !info update-manager-core precise
[17:08] <genii> wxl: You had a typo :)
[17:09] <KyouReeUs4nfo> nm-applet should autostart by default imo. I had to add /usr/bin/nm-applet to lx-session Autostart configuration (preferences--> default applications for lxsession --> Autostart ---> Type /usr/bin/nm-applet --> click Add).  Note that I didn't have edit or move any .desktop files to some .config dir.
[17:10] <ianorlin> known bug
[17:11] <wxl> genii: hahahaha
[17:11] <wxl> KyouReeUs4nfo: not only is it a known bug it's in the release notes
[17:16] <KyouReeUs4nfo> wxl: It would be great if one could execute a bash script with nm-applet. For instance, when connection goes down, it will be detected by this script for a change in mac address or something of that sort before it is automatically brought back up. using cron for such scripts is pain because it doesn't work well with commands that require sudo in front of it. js.
[17:17] <wxl> KyouReeUs4nfo: not an issue if you use the main crontab. do sudo crontab -e
[17:17] <wxl> KyouReeUs4nfo: however upstart will more easily handle what you're talking about
[17:18] <wxl> !upstart | KyouReeUs4nfo
[17:20] <KyouReeUs4nfo> wxl: I will try sudo crontab -e, thanks.
[17:28] <KyouReeUs4nfo> Another thing I observed in 14.04 is locking "issue". In that, I couldn't lock my screen before being away, unless I "tweaked" light-locker. I had to enable light-locker on to be able to lock my screen. I think it should also be on by default. In order to do it, I clicked  preferences --> light-locker settings --> enable lightlocker on and automically lock the screen when screensaver is activated.
[17:36] <KyouReeUs4nfo> nice way to get to root prompt without using sudo by using /usr/share/applications/Root*Terminal.desktop (I don't use it that often)
[17:45] <KyouReeUs4nfo> while I was trying to find a way to use nm-applet without using terminal, I accidentally locked my self out and went into a login loop. I don't know if one can reproduce this, (preferences--> default applications for lxsession --> type nm-applet in Widget1 text box and click Reload)..it most likely caused .Xauthority issue imo. This happened to me after an upgrade to 14.04 from saucy.  After that I wasn't able to log back into Lu
[17:45] <KyouReeUs4nfo> buntu profile.
[17:51] <KyouReeUs4nfo> Do I need pavucontrol and pulseaudio in LXDE for sound?
[17:53] <ianorlin> not usaually although sometimes if sound is so faint you can't hear it helps
[18:02] <KyouReeUs4nfo> how do I get out of tty3 if I press ctrl+alt+f3 ? shortcut?
[18:05] <wxl> KyouReeUs4nfo: ctrl-alt-f7
[18:05] <wxl> KyouReeUs4nfo: you have 6 ttys and then you go to x
[18:06] <KyouReeUs4nfo> wxl: tht makes sense, we login to 7 by default right?
[18:06] <wxl> KyouReeUs4nfo: yep
[18:06] <KyouReeUs4nfo> wxl: kewl
[19:01] <Unit193> wxl: What's your /etc/host.conf look like?  Or did you fix it already?
[19:01] <wxl> Unit193: you responding the the mailing list message?
[19:03] <Unit193> To your Avahi question.
[19:04] <wxl> Unit193: yeah that one. i haven't checked /etc/host.conf but will.
[19:04] <wxl> Unit193: it's odd i've never had to do this with avahi before.
[19:04] <Unit193> wxl: Right, indeed.  Only thing I'd think could be different is installed programs or startup.
[19:07] <wxl> Unit193: yeah i don't know. odd for sure.
[19:10] <Unit193> So, make sure your ps aux | grep avahi  and dpkg -l | grep avahi  don't lack anything too, in addition to that file.
[19:13] <wxl> hm that's an interesting thought!
[20:36] <zombiehoffa> is the new vlc crashing randomly for everyone or just me?
[23:23] <raalex> depends on what you mean by randomly
[23:23] <raalex> I watched a movie today and everything was fine


[01:42] <guiverc> Has anyone been able to run 'live' daily tests on hardware over the last few days?   I've had issues with ISOs wanting acting like netboot loaders, wanting to download... ubuntu-studio, kubuntu, xubuntu written to multiple (4) thumb-drives and from 2 boxes  (had no issues with lubuntu on past weekend though)
[02:07] <guiverc> lubuntu too; "unable to find medium container a live file system \n Attempt interactive netboot from a URL?"   (I can't rule out bad thumb-drives.. but only had this issue since sunday)
[03:08] <guiverc> ditto ubuntu (destkop) too :(
[03:11] <Bashing-om> guiverc: What is it that you need ? I can boot an old xubuntu 20.04 .iso and see what the haps be there.
[03:11] <guiverc> nah, it's groovy issues since sunday (my local time) I've had issues with; booting to netboot (download; focal didn't do that)
[03:11] <guiverc> but hanks Bashing-om
[03:11] <guiverc> s/hanks/thanks
[03:12] <Bashing-om> guiverc: :D
[03:48] <guiverc> issue only occurs on older BIOS boxes... media will boot on UEFI; bug raised
[04:02] <Bashing-om> guiverc: Good man that you are :P
[04:03] <guiverc> yeah... just had it boot on one box, my UEFI good, BIOS bad oversimplied, newer BIOS still boot maybe...  (my older BIOS wording does sort of fit; but I was thinking all BIOS)
[04:05] <guiverc> one dell d755 fails, another d755 boots... i've got lots of bios boxes anyway for a minimal survey I can add to report..


 PISSED
[01:47] <aedend> I need to apologize. I shouldn't have vented in the channel like that, Sorry folks.
[12:37] <aedend> To limit who can view my wordpress site, what is more secure - creating iptable rules or configuring mod_authz_host in Apache?
[12:39] <aedend> I've got .htaccess setup for admin login etc. But I'm trying to setup so only family can view the actual blog
[16:30] <cyberanger> aedend: considering the goal, iptables won't work
[16:30] <cyberanger> how are you going to keep it just family that way, betting you've all got dynamic ip's
[16:35] <cyberanger> Setup HTTPS, set wordpress on a subdirectory, and either .htaccess on that subdirectory or take a look at https://wordpress.org/support/topic/plugin-password-protect-wordpress-multiple-passwords-what-do-they-do
[22:17] <aedend> cyberanger,
[22:23] <aedend> For anyone that is interested, I've got something pretty interesting that's happened to one of my text files
[22:24] <aedend> After using unison to sync my files with my DO droplet, all files synced but one.
[22:26] <aedend> Both copies of this file have been erased and populated with a http error message from digital ocean
[22:26] <aedend> which is weird because I used ssh to sync the files.
[22:29] <aedend> If I try to open the file with vim, nano or gedit I get this (on both the server and locally) https://paste.debian.net/315209/


[18:17] <joeri> Hi guys, love the OS! Just wondering if there are any precautions I should take before installing the new Ubuntu Studio package on my Ubuntu 19.04 laptop


[00:46] <netritious> cyberanger: I read a little bit about tinc last year when I updated a friends router with shibby AIO and say it there along with openvpn.
[00:46] <netritious> *and saw it there
[00:47] <netritious> until then had never heard of it. are you using wireless routers to provide tinc services?
[02:28]  * [Ubik] makes note that cyberanger missed the ACS meeting
[02:33]  * cyberanger makes note that [Ubik] missed the church meeting that overlapped.
[02:42] <[Ubik]> church meeting?
[02:47] <cyberanger> Salvation Army used to always have the youth service on Thursdays, We just moved it to Mondays a week or two ago.
[02:47] <cyberanger> But in it's place are still youth activities, so I had to chaperone.
[02:47] <cyberanger> What did I miss at ACS?
[17:59] <netritious> howdy wrst
[18:00] <wrst> hey netritious!
[18:00] <wrst> how are you doing?
[18:00] <netritious> pretty good, you?
[18:02] <wrst> doing well, have been getting accustomed to new corporate overlords... how are things out west?
[18:11] <netritious> not to shabby wrst, mentoring a young man on ubuntu and LAMP...wants to learn web dev and eventually game dev
[18:11] <wrst> great, how is that going?
[18:17] <netritious> he fell asleep at the keyboard last night lol
[18:17] <netritious> he apologized via text. I said "well, it was pretty boring talk about static IPs, so I understand"
[18:19] <netritious> it went something kind of like...
[18:19] <netritious> Me: "so now we are going to edit the configuration file to assign a static IP to the network interface."
[18:20] <netritious> Him: "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
[21:28] <netritious> anyway, it was unny wrst
[21:40] <cyberanger> netritious: covered IPv6 yet?
[22:17] <wrst> netritious:  :)
[22:17] <wrst> at least you are keepign it interesting ;)