[00:02] <clivejo> mmmmmm
[00:03] <clivejo> sgclark: try installing plasma-desktop now
[00:03] <sgclark> k
[00:03] <sgclark> I think I need to disable mergers
[00:03] <clivejo> I seem to have broken plasma-discover
[00:03] <clivejo> its just triggering them at midnight UTC
[00:04] <sgclark> I am stuck on mergers until yofel sets up a user with push rights in jenkins
[00:04] <clivejo> sgclark: could not read Username for 'https://git.launchpad.net': No such device or address (Git::GitExecuteError)
[00:05] <sgclark> clivejo: yes I am very aware of the error
[00:05] <sgclark> because we don't have an LP user with commit push rights
[00:05] <clivejo> ah
[00:05] <sgclark> I am done fighting with it for now
[00:06] <sgclark> cause only council has the rights and password for kubuntu-ci-bot
[00:06] <clivejo> is kubunbu-ci not a user?
[00:06]  * sgclark turn off mergers
[00:06] <sgclark> clivejo: kubuntu-ci-bot it but I do not have the password
[00:06] <sgclark> KC does
[00:07] <sgclark> and they are ignoring my pleas for help
[00:07] <clivejo> uploads to the PPA, so it must have the key installed on KCI?
[00:08] <sgclark> clive I fought with it for 2 days straight and could not get it to work. Auth failure every time.
[00:09] <sgclark> I need a break. and help from folks that hold magical passwords. I am done fighting in the dark lacking tools
[00:10] <sgclark> hmm no pasma upgrades available
[00:10] <sgclark> plasma
[00:11] <sgclark> clivejo: no plasma to try
[00:11] <clivejo> have you plasma PPA enabled?
[00:11] <sgclark> yes
[00:11] <sgclark> oh
[00:12] <sgclark> duh
[00:12] <clivejo> apt update?
[00:12] <sgclark> I don't know what those other updates were
[00:12] <sgclark> I am on xenial
[00:12] <sgclark> ...
[00:12] <sgclark> I would not get these
[00:12] <clivejo> nope!
[00:12] <sgclark> must have been older stuff
[00:12] <clivejo> just yakkety
[00:12] <sgclark> yeha
[00:12] <sgclark> sorry
[00:12] <sgclark> is it all green?
[00:13] <clivejo> although when its tested, should be ready to backport
[00:13] <clivejo> Im not quite happy with it yet
[00:13] <clivejo> I made discover go red
[00:13] <sgclark> if you want testers toss it in landing and we can fcall for testers
[00:13] <sgclark> doh!
[00:13] <sgclark> np
[00:13] <clivejo> it was complaining about not finding a dep
[00:13] <sgclark> I am far from ready with apps, all seem to be broken installs
[00:14] <clivejo> so I added it and now its not building a pile of files
[00:14] <clivejo> that makes NO sense
[00:14] <sgclark> eek
[00:14] <clivejo> Ill just do a git revert me thinks
[00:18]  * clivejo should I add the staging PPA?
[00:19]  * clivejo opens Muon very slowly
[00:20] <soee_> sgclark: i think new Plasma is more important for users than Apps :) so it would be nice to have it backported when it will be possible
[00:20]  * clivejo looks for his trout 
[00:21] <clivejo> soee_: have you yakkety yet?
[00:21] <soee_> clivejo: no :)
[00:22] <clivejo> why not?
[00:23] <soee_> clivejo: because there is nothing fancy yet, not merges from debian etc.
[00:24] <soee_> i think i will jump with first alpha
[00:24] <clivejo> oh dear, what have I done!
[00:25] <soee_> -.-
[00:25] <clivejo> if you dont see me ever again, youll know why
[00:26] <clivejo> plasma went boom
[00:26] <soee_> well that is interesting no?
[00:26] <clivejo> soee_: I dont know yet
[00:26] <clivejo> its installing now
[00:26] <soee_> :D
[00:27] <clivejo> I think Im more stupid than brave!
[00:28] <clivejo> 22%
[00:28] <soee_> yy upgrade ?
[00:28] <soee_> or Plasma 5.6 ?
[00:28] <clivejo> Im on YY 
[00:28] <clivejo> Plasma 5.6.3
[00:28] <sgclark> clivejo: I am curious, have you used that backport script?
[00:28] <clivejo> 40%
[00:29] <soee_> i would say lucky you :)
[00:29] <clivejo> yes, back in xenial I think
[00:29] <sgclark> soee_: frameworks are backported, I expect plasma won't take long
[00:29] <clivejo> but probably needs mod to work with LP move
[00:29] <sgclark> clivejo: ok. maybe try it with plasma when ready 
[00:29] <sgclark> oh
[00:30] <sgclark> dang
[00:30] <sgclark> right nm
[00:30] <clivejo> eakk
[00:30] <clivejo> 100%
[00:30] <sgclark> I will let yofel keep the python stuff. I have my hands full with ci
[00:31] <soee_> sgclark: i have Frameworsk installed since you strted them on Xenial
[00:32] <sgclark> cool
[00:32] <sgclark> clivejo is working on plasma, so butter him up for the backports lol
[00:32] <clivejo> is frameworks working ok in xenial?
[00:32]  * sgclark drowns in apps
[00:33] <sgclark> clivejo: shouold be. let me check
[00:33] <soee_> sgclark: shouldn't we remove Wily from those Staging ppas ?
[00:33] <sgclark> soee_: yeah and from CI. on my Gigantic TODO list
[00:33]  * sgclark drowns some more and checks xenial backports
[00:34] <clivejo> klear in the dev-tools should help with that
[00:34] <soee_> the Frameworks have problem only with oxygen5-icon-theme but i think yofel might fix it?
[00:35] <clivejo> : error processing archive /var/cache/apt/archives/libkf5runner-dev_5.21.0-0ubuntu1~ubuntu16.10~ppa1_amd64.deb (--unpack):
[00:35] <clivejo>  trying to overwrite '/usr/share/kdevappwizard/templates/runner.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1
[00:36] <clivejo> I think thats a deal breaker
[00:36] <clivejo> anyways, Ill try rebooting.  If Im not back in five mins, its broken my system!
[00:38]  * soee_ goes to bed .. nn
[00:42] <clivejo> holy moley
[00:42] <clivejo> it works!
[00:42] <clivejo> KDE Plasma Version 5.6.3
[00:42] <clivejo> Kubuntu 16.10
[00:42] <sgclark> nice
[00:42]  * clivejo does happy dance
[00:43] <clivejo> sgclark: did you get my krunner message?
[00:43] <sgclark> seems like they are busting up that kapptemplate into main packages
[00:43] <sgclark> ^^
[00:43] <sgclark> I would add a breaks/replaces on kapptemplate
[00:44] <mamarley> Yay!
[00:44]  * mamarley looks forward to a Xenial backport. :)
[00:44]  * sgclark does too
[00:45] <mamarley> Speaking of Xenial, I accidentally updated one of my systems from the frameworks staging PPA.  It seems to work fine, FWIW.
[00:46] <sgclark> I just update extra-cmake-modules in xenial
[00:54] <clivejo> strange disconnection to my bouncer
[00:54] <valorie> woah, you folks have been working HARD!
[00:54] <valorie> <3 and kisses and {{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}
[00:55] <clivejo> I blame Scarlett!
[00:55]  * valorie heads off to visit the parental unit
[00:55] <clivejo> cracking the whip
[00:55] <valorie> it's odd to see the occasional green
[00:55] <valorie> what's magic there?
[00:55] <clivejo> valorie: are you on YY?
[00:55] <valorie> nope
[00:56] <mamarley> Yeah, great job!
[00:56] <clivejo> mamarley !!!
[00:56] <valorie> once I buy my son's "old" laptop so i have a backup again
[00:56] <valorie> I'll jump on this one
[00:56] <clivejo> did you install YY?
[00:56] <mamarley> clivejo: On a VM.
[00:56] <clivejo> can you add plasma staging and install 5.6.3?
[00:57] <mamarley> clivejo: Sure.
[00:58] <clivejo> I have to go to bed, but can you look into that krunner package install problem and give feedback to sgclark?
[00:58] <mamarley> Sure.
[00:58] <clivejo> pretty pls, with sugar on top :)
[01:02] <clivejo> night night all
[01:08] <sgclark> valorie: no magic. most of the fails are dependency issues, it will take some time for the CI to "catch up" and plus clivejo and I fixing packages like mad.
[01:08]  * sgclark cracks the whip
[01:09] <sgclark> uploaded a new oxygen-icons hopefully fixes the issue
[01:09] <mamarley> I tried to upgrade Yakkety with the plasma-staging and frameworks-staging PPAs but I can't install plasma-workspace  because it depends on kactivities which can't be installed because it depends on qml-module-org-kde-activities which can't be installed because it depends on libkf5activities ~ppa1 and ~ppa2 is installed.
[01:10] <sgclark> hmm
[01:11] <sgclark> ok I can fix that
[01:11] <sgclark> ty
[01:11] <mamarley> No problem.  Thank you for all your work!
[04:30] <valorie> nice to see the green!
[07:33] <soee_> good morninr
[07:34] <soee_> sgclark: oxygen5-icon-theme installed fine on Xenial, thank you for this fix
[08:43] <soee_> clivejo: will you backport 5.6.3 ?
 Gimme a chance to get it tested in Yakkety
 Yofel: ping
