[10:03] <koba> hi, could you please check if thermald is ready to release? thanks
[10:03] <koba> https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2028217
[10:03] -ubottu:#ubuntu-devel- Launchpad bug 2028217 in thermald (Ubuntu Jammy) "MTL: Add support for Meteor Lake" [Undecided, Fix Committed]
[12:16] <schopin> @pilot in
[15:00] <jbicha> @pilot in
[15:07] <zhsj> jbicha, schopin: not sure what did i miss, https://code.launchpad.net/~zhsj/ubuntu/+source/libevent/+git/libevent/+merge/451102 doesn't appear on https://reports.qa.ubuntu.com/reports/sponsoring/. so i just ping the pilots here.
[15:08] <schopin> jbicha: can I let you take it? I'm nearing the end of my day :)
[15:08] <jbicha> schopin: yes
[15:08] <schopin> thanks!
[15:10] <zhsj> actually it's glibc related, so schopin's problem :P
[15:10] <schopin> zhsj: I'm hating you a little bit right now ;)
[15:10] <zhsj> haha
[15:10] <schopin> oh that's a strlcat thing?
[15:10] <jbicha> zhsj: please check with Steve whether the Ubuntu diff can be dropped since we are in mantic now
[15:11] <jbicha> it looks like the Ubuntu diff was needed for upgrades from kinetic; hopefully kinetic machines get upgraded to lunar before lunar goes EOL
[15:12] <schopin> Is it for upgrade from kinetic, or from kinetic and below?
[15:13] <jbicha> based on the changelog, just kinetic users were affected
[15:16] <zhsj> maybe i could just tag steve on that merge proposal.
[16:27] <schopin> @pilot out
[19:01] <jbicha> @pilot out
[23:45] <Eickmeyer> enr0n: Last systemd upload in Jammy seems to be breaking USB cameras for a lot of folks. I've had 3 people already make anecdotal remarks about it. Seems it's not affecting all USB cameras, but it definitely had some sort of regression.


