[02:38] <ScottK> Now that mesa 10.3 went in, we should add a release note that kwin/display affects bugs should not be reported upstream.
[06:28] <lordievader> Good morning.
[08:54]  * Riddell does the 4.14.1 in utopic dance
[08:54] <Riddell> and kf5 5.2.0 nearly in
[08:54] <Riddell> jings that was more effort than it should have been
[08:54] <Riddell> SourBlue: you say the plasma5 image isn't fixed? :(
[08:58] <Riddell> I really wish I had time to care about Jung-Kyu Park's issue of korean fonts, but it just hasn't reached the top of my todo list yet :(
[09:00] <SourBlue> Riddell: I don't think it is
[09:00] <SourBlue> dind't work for me but the sddm.conf isn't changed at all
[09:01] <SourBlue> btw. my desktop starts on tty8 and tty7 stays the same
[09:04] <Riddell> foo
[09:05] <apachelogger> you'll want to make sure that plymouth has quit by the time sddm tries to start, otherwise it will probably not be able to use tty7
[09:06] <SourBlue> someone said it's a vm problem do you know something about that?
[09:06] <SourBlue> vm only*
[09:06] <apachelogger> vbox?
[09:06] <Riddell> needs testing on real hardware
[09:06] <apachelogger> do not bother with vbox
[09:06] <apachelogger> use kvm or real hardware or vmware
[09:07] <apachelogger> vbox is just always broken beyond comprehension before release
[09:07] <SourBlue> I mean Virtual Machines
[09:07] <apachelogger> well, *always broken
[09:07] <SourBlue> I use VirtualBox
[09:07] <apachelogger> yes
[09:07] <apachelogger> don't use it :P
[09:07] <apachelogger> it's rubbish
[09:08]  * SourBlue thinks about what he just said
[09:08]  * SourBlue gets that vbox and VirtualBox are the same
[09:08]  * apachelogger killed kubunt-ci jenkins by trying to make it produce a graph  -.-
[09:11] <SourBlue> does vmware run under linux?
[09:14] <SourBlue> or you tell me how to use kvm :D
[09:15] <Riddell> tell me too please, I've not worked it out
[09:16] <apachelogger> http://blog.liw.fi/posts/kvm-for-ubuntu-iso-testing/
[09:17] <soee> Riddell: one user on g+ asked about 4.14.1 2 days ago, they are in 14.10 but how about 14.04 ?
[09:19] <SourBlue> apachelogger, thank you that works!
[09:19] <SourBlue> Live Session still not working but the vm is running :D
[09:19]  * SourBlue uninstalls VBox
[09:23] <Riddell> soee: I honestly don't know but I'll find out today
[09:24] <soee> Riddell: the only thing i want to know atm is if it is or not available for 14.04 :)
[09:24] <soee> im on 14.10 so dont know about 14.04
[09:26] <SourBlue> soee: if what is available?
[09:28] <Riddell> soee: seems like it hasn't been packaged at all
[09:29] <Riddell> yeah, on to do list then
[09:33] <soee> Riddell: ok thank you
[09:33] <soee> SourBlue: i was asking about 4.14.1 packages for 14.04
[09:34] <SourBlue> Do you know whats the difference between "apt" and "apt-get"?
[09:38] <debfx> SourBlue: man apt
[09:38] <debfx> "DIFFERENCES TO APT-GET"
[09:39] <SourBlue> Thank you!
[09:39] <Riddell> apt is new and shiny, all the cool kids use it
[09:39] <Riddell> but I get confused when I want to do something that isn't available in apt and I need to go back to apt-foo
[09:41]  * SourBlue is a cool kid
[09:47] <Riddell> :)
[09:53] <Pali> Riddell: just to note that I applied these changes for backporting 4.14 to precise: http://bazaar.launchpad.net/~pali/+junk/kubuntu-automation/revision/438
[09:56] <Riddell> thanks Pali, I'll get to it in a bit
[09:56] <Pali> ok
[10:37] <apachelogger> Riddell: nm-qt is still in bzr?
[10:37] <apachelogger> ah, no found it
[10:37] <apachelogger> curious
[10:40] <Riddell> ?
[10:47] <apachelogger> Riddell: it's not a plasma thing is it?
[10:48] <Riddell> half plasma, libnm-qt and libmm-qt want to become frameworks but are plasma for now, plasma-nm will probably stay as part of plasma releases
[10:49] <apachelogger> I see
[10:49] <apachelogger> this reminds me of my concern on what happens to the git repos if a thing changes affinity from plasma to frameworks :S
[10:50] <Riddell> debian git?  we ssh in and do mv plasma/foo frameworks/foo
[10:51] <apachelogger> but then people need to update their remotes
[10:51] <apachelogger> it's fishy I say
[10:52] <Riddell> I'm sure we can just tell any packagers to do a fresh clone
[10:53] <apachelogger> changing remotes is faster
[10:53] <apachelogger> it still requires one to do it
[10:53] <apachelogger> pointless work if you ask me
[11:10] <sgclark> morning
[11:22] <soee> hiho sgclark
[11:22] <soee> its 13:22 :D
[11:23] <sgclark> hehe 4:22  am here
[11:23] <SourBlue> soee: are you german?
[11:25] <soee> :)
[11:39] <BluesKaj> Howdy folks
[11:39] <sgclark> hiyas
[11:39] <BluesKaj> hi sgclark
[11:41] <BluesKaj> was about try plasma5 again , but read the email from valorie ...oops still not ready
[11:42] <soee> what is not ready ?
[11:42] <BluesKaj> plasma5
[11:43] <soee> BluesKaj: yes but what exactly ? :)
[11:46] <BluesKaj> soee, http://paste.kde.org/ppyw6rujb
[11:46] <apachelogger> #unsupportedinstallmethod
[11:47] <sgclark> hmm, yeah that is sddm , however, it was fixed, not sure why it would happen
[11:47] <sgclark> now
[11:47] <apachelogger> I think that is more than sddm to be honest
[11:48] <apachelogger> the entire add-ppa-get-things thing is not exactly thought through
[11:48] <sgclark> yeah sddm and plasma-framework broken caused it for me, but was fixed, so unless she is pulling in old packages somehow
[11:49] <sgclark> anyway, plasma5 working fine for me
[11:50] <apachelogger> it would for valorie if someone where to like document how to do this
[11:51] <apachelogger> or well, not make it fail when one does not do everything right
[11:53] <soee> BluesKaj: ah no idea, i have Plasma 5 installed in my dell since 3 or more months
[11:53] <soee> works fine for me
[11:57] <BluesKaj> not here , caused all kinds of troubles, no run comand/krunner, links , widgets etc and the icons/look wasn't to my taste and there were no alternatives to the breeze theme at the time
[11:58] <BluesKaj> maybe it's better now lookwise
[12:08] <apachelogger> maybe you should report bugs instead of whining
[12:09] <BluesKaj> whoa :)  , too many bugs to be useful apachelogger
[12:10] <apachelogger> nothing is ever going to change then.
[12:10] <sgclark> we cannot fix what we are not aware of
[12:15] <BluesKaj> ok < i won't mention plasma5 again, since I have no desire to use it anyway
[12:17] <Riddell> meh, sddm will be the end of us
[12:17] <Riddell> I always said it
[12:22] <apachelogger> nono I said it :P
[12:36] <kbroulik> Mirv: ping
[12:36] <soee> BluesKaj: i like where P5 is going, im waiting for 5.1 that is going to be released september i think
[12:37] <soee> you should give it a try then if current version is not enough :)
[12:38] <BluesKaj> soee, are thee any other themes besides the default breeze available?
[12:38] <BluesKaj> there
[12:38] <soee> when it comes to themes, 98% of the time is see only panel so the default is enough, no need to change it :)
[12:38] <Riddell> soee: I'm releasing the beta today
[12:38] <soee> BluesKaj: i think all/most from plasma 4 should be compatible
[12:38] <soee> Riddell: 5.1 ? :o
[12:39] <kbroulik> soee: you cannot use plasma 4 widgets in 5 because the architecture is completely different
[12:39] <kbroulik> soee: yes 5.1 :) 
[12:41] <soee> kbroulik: but we are talkign about themes - tehy do not work ? i think i read somewhere they will
[12:41] <Riddell> so	yes
[12:41] <kbroulik> ah, sorry then
[12:41] <kbroulik> theoretically the themes should work but in practise that wasn't really looked after. Air for example sorta works but everything different from 4 (like systray) is broken
[12:41] <kbroulik> but then Breeze has a light and dark version :P
[12:42] <soee> yeah thats what im saying :) the 2 default breeze are enough for me atleast :)
[12:42] <soee> though i prefere dark one
[12:42] <soee> *theme -.-
[12:42] <kbroulik> I think ivan or so was porting his dark theme
[12:43] <soee> yup
[12:43] <soee> did he finished activities switcher alrfeady ?
[12:43] <soee> i think he said it will be in 5.1
[12:44] <Mirv> kbroulik: pong
[12:45] <kbroulik> Mirv: I'm having trouble with touch input on Qt 5.3 (which is shipped by 14.10) and I was told you were the person responsible for Qt stuff on kubuntu  :)
[12:45] <Mirv> kbroulik: sure, I've been packaging it. what kind of touch problem you have?
[12:46] <kbroulik> taps are not registered in Qt5-based applications. I can scroll in listviews (using two fingers) but taps are not detected. the cursor moves and the button hovers but is not actually pressed
[12:46] <kbroulik> https://codereview.qt-project.org/#/c/88361/ ← and in 5.3.2 I verified it works
[12:47] <Mirv> kbroulik: interestingly, we already have an earlier version of that patch in our 5.3.0 packages
[12:49] <kbroulik> interesting indeed. very very very rarely a tap is registered by eg. Plasma's panel but other than that it doesn't work
[12:49] <kbroulik> funnily scrolling through system settings using two fingers works
[12:49] <Mirv> kbroulik: can you file a bug at https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src and I can see what I can do. it's too close to the release so 5.3.2 will only land in the beginning of 15.04 dev cycle.
[12:49] <kbroulik> and also moving windows around or triggering screen edges (but then I think KWin is using lowlevel mouse detection rather than Qt's input)
[12:50] <kbroulik> running an app QT_XCB_DEBUG_XINPUT_DEVICES=1 shows that touch is indeed registered. But I will file a bug report once I am home (where that touchscreen is)
[12:50] <kbroulik> thanks for your patience Mirv :)
[12:51] <Mirv> :) thanks for reporting bugs
[12:56] <soee> Riddell: ping me ater @night when you will put 5.1beta into some ppa, i could test it :)
[13:12] <apachelogger> ehm
[13:12] <apachelogger> Riddell: are you sure kdesu is fixeD?
[13:14] <Riddell> apachelogger: well kdesu is, .desktop files with X-KDE-SubstituteUID=true not so much
[13:15] <apachelogger> https://bugs.launchpad.net/kubuntu-ppa/+bug/1375786
[13:16] <Riddell> yep
[13:20]  * Riddell cheers the liberation of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html from anything KDE
[13:35] <Riddell> Pali: two override errors http://paste.kde.org/pzgwo55a6
[13:35] <Riddell> Pali: those need the breaks/replaces adjusted
[13:48] <Riddell> apachelogger: I'm dropping a patch in kdoctools, which branch do I want to do it in?
[13:49] <apachelogger> master if it is applicable to 5.2
[13:49] <apachelogger> you then want to checkout kubuntu_unstable and git merge master and then push both branches
[13:55] <Riddell> groovy
[15:44] <gomek> hello
[15:52] <Riddell> oh, he left
[15:54] <sgclark> Riddell: since I am clueless on the new git workflow, any interest in me backporting 4.14.1 to trusty?
[15:57] <Riddell> sgclark: yeah that would be cool
[19:07] <soee> Riddell: hows the 5.1beta ?
[19:09] <Riddell> still in upstream mode
[19:09] <Riddell> tagging and announcing, not yet done the kubuntu packages (cos I'm was still catching up on kf5 and previous plasma today)
[19:09] <Riddell> so mañana as we say in spain
[19:10] <soee> ;D
[20:31] <ScottK> mañana is always a convenient deadline.
[20:37] <shadeslayer> heh
[21:44] <Riddell> yep, in scotland we just don't have anything with such enthusiasm
[21:53] <valorie> apachelogger: I did exactly as you suggested!
[21:53] <valorie> how is that "#unsupportedinstallmethod"?
[21:54] <valorie> I guess I just need to use the neon5 environment on this laptop to report bugs
[21:55] <valorie> because SDDM still not installing cleanly is the problem, I guess?
[21:56] <valorie> or just go whole-hog and install from the plasma5 iso
[22:43]  * jussi waves
[22:44] <jussi> and thinks australian keyboards now feel strange
[23:07] <claydoh> valorie: I run olasma 5 from the plsma 5 iso, but only had any serious issues when I decided to get some fresher crack from the Staging ppa :o
[23:08] <claydoh> haven't tried upgrading after  normal install yet, will try that on my "new" laptop when it arrives
[23:09] <valorie> the staging ppa killed networking, was the biggest problem
[23:09] <valorie> I've not been able to get the nice lil applet back
[23:09] <claydoh> never had that myelf, just some broken packages for a couple days
[23:09] <valorie> had to use nmcli to connect to my wireless
[23:10]  * claydoh is inordinately lucky with installs and upgrades, it seems
[23:15] <claydoh> Just can't have desktop effects on when using Chrome
[23:19] <jussi> oh wow, its claydoh! hello old man! 
[23:19] <claydoh> jussi: howdy ;)