[08:57] <clivejo> mamarley: any feedback?
[09:14] <yofel> clivejo: hm?
 Moring Soee
 o/
[09:16]  * yofel tries to generate l10n
[09:17] <soee_> hiho Sick_Rimmit>
[09:18] <soee_> uh reading the #plasma it seems that the desktop long loading time will be fixed in 5.6.4 by reverting one commit
[09:19] <yofel> yay, wgrant_ fixed launchpad
[09:20] <yofel> actually
[09:20] <yofel> wgrant: thanks a lot!
[09:22] <yofel> soee_: which one?
[09:22] <yofel> ah, I see
[09:23] <yofel> sounds like we want to SRU that
[09:23] <Odur> yofel: I tried to build l10n-sv and engb for xenial from yakkety source locally, and it went well. Not quite sure what sgclark ment by this comment https://bugs.launchpad.net/ubuntu/+source/kde-l10n-ru/+bug/1576455/comments/6
[09:24] <yofel> Me neither, that's why I want to try it
[09:24] <Odur> Nice :)
[09:24] <yofel> bah, we need to move all that l10n stuff to gid
[09:24] <yofel> *git
[09:24] <clivejo> yofel: hi
[09:24] <yofel> moin
[09:25] <clivejo> so I want to fix the VCS fields in plasma and also bump the standards
[09:25] <clivejo> VCS [09:26] <clivejo> is this something you want to script and do all at once?
[09:26] <Odur> btw. I saw that skanlite was tagged 2.0.0 as the first kf5 version of it. Not quite sure how to package it though... I really need to learn this sh*t :/
[09:26] <yofel> clivejo: yes, and I was kind of stuck on LP returning invalid data for that
[09:26] <yofel> which works now
[09:27] <yofel> Odur: well, you're at the perfect place then ;)
[09:27]  * yofel mumbles something about people not using correct l10n branches
[09:27] <yofel> well, she was overworked
[09:28] <clivejo> is xenial stuck on standards-version 3.9.7 (current is 3.9.8 in yakkety)?
[09:28] <Odur> yofel: Yeah, I know. I just have to finish this last semester in the university. Medical school is hard :)
[09:29] <yofel> clivejo: we really don't care about that, but feel free to fix if no changes are required
[09:29] <soee> yofel: btw. Scarlett has fixed this last package in Frameworks (the oxygen icons) :)
[09:29] <clivejo> well I thought kill several birds with the one stone
 Odur
[09:29] <yofel> ah good, I never uploaded that
 I plan to run a Kubuntu Dojo next week, introducing folks to packaging
[09:30] <clivejo> Ill have to rebuild all the packages with the new control file after you are done
[09:30] <yofel> clivejo: sure, but that's still the compliance version. You *did* read the the 3.9.8 changelog, yes?
[09:30] <Odur> Sick_Rimmit: Ok, I'll see if I have the time
 OK, there should some info on kubuntu.org early next week
 I'll update here
 too
