[01:21] <ScottK> Can someone verify the raring KTP SRU please.
[06:38] <soee> good morning
[08:32] <apachelogger> Riddell: are you working again?
[08:33] <apachelogger> shadeslayer: ping for when you should decide to get out of bed :P
[08:42] <jussi> hrm, Klipper, Kmix and Bluetooth all still need plasma UI's. is this something we have people to contribute to ?
[08:47] <apachelogger> jussi: I am not sure I folllow
[08:48] <jussi> apachelogger: go to your system, click the battery icon, or the nm icon. you get pretty plasma stuff. the others you get a very standard looking menu type thing.
[08:49] <apachelogger> there never was the target of having plasma applet implementations for every tray app
[08:49] <jussi> ie. http://i.imgur.com/20P53zp.png and http://i.imgur.com/1eCHXjw.png
[08:50] <jussi> apachelogger: would be nice to have it for the defaults though...
[08:50] <apachelogger> in that case you will have to file bugs with the individual developers
[08:51] <apachelogger> how a bluedevil applet would be different from what it has now I do not know though :P
[08:52] <apachelogger> what's the blue thing that pops up?
[08:52] <apachelogger> it's annoying as hell
[08:53] <apachelogger> apport
[08:53] <apachelogger> love of my life
[08:56] <jussi> apachelogger: no, the powermanagement thing I screenshoted to show differences to the bluetooth thing
[08:57] <apachelogger> yes
[08:57] <apachelogger> they don't do the same thign though
[08:58] <apachelogger> ScottK, shadeslayer: do you think there is a chance for 13.10.1 for bug 1242417
[09:55] <Riddell> apachelogger: I'm still at linuxcon today and tomorrow
[09:55] <apachelogger> k
[09:57] <jussi> which desktop effect is this? http://www.omgubuntu.co.uk/wp-content/uploads/2012/01/get_cface2.jpg
[10:19] <shadeslayer> apachelogger: I'd like a 13.10.1 if we can fix that
[10:19] <apachelogger> we do have a fix
[10:21] <shadeslayer> right, just finished reading the bug report
[10:21] <shadeslayer> I am for it
[10:23] <apachelogger> so make it happen? :P
[10:24] <shadeslayer> not entirely sure of the procedure
[10:24] <shadeslayer> just poke the release team?
[10:24] <apachelogger> I guess
[10:30] <shadeslayer> apachelogger: Is the fix released btw?
[10:31] <shadeslayer> smartboyhw_: ping
[10:31] <apachelogger> not yet I think
[10:31] <shadeslayer> apachelogger: cj says that installer probably fetches newer grub from network
[10:32] <shadeslayer> *probably*
[10:33] <shadeslayer> anyway, would like to smartboyhw_ then send a email to ubuntu-release
[10:34] <smartboyhw_> shadeslayer: yes?
[10:34] <shadeslayer> smartboyhw_: is ubuntustudio also affected by that EFI bug?
[10:34] <smartboyhw_> Actually, I have to deal with the bug on Studio's side too,
[10:34] <shadeslayer> exactly
[10:34] <shadeslayer> so do you want to get a respin done as well?
[10:35] <smartboyhw_> shadeslayer: The other two main developers have not yet replied about the sole problem on fixing the package, I need to wait for their reply.
[10:35] <shadeslayer> ack, I'll draft something till you wait
[10:36] <smartboyhw_> shadeslayer: Great.
[10:41] <apachelogger> shadeslayer: the installer fetches grub-efi-amd64, that I did not see observe it fetching grub2-common
[10:41] <apachelogger> s/that/but
[10:41] <apachelogger> woah that sentence is screwed
[10:41] <apachelogger> s/see//
[10:41] <kubotu> apachelogger: You did something wrong... Try s/you/me/ or tell me "help sed"
[10:42] <shadeslayer> thx for the brainfuck
[10:42] <shadeslayer> I am without coffee
[10:42] <apachelogger> wanna do video in phonon5's halfway ripped apart api, cause I'll glaldy switch brainfucks :P
[10:43] <shadeslayer> no thx
[10:44]  * shadeslayer passes around some awesome chocolate cake from his Birthday
[10:44] <apachelogger> oh I missed your birthday
[10:44] <apachelogger> zomg
[10:44] <apachelogger> shadeslayer: happy birthday and stuff
[10:44] <shadeslayer> thx
[10:44] <apachelogger> kubotu: order beer for shadeslayer
[10:44]  * kubotu gives shadeslayer a nice frosty mug of beer.
[10:45] <shadeslayer> beer at quarter to 1?
[10:45] <apachelogger> it's afternoon, time for beer I say
[10:45] <shadeslayer> are you trying to get me drunk so that I may not be able to do 13.10.1 good sir
[10:45] <apachelogger> glTexImage2D(GL_TEXTURE_2D, 0, GL_LUMINANCE, w, h, 0, GL_LUMINANCE, GL_UNSIGNED_BYTE, bits);
[10:45] <apachelogger> one year ago I apparently knew what that did
[10:46] <apachelogger> now I don't
[10:46] <apachelogger> life's a harsh mistress
[10:47] <yossarianuk> so you are making a new .iso ?
[10:48] <shadeslayer> maybe
[10:48] <shadeslayer> I will send a request
[10:48] <shadeslayer> upto the release team to decide
[10:52] <yossarianuk> cool - I hope they do or for the next 6 months  there will be a lot of people moaning about UEFI installation...
[10:52] <shadeslayer> smartboyhw_: http://paste.ubuntu.com/6282318/
[10:52] <yossarianuk> thanks to everybody who works on kubuntu !
[10:53] <apachelogger> (UEFI was broken in 13.04 ... no one complained)
[10:53] <shadeslayer> apachelogger: and now people are, so how about we fix it :)
[10:54] <shadeslayer> also, 13.04 installed fine on my machine at some point ( somewhere between alpha and beta )
[10:54] <shadeslayer> so it did work
[10:54] <apachelogger> just saying, this is not as critical as one would think
[10:54] <yossarianuk> 13.04 was fine with UEFI...
[10:54] <shadeslayer> but I suppose you broke it at somepoint then
[10:54] <yossarianuk> previous versions had issues if you had ubuntu + kubuntu installed in UEFI... 13.04 was fine.
[10:54] <shadeslayer> apachelogger: I don't see how rebooting into grub recovery after a install is not critical :P
[10:55] <yossarianuk> p.s - regarding not updating install .isos - Linus had something to say on that to the Fedora team...
[10:55] <yossarianuk> https://plus.google.com/+LinusTorvalds/posts/GqUgcYcfQuV
[10:55] <smartboyhw_> shadeslayer: ACK
[10:56] <yossarianuk> shadeslayer: I agree - how is a person new to Linux meant to be able to use Kubuntu 13.10....
[10:56] <apachelogger> shadeslayer: see incoming bugs?
[10:57] <apachelogger> from where I am standing the battery applet showing 0% when in fact the battery is fully charged is more critical
[10:57] <apachelogger> getting 5 mails a day on that
[10:58] <yossarianuk> maybe because people suffering the UEFI bug have given up after not being able to install the OS.....
[10:59] <yossarianuk> (my worry is people may try, fail then go back to windows.)
[11:00] <apachelogger> oh god that muon thing
[11:00] <apachelogger> :@
[11:00] <apachelogger> shadeslayer: where's apol anyway?
[11:18] <lordievader> Good afternoon.
[11:27] <BluesKaj> Howdy folks
[11:29] <ScottK> apachelogger: We can certainly SRU the fix.  I don't know about a 13.10.1.  If you do an install with internet access and check you want the upgrades, won't that be sufficient?
[11:30] <ScottK> We've got no way to upgrade the ISO with just that fix, it'd be everything in -updates, so it'd have to be completely retested.
[11:34] <apachelogger> xnox: would the installer try to update grub2-common of the base system?
[11:34] <apachelogger> because I have not seen it try to though since we have no update that is kinda hard to proof ;)
[11:35] <xnox> apachelogger: cjwatson already replied you to that question.
[11:35] <xnox> apachelogger: i don't have any other information for you.
[11:37] <apachelogger> ScottK: ^
[11:38] <ScottK> apachelogger: Let's get the fix in the archive and then test it.
[11:38] <apachelogger> faire enough
[11:38] <apachelogger> shadeslayer: wanna do the SRU? :P
[11:41] <smartboyhw_> Can you guys give me the SRU diff (BEFORE YOU UPLOAD) so I can easily implement the same to Studio :P
[11:42] <ScottK> smartboyhw_: You can't.
[11:43] <ScottK> There's already some partial support for this in Grub that's specific to Kubuntu, so the same fix wouldn't work.
[11:49] <smartboyhw_> ScottK: OK
[11:50] <apachelogger> smartboyhw_: you cannot
[11:50] <apachelogger> smartboyhw_: you'll have to talk to cj
[11:50] <apachelogger> the entire feature is depending on a bunch of special support in grub2
[11:50] <apachelogger> for kubuntu
[12:09] <shadeslayer> apachelogger: apol is on a plane
[12:11] <shadeslayer> apachelogger: afaik we can't upgrade grub-common
[12:13] <shadeslayer> apachelogger: <cjwatson> shadeslayer: That checkbox actually isn't relevant here
 It only applies to stuff in the livefs, which grub isn't
