[00:22] <ahoneybun> exit
[00:24] <ScottK> or not.
[06:56] <apachelogger> wgrant: thanks :)
[07:04] <apachelogger> sgclark: I fear that your changes to at least solid's install actually broke things
[07:05] <apachelogger> not that it had been your fault because what you did on its own would appear completely correct if everyone else in the team hadn't felt like breaking the build tooling
[08:01] <snele> I can confirm that update from LO 4.2.4 to 4.2.6 breaks kde file dialog integration. And generic file dialog which now pops up is terrible
[08:48] <alvin> Hi developers. May your coffee taste good today.
[08:49] <alvin> I'm intending to try plasma 5, but the installer from beta-1 does not start. (Just like that. I click it in the live image, but nothing happens). Should I try the daily?
[08:52] <soee> comepltely nothing ?
[08:52] <alvin> Well, the mouse icon changes and jumps a little. You know.
[09:19] <sgclark> apachelogger: sorry fell asleep again, how did I break it?
[09:21] <apachelogger> sgclark: 
[09:21] <apachelogger> [09:04] <apachelogger> -usr/lib/*/qt5/qml/org/kde/solid/libsolidextensionplugin.so
[09:21] <apachelogger> [09:04] <apachelogger> -usr/lib/*/qt5/qml/org/kde/solid/qmldir
[09:21] <apachelogger> [09:04] <apachelogger> +usr/lib/*/qml/org/kde/solid/libsolidextensionplugin.so
[09:21] <apachelogger> [09:04] <apachelogger> +usr/lib/*/qml/org/kde/solid/qmldir
[09:21] <apachelogger> this is a bogus path change introduced by extra-cmake-modules in combination with new pkg-kde-tools
[09:24] <sgclark> right the old path breaks the build. What should I have done in place of fixing the install file?
[09:24] <apachelogger> sgclark: waiting until someone fixes ECM
[09:24] <apachelogger> or well
[09:24] <apachelogger> shout at people for not having fixed ECM yet xD
[09:25] <sgclark> *yells has anyone fixed ECM? *
[09:25] <apachelogger> https://git.reviewboard.kde.org/r/120229/
[09:26] <sgclark> ok, holding. alot of packages will need to be fixed
[09:28] <apachelogger> sgclark: oh you did the qml change on more packages?
[09:28] <sgclark> yes, that was the build fail on several
[09:28] <apachelogger> that would explain why the CI builds are half green anyway xD
[09:28] <sgclark> mmhmm
[09:28] <apachelogger> sgclark: feel free to bzr revert that
[09:28] <sgclark> ok
[09:33] <sgclark> apachelogger: there was more work I would rather not lose, can't I just update the paths to the correct one?
[09:33] <apachelogger> yeah
[09:33] <sgclark> ty
[09:49] <alvin> Well, the installer in the daily (plasma5) works.
[10:53] <BluesKaj> HI folks
[11:19] <BluesKaj> 'Morning dougiel
[11:20] <dougiel> morning BluesKaj 
[11:20] <dougiel> how are you - we are in the dev channnel
[11:21] <BluesKaj> yeah, so I see...ok here dougiel, and you? 
[11:22] <dougiel> Learning how to drive tractor trailor - err trying
[11:23] <BluesKaj> ok , sounds challenging 
[11:51] <shadeslayer> what do we want to do for ktp 0.9 btw
[11:51] <shadeslayer> it's after FF
[11:51] <Quintasan> ppa it?
[11:51] <apachelogger> git
[11:51] <apachelogger> gitgitigit
[11:52] <alvin> (10.10 plasma5, daily) I have changed the name of my root filesystem (on LVM), edited /etc/fstab and ran update-grub from chroot. I've done this before, but on 10.10, the system still tries to mount the old name. Grub knows the correct path. I have no idea why this doesn't work. Does systemd somehow implement its own boot loader?
[11:54] <apachelogger> ^ 14.10 ^ wrong channel for grub/systemd questions ^ wrong channel for support questions :P
[11:54] <apachelogger> that reminds me that gdb is broken
[11:54] <apachelogger> there's too much stuff on my plate
[11:54] <apachelogger> this won't end well
[11:55] <alvin> Right. 14.10
[11:56] <alvin> I know :-( But asking questions of this kind in #kubuntu is generally ignored due to being too non-default.
[11:56] <alvin> I'm trying here because the behaviour is different from 14.10
[11:59]  * jussi01 eyes the channel...
[12:00] <shadeslayer> yo
[12:00] <jussi01> its been a while
[12:00] <jussi01> How was akademy? 
[12:01] <jussi01> oh and Riddell, I miss you also :)
[12:01] <shadeslayer> tiring
[12:02] <jussi01> did you end up sick like pretty much every linux conference has half the attendees?
[12:03] <jussi01> btw, anyone know how to make scrollwheel tilt on my logitech mouse work? (back and forwards in the browser?)
[12:03] <shadeslayer> jussi01: nah, that was Randa
[12:03] <shadeslayer> I was fine, still a bit tired as I discovered this morning
[12:03] <shadeslayer> couldn't even get out of bed
[12:04] <jussi01> oh well, sleep is a good thing...
[12:08] <ovidiu-florin_> ahoneybun: hey
[12:15] <ahoneybun> ovidiu-florin_: check the site test.kubuntu.co.uk
[12:15] <ahoneybun> you too valorie 
[12:19] <sgclark> shadeslayer: me too , I have slept the most of 2 days away
[12:22] <shadeslayer> but you probably have jetlag
[12:23] <shadeslayer> I was fine yesterday
[12:23] <shadeslayer> but today I couldn't even get up
[12:27] <sgclark> yeah likely jetlag for me, I can't wake up :( 
[12:35] <ovidiu-florin_> ahoneybun: first glance - I like it
[12:37] <ovidiu-florin_> ahoneybun: but that sidebar is very introusive on most pages
[12:37] <ovidiu-florin_> it shouls be split in the header and footer, IMHO. Do you agree?
[14:10] <apachelogger> alvin: ping, did you create a new user/home with the plasma5 isntall and if so, do you have the standard folders in your home? (Videos, Downloads, Music, Documents...)
[14:11] <apachelogger> on that note
[14:11] <apachelogger> shadeslayer: since I have a report for the xdg dirs not being created and kfunk had problems with gpg-agent I am getting the strong feeling that sddm's xsession sourcing might be broken or something
[14:11] <apachelogger> kfunk: did you try with lightdm btw?
[14:12] <shadeslayer> apachelogger: forward to d_ed?
[14:12] <shadeslayer> unless it's a integration issue on kubuntu's end
[14:12] <apachelogger> I don't even know if it is an issue yet
[14:12] <kfunk> apachelogger: let me do that now
[14:12] <kfunk> sec
[14:12] <apachelogger> I am jsut saying this is all a bit suspicious
[14:13] <apachelogger> shadeslayer: also kwrited fails to build with new ecm and pkg-kde
[14:13] <apachelogger> -- Installing: /build/buildd/kwrited-5.0.1+git20140916.1406.0/debian/tmp/usr/etc/xdg/autostart/kwrited-autostart.desktop
[14:13] <apachelogger> not sure that is an ECM problem tho
[14:13] <shadeslayer> that ... looks .. .weird
[14:17]  * sgclark is going back to bed
[14:18] <sgclark> the broken packages in frameworks will need a rebuild when ecm is fixed
[14:20] <kfunk> love the (seemingly) quick session restore in Plasma5 <3
[14:20] <kfunk> apachelogger: so, yes. with lightdm it works
[14:20] <kfunk> gpg-agent is started, and GPG_AGENT_INFO is set.
[14:21] <kfunk> I'll just stick with that for now, sddm looks crap for me anyway. :)
[14:21] <apachelogger> d_ed: ^
[14:21] <apachelogger> d_ed: xsession scripts are apprently not run by sddm at all or perhaps as the wrong user in the wrong context
[14:21] <apachelogger> breaks all sorts of stuff
[14:22] <kfunk> sec, let me test something else
[14:25] <kfunk> yes. with sddm, gpg-agent isn't started at all.
[14:26] <apachelogger> d_ed: ^
[14:27] <BluesKaj> wth, what combo of keys did i mistakenly hit to kick myself?
[14:27] <apachelogger> ctrl-q
[14:28] <kfunk> btw, worst shortcut ever.
[14:29] <BluesKaj> apachelogger, right
[14:30] <apachelogger> kfunk: worst shortcut is ctrl-w so you can close your tabs when you want to delete a word ;)
[14:30] <kfunk> indeed. that one as well.
[14:35] <alvin> apachelogger: No standard folders were created. Only 'Desktop'
[14:36] <apachelogger> kthx
[14:36]  * apachelogger is totally not getting to qt today
[14:37] <kfunk> apachelogger: my magic grep/dpkg/apt-file skills tell me that lightdm is doing the Xsession.d/* sourcing in its "lightdm-session" wrapper script.
[14:37] <kfunk> sounds like something we could steal easily
[14:38] <kfunk> sddm doesn't ever read stuff inside Xsession, judging from the source code.
[14:38] <kfunk> (just had a very brief look, might be wrong)
[14:38] <apachelogger> *nod*
[14:38] <apachelogger> just needs someone to do it :P
[14:39] <kfunk> http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/view/head:/debian/lightdm-session
[14:39] <kfunk> I think we/you could just copy/paste that and call that one instead :D
[14:39] <kfunk> d_ed: ^
[14:39] <apachelogger> oh, hm
[14:39] <apachelogger> I am lagging a lot
[14:39] <apachelogger> hooray
[14:40] <apachelogger> ./src/lightdm.c:        config_set_string (config_get_instance (), "SeatDefaults", "session-wrapper", "lightdm-session");
[14:41] <apachelogger> kfunk: I am not sure we have a similar construct in sddm to hook into
[14:41] <apachelogger> best wait for d_ed to sprinkle some wisdom
[14:42] <BluesKaj> was almost booted from freenode during a netsplit yesterday , took almost 2 mins to rejoin the server. I haven't seen that in long time.
[14:42] <BluesKaj> a long time
[14:43] <kfunk> apachelogger: so, how do I get the breeze theme going?
[14:43] <BluesKaj> lag here is normal, usually about 30ms
[14:43] <kfunk> I still need to download the theme, right?
[14:44] <BluesKaj> breeze should be default
[14:44] <kfunk> project-neon5-sddm-theme-breeze is just virtual for me.
[14:45] <kfunk> project-neon5-plasma-workspace: /opt/project-neon5/share/sddm/themes/breeze
[14:45] <kfunk> aah! oooh!
[14:45] <kfunk> who would've thought...
[14:47] <shadeslayer> fwiw d_ed is sick
[14:49] <apachelogger> kfunk: you need to config it in /etc/sddm.conf
[14:50] <apachelogger> comme ca http://bazaar.launchpad.net/~neon/neon/neon5-image/view/head:/hooks/140_neon_sddm.chroot
[14:54] <kfunk> https://github.com/sddm/sddm/pull/276 :)
[14:55] <kfunk> d_ed: ^
[14:55] <kfunk> d_ed: get well soon, btw!
[14:56] <kfunk> apachelogger: why is sddm not shipping the .conf template? :/
[14:56] <kfunk> it's all weird
[14:56] <apachelogger> yeah
[14:56] <apachelogger> because it is sddm :P
[14:57] <apachelogger> it's the weirdest daemon there is
[14:57] <d_ed> kfunk: I'll take a look
[14:58] <kfunk> apachelogger: but thanks, setting the theme worked
[14:58] <kfunk> awesome!
[14:58] <kfunk> all breezy now
[15:08] <kfunk> hmmm. looking at the lightdm code one easily understands why people just try to rewrite their on display manager...
[15:08] <kfunk> own*
[16:00] <kubotu> feed branches-next had 22 updates, showing the latest 6
[16:08] <apachelogger> http://buildwatch.org/setup.html oh la la
[16:09] <shadeslayer> ooh
[18:46] <ahoneybun> apachelogger: shadeslayer test.kubuntu.co.uk
[19:00] <yofel> ahoneybun: hm.... The header doesn't fit IMO, otherwise ~ok on first sight
[19:00] <yofel> I guess I'll complain that it's not responsive? (which would be pro, but is there no acceptable and free bootstrap theme?)
[19:04] <valorie> not excellent on my phone
[19:05]  * valorie got sick last night; Sunday I thought I beat jetlag one more time
[19:05] <valorie> soooo not true
[19:05] <valorie> :(
[19:59] <SonikkuAmerica> There we go.
[20:00] <SonikkuAmerica> Question: I do like sddm, are we going to replace lightdm with it when we go to Plasma 5, or are we still using lightdm
[20:00] <SonikkuAmerica> ?
[20:01] <yofel> going with sddm for plasma5 was the plan
[20:01] <valorie> SonikkuAmerica: I believe that kde is going with sddm, so we will as well
[20:01] <valorie> but plasma5 is still in the future for us
[20:02] <SonikkuAmerica> :D Thanks! I guess most of the flavors are moving off lightdm :P
[20:02] <valorie> 15.04 possibly
[20:02] <valorie> we'll see how the applications are coming along by then
[20:03] <SonikkuAmerica> I'll miss KDE 4, but 5 looks splendid so far. You do a great work.
[20:03]  * ahoneybun likes lightdm
[20:04] <SonikkuAmerica> Right now, SDDM seems to die at random times and I have to manually restart it... is that an upstream bug?
[20:19] <valorie> ahoneybun: look at www.qt.io
[20:19] <valorie> methinks this is the direction we should be headed in
[20:19] <valorie> works on your phone, table, and desktop
[20:19] <valorie> tablet, sheesh
[20:27] <ahoneybun> valorie: looking now
[20:29] <ahoneybun> valorie: I'll keep looking for themes and support all platforms, translations
[20:29] <ahoneybun> btw does anyone know if I could upgrade wordpress?
[20:30] <yofel> just do it and fix anything that might break. There's no point in worrying while the site isn't even official
[20:31] <ahoneybun> yofel: I know but it is not my system to mess with big time
[20:32] <yofel> make a backup then? Should be just a copy of the wp folder and a db dump
[20:39] <ahoneybun> valorie: check the site now (I have not changed the colors and what now yet)
[20:39] <ahoneybun> looks great on my phone, computer, and tablet
[20:44] <yofel> I see bootstrap, so that should be taken care of. And that theme doesn't waste so much horizontal space :)
[20:46] <ahoneybun> yea and I made sure it was reponsive as well
[20:47] <ahoneybun> well it was in the feature filter
[20:54] <valorie> ahoneybun: why does it say BLOG on top?
[20:55] <valorie> also I'd prefer "Technologies" to "Technologies Used"
[20:58] <ahoneybun> I have not changed that yet