[09:31] <Odur> I'll keep my eyes out for it
[09:31] <clivejo> I didnt, but I thought the idea of standards file was so that lintian reports stuff we are doing wrong and gives us a chance to "comply"
[09:31] <clivejo> or die
[09:32] <soee> yofel: oh the bug was in Frameworks not Plasma :/ So it will be fixed in Frameworks 5.22 it seems
[09:32] <yofel> soee: well, I care whether it's fixed in 5.18, so as long as the review says "Ship it", I'm fine
[09:32] <soee> Odur: follow Kubuntu on twitter :)
[09:33] <Odur> soee: No twitter here :P
[09:33] <soee> :O
[09:34] <Odur> (And no Facebook either. Just G+, and I follow Kubuntu there)
[09:34]  * yofel wrote a twitter post for the twitter birthday
[09:34] <yofel> sounded appropriate
[09:34] <soee> :)
[09:34] <yofel> hm, l10n is indeed busted, wft
[09:39] <clivejo> yofel: can I upload stuff to YY?
[09:39] <yofel> archive you mean?
[09:39] <soee> why Konversation ignores webbrowser set as default ?
[09:39] <clivejo> yea
[09:39] <yofel> no, requires ~ubuntu-dev
[09:40] <clivejo> ah thought so
[09:41] <wgrant> yofel: np, thanks for reporting.
[09:46] <clivejo> yofel: For https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma/+build/9685568/+files/buildlog_ubuntu-yakkety-amd64.plasma-sdk_4%3A5.6.3-0ubuntu1~ubuntu16.10~ppa1_BUILDING.txt.gz , should I add kdevplatform-dev as a build dep?
[09:48] <yofel> You could if we had kdevplatform >= 4.90.90
[09:48] <yofel> or do we?
[09:49] <clivejo> we have 1.7.3
[09:50] <clivejo> set(KDEVPLATFORM_LIB_VERSION 8.0.0)
[09:51] <clivejo> set(KDEV_PLUGIN_VERSION 17)
[09:51] <clivejo> set(KDEVPLATFORM_VERSION_MAJOR 1)
[09:51] <clivejo> set(KDEVPLATFORM_VERSION_MINOR 7)
[09:51] <clivejo> set(KDEVPLATFORM_VERSION_PATCH 3)
[09:52]  * clivejo shrugs, that makes NO sense
[09:53] <yofel> why not, those are 3 different things
[09:53] <clivejo> 4.90.90
[09:53] <clivejo> is that a version 5 beta or something?
[09:54] <yofel> that's the kf5 version. you need kf5 kdevplatform for kf5 dev tools
[09:54] <clivejo> ok, so we dont have that
[09:54]  * clivejo ignores it
[09:54]  * yofel fixed l10n
[09:55] <clivejo> what was the problem?
[09:55] <Odur> yofel: Nice job!
[09:56] <yofel> she accidentally edited the package name variable in the changelog, so the substitution was failing
[09:57]  * yofel goes back to work
[09:58] <clivejo> yofel: so Ill hold off until you do that batch VCS update?
[09:58] <yofel> oh right, I wanted to do that
[09:59] <clivejo> well Im currently running Yakkety with Plasma 5.6.3 so it seems to work :)
[09:59] <yofel> any new packages?
[09:59] <clivejo> but I wanted to get the packaging sorted before trying to backport it
[10:00] <clivejo> yeah I added them as I went
[10:00] <clivejo> plasma-intrgration is the only one I remember
[10:00]  * clivejo wonders did he push that to KA
[10:01] <yofel> does it need new frameworks?
[10:01] <clivejo> yes
[10:01] <yofel> ok, then that has to go in first
[10:01] <clivejo> I copied them over from the staging PPA
[10:01] <clivejo> as I needed them
[10:01] <yofel> maybe lets do another FW rebuild before uploading, so we don't end up in another build failure mess like a month ago..
[10:02] <clivejo> : error processing archive /var/cache/apt/archives/libkf5runner-dev_5.21.0-0ubuntu1~ubuntu16.10~ppa1_amd64.deb (--unpack):
[10:02] <clivejo>  trying to overwrite '/usr/share/kdevappwizard/templates/runner.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1
[10:02] <blaze> I've already created packages of kdevelop5, kdevplatform etc. in my ppa
[10:03] <clivejo> thats the only error I got on installing plasma on yakkety
[10:03] <yofel> well fix it ^^
[10:03] <clivejo> Im not allowed!
[10:03] <yofel> huh?
[10:03] <clivejo> frameworks are Scarletts
[10:03] <blaze> it's a bit too early to push'em into release
[10:03] <yofel> ...
[10:04] <yofel> blaze: why?
[10:04] <blaze> because some stuff isn't working
[10:04] <yofel> this is the development release, live with it...
[10:05] <yofel> seriously, all this dev-should-always-be-stable crap is what caused all the last-minute mess in xenial
[10:07] <clivejo> I dont understand that, surely dev version is to iron out the bugs
[10:07] <Odur> yofel: Why ubuntu1.1 on l10n? Yakkety is on ubuntu2. Just curious how it works :)
[10:07] <yofel> Odur: version has to be lower than 2, and .1 is the usual thing to do for SRUs
[10:08] <yofel> clivejo: well yes, but then someone in ubuntu said that people should be able to test dev with only minor hiccups and frowned upon devs that uploaded WIP stuff to dev
[10:08]  * clivejo mutters under his breath
[10:09] <yofel> and now the release team is even more angry at people breaking stuff post-beta
[10:09] <yofel> hence the mail that people should please upload stuff to release when they're ~done
[10:09] <yofel> and not do private tests for months
[10:11] <mamarley> clivejo: I posted a message about something not installing.  sgclark said she would fix it, but I haven't tested yet.  I am about to do that.
[10:11] <clivejo> what was the package
[10:12] <clivejo> did you get the krunner conflict?
[10:12] <mamarley> No, I can't remember what it was anymore.
[10:12] <yofel> dependency issue or...?
[10:14] <mamarley> Yeah, it was dependencies.  I am testing again, just a sec…
[10:15] <yofel> clivejo: if you've got nothing to do, fancy patching up an SRU for the plasma splash timeout?
[10:17] <mamarley> [21:09:38] [2016/05/05] <mamarley> I tried to upgrade Yakkety with the plasma-staging and frameworks-staging PPAs but I can't install plasma-workspace  because it depends on kactivities which can't be installed because it depends on qml-module-org-kde-activities which can't be installed because it depends on libkf5activities ~ppa1 and ~ppa2 is installed.
[10:17] <mamarley> Still happening. :(
[10:18] <clivejo> mamarley: what PPA's did you install?
[10:18] <mamarley> clivejo: Staging for both plasma and frameworks.
[10:19] <clivejo> ah
[10:19] <clivejo> I only used plasma
[10:19] <Odur> yofel: Where will the l10n packages end up after building?
[10:20] <yofel> xenial-proposed
[10:20] <Odur> thx
[10:20] <yofel> which will probably take a couple days
[10:20] <Odur> no worries
[10:20] <clivejo> yofel: plasma splash timeout?
[10:21] <yofel> https://git.reviewboard.kde.org/r/127848/
[10:21] <yofel> or at least a 5.5 test package so we can see if it helps
[10:22] <yofel> er, 5.18
[10:24] <clivejo> so I grab plasma-frameworks 5.18 and apply that patch?
[10:24] <clivejo> is there a LP bug?
[10:27] <yofel> dunno
[10:27] <yofel> soee: ^ ?
[10:28] <clivejo> yofel: for SRU what branch I use?
[10:28] <clivejo> xenial_archive?
[10:28] <yofel> yes
[10:29] <soee> bug for what ?
[10:29] <yofel> soee: the splash timeout thing
[10:29] <soee> well i think it is related to my report somehow https://bugs.kde.org/show_bug.cgi?id=360777
[10:30] <clivejo> soee: it on LP?
[10:30] <soee> i doubt
[10:30]  * clivejo shakes head
[10:35] <clivejo> yofel: should he make one?
[10:35] <clivejo> for me to close in the SRU?
[10:35] <clivejo> so the powers that be know its a fix for something
[10:35] <yofel> well, make a test package first. If it works we can create a bug and add it to the changelog
[10:41] <clivejo> yofel: that patch seems to be applied in 5.18 
[10:42] <yofel> oh, then it's unrelated I guess..
[10:42] <mamarley> I should probably look at getting Quassel 0.12.4 SRUed since it fixes some pesky database problems, a bug causing users to receive broadcasted PM SPAM, and a core crash bug.
[10:43] <yofel> mamarley++
[10:43] <clivejo> yofel: plasma-framework 5.18 SC - http://paste.ubuntu.com/16255472/
[10:43] <soee> clivejo: what patch?
[10:43] <mamarley> Oh wait, 0.12.4 isn't even in Yakkety yet.  Who is the maintainer these days?
[10:44] <yofel> uh, us probably
[10:45] <yofel> or not
[10:45] <yofel> MOTU I guess
[10:45] <mamarley> yofel: What's the process for getting it updated then?
[10:46] <yofel> File a bug, attach a package/debdiff and subscribe ~ubuntu-sponsors to get it uploaded
[10:46] <mamarley> This would be more than a new debdiff though, this would be a whole new orig.tar.gz.
[10:47] <yofel> Pointing to a ppa is accepted too I believe
[10:47] <yofel> #ubuntu-motu might give you more accurate information
[10:47] <mamarley> Ah, OK.
[10:50] <mamarley> Would it perhaps be possible for me to become the Quassel maintainer?  I have been doing the PPA for a while now and I am somewhat involved with Quassel development, so…
[10:50] <yofel> sure, you can apply to the DMB for package-specific upload permissions
[10:51] <yofel> https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess
[10:52] <mamarley> That looks do-able, though I should probably get the 0.12.4 upload done first.  I'm not really sure of anyone who would endorse me though.
[11:00] <mamarley> Hmm, I seem to have run out of time for this morning.  I will work on this more over the weekend.
[11:02] <soee> it is almost weekend ;)
[11:03] <debfx> there is also requestsync which avoids duplication of work
[11:06] <yofel> which would first require a package review
[11:06] <yofel> as our quassel package does not share a history with debian
[11:07]  * soee reboot
[11:07] <yofel> l10n uploaded
[11:08] <yofel> someone needs to write a 'generate-packages-from-ref.sh'
[11:08] <clivejo> soee: is your xenial a test system?
[11:08] <soee> clivejo: well i work on it but i always test things here :)
[11:09] <clivejo> can I ask you to test something?
[11:09] <soee> i am not an expert but i know how to fix thngs if something break
[11:09] <soee> clivejo: sure
[11:11] <clivejo> this is purely experimental!
[11:11] <clivejo> in my xenial PPA there is a package building - plasma-framework 5.18.0-0ubuntu1.1~ubuntu16.04~ppa1
[11:11] <clivejo> it will take a while to publish
[11:12] <soee> hmm but im on frameworks 5.21 
[11:12] <clivejo> can you install it and test that login splash screen delay
[11:12]  * clivejo rolls eyes
[11:13] <clivejo> is it fixed in frameworks 5.21?
[11:13] <soee> i doubt, wasn't this patch proposed today ?
[11:13] <soee> so it will land in 5.22 when accepted i think
[11:14] <yofel> hm, there is a plasma-discover repo again
[11:14] <clivejo> well if someone with the delay bug can test that package in my PPA
[11:14] <soee> yofel: user reported kdeconnect problem on 14.04 do we support it? https://paste.kde.org/pszn44wbc
[11:15] <soee> clivejo: i'll try i have this bug active atm :)
[11:15] <clivejo> soee: can you ppa purge FW5.21?
[11:15] <soee> and if i have it active and im on Frameworks 5.21
[11:15] <soee> it isn;t fixed for sure in this ver
[11:16] <clivejo> well if this fix works it can be applied to 5.21
[11:16] <clivejo> but Im not holding my breath
[11:18] <soee> i think i have to downgrade frameworks
[11:34] <soee> hmm purging ppa failed with this one
[11:34] <soee> qml-module-org-kde-activities : Depends: libkf5activities5 (= 5.21.0-0ubuntu1~ubuntu16.04~ppa2) but 5.18.0-0ubuntu1 is to be installed
[11:40] <soee> ok fixed it by manually installing qml-module-org-kde-kquickcontrols_5.18.0-0ubuntu1_amd64.deb
[11:40] <soee> brb
[11:42] <yofel> clivejo, sgclark: VCS URLs in all repositories updated
[11:43] <sitter> why did you move away from git.debian btw?
[11:44] <yofel> sitter: permission issues and lisandro__ being annoyed at people messing up
[11:45] <soee> claydoh: iv installed this files from your ppa (all without dev one)
[11:45] <sitter> I am not sure technical solutions to social problems is all that wise, but I can understand the motivation there ^^
[11:45] <sitter> rather unfortunate
[11:45] <yofel> it's a  workaround sure, but like this we can actually get work done
[11:45] <soee> it breaks plasma in sense not loading panels etc. and teh loading time is even longer
[11:53] <soee> meh my panel is  gone after removing this package
[12:11] <BluesKaj> Hiyas all
[12:14] <allee> Hi BluesKaj
[12:14] <BluesKaj> Hi allee
[12:23]  * allee !@#$% search does not work in quassel-client anymore :-(
[12:29] <yofel> clivejo: so, I wrote a script that should allow to re-upload packages to the PPA (or generate a new upload set)
[12:29] <yofel> pull KA and run ./generate-packages-from-ref -c plasma -w /tmp/generated-packages if you want to alpha-test it
[12:31] <allee> yofel: hi, I found by accident:  kdegraphics-strigi-plugins  # qt4 Task: kubuntu-desktop, kubuntu-full
[12:31] <allee> and qt4 based: baloo-utils libbaloo*4 libakondi-{kmime,kde,kabc}4 kdeconnect
[12:31] <yofel> allee: file a bug against kubuntu-meta please
[12:32] <allee> k
[12:32] <yofel> doesn't need much info, just what shouldn't be there
[13:18] <clivejo> yofel: how does the script handle ppax versions?
[13:19] <yofel> clivejo: same as gbp, -s
[13:19] <telegram> @IrcsomeBot was added by: @ovidiuflorin
[13:20]  * yofel throws chat_id's at IrcsomeBot
[13:20] <ovidiuflorin> IrcsomeBot is the duplicate user created by KDE sysadmins because the didn't want to get ownership of the one I made
[13:21] <ovidiuflorin> even though I gave it to them
[13:22] <BluesKaj> irksome bot the correct name :-)
[13:22] <BluesKaj> is
[13:23]  * ovidiuflorin is pissed off because of this
[13:23] <clivejo> is anyone else experiencing the plasma login splash delay?
[13:24] <mamarley> clivejo: I experience it on a couple of systems I maintain that have Intel GPUs.
[13:25] <clivejo> mamarley: could you test a package for me?
[13:26] <yofel> where's the package? My notebook shows the splash a bit long, but that'll have to wait a couple more hours
[13:26] <mamarley> clivejo: Tonight, once I get to my parents' house where those two systems reside?
[13:26] <allee> kubuntu-meta bug filed.
[13:27] <soee> mamarley: it will break your dekstop a bit imo :)
[13:27] <clivejo> soee: did you try it?
[13:27] <yofel> allee: thanks
[13:27] <soee> clivejo: yes
[13:27] <clivejo> and?
[13:28] <soee> clivejo: loading time is even longer, disk seems to do some hard work during booting, desktop looses all panels, wallpapers etc. so it messes something in configuration
[13:29] <clivejo> eakk
[13:29] <soee> after restoring current version my panel was not restored i had to recreate it
[13:30] <soee> clivejo: maybe there is something else related to this change in newer Frameworsk that makes it fail on 5.18 ?
[13:30] <clivejo> wonder is that the patch or the fact you downgraded 
[13:30] <soee> clivejo: i downgraded to frameworks in archive
[13:30] <soee> than downloaded debs  from launchapd and updated
[13:31] <clivejo> yeah, but the downgrade could been to blame for the trashed desktop
[13:31] <soee> debs from our ppa
[13:31] <soee> well not it works fine after overwriting your packages and im on 5.18 atm.
[13:31] <clivejo> hummm
[13:31] <clivejo> weird
[14:03] <yofel> lolwhat
 sorry, completely forgot: the workers blacklist yakkety/s390x/marble
 as this is killing the workers and causing tmpfail loops
