[08:24] <yossarianuk>  hi - looks like the bug with korganizer not sending alerts has been fixed ?   But I now have an issue, its using a metric tonne of memory .... 
[08:24] <yossarianuk>  i'm literally just using one simple google calender with it and the korganizer process is using over 1 GB MEM (looking at kde system activity) and the korgac is also using over 1 GB - that's 2 GB for 1 cal ?
[08:24] <yossarianuk> I am using plasma 5.3.1
[08:29] <yossarianuk> put it this way the korganizer processes are the highest mem usage in my machine, beating Chrome and Firefox at present.
[08:29] <yossarianuk> that cannot be right ?
[09:50] <yossarianuk> going to just disable korganizer
[09:50] <lordievader> Good morning.
[12:04] <soee_> gusy i need someone on Wily + hubrid graphic 
[12:08] <mparillo> How do I know if I have hybred graphics?
[12:10] <lordievader> mparillo: Do you have two graphics cards?
[12:10] <lordievader> lspci |grep VGA
[12:13] <soee_> lordievader: i have intel  + nvidia but after latets kernel update i think system does not see nvidia
[12:13] <lordievader> Hehe, that is annoying.
[12:13] <lordievader> Which reminds me, I need to update this box.
[12:15] <mparillo> 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
[12:18] <lordievader> mparillo: Unless you have a secondary nVidia or AMD you don't have hybrid graphics.
[12:22] <mparillo> lordievader: TY. I knew I had two video ports in the laptop, but I did not know whether they had separate graphics cards.
[12:26] <ahoneybun> I need a working machine soee_ sadly
[12:26] <soee_> :)
[12:27] <ahoneybun> since I have hybrid graphics
[12:27] <ahoneybun> 15.04 works decent
[12:28] <soee_> yes worked fine also here on Wily before Kernel 4.0 :)
[12:28] <ahoneybun> ohhh
[12:28] <ahoneybun> 4.0
[12:28] <lordievader> ahoneybun: Dualboot?
[12:28] <ahoneybun> lordievader: I don't really want to do that
[12:28] <lordievader> Hmm... -.-
[12:29] <lordievader> Darn, I need to reboot if I want 4.0 on this box.
[12:29] <ahoneybun> only time I ever did that was with Windows
[12:29] <ahoneybun> but I'm full Linux now
[12:32] <ahoneybun> lordievader: are their daily images?
[12:32] <ahoneybun> *there
[12:32] <ahoneybun> or from the Alpha?
[12:34] <ahoneybun> soee_: ^
[12:34] <lordievader> Probably.
[12:35] <lordievader> ahoneybun: Check http://iso.qa.ubuntu.com
[12:35] <ahoneybun> daily would require less downloads for latest packages
[12:35] <ahoneybun> it's down
[12:35] <lordievader> Heh.
[13:13] <BluesKaj> Hi folks
[13:17] <ahoneybun> hey BluesKaj
[13:18] <BluesKaj> hey ahoneybun
[13:28] <yossarianuk> hi - potential bug - running 15.04 + plasma PPA - I have the filemanager PCManFM installed and KDE has defaulted to use that as its file manager
[13:28] <yossarianuk> if I choose a different file manager - i.e dolphin the changes are lost after I apply
[13:28] <yossarianuk> (i.e it still uses PCManFM)
[13:28] <yossarianuk> is this a known bug ?
[13:28] <yofel> shadeslayer: so, I set up my raspi2 and tried to fix kdenlive, but GLES isn't what it's looking for, and with GL I get http://paste.ubuntu.com/11841424/
[13:31] <santa_> hey shadeslayer
[13:31] <santa_> http://anonscm.debian.org/cgit/pkg-kde/frameworks/networkmanager-qt.git/commit/?h=kubuntu_unstable&id=0d5ee77df5147ea3a0fc22ba0ceedc016894478c
[13:32] <shadeslayer> yo
[13:32] <santa_> this doesn't work when building for debian I think
[13:32] <shadeslayer> santa_: no, I changed it later on I think
[13:32] <santa_> not in libnm-qt
[13:32] <santa_> http://gpul.grupos.udc.es/logs/networkmanager-qt_5.12.0-siduction1_amd64.build
[13:33] <shadeslayer> ok, let me fix it
[13:33] <santa_> ↑ this is a build of kubuntu_vivid_archive + kubuntu_unstable merged
[13:33] <santa_> + not important changes of siduction
[13:33] <shadeslayer> santa_: sitter http://paste.ubuntu.com/11841448/
[13:34] <shadeslayer> should work for kubuntu and debian
[13:34] <shadeslayer> though it's clearly a workaround
[13:34] <santa_> yeah, that should do the trick
[13:34] <sitter> no
[13:34] <sitter> the symbols are different
[13:34] <shadeslayer> sitter: I still don't understand that reasoning
[13:34] <sitter> the symbols table for debian needs to include symbols that are not there in kubuntu
[13:35] <shadeslayer> sitter: symbols for DCI don't matter
[13:35] <shadeslayer> ( atleast at the moment )
[13:35] <santa_> hmm have you considered to keep different symbols files for debian and kubuntu?
[13:35] <shadeslayer> santa_: I'm trying to avoid having to make 2 branches 
[13:35] <santa_> that's what one of your fellows of ubuntu did with qt
[13:35] <shadeslayer> kubuntu_unstable and ci_unstable
[13:35] <shadeslayer> that sounds icky
[13:36] <shadeslayer> or debian_unstable
[13:36] <shadeslayer> or whatever
[13:36] <santa_> shadeslayer: you dont have to do that
[13:36] <santa_> one of your qt guys added a file to skip the symbols files in the merges
[13:36] <shadeslayer> didn't I say symbols don't matter for DCI
[13:36] <shadeslayer> I think I did
[13:36] <sitter> they matter to everyone else
[13:36] <shadeslayer> why are we even discussing them
[13:36] <sitter> so what you are proposing is a bloody workaround only applicable to dci
[13:37] <shadeslayer> then everyone else can fix the issue
[13:37] <sitter> and doing nothing to solve the underlying problem
[13:37] <shadeslayer> which is what?
[13:38] <santa_> but I don't get how symbols handling is related to the libnm-dev build depend problem
[13:38] <santa_> aren't they different problems?
[13:38] <shadeslayer> santa_: nah, he's talking about the other Depends
[13:38] <santa_> ah, ok
[13:38] <shadeslayer> santa_: I've pushed the build-depends fix
[13:39] <shadeslayer> and I still don't get the issue with the Depends and symbols FWIW
[13:41] <santa_> shadeslayer: ok, I have scheduled a rebuilld with your change, thanks
[13:42] <santa_> shadeslayer: also, please note that I have a merge request for kdesu to not differ between debian and ubuntu
[13:42] <santa_> would be nice to get that one fixed too
[13:42] <shadeslayer> yeah, I have no time for that at the moment
[13:43] <shadeslayer> I'll try to make some time for it
[13:43] <santa_> ok, thank you
[13:45] <soee_> http://news.softpedia.com/news/debian-9-stretch-moves-to-ffmpeg-from-libav-486367.shtml
[13:54] <mparillo> how does kdesu differ from kdesudo?
[13:55] <sgclark> shadeslayer: sitter: plasma-nm in vivid seems to be looking for modemmanager-qt-dev , any idea where this might have gone? Or why it can't find it?
[13:56] <sitter> sgclark: might be new to vivid. modemmanager-qt-dev (framework) was libmm-qt-dev (plasma) until plasma 5.3 and some frameworks release
[13:57] <sgclark> ok
[13:59] <sitter> sgclark: i.e. it probably needs a frameworks backport as well
[13:59] <BluesKaj> !kdesu
[13:59] <sgclark> er oh
[14:23] <mparillo> Thanks, BluesKaj, but I always use kdesudo (except for one time I fogot. I tried sudo nano filename, thought better of it, and up-arrowed, and changed nano to kate). I was wondering what/why use kdesu instead of kdesudo.
[14:33] <lordievader> Ain't it the same thing? Kdesu and kdesudo?
[14:44] <thelionroars> I don't think kdesu is a valid command any more.
[14:46] <thelionroars> command -v kdesu gives me nada
[14:47] <lordievader> Guess it is replaced alltogether with kdesudo then.
[14:50] <BluesKaj> yeah , I think it has been , for graphical permissions at least
[14:51] <thelionroars> I wonder if pkexec works for gooey stuff
[14:52] <thelionroars> herpderp, negative
[14:56] <lordievader> thelionroars: Perhaps if you set the display variable first.
[15:17] <ahoneybun> This looks cool: http://tech.thaivisa.com/intel-ubuntu-hdmi-dongle/12160/
[15:17] <ahoneybun> load up some Kubuntu on there
[15:17] <shadeslayer> I'm unsure if 1GB would be enough
[15:18] <shadeslayer> probably won't be able to do much
[15:18] <ahoneybun> maybe
[15:18] <ahoneybun> maybe MATE
[15:18] <clivejo> is it possible for Kubuntu to stream to a Chromecast?
[15:18] <ahoneybun> chrome browser
[15:18] <shadeslayer> sure
[15:18] <ahoneybun> webpages
[15:18] <shadeslayer> WFM
[15:19] <shadeslayer> ahoneybun: I can stream my entire desktop
[15:19] <ahoneybun> what?
[15:19] <ahoneybun> WFM?
[15:19] <clivejo> Whole Foods Market?
[15:19] <shadeslayer> works for me
[15:19] <ahoneybun> lol
[15:20] <clivejo> founded 1980
[15:20] <shadeslayer> :P
[15:20] <clivejo> what is WFM?!?
[15:20] <maxyz> $ wtf WTM
[15:21] <clivejo> google isnt being very helpful!
[15:24] <thelionroars> Whifflebat Fighting Match
[15:24] <clivejo> Ive been waiting to see if VLC would bring in support, but hasnt appeared yet
[15:25] <shadeslayer> sgclark: vivid backports merge failing
[15:25] <thelionroars> *wifflebat
[15:25] <shadeslayer> sgclark: all the mergers are failing http://kci.pangea.pub/view/merge%20FIX/
[15:25] <shadeslayer> might want to go through those and fix them
[15:28] <sgclark> shadeslayer: okies
[15:32] <sgclark> I really don't understand why ci explodes like this. what a pain to try and backport...
[15:34] <shadeslayer> mergeroo failed because of conflicts
[15:34] <shadeslayer> brb
[15:35] <sgclark> not something we can merge
[15:35] <shadeslayer> hm? sure we can
[15:35] <sgclark> well how do I convince git that?
[15:36] <shadeslayer> git checkout kubuntu_unstable; git merge kubuntu_vivid_backport; fix things by hand; git commit -a
[15:37] <sgclark> unstable.. I thought this was stable. ugh. 
[15:37] <shadeslayer> look at the logs
[15:37] <shadeslayer>  kubuntu_vivid_backports -> remotes/origin/kubuntu_unstable   
[15:52] <shadeslayer> sgclark: what did you do to frameworksintegration
[15:52] <shadeslayer> why did you merge unstable into vivid backports
[15:56] <sgclark> sigh I don't know wtf is suppose to be going on here. All I wanted to do was backport some frameworks, not this.
[15:57] <shadeslayer> sgclark: https://community.kde.org/images.community/a/a5/Kubuntu_CI_Mergeflow.png
[15:57] <shadeslayer> although that does not show backports