[12:19] <jussi> so, it seems kde partition manager is broken/unworkable
[12:20] <jussi> at least I am unable to do anything with a USB stick on it. (and on a side note, why is it so hard to format a usb drive in kde)
[12:35] <apachelogger> shadeslayer: grub2-comon is in the livefs
[12:35] <shadeslayer> well then
[12:35] <apachelogger> shadeslayer: and that's where the key change is (grub-install)
[12:35] <shadeslayer> lets wait for the fix to land
[12:35] <shadeslayer> then we can test somehow in VBox?
[12:35] <apachelogger> who's landing the fix anyway?
[12:36] <apachelogger> I would rather like to focus on phonon for the rest of the week
[12:36] <apachelogger> I am kinda behind because of all the .10 madness
[12:37] <shadeslayer> apachelogger: I thought you or cj was :S
[12:39] <apachelogger> shadeslayer: cj wants us to do it
[12:39] <apachelogger> alas, I can do it, but not today
[12:39] <shadeslayer> yeah because I totally know how grub2 works
[12:40] <shadeslayer> apachelogger: how long would it take you :S
[12:40] <apachelogger> it just needs a verbatim backport of the patch IMO
[12:40] <BluesKaj> hmm, I saw what appeared to be a fix for the missing vpn icon connect indicator in an upgrade earlier today , but even after a reboot it doesn't appear, the disconnect indicator (a red circle with a line thru it) still appears on top of the ethernet icon
[12:40] <apachelogger> grub-mkinstall is triggered by the postinst
[12:41] <apachelogger> and that will install the efi images into EFI/ubuntu with the patch
[12:41] <shadeslayer> okay
[12:42] <apachelogger> well, in an installation scenario grub-install is called by grub-installer/ubiquity, but the fact remains ;)
[12:42] <apachelogger> for upgrades systems it is triggered by the postinst and the actual on-disk result will be that both EFI/kubuntu and EFI/ubuntu are there, but the UEFI bootmanager entry should get updated to point to latter, so that's fine too
[12:43] <shadeslayer> k
[12:48] <apachelogger> actually let me write the verification bit I have no idea in which konsole window I was poking around before getting distracted anway -.-
[13:06] <shadeslayer> apachelogger: http://paste.kde.org/p46592879
[13:06] <shadeslayer> does that look sane to you
[13:07] <apachelogger> shadeslayer: yeah
[13:07] <apachelogger> although
[13:07] <apachelogger> http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/trusty/grub2/trusty/revision/2359
[13:07] <apachelogger> also has the change to install applied directly
[13:07] <apachelogger> not sure why
[13:08] <apachelogger> shadeslayer: best just do a testbuild and see if grub-install looks ok ;)
[13:08] <apachelogger> shadeslayer: also series is saucy-proposed
[13:08] <shadeslayer> saucy is redirected to saucy-proposed no?
[13:12] <shadeslayer> apachelogger: <cjwatson> shadeslayer: so that for example I can "bzr blame" across both upstream and patches at once
[13:17] <shadeslayer> hooray
[13:17] <shadeslayer> VBox doesn't want to boot the ISO at all
[13:19] <shadeslayer> ahh 
[13:19] <shadeslayer> stupid i386 ISO
[13:28] <shadeslayer> apachelogger: what other bugs btw?
[13:28] <apachelogger> shadeslayer: i386 doesn't have efi support btw
[13:28] <shadeslayer> yeah yeah
[13:28] <shadeslayer> amd64 doesn't boot as well fwiw
[13:28] <apachelogger> I think that test case got a bit away from me
[13:28] <apachelogger> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417
[13:28] <apachelogger> shadeslayer: yeah, vbox is shit
[13:29] <apachelogger> actually you could possible boot via the shell, because vbox drops you into the intel tianocore shell
[13:29] <apachelogger> I have not found out how to do that tho
[13:29] <apachelogger> or perhaps create a boot entry
[13:30] <apachelogger> anyway.... if you use the fakebios to tryt and load the EFI image it also drops you to the shell so I suspect there's simple incompat with vbox
[13:30] <apachelogger> didn't look too much into it
[13:30] <apachelogger> anyway
[13:30] <apachelogger> shadeslayer: testcase written
[13:30] <shadeslayer> yeah was reading that
[13:30] <BluesKaj> vbox runs windows as a guest OS much better than a linux guest ...couldn't install guest additions with linux 
[13:30] <apachelogger> also 
 saucy is redirected to saucy-proposed no?
