[00:29] <ahoneybun> Riddell: did you get any of those messages on Hangout?
[05:31] <blubberbop> Anybody who might know when the next sddm updates are due? Current kubuntu 15.04 has been quite buggy for me, and though I have workarounds for most of the heavy problems, booting my machine gives me a black screen 9 out of 10 times (gotta drop to text console, restart sddm, restart sddm, 10x till I get the login screen) and thats.. anoying :) Just wondering when an update might be expected
[08:10] <Riddell> happy May day, may the proletariat rise up against the bourgoisie
[08:33] <lordievader> Good morning.
[11:39] <soee_> Riddell, sgclark: this 2 packages are marked to be removed now in apps: libktpotrprivate8 libmarblewidget20
[11:52] <BluesKaj> Hey all
[12:32] <soee_> BluesKaj: you are sudo lover i think so please read: https://plus.google.com/110954078302330754910/posts/fXjVF9UZ2kF:)
[12:34] <mparillo> Don't all those problems go away if you kdesudo? And yes, I did forget once, when I sudo nano filename. Then thought better of it, hit up-arrow and changed nano to kate.
[12:44] <BluesKaj> sudo for the the cli, kdesudo for gui root permissions, so how else does one edit files and save the changes ?
[12:44] <BluesKaj> soee_, ^
[13:07] <soee_> BluesKaj: what files exactly ?
[13:08] <soee_> i think  this bug wont happen if you edit some files outside your home
[13:08] <soee_> or maybe it might ..
[13:08] <soee_> hmm im not sure what cache exactly is saved in your home .cache
[13:19] <mparillo> The way I read the sudo G+ posts, it does not sound like a bug to me, but a way of safeguarding users who forget this: https://help.ubuntu.com/community/RootSudo#Graphical_sudo 
[13:27] <BluesKaj> soee_, idon't see anything in cache pertaining to any files I edit with kdesudo or sudo, like the sources.list etc
[13:46] <lordievader> BluesKaj: sudo nano?
[13:46] <BluesKaj> lordievader, nope, kdesudo kate in krunner
[13:47] <lordievader> BluesKaj: I thought you were asking for a way to edit files as root... that is one way.
[13:48] <BluesKaj> suppose I could use nano , now that the fonts are so small on the toolbars it's hard to find the save button
[18:47] <Riddell> http://summit.ubuntu.com/uos-1505/meeting/22508/kubuntu-kickoff/ Wed 6th 19:00UTC
[18:47] <Riddell> meeting
[18:56]  * ahoneybun needs to call for wednesday off lol
[18:57] <ahoneybun> oh I can make it without taking off work :)
[18:59] <soee> 20:00 cet ?
[19:00] <soee> Riddell: can you touch a bit this calligra that fails to biuld ?
[22:05] <Riddell> suggestions welcome https://lists.ubuntu.com/archives/ubuntu-community-team/2015-May/000422.html
[22:08] <shadeslayer> not a ML I'm subscribed to
[22:09] <shadeslayer> Riddell: also, all I've heard back on that issue is that Canonical is working with the SFLC to figure something out
[22:09] <shadeslayer> you can quote me on that if you want to
[22:09] <Riddell> shadeslayer: delaying games stop being fun after a while
[22:10] <shadeslayer> indeed
[22:10] <shadeslayer> been a year and a half now
[22:13] <valorie> Riddell: thank you for a very clear and non-emotional statement of the problem
[22:14] <shadeslayer> Riddell: there, done
[22:14]  * shadeslayer jumps into the frying pot 
[22:15] <valorie> lol
[22:15] <valorie> usually said as "frying pan"
[22:15] <shadeslayer> https://lists.ubuntu.com/archives/ubuntu-community-team/2015-May/000424.html
[22:15] <shadeslayer> no frying pan can fit a human
[22:15] <valorie> but I guess deep-fat frying is done in a pot
[22:16] <shadeslayer> have you seen how shallow frying pans are >.>
[22:16] <shadeslayer> not even a VS model can fit on there
[22:16] <valorie> yes, I've been cooking since I was like 5
[22:16] <valorie> even then I couldn't have fit
[22:16] <shadeslayer> :P
[22:17] <shadeslayer> valorie: we came up with the idea of sending your book on a tour around the world
[22:17] <shadeslayer> at Akademy
[22:17] <valorie> which book? 
[22:17] <shadeslayer> Shadow of the Wind
[22:17] <valorie> ah
[22:17] <valorie> good idea!
[22:17] <shadeslayer> maybe give it to someone from India
[22:17] <shadeslayer> or like, !Europe
[22:17] <valorie> right
[22:18] <shadeslayer> could become a thing
[22:18] <valorie> it's so nice to see you active in channel, rohan
[22:19] <valorie> <3
[22:19] <valorie> I miss you
[22:19] <shadeslayer> <3
[22:19] <valorie> coming to Akademy?
[22:19] <shadeslayer> yeah, I've been hiding in other channels
[22:19] <shadeslayer> and then when I get home, I don't really want to hang around on IRC
[22:19] <shadeslayer> valorie: ofcourse
[22:19] <valorie> cool
[22:19] <shadeslayer> possibly even giving a talk
[22:19] <valorie> excellent!
[22:19] <shadeslayer> if vHanda accepts my proposal
[22:20] <shadeslayer> valorie: with sitter
[22:20] <shadeslayer> Riddell: http://www.ubuntu.com/legal/terms-and-policies/contact-us
[22:20] <valorie> oh good, you talked him into attending
[22:20] <shadeslayer> that looks funsie
[22:20] <shadeslayer> valorie: talked? hah
[22:20] <shadeslayer> valorie: he 'volunteered'
[22:20] <shadeslayer> ;)
[22:20] <valorie> well, strong-armed then
[22:23] <valorie> hi stevesss1, can you restate here?
[22:23] <stevesss1> kubuntu is not compatible with mysql-5.6 due to akonadi-server and akonadi-backend-mysql version requirement issues
[22:23] <stevesss1> all of kde(most of it at least) requires akonadi-server
[22:23] <stevesss1> akonadi-server can work with akonadi-backend-sqlite and akonadi-backend-postgresql so akonadi-backend-mysql shoudlnt be required
[22:24] <stevesss1> akonadi-backend-mysql can 99% likely work with mysql-server-core-5.6 instead of 5.5
[22:24] <stevesss1> same for mysql-client-core-5.6
[22:24] <stevesss1> mysql-server-core-5.6 says it replaces 5.5 as does mysql-client-core-5.6
[22:24] <stevesss1> somehow akonadi-backend-myql doesnt honor this 
[22:25] <stevesss1> I beleive this to be a packaging error 
[22:25] <stevesss1> I edited the akonadi-backend-mysql control file in its deb, to allow for 5.6 as an alternative
[22:25] <shadeslayer> kind of , but not really
[22:25] <shadeslayer> there was a thread about it on Kubuntu Devel
[22:26] <stevesss1> so by force-removing that dpend part of kde may be broken for me?
[22:26] <stevesss1> got a link to the thread?
[22:27] <shadeslayer> stevesss1: https://lists.ubuntu.com/archives/kubuntu-devel/2015-April/009468.html
[22:28] <shadeslayer> stevesss1: this is in vivid?
[22:28] <stevesss1> trusty.. but shoudl test on vivid
[22:29] <stevesss1> maybe me fixing it for just me is good for now.. and let future ubuntu versions have a method to let a user choose what backend they want to use
[22:29] <stevesss1> and have it allow more choices
[22:29] <shadeslayer> stevesss1: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1336005
[22:29] <shadeslayer> potentially fixed in vivid
[22:31] <stevesss1> if I give a modified control file for the deb package that allows the user to choose from a list of valid backends using the debian depends | (OR) statements
[22:31] <stevesss1> can you test that and update?
[22:32] <stevesss1> I migth want to change akonadi-server to allow multiple backends and give a choice
[22:32] <stevesss1> and install/removal of any of them(unless its a first time backend install)  to warn before proceeding that there is no auto data transfer between backends
[22:32] <stevesss1> so if I install akonadi-backend-sqlite first time and have no other backedns.... no warning....
[22:33] <valorie> stevesss1: the problem I see with that is that it is an intrusive change
[22:33] <stevesss1> if I install second backend or remove a backend I get data transfer warning
[22:33] <valorie> and should be done upstream
[22:33] <stevesss1> for ubuntu?
[22:33] <valorie> no, for akonadi
[22:33] <stevesss1> do they maintain apt archives?
[22:33] <valorie> downstream patches are ugh
[22:33] <stevesss1> or apt repoistories?
[22:33] <valorie> no
[22:33] <stevesss1> its somethign for the package maintainer to fix
[22:34] <valorie> they maintain their own package, which should allow for this, right?
[22:34] <stevesss1> ubuntu makes the deb files and the bug is with packaging
[22:34] <stevesss1> I dont think they maintain one for ubuntu
[22:34] <stevesss1> but I can ask
[22:36] <valorie> no, there should be no need to maintain anything for one distro
[22:36] <valorie> that's my point
[22:36] <valorie> our packaging should not need patching
[22:36] <stevesss1> it shouldnt but it often does
[22:37] <stevesss1> maybe the bug is it doesnt honor that mysql-server-core-5.6 says it replaces mysql-server-core-5.5
[22:37] <stevesss1> that might be an aptitude/dpkg bug
[22:38] <stevesss1> if A replaces B(and states so in deb package info).... and C requires B.. then C should accept A
[22:38] <valorie> well, I'm not a packager or coder, which is why I wanted you to bring the issue in here, where the experts live
[22:38] <stevesss1> we'll see what happens
[22:39] <shadeslayer> stevesss1: again, have you checked if this happens in vivid?
[23:23] <yofel> shadeslayer: we only have 5.6 in vivid, and no, it doesn't
[23:23] <shadeslayer> yofel: so it's fixed \o/
[23:23] <shadeslayer> stevesss1: ^^
[23:24] <yofel> stevesss1: the reason why mysql is a hard dep, is that akonadi defaults to it. So if a random e.g. xubuntu users installs kmail, akonadi will be installed expecting to use mysql
[23:25] <yofel> so if apt chooses some other backend other than mysql for whatever reason, akonadi simply says it's broken and can't work
[23:25] <yofel> and there's not really any other sane way to solve this on a packaging level
[23:27] <yofel> stevesss1: FWIW, yes, you're right, the mysql version deps should be fixed in trusty. I didn't get around to do that yet
[23:29] <Etriaph> Just experienced a crash after unlocking the display; it started in Konversation but the exception thrown was from kdeinit5.  I couldn't report the bug because kdeinit5 has no bug reporting address?
[23:29] <Etriaph> 15.04 w/5.3 PPA
[23:30] <valorie> hmmm, I've heard this one before
[23:30] <Etriaph> I tried to restabilize everything by rerunning plasmashell and kwin_x11 but it eventually just logged me out
[23:30] <valorie> Etriaph: https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1411259
[23:30] <yofel> I saw that "no bug address" thing mysql, no idea what that's about
[23:31] <yofel> s/mysql/myself
[23:31] <yofel> I should be sleeping really...
[23:31] <Etriaph> What's your local time?
[23:31] <yofel> 01:30AM
[23:32] <Etriaph> Yup, time for nappy
[23:33] <Etriaph> I wasn't trying to logout, though.
[23:33] <Etriaph> I locked my screen, came back and unlocked it.  As soon as Konversation took focus the shell and the window manager died
[23:33] <valorie> "kdeinit5 crashes on logout and log in screen never loads "
[23:34] <Etriaph> Is the lock screen SDDM?
[23:34] <valorie> https://forums.opensuse.org/showthread.php/506850-kdeinit5-crash-You-cannot-report-this-error!
[23:34] <valorie> no, lock screen is part of kwin
[23:35] <valorie> niters yofel, sweet dreams
[23:35] <Etriaph> I can successfully logout sometimes.
[23:36] <valorie> I've not experienced this, but I've seen others report it in #kubuntu and #kde
[23:36] <Etriaph> *nods*  I have too, I just wish I could report it.
[23:37] <Etriaph> How do we get a reporting address for kdeinit5 configured?
[23:37] <Etriaph> It should go to kdelibs yes?
[23:40] <valorie> might be good to ask in #kde-devel where those experts live
[23:40] <Etriaph> valorie: Cool, I'll let you know what I learn
[23:41] <Etriaph> valorie: But it's software, not packaging yes, those reporting locations?
[23:41] <valorie> well, I'm there too
[23:41] <valorie> lol
[23:41] <valorie> yes
[23:41] <Etriaph> Cool, let's see who bites :D