[07:06] <Kalidarn> hah i was wondering where raring-desktop-amd64.iso was, then i refreshed my browser :D
[07:07] <Kalidarn> must have just been uploaded.
[08:46] <smartboyhw> Hello:P
[10:58] <Kalidarn> ooh, i should try out secure boot, in Kubuntu 13.04
[10:59] <smartboyhw> Kalidarn, thank you!
[10:59] <Kalidarn> is there a guide for setting up the key stuff?
[11:00] <Kalidarn> or do you do that post install with secureboot off
[11:00] <Kalidarn> because I noticed with the latest bios update for the E6530 dell i have here that it added a heap of secure boot stuff
[11:01] <Kalidarn> afaik the system would only have a master key for windows
[11:04] <Kalidarn> smartboyhw: yeah that documentation could do with a bit more verbosity https://help.ubuntu.com/community/UEFI#SecureBoot
[11:05] <Kalidarn> and probably an update
[11:05] <smartboyhw> Kalidarn, maybe you can help?
[11:05]  * smartboyhw doesn't have UEFI here phew
[11:06] <Kalidarn> smartboyhw: ill give it a look at it.
[11:06] <Kalidarn> although bug 1087501 sounds pretty serious
[11:07] <smartboyhw> Kalidarn, eee no good
[11:07] <smartboyhw> Any python experts here?
[11:07] <Kalidarn> smartboyhw: maybe ask in #python
[11:07] <smartboyhw> Kalidarn, they said I should try to find the problem myself:O
[11:07] <smartboyhw> ....\
[11:08] <smartboyhw> If I can find the problem myself I wouldn't have asked
[11:08] <Kalidarn> :(
[11:08] <Kalidarn> maybe try a python users mailing list
[11:50] <Kalidarn> uhh oh, noticed one problem
[11:50] <Kalidarn> grub-install dummy failed "This is a Fatal error"
[11:56] <Kalidarn> http://paste.ubuntu.com/5724219/ hmm
[11:56] <Kalidarn> the line in particular seems to be:
[11:56] <Kalidarn> Apr 20 11:49:58 kubuntu kernel: [  274.164004] efivars: set_variable() failed: status=8000000000000009
[11:57] <yofel> smartboyhw: not an expert, but what's the problem?
[11:59] <Kalidarn> :) uhh oh :D
[11:59] <Kalidarn> i think i just ran into bug 1167622
[12:05] <Kalidarn> SteveRiley: any ideas how i might bypass this? (while still installing with EFI)
[12:05] <Kalidarn> at this point im prepared to roll my own media with the patch
[12:08] <Kalidarn> actualy if it's a regression beta2 is probably alright
[12:09] <apachelogger> ScottK: looking
[12:12] <apachelogger> ScottK: might be a bug in our qt (version)
[12:12] <apachelogger> will have to debug the qt codez, which could take a while seeing as I am not home right now
[12:24] <BluesKaj> Howdy all
[12:30] <soee> ho can i exclude some folder from beeing indexed 
[12:30] <soee> for example in my home direcotry i have several subfolders thath should not be indexed
[12:33] <soee> ok i think i got this - Cutom folders 
[12:34] <Kalidarn> soee: sounds more like a question for #kubuntu
[12:58] <BluesKaj> Hey again
[13:33] <Kalidarn> hmm kubuntu beta 2 seems to finish the installer and tell me to reboot before it is actually finished
[13:34] <Kalidarn> i don't think it installed a bootloader either.
[13:34] <smartboyhw> Kalidarn, eh?
[13:34] <smartboyhw> How come?
[13:34] <Kalidarn> i decided to use beta 2 because it has kernel 3.8.0 instead of 3.8.3 (the one with the EFI regression)
[13:35] <Kalidarn> the progress bar was going along them bam it smacked a dialog in my face saying it was finished :S seemed abrupt
[13:35] <smartboyhw> Kalidarn, em 3.8.0 isn't exactly 3.8.0
[13:35] <smartboyhw> It's 3.8.4 (or 3.8.5, I forgotten)
[13:35] <Kalidarn> and wasn't able to boot off the interhal hd
[13:35] <Kalidarn> oh.
[13:35] <Kalidarn> i didn't get the grub error :P
[13:45] <Kalidarn> success :D
[13:46] <Kalidarn> silly dell bios didn't automatically add a EFI option
[13:48] <smartboyhw> Kalidarn, :D
[13:50] <Kalidarn> had to go into the BIOS and point it to grubx64.efi then it would boot properly.
[14:50] <lordievader> Good afternoon
[15:24] <Kalidarn> :S im positive a update has broken my network driver
[15:25] <smartboyhw> Kalidarn, uh oh
[15:25] <Kalidarn> so get this right my e1000e was working just fine in the livecd, both the daily for the 20th and beta 2
[15:26] <Kalidarn> and it was working post install, anyway i did a dist-upgrade
[15:26] <Kalidarn> and now it's "unplugged" tried two different cables, tried to manually bring it up and down and run dhclient on it
[15:27] <Kalidarn> no errors in syslog or dmesg, but it seems to think it's unplugged, and also i tried removing the e1000e module and replacing it, no errors.
[15:27] <Kalidarn> but it sure as hell doesn't work anymore :P
[15:27] <Kalidarn> im kind of out of ideas
[15:27] <Kalidarn> i know its not a hardware issue, cos i rebooted into the live daily for today and it worked in that.
[15:29] <Kalidarn> and im 99.9% confident it isn't a user error
[15:34] <Kalidarn> .com
[15:36] <shadeslayer> pastebin apt logs
[15:36] <shadeslayer> maybe something was removed
[15:36] <Kalidarn> that's possible
[15:36] <Kalidarn> was actually going through them now :)
[15:37] <shadeslayer> my computer needs linux-firmware-nonfree to get the wifi to work :P
[15:37] <shadeslayer> so possibly you also need that?
[15:38] <Kalidarn> nah the wifi works, its the ethernet that doesn't
[15:38] <Kalidarn> http://paste.ubuntu.com/5724772/ apt-history
[15:38] <Kalidarn> now im sure
[15:38] <Kalidarn> ah its cut it
[15:38] <shadeslayer> huh?
[15:39] <Kalidarn> the history file was too long i think pastebin didn't put it all up there
[15:39] <shadeslayer> ah
[15:39] <shadeslayer> !pastebinit
[15:39] <Kalidarn> ill stick it up on my own server
[15:41] <ScottK> apachelogger: Thanks.
[15:47] <Kalidarn> so yeah shadeslayer http://david.corra.com.au/history.log and http://david.corra.com.au/term.log
[15:47] <Kalidarn> anyway it was working right until the last dist-upgrade
[15:47] <Kalidarn> in which it installed a new kernel
[15:48] <Kalidarn> that would have been Start-Date: 2013-04-20  23:26:46
[15:48] <shadeslayer> I see a new kernel
[15:48] <shadeslayer> yeah
[15:48] <shadeslayer> try booting with the old kernel?
[15:48] <Kalidarn> i will try specifically on that
[15:48] <shadeslayer> and if it works in that, that's a pretty huge regression
[15:48] <Kalidarn> but yeah the daily 2013/04/20 works
[15:48] <shadeslayer> check what kernel that one has?
[15:48] <Kalidarn> and it worked just before it was updated :D
[15:49] <Kalidarn> ill defintely do all that :D
[15:49] <Kalidarn> cos it's got me worried now :)
[15:49] <shadeslayer> :)
[15:50] <Kalidarn> i think ethernet breaking is one of the most annoying things too :P
[15:52] <Kalidarn> and yes the other one it upgraded from was 3.8.0-16 to 3.8.0-19
[15:52] <Kalidarn> and yes shadeslayer booting the old kernel fixes it!
[15:52] <shadeslayer> great
[15:53] <shadeslayer> so regression
[15:53] <shadeslayer> please report in #ubuntu-release
[16:26] <Kalidarn> shadeslayer: i thought that it was frozen only documentation changes?
[16:26] <shadeslayer> nah
[16:26] <shadeslayer> kernel bump was planned
[16:27] <shadeslayer> Kalidarn: I'd recommend reporting a bug using ubuntu-bug
[16:27] <shadeslayer> so that it can be put in the release notes
[16:56] <nonickname2> could someone with casper or plymouth knowledge maybe look at bug #1170421? might also be something for the release notes imho
[16:58] <smartboyhw> nonickname2: Hmmm.......
[16:59] <smartboyhw> I think this bug will be quite critical.
[16:59] <nonickname2> someone else confirmed it in the meantime
[17:03] <smartboyhw> nonickname2: Ask in #ubuntu-devel will be better I think.
[19:59]  * yofel ponders bug 1170609
[20:00] <yofel> for some reason, comparing the upstream choqok-1.3.tar.bz2, and the choqok_1.3.orig.tar.bz2 from debian looks like this:
[20:00] <yofel> $ diff -ruN c/choqok-1.3/ cc/choqok-1.3/ | wc -l
[20:00] <yofel> 129903
[20:15] <yofel> ScottK: could I squeeze a 1.3a upload into raring still? Or would it be less of a change to simply patch all po files into the package?
[20:15] <yofel> I'll ask the debian maintainer later how this happened.
[21:35] <ScottK> yofel: Can still get it in.
[22:04] <xnox> yofel: diffstat is a more useful presentation of changes.