[02:05] <imgbot> [03:30] <imgbot> [03:30] <imgbot> [06:55]  * sil2100 needs to drive to his parents place
[06:55] <sil2100> In case trainguard things are required while I'm in mid-drive, if urgent, please poke mvo once he's around
[06:56] <sil2100> I'll be available in ~1.5h
[08:58]  * sil2100_ sighs
[09:30] <ogra_> ugh ... FF crash
[10:41] <sil2100_> dbarth-afk: hey, give us a sign once you're back :)
[11:20] <Laney> hello
[11:20] <Laney> The latest UITK introduced a component-mismatch
[11:21] <Laney> Which is making Ubuntu desktop image builds fail https://launchpadlibrarian.net/199731958/buildlog_ubuntu_vivid_i386_ubuntu_BUILDING.txt.gz
[11:22] <sil2100_> Hey! Oh my, geh
[11:22] <sil2100_> I wonder why it didn't get noticed before publication, let me see what was up
[11:24] <sil2100_> Laney: not sure who signed off the packaging changes, but the publisher was robru
[11:26] <Laney> sil2100_: Well, probably just needs an MIR filed by the lander or their delegate. :)
[11:26] <Laney> (making the assumption that this doesn't drag in loads of universe packages and isn't huge)
[11:27] <sil2100__> ...
[11:28] <sil2100__> Laney: anyway, yeah, need to poke robru which core-dev he poked when signing off the changes
[11:28] <sil2100__> bzoltan_: we need to fix UITK deps
[11:29] <sil2100__> bzoltan_: I see that qml-module-qtquick-layouts which you are now using is in main
[11:32] <Laney> Doesn't look like it has any further universe deps or build-deps - probably a reasonable candidate for MIR
[11:35] <sil2100_> My only concern is how this got into the archive
[11:37] <sil2100_> Laney: indeed, check-mir says it's clean, need to make sure about its maintainability
[11:37] <sil2100_> But it looks safe
[11:38] <sil2100_> Seems like it's from the Qt codebase
[11:38] <sil2100_> popey: \o/ on it
[12:02] <popey> sil2100_: thanks
[12:07] <bzoltan_> sil2100_: ohh... is there anything I should do?
[12:10] <sil2100_> bzoltan_: no no, I'll just make some coffee and I'll prepare some MIR formalities
[12:11] <bzoltan_> sil2100_:  thanks for the coffee, it was not really necessary ... I drink it with milk without sugar please
[12:11] <sil2100_> bzoltan_: ;D
[12:12] <bzoltan_> sil2100_:  CI service has improved big deal :) Only if we were at the same office :D
[12:12] <sil2100_> hah! I'm not CI though, so it's more like foundations service..? Doesn't sound right though ;)
[12:20] <rvr> Is the image server down?
[12:20] <rvr> 2015/03/09 12:19:44 Get https://system-image.ubuntu.com/gpg/image-master.tar.xz: EOF
[13:42] <popey> bfiller: any chance we can get that patch from renato tested more widely and landed in vivid? It fixes the crasher.
[13:43] <bfiller> popey: let me create a silo
[13:43] <popey> thanks
[13:46] <sil2100_> o/
[13:48] <bfiller> popey: building in ubuntu silo 2
[13:48] <popey> k
[13:51] <dbarth> sil2100_: i'm back and on silo-010 now
[13:52] <sil2100_> dbarth: \o/
[13:52] <sil2100_> dbarth: any ETA?
[13:53] <davmor2> sil2100: silo 003 has qa signoff now so what is the process for getting silo001 rebuilt when it lands?
[13:54] <dbarth> sil2100_: within an hour, or tomorrow morning; i'm checking a potential regression for users with many apps / accounts configured
[13:55] <jibel> dbarth, it's the last fix remaining before we can build an image for this week's promotion. Having this silo ready for testing today would be great
[13:55] <pmcgowan> popey, do we plan to release a new weather app? or have we recently?
[13:55] <pmcgowan> hoping for the fix to https://bugs.launchpad.net/ubuntu-weather-app/+bug/1404520
[13:56] <popey> pmcgowan: yes, it's on my list.
[13:57] <sil2100_> pmcgowan: right now QA has the new reminders-app on their list
[13:59] <popey> they'll have weather too in a few minutes :)
[14:02] <popey> sil2100_: you have mail :)
[14:03] <sil2100_> popey: something new? :)
[14:03] <popey> weather
[14:03]  * sil2100_ refreshes like crazy
[14:03] <sil2100_> Ah ha!
[14:04] <sil2100_> On it
[14:07] <nerochiaro> greyback: do you have any news on the autopilot issue were looking at last week
[14:08] <greyback> nerochiaro: so I reproduced it Friday, but had to nuke the device to work on something else. Today I've had the test running in a loop for over an hour. It managed to deadlock the shell, which isn't your issue though
[14:08] <greyback> nerochiaro: so no real news yet
[14:09] <nerochiaro> greyback: did you run the test using the process I sent you the other day ? (the same that CI uses)
[14:10] <greyback> nerochiaro: using the "phablet-test-run camera-app" ? If so, yes
[14:11] <nerochiaro> greyback: yes
[14:29] <sil2100_> jibel: just to make sure it's not missed: reminders and weather should now be added on the trello board
[14:30] <nerochiaro> fginther: hi, did you manage to find out about the license problem ?
[14:31] <sil2100_> jibel, davmor2: soonish it would also be nice to have silo 001 for vivid signed-off, since we just landed it for 14.09 today
[14:32] <davmor2> sil2100: did you see my question to you earlier?
[14:32] <rvr> sil2100_: I will test it, but needs to be rebuilt, isn't it?
[14:32] <rvr> (silo 1)
[14:32] <davmor2> davmor2> sil2100: silo 003 has qa signoff now so what is the process for getting silo001 rebuilt when it lands?
[14:32] <nerochiaro> fginther: we were discussing it last week
[14:32] <jibel> sil2100_, reminder and weather are both on the board
[14:33] <fginther> nerochiaro, I have a solution in place now. There was an alternate license check that works for this source (at least it did when I last tested on Friday). I just switched that a moment ago
[14:33] <sil2100_> davmor2: ah, sorry, it seems my notify's aren't working
[14:34] <sil2100_> hm, let me rebuild and ping kenvandine
[14:34] <sil2100_> kenvandine: piing
[14:34] <fginther> nerochiaro, I'll still do some follow-up, but this should work for now
[14:34] <sil2100_> rvr: silo 1 in vivid shouldn't need a rebuild
[14:34] <sil2100_> rvr: I'm talking about vivid ;) Not rtm
[14:34] <rvr> sil2100_: Ah
[14:34] <nerochiaro> fginther: if i have a merge request on which CI fails because of that, can CI be re-run on it ?
[14:34] <sil2100_> Actually, it's rebuilding already
[14:35] <nerochiaro> fginther: https://code.launchpad.net/~phablet-team/camera-app/refactor-and-fix-editor-tests/+merge/250931
[14:35] <fginther> nerochiaro, sure, one moment
[14:35] <sil2100_> kenvandine is on it it seems :)
[14:36] <fginther> nerochiaro, build in progress
[14:36] <nerochiaro> fginther: thank you
[14:37] <kenvandine> sil2100, yup... i saw it merge so kicked a rebuild
[14:52] <dbarth> sil2100: we're merging a last fix real quick in silo 010; hopefully for good this time
[14:58] <plars> popey: what ever became of calendar app? is it back now?
[14:58] <popey> plars: I'm going to resubmit once https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1423185/+merge/252184 lands
[14:58] <popey> right now QA rejected it for various reasons, all fixed execpt that
[14:58] <plars> popey: cool. No big deal from my end, just wanted to follow up in case we had missed it :)
[15:01] <popey> oh it's very much at the top of my list!
[15:02] <plars> no doubt :)
[15:23] <oSoMoN> robru, hey, can https://code.launchpad.net/~robru/webbrowser-app/no-change-rebuild/+merge/251202 be deleted?
[15:29] <Laney> sil2100: thanks for the MIR - are you chasing people to look at it?
[15:29] <Laney> They'll ask for bug subscribers. ;-)
[15:49] <mzanetti> trainguards: please reconfig silo 0. I've dropped the ui-toolkit branch that landed in trunk by now
[15:51] <sil2100> pstolowski: regarding that rtm silo request - is that a critical/factory/battery fix?
[15:51] <sil2100> mzanetti: on it
[15:51] <mzanetti> ta
[15:52] <sil2100> Laney: I poked on -release ;) But I'll poke around some more
[15:52] <Laney> There's not the biggest of overlap between the MIR and release teams
[15:53] <pstolowski> sil2100, nope..
[15:53] <sil2100> I was actually waiting for mterry_ to pop up, thought I might have his eyeballs looking at it
[15:53] <mvo> sil2100: uh, I just noticed that I was invited for the standup of you guys this morning, should I come tmorrow? what do you want to talk about?
[15:53]  * mterry_ looks up
[15:53] <sil2100> pstolowski: since generally we're slowly moving away from assigning to ubuntu-rtm
[15:54] <sil2100> mterry_: so, a MIR!
[15:54] <sil2100> mterry_: https://bugs.launchpad.net/ubuntu/+source/qtquickcontrols-opensource-src/+bug/1429836
[15:54] <mterry_> sil2100, which one?  I'm looking at media-hub right now
[15:54] <mterry_> sil2100, huh ok
[15:54] <sil2100> mterry_: this one is actually causing some trouble in the desktop world
[15:55] <sil2100> mvo: hey, uh, I think it was something strange that google did since I didn't change anything in the invitation :)
[15:55] <mterry_> sil2100, desktop uses of the toolkit?  Or for other reasons
[15:55] <sil2100> mterry_: yeah, I guess it's pulled in by webbrowser-app etc.
[15:56] <mterry_> sil2100, ok well I will look at it
[15:56] <mvo> sil2100: aha, ok
[15:56] <pstolowski> sil2100, i see. let me check with pat, he was asking about landing that bug but I think that was just confusion about its importance
[15:56] <mvo> sil2100: even better, then I will claim I knew that and therefore did not show up ;)
[15:56] <pstolowski> s/bug/bugix/
[15:57] <sil2100> mvo: ;)
[15:57] <sil2100> pstolowski: ok, since I think we're only aiming for battery fixes and the u1 fix for the OTA this week
[16:04] <sil2100> bfiller: hey! Apparently the camera-app seems to suffer 7 AP failures on ubuntu-rtm/14.09 - is that something on your team's radar? :)
[16:04] <bfiller> sil2100: yes
[16:05] <bfiller> sil2100: there is a mir issue causing some of the failures that is being worked as well
[16:09] <sil2100> bfiller: ah, ok, so I suppose it's not something that won't be fixed by tomorrow, right?
[16:09] <sil2100> dbarth: hey! How's the fix going? Has it been merged and tested?
[16:10] <bfiller> sil2100: nerochiaro is working on it, some of the issues are already fixed in ubuntu silo 28. hopefully many can be fixed by tomorrow
[16:11] <bfiller> nerochiaro: these are the failures from the nightly smoketests, please make sure they are related to the fixes you are working on http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/252:20150306:20150225-b67e0b6/384/camera_app/
[16:12] <sil2100> bfiller: thanks o/
[16:12] <sil2100> bfiller, nerochiaro: would be grately appreciated, since the dashboard starts looking really nice in overall
[16:14] <sil2100> alex-abreu: hey! Regarding your silo request for rtm - how critical are those fixes? Have they been requested by pmcgowan or anyone from the product team/BQ ?
[16:15] <alex-abreu> sil2100, pmcgowan +1'd them ... (right?)
[16:15] <sil2100> Ok, I see one +1 already
[16:15] <sil2100> ACK, assigning
[16:16] <alex-abreu> sil2100, thx
[16:16] <nerochiaro> sil2100: now that fginther fixed the license problems that prevented camera MR to build, I am waiting to see the results of the test run on this MR https://code.launchpad.net/~phablet-team/camera-app/refactor-and-fix-editor-tests/+merge/250931
[16:16] <nerochiaro> sil2100: which should fix several of the problems
[16:16] <sil2100> The number of fixes for this release is getting bigger and bigger ;)
[16:17] <nerochiaro> sil2100: greyback_ is working on figuring out what causes a random failure somewhere between upstart-app-run and MIR that prevents all tests following the problem to pass
[16:17] <sil2100> rvr: silo 001 in rtm is ready for a re-test ;)
[16:18] <pmcgowan> sil2100, alex-abreu yes we want those for the china dev contest
[16:18] <nerochiaro> sil2100: and from that dashboard link you sent to me there seems to be a few new ones that were not in my original list of things to fix
[16:18] <rvr> sil2100: Ack
[16:27] <oSoMoN> trainguards: can I have a silo for line 44, please?
[16:27] <sil2100> oSoMoN: on it
[16:29] <ralsina> trainguards: also a silo for like 45 please :-)
[16:29] <dbarth> sil2100: nope, i have had to flash the phone fully, to make sure i test the right things; still on it
[16:31] <ralsina> thanks so much
[16:32] <robru> sil2100: hey do you have the diff handy for that uitk MIR issue? I don't remember who acked it but seeing the diff might jog my memory
[16:34] <sil2100> robru: https://ci-train.ubuntu.com/job/ubuntu-landing-003-2-publish/77/artifact/packaging_changes_ubuntu-ui-toolkit_1.2.1433+15.04.20150306-0ubuntu1.diff
[16:34] <sil2100> robru: the core-dev ACKing that missed checking both new deps with check-mir
[16:35] <sil2100> dbarth: thanks!
[16:37] <robru> sil2100: Laney ah it was acked by ken, sorry I forgot to mark that when I hit publish. https://pastebin.canonical.com/127182/
[16:45] <nerochiaro> fginther: i still see the build failures due to the license issue: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-amd64/822/console
[16:47] <davmor2> popey: mzanetti : see row 34 \o/
[16:47] <davmor2> sil2100: ^
[16:47] <sil2100> davmor2: Yaay!
[16:47] <sil2100> popey: publish!
[16:49] <mzanetti> davmor2, awesomes :)
[16:49] <davmor2> sil2100:  I found 1 minor issue that mzanetti is aware of and I'll file a bug for it, now I've finished, but it isn't a regression could just do with a fix for the next update to the app :)
[16:49] <mzanetti> didn't know we're doing the train thing with reminders
[16:50] <davmor2> mzanetti: anything that touches rtm needs a check and we needed to make a single process for everything
[16:50] <mzanetti> sure, makes total sense
[16:51] <mzanetti> davmor2, are we releasing that to vivid/the store too?
[16:51] <sil2100> mzanetti: we only have one store, so anything landing from the clicks is essentially on both rtm and vivid
[16:51] <davmor2> mzanetti: as far as I am aware yes, popey can confirm it though
[16:51] <popey> we have only one store, yes.
[16:51] <mzanetti> ack. perfect
[16:51] <mzanetti> wasn't sure if there's a difference between preinstalled on rtm and the store
[16:52] <popey> reminders isn't pre-installed on krillin
[16:52] <popey> only on nexus
[16:52] <mzanetti> ah
[16:52] <popey> (this may change)
[16:52] <mzanetti> +1 for the previous version not being preinstalled :D
[16:52] <popey> So, sil2100 I don't need to run this past pmcgowan ?
[16:52]  * mzanetti food. biab
[16:53] <nerochiaro> cihelp: fginther: plars: i requested to one of you some times ago to have the system where tests are run set up to have python3-wand installed. i was told it was done. but a test ran today still fails because it is missing: https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/812/testReport/junit/unittest.loader.ModuleImportFailure.camera_app/tests/test_capture/
[16:53] <popey> mzanetti: well done!
[16:53] <plars> nerochiaro: hmm, let me take a look
[16:53] <mzanetti> popey, thanks :D
[16:55] <plars> nerochiaro: ah, I bet it only ended up in the smoke testing branch, not the one used by that job, one sec and I'll verify that. If so, it will be a really quick fix
[17:00] <sil2100> popey: I think we all agreed on getting this landed
[17:02] <popey> ok
[17:08] <sil2100> alex-abreu: are you building the silo?
[17:08] <alex-abreu> sil2100, now yes
[17:17] <davmor2> sil2100: less sailing more bobby in the water desperate to stay afloat ;)
[17:21] <fginther> nerochiaro, regarding the failure on https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-amd64/822/console... Looks like you did a rebuild of another build. Unfortunately, this will cause it to re-use the same parameters which includes specification of the old license check script. In order to avoid this, the job has to be rebuilt from scratch which I did here: https://jenkins.qa.ubuntu.com/job/camera-app-ci/403/
[17:21] <nerochiaro> fginther: ok, sorry. did not see it built from hours so I launched another rebuild
[17:22] <nerochiaro> fginther: i will wait for that one to finish and check tomorrow
[17:22] <fginther> nerochiaro, also looks like other issue is being addressed, sorry about that oversight
[17:23] <nerochiaro> fginther: np
[17:34] <robru> fginther: hey is the engine mojo spec expected to be deployable in juju-lxc?
[17:34] <fginther> robru, yes
[17:35] <robru> fginther: https://pastebin.canonical.com/127187/
[17:37] <fginther> robru, looking
[17:37] <robru> fginther: https://pastebin.canonical.com/127188/ oops there's a bit more. thanks.
[17:38] <kgunn_> trainguards hi, can we get the ubuntu-ui-toolkit deleted from silo 0 ?
[17:38] <robru> kgunn_: sure one sec
[17:38] <kgunn_> we've got no more MP's for that...but have an old plg
[17:38] <kgunn_> pkg even
[17:38] <kgunn_> thanks!
[17:39] <robru> kgunn_: you're welcome. should be gone in a sec
[17:39] <kgunn_> ta
[17:40] <robru> fginther: oops, just noticed I'm not on the VPN. trying again...
[17:41] <fginther> robru, yeah, two things.  Even for local deployments, you need to have the nova OS_, etc environment variables set (it uses swift to upload the application tarball)
[17:41] <robru> fginther: yeah I set OS_PASSWORD correctly I think, had that one saved in my password manager from the last time I tried to deploy in hpcloud months and months ago
[17:42] <fginther> robru, and make sure you have "cheetah python-apt jinja2 statsd python-neutronclient" dependencies installed on the host
[17:42] <bzoltan_> kgunn_: I was already wondering about that uitoolkit thing :)
[17:42] <robru> fginther: where can I get cheetah and statsd from?
[17:42] <kgunn_> :)
[17:43] <plars> nerochiaro: ok, if you want to retry that job, it should work now
[17:43] <kgunn_> bzoltan_: hey, while you're here...who is the best person to include on grid unit discussion from sdk team?
[17:43] <robru> fginther: you mean python-cheetah and python-statsd?
[17:43] <fginther> robru, oops sorry, yep try those
[17:43] <robru> fginther: k thanks
[17:45] <nerochiaro> fginther: can you please restart the build job one more time after the change plars made ?
[17:45] <plars> nerochiaro: I can do that
[17:46] <nerochiaro> plars: please do then
[17:46] <plars> nerochiaro: I didn't want to do it without taking to you first though, if you are ready for it I'll push it through again though
[17:46] <fginther> plars, in this case, the build has to be entered from scratch because the parameters changed (due to another change in the job config)
[17:46] <nerochiaro> plars: fginther: the MR is ready, so please push a rebuild
[17:47] <plars> fginther: so it's actually https://jenkins.qa.ubuntu.com/job/camera-app-ci/404/ that has to start over then?
[17:48] <fginther> plars, right, just do a new build of the camera-app-ci job and copy over the landing_candidate, merge_proposal and candidate_revision parameters
[17:48] <plars> fginther: ah, I just hit rebuild on it, which I think should do all we need right?
[17:48] <plars> nerochiaro: it's in progress
[17:50] <fginther> plars, almost, "hooks" has been updated in the new config. So you could do a rebuild, then copy in the new value of hooks from the job configuration
[17:51] <plars> ah, ok
[17:51] <fginther> sorry about that
[17:51] <fginther> it's not the most elegant design
[17:51] <plars> np, I remember seeing that mp now, just forgot it was related to this
[17:51] <plars> timing...
[18:04] <dbarth_> trainguards: can i get a quick reconfig on rtm-010 please?
[18:04] <robru> dbarth_: sure,one sec
[18:04] <dbarth_> this is to wrap the image (hopefully)
[18:06] <robru> dbarth_: ok, good to go. just mind the conflict in rtm1
[18:06] <dbarth_> robru: which conflict?
[18:07] <dbarth_> robru: ah i see
[18:07] <robru> dbarth_: yeah system settings
[18:08] <robru> kenvandine: will you be publishing silo rtm 1 shortly? I see it's approved. dbarth_ has a conflicting silo
[18:08] <dbarth_> robru: hmm, then maybe i can drop the system-settings branch to avoid any mistake
[18:08] <dbarth_> it's "belt & suspenders", whereas the signon fix is the key one
[18:09] <robru> dbarth_: well I'm not sure what the plan is. if ken will publish his you can just rebuild yours afterwards and it'll be fine.
[18:09] <dbarth_> robru: i dropped the uss line, if you can reconfig one last time
[18:09] <robru> dbarth_: ok
[18:11] <davmor2> popey: I think there is a serious bug in the weather app that jibel will be able to attest to.  It say sunny in London that can't be right, it should default to rain surely ;)
[18:11] <popey> lulz
[18:12] <popey> it also is dark!
[18:23] <elopio> ping cihelp: is it ok for you if we make a dep8 test that requires the host to be on vivid?
[18:25] <plars> elopio: the host? can you give me more details?
[18:25] <robru> fginther: https://pastebin.canonical.com/127192/ no such luck I'm afraid, even with deps installed and env vars set
[18:25] <robru> and on the vpn
[18:26] <fginther> robru, looking
[18:26] <robru> thanks
[18:27] <elopio> plars: we have a host and a testbed. On the host, we call adt-run and it executes the dep8 tests in the testbed.
[18:27] <elopio> for this project, we might require the machine that calls adt-run to be on vivid to use the latest packages from ubuntu-system-image.
[18:28] <elopio> plars: so, do we have vivid machines on the lab to execute the tests?
[18:28] <plars> elopio: no, but if it's just a certain version of adt-run that's required, I think it would be easier to make sure we have that version
[18:28] <plars> elopio: what kinds of tests are these?
[18:29] <elopio> plars: what we need is a specific version of system-image-dbus.
[18:29] <fginther> robru, I gave you some missing info, one moment, trying to figure out what else I might have missed
[18:29] <elopio> plars: over the air upgrades.
[18:29] <robru> fginther: yeah I'll have to update the README once I finally get this working
[18:32] <plars> elopio: assuming the thing calling adt-run is on trusty, would it be possible to give us a list of hard dependencies? It would seem that we should easily be able to get a backport of those things if we really need to.  It gets messy really fast if we have to have a different host environment for tests, and much worse if it has to be on a development version.  We need a pretty stable environment or we're likely to hit infrastructure p
[18:32] <plars> roblems
[18:33] <plars> elopio: it sounds like these tests may be special enough to need a story on our side though, have you talked to Ursinha about it?
[18:33] <elopio> plars: I'll ask.
[18:34] <elopio> plars: not yet. We are just defining what the tests are, and how to run them.
[18:34] <elopio> at the end of this week we'll have our requirements better defined.
[18:35] <plars> elopio: anything you can do to reduce special requirements on the host side will surely help with stability of the test environment
[18:35] <plars> something to think about
[18:37] <fginther> robru, sent you an updated email
[18:37] <robru> fginther: thanks
[18:39] <elopio> plars: ack. Thanks for the info. We have plenty of options, so we'll make them adjust to trusty hosts.
[19:11] <rvr> ricmm: Vivid silo 13 is approved
[19:13] <ricmm> rvr: thanks
[19:13] <ricmm> rsalveti: could you publish 13 for me please
[19:15] <rsalveti> ricmm: sure
[19:18] <rsalveti> ricmm: done
[19:19] <ricmm> thanks
[19:29] <davmor2> popey: row 42
[19:35] <popey> davmor2: \o/ sweet! Thank you.
[19:36] <davmor2> popey: no thank you for the etherpad makes it much easier :)
[19:39] <popey> \o/
[19:39] <popey> pmcgowan: weather updated in store.
[19:41] <pmcgowan> popey, yay
[19:44] <popey> \o/ two down, loads to go!
[19:44] <dbarth_> robru, davmor2, whoever can wrap the image; silo 010 is ok for qa now
[19:44] <davmor2> dbarth_: I'm about to EOD so one for ToyKeeper probably
[19:45] <dbarth_> ok, let me know; i'll be around
[19:47] <ToyKeeper> I've got a meeting in a few, but perhaps after that?
[19:53] <robru> dbarth_: yep I'm happy to publish once ToyKeeper qa's it.
[19:59] <dbarth_> perfect; ToyKeeper it's in your hands now ;)
[20:00] <sil2100> dbarth: teh silo is ready? :)
[20:13] <dbarth> sil2100: it is yes
[20:29] <sil2100> \o/
[21:09] <robru> bfiller: failure looks transient, retrying: https://ci-train.ubuntu.com/job/ubuntu-landing-028-1-build/31/console
[21:13] <ToyKeeper> dbarth: Starting now.
[21:19] <dbarth> ToyKeeper: ok
[21:20] <ToyKeeper> Well, that's what I get for being efficient and starting a new flash before finding out what the silo does.  Gotta go reflash again now.  ;P
[21:20] <dbarth> ToyKeeper: i may switch to sleep mode in a bit, but keep me posted
[21:21] <dbarth> ToyKeeper: right, sorry; flash to #16, create u1 account, apply silo; reboot; flash to #18 and check that you still have the u1 account around
[21:21] <ToyKeeper> Yeah, I just should have read it first.  :)
[22:43] <dbarth> ToyKeeper: everything ok ?
[22:44] <ToyKeeper> dbarth: So far, yeah; OTA always takes forever here.
[22:45] <dbarth> ok
[22:58] <ToyKeeper> ... that is, if citrain device-upgrade would stop failing.  This is new...
[23:38] <ToyKeeper> dbarth...  left.  D'oh.
[23:38] <ToyKeeper> Test tools finally stopped failing, and I *still* see no difference at all pre- and post-silo.


