=== rdieter_laptop is now known as rdieter [06:18] Good morning. [07:42] Riddell: did you not clean up staging after 5.1? [07:42] why was that in staging anyway when it didn't land in next? [07:45] I've added a link to our notes to the Bof page [07:45] and added a note in the notes about sune vorela wanting to meet with us in the morning [07:46] * valorie goes back to watching a very old doctor who ep [08:00] apachelogger: why was what? [08:03] Riddell: kf5.1 is in next-staging and I do not compute why === vinay is now known as Guest20599 [08:20] hmmm yeah what is the deal with next, some of the versions are 5.1.0 and some are 5.0.1 and none made it to next ppa [08:21] * sgclark is going to need gallons of coffee for this schedule [08:23] hmm I'll take a look [08:42] sgclark: it's because 5.1 should not have been in next-staging as it never was supposed to go to next and when it was then uploaded to the archive staging didn't get cleared which didn't help either [08:42] * apachelogger thinks we might have to get more staging repos soonishy [08:53] apachelogger: ok, I guess I don't understand why it wouldn't go to next, is it a beta release or something? [08:55] sgclark: no, because frameworks go to the archive [08:55] well, until release or as long as we get feature freeze exceptions anyway ^^ [08:57] so it needs to go to ninja staging to prep for archive or ? [08:58] I do not think we have a PPA were it should have been preped, ninjas would have been more appropriate though [08:58] Ok, my apologies then. [08:58] not your fault really [08:58] muchos complicated [08:59] * apachelogger puts figuring out stage ppas on todo for CP [09:00] Riddell: apachelogger: any idea why the mix of 5.0.1 and 5.1.0... seems that would bugger up depends... [09:02] sgclark: that should be plasma and kf5, no? [09:02] they don't have matching versions === yofel_ is now known as yofel [09:03] yofel: yep that is it, thanks [09:05] as I said yesterday... good thing upstream decided against year.month versions, that'd have been way too reasonable :P [09:05] isn't that going to be used for the applications? :D [09:06] kubotu: order jaegermeister for shadeslayer [09:06] * kubotu slides a glass of Jägermeister down the bar, shouting 'Jogdzeit is!'. [09:06] I really think this used to be different [09:07] ... [09:08] when "jaegermeister" then [09:08] "throws out cough syrup! whoop! whoop!" [09:09] it's a good thing the bar plugins has like 300 forks all over the place because I cannot be bothered to use the feature I built to override and add random stuff [09:14] Riddell: I am not coming today BTW, feel quite lightheaded and sick :( [09:15] shadeslayer: I did tell you to rest yesterday! [09:16] but oh no, like the alpha male you are, you came in and did useful things all day long! [09:16] Yeah :( [09:16] Should have listened [09:16] Did not get a wink of sleep last night too [09:17] shadeslayer: you can watch the independence debate on bbc iplayer, salmond kicks darling's eyebrows into cedeing to become a new state [09:17] Heh === Riddell changed the topic of #kubuntu-devel to: Kubuntu - ¡My eyebrows are going to cede! | https://trello.com/kubuntu [09:22] apachelogger, sgclark: kf5 5.1.0 is not in next ppa because it is in the utopic-release archive [09:22] yes [09:22] right. cleared up thanks [09:22] Riddell: mind reserving a bof room for Kubuntu dev days at Akademy [09:22] Riddell: it shouldn't be in next-staging though [09:23] as that is staging for next [09:23] Riddell: apachelogger: safe for me to delete from staging ? [09:23] sgclark: yeah, be careful though I think there's other stuff lingering in there [09:23] e.g. I think usbcreator should have a staged build [09:24] ok [09:24] shadeslayer: we have one do we not? [09:24] sgclark: yes but there's stuff in staging we want kept [09:25] I did not put it on the wiki [09:25] sgclark: extra-cmake-modules that shadeslayer uploaded, although it breaks stuff in /etc [09:25] so maybe delete it if it causes problems [09:25] Riddell: I also noticed mkspecs are being installed in wrong dir again [09:25] I would have fixed it today :( [09:26] sgclark: ecm again [09:26] I uploaded a plasma-workspace [09:26] shadeslayer: is ecm in archive or just staging? [09:26] I am only going to delete 5.1.0 frameworks [09:26] sgclark: right so just delete that extra-cmake-modules [09:26] apachelogger: staging [09:26] ok [09:26] https://git.reviewboard.kde.org/r/119901/ [09:26] For full context [09:27] yeah, drop it from stage -> bad package :P [09:27] tier1 branches should be reverted to building condition with present pkg-kde-tools [09:27] Riddell: I am expecting mail today btw [09:30] Riddell: kde-runtime 4:4.13.97 in next staging? [09:30] sgclark: la la la, delete that [09:30] lol [09:31] :S [09:32] http://mail.kde.org/pipermail/kde-frameworks-devel/2014-August/018572.html woo kdepimlibs split 30 different ways [09:32] shadeslayer: sorry about yesterdays rant ... was not meant to be at you [09:33] thy shaltn't rant at my shadeslayer [09:33] he's not well, plus only I get to rant at him [09:33] shadeslayer: you uploaded a few 5.1.0-0ubuntu2 frameworks, are those needed? [09:34] apachelogger: wont happen again, and it was more a rant about ubuntu installer [09:34] kdeuser56: its alright :) [09:34] It is a bug [09:34] * apachelogger even knows where the bug is :P [09:34] Someone more knowledgeable needs to look at it [09:35] apachelogger: oh? fix it ! [09:35] enotime [09:35] Sddm init script ? [09:35] That's the only other place I can think of ? [09:36] sgclark: nuke em [09:36] ok [09:36] shadeslayer: yeah [09:36] shadeslayer: it doesn't handle text cmdline IIRC [09:37] or well, to put it as usual: it should just replicate what lightdm does [09:40] :) [09:40] kdeuser56: I will look at it tomorrow then [09:40] :-)) [09:41] apachelogger: Riddell: ok so next ppa, frameworks in archive don't need to be in next ppa correct? [09:41] right [09:41] ok removing [09:41] yeah, plus the version in next is outdated anyway :) [09:41] they should all be in the archive so you can remove them all from the ppa [09:41] Riddell: btw, since you were asking about usbcreator ... they are in next, except usbcreator is currently outdated [09:41] feel free to test the autobuild waiting in staging [09:42] if good please move to next [09:42] apachelogger: and thanks again for pointing me to the source yesterday, I have modified the patch and it works as expected [09:42] sweet [09:43] apachelogger: I have updated your diff for kcrash framework, but I guess it does not make much sense yet, since drkonqi needs a patch too, right? (the button you can check/uncheck) to report the problem [09:44] apachelogger: even kubuntu-driver-manager is in next? [09:45] kdeuser56: yep [09:45] Riddell: might be, or maybe that was waiting on qapt/kauth/polkit [09:45] apachelogger: which package is that patch in? I'll happily try to apply it to the frameworks package, compile and test [09:46] Riddell, sgclark: shouldn't we also nuke plasma5.0.1 from staging? [09:46] it is in ppa so i am thinking yes [09:46] apachelogger: i though kde-runtime since it contains a drkonqi binary but it does not seem like that [09:46] kdeuser56: kde-runtime in 4.x, plasma-workspace in 5.x [09:46] or maybe plasma-desktop for 5.x [09:46] workspace says dpkg [09:47] http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kde-runtime/files/head:/debian/patches/kubuntu_drkonqi_whoopsie_integration.patch [09:47] shadeslayer, yofel: when are we moving the patch list page to qa.kubuntu? [09:47] apachelogger: ah thanks, i know why i did not find it: because i am still on a saucy box [09:48] i know EOL [09:48] apachelogger: someone just needs to set it up [09:48] never going to happen then :'< [09:49] :p [09:49] hm [09:50] btw: does someone know an apt-file equivalent that can search source files? (like for exmaple if I wanted to find the package that contains kcrash.cpp) [09:50] shadeslayer: did you change the -j'ness of ctest in pkg-kde-tools? [09:50] either that or threadweaver has a new test that doesn't like -jN a lot [09:50] Nope [09:50] actually I think the test is crap [09:50] wow our bindings are screwed, smoke all sorts of broken and then the new perl adds to perl's issues [09:50] 'Morning folks [09:51] all for bindings that nobody much uses :( [09:51] * shadeslayer puts on some music [09:52] Riddell: baloo-widgets5 needs a review when you have a moment [09:53] shadeslayer: https://www.youtube.com/watch?v=oAPjTHA19Kw [09:53] shadeslayer: also I told you to go back to sleep :@ [09:53] bugsies https://bugs.kde.org/show_bug.cgi?id=338568 [09:53] KDE bug 338568 in general "master test not compatible with ctest -jN" [Normal,Unconfirmed] [09:57] I am in bed :( [10:01] sgclark: oh yes, what is it you're packaging it for? [10:02] sgclark: are you becoming a test suite maestro? cos that's still mostly black magic to me [10:02] Riddell: I have been working on packaging some frameworks branches eg kde-baseapps etc and the baloo-widgets we have done is very old. [10:02] Riddell: yes I am studying the mysteries of autopkgtests [10:03] well done [10:03] sgclark: I think these packages will need to go into experimental rather than next [10:03] else apachelogger will get grumpy [10:03] Riddell: yeah [10:03] I also had to package a snapshot of kio [10:04] Riddell: maybe we should make next-experimental? === davmor2_ is now known as davmor2 [10:05] That sounds like a good idea to me [10:06] pkg-kde-tools 0.15.15 in staging... story on this? [10:06] kick it out [10:06] ok [10:07] ok staging mostly clean. last bit of stragglers need to be looked out to see if they shoud be there or somewhere else. [10:09] Riddell: baloo 4:4.13.97 in next? :) [10:09] sgclark: if you look at the ppa page, anything that's dark-grey can be deleted [10:10] * yofel wonders if we could write a janitor for that [10:10] yofel: ok ty [10:13] sgclark: um, you can probably delete that [10:21] feed branches-next had 20 updates, showing the latest 6 [10:21] sgclark: baloo-widgets comments: I tidied up some formatting ↑ [10:21] baloo-widgets5 -> rename to baloo-widgets-kf5 [10:21] why comments in "No tests were found!!! I guess tests are not ready... Uncomment when they are" but then tests are in "testsuite.xsession" [10:23] Riddell: testsuite.xsession will not get called while it is commented. [10:23] sgclark: so should it not just all be deleted or do you expect it to be used in future? [10:24] Riddell: I would think tests will be functional in the future... one would hope. Can remove for now to avoid confusion if you like [10:24] sgclark: if it looks like they will be functional in future then great, keep them [10:26] Riddell: yeah the tests are there and seem to get built but do not seem to be called.. dh_auto_test results in the No tests found [10:27] Riddell: I can fiddle with it to see if I can manually call them [10:28] sgclark: leave it for now and I'll ask vishesh what he expects them to do when he wakes up [10:28] ok [10:38] debfx: can you give me a summary of your understanding of the smoke issue? [10:41] any thoughts on how to fix the test https://launchpadlibrarian.net/183197397/buildlog_ubuntu-utopic-i386.kcoreaddons_5.1.0%2Bgit20140826.0941~9a623f9_FAILEDTOBUILD.txt.gz [10:44] send in a crack debugging coder? [10:50] rmdir: failed to remove ‘debian/man’: No such file or directory [10:50] /usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk:80: recipe for target 'cleanup_manpages' failed [10:50] I have a feeling like pkg-kde-tools is still broken [10:50] oh no [10:50] that's ignored [11:09] I am a bit surprised by the amount of test fail due to integration issues [11:10] makes me doubt the usefulness of running tests to begin with [11:36] apachelogger: kubuntu-driver-manager : Depends: libqapt3 but it is not installable [11:36] do you know where I can find that? [11:39] staging [11:42] apachelogger: nothing in next-staging or staging PPAs with libqapt3 [11:42] Riddell: someone deleted it then [11:42] apachelogger: usb-creator-kde is just as broken in qt5 version with scary dbus errors, did it work for you? [11:42] which is another problem with how we stage things right now [11:42] Riddell: that's from the backend [11:43] but yeah I have seen it last I used it [11:43] so it's pretty much useless :( [11:44] apachelogger: do you know who might have a copy of the missing libqapt3 packaging? [11:45] I think launchpad should [11:45] Riddell: the c++11 feature definitions in qglobal.h have been shuffled around. now the smokegen preprocessor activates Qt c++11 features but it can't parse them. [11:45] for some reason smokegen thinks "# if defined(__GXX_EXPERIMENTAL_CXX0X__) || __cplusplus >= 201103L" evaluate to true. [11:45] Riddell: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next-staging/+packages?field.name_filter=qapt&field.status_filter=&field.series_filter= [11:45] the "|| __cplusplus >= 201103L" part has been added with the latests Qt snapshot. [11:46] without the debian patch in smokegen it works fine. [11:47] debfx: you are truely elite [11:48] debfx: so smokegen_load_system_defines.diff is to blame? [11:51] possibly. at least you only hit the bug when that patch is applied. [11:51] I haven't dug deeper than that. [11:52] debfx: do you know the fallout from removing the patch? [11:53] * Riddell lunches [11:54] could break the build on some architectures. [11:55] what part of the build tooling uses debian/tests? [12:47] the jenkins ruby api is perfectly horrible [12:47] * apachelogger shivers [12:47] Is Project Neon Kubuntu or not? (See the discussion in #kubuntu) [12:48] * apachelogger aint in #kubuntu [12:49] is that the question, or is the *real* question "do we offer support for it in #kubuntu"? [12:49] tsimpson: more a line of who supports the project provided resources on kde.org [12:49] specfically in this case the neon.iso from the kde.org website [12:49] where is the best place for a user to get help using/developing against that iso [12:50] support is a strong word there :P [12:51] either #kubuntu or #project-neon I'd say [12:51] there's a neon channel, not that I am in there, so I guess this here channel would be most appropriate [12:51] Neon is strongly linked to Kubuntu [12:51] sure, that's why support is a strong word, you get a support for the base system, you wouldn't for all the neon bits [12:52] for the neon bits one may get *help* if there's a specific question to do with how to use it, but due to the nature of neon one really shouldn't talk about support with regards to it ^^ [12:52] #project-neon looks good [12:52] nice one [12:52] I suppose if no one can help in #kubuntu or here, then it's #project-neon or just #kde [12:53] not a whole lot of supporters in #project-neon [12:53] but I don't have a problem with people asking general questions in #k [12:53] too late he went [12:53] sure, but the question remains :) [12:55] if someone's using Neon and has a problem, where it' clear that it's a Neon-specific problem, then they'd get better help elsewhere [12:56] it looks like pointing people wanting to develop against neon/use the kde resources the #project-neon looks like a good starting point [12:58] dpkg -L libqapt2-runtime [12:58] useful info [12:58] thanks [12:59] hmm [13:01] Riddell: This would not have happend with Konversation. [13:03] oh? [13:04] well feel free to package konversation frameworks branch and put it in the seed [13:04] why do we need the frameworks? [13:05] just a nice excuse [13:05] Riddell, shadeslayer, yofel: thoughts on jenkins for CP orchestration? [13:05] what would jenkins do? [13:05] and which jenkins install? [13:06] our own jenkins [13:06] it would poll our packaging branches for changes and trigger builds accordingly [13:06] possibly also do daily builds in orderly fashhion [13:06] isn't that what launchpad build receipies should do? [13:07] yes [13:08] except they require bzr for everything, are not dynamic enough as you cannot define arbitrary stuff, have no nice status pages, cannot aggregate tests data (lintian etc.), sometimes take long to build, take forever to build.... [13:09] and where would the builds take place? [13:09] Riddell: launchpad [13:11] seems interesting [13:11] the way I imagine this right now is that the actual build job would do what our neon builder does right now except jenkins takes over the trigger part... the jobs themselves then get the sources, put them together in a source package, upload to launchpad and then poll launchpad every other minute until the build either fails or succeeds [13:11] on success we could then go ahead and grab the build log and tear out lintian data, symbol data and whatnot to make our jenkins job fail accordingly [13:18] I'm fine with jenkins for that but I've never configured it so can't help [13:19] * apachelogger puts an lxc in another lxc [13:22] apachelogger: libqapt, kubuntu-driver-manager and kubuntu-debug-installer seem to be working, I'll copy to next ppa and seed [13:22] usb-creator I'll just remove from the seed I guess [13:22] ok [13:27] broken beyond salvation? [13:28] yofel: dunno but it gives me scary dbus errors and hasn't worked for me for ages [13:28] true, go ahead [13:34] since few days i have a strange issue - not sure if it is keyboard or system problem: for some reason from time to time apps stops to recieve keyboard input, i have to switch to other app than back to previous and all works fine [13:34] oh my [13:34] W: Failure trying to run: chroot /var/cache/lxc/utopic/partial-amd64 mount -t proc proc /proc [13:34] apparently you mustn't put an LXC in an LXC [13:34] what madness is this [13:35] if all you need is a container "lxc.aa_profile = unconfined" might help [13:45] looking at all the gtk3 themes I think orion-gtk-theme is the one that fits in nicest with breeze [13:45] * Riddell seeds [13:50] Riddell: aren't we getting a breeze theme for 5.1? [13:52] shrug, maybe for qt5, no sign of a gtk2/3 or qt4 one yet that I know of [13:54] curious, I thought I saw commits somewhere [13:54] maybe I've not been following [13:55] but for now better to go with something than default uglyness [13:55] Riddell: should be implemented upstream though? ... setting as default or whatever [13:55] yofel: apparently it doesn't care much for that [13:56] hm [13:56] not sure then [13:57] apachelogger: um, how? [13:57] Riddell: dunno, somehow we set the gtk2 theme, so somehow we should set a gtk3 theme [13:57] unless the upstream intention is to have ugly gtk3 in which case we shouldn't really do anything about it downstream [13:58] apachelogger: what makes you think we set a gtk2 theme [14:00] was pitched to me way back when as a feature and why we want to use qtcurve [14:00] alas, I personally never have seen it work in neon xD [14:00] right, qtcurve is recommended but nothing sets it for use [14:00] Riddell: at any rate, breeze needs an upstream runtime check for the gtk3 theme or something [14:01] randomly picking a theme without also suggesting it as the upstream default pick for gtk3 seems inconsistent [14:01] runtime of what checking for what to do what? [14:01] cmake runtime dependency check for whatever gtk3 theme upstream wants as gtk3 theme [14:02] who wants to be the co-contact for plasma5 ISO? ScottK? shadeslayer? [14:03] yofel: http://s3hh.wordpress.com/2014/03/31/nested-lxc/ [14:03] gives me a headache [14:05] apachelogger, Riddell: maybe some should write a mail to hugo pinheiro about his intentions regarding the theme situation [14:05] jens would be the dude these days [14:05] not heard from him in a bit [14:06] and he likes to use forums which is a bit non-hackery [14:06] Riddell: yeah but hugo pinheiro implements the theme ... so I think it would better to ask him, because he can tell if the time is enough to patch the gtk themes too [14:07] there's no such person, you are mixing up two names there :P [14:09] apachelogger: lol ... sry you are right [14:10] apachelogger: so you see, in #plasma, upstream has no recommendation for gtk3 and is not very sure about gtk2 [14:10] apachelogger: Hugo Pereira Da Costa ... now I got it [14:12] Riddell: yeah, so that's a bug :P [14:12] upstream is a bug? [14:13] Riddell: not having a theme [14:13] look at it this way, if I install plain kde from source I have shitty gtk [14:13] yep [14:14] so instead of making it not have shitty gtk in kubuntu we should make it not have shitty gtk upstream [14:14] Riddell: I think hpereira on #oxygen channel should be him [14:14] what with designer involvement and our visual experience being the one from upstream [14:15] kio ftbfs :'< [14:16] many a new symbols have been had [14:19] #MISSING: 5.1.0a+git20140826.1344# _ZN3KIO7CopyJob13aboutToCreateEPNS_3JobERK5QListINS_8CopyInfoEE@Base 4.96.0 [14:19] why this aint good now is it [14:22] so much for upstream ABI checks [14:23] There are none [14:24] Someone needs to setup abi compliance checker [14:25] ABI Check as a Service [14:25] well, do that then? AFAIR that has been planned for ages [14:25] ACaaS [14:25] Yeah [14:25] anyway, someone go complain [14:25] :p [14:32] it's a good that I started CP testing isn't it :P [14:33] we would've caught that in the usual process anyway, but this has it's nice edge to it [14:33] *its [14:35] yofel: no we wouldn't [14:35] we would have after kf5 went out [14:35] because until we got to kio even building it would have taken longer than the embargo :P [14:35] we would have after kf5 tars are out, or does it not have pre-release testing? [14:35] yofel: it does, alas a short one I think [14:36] hm, right [14:37] uh nice, lxc nesting with the cgroup mount stuff works nicely [14:41] and lxc-start-ephemeral works as well [14:41] whoo [14:53] ok this is spooky, colin has made the .install files in perlqt be perl scripts [15:17] !testers | beta 1 candidates! [15:17] beta 1 candidates!: Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket for information [15:24] Oehh, fancy :) [15:27] hope nobody asks me for beta2 Plasma 5 info because I have no clue where it is [15:28] beta2 plasma 5? [15:29] oops beta1 [15:29] wasn't that like back in June? [15:29] that was plasma beta, now we're onto ubuntu betas :) [15:29] alpha was I think [15:29] BluesKaj: http://cdimage.ubuntu.com/kubuntu-plasma5/ [15:29] oh [15:30] Oh. I can break from beating my head against autopkgtest and test. Where might I find this ubuntu beta to test? [15:33] Riddell, the last plasma image from a few days ago was too unstable to run on my laptop/intel graphics...hope this one runs at least [15:35] and had no power control whatsoever...brightness etc was totally maxed [15:37] right, who has a linkedin account? [15:37] sgclark: http://cdimage.ubuntu.com/kubuntu-plasma5/ [15:37] then report results on http://iso.qa.ubuntu.com/qatracker/milestones/322/builds [15:39] Riddell: I have linkedin account [15:48] sgclark: I just set up a kubuntu "company" on it [15:48] sgclark: can you see if you can find it and follow it? [15:48] you bet [15:50] kubuntu 14.10 kde 4.14 plasma 5... after installed plasma 5 power management configuration module not be loaded... The power management service apears not to be running... ..system seetting startup and shutdown.. background services.. says power management is running... but under power management it is gray out [15:51] Riddell: could you change "tester56" to "kdeuser56" in the tester call? [15:51] kdeuser56: Tm_T if your dude for that sort of thing [15:51] Tm_T: ↑ [15:51] MichaelP: yes I've come across that, not investigated it yet [15:52] MichaelP: what did you upgrade from? [15:53] fresh install of 14.10 lastnight [15:53] MichaelP: fresh install of plasma 4 or plasma 5? [15:53] 5 [15:54] yep, same as I saw [15:54] now I wonder where we track bugs in plasma5 ISO [15:54] apachelogger: got a policy for that? ↑ [15:56] http://i.imgur.com/D4c3QnM.png [15:58] MichaelP: yep, sorry I doubt it'll be fixed for beta 1, but if you want to be super helpful you can test the beta 1 candidates :) [15:58] Riddell, is that plasma 5 image different than the one from 4 days ago ? [16:01] Riddell: downloading kubuntu-plasma5/daily-live.... 26-Aug-2014 14:41 right now [16:02] was not a plasma image.. was utopic lde live... from 3 weeks ago... then added ppa [16:09] MichaelP: if you can test this and report back on http://iso.qa.ubuntu.com/qatracker/milestones/322/builds it would be much appreciated :) [16:12] Riddell: will do [16:24] bah, everyone says hootsuite is a better social media management tool but seems very limited unless you want to pay a tenner a month [16:25] yeah [16:25] what all are you trying to manage Riddell ? hootsuite sucks unless you are some giant corporation, and even then I heard people complain [16:27] nixternal: I want to be able to type an announcement once and it to go out on the facebook page, twitter account, g+ and linkedin [16:29] ahhh, yeah then there isn't much out there that will doo all of those at the same time. then again I haven't really looked into it [16:29] I know with WordPress at least, you can do that, but that's about the only one I know [16:30] now that would be awesome in the new site [16:31] if someone finishes the new site [16:31] yeah wordpress your best bet [16:32] WordPress Jetpack does all of that [16:38] ovidiu-florin: let's get that! ↑ [16:48] ok I think I got it set so that hootsuite can post to g+, linkedin and twitter, and twitter posts onto facebook [16:48] now I need some news to test it all [17:11] Riddell: http://paste.ubuntu.com/8151581/ when building kcrash [17:11] Riddell: That link you gave me... I downloaded Kubuntu Plasma 5 i386... burnt to dvd.. booted into desktop... nothing is plasma 5.. looks just as kde 4.14 [17:11] Riddell: note the "make: *** [debian/dhmk_binary] Error 2" [17:12] Hmm, I am in Live ssession of that dvd and it looks like plasma5 to me [17:13] Somehow your DSC disappeared kdeuser56 [17:13] However, unfortunately ythe Power management is broken [17:13] sgclark: from here http://iso.qa.ubuntu.com/qatracker/milestones/322/builds [17:13] shadeslayer: ah right damn, thanks a lot [17:14] That seems odd BTW :p [17:15] MichaelP: yeah [17:15] MichaelP: did you create a bug report for the Power Management non-functionality? [17:16] i downloaded Kubuntu Plasma 5 i386 burnt to dvd booted into live session and get kde 4.14.0 [17:16] no [17:16] O.o [17:16] kded5 is known to cause a lot of headache [17:17] odd, I am amd64, but that should not make a diff? definitely plasma5 on mine [17:17] it plasma 5 had no power management problem in 14.10 with kde 4.13... after kde 4.14 is when it started [17:18] MichaelP: what makes you say its KDE 4? [17:19] shadeslayer: im just saying kde 4.14 with plasma5 was when power management problem started for me [17:19] kde 4.13 with plasma i had no power management problem [17:21] now is there a config file to edit by hand to screen don't go black [17:22] MichaelP: please make a screenshot and upload that [17:22] MichaelP: only plasma5 bits on http://cdimage.ubuntu.com/kubuntu-plasma5/daily-live/20140826/utopic-desktop-i386.manifest [17:23]