[06:09] <zub> Hi. I'm using an OptionSelector with OptionSelectorDelegate with custom images (iconSource).
[06:10] <zub> I see there is the property contrainImage, which is almos what I need.
[06:10] <zub> I'd also like to set margins, so that the image is not occupying 100% of the height of the delegate
[06:10] <zub> is there a way how to do it?
[06:11] <zub> If it was possible to change the margins of the delegate's leftIcon...
[06:18] <zub> hm, it seems I can get to the image via a hack like: Component.onCompleted: this.children[0].children[0].height -= units.gu(2); but that's hacky and fragile
[06:51] <zub> http://paste.ubuntu.com/12011980/ ... any idea how to make this less hacky while sticking to the OptionSelectorDelegate?
[07:13] <dholbach> good morning
[11:54] <didrocks> is that wanted that the activeFocusOnPress from https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Pickers.DatePicker/ seems to be taken from TextField doc?
[14:16] <pindonga> hi, is this the right place to ask about snappy packages too?
[14:42] <popey> pindonga: there is #snappy
[14:46] <pindonga> thx popey
[14:47] <popey> np
[14:53] <cwayne> should .local/share/<app-name> be created automagically? or is it up to the app to create it if its needed?
[15:11] <zub> I asked already in the morning, but perhaps more people are here now... any idea on how to do this: http://paste.ubuntu.com/12011980/ without such horrible hack?
[15:12] <popey> zub was one of my fave speccy games.
[15:12] <zub> i.e. to make the OptionSelectorDelegate's icon smaller (so that the image does not fill the height completely - that looks ugly)
[15:13] <zub> https://en.wikipedia.org/wiki/Zub (not related :) )
[15:23] <popey> I heard it was origially called Zob, but changed at the last minute because Zob is a rude word in some language.
[16:35] <nemo> mcphail: any news? ☺
[20:42] <sl1rpy> okay im getting kinda fustrated.  i released some apps in high school that used the .net framework and made money on it.  im trying to find a way to market myself in the linux community *1-2$ apps* ... wondering why paid apps havent been in the software store for a while now and wondering if i should just advertise my website instead? any tips are appreciated...
[20:47] <wellsb> Is there no way to apply a conditional userscript to a webview with oxide?  You could do url:variable?style1.js:style0.js with qtwebkit.experimental back in the day
[20:59] <mhall119> sl1rpy: the desktop store is on it's way out, it's being replaced by the much better app store developed for the phone
[21:00] <mhall119> so for now, if you're targeting desktop, yeah you're better off just advertising your own website and .deb package
[21:01] <sl1rpy> huh, thanks for the tip.  now would forums be a good way to get the word out about my portfolio?
[21:01] <sl1rpy> idk what the chat policies are, havent read them... i know some of them dont like ads
[21:02] <sl1rpy> mhall119, ^
[21:05] <sl1rpy> would it be better to compile software in 14.04 than 15.04?
[21:08] <mhall119> sl1rpy: forums are fine, so is out Google+ App Developers group
[21:11] <sl1rpy> oh cool.. do you have linky to it? mhall119
[21:12] <sl1rpy> nvm ... found it
[21:14] <sl1rpy> mhall119, only thing left is whether 15.04 or 14.04 lts is best for developing game and software...
[21:30] <kivi> !ping
[21:30] <kivi> !ping
[21:30] <kivi> !ping
[21:48] <wellsb> Is there still no documentation for Oxide?
[23:28] <kalikiana> wellsb: how about https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Web/
[23:29] <wellsb> kalikiana, Nah, I need oxide for UserScripts and some other features.  I figured out a way to do what I wanted.  Thanks
[23:30] <kalikiana> ah, okay
[23:30] <kalikiana> wellsb: what are you working on?
[23:32] <wellsb> I had an old app (esv-bible) for ubuntu touch, and it has been broken for eons because so much had changed with the api (I was still using Ubuntu.Components.Extras.Browser).  Anyway, it has a night mode for reading, and I needed to be able to style a webview one of two ways depending on this setting.  With oxide, a webview can only be set to a context (w/ associated userscripts) on creation, so I had to find a new way
[23:37] <kalikiana> wellsb: seems like a pretty big limitation. how did you handle it now?
[23:41] <wellsb> It's a bit convoluted, but it works.  In my webview, I wrote a function to execute javascript rootFrame.sendMessage("oxide://", "EXECUTE", {code: code});  and then in my .js file I have a message handler to handle the above and then I have the function in my .js style, and I pass a qml variable to it as a string in the executejavascript function of the webview