[00:20] <sebner> geser: fails as well
[02:27] <vhenry93> Hi, developer newbie here who would like to contribute. Question, is MOTU or bugsquad best place to start?
[02:33] <vhenry93> disregard, found the answer.
[06:02] <simar> Hello everyone
[06:02] <simar> I have a doubt..
[06:03] <simar> https://wiki.ubuntu.com/PbuilderHowto pbuilder sets up a chroot environment for for building source packages for ubuntu..
[06:07] <RAOF> simar: Do you have a question?
[06:07] <paultag> simar: yes?
[06:08] <simar> So how this is different from.. https://wiki.ubuntu.com/DebootstrapChroot
[06:08] <paultag> simar: check /var/cache/pbuilder/
[06:08] <simar> I mean do I also need a chroot enviroment for building source packages..
[06:08] <paultag> simar: it stores it in a .tar.gz and cleans it after use to ensure a clean build (and good to check if it's deps are right)
[06:09] <paultag> simar: pbuilder builds source packages
[06:09] <paultag> last I checked, anyway :)
[06:09] <RAOF> No, but it can be useful to have a chroot environment if you want to check that it'll build in the archive.
[06:10] <simar> No chroot creats binary packages .. but when i have to create source packaes by debuild -S then should i do that in a chroot
[06:10] <simar> *No pbuilder creats ....*
[06:12] <RAOF> Ah, no.
[06:12] <RAOF> There's no reason to create source packages in a chroot.
[06:14] <simar> paultag, Does it means something like pbuilder also creates a chroot but handles it nicely in a tar.. So can we make binary packages without pbuilder but with a simple chroot .. I will be happy if you can tell me what are all the ways to create a chroot enviroment .. tha will make it more clear
[06:15] <cdbs> simar: Why would you avoid using pbuilder?
[06:15] <cdbs> simar: it speeds up the chroot creating, extracting and building, and automates it all
[06:15] <paultag> simar: pbuilder just creates a chroot of your choosing, puts it into a tar, and automates extracting it, updating it, and so forth without builds klobbering ( such as leaving old deps that may "save" a ftbfs )
[06:15] <paultag> cdbs: +1
[06:15] <simar> RAOF, But if I want to create source packages for natty and I'm currently using maverick won't dependies gonno conflict..
[06:15] <RAOF> Fundamentally, creating a chroot is not much more than running debootstrap on a directory.  But pbuilder and sbuild are two tools that make managing build chroots easy.
[06:16] <cdbs> simar: of course not
[06:16] <paultag> simar: you can create a natty pbuilder env
[06:16] <cdbs> simar: install the package ubuntu-dev-tools and then use the pbuilder-dist script as a front-end of pbuilder, it will make life easier
[06:16] <cdbs> simar: eg pbuilder-dist natty create
[06:16] <paultag> +1 there
[06:16] <cdbs> simar: then pbuilder-dist natty build foo.dsc
[06:16] <RAOF> simar: If you're making a *source* package you generally don't care about the build-dependencies, because you're *not* building the code.
[06:16] <simar> oh..
[06:17] <RAOF> simar: The only dependencies you need to care about for source packages are the packaging tool dependencies - quilt, dpkg, debhelper, cdbs, etc.
[06:17]  * cdbs is a dependency :)
[06:17] <RAOF> cdbs: Only for annoying packages :P
[06:18] <cdbs> RAOF: exactly. Even I prefer dh7/8 over cdbs
[06:18] <simar> cdbs, I use pbuilder but don't understand what is it.. n I get confused when I read something like 'Chroot enviroment' in packaging guide..
[06:18] <paultag> simar: play with it
[06:19] <simar> cdbs, I should use pbuilder thats for sure
[06:19] <paultag> simar: you'll grab the idea after you try to hack it into normal usage (and read the man page)
[06:19] <cdbs> simar: pbuilder builds in a chroot environment. When they ask you to build in one, just build using pbuilder
[06:19] <cdbs> simar: so, you have a natty pbuilder chroot already?
[06:19] <RAOF> simar: Basically, pbuilder is a way of turning a source package into a binary package, while not polluting your regular install.
[06:20] <simar> cdbs, No but I will have one .. today .. using the command pbuilder-dist
[06:20] <cdbs> simar: yes, that's the way to go
[06:21] <simar> RAOF, I understand that .. but when I create source packages .. then can I do that in my regular directory of maverick...
[06:21] <simar> I will be creating source packages for natty
[06:21] <RAOF> simar: Right*.  (* Unless the source package uses *packaging* tools available in Natty but not Maverick; there aren't a lot of those, but they exist)
[06:22] <RAOF> There's no need to do anything special for source packages.
[06:22] <simar> RAOF, Sould this be a point of worry for a beginner...??
[06:23] <RAOF> No.  The cases where it matters are very rare.
[06:23] <RAOF> And you'll know when it happens.
[06:24] <simar> @everyone Thanks for help. I think I got most of the stuff. But I want to know what usually developers do. I can do all this in virtual machine as well. So should I use pbuilder or virtual machine..
[06:24] <RAOF> I use sbuild personally; others use pbuilder.
[06:25] <cdbs> simar: I 'd recommend pbuilder whether you use in a VM or outside it
[06:25] <simar> RAOF, why si
[06:25] <simar> *so
[06:25] <simar> cdbs, ok.. that sounds more clear..
[06:25] <cdbs> simar: the main point of a pbuilder is to check whether the build-depends are okay and the package builds well in the target distro
[06:26] <simar> cdbs, ya i understand that..
[06:26] <RAOF> sbuild is (closer to) what's used on the buildds, so it sometimes picks up problems that pbuilder wouldn't.  It's also more powerful, so I can do funky things with it.  pbuilder (and particularly pbuilder-dist) are plenty good, though.
[06:26] <cdbs> simar: I am using natty for daily use (mind you its buggy) and even after that I use pbuilder, not sane building using debuild
[06:28] <paultag> The issue is that it will pick up system deps that might not be on a build machine -- let's say you forget libfoo-dev in your build-deps, but you have it installed locally. Your build will be fine, but when you upload it will FTBFS
[06:29] <paultag> That's why we use chroots to test -- and pbuilder to keep up sane
[06:29] <simar> paultag, ok..
[06:30] <simar> and what exactly is a debootstrap? thats a term related to these i think..
[06:30] <paultag> simar: it's what creates a chroot -- layered under levels of sanity it's called for pbuilder
[06:31] <paultag> simar: because you can't just chroot into ./chroot-dir, you also have to have ./chroot-dir/proc, dev and a few other fun things before you have a sane env
[06:32] <paultag> "One does not simply chroot into mordor"
[06:32] <paultag> if you will
[06:32] <RAOF> debootstrap is DEbian Bootstrap - it basically downloads and unpacks all the packages you need to set up a debian environment (you need a shell, libc, dpkg, etc) without needing any of the tools in there.
[06:32] <broder> paultag: +1 :)
[06:32] <paultag> ;)
[06:33] <simar> i got it .. so much thanks for help ... :))
[06:33] <paultag> simar: godspeed!
[06:33] <simar> paultag, ;)
[08:01] <dholbach> good morning
[09:07] <RainCT> morning dholbach :)
[09:08] <dholbach> hola RainCT - Feliz Cumpleaños! :)
[09:09] <RainCT> dholbach: thanks :)
[09:51] <iulian> Morning dholbach, RainCT.
[09:51] <iulian> Uhmm.
[09:51] <dholbach> hi iulian
[09:51] <iulian> Happy what?
[09:51] <dholbach> Birthday!
[09:52] <iulian> Uh oh!
[09:52] <iulian> RainCT: Happy birthday mate!
[10:00] <RainCT> iulian: thanks!
[10:01] <sebner> RainCT: happy birthday! :)
[10:01] <sebner> ~o~ ~o~ ~o~ ~o~ ~o~
[10:18] <cdbs> RainCT: Happy Birthday
[10:25] <RainCT> sebner, cdbs: ~o~ thanks ~o~
[13:32] <Raydiation> hi ive written something like ampache, just in django and with a better userinterface plus ogg vorbis support (its in HTML5). you can see a preview on http://laudio-player.org/
[13:33] <Raydiation> ive also done the packaging (was a lot of work) and now its in revu http://revu.ubuntuwire.com/p/laudio
[13:33] <Raydiation> if someone is interested :)
[13:33] <Raydiation> after install its available under http://localhost/laudio
[16:12] <gondoi> blueyed: morning! I think that branch is all ready to go for #699967 SRU.  Do I need to propose merge again?
[16:40] <ari-tczew> bug 699967
[16:41] <ari-tczew> gondoi: You don't need to propose again. However, there are still some issues.
[16:41] <gondoi> :-(
[16:41] <gondoi> okay
[16:41] <ari-tczew> I'll comment.
[16:41] <gondoi> thanks
[16:58] <ari-tczew> gondoi: done
[16:59] <gondoi> ari-tczew: thanks, I'll have a look
[17:25] <ari-tczew> siretart: ping
[17:31] <gondoi> ari-tczew: I'm not seeing where the DEP-3 info needs to go
[17:32] <gondoi> oh wait, I think I do now
[17:32] <gondoi> is there a tool to embed that? or is it manually created?
[17:33] <ari-tczew> gondoi: manually
[17:33] <ari-tczew> gondoi: but tool in future is a good idea
[18:03] <grunthus> Hi cyphermox.
[18:05] <micahg> gondoi: source format 3 can create most of what you need if the package supports it and you're creating the patch
[18:09] <cyphermox> grunthus, hey
[18:10] <grunthus> Hi cyphermox, I was pleased with how the fix went overall!
[18:10] <ari-tczew> micahg: do you encourage to change source format in Ubuntu instead Debian?
[18:10] <micahg> ari-tczew: no
[18:10] <micahg> that's why I said, if the package supports it :)
[18:10] <grunthus> cyphermox: Funny issue with my DEBFULLNAME etc however as those are set in .bashrc
[18:13] <grunthus> cyphermox: I have to go out now for 2 hours. Speak later if you are around!
[18:17] <grunthus> cyphermox: fixed DEBEMAIL, just had to export!
[18:19] <cyphermox> grunthus, great :)
[19:05] <bcurtiswx> i downgraded a package from the gnome3 PPA to natty (nautilus), but it still links to libgtk-3.0.so.0 => /usr/lib/libgtk-3.0.so.0 (0x00007fd03e47b000).. how can i change that back to -2.0 ?
[19:06] <geser> bcurtiswx: this is from ldd nautilus?
[19:06] <bcurtiswx> geser, correct
[19:06] <geser> bcurtiswx: is it nautilus linking against libgtk3 or one of the libs it uses?
[19:07] <geser> I guess the later
[19:07] <bcurtiswx> geser, the later probably. how would I find out which?
[19:07] <geser> try and error with ldd
[19:08] <geser> or see which packages will be gone too if you remove it (the package for libgtk3) and check those
[19:10] <blueyed> ari-tczew, micahg: gondoi is working on a SRU with a patch that has been applied upstream already - I do not think he should edit the patch to make it match DEP-3. After all, that would have been the job of the committer for the Natty package (which is me).
[19:11] <gondoi> blueyed, ari-tczew: i pushed up the changes earlier
[19:11] <bcurtiswx> geser, apt-cache rdepends was my savior
[19:11] <bcurtiswx> it was libnautilus-extension1 that i didn't downgrade too
[19:11] <bcurtiswx> geser, thx for the help :)
[19:12] <micahg> blueyed: I was just answering a question that was asked, not commenting on relevance of the headers
[19:13] <blueyed> micahg: you are right, of course. thanks.
[19:13] <micahg> blueyed: also, is there a good chance to get the new upstream version in natty (in which case the patch would disappear?), in any case, a new upload is a good chance to get that recorded somewhere, and in an SRU, if there are any problem with the patch, it's probably best to have all the info right there
[19:16] <blueyed> micahg: there's no new release yet (AFAIK), would be munin 1.4.6. Of course, additional info won't hurt. And it was added by gondoi.
[19:16] <ari-tczew> blueyed: patch should be included in devel (natty) first, then SRU
[19:16] <blueyed> gondoi: the author lines appear to be wrong: we are both not the author of the patch.
[19:17] <blueyed> ari-tczew: it is in natty already.
[19:17] <ari-tczew> blueyed: a lot of patches are go through SRU and everyone has got DEP3 tags. why gondoi's case should be special?
[19:17] <blueyed> gondoi: that is quite pedantic though, but should be easy for you to remove those lines and push again.
[19:18] <blueyed> ari-tczew: there are no DEP3 tags in the natty patch. so it differs from natty. While this is only meta info, it is better to use the same patch as with the devel version, isn't it?
[19:19] <ari-tczew> blueyed: I won't click 'Approve', dunno how about you.
[19:19] <blueyed> ari-tczew: just because, or because of some reason?
[19:19] <blueyed> ari-tczew: there are DEP3 tags now.
[19:20] <ari-tczew> blueyed: that's policy. every patch which is going to Ubuntu archive should be described by DEP3 tags
[19:20] <ari-tczew> Debian should as well
[19:20] <gondoi> blueyed, ari-tczew: DEP3 modified
[19:21] <micahg> blueyed: if there's a problem with the headers, that should be caught test building the SRU, otherwise, it is the same patch
[19:22] <geser> ari-tczew: is the DEP3 requirement documented somewhere?
[19:23] <ari-tczew> geser: https://wiki.ubuntu.com/PackagingGuide/PatchSystems#Patch Tagging Guidelines
[19:23]  * micahg was thinking about asking that
[19:23] <ari-tczew> merged from https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines
[19:24] <blueyed> gondoi: approved, thanks so far.
[19:24] <micahg> it seems to be a suggestion (a very good one) as opposed to a hard requirement though
[19:25] <ari-tczew> micahg: nitpick
[19:25] <geser> I read also it as "nice-to-have" but no requirement
[19:25] <geser> I've never added any DEP3 headers when fixing any FTBFS till now
[19:26] <gondoi> blueyed: thanks
[19:45] <ari-tczew> gondoi: is this line not necessary? $node = lc($node);
[19:45] <ari-tczew> looking from http://munin-monitoring.org/changeset/3404#file19
[19:48] <gondoi> ari-tczew: it's already there from the 1.4.5 release src
[19:48] <gondoi> that's what started the bug
[19:50] <ari-tczew> gondoi: you don't understand me.
[19:50] <gondoi> that view is a bit odd, but it looks like the _list_services line had the correct code, but somehow regressed in a later revision
[20:04] <ari-tczew> gondoi: look on the patches:
[20:05] <ari-tczew> gondoi: natty: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/munin/natty/view/head:/debian/patches/upstream_bug_952.patch
[20:05] <ari-tczew> gondoi: upstream: http://munin-monitoring.org/changeset/3404#file19
[20:05] <ari-tczew> changes on file Server.pm are not the same
[20:05] <ari-tczew> is it correct?
[20:06] <ari-tczew> blueyed: do you have PPU for munin?
[20:07] <ari-tczew> blueyed: ok nevermind
[20:08] <gondoi> ari-tczew: that line is already there... no need to patch it
[20:08] <gondoi> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/munin/maverick/view/head:/node/lib/Munin/Node/Server.pm#L93
[20:09] <gondoi> L174 is the one that is patched and incorrect
[20:10] <ari-tczew> gondoi: ok, some concerns about DEP3, will quickly comment
[20:18] <ari-tczew> gondoi: done. please fix rapidly and I'll ask patch pilot to upload it today ;-)
[20:27] <bcurtiswx> what are the basic steps in a sync, is this documented well in the wiki?
[20:27] <Rhonda> Yes.
[20:27] <maco> bcurtiswx: just request one on launchpad. subscribe archive admins
[20:27] <maco> theyre the only people who can do them
[20:27] <bcurtiswx> maco, OK
[20:28] <Rhonda> The requestsync tool is extremely helpful for that
[20:28] <Rhonda> No need to extract and write it up all yourself.
[20:28] <maco> dont use the rogue script some people use for syncing around the archive admins
[20:28] <maco> it apparently breaks stuff
[20:29] <maco> (yeah, i got told this /after/ using that script...)
[20:29] <ari-tczew> bcurtiswx: https://wiki.ubuntu.com/SyncRequestProcess
[20:30] <bcurtiswx> ty ty ty :)
[20:34] <ari-tczew> np
[20:35] <siretart> ari-tczew: this is a contentless pong.
[20:36] <ari-tczew> siretart: FTBFS in libva wasn't fixed
[20:36] <siretart> ari-tczew: pardon me?
[20:36] <siretart> what's missing?
[20:37] <ari-tczew> siretart: debian bug 609554
[20:37] <ari-tczew> I tried to build it on natty and it still fails to build due to linking
[20:41] <siretart> ari-tczew: so you're basically saying that http://git.debian.org/?p=pkg-multimedia/libva.git;a=blob;f=debian/patches/remove-unneeded-dep2.patch is incomplete or broken, right?
[20:43] <ari-tczew> siretart: probably yes
[20:44] <siretart> in this case that patch needs to be revised/fixed
[20:54] <ari-tczew> siretart: I could help you fix it, but not today.
[21:19] <geser> TrudEev4
[21:19] <geser> crap, wrong window :(
[21:19] <Laney> :(
[22:53] <grunthus> hi cyphermox again,
[22:53] <grunthus> you probably got my email...
[22:54] <grunthus> now I need to find another task.
[23:11] <cyphermox> grunthus, I sent you links for two ways to find new stuff to do -- LP bugs (bitesize), and Harvest. but one other way is to find something that annoys you and try to fix it :)
[23:12] <grunthus> Thanks cyphermox, I see that now.
[23:16] <cyphermox> grunthus, now just like yesterday, I'll need to travel from the office to back home, so I'd be back in hopefully about an hour
[23:16] <grunthus> Well, cyphermox, the next hour will be midnight for me.
[23:16] <cyphermox> ah
[23:16] <cyphermox> those pesky timezones
[23:17] <grunthus> I hope to be in bed! What timezone are you?
[23:17] <cyphermox> EST
[23:17] <grunthus> GMT+5
[23:17] <cyphermox> -5
[23:17] <grunthus> I'm UT
[23:18] <grunthus> EST is GMT-5
[23:18] <grunthus> ?
[23:18] <cyphermox> yes
[23:18] <grunthus> of course!
[23:36] <grunthus> Hi, bzr branch is showing port 22:Connection refused. Is that down to maintenance mode?
[23:51] <micahg> grunthus: yep, LP is read-only at the moment (bzr down), should be about 45 more minutes
[23:53] <grunthus> micahg: thanks for info.


[10:16] <rsajdok> https://code.launchpad.net/~ris/loco-team-portal/fix-552762/+merge/142553/comments/341945 I've created a table "TeamEventVenue" which links "Teamevent" and "Venue". What does it mean "store in memory"?
[10:30] <daker> rsajdok: i mean if we run the migration script we will lost all the relation between events and venues
[10:40] <rsajdok> daker: Do you mean past relations?
[10:41] <daker> yep
[10:41] <daker> rsajdok: how do you will relink the re-generate the new TeamEventVenue data ?
[10:42] <rsajdok> daker: ah, I  understand now :)
[10:44] <rsajdok> daker: Should I prepare a script that migrates the data?
[10:45] <daker> it can be done on the migrations script
[10:46] <rsajdok> daker: Should I use for that south?
[10:49] <daker> rsajdok: something like this http://paste.ubuntu.com/5598009/
[11:33] <rsajdok> daker: ok, Thanks You. I am going to prepare it in a few days.
[11:33] <daker> ty


