[03:48] <Riddell> anyone tried kpowersave?
[04:06] <raphink> Riddell: did I understand there was an equivalent to update-notifier being developped for kubuntu ?
[04:06] <raphink> well I did understand that but I'm not sure it's right ;)
[04:08] <Riddell> raphink: mornfall is working on it
[04:08] <raphink> how is it called?
[04:08] <Riddell> although we're still waiting to hear if he'll get a bounty for it so no guarantees yet
[04:08] <raphink> (Happy New Year 2006 btw)
[04:08] <raphink> hmmm ic
[04:08] <Riddell> not sure if it has a name yet
[04:08] <raphink> is he porting update-notifier or devloping from scratch?
[04:09] <Riddell> developing from scratch I think, update-notifier is all of about 4 classes
[04:09] <Riddell> look at ept/adept in KDE's SVN playground/admin module, there may be code in there
[04:10] <raphink> hmm ok
[04:10] <Riddell> happy new year :)
[04:10] <raphink> thanks
[04:10] <raphink> do you have any idea when next CC is to be?
[04:10] <Riddell> nope, check the calendar
[04:10] <raphink> it's not in the calendar yet
[04:10] <raphink> ;)
[04:10] <raphink> so I'll wait
[04:11] <raphink> theorically it should be on the 3rd
[04:11] <raphink> but it doesn't seem it's going to be
[04:11] <raphink> ;)
[08:06] <jpatrick> Happy New Year allee
[08:07] <allee> jpatrick: thx. Same to you!!
[08:08] <allee> jpatrick: everyone recovered? Or are some members still missing in action? ;)
[08:09] <jpatrick> Not sure...
[08:10] <jpatrick> I've had nothing to drink...
[08:10] <jpatrick> due to unavoidable thingies
[08:11] <allee> jpatrick: heh, no alcohol here for years.  Once can survive
[08:11] <jpatrick> allee: I think I have to wait 3 more years for alcohol...
[08:12] <allee> jpatrick: btw. arn't you involved in docs?
[08:12] <jpatrick> allee: Nope
[08:13] <jpatrick> I tried to get involed...
[08:13] <jpatrick> except for KubuntuPackagingGuide
[08:14] <allee> ah, I've some TODO for this.  Sigh.
[08:27] <jpatrick> wow a kubuntu-i18n spec
[10:48] <Riddell> do we know philscite?  wanting to join kubuntu-team
[11:06] <Tm_T> hmm, can't remember seen that ever
[11:08] <Riddell> turns out to be the philipine school of it
[11:08] <Riddell> which would be cool to have them as users
[11:08] <Riddell> a
[11:08] <Riddell> alas launchpad doesn't want to work for approving or declining members just now
[11:08] <Tm_T> hmm, if there's no reason not to allow, bring him in :)
[11:08] <Tm_T> him/her/them
[11:08] <Tm_T> whatever
[11:09] <Riddell> well I'm trying to keep kubuntu-team as a list of people who actually are kubuntu developers
[11:10] <Riddell> so random people I decline with a note saying please say hi to us first
[11:11] <Tm_T> heh
[11:12] <jjesse> so where do i fit into kubuntu-team :P
[11:13] <Riddell> jjesse: you're on the team!
[11:14] <Tm_T> hmm, jingle voice support on kopete... almost ok, crashes if I accept audio =)
[11:14] <Tm_T> (haven't tried myself yet)
[11:15] <jjesse> just being difficult "Riddlel: well I'm trying to keep kubuntu-team as a list of people who actually are kubuntu developers"
[11:16] <Tm_T> I hope I'm not that list...  :O
[11:16] <Tm_T> hmm, no hitlist?
[11:17] <Riddell> jjesse: and you are!
[11:17] <Riddell> where developer means anyone who's done anything to help
[11:17] <jjesse> grin thanks :)
[11:32] <Tm_T> mez o/
[11:47] <Riddell> anyone want to package kflickr
[11:47] <Riddell> upstream already has a package
[11:47] <Tm_T> I don't think I'm sharp enough atm to do it
[11:48] <Riddell> http://www.destination-linux.org/kflickr/index.php?path=0.5/
[11:48] <Riddell> just needs checked for sanity I guess
[11:50] <seth_k|lappy> I'm on it, Riddell
[11:51] <seth_k|lappy> should I keep it native, or break out debian/
[11:55] <allee> seth_k|lappy: there nothing that stops you to create a orig.tar.  IMHO do it
[11:59] <Riddell> seth_k|lappy: use whatever the upstream tar has
[12:00] <seth_k|lappy> Riddell, okay. It's a native package, so I'll just make sure it builds and then REVU it
[12:03] <Riddell> cool