[13:30] <apachelogger> no
[13:30] <shadeslayer> once released, that's turned off?
[13:31] <apachelogger> during development uploads to saucy are redirected to the proposed pocket, they still will end up in saucy
[13:31] <apachelogger> the saucy pocket is however frozen since release so you cannot land anything in the saucy pocket
[13:31] <apachelogger> that's why you need to target saucy-proposed
[13:31] <shadeslayer> aha, they move from proposed to -updates then
[13:31] <apachelogger> aye
[13:31] <yofel> really? Uploading to raring always worked for me
[13:31] <apachelogger> yofel: used to be like that in 2007 anyway :P
[13:32] <shadeslayer> possibly ScottK knows ^^
[13:32] <apachelogger> you may get away with targetting saucy-updates or raring-updates
[13:32] <apachelogger> denoting raring and it ending up in raring-updates would be weird though
[13:33] <yofel> well, I did upload SRU's to 'raring', and they were queued in raring-proposed
[13:33] <shadeslayer> the question is what happens if you target saucy and then it gets redirected to -proposed and then when the package is approved, does it give you a error
[13:33] <shadeslayer> because saucy is frozen, so where does it go?
[13:34] <apachelogger> ^ that would seem more likely, or perhaps you can reroute when approving
[13:35] <apachelogger> yofel: eitherway uploading to the raring pocket while you cannot land anything in there is silly
[13:36] <shadeslayer> BluesKaj: I just install the guest packages
[13:36] <shadeslayer> virtualbox-guest-{dkms, utils, x11}
[13:36] <shadeslayer> and voila, everything just works on the guest VM
[13:37] <shadeslayer> ahhhh
[13:37] <shadeslayer> VBox is just slow in EFI
[13:37] <yofel> *shrug* - it saves me from special casing SRU's in some places, and it makes uploading test packages from PPA's less error-prone
[13:38] <BluesKaj> ok sha , nice to know it works in some setups 
[13:38] <BluesKaj> shadeslayer.^
[13:38] <shadeslayer> well, it's worked for me always
[13:39] <Quintasan> \o
[13:39] <shadeslayer> Quintasan: nice of you to show up
[13:40] <Quintasan> I'd like to do that more often but currently it's more or less impossible
[13:40] <Quintasan> Anything needs doing?
[13:41] <yofel> someone asked me to update digikam to 3.5 - if you're bored ^^
[13:41] <Quintasan> Sounds like plan.
[13:49] <smartboyhw> shadeslayer, on the UEFI stuff: cjwatson is probably fixing it for us, and we will want the respin.
[13:50] <shadeslayer> okay
[13:50] <shadeslayer> are you going to take care of backporting the fix to saucy?
[13:52] <smartboyhw> shadeslayer, I think so.
[13:52] <shadeslayer> okay, I have the fix for kubuntu compiling here https://launchpad.net/~rohangarg/+archive/experimental/+files/grub2_2.00-19ubuntu2.1.dsc
[13:52] <shadeslayer> so that I can test it
[15:25] <shadeslayer> yossarianuk: ping
[15:25] <shadeslayer> yossarianuk: can you test my GRUB package?
[15:25] <shadeslayer> with the EFI fix
[15:33] <yossarianuk> shadeslayer: I can;t right now (im @ work with no UEFI) - I can do tonight for sure 
[15:33] <yossarianuk> shadeslayer: where can I get the package ?
[15:33] <shadeslayer> https://launchpad.net/~rohangarg/+archive/experimental
[15:33] <shadeslayer> please upgrade to that grub before installing
[15:34] <yossarianuk> sure - it will be a bit later ... (when I get home got baby to feed/bath, etc) but about 9 - 10 pm UK time I should have time to do so
[15:35] <yossarianuk> just to confirm I already have an install where I changed the efi folder name from ubuntu -> kubuntu (to get it to boot) - shall I leave that as it is or change it back to kubuntu ?
[15:36] <yossarianuk> or did you mean test a new install and install your grub during the install process ?
[15:36] <yossarianuk> (either way its fine...)
[15:47] <shadeslayer> yossarianuk: would it be possible for you to do a complete wipe?
[15:47] <shadeslayer> and install again?
[15:48] <yossarianuk> shadeslayer: not a problem
[15:48] <shadeslayer> cool
[15:48] <yossarianuk> shadeslayer: please confirm how to use your package in the install though...
[15:49] <yossarianuk> i.e I do a normal install - then chroot and install package ?
[15:49] <shadeslayer> boot to live session -> add PPA -> upgrade all grub packages 
[15:49] <shadeslayer> proceed to install
[15:49] <yossarianuk> ok - np
[16:10] <yossarianuk> shadeslayer: Shall I contact you via irc / email with results ?
[16:10] <yossarianuk> (about to go home - yey!)
[16:10] <shadeslayer> email plz
[16:10] <shadeslayer> Hopefully I'll have internet at my apartment today
[16:10] <yossarianuk> what is your email ?
[16:11] <shadeslayer> rohangarg AT kubuntu DOT org
[16:11] <yossarianuk> cheers 
[16:11] <yossarianuk> Will let you know how it goes .....
[16:28] <apachelogger> shadeslayer: you cannot update grub before install... the squasfs is unpacked onto /target what is installed or not on the live system has no impact
[16:28] <shadeslayer> 0.o
[16:29] <shadeslayer> didn't you say it would work before?
[16:29] <apachelogger> no
[16:29] <apachelogger> why would I say something works even if I know it doesn't? :P
 shadeslayer: grub2-comon is in the livefs