[00:00] <ahoneybun> clivejo: https://cerberus.mycroft.ai/
[00:00] <yofel> on the positive side, I think I'm done with the ci image publisher. Time to spend the weekend on other parts
[00:00] <clivejo> it thinks Im in the US
[00:01] <clivejo> ahoneybun: did you get the plasmoid working?
[00:03] <clivejo> grrrrr
[00:03] <clivejo> "hey mycroft, open firefox"
[00:04] <clivejo> replies "Firefox (movie) release date is june 18, 1982"
[00:04] <clivejo> frustating!
[00:05] <yofel> lol
[00:05] <tsimonq2> hahahahahaha
[00:05] <clivejo> and its 42 degrees
[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #826: SUCCESS in 6 min 48 sec: http://kci.pangea.pub/job/mgmt_merger/826/
[00:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #806: FIXED in 6 min 49 sec: http://kci.pangea.pub/job/mgmt_progenitor/806/
[00:07] <clivejo> keeps crashing plasmashell
[00:08] <clivejo> LOL
[00:09] <clivejo> wrong enniskillen my silly friend
[00:12] <clivejo> NPR washington ?!?
[00:12] <clivejo> eakkk
[00:12] <clivejo> how to I stop the news?!?
[00:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalgebra build #270: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kalgebra/270/
[00:13] <clivejo> OMG!!
 (Voice, 16s)https://irc-attachments.kde.org/1OSY4SWS/file_2200.oga
[00:14] <clivejo> how do I stop it!!
 huh?
[00:16] <clivejo> there is no way to stop the news
[00:17] <clivejo> when I say "Hey Mycroft, stop the news" it starts a new one
[00:17] <clivejo> https://github.com/MycroftAI/mycroft-core/issues/24
[00:19] <clivejo> I do like the way it displays stuff using krunner
[00:20] <clivejo> has a long way to go to be useable me thinks
[00:21] <clivejo> "hey mycroft, put a log on the fire" sorry I couldnt find an answer, perhaps you meant fire instead
 Hey mycroft, open the pod bay doors.....
[00:25] <clivejo> Im sorry Dave
[00:25] <clivejo> Im afraid I cant do that
[00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalgebra build #172: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kalgebra/172/
[00:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #267: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/267/
[00:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #76: STILL FAILING in 21 min: http://kci.pangea.pub/job/zesty_unstable_kdb/76/
[00:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-call-ui build #193: FIXED in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-call-ui/193/
[00:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #118: FIXED in 22 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/118/
[00:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmailtransport build #157: FIXED in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kmailtransport/157/
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdb build #49: NOW UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kdb/49/
[00:30] <clivejo> if all KDE apps could be controlled via mycroft it would be awesome!
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #419: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/419/
[00:33] <clivejo> time for bed!
[00:33] <clivejo> night all
[00:34] <tsimonq2> clivejo: Sweet dreams
[00:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #133: STILL FAILING in 37 min: http://kci.pangea.pub/job/xenial_unstable_kmail/133/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #81: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/81/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #114: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/114/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #176: FAILURE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kmail/176/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #74: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kdb/74/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #73: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/73/
[00:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #52: STILL UNSTABLE in 48 min: http://kci.pangea.pub/job/xenial_unstable_k3b/52/
[00:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #83: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/xenial_unstable_akregator/83/
[00:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #180: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/180/
[00:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #59: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/59/
[00:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #48: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/zesty_unstable_k3b/48/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #204: FAILURE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/204/
[01:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #123: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/123/
[01:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-dev-utils build #98: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/zesty_unstable_kde-dev-utils/98/
[01:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-dev-utils build #160: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kde-dev-utils/160/
[01:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #197: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/197/
[01:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #136: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_minuet/136/
[01:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #209: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/209/
[01:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #106: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/106/
[01:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #271: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/271/
[01:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #134: FAILURE in 36 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/134/
[01:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #126: UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_ark/126/
[01:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #138: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kstars/138/
[01:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #366: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_plasma-pa/366/
[01:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #305: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/305/
[01:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadiconsole build #88: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_akonadiconsole/88/
[01:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #125: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_minuet/125/
[01:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-dev-utils build #147: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kde-dev-utils/147/
[01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #118: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/118/
[01:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalgebra build #271: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kalgebra/271/
[01:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #228: FAILURE in 28 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/228/
[01:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalgebra build #173: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kalgebra/173/
[01:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #420: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/420/
[01:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #268: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/268/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #327: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/327/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #199: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/199/
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #441: UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_ark/441/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-text-ui build #158: FAILURE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-text-ui/158/
[02:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-import-wizard build #93: UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-import-wizard/93/
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #91: STILL UNSTABLE in 1 hr 36 min: http://kci.pangea.pub/job/yakkety_unstable_krita/91/
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #205: STILL FAILING in 27 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/205/
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #74: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/74/
[02:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #77: STILL FAILING in 38 min: http://kci.pangea.pub/job/zesty_unstable_kdb/77/
[02:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-php build #113: FAILURE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kdev-php/113/
[02:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #190: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/190/
[02:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ark build #342: UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_ark/342/
[02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #404: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/xenial_unstable_kstars/404/
[02:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-text-ui build #159: STILL FAILING in 6 min 39 sec: http://kci.pangea.pub/job/yakkety_unstable_ktp-text-ui/159/
[02:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-php build #114: STILL FAILING in 4 min 38 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-php/114/
[02:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #177: STILL FAILING in 49 min: http://kci.pangea.pub/job/zesty_unstable_kmail/177/
[02:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #135: STILL FAILING in 36 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/135/
[02:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #134: STILL FAILING in 49 min: http://kci.pangea.pub/job/xenial_unstable_kmail/134/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #148: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/148/
[02:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #61: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/zesty_unstable_trojita/61/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #69: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_trojita/69/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #91: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/91/
[02:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #48: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/48/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #61: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_kexi/61/
[02:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #84: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/84/
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #233: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/233/
[02:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #229: STILL FAILING in 31 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/229/
[02:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #59: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kexi/59/
[02:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #225: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/225/
[02:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailimporter build #40: STILL FAILING in 19 min: http://kci.pangea.pub/job/zesty_unstable_mailimporter/40/
[02:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #127: FAILURE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/127/
[02:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #117: STILL UNSTABLE in 2 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_krita/117/
[02:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #202: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/202/
[02:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #90: STILL UNSTABLE in 1 hr 33 min: http://kci.pangea.pub/job/xenial_unstable_krita/90/
[02:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #140: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/140/
[02:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailimporter build #41: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_mailimporter/41/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-import-wizard build #57: UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-import-wizard/57/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #101: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/101/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akregator build #105: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_akregator/105/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #83: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/83/
[03:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #174: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/174/
[03:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #128: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/128/
[03:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #132: FIXED in 37 min: http://kci.pangea.pub/job/zesty_unstable_kwin/132/
[03:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #125: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kmail/125/
[03:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #89: UNSTABLE in 1 hr 56 min: http://kci.pangea.pub/job/zesty_unstable_calligra/89/
[03:20] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #139: FIXED in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/139/
[03:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #103: STILL UNSTABLE in 2 hr 7 min: http://kci.pangea.pub/job/xenial_unstable_calligra/103/
[03:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #103: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/103/
[03:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #139: FAILURE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/139/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #102: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/102/
[03:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #126: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kmail/126/
[03:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #140: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/140/
[03:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #129: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_marble/129/
[04:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #118: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kitemviews/118/
[04:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kauth build #61: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kauth/61/
[04:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #89: STILL UNSTABLE in 1 hr 18 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/89/
[04:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #128: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/128/
[04:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #207: UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/207/
[04:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #125: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/125/
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kjobwidgets build #388: UNSTABLE in 6 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_kjobwidgets/388/
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #394: STILL UNSTABLE in 6 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/394/
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #388: STILL UNSTABLE in 6 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kitemviews/388/
[04:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #119: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/119/
[04:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #82: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/82/
[04:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #337: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kauth/337/
[04:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #397: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/397/
[04:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #431: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/431/
[04:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #421: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/421/
[04:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #393: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/393/
[04:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #214: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/214/
[04:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #99: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/99/
[04:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #86: FAILURE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kconfig/86/
[04:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #272: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/272/
[04:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #389: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/389/
[04:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #416: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/416/
[05:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #87: STILL FAILING in 9 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kconfig/87/
[05:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #273: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/273/
[05:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #392: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/392/
[05:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #210: STILL UNSTABLE in 6 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/210/
[05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #267: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/267/
[05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #225: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/225/
[05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #192: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/192/
[05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #282: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/282/
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #285: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/285/
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #281: STILL UNSTABLE in 8 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_ki18n/281/
[05:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #393: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/393/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #220: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/220/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #286: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/286/
[05:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #249: STILL UNSTABLE in 7 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/249/
[06:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #121: FAILURE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/121/
[06:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #122: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/122/
[09:29] <acheronuk> yofel: akonadi in zesty still does not start. the 16.04.3 version
[09:29] <acheronuk> stile the /var/lib/mysql-files/
[09:29] <acheronuk> *still
[09:30] <yofel> well, the fixed package was never uploaded. 4:16.04.3-0ubuntu3~2 still has all patches commented out
[09:30] <acheronuk> ????
[09:31] <acheronuk> yofel: ok. if that is the case, I will build in a ppa later today and test with those enabled
[09:31] <yofel> thanks
[09:31] <acheronuk> just in case we don't new PIM into zesty
[09:32] <yofel> right, thanks for checking
[09:32] <acheronuk> yofel: I guess an even more brute force method would be....
[09:33] <acheronuk> adding akonadi-backend-mysql.dirs with 'var/lib/mysql-files/' in it
[09:33] <acheronuk> to create that dir anyway, no matter what
[09:34] <yofel> maaaybe... but 'mysql-server' already creates that for internal purposes, and I would rather not mess with that. That's why I went with disabling the check
[09:34] <yofel> I'm not sure if the server package chowns the dir no matter what
[09:35] <acheronuk> yeah. not ideal
[09:35] <acheronuk> yofel: I just noticed this the other day.... https://packaging.neon.kde.org/neon/settings.git/tree/debian/neon-settings.dirs?h=Neon/release
[09:36] <acheronuk> seems to work for them
[09:36] <acheronuk> but yes, a proper fix would be better. if it can be made to work
[09:37] <yofel> hm, does work then I guess. You can try to ditch the patch and go with the dir then see if the server works right in a chroot
[09:38] <yofel> a packaging rule would be better than a patch
[09:38] <yofel> (you'll still need the other patches though)
[09:38] <acheronuk> yofel; ok. I will likely try playing with both way tonight. see which option or combination looks best
[09:40] <acheronuk> daily iso looks good today I think. :) (apart from that issue)
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1367: SUCCESS in 59 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1367/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1367: SUCCESS in 1 min 8 sec: http://kci.pangea.pub/job/mgmt_docker/label=linode-01/1367/
[09:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1367: SUCCESS in 3 min 41 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-01/1367/
[09:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1367: SUCCESS in 4 min 10 sec: http://kci.pangea.pub/job/mgmt_docker/label=swy-02/1367/
[11:16] <BluesKaj> Howdy folks
[11:32] <clivejo> someone working on KCI?
[11:32] <yofel> me
[11:33] <yofel> seems like I broke the reverse proxy by enabling SSL
[11:33] <clivejo> the paths have gone all screwy :/
[11:36] <clivejo> is that LetsEncrpt cert on a cron job to renew in June?
[11:37] <yofel> yes
[11:38] <clivejo> have you got the iso publishing now?
[11:38] <yofel> yes
[11:38] <clivejo> whats the URL?
[11:38] <yofel> https://kci.pangea.pub/images/
[11:39] <clivejo> :)
[11:43] <yofel> ok, added the protocol forwarding. This should work now
[11:47] <clivejo> still missing a /
[11:47] <clivejo> https://kci.pangea.pubjob/mgmt_docker/label=swy-02/1367/
[11:47] <yofel> brrr
[11:48] <clivejo> seems to be only redirects from http to https though
[11:48] <yofel> oh
[11:48] <yofel> then I know what's wrong
[11:49] <yofel> should work now, your browser probably cached the 301 though :/
[11:49] <clivejo> yup, working :)
[11:49] <yofel> I forgot the slash at the end of the redirect
[11:50] <yofel> thanks for testing that
[11:51] <clivejo> thanks for doing it and getting the iso builds working again!
[11:51] -kubuntu-ci:#kubuntu-devel- Starting build #15 for job iso_xenial_unstable_amd64 (previous build: FAILURE -- last SUCCESS #13 3 mo 0 days ago)
[11:52] <clivejo> could that iso filenames be made a bit more verbose?
[11:52] <yofel> sure, I just threw the date out
[11:53] <clivejo> no biggie
[11:53] <yofel> how do you want them named?
[11:54] <clivejo> dunno, just with bit more info, distro, unstable, date and time maybe?
[11:54] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #15: STILL FAILING in 2 min 56 sec: https://kci.pangea.pub/job/iso_xenial_unstable_amd64/15/
[11:55] <yofel> date and time - no. That would e.g. make it impossible to have a fixed URL to the current zsync file
[11:55] <clivejo> can the job name be captured?
[11:55] <clivejo> iso_xenial_unstable_amd64 ?
[11:55] <yofel> sure, the folder is named like that already
[11:55] <yofel> you want that as the filename as well? ^^
[11:56] <clivejo> just thinking of downloading them
[11:56] <yofel> hm...
[11:56] <clivejo> kubuntu-ci.iso's
[11:57] <clivejo> and not know what they are!
[11:57] <yofel> I can understand wanting the date in the filename, but that kind of defeats the idea of both rsync and zsync
[11:57] <yofel> kubuntu-ci-unstable-amd64.iso I don't mind
[11:57] <yofel> heck, add xenial
[11:57] <yofel> that's in the foldername anyway
[11:57] <clivejo> well the date can be got from the file I guess
[11:58] <yofel> either that or you just sync a specific folder instead of current/
[11:58] <clivejo> its more the distro and branch Id like
[11:58] <clivejo> as the long term plan would be to get stable up and running again
[11:59] <yofel> kubuntu-ci-${TYPE}-${DIST}-{$ARCH} ?
[12:00] <clivejo> sure
[12:00] <yofel> done
[12:01] <clivejo> how often is the zesty iso job running?
[12:01] <yofel> so far, never
[12:01] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #73: STILL FAILING in 34 sec: https://kci.pangea.pub/job/mgmt_tooling/73/
[12:01] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Give the images a more descriptive name
[12:01] -kubuntu-ci:#kubuntu-devel- Failed tests:
[12:01] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/73/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[12:01] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: https://kci.pangea.pub/job/mgmt_tooling/73/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[12:01] <clivejo> just when poked
[12:01] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: https://kci.pangea.pub/job/mgmt_tooling/73/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[12:01] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: https://kci.pangea.pub/job/mgmt_tooling/73/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[12:01] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: https://kci.pangea.pub/job/mgmt_tooling/73/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[12:01] -kubuntu-ci:#kubuntu-devel- (2 more)
[12:02] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #13: SUCCESS in 30 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/13/
[12:02] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #13: SUCCESS in 34 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/13/
[12:03] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #13: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/13/
[12:03] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #13: SUCCESS in 1 min 8 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/13/
[12:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1368: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1368/
[12:04] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1368: SUCCESS in 1 min 2 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1368/
[12:04] <clivejo> light rain my backside Mycroft
[12:05] <yofel> now who broke apt in xenial
[12:05]  * clivejo looks around nervously
[12:06] <yofel> nah, not us
[12:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1368: SUCCESS in 3 min 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1368/
[12:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1368: SUCCESS in 4 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1368/
[12:12] <clivejo> ahoneybun valorie: do you know this Aditya Mehra person?
[12:14] <yofel> *sigh*
[12:14] <yofel> as usual, debugging live-build is just impossible
[12:14] <yofel> break over, bbl
[12:14] <clivejo> don't work too hard :)
[12:14] <yofel> work doesn't work like that XD
[12:14] -kubuntu-ci:#kubuntu-devel- Starting build #40 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[12:15]  * clivejo is enjoying a wet and wind Saint Patrick's day
[12:15] <yofel> enjoy :D
[12:35] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #40: SUCCESS in 20 min: https://kci.pangea.pub/job/iso_zesty_unstable_amd64/40/
[12:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mycroft build #8: FAILURE in 6 min 30 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-mycroft/8/
[13:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mycroft build #9: FIXED in 23 min: https://kci.pangea.pub/job/xenial_unstable_plasma-mycroft/9/
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1369: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1369/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1369: SUCCESS in 1 min 16 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1369/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1369: SUCCESS in 3 min 40 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1369/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1369: SUCCESS in 3 min 58 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1369/
[15:58] <yofel> ah ahah ahahhahaha
[15:59] <yofel> ok, I think I know what broke the xenial image, fun issue :D
[16:12] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #74: STILL FAILING in 46 sec: https://kci.pangea.pub/job/mgmt_tooling/74/
[16:12] -kubuntu-ci:#kubuntu-devel- Philip Muškovac: Improve the task removal so it doesn't leave stuff behind by accident
[16:12] -kubuntu-ci:#kubuntu-devel- Failed tests:
[16:12] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run: https://kci.pangea.pub/job/mgmt_tooling/74/testReport/junit/junit/(root)/CI__ContainmentTest/test_run
[16:12] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_env: https://kci.pangea.pub/job/mgmt_tooling/74/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_env
[16:12] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_run_fail: https://kci.pangea.pub/job/mgmt_tooling/74/testReport/junit/junit/(root)/CI__ContainmentTest/test_run_fail
[16:12] -kubuntu-ci:#kubuntu-devel- CI::ContainmentTest.test_ulimit: https://kci.pangea.pub/job/mgmt_tooling/74/testReport/junit/junit/(root)/CI__ContainmentTest/test_ulimit
[16:12] -kubuntu-ci:#kubuntu-devel- DeployUpgradeTest.test_no_argv0: https://kci.pangea.pub/job/mgmt_tooling/74/testReport/junit/junit/(root)/DeployUpgradeTest/test_no_argv0
[16:12] -kubuntu-ci:#kubuntu-devel- (2 more)
[16:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #14: SUCCESS in 28 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/14/
[16:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #14: SUCCESS in 28 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/14/
[16:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #14: SUCCESS in 56 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/14/
[16:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #14: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/14/
[16:15] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1370: SUCCESS in 55 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1370/
[16:15] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1370: SUCCESS in 1 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1370/
[16:16] -kubuntu-ci:#kubuntu-devel- Starting build #16 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #13 3 mo 0 days ago)
[16:17] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1370: SUCCESS in 3 min 41 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1370/
[16:17] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1370: SUCCESS in 3 min 52 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1370/
[16:31] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #16: STILL FAILING in 15 min: https://kci.pangea.pub/job/iso_xenial_unstable_amd64/16/
[16:34] <yofel> ok, leaves apt and that dep 11 issue
[16:39] <acheronuk> they are meant to be backporting a fix to apt for xenial. sometime....
[16:40] <yofel> yeah, I kind of assumed they had done that already... I don't really want to maintain an apt fork in a ppa :/
[16:42] <acheronuk> neon had the same issue in their xenial image builds. not sure what they did in the end as a dirty fix, but the proper fix was trying to get the an apt dev for ubuntu/debian to SRU a fix back to xenial
[16:42] <acheronuk> about a month ago, it was going to take 'about a month'...
[16:43] <yofel> hm
[16:47] <yofel> well, there's a big patch in proposed, maybe that covers it
[16:51] <acheronuk> could also disable the offending /etc/apt/apt.conf.d/60plasma-discover from being installed with the KCI/unstable version of discover, but that then brings the danger of me/us forgetting to re-enable that should we merge unstable for a future plasma release.
[16:52] <acheronuk> and I think would bring back ugly low res icons in discover
[16:56] <yofel> was someone looking at plasma 5.8.6?
[16:56] <acheronuk> I keep meaning to, but gets pushed to one side :/
[16:57] <yofel> np
[16:57] <acheronuk> maybe it's something one of us could do a session with Darrin/wxl etc on BBB and linode and go through backporting it with them
 Would if I could man, would if I could...
[16:59] <acheronuk> tsimonq2: maybe you still could as well. no real barrier except that you would need someone to remote debsign the packages for you. did that with Darrin on apps 16.12.2
[17:00] <yofel> and batch merge the branches, but that's pretty much it
[17:01] <yofel> hm.....
[17:01] <acheronuk> maybe something to do while beta freeze is in place for a couple of days, if not got to before. will have plasma 5.9.4 to get ready as well by then
[17:02]  * yofel just realized that the stable ci jobs will in the future need a release specific target version override for LTS
[17:02] <yofel> yay, even more work
[17:02] <acheronuk> o_O
[17:03] <yofel> well otherwise the stable build jobs for xenial would build plasma 5.9, which would be somewhat useless
[17:03] <acheronuk> um, yes!
[17:04] <acheronuk> ok akonadi seems to start on zesty with those patches refreshed and enabled. no added dir needed.
[17:04] <acheronuk> just not sure if I upload it that it won't fail a million autotests!
[17:05] <yofel> you can somehow run them yourself
[17:05] <yofel> using qemu or something like that
[17:06] <yofel> that would also be kind of useful to have in the CI... simon was looking for something fun to do, right? :D
[17:07] <acheronuk> yep. just going to try. does not look very hopeful: https://autopkgtest.ubuntu.com/packages/akonadi
[17:08]  * acheronuk tries
[17:09] <yofel> bbl
[17:40] <acheronuk> yofel: http://paste.ubuntu.com/24196408/
[17:44] <acheronuk> we don't support the sqlite backend anyway? so I guess those failing tests could be disabled?
 @acheronuk, I can take a look a bit later if it isn't done yet
[18:13] <acheronuk> tsimonq2: take a look at what?
[18:14] <acheronuk> tsimonq2: if you mean plasma 5.8.6, probably the best thing to do would be to discuss in tomorrows BBB meeting if that happens.
 Ok
[19:20] <yofel> acheronuk: hm, it's supposed to work - even if we don't use it by default
[19:21] <yofel> but that looks like the Qt5 Sqlite driver is missing
[19:21] <yofel> otoh, wasn't that built by akonadi itself?
[19:24] <acheronuk> yofel: duh. Mirv did a rebuild as the sqlite backend lib was not being built https://launchpad.net/ubuntu/+source/akonadi/4:16.04.3-0ubuntu3~2
[19:24] <acheronuk> so that is an empty package :/
[21:44] <acheronuk> yofel: looks like changes in Qt 5.7 broke the build on the sqlite driver for akonadi. in 16.04.3 seem they had disabled build in that case, but had not implemented the later fix that's in later akonadi
[21:45] <clivejo> is the fix in 16.12?
[21:46] <acheronuk> clivejo: https://cgit.kde.org/akonadi.git/commit/?h=Applications/16.12&id=068c0bd5f93232eea97e492354eff2b9b62c6643
[21:47]  * clivejo wonders if he could hook/link mycroft and acheronuk
[21:47] <acheronuk> I had that open in a tab :P
[21:48] <acheronuk> clivejo: can you make 3pm on BBB tomorrow?
[21:53] <acheronuk> oh. wait DarinMiller's membership meeting is 15:00 UTC!
[21:53] <acheronuk> :)
[22:00] <clivejo> two birds with the one stone
[22:00] <clivejo> Im hoping to make it yes
[22:05] <clivejo> ahoneybun: boo
 Boo?
[22:06] <clivejo> just getting your attention
 Lol
[22:06] <clivejo> how do I teach mycroft new skills?
[22:07] <acheronuk> clivejo: is there a build of the core somewhere?
[22:08] <clivejo> all in here - https://launchpad.net/~clivejo/+archive/ubuntu/plasma-mycroft
[22:08] <clivejo> mimic > mycroft-core > plasma-mycroft
[22:08] <clivejo> just install plasma-mycroft and it should pull in the rest
[22:09] <clivejo> and only for zesty
[22:12] <clivejo> trying to figure out how to enable the KDE skills
[22:13] <ahoneybun> clivejo: there is a dir for 3rd party skills
[22:13] <ahoneybun> at least when I used it in git
[22:13] <ahoneybun> not sure as a package
[22:15] <acheronuk> clivejo: where did the packaging come from for that?
[22:16] <clivejo> mycroft devs have a ppa on LP
[22:17] <clivejo> so just rebuilt for zesty
[22:18] <clivejo> https://launchpad.net/~mycroft-ai/+archive/ubuntu/mycroft-ai
[22:19] <acheronuk> ah. I was looking on their CI. LP was too obvious!
[22:21] <clivejo> I dont like their packaging though
[22:26] <clivejo> I guess noone in Ubuntu-land is interested in packaging it and putting it in the archive
[22:28] <clivejo> if it was, we could maybe package plasma-mycroft so that it works in plasma out-of-the-box
[22:30] <clivejo> surprised there isnt more interest in it
[22:30] <clivejo> cause the voice detection is very good
[22:30] <clivejo> even with my accent :/
 last I heard they were still using Google's V2T
[22:34] <clivejo> ahoneybun: did you get the plasmoid to work?
[22:34] <clivejo> I like the way it integrates with krunner
 it's only on my laptop atm
 it just says disabled for me
[22:35] <clivejo> did you click the "play" button
[22:35] <clivejo> to make it ready
 I've tried
[22:36] <ahoneybun> clivejo: did you use this: https://mycroft.ai/mycroft-gets-a-plasmoid/ ?
[22:36] <clivejo> no
[22:37] <clivejo> I used the packages to install mycroft-core
[22:37] <clivejo> and packaged plasma-mycroft on KCI
[22:37] <ahoneybun> mm
[22:37] <clivejo> they all in my PPA https://launchpad.net/~clivejo/+archive/ubuntu/plasma-mycroft
[22:37] <clivejo> so I just add that and apt install plasma-mycroft
[22:38] <clivejo> all the basic "core" skills work
[22:38] <clivejo> time, weather, alarms, etc
[22:38] <clivejo> but can't seem to get the KDE skills working
[22:38] <ahoneybun> are there KDE skils?
[22:38] <clivejo> for openning apps, locking, shutdown etc
[22:39] <clivejo> making it work with plasma basically
[22:43]  * clivejo ties a rope around Snowhog to keep him in the channel
[22:45] <Snowhog> clivejo: It's the damned kiwiirc connection (I'm using Safari Browser on my iMac, and connected here via kiwiirc.com); every time I move away from "this tab", I'm 'disconnected'. It's very annoying.
[22:47] <Snowhog> ^^this tab = the kiwiirc.com tab in Safari.
[22:51] <clivejo> mhall119: do you know if there is any plans to package mycroft core in Ubuntu?
[23:19] <Snowhog> I just installed 17.04 in an Oracle VirtualBox VM. The Desktop has, by default, a Trash folder icon. I don't prefer having this on the Desktop; I always have it in the Panel. There doesn't appear to be a way to remove it from the Desktop. Is there?
[23:20] <clivejo> you can switch back to desktop mode
[23:21] <clivejo> open the menu > configure desktop
[23:21] <Snowhog> Doh! That was simple enough!! /me slaps forehead.
[23:21] <clivejo> Layout : Desktop view
[23:22] <Snowhog> I know that there is a rational, but why is Folder View the default? Curious.
[23:33] <clivejo> its been made default in Plasma 5.10
[23:33] <clivejo> we have been having issues with the installer icon on the live CD for a long time
[23:34] <clivejo> and this basically makes things a lot better, so we backported the change to 5.9
[23:35] <clivejo> we felt that new users coming from Windows would be more acustom to this layout
[23:35] <clivejo> and that more established users would know how to switch it back if they don't like it
[23:36] <tsimonq2> clivejo: We could probably backport this to Plasma LTS too
[23:36] <tsimonq2> Because aren't we still going with that one plan?
[23:36] <clivejo> it was announced here - https://blogs.kde.org/2017/03/01/plasma-510-folder-view-default-desktop-mode
[23:36] <tsimonq2> Y'know, Xenial with Plasma LTS and $current-release with Plasma Regular?
[23:37] <clivejo> tsimonq2: I'm not sure on that to be honest
[23:37] <tsimonq2> clivejo: Well what do we have where?
[23:37] <tsimonq2> Oh, duh. Topic...
[23:38] <clivejo> it quite a big feature change for the LTS
[23:38] <clivejo> we might have a lot of users who hate this
[23:38] <tsimonq2> Ok, well then let's not
[23:38] <clivejo> but its coming in 5.10
[23:38] <tsimonq2> wxl: Are you around my friend?
[23:46] <mamarley> Wow, the build farm is slammed: https://launchpad.net/builders  It seems to be functioning properly though.
[23:47] <clivejo> at least KCI wont be adding to that tonight!
[23:47] <clivejo> Snowhog: what are your thought and feelings on that change?
[23:48] <yofel> queues are almost empy though ^^
[23:49] <mamarley> amd64 has 56 jobs in the queue.
[23:51] <yofel> ring the alarm when that has 4 digits :D
[23:51] <Snowhog> clivejo: Personally, I prefer that Desktop be the default. Everything refers to the "Desktop Environment", and whether it is universally accepted, we are targeting the Windows user as a potential convert to Linux. The Desktop is understood to be just that; the Desktop. Not a Folder. I'm a seasoned Linux/Kubuntu user, yet my question about the unrem
[23:51] <Snowhog> ovable Trash Folder after I installed 17.04 should be a clear warning sign to the team; I was expecting the Desktop, not Folder.
[23:52] <yofel> which happens usually during archive test rebuilds
[23:53] <wxl> @tsimonq2: what up?
[23:54] <tsimonq2> wxl: valorie is here, say hai valorie
[23:54] <tsimonq2> wxl: You might want to update her on all the LFNW stuffs and etc.
[23:54] <tsimonq2> Such bestest grammar
[23:54] <wxl> we can move this to #lfnw :)
[23:56] <valorie> hello, I'm going to attack the backlog in this chan now
[23:56] <tsimonq2> valorie: {{{{{{{{{{hugs}}}}}}}}}
[23:56] <valorie> missing quite a bit because I had to shut off this machine during the trip to India
[23:56] <valorie> {{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}
[23:57] <valorie> how are we doing on final beta, folks?
[23:57] <tsimonq2> Nothing yet
[23:57] <tsimonq2> No freeze, no images, nothing yet
[23:58] <yofel> rik was looking at the images earlier


[11:44] <bac> hi gmb
[12:08] <gary_poster> (bac is already here) benji frankban gmb: https://plus.google.com/hangouts/_/cc873feeffaf2d89f51f40706dd22be36570cb3d?authuser=1&hl=en-US in 2
[12:21] <bac> gmb, my last change to z.t was r43 "[r=bac] Cleaned up stdout/stderr data handling."
 I merged trunk, and then everything re-broke.
[12:34] <benji> gary_poster: I submitted the last blog post to hacker news: http://news.ycombinator.com/newest
[12:35] <gary_poster> benji, heh, cool, thanks.  I guess I should follow along there too then.  They seem to like to talk amongst themselves over there
[12:35] <gmb> bac, So, my branch at r43 works.
[12:35] <gmb> My branch with today's trunk merged into it, not so much.
[12:36] <gmb> bac, I need to go and grab some food - or else just eat a colleague - are you okay poking around at it for now?
[12:36] <bac> gmb, sure.  i just wanted to ensure we saw the same thing
[12:36] <benji> well, given that my submissions almost never take off, I wouldn't worry too much about that ;)
[12:36] <gmb> Yep. It broke.
[12:37] <bac> gmb: not completely unsurprising since we worked in parallel making changes to sys.stdout
[13:24] <bac> hey benji, got a second?
[13:24] <benji> bac: I will in about 2 minutes; be right back
[13:24] <bac> ok
[13:26] <gary_poster> benji or bac, I want to start "lpsetup: add workaround for bug 1014916" but I'm not allowed without a partner.  boo hoo.  When either of you are available to pair, lemme know
[13:26] <_mup_> Bug #1014916: simultaneously started lucid containers pause while starting after the first seven <lxc (Ubuntu):Confirmed> < https://launchpad.net/bugs/1014916 >
[13:26] <gary_poster> oh nm
[13:26] <gary_poster> we're full :-)
[13:27] <benji> bac: 'sup?
[13:28] <benji> gary_poster: you could pair with me on "lpsetup init"
[13:28] <bac> benji: wanted to talk about stdout, __stdout__, etc in zope.testing.  it looks like our changes are a bit incompatible
[13:28] <gary_poster> ok cool, benji lemme know when you are ready
[13:28] <benji> gary_poster: will do
[13:28] <benji> bac: do you want to discuss via hangout?
[13:28] <bac> benji: https://plus.google.com/hangouts/_/52afa9329db48899dcaaf86f18e58df34ab497f3?authuser=0&hl=en
[13:32] <benji___> bac: hangouts seem to crash my UI on occasion; will you give me that URL again?
[13:33] <bac> https://plus.google.com/hangouts/_/52afa9329db48899dcaaf86f18e58df34ab497f3?authuser=0&hl=en
[13:46] <bac> benji: you've gone away
[14:18] <benji> bac: you have been booted from the hangout
[14:18] <bac> google hates me this i know
[14:19] <benji> this is the same thing that has happened to me
[14:19] <benji> I think termbeamer needs a new transport
[14:19] <bac> i'll start a new one
[14:19] <bac> jabber.benjiyork.com ?
[14:19] <benji> termbeamer.com :)
[14:19] <benji> I'll make it a pay service and get RICH!
[14:21] <bac> google says "unable to reach chat servers.  check your internet"
[14:21]  * bac gets a beverage
[14:25] <bac> i have pissed off the GOOG
[14:25] <bac> i cannot reconnect
[14:28] <bac> benji: can you start a hangout and invite me?
[14:29] <bac> is this thing on?
[14:30] <benji> bac: trying
[14:32] <benji> bac: https://plus.google.com/hangouts/_/053813e4a0cbd571b5704a06108437be2b6af73f?authuser=0&hl=en-US
[14:33] <bac> first attempt failed
[14:34] <bac> geez, do i need to reboot?  get a new IP address?
[14:34] <bac> benji: skype?
[14:34] <benji> bac: ok
[14:40] <bac> benji: http://paste.ubuntu.com/1051006/
[14:54] <gary_poster> fun.  stub introduced a branch that gives our ec2 parallel test three failures, but it does not fail on buildbot nor can I make them fail locally even with the full worker test list.
[14:55] <gary_poster> I mean, it does not fail on lpbuildbot
[15:06] <benji> bac: lp:~benji/zope.testing/stdio-and-testing-debug-session
[15:08] <benji> gary_poster: I'm going to get a refreshing beverage and then I'll be ready to work on lpsetup init
[15:14] <gary_poster> benji, ok cool.  I think I need to figure out what is going on with those test failures I mentioned above
[15:15] <gary_poster> When I do that I'll ping you
[15:15] <benji> k
[15:16] <gary_poster> gmb, bac, boo hoo (re the fix-all-the-tests branch)
[15:17] <benji> bootstrap seems to be broken ob my machine: http://paste.ubuntu.com/1051061/
[15:17] <gary_poster> please make sure that's handed off, and if the card is still around tomorrow let's escalate its importance (making sure someone is always available for pairing and all that jazz per our checklists)
[15:18] <gary_poster> benji, this is in lpsetup?
[15:19] <gary_poster> gmb, "please make sure that's handed off..." was to you, in case that's not clear
[15:19] <benji> gary_poster: "this" being "lpsetup init command"?  If so, yes. ;)
[15:20] <gary_poster> benji, um.  OK, is that the lpsetup bootstrap, or the Launchpad bootstrap as driven by lpsetup?
[15:21] <gary_poster> ugh, I can't get the tests to fail locally that are failing in parallel tests!  :-(  :-(
[15:21] <benji> oh! the error; yes, that error is from running the bootstrap with my system python
[15:21] <gmb> gary_poster, understood.
[15:21] <gary_poster> thanks
[15:23] <frankban> benji: lpsetup no longer uses buildout for tests, so, no need to bootstrap. that said, bootstrap was broken in my system too and I had to run it inside a virtualenv to work around some setuptools problem
[15:26] <gmb> bac, benji: So, what's the situation with the zope.testing branch (apologies for the delay in asking; I've had a spectacularly interrupty afternoon)
[15:27] <bac> gmb: it looks like the use of doctests within testrunner is horribly confused by the stdout/stderr shenanigans
[15:27] <benji> frankban: We should remove the [test] target from the buildout then.  And add something to README or a new HACKING file to describe how to set up a dev environment and how to run the tests.
[15:27] <benji> in fact, does it need buildout at all now?
[15:28] <bac> gmb: our next approach is to rewrite those doctests as  unittests.  i have regretably rejected your MP as it appears DOA
[15:28] <bac> gmb: though some parts of that branch may prove useful
[15:28] <gmb> Botheration.
[15:28] <gmb> bac, Okay. Is there anything that I can do at this point to help you?
[15:29] <bac> gmb, not that i can think of
[15:29] <gmb> Okay.
[15:29]  * gary_poster performs small cheering routing about pairing.  Everyone is frightened away and looks out the window, embarrassed.
[15:30] <gmb> bac, If, at your eod, you're not done, feel free to send me a summary of your progress so I can pick it up in the morning.
[15:30] <bac> gmb: will do
[15:31] <frankban> benji, no buildout is not needed at all, and the buildout/bootstrap files can be deleted. The README(.rst) file is already there.
[15:32] <benji> frankban: indeed!  (I didn't expect the Spannish... .rst file)
[18:35] <gary_poster> whee
[19:56] <bac> hey benji, this is the start to the conversion: http://pastebin.ubuntu.com/1051482/
[19:56] <bac> i've got most of the required structure.  the last test is one of the troublesome ones from the doctest and it works fine.
[19:56] <bac> lemme know if you see something boneheaded
[19:56] <benji> bac: cool!
[19:57]  * benji looks.
[19:57] <bac> now, just put on some loud Lynryd and plow ahead
[19:57] <bac> or joshua bell
[20:03] <benji> bac: the tests look good; hopefully it will be mostly mechanical
[20:03] <bac> yep
[20:03] <benji> bac: if you need some extra sonic inspiration I suggest http://www.youtube.com/watch?v=pmo1VW_wA_o
[20:03] <bac> i can't type that fast
[20:04] <benji> heh
[20:04]  * benji learns that bac types in rythm to the music.
[20:17] <gary_poster> benji, how goes lpsetup init?
[20:23] <benji> gary_poster: (I was preparing to answer your question.) It goes well, I think.  Because of the lack of test coverage I have taken a conservative tack, but I think I'm about done.
[20:23] <benji> we should discuss testing strategies
[20:29] <gary_poster> great, benji.  frankban had a thought on testing strategy: an object that had a minimal API that the commands could talk to.
[20:29] <gary_poster> then we substitute in a testing version
[20:30] <gary_poster> that approach captures at least some important aspects of testing
[20:30] <gary_poster> we talked about that for the host, and then also for the lxc commands
[20:31] <benji> I've had some luck with an approach like that in termbeamer tests, I did it at the module level (I have a few fake GTK modules that I use in different circumstances)
[20:31] <bac> gary_poster: i was just reminded i need to take an early lunch (11-12) tomorrow, lest i forget to mention it
[20:32] <benji> writing the more unity of unit tests for this won't be too hard (and there are several already), the hard part will be deciding what we really want the higher level tests to demonstrate
[20:35] <gary_poster> bac, ack
[20:35] <gary_poster> agreed benji.  I'm ok with aiming a bit low in that regard, but I'm also ok with be convinced otherwise :-)
[21:35] <bac> hey benji, still around?
[21:54] <bac> how does testrunner-subunit.txt ever pass, given that it has hard-coded expected output with a path to jml's home directory?
[22:12] <gary_poster> bac, it works because the test hookup normalizes the output
[22:12] <gary_poster> look at how that doctest is integrated into the python test suite
[22:13] <gary_poster> look for ReNormalizer or something like that
[22:14] <bac> ah, ok


[13:05] <vimerrrrrrr> hi all~ can anyon tell me why when i do this int[][] array = image.getPixelArray(); it give me this error: cannot find symbol     symbol:   method getPixelArray()
[13:05] <vimerrrrrrr> seems i lost my getPixelArray() method
[13:06] <vimerrrrrrr> i imported acm program and graphics


[11:04] <seiflotfy> hey guys
[11:05] <seiflotfy> any idea why my touchpad only works with 2 fingers and not 1 finger
[20:31] <Spartan29> hallo!
[20:31] <Spartan29>  I've a trouble. I can't share files from linux to windows, files are in a folder of an NTFS partition mounted on boot time. What i see is that i can't change folder and than in it contained files. Can someone help me?


[14:34] <skjones> checking out Lubuntu with the LXQt desktop. having trouble signing in to dropbox. installed dropboc but when i click on "sign in" - nothing. thoughts?
[14:58] <skjones> i think i figured it out - thx
[16:48] <maazid__> exit


[07:54] <kjackal> good morning juju world!
[08:52] <kjackal> Hi everyone, a member/partner from scaledb cannot register with the juju list. Who is the juju list owner?
[10:17] <BlackDex> Hello there, i'm looking for the minimum requirements for a juju "node"/vm but i can't seem to find it
[10:23] <kjackal> BlackDex: What do you mean by minimum requirements?
[10:24] <kjackal> BlackDex: A base charm is the ubuntu charms
[10:24] <kjackal> BlackDex: That deploys ubuntu and it should run wherever ubuntu runs
[10:29] <BlackDex> I meen the juju bootstrap node
[10:29] <BlackDex> So, how much mem, disk, cpu etc.. is the minimum requirement for a juju-bootstrap node
[10:30] <BlackDex> For maas it is located here: http://docs.ubuntu.com/maas/2.1/en/#minimum-requirements
[10:30] <BlackDex> For JuJu i couldn't find it
[11:45] <cjwatson> Is there any equivalent of optional_resources from jujuresources in Juju 2.0 resources?
[11:45] <cjwatson> I'm trying to write a charm that installs packages from resources if they're provided that way, but otherwise installs from a PPA
[11:46] <cjwatson> Simply not attaching the resources and having a bit of conditional behaviour in the charm worked OK until I tried to do "charm release", at which point I got "cannot release charm or bundle: bad request: charm published with incorrect resources: resources are missing from publish request: ..."
[11:52] <cjwatson> I've thought about building metadata.yaml conditionally, but that's fiddly, and it would mean two different versions of the charm, one with resources and one without
[11:53] <cjwatson> Do I just have to fall back to bundling files in the charm instead?  Seems a shame - resources are a nicer UX in general
[12:04] <kjackal> Optional resources....
[12:05] <kjackal> you can have dummy 0-sized recources
[12:05] <cjwatson> True; feels extremely hacky
[12:05] <kjackal> cjwatson: there is an email thread that is somewhat related
[12:05] <cjwatson> Is that something that other charms do?
[12:05] <kjackal> perhapse you could give some feedback
[12:06] <kjackal> yes, there is no other option for now
[12:06] <kjackal> but your feedback/usecase needs to be heard
[12:06] <kjackal> please send some email to the list/or say something about your needs in that email thread
[12:07] <kjackal> cjwatson: title "Hide resources from showing on the store"
[12:07]  * cjwatson finds https://lists.ubuntu.com/archives/juju/2016-December/008265.html
[12:08] <cjwatson> kjackal: do you happen to have the Message-Id of that message?  That way I can synthesise a reply - I'm not subscribed to that list
[12:14] <cjwatson> kjackal: ah, never mind that, I can extract it from the HTML source
[12:29] <kjackal> sorry cjwatson. I am back now
[12:52] <shruthima> Hi all, iam trying to push multiseries charm to charm store. i have successfully ran charm push but charm publish command if giving following error http://paste.ubuntu.com/23583217/, anyone please suggest?
[13:17] <shruthima> Hi all, iam trying to push multiseries charm to charm store. i have successfully ran charm push but charm publish command is giving following error http://paste.ubuntu.com/23583217/, anyone please suggest?
[13:18] <kjackal> hi shruthima I thought the publish was replaced by charm release
[13:19] <kjackal> i get a "ERROR unrecognized command: charm publish"
[13:19] <kjackal> shruthima: is it possible you are running some old version of charm tools?
[13:19] <shruthima> ya in some machines i faced even that error
[13:20] <shruthima> iam using charm-tools 2.1.2
[13:21] <shruthima> kjackal: any document related to charm release?
[13:22] <kjackal> should be the same as charm publish
[13:22] <shruthima> oh k il give a try
[13:23] <shruthima> kjackal: ERROR unrecognized command: charm release
[13:24] <shruthima> in which version of charm-tools will it work?
[13:24] <kjackal> I couldnt find docs on the web for charm release, but here is the --help output: http://pastebin.ubuntu.com/23583338/
[13:25] <kjackal> shruthima: Regarding the "access denied" error you are getting I would start by looking at the permissions you have on launchpad
[13:26] <kjackal> shruthima: are you in the right group(s)?
[13:26] <shruthima> kjackal: ya i have pushed 3-4 charms with same launchpad id
[13:27] <kjackal> so it is only that one you cannot release?
[13:27] <kjackal> you can release other charms in that group?
[13:28] <shruthima> almost everyone is facing this issue from last friday
[13:28] <kjackal> In that case, use charm show <charm-name> to compare the permissions set
[13:28] <kjackal> last friday...
[13:28] <kjackal> strange..
[13:29] <kjackal> let me try to release a charm myslef.
[13:29] <shruthima> kjackal: no other charms also iam unable to publish now
[13:29] <shruthima> ok
[13:33] <kjackal> shruthima: I am sorry I cannot reproduce the error. Releasing charms works here: http://pastebin.ubuntu.com/23583368/
[13:34] <kjackal> shruthima: can you try the publish command with the --debug option
[13:34] <shruthima> kjackal: almost everyone from ibmcharmers facing same error http://paste.ubuntu.com/23583370/
[13:34] <shruthima> ok
[13:35] <marcoceppi> shruthima: you have an old version of the charm command, if you run `charm version` you should get charm with at least 2.2.0
[13:38] <shruthima> marcoceppi: how to update the charm version
[13:38] <marcoceppi> `sudo add-apt-repository ppa:juju/stable; sudo apt update; sudo apt dist-upgrade`
[13:39] <marcoceppi> `sudo add-apt-repository -y ppa:juju/stable; sudo apt update; sudo apt dist-upgrade`
[13:39] <shruthima> kjackal: here is the output with debug option http://paste.ubuntu.com/23583387/
[13:41] <kjackal> shruthima: can you please try the upgrade marcoceppi suggested and then do a charm logout, login, release ?
[13:41] <shruthima> kjackal: ya iam trying to upgrade now
[13:41] <kjackal> shruthima: thanks
[13:52] <shruthima> marcoceppi: kjackal : i have updated the cahrm version http://pastebin.ubuntu.com/23583438/ , still iam facing the same ERROR cannot release charm or bundle: unauthorized: access denied for user "salmavar"
[13:52] <marcoceppi> shruthima: which charm are you trying to release?
[13:52] <shruthima> ibm-im
[13:53] <shruthima> multiseries charm
[13:53] <marcoceppi> shruthima: you can't release to the stable channel for that charm, it's an approved charm.
[13:53] <marcoceppi> https://jujucharms.com/ibm-im/
[13:54] <marcoceppi> instead, sonce you push, enter the URL you get back from push into http://review.jujucharms.com/ and it'll follow a review cycle then be released once reviewed
[13:56] <shruthima> marcoceppi: oh ok so just i have to create a new request for review with new URL right ?
[13:56] <marcoceppi> yes
[13:56] <shruthima> marcoceppi: thanku :)
[13:58] <shruthima> marcoceppi: any updates on this issue https://github.com/juju-solutions/interface-http/issues/5
[14:16] <marcoceppi> shruthima: no, not at the moment
[14:18] <shruthima> marcoceppi: ok when can we expect that to be resolved?
[14:22] <admcleod> is there a way, when adding a machine manually with 2.x, to define what kind of lxc networking you'd like to use by default?
[14:30] <deanman> marcoceppi: Hi, i joined recently the aws charmers program, I was wondering if i do have access to AWS web console as well.
[14:30] <marcoceppi> deanman: you do not
[14:31] <marcoceppi> deanman: is there something you need in the web console?
[14:32] <deanman> marcoceppi: i was controlling a deployment yesterday from home and now from office (and behind proxy) it seems my client cannot talk to AWS. I'm trying to debug whether is due to controller dies or some other network issue.
[14:32] <marcoceppi> deanman: ah, do you know the instance id for your controller?
[14:33] <deanman> marcoceppi: does that help ? http://paste.ubuntu.com/23583601/
[14:34] <marcoceppi> deanman: ah, can you get the controller UUID from `juju show-controller`
[14:36] <deanman> marcoceppi: hmm it seems that i can't http://paste.ubuntu.com/23583609/
[14:37] <marcoceppi> deanman: $HOME/.local/share/juju/controllers.yaml should have that cached
[14:39] <deanman> marcoceppi: http://paste.ubuntu.com/23583631/
[14:39] <deanman> uuid: d1a79bb1-a362-4551-81ec-d51613d31a1f
[14:40] <marcoceppi> deanman: it is alive still
[14:40] <marcoceppi> bootstrapped about 22 hours ago
[14:41] <deanman> marcoceppi: how does local juju client talks to the controller ? ssh or other protocol ? SSH is blocked and needs some tsocks configuration but everything else should go through the proxy server.
[14:43] <marcoceppi> deanman: I'm under the impression that it's directly with a websocket
[14:43] <deanman> ah websockets
[14:44] <deanman> ok thanks, ill try troubleshoot it
[15:41] <bildz> goood morning
[15:41] <bildz> are there any docs at running a juju controller in HA?
[15:41] <bildz> im designing an HA MAAS solution and haven't been able to find any docs yet
[15:41] <marcoceppi> bildz: let me take a look
[15:42] <bildz> marcoceppi: thanks!
[15:45] <marcoceppi> bildz: in short, `juju enable-ha` is the command you want (juju help enable-ha for more info). I've filed a bug on the docs to document this better https://github.com/juju/docs/issues/1556
[15:47] <Ankammarao> Hi Kevin
[15:48] <Ankammarao> Hi i have firefox browser issue on ubuntu z machine ,can anyone help me
[15:49] <marcoceppi> Ankammarao: you mean, a problem with Firefox on Z or problem with Juju GUI on Firefox (on Z)?
[15:50] <Ankammarao> when running firefox command on vnc server ,getting the error like "Error: GDK_BACKEND does not match available displays"
[15:50] <Ankammarao> marcoceppi ,i want to open firefox browser on vnc session for ubuntu z machine
[15:51] <marcoceppi> Ankammarao: this sounds like a general Ubuntu question. http://askubuntu.com or #ubuntu on irc
[15:51] <marcoceppi> Ankammarao: those are probably the best source for help
[15:51] <marcoceppi> Ankammarao: I'd help, but I've not encountered that problem :(
[15:55] <Ankammarao> marcoceppi, can we install other browsers like "firefox" on ubuntu z machine
[15:55] <marcoceppi> Ankammarao: probably, sure. It's the same ubuntu as you'd expect on any other architecture. So long as there's a package for that architecture
[15:58] <marcoceppi> bildz: https://jujucharms.com/docs/2.0/controllers-ha
[16:08] <marcoceppi> petevg: hey, are you in DC?
[16:12] <petevg> marcoceppi that I am.
[16:12] <petevg> Just for the day.
[16:32] <magicaltrout> petevg: you visiting the whitehouse before it turns gold?
[16:32] <magicaltrout> personally, I think it'll look nice gold...
[16:35] <petevg> magicaltrout: heh. I thought about doing that.
[16:35] <petevg> I have just enough time to wander through the National Mall, though. Then I have to hit the conference.
[16:35] <magicaltrout> i was down there the other day.... huge blisters
[16:35] <magicaltrout> I never learn
[16:36] <petevg> Outside > inside. I'll have to see the Whitehouse after Trump's successor restore it :-)
[16:36] <magicaltrout> I reckon he'll turn it into a downtown golf course
[16:36] <magicaltrout> he'd make a lot of money.....
[16:36] <petevg> Ew.
[16:36] <magicaltrout> think about it
[16:36] <magicaltrout> teeing off from the roof, with the hole being the washington monument
[16:36] <magicaltrout> it doesn't get any better than that
[16:37] <petevg> Sigh.
[16:37] <magicaltrout> you could zipwire from the roof
[16:37] <petevg> The problem is that I can see it.
[16:37] <magicaltrout> then, tee #2 could be the lincoln memorial
[16:37] <magicaltrout> it would be the best golf course ever
[16:38] <magicaltrout> i need to figure out how to incorporate capitol hill
[16:41] <magicaltrout> I also happen to think the roof of the kennedy centre would make a great green
[16:41] <magicaltrout> plenty of room, but testing enough  because if you go off the edge, you're gonna have a tricky chip to get back onto the green from 4 stories below
[16:41] <magicaltrout> maybe a short par 3 from the Watergate hotel
[17:09] <bdx> marcoceppi: can you link me to anything you have done for datadog-agent?
[17:18] <cory_fu> marcoceppi: https://github.com/marcoceppi/svg.juju.solutions/pull/8
[17:48] <marcoceppi> bdx: give me 10 mins to clean up this iteration
[17:48] <marcoceppi> bdx: and we can chat
[17:48] <bdx> marcoceppi: ok
[17:49] <marcoceppi> cory_fu: thanks for the contribution!
[17:49] <marcoceppi> cory_fu: I wnat to merge post/get, since it's a lot of duplication
[17:49] <marcoceppi> maybe one day
[17:52] <bdx> rick_h: you were talking about how you specified the default aws region in clouds.yaml, how exactly are you specifing that?
[17:53] <marcoceppi> bdx: don't listen to rick, use juju set-default-region ;)
[17:53] <marcoceppi> cory_fu: I've got a crazy idea, need sanity check
[17:54] <marcoceppi> cory_fu: got a min?
[17:54] <cory_fu> marcoceppi: Sure
[17:54] <bdx> marcoceppi: thx
[17:55] <marcoceppi> cory_fu: https://appear.in/lets-talk-about-interfaces-charms-and-reactive
[17:59] <rick_h> bdx: yea right , that Rick guy is nuts. Don't listen to him.
[18:09] <lucacome> hey guys, I'm from NGINX and working on the official charm, does someone have time to take a look at it and see if I'm going in the right direction?
[18:15] <marcoceppi> lucacome: yeah, totally
[18:19] <lucacome> marcoceppi, I've started form layer-nginx and continued from that https://github.com/lucacome/juju-layer-nginx
[18:21] <marcoceppi> lucacome: taking a look now!
[18:21] <lucacome> thank you
[18:21] <bdx> lucacome: cert/key might be better specified as config options
[18:23] <lucacome> bdx, can I pass files wit config options?
[18:26] <bdx> lucacome: I don't think so, you can pass the cert/key as strings <- this might not be the prefered way either tho
[18:26] <bdx> luacome: https://github.com/jamesbeedy/charm-datadog-agent/blob/master/config.yaml#L22
[18:28] <bdx> lucacome: others have made charms and layers to help facilitate SSL/TLS, see https://jujucharms.com/u/containers/easyrsa/3, and https://github.com/cmars/layer-lets-encrypt
[18:29] <bdx> lucacome: ^ only cover self signed, and LE certs/keys though ... so to acommodate user specified sighned cert/key, I would thing config options would do it, but I'll let the pros chime in here
[18:30] <bdx> signed*
[18:30] <bdx> think*
[18:31] <lucacome> bdx, they are not self signed cert/keys, they are handed out by us to install the NGINX Plus, our commercial version
[18:32] <bdx> lucacome, I see that now
[18:32] <lucacome> but I'll take a look in to it to see how others are doing dealing with certs
[18:33] <marcoceppi> cory_fu: I've backed myself into a corner
[18:33] <bdx> lucacome: I would lean towards config options for that .... @marcoceppi should be able to confirm whether that is the best route or not
[18:34] <marcoceppi> lucacome bdx I don't think resources is a bad way, but if you had a "nginx-cert" resource that was a tar.gz of a .key and .crt file it'd be easier for users
[18:34] <marcoceppi> I'd go either way, config or resources - both are valid
[18:35] <bdx> marcoecppi: in his charm the resouce is optional though
[18:35] <marcoceppi> I do have a few other concerns, still working through it
[18:35] <marcoceppi> bdx: yeah, and that's fine, as long as there's a 0 byte blank resource
[18:35] <bdx> ahhh
[18:35] <marcoceppi> neither config or resources is ideal for this
[18:35] <marcoceppi> cory_fu: can I do something like this?
[18:36] <marcoceppi> bdx: haven't forgotten about you, but I have some code I think you'll like
[18:36] <marcoceppi> bdx: for datadog
[18:36] <lucacome> marcoceppi, is there a better way to upload files?
[18:36] <bdx> nicccee
[18:37] <marcoceppi> lucacome: configuration, resources, and scp are the three methods. With the last one not being recommended at all given the UX around it
[18:37] <marcoceppi> resources is preferable, because it doesn't expose the key and crt files in plain text anywhere
[18:37] <marcoceppi> unless you want the configuration options for nginxplus to be exposed
[18:38] <marcoceppi> in exports
[18:38]  * bdx eats his words
[18:38] <marcoceppi> well, configuration isn't bad bdx, there are cases you'd wnat the crt to be in a bundle export
[18:39] <marcoceppi> but I'm not sure that's the case here
[18:39] <marcoceppi> but I also can't tell, those are the two paths ultimately
[18:40] <marcoceppi> cory_fu: http://paste.ubuntu.com/23584586/ line 13, can I use getattr on the class for autoaccessors?
[18:40] <marcoceppi> cory_fu: or is there an easier way?
[18:48] <cory_fu> marcoceppi: I think that's the best way, though "rel_data.k()" won't work
[18:48] <marcoceppi> cory_fu: right, so will getattr work?
[18:49] <marcoceppi> or is there a better way?
[18:49] <cory_fu> marcoceppi: Actually, what about standardizing the interfaces so that they share a common method name.  Something like, "get_configuration()"?
[18:50] <marcoceppi> cory_fu: not a bad idea
[18:50] <marcoceppi> cory_fu: I want to ultimately standardize these stats interfaces
[20:01] <bdx> is there a debug method of sorts that will list all flags/states that are set for a charm?
[20:30] <skay_> how do I get tests to run against a live deployment? I can't only use containers because I'm using a snap and snaps have a problem installing in containers at the moment
[20:31] <skay_> so my one test at the moment makes a deployment and checks that my charm is a blocking state while it waits for a snap resource
[20:31] <skay_> I can verify that
[20:37] <marcoceppi> bdx: `charms.reactive get_states` I think
[20:37] <marcoceppi> bdx: I am finally ready to talk about datadog
[21:08] <bdx> marcoceppi: all ears
[21:08] <marcoceppi> bdx: so, this is what I came up with
[21:09] <marcoceppi> https://github.com/silph-io/layer-datadog/blob/master/reactive/datadog.py#L52
[21:09] <marcoceppi> I'm testing it now, but basically it means you only need to touch metadata.yaml and layer.yaml to add new integrations
[21:10] <marcoceppi> that was the biggest concern when talking to ilan at data dog, about overhead of maintenance and boilerplating
[21:11] <marcoceppi> bdx: I'd like to collaborate going forward, and get this repo into upstream
[21:11] <bdx> marcoceppi: I'm trying to get something official going for it before I start putting it out everywhere for sure
[21:11] <marcoceppi> bdx: yeah, we've been in touch with datadog about this, we have an internal business relationshiop being developed
[21:12] <bdx> marcoceppi: so why list integrations in metadata?
[21:14] <marcoceppi> bdx: well, interfaces should drive the entire configuration for everyhting. So if the nginx and php-fpm (and kubernetes, mysql, etc) charms and layers include a unique stat inferface, which supplies the keys required by datadog, or any other stat generations/configuration tool, you get a fully automated experience
[21:14] <marcoceppi> we can jump on a quick call to explain more if you'd like
[21:14] <bdx> marcoceppi: ok
[21:15] <marcoceppi> bdx: https://appear.in/datadog
[21:57] <marcoceppi> bdx: I found a few foul ups, updating the repo in a min with some patches
[21:57] <marcoceppi> lots of missing imports
[22:19] <xplatform12> I have the latest juju and MAAS. When trying to "conjure-up openstack" and running the OpenStack option, I use the "Connect to an existing MAAS" option. For maas server, I am entering "http://x.x.x.x/MAAS/api/2.0/" and entering my maas-auth key in that field. When I Confirm the options, it shows that it is trying to bootstrap the environment and then almost immediately failes with "error: flag provided by not define: --upload-tool
[22:19] <xplatform12> s" does anyone know what is causing this issue?
[22:24] <marcoceppi> xplatform12: to start, you should need to enter "http://x.x.x.x/MAAS/"
[22:25] <marcoceppi> xplatform12: what version of juju do you have installed?
[22:25] <marcoceppi> xplatform12: `juju version`
[22:25] <marcoceppi> cory_fu: I hit a snag
[22:26] <cory_fu> marcoceppi: ?
[22:27] <marcoceppi> cory_fu: `RelationBase.from_state('php-fpm')` returns None despite these states: {'apt.installed.apt-transport-https': None, 'datadog.configured': None, 'apt.installed.datadog-agent': None, 'php-fpm.available': {'conversations': ['reactive.conversations.php-fpm:3.silph-web/0'], 'relation': 'php-fpm'}}
[22:28] <cory_fu> marcoceppi: The states have to match exactly.  You'll want RelationBase.from_state('%s.available' % relation_name)
[22:28] <marcoceppi> cory_fu: oh, boss, even easier
[22:28] <marcoceppi> this removes my entire `relation_name.available` state check
[22:30] <marcoceppi> bleh
[22:30] <cory_fu> ?
[22:31] <marcoceppi> cory_fu: http://paste.ubuntu.com/23585512/
[22:31] <marcoceppi> these are set to scope.UNIT
[22:31] <xplatform12> marcoceppi: I tried with just http://x.x.x.x/MAAS/ and my key and got the same error. I am using juju Version: 1:2.0.1-0ubuntu1~16.04.4~juju1
[22:31] <marcoceppi> xplatform12: huh, yeah, conjure-up should work just fine. stokachu ^ ?
[22:32] <cory_fu> marcoceppi: Yeah, if it's set to scope UNIT, that means there will be a separate conversation per remote unit, so you have to iterate over self.conversations() instead of assuming a single self.conversation()
[22:33] <marcoceppi> cory_fu: yeah, it's a subordinate relation, so, single conversation makes sense
[22:33] <xplatform12> I also checked in /var/log/openstack.log and it has the following: "Dec  5 22:28:27 juju openstack: [ERROR] ['error: flag provided but not defined: --upload-tools']" I can't seem to find any info about htis issue online.
[22:33] <cory_fu> marcoceppi: So if it's always going to be subordinate, you can just change it to GLOBAL scope
[22:33] <marcoceppi> xplatform12: --upload-tools was a flag for juju 1.x conjure up thinks that's your version, for whatever reason
[22:33] <marcoceppi> cory_fu: ack, just did
[22:34] <marcoceppi> time to re-deploy
[22:36] <xplatform12> marcoceppi: This was upgraded from juju 1.x. Let me rebuild the juju system and go right to 2.0 without an upgrade. I hope that helps and thanks.
[22:47] <xplatform12> marcoceppi: I rebuild and made sure I had the correct repositories when installing juju and now conjure-up is past that issue and bootstrapping. Thanks for your assistance.
[22:48] <marcoceppi> xplatform12: no worries! sorry you got caught up in that transition
[22:48] <marcoceppi> bdx: alright, finally got configuration files writing
[22:48] <bdx> marcoceppi: niceee
[22:49] <marcoceppi> bdx: my latest work was just pushed to the repo
[22:49] <bdx> marcoceppi: looking
[22:51] <marcoceppi> bdx: bunch of awful little papercuts


[00:01] <OvenWerks> Ok, just looking now. ...
[00:01] <OvenWerks> more problems than jackd not starting
[00:01] <OvenWerks> which desktop?
[00:01] <OvenWerks>  is pulse installed?
[00:02] <OvenWerks> The calls using pactl are failing
[00:02] <OvenWerks> " Connection refused"
[00:03] <OvenWerks> what does .log/jack/jackdbus.log look like? I expect it says no access to the device
[00:04] <OvenWerks> if pactl can't connect to pulse via dbus, it is a good guess jack can't either
[00:05] <OvenWerks> Eickmeyer: ^^^
[00:06] <OvenWerks> that may be a logind/systemd difference in dbus instance
[00:07] <Eickmeyer> I believe it was Gnome, but I'll check with Plasma as well.
[00:07] <Eickmeyer> And, yes, Pulse is definitely installed.
[00:10] <OvenWerks> if the gnome desktop on fedora is the same as on ubuntu, logout and in will not work. a reboot each time probably.
[00:12] <OvenWerks> gnome never realy shuts down their logind session properly... or maybe opens a second one on top of the first. either way pulse ends up on another instance of dbus. also make sure that pulse is set up as a user process not system
[00:12]  * OvenWerks goes to spend time with wife
[00:20] <Eickmeyer> OK, maybe that's it. Will keep investigating.
[00:21] <Eickmeyer> Just a lot on my plate at the moment.
[00:44] <Eickmeyer> OvenWerks: It has the same problem in Plasma. It seems as though it's shutting-down Pulse, but then Pulse isn't coming back for whatever reason.
[00:46] <Eickmeyer> Bingo: W: [pulseaudio] module-jack-sink.c: JACK error >Cannot use real-time scheduling (RR/15) (1: Operation not permitted)<
[01:14] <OvenWerks> Eickmeyer: thats pretty much normal and should not stop things from working
[01:21] <OvenWerks> Eickmeyer: do you have autospawn = yes in client.conf in /etc/pulse/?
[01:22] <OvenWerks> because pulseaudio -k kills pulse and expects it to respawn
[01:22] <OvenWerks> cadence turns that off)
[01:31] <OvenWerks> Eickmeyer: something to try:
[01:31] <OvenWerks> killall autojack
[01:31] <OvenWerks> ps ax |grep autojack should show no autojack running
[01:32] <OvenWerks> then use -controls to start jack again.
[01:33] <OvenWerks> this should start another instance of autojack. If this works... we may have to go back to  /etc/xdg/autostart/autojack.desktop
[01:34] <OvenWerks> anyway, it seems dbus related
[02:01] <Eickmeyer> OvenWerks: Interesting... autospawn=no is set in Fedora by default. :S
[02:01] <Eickmeyer> Never had this issue before.
[02:42] <Eickmeyer> OvenWerks: That method did not work. I'm guessing we've got some new dbus stuff that's messing up our flow. Unfortunately, if it's in Fedora now, then that means it'll land in Ubuntu in the future.
[15:10] <OvenWerks> Eickmeyer: it seems carla is to blame for things freezing up... but I am not sure why. I think there is also a problem with jack itself because once carla messes things up, restarting jack does not clear the problem.
[15:11] <OvenWerks> so if carla freezes, nothing that reads or changes the graph works (qjackctl, jack_lsp, -controls, etc)
[15:11] <OvenWerks> even after restarting jack.
[15:13] <OvenWerks> so there is something left in memory... This looks like a problem with either jack itself or libjack.
[15:16] <OvenWerks> that is aside from the problem with carla :) I actually think if the problem in jack/libjack was taken care of, the problem with carla would at least be less of a problem.
[15:17] <OvenWerks> Eickmeyer: with regard to the different way pulse may be set up from one system to the next, I feel that is a small problem.
[15:18] <OvenWerks> it means we go from: kill pulse and expect it to reset itself
[15:19] <OvenWerks> to: kill pulse, check if it is running, start it if not.
[15:21] <Eickmeyer> OvenWerks: Yeah, it's more complicated than that, unfortunately.
[15:23] <OvenWerks> have they also gone from user based to system based?
[15:23] <Eickmeyer> I'm not following.
[15:24] <OvenWerks> pulse can be run as a system service so that if there is more than one user logged in at the same time they all have access to the audio device.
[15:24] <OvenWerks> it does limit pulse's operation which is why it is normally not done.
[15:25] <OvenWerks> it may also be that the respawn setting is done by systemd rather than pulse itself.
[15:25] <Eickmeyer> Hmmm... not sure. Seems to be a user service, but I'm not 100% sure.
[15:26] <OvenWerks> you should find it either in /lib/systemd/  system or user
[15:27] <OvenWerks> ls /lib/systemd/user/pulse*
[15:30] <Eickmeyer> I'm rebooting into Fedora to find out. That seems to have had to be a systemwide change proposal, and I saw nothing.
[15:32] <Eickmeyer> Fedora doesn't make changes like that without making it a big deal.
[15:55] <OvenWerks> so far carla 2.1 has shown no problems....
[15:55]  * OvenWerks notes that carla 2.2 uses juce and maybe uses juce libs to talk to jack
[15:56] <OvenWerks> certainly juce is the big difference from 2.1 to 2.2
[15:56] <Eickmeyer> Hmmmm.....
[15:57] <Eickmeyer> Perhaps I should package Cadence if only for catia, i.e. not making the cadence binary available.
[15:58] <OvenWerks> I like that 2.2 handles jack restarts but I can't recommend carla as a replacement for patchage/qjackctl if we ship 2.2
[15:58] <OvenWerks> catia _should_ be out on it's own "soon".
[15:59] <OvenWerks> but falktx is pretty busy these days
[16:00] <OvenWerks> I think patchage has sprouted python3 in the mean time too. but it may not be in debian yet. (and I could be wrong)
[16:01] <OvenWerks> if catia has the same trouble as carla... it does use the same patchbay code after all, all bets are off
[16:01] <Eickmeyer> Yeah, but you've got to remember that Carla is primarily a plugin host, so it makes sense for it to use juce.
[16:05] <Eickmeyer> New patchage is not yet in Debian.
[16:05] <Eickmeyer> Looks like it's being worked on.
[16:10] <OvenWerks> with so many things using juce, finding bugs is worth while.
[16:10] <Eickmeyer> Also remember that Carla 2.2 is just an RC at this point, he's still working on it.
[16:11] <OvenWerks> yup.
[16:24] <Eickmeyer> OvenWerks: in Fedora, pulseaudio is a user service.
[16:24] <OvenWerks> good.
[16:25] <Eickmeyer> https://paste.centos.org/view/3b3522ac
[16:25] <Eickmeyer> That's the log.
[16:26] <OvenWerks> maybe we can use systemd commands to stop start.
[16:27] <Eickmeyer> Also this: https://paste.centos.org/view/61979ad1
[16:27] <Eickmeyer> I'm wondering if Jack is the issue.
[16:30] <Eickmeyer> Either way, that's two separate machines I've tried now with Fedora that are experiencing the exact same issue with studio-controls.
[16:30] <OvenWerks> assume starting jack with -controls so max ports should be 2k or so
[16:32] <OvenWerks> Jack::JackGraphManager::AssertPort(jack_port_id_t): Assertion `port_index < fPortMax' failed.
[16:33] <Eickmeyer> Is that the issue right there?
[16:34] <OvenWerks> but I see other problems anyway. from the stuff you shared with me before, pactl is not able to communicate with pulse.
[16:34] <OvenWerks> yes an assert is always a fail and dump.
[16:35] <OvenWerks> but there are other things: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
[16:35] <OvenWerks> module alsacard should have already been unloaded
[16:36] <OvenWerks> from your autojack logfile that did not happen because pactl got a permision denied when it tried to do things with pulse. It looks like a dbus permission denied
[16:37] <OvenWerks> I have seen reports of similar things in the ardour forums
[16:37] <Eickmeyer> Hmmm....
[16:40] <OvenWerks> we may need to stop the systemd pulse and directly start our own, but I think others have found a solution without
[16:40] <OvenWerks> I will do some research... but it may take a while
[16:42] <Eickmeyer> ok
[16:57] <OvenWerks> in the mean time maybe remove carla 2.2 from backports
[16:57] <Eickmeyer> Ok, can do.
[16:58] <OvenWerks> I am not sure what to do with groovy... will 2.2 see a fix and release?
[16:59] <OvenWerks> I can't do a bug from here for that, maybe later I can reboot to groovy and do it there.
[17:00] <Eickmeyer> Well, you can always report your findings upstream to https://github.com/falktx/carla
[17:00] <OvenWerks> I suspect that it is not just unplugging USB devices but other graph changes as well
[17:00] <Eickmeyer> Because this issue isn't a packaging error, so it's completely beyond my control. Falktx doesn't watch launchpad for bugs.
[17:01] <Eickmeyer> And while launchpad can watch github issues, github cannot watch launchpad bugs.
[17:01] <Eickmeyer> So I'd rather any bug reporting go straight to falktx's github.
[17:01] <OvenWerks> 314 issues :P
[17:02] <Eickmeyer> Yep, but you've got to remember that a lot of those are support questions and feature requests, not actual bugs.
[17:02] <Eickmeyer> Github issues don't differentiate that like Launchpad and Bugzilla do.
[17:03] <Eickmeyer> It's up to the repo owner on github to tag issues as actual bugs, feature requests, support questions, or discussions.
[17:07] <OvenWerks> why can't github put dates on things? (26days ago...) a proper time stamp date time would be better.
[17:07] <Eickmeyer> Hover over it and it will give you the date.
[17:10] <OvenWerks> hmm, there is a commit 12 hours ago, "Alternative/better way to find all audio ports in juce plugins"
[17:11] <Eickmeyer> That might be the fix, but we won't know for a while.
[17:11] <Eickmeyer> This actually might be a good discussion to have in #lad.
[17:22] <OvenWerks> https://github.com/falkTX/Carla/issues/1237
[17:22] <OvenWerks> I will now clone master and build to see if it works better
[17:23] <Eickmeyer> Ok.
[17:47] <OvenWerks> Problem still exists
[19:59] <OvenWerks> this is painful... I have to reboot every time I kick this bug.
[21:39] <Eickmeyer> OvenWerks: Yikes.
[21:39] <Eickmeyer> Well, I've deleted it from the PPA, so if you "sudo apt autoremove carla && sudo apt update && sudo apt clean && sudo apt install carla" it should downgrade you.
[23:06] <OvenWerks> it is too bad it doesn't happen every time.
[23:07] <OvenWerks> I managed to downgrade thankyou.
[23:08] <OvenWerks> I have 2.1 installed and 2.2 built that I can run from the source directory. So I can compare
[23:59] <teward> Eickmeyer: i need a list of packages you need updated.
[23:59] <teward> never got a ping from you that I can see
[23:59] <teward> unless the Internet fubar'd
[23:59] <Eickmeyer> teward: On telegram.
[23:59] <Eickmeyer> Only two so far, no updates at this time since I can handle most of those myself.
[23:59] <teward> oh NOW it arrived
[23:59] <teward> never arrived before heh
[23:59] <Eickmeyer> Hahaha