[00:57] <spstarr> any reason usbcore is compiled into kernel?
[00:57] <spstarr> I cannot mount usbfs oddly
[00:58] <amason> Hi guys, having some problems with packaging a kernel. Despite passing the --initrd flag to make-kpkg it does not seem to create an initrd or run update-initramfs on installation
[00:58] <amason> any ideas where i am going wrong ?
[00:58] <spstarr> make-kpkg clean ? first
[00:58] <spstarr> then
[00:59] <spstarr> CONCURRENCY_LEVEL=5 fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers
[00:59] <spstarr> taking ubuntu's .config usbfs broke
[01:00] <amason> spstarr: asside from the CONCURRENCY_LEVEL=5 I have pretty much the same line.
[01:00] <amason> this is building a 2.6.31 kernel on 8.04.
[01:01] <amason> does that make any difference ?
[01:01] <amason> i grabbed the 2.6.31 source from kernel.org
[02:24] <spstarr> erm where is usbfs in /proc/filesystems?
[02:24] <spstarr> its not there?
[02:24] <spstarr> given im building a custom kernel using ubuntu's .config i even rebuilt usbcore as a module, still no usbfs registered in /proc/filesystems ?
[02:25] <spstarr> and usbcore is loaded
[02:26]  * spstarr boots into a ubuntu kernel to confirm
[02:29] <spstarr> ubuntu's kernel is fine, so then building a custom kernel breaks usbfs?
[03:20] <spstarr>  if you do not enable CONFIG_USB_DEVICEFS doesn't it defer to both /sys/bus/usb/drivers AND /proc/bus/usb?
[03:20] <spstarr> since the latter is the new mount point for usbfs
[07:09] <amason> Hi guys, having some problems with packaging a kernel. Despite passing the --initrd flag to make-kpkg it does not seem to create an initrd or run update-initramfs on installation
[12:20] <tuukkah> hey guys! what's the chance of getting the small module fixing this bug into karmic? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/435906
[12:20] <ubot3> Malone bug 435906 in linux "need to turn off extra "Switchable graphics" GPU" [Undecided,Confirmed]
[15:47] <nxvl> hi!
[15:48] <nxvl> for some reason since one of the updates in karmic, my computer is not reading my swap anymore
[15:48] <nxvl> i've a bunch of encrypted LVM partitions for my swap
[15:48] <nxvl> but everytime i reboot my machine i need to add them by hand
[15:48] <nxvl> is that a known issue?
[15:49] <nxvl> i've no idea where to check for the error/logs/information
[15:49] <nxvl> ogasawara: ^^
[15:52] <tormod> nxvl: you'd better file a bug, and attach your fstab
[15:53] <rtg> nxvl, I wonder if its related to my bind mount problems, i.e., they are not mounted automagically. Keybuk, any thoughts?
[15:54] <nxvl> mm, for some reason some UUIDs are wrong
[15:54] <nxvl> i wonder if that's the issue
[15:54] <nxvl> not all of them though
[15:54] <nxvl> will reboot and check, brb
[15:58] <nxvl> wrong assumption, still doesn't work
[16:02] <nxvl> tormod: so you just need my fstab?
[16:02] <tormod> nxvl you have them referenced with UUID in fstab? do they appear in /dev/disk/by-uuid?
[16:02] <nxvl> yup
[16:03] <nxvl> and yes
[16:03] <nxvl> that's what you get with the installer
[19:53] <smoser> rtg, i'm guessing that there are tools that grab dependencies, but if not, for bug 439415, you need scsi_transport_spi.ko in -virtual also
[19:53] <ubot3> Malone bug 439415 in vm-builder "Bundling UEC image with uec-images-provided kernel/ramdisk results in an EMI that fails to boot" [High,Triaged] https://launchpad.net/bugs/439415
[19:56] <rtg> smoser, I'll check. thanks for the heads up
[19:58] <rtg> smoser, drivers/scsi/scsi_transport_spi.ko is already in the list
[19:59] <smoser> good deal
[21:31] <CarlFK> bug 439456  "missing nic firmware" should be easy to a) verify (the file is indeed missing) b) decide on if it should be included and c) include it
[21:31] <ubot3> Malone bug 439456 in linux "netboot e100/d101m_ucode.bin not found" [Undecided,New] https://launchpad.net/bugs/439456
[21:31] <CarlFK> can someone make sure the right person looks at it?
[21:33] <rtg> CarlFK, looking...
[23:00] <zooko> Folks: what's the process that Ubuntu folks use to look out for security problems in supported kernels?  I'm thinking mostly of Hardy.
[23:01] <zooko> This is probably a FAQ.  I'll look for such information on the web.
[23:20] <zooko> Hm, I haven't yet found a statement of the process.
[23:30] <zooko> Aha. http://www.ubuntu.com/products/whatisubuntu/serveredition/features/security