[00:52] <user|59849> Is it possible to have 2 OS's on one computer at a time?
[00:53] <sintre> yes
[00:53] <user|59849> Alright, thank you.
[02:38] <MK> hey guys, for some reason Discover isn't letting me see anything or search for anything. When I go to Advanced->History it shows everything correctly, but the Discover and Installed tabs otherwise don't list any programs. Any idea what the problem could be?
[02:39] <MK> On 16.04.2
[02:40] <sintre> discover is a mess
[02:40] <sintre> its a work in progress
[02:40] <sintre> anything in paticular you're looking to install
[02:41] <MK> nah I know how to install things from the terminal, but I wanted to try to diagnose and fix this problem in case it were a symptom of some other problem
[02:41] <sintre> i use 16.04.1 with back ports
[02:42] <sintre> i haven't done a clean install of 16.04.22 yet
[02:42] <sintre> sudo add-apt-repository ppa:kubuntu-ppa/backports
[02:42] <sintre> then the normal sudo apt update
[02:42] <sintre> then sudo apt full-upgrade
[02:42] <sintre> maybe problem has been found ands fixed
[02:43] <sintre> just launched discover , seems kinda bare
[02:43] <sintre> but does have some apps poping up
[02:43] <sintre> mostly ones already installed
[02:44] <MK> it shows apps in the spotlight, but nothing in most popular/best rating or when searching, or when I click any of the categories
[02:44] <sintre> its bringin up stuff that i don't have installed as well
[02:44] <sintre> type in chess
[02:44] <sintre> i don't play or have any chess apps installed
[02:44] <MK> Nothing
[02:45] <sintre> see if it brings any games up
[02:45] <MK> It shows VLC in the spotlight, but searching for VLC comes up nothing @_@
[02:45] <MK> i'll just use muon for the time being I guess
[02:45] <sintre> yea seems bare bones atm
[02:48] <sintre> i guess i'd rather see it bee somewhat bare and actually work than in past incarnations
[02:48] <sintre> but kubuntu team isn't responsible for discover a kde team i believe is
[08:22] <lordievader> Good morning
[08:31] <viewer|54513> Hello everybody. I'm not sure, whether this is the right place or not, but how does the Kubuntu Team wants to be cited in a scientific thesis?
[08:32] <lordievader> viewer|54513: I'd ask that in #kubuntu-devel, there are more developers in there.
[08:32] <viewer|54513> cool, thanks for the tip
[11:36] <BluesKaj> HI all
[21:09] <heinzelmaenchen> hi everyone, I have a problem with kde on x220 and dockingstation. an external monitor is not working, xandr and bios setting was not working. any solutions?
[21:20] <genii> heinzelmaenchen: FN-F7 key combo will cycle through multiple monitor configurations at a hardware level, might want to try it
[21:46] <heinzelmaenchen> genii: nice, worked perfectly! thanks a lot, was looking for a solution for days! cheers!
[21:47] <genii> heinzelmaenchen: Glad to assist :)
[21:50] <heinzelmaenchen> hopefully this is it for now, had more problems with kubuntu than xubuntu and ubuntu, but it's worth it.
[21:51] <sintre> good team of people that will help trouble shoot anything
[21:51] <sintre> not all communities you can say that about
[21:52] <sintre> hope to see you around :)
[21:55] <rarity> hello
[21:56] <rarity> I love kubuntu i think it's the ubuntu i will stick with :D
[21:56] <sintre> glad to hear :)
[21:57] <rarity> still setting up stuff. mostly the dvd support
[21:57] <sintre> run into any problems just post em in the channel
[21:58] <sintre> still work hours for alot of people but eventually somebody will come around to assist
[22:00] <rarity> i think i can manage. i been useing open sorce ubuntu system's for a few month's now and learning the sudo command's well
[22:13] <heinzelmaenchen> plasma ist by far the most beautiful environment... I was shocked how good it looks