[14:23] <yofel> hm, our build-version bumping seems to still be broken
[14:24] <yofel> attica 5.21 should not be depending on ecm 5.18
[14:35] <mamarley> So I just happen to mention in passing that I use KDE in another channel, and someone says it is bloated and "sh*tty".  I state that most of the stuff people consider to be bloaty can be removed.  The person then says "no one has said its good software" "you are looking stupid atm" "move on already".  I really hate immature people.
[14:36] <mamarley> (And I was not, of course, saying anything negative about any other DEs, or even why I don't use those DEs.)
[14:36] <mamarley> Argh.
[14:39] <allee> mamarley: weird :-(
[14:41] <mamarley> I know it is kind of OT, but I just needed to blow off some steam and this is the channel I am in that is least likely to spew KDE hate, so…
[14:43] <allee> no problem
[14:52] <yofel> *yawn*
[14:52] <yofel> where's the news... -.-
[14:55] <mamarley> No news, I guess.  Just the same as elementary-school bullies.  They are apparently lack so much confidence in their own DE choices that they need to put others down to feel better about it…
[14:56] <yofel> right, and linux in general seems to have a lot of those, which certainly isn't helping the reputation
[14:57] <mamarley> Indeed.
[14:57] <yofel> (the only sad part is that I can't really counter any 'kde is buggy' statements because it's the truth)
[14:57] <mamarley> All software has bugs.
[14:59] <yofel> yes, but kde seems to have a particulary fragile architecture. At least compared to other DEs
[15:00] <mamarley> The stuff I have heard the most complaints about is Akonadi and PIM, and I don't use those, so I can't really comment.
[15:02] <clivejo> well my akonadi and Kontact was very stable up until Ubuntu forced MySQL 5.7 into Xenial
[15:02] <mamarley> I think the fact that it depends on MySQL at all is rather silly.
[15:03] <mamarley> (And is the primary reason I don't use it.)
[15:03] <mamarley> (Not because I hate MySQL (I don't) but because I don't think it is a good idea to require a full RDBMS for a desktop system like that.)
[15:03] <yofel> +1
[15:06] <BluesKaj> is it safe to purge mysql  ?
[15:06] <mamarley> If you don't use anything depending on it (like Akonadi), it should be.
[15:07] <sgclark> yofel frameworks were done prior to the move and by hand backport->yakkety and therefore done by the script of Scarlett. Which is quite broken and buggy.
[15:07] <BluesKaj> good , akonadi is pita for us home users anyway
[15:10] <yofel> sgclark: the whole thing is broken in one way or another anyway, so I'm not surprised
[15:11] <sgclark> akonadi has some really cool resources though ( like watching git repos ) of course I don't have time to package them.
[15:11] <sgclark> what whole thing?
[15:11] <sgclark> what did I miss?
[15:11] <yofel> the build-dep stuff
[15:11] <sgclark> ah well it cannot be blamed for frameworks
[15:11] <sgclark> all by hand
[15:11]  * sgclark goes to fix attica
[15:12] <yofel> I would rather try to fix the script and then see if that can be run over all frameworks..
[15:13] <yofel> but don't let that hold you back if it would
[15:13] <yofel> bbl
[15:13] <sgclark> yofel: in this case things were wierd, in the merge I had mixed 5.18 and 5.19 so my sed only caught 5.19 defined
[15:14] <yofel> aaah
[15:14] <yofel> I've been thinking about the upload workflow lately
[15:15] <yofel> I really believe that staging-upload *has* to be run, no matter what you did before
[15:15] <yofel> we have a bunch of QA and safety mechanisms that get omitted if you don't use it
[15:16] <yofel> and in the end we run face-ahead into hell
[15:16] <sgclark> haha
[15:16] <sgclark> sure
[15:16] <sgclark> this whole move has been madness
[15:17] <sgclark> yofel: I still need a user set up in jenkins with push rights
[15:17] <yofel> I don't mean only the move. e.g. the whole akonadi build-ordering mess we had in xenial would never have happened if staging-upload would have worked as designed and had actually been used
[15:17] <sgclark> set it up in credentials
[15:17] <yofel> oh right sorry
[15:17] <yofel> harald sent me some credentials for that, sec
[15:18] <sgclark> hmm surely we used the script in xenial
[15:18] <yofel> we did not, we did a 2 month merge and skipped the staging
[15:18] <yofel> and hell broke loose
[15:19] <yofel> so lets maybe not do that again -.-
[15:19] <yofel> (well, that was everyone's fault really, mine included)
[15:19] <sgclark> oh
[15:19] <sgclark> right
[15:19] <sgclark> that was merge hell
[15:20] <yofel> anyway, bbl
[15:20] <sgclark> but it made this merge very easy. but still I agree
[15:44] <ronnoc> Does anyone know off the cuff if the fact that KMM stopped working on 14.04.04 is an Ubuntu packaging issue or a KDE / KMM issue? I need to know where to report the bug. For reference: https://forum.kde.org/viewtopic.php?f=69&t=132787&sid=747103ee3b94e4a4d366739ad2c0c955 
[15:45] <ronnoc> KMM = KMyMoney, BTW
[15:51] <sgclark> omg
[15:51]  * sgclark dances
[15:59] <sgclark> ronnoc: never packaged KMM. not sure who has. afaik they have their own PPA
[16:01] <ronnoc> Actually, I think it's claydoh 's personal PPA on further review ;)
[16:01] <ronnoc> so hopefully he'll jump in
[16:02] <sgclark> oh in that case report to him. and please do I would like to get it in archive, just have not had time to test it myself
[16:02] <ronnoc> should be related: https://bugs.archlinux.org/task/49209
[16:03] <ronnoc> he's logged in here so I'll just wait to see if he sees it
[16:04]  * ronnoc goes back to the day job so sgclark can continue dancing :)
[16:04] <sgclark> lol
[17:03] <shadeslayer> sgclark: I think you should not have this https://github.com/ScarlettGatelyClark/pangea-tooling/blob/master/Gemfile.lock
[17:04] <sgclark> I did not touch that file?
[17:04] <shadeslayer> yes you did :P
[17:04] <shadeslayer> https://github.com/ScarlettGatelyClark/pangea-tooling/blame/master/Gemfile.lock
[17:04] <shadeslayer> sgclark: probably accidentally though
[17:06] <sgclark> shadeslayer: please explain wtf I did, I have 50 things going on and I cannot read your mind :(
[17:06]  * sgclark cries
[17:06] <shadeslayer> oh noes :(
[17:07] <shadeslayer> sgclark: *hugs*
[17:07] <shadeslayer> sgclark: Gemfile.lock describes what gems you have installed on your system
[17:08] <shadeslayer> sgclark: you don't want to check that into source control
[17:08] <shadeslayer> actually, let me add that to .gitignore
[17:08] <sgclark> ah
[17:08] <sgclark> I see
[17:09] <shadeslayer> sgclark: would not recommend doing 50 things at once btw
[17:09] <shadeslayer> 49 of them tend to go wrong then
[17:09] <sgclark> ScottK: I need to know what process we used at release to test kde-l10n* packages if any.
[17:09] <sgclark> ScottK: please
[17:10] <sgclark> shadeslayer: yes that is the results I am getting
[17:10] <sgclark> I need to drop hats, and the question is which ones get the boot?
[17:10]  * sgclark loves all her projects
[17:11] <shadeslayer> sgclark: I'd presume that testing kde-l10n requires you to install it via the language KCM and check if things are translated
[17:11] <shadeslayer> sgclark: you need to prioritize :P
[17:11] <shadeslayer> or you'll burn out
[17:11] <clivejo> time slice
[17:11] <sgclark> indeed
[17:11] <sgclark> I burned out long ago lol
[17:11] <shadeslayer> or time slice, but then your time slices are too thin
[17:11] <clivejo> setup an alarm to ring every 5 mins
[17:11] <shadeslayer> if you have 50 projects
[17:12] <clivejo> and switch jobs
[17:12] <sgclark> but I cannot get myself to drop anything
[17:12] <shadeslayer> that's ... about 10 minutes per project if you have 8 hours a day and 50 projects :P
[17:12] <shadeslayer> I can't make context switches that fast xD
[17:13] <shadeslayer> sgclark: you have to :(
[17:13] <shadeslayer> sgclark: for the sake of your health
[17:13] <sgclark> well my problem is that instead of learning to do anything *really well* I know how to scrape by on everything. THis really is not good for my career
[17:13] <clivejo> be more machine, like yofel!
[17:13] <shadeslayer> sgclark: I know the feeling
[17:13] <shadeslayer> sgclark: actually, you'd be surprised
[17:13] <shadeslayer> I believe more companies are hiring for generalists than specialists these days
[17:14] <sgclark> anyway, I am almost there with ci, but having a heck of a time wrapping my head around this git semaphore
[17:14] <shadeslayer> or well, most of the people I talk to want more 'generalists'
[17:14] <sgclark> ah well that is good to know
[17:14] <shadeslayer> idk what being a generalist entails xD
[17:14] <shadeslayer> sgclark: oh also btw : https://api.launchpad.net/1.0.html#git_repositories
[17:14] <sgclark> it passes the tests :( but epic fails in job
[17:16] <sgclark> yeah my brain is too broken to work out that. I am not an api master. still sooooo much to learn
[17:16]  * sgclark cries again
[17:16] <shadeslayer> I'm going to stop throwing things at sgclark
[17:16] <shadeslayer> :(
[17:16] <shadeslayer> sgclark: really, take a break, the world is still going to be here when you get back
[17:17] <sgclark> well considering I started at documentation, I have rather grown in knowledge. 
[17:17] <shadeslayer> ^_^
[17:17] <shadeslayer> I started writing out docbooks fo rekonq
[17:18] <shadeslayer> back when it was hosted on ... gitorious
[17:18] <sgclark> wow
[17:24] <clivejo> If someone hand holds me, Im game to learn
[17:24] <clivejo> although maybe not this weekend1
[17:26] <sgclark> leanr what?
[17:26] <sgclark> learn
[17:28] <clivejo> how KCI works
[17:30] <clivejo> but not now, Ive just got in from a wake and have to get up at 3:15am in the morning
[17:32] <sgclark> Oh, I wont be much help. I am getting good at breaking it though
[17:33] <clivejo> its more fun when somebody else is helping too :P
[17:36] <clivejo> shadeslayer: what OS do you run perosnally?
[18:23] <shadeslayer> clivejo: Debian Testing
[18:23] <shadeslayer> though I'm kind of sad that it has't had updates to Plasma yet
[18:26] <clivejo> how come?
[18:30]  * sgclark fears the kickback from her blog post
[18:55] <sgclark> hmm
[18:56]  * sgclark is very confused
[19:07] <soee> uh lala
[19:08] <yofel> see it from the positive side, it's fixing stuff ;P
[19:08] <sgclark> lol
[19:14] <soee> yofel: will you backport 5.6.3 or it is clivejo part?
[19:14] <yofel> his
[19:15] <sgclark> ok CI is working enough for me to focus on apps.
[19:16] <soee> :)
[19:16] <sgclark> and perhaps fixing some mergers :p
[19:16] <yofel> oh how I've missed kci blaming me for breaking mergers

[19:16] <sgclark> ikr
[19:17] <sgclark> I have not touched plasma in a long time yet I broke a bunch!
[19:18] <sgclark> so obviously webhooks are not working. but I need to move on for now. so much to do in so little time before my internship.
[19:20] <yofel> meh
[19:20] <yofel> well, we can figure that out in time
[19:22] <sgclark> it might be fairly simple to just have the job poll hourly? or something like that.
[19:24] <sgclark> why does it feel like it is repeating these mergers over and over
[19:24] <sgclark> make it stop
[19:27] <yofel> well, there's still another hundred in the queue..
[19:28] <sgclark> yes I am confused
[19:28] <yofel> it doesn't look like it's adding more though?
[19:35] <clivejo> please stop 
[19:36] <yofel> it ran out of jobs now
[19:39] <clivejo> thank Jebus!
[19:39] <yofel> sgclark: what repository did you use to try the triggers?
[19:39] <sgclark> yofel: ehm wut?
[19:40] <yofel> you said that they don't work?
[19:40] <yofel> I remember our talk with harald, just curious if you tried something somewhere?
[19:41] <sgclark> no, that talk made me dizzy, I have not tried anything.
[19:41] <yofel> ok
[19:41] <sgclark> I have been busy just getting ci to work at all
[19:42] <yofel> yeah, and you did a great job, thanks :)
[19:42] <sgclark> no sense triggering a broken ci :)
[19:51] <valorie> wooooo, lotta green!
[19:51]  * clivejo thinks valorie might be colour blind
[19:51] <sgclark> hm
[19:52] <sgclark> how now
[19:52] <sgclark> there was a ton of green
[19:52] <valorie> yes, I see some red too
[19:52] <sgclark> I am baffeled on attica
[19:52] <valorie> but instead of a scattering of green, there was a huge mass
[20:36] <sgclark> that makes zero sense
[20:49] <sgclark> hah I win
[20:50] <yofel> what was it?
[20:51] <clivejo> do we have a list of testers on Yakkety?
[20:51] <sgclark> corrupt workspace
[20:51] <yofel> ah, how does one fix that?
[20:51] <sgclark> yofel: so if you run into it saying no branch blah blah just wipe workspace on jenkins
[20:52] <yofel> the web ui button?
[20:52] <sgclark> You can within jenkins or just log in and rm /varlib/jenkins/jobs/jobname/workspace
[20:52] <yofel> ok
[20:58] <clivejo> yofel: is there any way to auto bump the FW build deps in Plasma at this stage?
[20:59] <clivejo> the staging script bumped the plasma build deps, but not the FW
[20:59] <yofel> yes, figure out how bump-build-dep-versions works and run it using do-all
[21:01] <clivejo> can I bump all the ppa versions to something more manageable
[21:01] <clivejo> ie ppa10?
[21:02] <clivejo> yofel: so you reckon we should just ignore standards version number ?
[21:02] <yofel> yes and yes
[21:03] <clivejo> have you scanned this - http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.6.3_yakkety.html ?
[21:28] <sgclark> clivejo: just an FYI I am fixing all the mergers so will be commiting to plasma repos, be sure to "pull" if you make changes. my changes will have no affect on your packages
[21:29] <sgclark> yofel: is it really necessary to have the git add remote (neon and siduction) will silly uri's?
[21:30] <sgclark> or is that left over from santa?
[21:30] <shadeslayer> silly URI's?
[21:31] <clivejo> eak
[21:31] <sgclark> git remote add neon git:/sample_url_please_replace_it_whenever_you_can/plasma/kdecoration.git
[21:31] <valorie> woah
[21:31] <clivejo> I must have forgot to clone the new repo for discover
[21:31] <shadeslayer> sgclark: where is this?
[21:31] <clivejo> and accidently pushed to plasma-discover
[21:31] <sgclark> I don't expect we will use neon as they diverged from debian
[21:31] <clivejo> how do I fix that?
[21:32] <sgclark> shadeslayer: in git-clone-all from KA, stuff santa wrote
[21:32] <shadeslayer> sgclark: because I don't see it in my pangea-tooling
[21:32] <sgclark> shadeslayer: kubuntu-automation
[21:32] <shadeslayer> oh, not in pangea-tooling
[21:32] <sgclark> nah
[21:32] <shadeslayer> not a clue then :P
[21:32] <sgclark> haha
[21:32] <shadeslayer> is that even a valid URI
[21:32] <sgclark> no
[21:32] <sgclark> but it is adding it anyway!
[21:33] <sgclark> The following packages couldn't be cloned:
[21:33] <shadeslayer> sgclark: seems to be a valid URI
[21:33] <shadeslayer> 2.3.0 :002 > URI.parse("git:/sample_url_please_replace_it_whenever_you_can/plasma/kdecoration.git")
[21:33] <shadeslayer>  => #<URI::Generic git:/sample_url_please_replace_it_whenever_you_can/plasma/kdecoration.git> 
[21:34] <sgclark> kactivitymanagerd
[21:34] <sgclark> breeze-grub
[21:34] <sgclark> breeze-plymouth
[21:34] <sgclark> clivejo: ^^
[21:34] <soee> clivejo: ping
[21:34] <sgclark> are these packaged?
[21:34] <clivejo> yeah
[21:34] <sgclark> shadeslayer: well valid it may be, it leads to nowhere lol
[21:34] <clivejo> sure you packaged them
[21:35] <shadeslayer> sgclark: needs mocking then?
[21:35] <sgclark> clivejo: um wut?
[21:35] <clivejo> maybe they need unstable branches for KCI?
[21:35] <shadeslayer> if it's in a test
[21:35] <sgclark> clivejo: I am running git-clone-all
[21:35] <clivejo> have you added them to the package list?
[21:36] <clivejo> they are frameworks
[21:37] <sgclark> ehm what?!
[21:38] <clivejo> they are framework packages?
[21:38] <sgclark> no they aren't!
[21:38] <sgclark> plasma
[21:38] <sgclark> they look new
[21:39]  * sgclark looks
[21:42] <yofel> sgclark: leftover from santa because nobody ever set a proper URL
[21:42] <yofel> I personally like the remotes, but the URLs should be fixed
[21:43] <sgclark> ok
[21:44] <sgclark> we need to add debian as well
[21:44] <sgclark> clivejo: those 3 did not make my transfer from debian, running it now
[21:44] <sgclark> they will need to be packaged
[21:47] <shadeslayer> yofel: btw regex question for you
[21:47] <sgclark> will need to use debians package to start as it looks like we never have packaged. must be new
[21:47] <shadeslayer> yofel: is it possible to not match foo.iso but not foo.iso.zsync or bar.iso
[21:47] <soee> clivejo: i am downloading YY daily of you want me to test P 5.6 in VB 
[21:51] <shadeslayer> yofel: nvm figured it out :P
[21:51] <yofel> shadeslayer: so not match the first one but match the other 2? 
[21:51] <yofel> well then
[21:51] <shadeslayer> yofel: (.*[^.*.zsync||^.*latest.iso])
[21:51] <shadeslayer> much fun :P
[21:51] <yofel> indeed
[21:52] <shadeslayer> actually, matches zsync
[21:52] <yofel> I'm too tired for this, sry
[21:53] <shadeslayer> np
[21:54] <valorie> {{{{{{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}}}}} to yofel
[21:55] <valorie> and sgclark, and clivejo, and shadeslayer
[21:55] <valorie> y'all rock
[21:58] <shadeslayer> oh jesus
[21:59] <shadeslayer> yofel: .*(?<!iso.zsync|latest.iso)$
[21:59] <shadeslayer> that works :P
[22:03] <mparillo> https://xkcd.com/208/
 Sorry Scarlett. My head isn't in packaging today
 I need sleep but my mind won't let me. Have to get up again in four hours
 Np. Take some time off.
 Go sleep please!
 Tell my body!
 I know the feeling
 I'm nervous about tomorrow
[22:05] <valorie> what's up tomorrow?
 Its a suicide awareness walk
 And then on to a funeral at 10am
[22:06] <sgclark> ekkk :(
[22:06] <valorie> oh dear
[22:07] <valorie> my sympathy and regrets for your loss
[22:07] <valorie> I lost my niece to suicide
[22:07] <valorie> it is devastating
 The walk is a planned event
[22:11] <valorie> I'm glad there is more awareness now
 Start off walking in pitch dark at 4am
 Carrying candles and torches
[22:11] <valorie> instead of it being a hushed subject everyone avoids
 And they walk into the day break of the new day
 Expecting a couple thousand at it
[22:12] <valorie> sounds tremendous
[22:14] <shadeslayer> valorie: :(
[22:14] <shadeslayer> valorie: *hugs*
 http://dil.pieta.ie
[22:16] <valorie> thank you shadeslayer
[22:17] <valorie> I love that name Darkness into Light
 Its symbolic
[22:22] <soee> is there someworkaroudn for not working button "Next" on first installer step ?
[22:23] <soee> *second
[22:23] <sgclark> um that sounds like a non functional installer
[22:24] <soee> yup :/
[22:25] <sgclark> we generally do not touch ubiquity
[22:25] <sgclark> but somehow get broken often
[22:25] <sgclark> dunno
[22:33] <soee> an why the hell there is some red trash icon with black check sign on it before section title ...
[22:36] <sgclark> dunno that either
[22:41] <valorie> ok, gotta get some sun on this beautiful day
[22:45]  * sgclark is jealous
[22:45] <soee> yofel: ping
[22:45] <yofel> hm?
[22:46] <soee> if we go to live session - all plasma configuration files are created dynamically ?
[22:46] <soee> or they are predefined ?
[22:46] <yofel> plasma maybe yes, but some things are pre-set
[22:47] <soee> in one file  we can manipulate this small folderview widget size/position
[22:47] <yofel> actually, not plasma either. The folderview isn't
[22:47] <yofel> Do you know if that's fixed in plasma 5.6?
[22:47] <soee> nope :/
[22:48] <soee> * i dont know this
[22:48] <yofel> Because if I add a folderview on my 5.5 session here, then the folderview is too small as well :(
[22:48] <yofel> so that has nothing to do with the live session, just plasma
[22:48] <sgclark> ahhh
[22:48] <sgclark> I tried desperately to sort that out at release. the docs for plasma theming is bad
[22:49] <soee> well i thought i test what clivejo packaged but installer does not work so i cant do much :/
[22:49] <yofel> right, I was lost as well. Until I tried adding a folderview on my notebook, and realized that we probably never had to set a size in the past
[22:54] <soee> ill try to ask someone on #plasma after weekend
[23:18] <mparillo> soee: I think the red trash ubiquity icon has been there since the switch to plasma 5. I think it means you do not have a working Internet connection.