[02:46] <rsvp> the basic idea is to use Dropbox for more than message passing: e.g. drop in a script locally and cron execute by AMI, then retrieve its result from any computer/mobile device -- but first we must install Dropbox into our instance. So here's what we have so far: http://privatepaste.com/3a6c632e69 -- installs fine, however, we are 97% to completion -- what the missing 3% ?? -- Your feedback appreciated on the FAIL section of th
[05:39] <superxgl> hi room
[05:40] <superxgl> does anyone who use the current stable release eucalyptus 2.0?
[06:18] <superxgl> hi all , i want to ask that the package Eucalyptus 1.6.2 - RHEL / CentOS 5.4 - i386 ,may i also use cento 5.3  ?
[06:44] <superxgl> can anyone help me pls?
[06:44] <flaccid> people help if they can
[06:44] <superxgl> hmm.tnx
[06:45] <flaccid> you should be able to get centos going
[06:45] <superxgl> hmm.. i am not sure
[06:45] <superxgl> if i can use centos 5.3
[06:46] <superxgl> but the package release if for 5.4
[06:46] <flaccid> i don't see any point in using something old
[06:46] <superxgl> hmm..yes,u r right
[06:46] <superxgl> but because i have installed centos5.3
[06:48] <flaccid> eek
[06:48] <superxgl> yes