[16:30] <apachelogger> that's the squashfs
[16:31] <shadeslayer> when I said only the packages on the livefs can be updated?
[16:31] <apachelogger> I am confused
[16:31] <apachelogger> where did I say that anyway?
 shadeslayer: the installer fetches grub-efi-amd64, that I did not see observe it fetching grub2-common
[16:32] <shadeslayer> http://irclogs.ubuntu.com/2013/10/22/%23kubuntu-devel.html#t12:35
[16:32] <apachelogger> ^ that is because efi-amd64 is installed on /target
[16:33] <apachelogger> whereas grub2-common is unpacked from the squashfs
[16:33] <shadeslayer> oh
[16:33] <apachelogger> shadeslayer: miscommunication it seems
[16:34] <shadeslayer> yeah
[16:34] <shadeslayer> so, tl;dr can't be done
[16:34] <apachelogger> livefs for me == squashfs :P
[16:34] <shadeslayer> so, how do we test this fix
[16:34] <shadeslayer> just trust cj?
[16:34] <apachelogger> no clue what cj meant
[16:34] <shadeslayer> heh
[16:34] <apachelogger> shadeslayer: needs SRU then you can as per the test cases I outlined
[16:34] <shadeslayer> okay
[16:35] <shadeslayer> yossarianuk needs to be told then xD
[16:35] <apachelogger> i.e. if ubiquity will in some capacity try to upgrade -common on the target it will work
[16:35] <shadeslayer> I see
[16:35] <apachelogger> the fix can be tested in an upgrade capacity though
[16:35] <shadeslayer> trie
[16:35] <shadeslayer> *true
[16:35] <apachelogger> install system -> mount root -> mount efi paritition -> chroot into root -> install debs
[16:36] <apachelogger> i.e. the upgrade test case 
[16:36] <shadeslayer> right
[16:38] <apachelogger> if -common is not updated by ubiquity we need to make .1 and if that is not possible either we shoudl put up some good instructions on how to work around the issue
[16:39] <apachelogger> or make a scripty xD
[16:39] <apachelogger> or both
[17:05] <shadeslayer> o_o
[17:06] <shadeslayer> grub2 failed on i386
[17:39] <palasso> It's not directly related to development but in any case a dev might want to respond http://www.bluemintlinux.com/2013/10/kde-grub-2-editor-what-it-is-and-how-to-install-it-aka-why-isnt-it-installed-by-default.html
[17:46] <BluesKaj> palasso. make sure you read the tutorial closely , that app can muck up grub so easily,  it's really quite dangerous 
[17:48] <palasso> BluesKaj: thnx for the warning, I am cautious with my computer :)
[17:49] <BluesKaj> I found that the choices one makes don't appear correctly in the grub changes list , unless they've fixed the app
[20:30] <yossarianuk> I tested the updated grub packages here -  https://launchpad.net/~rohangarg/+archive/experimental
[20:30] <yossarianuk> I 'think' it was shadeslayer: that mentioned them
[20:30] <yossarianuk> same UEFI install issue.
[20:32] <yossarianuk> to avoid any conflicts with ealier I completely cleared the disk / all UEFI entries also.
[20:33] <yossarianuk> again the workaround works - i.e boot to live cd , mount EFI partition then mv /mnt/sda1/EFI/kubuntu -> /mnt/sda1/EFI/ubuntu 
[20:35] <yossarianuk> sorry - I have always copied not moved....