[04:43] <ScottK> mamarley: Thanks.  Since debfx  tested it before, I'll let him have first crack at it.
[04:43] <ScottK> shadeslayer: Pretty sure it's OK.
[07:08] <soee> good morning
[07:32] <lordievader> Good morning.
=== jmux is now known as Guest65398
=== Guest65398 is now known as jmux_
=== jmux_ is now known as jmux
[09:52] <yofel> can someone try to run the nepomuk kcm in 4.11.3? Here running 'kcmshell4 nepomuk' gives me a frozen window
=== seaLne_ is now known as seaLne
[10:02] <soee> yofel, if you tell me that i can upgrade my machine @ work :D
[10:02] <soee> 4.11.3 officially released ?
[10:03] <vHanda> Nothing has changed in the nepomuk kcm for 4.11.3
[10:10] <valorie> released by KDE
[10:10] <valorie> ....
[10:14] <yofel> vHanda: probably, but then I wonder why it's hanging. (I was trying to stop it in an attempt to kill virtuoso)
[10:15] <yofel> if only I could tell virtuoso to not run while on battery :S
[10:15] <vHanda> Indexing doesn't run when on battery
[10:15] <vHanda> queries and all, yes. Anyway, we're working on a replacement so this should get a lot better.
[10:16] <yofel> yeah, but nepomuk isn't doing anything as far as I can tell. It's just virtuoso-t using 100% cpu
[10:16] <vHanda> then that's virtuoso going mad, just kill it
[10:16] <vHanda> It has a nack for doing that at times :/
[10:17] <yofel> yeah, SIGKILL helped :/
[10:18] <yofel> now the kcm works again ^^
[10:18] <vHanda> urgh, virtuoso
[12:59] <BluesKaj> 'Morning folks
[14:15] <Mamarok> claydoh: /me grrrmls at Basil Chupin on the ML, should we drop him a note? That guy is not even using Kubuntu
[14:21] <apachelogger> uhhh, drama?
[14:22] <apachelogger> "Your signature line tells me that you are from Holland - Utrecht, the 
[14:22] <apachelogger> place where my wife's god-daughter (and our 'unofficial niece') was 
[14:22] <apachelogger> married to Jarno [but both who now live in Melbourne, Australia]."
[14:22] <apachelogger> Oo
[14:24] <apachelogger> claydoh: Mamarok: ask him to refrain from posting until such time that he actually uses kubuntu maybye?
[14:24] <apachelogger> and inform him that his life story aint not belonging on no mailing list
[14:26] <BluesKaj> but he has such an interesting life , he just wants to share it with everyone :)
[14:26] <apachelogger> he can gladly share it on the facebookz or something
[14:29] <BluesKaj> I'm sure he already does , but he's more special than the rest of us so we deserve to hear all about it, don't you understand ? :)_
[14:40] <apachelogger> "Ask release team about possibility of a .10.1 ISO for kubuntu and ubuntustudio" <- ScottK shadeslayer_ Riddell did anything come out of that?
[14:41] <shadeslayer_> apachelogger: IIRC you said that updating via installer works
[14:41] <shadeslayer_> so I did not pursue that
[14:42] <apachelogger> mh, k
[14:46] <benvantende> hey kubuntu devs
[14:47] <benvantende> since a few months i get this purple background with video's. a bit randomly. i could not find that as an issue somewhere. does that sound familiar?
[14:48] <soee> graphic card issue benvantende  ?
[14:48] <apachelogger> define purple background please
[14:49] <shadeslayer_> the ubuntu wallpaper xD
[14:49] <benvantende> lol
[14:49] <soee> also what videos ?
[14:49] <apachelogger> shadeslayer_: prepping a mail to -devel and -users on UEFI
[14:49] <apachelogger> "Create a comprehensive guide on how to install despite broken UEFI"
[14:49] <soee> maybe they are just encoded wrong
[14:49] <shadeslayer_> apachelogger: ack
[14:49] <apachelogger> shadeslayer_: I wonder where to put such a guide
[14:49] <apachelogger> or whether it would suffice to detail that in the mail
[14:49] <shadeslayer_> apachelogger: maybe a announcement on kubuntu.org as well
[14:49] <shadeslayer_> apachelogger: wiki?
[14:49] <apachelogger> wiki aint for users :P
[14:49] <apachelogger> question is
[14:50]  * shadeslayer_ is feeling poorly today, not going to be online for long
[14:50] <apachelogger> how detailed should we go there anyway
[14:50] <Mamarok> claydoh: sent a mail, you should see it in -owner
[14:50] <benvantende> no, it comes as a layer behind the video and also disappears again. in full screen i can see the video darkens. so with all youtube (html 5) and vimeo
[14:50] <apachelogger> shadeslayer_: because if we assume: must install with updates or you are screwed, then that can just be outlined in the mail really
[14:50] <apachelogger> manual repair is somewhat tricky anyway
[14:50] <shadeslayer_> "No one tested stuff on EFI, some details about post install issue, fix pushed, two ways to fix, document both fixes"
[14:51] <shadeslayer_> fine, the less technical people will just reinstall, the more technically able people with try recovery
[14:51] <apachelogger> *shrug*
[14:51] <apachelogger> we could also write a scripty to attempt fixing that
[14:52] <apachelogger> but chances are that goes wrong and then it's even more screwed :P
[14:52] <shadeslayer_> ^^
[14:52] <apachelogger> benvantende: how do you see it if it is behind the video?
[14:54] <benvantende> apachelogger: ahaaa well it extends a little bit beyond the border of the video. taking a screenshot does not work, because that seems to redraw the screen 
=== shadeslayer_ is now known as shadeslayer
[14:56] <benvantende> apachelogger: so ok. it is hard to say if it as a layer behind. could be on top too.
[14:57] <apachelogger> sounds like a driver bug if a screen redraw fixes it
[14:58] <apachelogger> `ubuntu-bug video` should bring up an appropriate bug report screen
[14:58] <benvantende> ok
[14:58] <benvantende> but does not sound familiar?
[15:00] <benvantende> Package video does not exist.
[15:00] <apachelogger> shadeslayer: http://paste.ubuntu.com/6370898/
[15:00] <apachelogger> benvantende: nope
[15:03] <apachelogger> benvantende: maybe it was ubuntu-bug display
[15:03] <apachelogger> well, if all else fails, try to find out what graphics driver you have and report a bug against that ;)
[15:03] <apachelogger> -> afk
[15:03] <benvantende> ok tHNx
[15:24] <apachelogger> ScottK, shadeslayer, Riddell: http://paste.ubuntu.com/6371017/ announcement mail
[16:26] <Riddell> apachelogger: I'd get rid of "the final version of" as that sounds like there might be other versions
[16:27] <Riddell> apachelogger: where do you expect to put that?
[16:28] <apachelogger> Riddell: -devel -users
[16:28] <Riddell> apachelogger: and kubuntu.org?
[16:28] <Riddell> maybe update the release page too
[16:29] <apachelogger> did that aready
[16:29] <Riddell> ovidiu-florin: travel funds approved!
[16:34] <ovidiu-florin> Riddell: by Canonical?
[16:34] <Riddell> yep
[16:35] <ovidiu-florin> yeeey
[16:35] <ovidiu-florin> Riddell: thanks for the news
[16:35] <ovidiu-florin> KDE 4.11.3 was released. Is it available in backports already?
[16:39] <Riddell> I've not looked at it at all, been working on kde frameworks coinstallability
[16:40] <soee> its i ninjas ppa :)
[16:40] <soee> im using it since 2 days on saucy. works perfect
[16:42] <yofel> saucy is done and needs to be copied, raring needs testing, precise needs fixing
[16:57]  * Riddell high fives yofel 
[17:00] <genii> Hm. Maybe the #kubuntu !contribute factoid needs updating. It's pretty Ubuntu-centric.
[17:22] <Riddell> hi bukai :)
[17:23] <bukai> Riddell:  hi
[17:24] <Riddell> bukai: are you going to become an elite kubuntu contributor? 
[17:25] <bukai> Riddell: yes , but i need some help regarding how to proceed.
[17:27] <bukai> Riddell: i am really eager to contribute and become an elite contributor.
[17:28] <Riddell> sweet
[17:29] <Riddell> I need to run off now but there's others about or I'll be back later this evening
[17:30] <bukai> Riddell: ok :)
[17:32] <debfx> mamarley: sorry, forgot about your upstart script. the problem was that I've tested it with precise. newer upstart version call initgroups() so that should be fine.
[17:32] <debfx> still need to test it though
[18:20] <debfx> ScottK: do you have an unpushed quassel bzr branch or should I just import the latest version?
[19:00] <mamarley> debfx: Using start-stop-daemon doesn't seem to cause any problems, so should I just stick with that?
=== mamarley_ is now known as mamarley
[20:22] <genii> "Begin 64-Bit Download" at http://www.kubuntu.org/getkubuntu/download#download-block is broken. Url has raring in the path but saucy iso file 
[20:23] <eagles0513875> genii: you beat me to it lol
[20:23] <eagles0513875> genii: according to launchpad Riddell seems to be in charge of the site not sure who else has access to it
[20:24] <eagles0513875> genii: bug already reported https://bugs.launchpad.net/kubuntu-website/+bug/1248656
[20:24] <ubottu> Ubuntu bug 1248656 in Kubuntu Website "Kubntu 64bit download link not working" [Undecided,New]
=== wendar_ is now known as wendar
[22:47] <apachelogger> yofel: https://trello.com/c/6YqRWWdd
[22:48] <eagles0513875> apachelogger: are you able to fix something on the kubuntu website?
[22:49] <Riddell> eagles0513875: what's up?
[22:49] <eagles0513875> Riddell: its a rather urgent bug the 64bit iso on the download page the button is pointing to raring with nothign there
[22:49] <eagles0513875> bug 1248656
[22:49] <ubottu> bug 1248656 in Kubuntu Website "Kubuntu 64bit download link not working" [Undecided,Confirmed] https://launchpad.net/bugs/1248656
[22:50] <Riddell> eagles0513875: how's it now?
[22:50] <eagles0513875> thanks :) Riddell its working now
[22:51] <eagles0513875> whats the normal procedure for website bugs? just to file a bug on launchpad?
[22:51] <Riddell> eagles0513875: and ping someone here
[22:52] <Riddell> so you did good :)
[22:52] <eagles0513875> :) I am wondering if that should be added on the website somewhere. especially now that a 3rd party has taken over maintaining kubuntu etc instead of canonical
[22:53] <valorie> I got hit with the muon updating bug -- 5 mins and it's still grayed out and working away with no progress
[22:53] <valorie> also grayed out: the cancel button
[22:56] <Riddell> valorie: fix may well be in 2.1 branch if you want to test a git compile
[22:56] <Riddell> eagles0513875: no third party, kubuntu is still incharge of kubuntu
[22:57] <valorie> hmm, so that means uninstall muon, and then compile muon from git?
[22:57] <Riddell> just compile muon from git and install that over the package
[22:57] <valorie> ah, ok
[22:58] <valorie> I'll check the muon techbase for details
[22:58] <eagles0513875> Riddell: hopefully with ikonia mentoring me ill be able to package stuff for the community :) 
[22:58] <Riddell> that would be awesome
[22:58] <Riddell> calligra needs done :) 
[22:58] <Riddell> (it's a beast)
[22:59] <eagles0513875> :) also mysql workbench
[22:59] <eagles0513875> we have 5.2.47 latest is 6.0.7
[22:59] <eagles0513875> probably be best to get that pushed upstream?
[23:02] <Riddell> that's up to the server team, I assume they have their reasons
[23:02] <eagles0513875> Riddell: workbench is a GUI front end though not server side
[23:03] <yofel> apachelogger: I know - what should we do about merging? AFAIK nothing got done and I was busy with 4.11.3
[23:14] <apachelogger> yofel: I think the conclusion was to not merge at all
[23:15] <yofel> if we had a conclusion then I missed it - though I guess nobody doing anything would be a conclusion of some sort
[23:16] <valorie> I asked for a conclusion on the list and got no reply
[23:16] <apachelogger> which is the conclusion :P
[23:16] <valorie> and yet the consensus seemed to be 'merge when it seems a good idea'
[23:16] <valorie> which is why I asked
[23:17] <apachelogger> FWIW considering the amount of weird regressions we get out of merging it doesn't seem like the worst of ideas for 14.04
[23:17] <yofel> well, we could still do a comparison with debian later on to cherry pick some fixes
[23:18] <yofel> full merging is generally full of regressions :S
[23:18] <apachelogger> yah
[23:36] <valorie> i'm in the build folder of muon after cloning, but I've forgotten how to change to 2.1 branch
[23:36] <valorie> and then: 
[23:36] <valorie> cmake -DCMAKE_BUILD_TYPE=DebugFull ..
[23:36] <valorie> make && sudo make install
[23:36] <valorie> ?
[23:42] <valorie> muon isn't ON techbase, btw
[23:42] <valorie> which is a bit weak