[08:04] <apw> ramsudharsan (N,BFTL), i have a great many answers, no idea which one you want
[09:42] <Kano> hi, do you want to use 3.16 or 3.17 for 14.10?
[09:44] <apw> we will be using 3.16 for 14.10
[09:44] <Kano> with hawaii backports?
[09:45] <Kano> i am thinking about using 3.17 from your unstable branch, after you rebased it
[09:46] <Kano> mesa 10.3 is very interesting
[09:47] <Kano> but needs 3.17 for latest amd hardware
[09:57] <apw> Kano, we will be keeping it rebased for sure, but it will likely skip from v3.17 to v3.18 quite quick
[09:57] <Kano> hm
[09:58] <Kano> well should not be hard to update it a bit on your own
[10:00] <binBASH> apw: you saw my updates on https://bugs.launchpad.net/bugs/1318551 ?
[11:27] <apw> binBASH, the next logical step is to test the v3.8-rcN candidates between 3.7 and 3.8 to see if we can narrow it down
[13:30] <binBASH> apw: ok tested and it's also crashing @ 3.8-rc1
[13:48] <apw> binBASH, the worst place ...
[13:50] <mlankhorst> also most likely place ;-)
[13:50] <binBASH> :-)
[13:53] <apw> binBASH, we need to do a proper bisect then between those, i'll ask a collegue to help with that
[13:54] <binBASH> ok
[13:56] <apw> binBASH, what i am proposing is this described here: https://wiki.ubuntu.com/Kernel/KernelBisection
[14:27] <tyhicks> rtg: Hi - thanks for processing all of the AA pull requests. When should we expect the generic kernel to migrate from proposed and new goldfish/mako/manta/flo kernels to be uploaded?
[14:28] <rtg> tyhicks, I'm still working on a goldfish build problem, but the rest could be pocket copied. rsalveti normally handles that.
[14:28] <tyhicks> rtg: I was unaware of a goldfish problem. Is it due to the AA pull request?
[14:29] <rtg> tyhicks, the generic kernel should migrate as soon as its added to the d-i
[14:29] <rtg> tyhicks, I think the goldfish build problem is unrelated, but I need to get back to it
[14:29] <tyhicks> ok
[14:29] <tyhicks> rtg: 'd-i'?
[14:29] <rtg> debian installer
[14:29] <tyhicks> ah
[14:29] <tyhicks> thanks :)
[14:32] <ricotz> rtg, hi :), i am curious will the kernel ppa receive some preview/testing packages of 3.17 for utopic?
[14:32] <tyhicks> rtg: one more question - who/what adds kernels to the debian-installer?
[14:32] <rtg> tyhicks, generally soneone in foundations, e.g., infinity (or sometimes apw)
[14:33] <rtg> ricotz, there is a mainline 3.17 build at http://kernel.ubuntu.com/~kernel-ppa/mainline/
[14:34] <ricotz> rtg, ah, right, i meant proper builds with apparmor support likely based on http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-utopic.git;a=shortlog;h=refs/heads/unstable
[14:35] <tyhicks> ricotz: the kernel team doesn't provide that
[14:35] <tyhicks> ricotz: the security team will soon be in the process of upstreaming those apparmor patches
[14:36] <rtg> ricotz, the unstable branch will eventually morph into 15.04, but we won't start producing builds for it until after 14.10 is released
[14:36] <ricotz> tyhicks, ok, that is why i was asking tim since he is updating and rebasing this branch
[14:37] <ricotz> rtg, alright, thanks
[15:38] <rsalveti> tyhicks: rtg: we should only promote those kernel packages once goldfish is also fixed, as we got apparmor related changes
[15:38] <rsalveti> but yeah, I'm taking care of testing and copying
[15:38] <jdstrand> I don't think they have to be all copied en masse
[15:39] <jdstrand> the goldfish kernel would continue functioning as it is now
[15:39] <rsalveti> jdstrand: otherwise the cache will be invalid for a few
[15:39] <jdstrand> does that matter?
[15:39] <rsalveti> jdstrand: well, emulator will take way longer to boot
[15:39] <rsalveti> that's a regression
[15:40] <jdstrand> rsalveti: I guess what I am asking is why the cache precompilation for goldfish is tied to the other kernels
[15:40] <jdstrand> rsalveti: does the server logic all use the same features file or something?
[15:40] <rsalveti> jdstrand: because you said the feature file would change
[15:40] <rsalveti> and yeah, we use only one feature file for every kernel
[15:40] <rsalveti> at least atm they are all the same
[15:41] <rsalveti> that's why the cache is valid for every device we support
[15:42] <rtg> rsalveti, the build failure is a firmware rule (whch has me a bit mystified). I could work around it by just disabling the firmware part of the build. Does goldfish actually use any firmware since its an emulated environment ?
[15:42] <rsalveti> rtg: I don't think it uses any
[15:42] <jdstrand> rsalveti: I think we are not communicationg well. when the kernels are going to be copied, we should change the feature file. if you aren't going to copy the goldfish kernel, don't change its feature file
[15:43] <rtg> rsalveti,  ok, lemme experiment with just turning it off.
[15:43] <rsalveti> jdstrand: what I said is that we have one single feature files that are the same for every kernel package we support
[15:43] <rsalveti> because the rootfs is generic, so it needs a generic feature file
[15:43] <jdstrand> rsalveti: right, but isn't linux-goldfish a different kernel package than linux-mako?
[15:43] <rsalveti> jdstrand: it is
[15:43] <rsalveti> but the final feature file is still the same
[15:44] <jdstrand> oh I misread what you said
[15:44] <jdstrand> I thought you meant one per kernel
[15:44] <rsalveti> oh, sorry, no, we have one common feature file in live-build
[15:44] <jdstrand> I see. ok, then yes, waiting makes sense
[15:45] <jdstrand> rsalveti: how does this relate to krillin?
[15:45] <rsalveti> jdstrand: will coordinate with the PES team
[15:45] <rsalveti> jdstrand: because they are the ones publishing the device tarball for it
[15:45] <jdstrand> ok, perfect
[17:00] <El_Presidente> hi, i may have run into a bug on my fathers machine, he is running ubuntu 14.04 on a sandy bridge cpu with hd2000 (onboard) video. since some kernel upgrades the system freezes nearly every time when the "plymouth" xubuntu logo appears. i installed 3.17 rc5 mainline kernel for testing and now this error does not appear anymore. have you got similar reports or do i have to bisect this issue?
[17:11] <apw> El_Presidente, i do not recall that specifically, i would file a bug against linux, and test the mainline kernels nearer the ubuntu version
[17:11] <El_Presidente> apw, ty
[17:12] <El_Presidente> it must have been in the last two weeks
[17:13] <apw> El_Presidente, do you thik this occured in a kernl update, ie an older ubuntu kernel was ok?  if so you can test those too
[17:13] <El_Presidente> apw, well i installed his system in april with a fresh dvd
[17:14] <El_Presidente> and he has problems since 35 or 34 im not sure
[17:14] <apw> and it worked then, and does not now, so that sounds like a kernel update ...
[17:14] <El_Presidente> yes he had no problems till that
[17:14] <apw> ok so finding the exact last working ubunru kernel and first non-working ubuntu one would be best
[17:14] <apw> as there are a lot less changes in that range
[17:15] <El_Presidente> okay i will start there
[17:15] <El_Presidente> ty again
[17:23] <El_Presidente> apw, well according to the changelogs there are tons of i915 changes to 35-62
[17:24] <El_Presidente> and below that the first i915 change is on 31-55
[17:25] <El_Presidente> i will check that
[19:14] <catbus1> Dear kernel people, can someone please tell me about what the warn_slowpath_common and warn_slowpath_fmt are about in the kernel call trace?
[19:19] <apw> catbus1, they are just the functions which produce the WARN messages that the caller of those is trying to emit
[19:42] <catbus1> apw: thank you!
[20:31] <cmagina> is the sru-workflow page on kernel.ubuntu.com a good place to watch the status of the current sru kernel?
[23:54] <infinity> zyga: And it starts all over again: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1372685
[23:54] <infinity> Err...
[23:54] <infinity> zyga: Not you.
[23:54] <infinity> zequence: See above. :P