[12:11] <LaserJock> azeem: awesome, now I can upload it to Ubuntu ;-)
[02:06] <bddebian> Heya gang
[02:07] <crimsun> hullo
[02:07] <bddebian> Hail Master crimsun
[02:12] <LaserJock_away> hi bddebian and crimsun
[02:14] <LaserJock_away> in Debian, when a package is built and ready for the mirrors is taken off incoming.debian.org?
[02:15] <crimsun> hullo lj
[02:24] <bddebian> Heya LaserJock_away
[02:24] <LaserJock_away> ewww, 40 KB/s upload
[02:24] <LaserJock_away> this is going to take a while
[02:25] <LaserJock_away> if only I wasn't so cheap :-)
[02:33] <LaserJock_away> hi Hobbsee
[02:35] <Hobbsee> ooh, upgrades!
[02:35] <Hobbsee> hehe
[02:36] <bddebian> Heh
[02:36] <bddebian> Hi Hobbsee
[02:37] <Hobbsee> hi bddebian
[02:37] <Hobbsee> 324kb/s - that's pretty good!
[03:33] <bddebian> Heya Yagisan
[03:36] <Yagisan> G'day bddebian
[03:38] <Yagisan> bddebian: our SDL, is it broken ? I'm trying to debug why I'm getting a "Fatal signal: Segmentation Fault (SDL Parachute Deployed)" from an app I built
[03:38] <bddebian> SDL?
[03:39] <crimsun> our sdl should be fine. What's the bt like?
[03:39] <Yagisan> bddebian: http://www.libsdl.org/index.php
[03:39] <Yagisan> crimsun: I wish I had one atm
[03:40] <bddebian> Yagisan: Ah, thx
[03:40] <dolson> bddebian: I have built SDL apps recently.. should be ok. gdb is your friend and such ;)
[03:40] <dolson> er
[03:40] <dolson> that was for Yagisan
[03:40] <bddebian> :-)
[03:40] <dolson> I wish my update-notifier would work right :\
[03:44] <Yagisan> odd. strace shows it being unable to open libs that exist.
[03:49] <crimsun> permissions?
[03:49] <crimsun> a lot of people seem to have been bitten by the "user not in the audio group" bug lately. I have no idea whether it's rooted in the installer, or...
[03:53] <Yagisan> ah, I see. it wants other libs that sdl should have loaded, but sdl didn't load them because they are not in ia32-libs.
[03:53] <LaserJock> crimsun: you probably won't have any problems from me, I hardly ever use sound
[03:53] <bddebian> Ack, why am I having trouble finding bugs in Universe all the sudden on LP?
[03:53] <Hobbsee> search borked again?
[03:54] <bddebian> Dunno, I'm doing something wrong probably
[03:54] <bddebian> I'm not too smart :-)
[03:55] <LaserJock> maybe we need to put some links on bddebian's special wiki page ;p
[03:55] <LaserJock> so he know where to go
[03:55] <bddebian> Yes
[03:55] <Hobbsee> hehe
[03:55] <crimsun> LaserJock: that's exactly the opposite of what I intend ;)
[03:56] <crimsun> the more people bang on sound, the more I know where to fix stuff
[03:57] <Yagisan> bbl, need to take my son to the doctor
[03:57] <bddebian> Yagisan: Yikes, hope he's OK
[03:57] <crimsun> LaserJock: you haven't had a chance to test dapper on your imac, have you?
[04:00] <crimsun> I'm just happy to have resolved an issue where loading rosegarden in a default config causes the machine to freeze hard
[04:00] <crimsun> nothing like nonexistent error-checking in the kernel :/
[04:03] <bddebian> Oh well guess, I can't fix bugs if I can't find them.. :-)
[04:04] <crimsun> what about unmetdeps? ;)
[04:06] <LaserJock> crimsun: can't. I think I'll have to wait until edgy
[04:07] <bddebian> crimsun: We still have those? :-)
[04:09] <crimsun> LaserJock: k. If you can try the live cd, that would help, too.
[04:10] <LaserJock> hmm, I need some lvm advice
[04:11] <LaserJock> namely, what kind of partitioning scheme should I have
[04:12] <bddebian> crimsun: Seriously, do we have an unmet deps list somewhere?  The wiki one looks like the one from Breezy?
[04:12] <LaserJock> bddebian: I think siretart had something
[04:13] <crimsun> bddebian: besides apt-cache unmet?
[04:14] <LaserJock> bddebian: you might try http://tiber.tauware.de/~siretart/unmet/dapper-unmet.txt
[04:17] <LaserJock> does lvm *not* work for certain things? booting is one I think
[04:18] <bddebian> LaserJock: It used to not work for booting, I dunno if that is still the case or not
[04:19] <crimsun> lvm works fine with lilo.
[04:20] <crimsun> well, unless you sacrifice chickens, but then you probably have more significant issues than lvm
[04:20] <LaserJock> lol
[04:22] <LaserJock> hmm, are there any drawbacks to lvm? I tried googling but that didn't really give me much helpful
[04:23] <crimsun> more pieces to upgrade (installer handles them fine), lilo required, etc.
[04:23] <crimsun> frankly the flexibility afforded by lvm over say, my static install is overwhelming
[04:25] <LaserJock> yeah, I've juggled partitions for the last couple years, but for Dapper I'm going to wipe my drive and start from scratch
[04:25] <LaserJock> you have to use lilo, or can you use grub if you have a regular /boot partition?
[04:25] <Chipzz> why not just use one big partition?
[04:26] <Chipzz> the days when you needed a seperate /boot are long over, no?
[04:26] <LaserJock> Chipzz: well, I prefer grub
[04:27] <Chipzz> and using one big partition prevents you from using grub how?
[04:27] <LaserJock> Chipzz: well that is what I'm unsure of
[04:27] <LaserJock> if lvm plays well with one big partition
[04:27] <Chipzz> I have one big partition on this laptop
[04:27] <Chipzz> well
[04:27] <Chipzz> one big / and then swap ofcourse
[04:28] <LaserJock> and grub?
[04:28] <Chipzz> yes
[04:28] <Chipzz> this disk is only 30GB though
[04:28] <LaserJock> do you have chroots or pbuilders on it?
[04:28] <Chipzz> yes
[04:28] <LaserJock> k, cool
[04:28] <LaserJock> that is sort of what I wanted to know
[04:29] <Chipzz> lvm is nice if you have multiple hd's and want to merge them I guess
[04:29] <LaserJock> I've just never looked at lvm so I'm afraid I'm quite the newb
[04:29] <LaserJock> I just have 1 120GB drive for linux
[04:29] <Chipzz> but I was a bit tired of using a seperate (too small) /, next to seperate /usr etc...
[04:29] <LaserJock> but I often like to resize partitions
[04:30] <Chipzz> ubuntu kernels are quite big :P
[04:30] <crimsun> please, let's not rehash _that_ :)
[04:30] <Chipzz> *g* ;)
[04:30] <Chipzz> but they are :P
[04:31] <crimsun> you can always build your own :)
[04:31] <LaserJock> I don't really care about the size of the kernel
[04:31] <Chipzz> crimsun: doesn't work for me
[04:31] <Chipzz> for some reason baking my own doesn't include the ipw2200 firmware :/
[04:31] <LaserJock> I spent so much time redoing kernels in Gentoo, I like having one that "just works"
[04:32] <Chipzz> LaserJock: make one, then use make oldconfig?
[04:32] <crimsun> when you roll your own, you just need to drop the firmware files in /lib/firmware/$(uname -r)
[04:32] <Chipzz> crimsun: yes, but I want them to be in my kernel deb
[04:32] <crimsun> you don't even need make oldconfig, since /boot/config-$(uname -r) is parsed first
[04:32] <LaserJock> crimsun: cool
[04:36] <Amaranth> stupid xchat python
[04:57] <joelbryan> anyone, what's a good docu to start off packaging easily
[04:58] <LaserJock> joelbryan: doc.ubuntu.com/ubuntu/packagingguide/C/index.html
[04:59] <LaserJock> joelbryan: and then http://www.debian.org/doc/maint-guide/
[04:59] <joelbryan> does it depends on Makefile.am or should I recreate them in debian/rules file?
[05:00] <LaserJock> joelbryan: does what depend?
[05:01] <joelbryan> if I'm going to create a deb package, will dpkg-buildepackage use Makefile.am?
[05:01] <Chipzz> joelbryan: afaik this is not related to dpkg-buildepackage at all
[05:01] <Chipzz> joelbryan: but to automake
[05:02] <Chipzz> joelbryan: normally, the Makefile has rules to check if Makefile.in and Makefile.am or more recent
[05:02] <Chipzz> s/or/are
[05:02] <Chipzz> but you may want to do the regeneration yourself, as you have more control about the version and command-line switches
[05:03] <lifeless> Chipzz: AUTOMAKE_OPTIONS in Makefile.am
[05:03] <lifeless> Chipzz: sets the options
[05:03] <Chipzz> lifeless: and autoconf options etc?
[05:03] <lifeless> Chipzz: set in configure.ac
[05:03] <Chipzz> lifeless: since what version of automake/autoconf ?
[05:03] <lifeless> about the only ones not controllable are -i and -c
[05:04] <joelbryan> because Makefile.am also have rules where to put the package, and debian/rules also, i'm confused.
[05:04] <Chipzz> prolly that was what I was thinking off
[05:04] <lifeless> Chipzz: been improving slowly for ages.
[05:04] <Chipzz> lifeless: so you may not want to rely on that for older versions of autoconf/automake, right?
[05:04] <lifeless> Chipzz: well, thats true.
[05:05] <Chipzz> :)
[07:11] <joelbryan> hello, why do I get License, Blank, when issuing dh_make?
[07:12] <joelbryan> but I copied /usr/share/common-license/GPL-2 to mypackagedir/LICENSE
[07:29] <lifeless> joelbryan: ifI may suggest, it appears you are missing some of the basics about how packaging works. Any of the HOWTO's  or the new maintainer pguide would probably be useful to you
[07:32] <joelbryan> i just figure it out, i should issue -c gpl with dh_make
[07:33] <lifeless> ok, cool
[08:14] <joelbryan> hello, I issue dpkg-buildpackage -rfakeroot, but I got chmod: cannot access build-tree/<package>/configure, but I have src/ directory in the current dir.
[08:14] <joelbryan> I'm sorry, should I unpack the package.tar.gz in the build-tree dir?
[08:16] <joelbryan> should I do it manually or there's a config file in debian/ where I can edit
[08:17] <joelbryan> I'm choose a cdbs package.
[08:22] <LaserJock> joelbryan: maybe you should look at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html and http://www.debian.org/doc/maint-guide/
[09:13] <joelbryan> hello, how can I define my PGP in my package?
[09:57] <crimsun> joelbryan: clarify, please?
[10:43] <\sh> morning
[10:44] <\sh> oh well, it's nice to have something to do during the week :)
[10:50] <nomed> Mithrandir: around ?
[10:54] <Mithrandir> nomed: yes
[10:55] <nomed> is it still possible to get new pkges in universe ?
[10:55] <nomed> Pinot released the version 0.46 ...
[10:55] <nomed> i was waitin for that .. as now it builds using firefox-dev
[10:56] <nomed> and it would be a suitable desktop search app for xubuntu
[10:56] <nomed> not talkin about main just universe (obviously)
[10:58] <joelbryan> hello, in ubuntu, where would /usr/libexec apps be installed?
[11:00] <joelbryan> can I use the /usr/libexec dir for my apps?
[11:01] <lifeless> hi joelbryan. I'm seeing a series of contextless questions from you.
[11:02] <lifeless> maybe we can help you more for packaging if you give us some context.
[11:02] <joelbryan> I mean, where would perl scripts be installed? in /usr/bin?
[11:03] <lifeless> this page http://www.debian.org/doc/packaging-manuals/perl-policy/ describes packaging of perl programs for debian
[11:03] <joelbryan> I'm currently editing my Makefile.am, I have 2 perl scripts and 1 bash, and 1 gtk+ app, I don't know the standards of putting those files, so I use /usr/libexec for my scripts instead.
[11:04] <lifeless> this is why I suggested you might like to read the HOWTO for packaging. Packaging is not complex, but theres lots of little details
[11:04] <lifeless> and starting cold with a new package is hard without guidance :)
[11:04] <lifeless> anyhow, all programs go in /usr/bin
[11:05] <joelbryan> including perl scripts?
[11:05] <lifeless> the program the user runs yes
[11:06] <joelbryan> no, it is run by another app
[11:07] <lifeless> please dont take offense at this, but I don't have the time to do 20-questions-to-package your code. I'm sure some of the MOTU's would be delighted to create ubuntu packages for you, or you *really should* read the guides for new packagers
[11:09] <joelbryan> i learned alot from the docu, I can now capable of creating .deb files from source,  my problem is I have 3 apps that should not be executed, and only 1 app should be executed. I can't find a directory where I can put those 3 apps.
[11:09] <lifeless> have you read the new maintainers guide ?
[11:10] <joelbryan> from debian, currently reading it, from doc.ubuntu.com yes
[11:16] <lifeless> joelbryan: http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA
[11:16] <lifeless> debian mostly follows the FHS
[01:21] <jaldhar> joelbryan: if the script is run by the user it goes in /usr/bin.  If it is only used internally by a program it goes into /usr/lib/<package> if arch-dependent or /usr/share/<package> id arch-independant.  Debian doesn't use /usr/libexec
[01:29] <nomed> raphink: ping
[02:45] <raphink> pong nomed
[02:46] <raphink> nomed: I added you
[02:46] <nomed> raphink: thanks :)
[03:06] <JohnnyMast> where can i download trac hmmm
[03:06] <JohnnyMast> found it
[03:37] <siretart> slomo: around?
[03:37] <slomo> siretart: yes
[03:38] <siretart> slomo: could you please have a look at #27983
[03:38] <siretart> bug #27983
[03:38] <Ubugtu> Malone bug 27983 in openal libopenal0 "libopenal0: openal changed API without adjusting versioning" [Unknown,Unknown]  http://launchpad.net/bugs/27983
[03:38] <siretart> slomo: I have now done the whole transition including test builds, patches and so on to get this through universe
[03:39] <siretart> slomo: do I need a UVF report to start this transition? mdz told me to do so, but this was before it was demoted to universe
[03:39] <slomo> are new upstream versions involved? then yes... otherwise i'm fine without one
[03:40] <siretart> slomo: openal IS a new upstream, freealut used to be a part of openal
[03:40] <siretart> slomo: there are only 2 new upstreams involved: osgal-cvs and openalpp-cvs (both highly unstable development snapshots)
[03:41] <siretart> the rest keeps the upstream versions: xpilot-ng, vegastrike, trigger, torcs, scorched3d, python-openal, flightgear, chromium, boson-base
[03:42] <slomo> hm then better ask dholbach too... i would be fine with the new upstream versions
[03:43] <siretart> slomo: I have them in a local repo right now. amd64 only, because I thought that might be more challanging than i386
[03:43] <siretart> sources + binaries
[03:43] <siretart> only 122mb big :)
[03:45] <slomo> siretart: when they work on amd64 they most probably work on x86 too ;) i trust you that this won't break anything and that any unexpected breakages could be fixed rather fast
[03:45] <siretart> slomo: I've done the whole transistion in a few hours (thanks to reprepro, schroot and sbuild).
[03:46] <siretart> slomo: if you don't have any other concerns, I'd rather not wait for dholbach, because I'd rather like to start this transition quick.
[03:46] <siretart> I mean, I tested it, debian went through it without much hassle
[03:46] <slomo> siretart: ok... so do it then :)
[03:47] <siretart> and regarding osgal-cvs and openalpp-cvs.. well, that are unstable development snapshots
[03:47] <siretart> ok. then lets upoad freealut and openal first. they need both to go through new
[03:49] <phanatic> hi people
[03:49] <siretart> err, even better. they just need to be synced.
[03:56] <phanatic> hi Gloubiboulga
[03:57] <Gloubiboulga> hey phanatic
[04:14] <bddebian> Heya gang
[04:19] <jpatrick> hey bddebian
[04:19] <bddebian> Hello jpatrick
[04:56] <zakame> hi MOTUs
[04:56] <bddebian> Heya zakame
[05:09] <LaserJock> morning all
[05:09] <Gloubiboulga> morning LaserJock
[05:09] <LaserJock> well, I tried out the Beta livecd last night
[05:09] <Gloubiboulga> well, afternoon LaserJock (it's 5pm here)
[05:10] <LaserJock> the livecd is great, espresso is, ummm, difficult
[05:10] <webwolf_27> hi LaserJock
[05:10] <LaserJock> hi Gloubiboulga and webwolf_27
[05:10] <zakame> hello LaserJock Gloubiboulga
[05:10] <LaserJock> hi zakame
[05:10] <webwolf_27> LaserJock, ok, whatever that second word meens
[05:11] <LaserJock> webwolf_27: it is the livecd installer (now called ubiquity, I think)
[05:11] <jpatrick> haha
[05:11] <Gloubiboulga> hi zakame
[05:12] <Gloubiboulga> LaserJock, I've used it with the Xubuntu live cd, it worked just fine
[05:13] <LaserJock> I think I'm going to have to download the regular install cd
[05:13] <webwolf_27> ok, I'm just working on getting the DHCP-client on the notebook setup
[05:20] <phanatic> hi zakame, raphink
[05:21] <LaserJock> hi raphink and bmonty
[05:21] <bmonty> morning LaserJock
[05:21] <raphink> hi phanatic && LaserJock
[05:22] <zakame> hi phanatic raphink bmonty
[05:22] <raphink> hi zakame
[05:23] <zakame> gaah my DhIconCache uploads haven't shown up to now... is it really low priority, or rejected already? :/
[05:23] <crimsun> you haven't gotten any rejection e-mails?
[05:24] <crimsun> if not, are you using the correct key?
[05:24] <zakame> no, no REJECTEDs, and using my only key
[05:27] <crimsun> perhaps ping elmo on Monday
[05:31] <LaserJock> anybody know offhand if the livecd has gparted on it?
[05:33] <LaserJock> so far Dapper Beta is turning into a more frustrating install the Gentoo
[05:34] <nomed> LaserJock: espresso-frontend-gtk depends on gparted
[05:36] <LaserJock> ah, ok. so maybe I can partition everythin in gparted and then run espresso
[05:47] <nomed> LaserJock: gparted is in expresso
[05:47] <nomed> it would be a good test to partition your hd from within it :) .. i guess
[05:47] <LaserJock> that is my problem, I can't get it to partition right
[05:48] <nomed> i've had some problem too ..
[05:48] <nomed> i tried to (re)format  a partition from ext2 to ext3
[05:48] <nomed> the result was the livecd installed on an ext2 fs
[05:49] <LaserJock> I just want to wipe my drive and start over
[05:49] <crimsun> using *parted? and that failed? it's just a tune2fs operation, so that's a pretty silly bug
[05:49] <LaserJock> I was going to do LVM but I don't see any options
[05:49] <LaserJock> and then I tried just setting up regular partitions, and that didn't really work either
[05:49] <LaserJock> so I think I need to partition before I run espresso
[05:51] <nomed> crimsun: once i got the error msg saying the dev was busy
[05:51] <nomed> i'll test the install again with the new livecd
[05:52] <nomed> ahh .. the device was not busy in real .. and not mounted anywhere
[07:10] <bmonty> anyone know how to get rid of a pending merge in bzr?
[07:10] <bmonty> not even sure I know how a merge gets marked as pending
[07:30] <nomed> http://revu.tauware.de/details.py?upid=2294
[07:30] <nomed> could anyone review this pkge ?
[07:41] <\sh> any objecttons if I'm trying again to become a motu? :)
[07:41] <\sh> objections
[07:42] <bmonty> hi \sh!
[07:43] <\sh> hey bmonty
[07:43] <bmonty> \sh: did you stop being an MOTU?
[07:44] <\sh> yes..I removed myself from the dev and core dev team because of private issues
[07:45] <\sh> well, it means, i didn't stop being a motu, but I removed the rights to upload :)
[07:46] <bmonty> well if it was up to me I would re-add you now :)
[07:48] <\sh> no..that I wouldn't want...
[07:48] <\sh> I'll go the way again :)
[11:50] <bddebian> Heya gang
[11:58] <LaserJock> hi bddebian
[11:59] <bddebian> Heya LaserJock


[20:59] <jussi> o/
[21:00] <topyli> \m/
[21:00] <tsimpson> ok..
[21:00] <tsimpson> #startmeeting
[21:00] <MootBot> Meeting started at 15:00. The chair is tsimpson.
[21:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[21:01] <tsimpson> [link] https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[21:01] <MootBot> LINK received:  https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[21:01] <topyli> zarro boogs
[21:01] <tsimpson> [topic] Review last meetings action items
[21:01] <MootBot> New Topic:  Review last meetings action items
[21:02] <tsimpson> [link] https://wiki.ubuntu.com/IRCCouncil/TeamReports/11/March
[21:02] <MootBot> LINK received:  https://wiki.ubuntu.com/IRCCouncil/TeamReports/11/March
[21:03] <tsimpson> jussi: did you get anywhere on "[ACTION] jussi to document thoughts on namespace limits"?
[21:03] <topyli> jussi: have you gotten around to documenting the namespace limits? i suppose you've been a bit distracted by travel
[21:03] <jussi> tsimpson: no, Ive been away and barely had time to think-
[21:04] <tsimpson> I'll put that on the review items for the next meeting then
[21:04] <jussi> thanks
[21:05] <tsimpson> so eir then
[21:05] <topyli> we have feedback
[21:05] <tsimpson> I don't think we got any real objection to its using NOTICEs, so that should be ok
[21:05] <topyli> yeah
[21:06] <tsimpson> I was thinking that, when we enable it, we could use #ubuntu-ops-team for its reporting
[21:06] <tsimpson> that way it can be done in public, but not have everyone read internal comments etc
[21:06] <jussi> that sounds sane to me
[21:06] <topyli> it does
[21:07] <tsimpson> it would probably be better than having everything in /msg, as ubottu does now
[21:07] <jussi> Im a bit out of things, what still needs to be done for integration with ubottu?
[21:08] <tsimpson> mostly some technical issues with getting ubottu to figure out the ban/action ID
[21:08] <topyli> tsimpson: it would be much better, we'd have some "papertrail" even if it's not public
[21:08] <tsimpson> eir just knows "the last ban from <nick>", but it's a little more complex for ubottu
[21:09] <tsimpson> I'm working on having ubottu query eir for the ban, then using that to get the ID
[21:09] <tsimpson> but it's a bit of a pain, especially as our DB is quite large
[21:10] <jussi> Ok. one thing that I do suggest (and Im quite willing to help) is that we make sure the usage is all documented before we implement.
[21:10] <tsimpson> but it's not impossible, just a bit technical to find the "best" way
[21:10] <tsimpson> basically what I'm trying to do is, when eir pokes you for a comment in -team, ubottu will pick up the comment that you give to eir
[21:11] <tsimpson> so you don't have to repeat yourself to ubottu and eir
[21:11] <topyli> sounds good if you can get it working
[21:12] <tsimpson> it may take some fiddling, eir uses ! for commands, where ubottu uses @
[21:12] <tsimpson> but we can mash something together, as !find and !info do now
[21:12] <jussi> ok.
[21:13] <tsimpson> so in general, we agree that, when ubottu is ready, eir should be added to #ubuntu?
[21:13] <jussi> yes
[21:13] <topyli> yes i support it
[21:13] <tsimpson> [agreed] eir to be added to #ubuntu once ubottu interoperates with it
[21:13] <MootBot> AGREED received:  eir to be added to #ubuntu once ubottu interoperates with it
[21:14] <topyli> let's review progress at meetings
[21:14] <jussi> ++
[21:14] <tsimpson> [action] progress review for ubottu-eir interoperability at the next meeting
[21:14] <MootBot> ACTION received:  progress review for ubottu-eir interoperability at the next meeting
[21:14] <tsimpson> :)
[21:14] <topyli> right :)
[21:15] <tsimpson> I think that's all the items from the last meeting
[21:16] <topyli> it also completes our agenda :)
[21:16] <tsimpson> is there anything else anyone wants to discuss?
[21:17] <topyli> oh one thing
[21:17] <topyli> we should ask for ideas for uds
[21:18] <tsimpson> ah, yes
[21:18] <topyli> jussi: you're going there right?
[21:18] <jussi> I mentioned this in -ops a few days back
[21:18] <jussi> topyli: no idea
[21:18] <topyli> oh
[21:18] <jussi> Lets see if they sponsor me
[21:18] <topyli> there is that
[21:19] <topyli> anyway, an email to the list might be a good idea
[21:19] <tsimpson> perhaps we should wait until we find out if one of us is going ;)
[21:19] <topyli> i suppose :)
[21:20] <topyli> however, the ideas will probably find a good place somewhere in the community stream even if we didn't have our own sessions
[21:20] <tsimpson> yeah
[21:20] <jussi> Have either of you applied?
[21:20] <tsimpson> wiki page + email would be my suggestion
[21:20] <tsimpson> well I definitely can't go this year
[21:21] <topyli> i haven't applied
[21:21] <tsimpson> I'm not sure if I'll even be around on irc during UDS
[21:21] <tsimpson> hopefully, but not sure
[21:21] <jussi> topyli: you have 2 days :)
[21:21] <topyli> oh that's plenty! :)
[21:22] <jussi> but yes, I agree with tsimpson - wiki + email should do it
[21:22] <jussi> topyli: http://www.jonobacon.org/2011/02/23/ubuntu-developer-summit-sponsorship-now-open/
[21:22] <tsimpson> who wants to set that up?
[21:23]  * tsimpson gets @random ready
[21:23] <jussi> @random elky nhandler tsimpson topyli jussi
[21:23] <tsimpson> bad bot!
[21:23] <topyli> ha
[21:23] <tsimpson> I guess I'll do that then...
[21:23]  * tsimpson makes a note to blacklist "tsimpson" from @random ;)
[21:24] <jussi> I can help out. (you can be responsible)
[21:24] <topyli> yeah you can write a draft and we'll chip in
[21:24] <tsimpson> there was also #ubuntu-helpteam before I forget again
[21:24] <tsimpson> it's unused
[21:25] <tsimpson> and should be closed/forwarded somewhere useful
[21:25] <jussi> drop it.
[21:25] <tsimpson> @random drop close forward
[21:25] <topyli> haha
[21:25] <tsimpson> the bot agrees, it shall be done
[21:26] <tsimpson> anyone want to do that one?
[21:26] <jussi> I gues just idle there a few weeks as to make sure someone doesnt pick it up
[21:26] <jussi> I can
[21:26] <tsimpson> I've been idling there for a couple of months...
[21:26] <tsimpson> I just keep forgetting to bring it up
[21:27] <jussi> anyway, Im on it
[21:27] <topyli> i don't really know how to drop channels :)
[21:27] <topyli> sounds like a technical thing!
[21:27] <jussi> topyli: /msg chanserv drop #channel
[21:27] <jussi> :P
[21:27] <topyli> oh
[21:28] <tsimpson> we'd want to get staff to do it for us though, we aren't +F
[21:28] <tsimpson> and to give you an idea of how unused it is, it has a link for 8.10 in the topic..
[21:28] <topyli> action nhandler then?
[21:28] <tsimpson> [action] jussi to get staff to drop #ubuntu-helpteam
[21:28] <MootBot> ACTION received:  jussi to get staff to drop #ubuntu-helpteam
[21:28] <jussi> action completed :)
[21:29] <topyli> heh
[21:29] <tsimpson> anything else now that's done?
[21:29] <jussi> [action] Jussi to go to bed.
[21:29] <jussi> :P
[21:30] <topyli> is there something we should do publicly about the rubbish channels?
[21:30] <tsimpson> we were going to mention dropping other channel right?
[21:30] <topyli> yeah
[21:31] <jussi> ahh, yes.
[21:31] <jussi> We should probably mail the list about that
[21:31] <tsimpson> all the obviously off-topic and unused ones should probably just be dropped
[21:32] <tsimpson> we can compile a list of the others and attempt do do something sensible with them
[21:32] <topyli> are there a lot of channels we're uncertain about?
[21:32] <jussi> uncertain?
[21:32] <topyli> whether they're useful or not
[21:33] <tsimpson> well the ones with freenode-staff as founder need sorting
[21:33] <tsimpson> and there are a *lot* of channels to look through
[21:34] <jussi> I would think that if the channel is active and has FS as founder, then need to sort. otherwise, just get them dropped.
[21:34] <tsimpson> we need to go through the list and weed them out, that's going to take some time though
[21:35] <tsimpson> and it's not something I'd like to action to one person ;)
[21:35] <topyli> i wonder if we can get help from ops
[21:35] <topyli> nobody probably *wants* to :)
[21:36] <tsimpson> we can just work our way through them, marking the ones that need dropping, and batch the drops
[21:36] <tsimpson> then go into details of in-use channels later
[21:37] <topyli> i suppose it'll be done sooner or later if we get to it
[21:37] <jussi> I think thats the best way
[21:37] <jussi> We have the document with the list already, so just to start marking them
[21:37] <topyli> yeah
[21:38] <topyli> my new hobby!
[21:38] <jussi> lol
[21:38] <tsimpson> [action] IRCC to drop unused and off-topic channels, and contact other channels with freenode-staff as founder
[21:38] <MootBot> ACTION received:  IRCC to drop unused and off-topic channels, and contact other channels with freenode-staff as founder
[21:38] <jussi> excellent :)
[21:39] <tsimpson> I think that really is all this time
[21:40] <topyli> alright. thanks guys
[21:40] <tsimpson> [action] tsimpson to do post-meeting tasks
[21:40] <MootBot> ACTION received:  tsimpson to do post-meeting tasks
[21:41] <tsimpson> #endmeeting
[21:41] <MootBot> Meeting finished at 15:41.
[21:42] <jussi> thanks lads!
[22:32] <Thermi> gn8


[02:14]  * EvilResistance walks in
[02:14] <EvilResistance> Ubuntu global jam started yet?
[03:05]  * InHisName wanders in after browsing unanswered ubuntu questions to answer.
[03:08] <InHisName> EvilResistance: it started Friday
[03:08] <InHisName> Ends tomorrow
[03:37] <passstab> anyone home?
[03:38]  * InHisName thinks he is home
[03:39] <passstab> would it help to bring a system 76 laptop tomorrow?
[03:40] <passstab> i don't have a spare drive for it
[03:45] <passstab> meh i'll bring it
[03:49] <InHisName> would that be a decendant from IBM system 36  ?
[03:49] <passstab> ...
[03:51] <passstab> http://www.system76.com/index.php/laptops/model/lemur
[03:59] <passstab> good night
[11:06] <InHisName> Good Morning
[14:40] <jedijf> setup and ready at hive76 - come on down - we'll be here til 6pm
[15:13] <jedijf> updating my dell hoping to do some friendly testing
[15:14] <jedijf> you can do friendly testing at home too, dl 12.04 beta1 burn to cd, run live and do system testing - send report - i know each of you have at least 3 boxes you can do!
[15:26] <waltman> I just uploaded my first-ever video to youtube, but I'm not seeing it there. Does it usually take some time to show up?
[15:27] <waltman> At least, iMovie *said* it was uploading it to youtube...
[18:18] <pleia2> jedijf: woohoo!
[19:49] <InHisName> waltman: did your movie show up yet ?
[20:09] <EvilResistance> InHisName, ah, this is what happens when I disappear due to studyi8ng :/
[20:11] <InHisName> bing !   torrent notified me that my 12.04 d/l has completed.
[21:12] <ChinnoDog> pungent pangolin
[21:13] <pangolin> :(
[21:14] <ChinnoDog> That would have been a fun name for an Ubuntu release
[21:35] <EvilResistance> ChinnoDog, lol
[21:55] <waltman> InHisName: http://www.youtube.com/watch?v=qgUjD0Axgjc
[21:55] <waltman> The version I uploaded from iMovie never showed up.  That was sent from my iPhone.
[21:56] <waltman> The iPhone *said* it was uploading as "HD", but the highest quality's only 360p.
[22:01] <ChinnoDog> Your phone lied to you
[22:02] <waltman> :(
[22:03] <ChinnoDog> Are you surprised?
[22:03] <waltman> :(
[22:04] <waltman> Well, "HD (23.0 MB)" seemed odd, considering the full 1080p clip was 237 MB.
[22:18] <rmg51> sound isn't working for me in flash :P
[22:23] <ChinnoDog> I wish there was an open source shared disk file system that was both Linux and Windows compatible
[22:24] <rmg51> don't like fat?
[22:25] <ChinnoDog> fat is not shared disk
[22:25] <ChinnoDog> If I mount that from two operating systems at once it will blow up
[22:25] <ChinnoDog> It will be a grease fire!
[22:26] <rmg51> Microsoft doesn't care about linux
[22:26] <rmg51> not unless linux can close the user gap
[22:27] <ChinnoDog> Shared disk file system developers care about compatibility. There just aren't any that are open source/free with Windows drivers that I can find.
[22:30] <rmg51> that's why I keep separate laptops for linux and windows
[22:31] <ChinnoDog> I don't like lugging around separate laptops.
[22:31] <ChinnoDog> I am not a pack mule
[22:31] <rmg51> I use Teddy for that ;-)
[22:32] <rmg51> any more I just leave the windows box at home
[22:37] <ChinnoDog> poor teddy
[22:37] <rmg51> not really......
[22:38] <ChinnoDog> gobble
[22:38] <rmg51> he expects me to not only carry the laptops but him as well :P
[22:39] <MutantTurkey> weeb wub
[22:39] <MutantTurkey> hit this gym for the first time in a long time
[22:42] <ChinnoDog> You should do a teddy bear case mod so you only have to carry one item instead of two. You can connect the disk lights to LEDs behind teddys eyes.


[04:33] <bandali> hey ginggs you around?
[04:35] <bandali> i was wondering what the common practice is for upstreaming "optional=lto" for symbols files, from ubuntu to debian? do maintainers on the debian side usually welcome it? or are these almost always maintained downstream in ubuntu?
[08:14] <seb128> goood morning desktopers!
[10:09] <sil2100> Hello desktop team! How's .2 testing going?
[13:34] <KGB-0> gjs signed tags 1ba00f8 Jeremy Bicha upstream/1.74.2 * Upstream version 1.74.2 * https://deb.li/qkbc
[13:47] <KGB-2> gjs upstream/1.74.x df76fb2 Jeremy Bicha * pushed 7 commits (first 5 follow) * https://deb.li/38dky
[13:47] <KGB-2> gjs upstream/1.74.x 35e1d81 Philip Chimento gi/function.h * function: Add missing include * https://deb.li/HdSd
[13:47] <KGB-2> gjs upstream/1.74.x 4bfdaa1 Philip Chimento test/gjs-tests.cpp * tests: Avoid using char type in uniform_int_distribution<T> template * https://deb.li/3SNXV
[13:48] <KGB-2> gjs upstream/1.74.x 26ddbcf Philip Chimento gi/gobject.cpp installed-tests/js/testIntrospection.js * gobject: Guard against null JS wrapper in set/get property * https://deb.li/NG91
[13:48] <KGB-2> gjs upstream/1.74.x fd51270 Valentin David util/log.cpp * log: Fix an off-by-one buffer overflow * https://deb.li/i3kWN
[13:48] <KGB-2> gjs upstream/1.74.x 978f232 Philip Chimento meson.build * build: Pre-release version bump * https://deb.li/2GNR
[13:48] <KGB-0> gjs upstream/latest dbaec89 Jeremy Bicha * pushed 131 commits (first 5 follow) * https://deb.li/3x0zI
[13:48] <KGB-0> gjs upstream/latest 2079e0e Philip Chimento installed-tests/js/meson.build * CI: Put testGtk4.js in 'dbus' suite * https://deb.li/bvDE
[13:48] <KGB-0> gjs upstream/latest 92f7a45 Philip Chimento (9 files in 5 dirs) * Merge branch 'december-maintenance' into 'master' * https://deb.li/3vUse
[13:48] <KGB-0> gjs upstream/latest 2e5fe3d Marco Trevisan (Treviño) installed-tests/js/testSignals.js modules/core/_signals.js modules/script/signals.js * signals: Simulate GObject's connect_after behavior on signals * https://deb.li/hwjD
[13:48] <KGB-0> gjs upstream/latest 146787f Philip Chimento installed-tests/js/testSignals.js modules/core/_signals.js modules/script/signals.js * Merge branch 'legacy-signals-connect-after' into 'master' * https://deb.li/3Cfvz
[13:48] <KGB-0> gjs upstream/latest abcff91 Evan Welsh (6 files in 2 dirs) * Introduce runAsync() to run main loops without blocking module resolution * https://deb.li/oHRR
[14:07] <jbicha> seb128: https://salsa.debian.org/gnome-team/rhythmbox/-/merge_requests/2 does this sound ok with you?
[14:07] -ubottu:#ubuntu-desktop- Merge 2 in gnome-team/rhythmbox "Disable ipod plugin" [Opened]
[14:34] <seb128> jbicha, it's suboptimal but might be ok... we could try this cycle and see what's the feedback
[14:40] <ginggs> bandali: I haven't tried sending an "optional=lto" type patch to Debian yet.  I'd guess these would be ignored because "FTBFS with LTO" is not RC in Debian, and they're entering their freeze for bookworm
[14:47] <jbicha> seb128: I suspect if we drop libgpod to Universe, we might not get it back
[14:48] <seb128> well, don't merge that change back to Ubuntu yet, please put a card in the backlog, I need to properly check what's the issue because I'm not sure ot understand
[14:49] <seb128> having to bump the soname with every update doesn't seem like a reason to remove it
[14:49] <seb128> neither is the fact that it's unmaintained if it's working and allows us to support hardware our users own
[14:56] <KGB-0> rhythmbox Jeremy Bicha 383677 * commented merge request !2 * https://deb.li/3hyZG
[15:14] <KGB-0> rhythmbox Andreas Henriksson 383679 * commented merge request !2 * https://deb.li/ikjXF
[15:22] <KGB-2> rhythmbox Jeremy Bicha 383681 * commented merge request !2 * https://deb.li/i7gIE
[17:42]  * luna used plain Ubuntu at the new job for the first time today :)
[18:54] <bandali> ginggs, ack, thank you
[20:22] <KGB-0> xdg-desktop-portal-gnome pipeline Jeremy Bicha 503413 * pending (piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build i386: created; extract-source: pending; build source: created; build: created)
[20:22] <KGB-2> xdg-desktop-portal-gnome pipeline Jeremy Bicha 503413 * running (extract-source: running; piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build i386: created; build source: created; build: created)
[20:30] <KGB-2> xdg-desktop-portal-gnome pipeline Jeremy Bicha 503413 * [7 minutes and 39 seconds] success (reprotest: success; piuparts: success; autopkgtest: success; test-build-any: success; test-crossbuild-arm64: failed; lintian: success; blhc: success; test-build-all: success; build i386: success; build: success; build source: success; extract-source: success)
[22:15] <KGB-2> gnome-builder upstream/latest e860ad7 Jeremy Bicha * pushed 676 commits (first 5 follow) * https://deb.li/FbQi
[22:15] <KGB-2> gnome-builder upstream/latest 95f0979 Christian Hergert src/plugins/shortcutui/ gbp-shortcutui-dialog.c gbp-shortcutui-dialog.h gbp-shortcutui-row.c gbp-shortcutui-tweaks-addin.c * plugins/shortcutui: give row access to observer * https://deb.li/3dX9h
[22:15] <KGB-2> gnome-builder upstream/latest 6f00ee1 Christian Hergert src/plugins/shortcutui/ gbp-shortcutui-dialog.c gbp-shortcutui-row.c gbp-shortcutui-row.h * plugins/shortcutui: plumb access to action to setter * https://deb.li/uBS2
[22:15] <KGB-2> gnome-builder upstream/latest 421aa22 Yosef Or Boczko po/he.po * Update Hebrew translation * https://deb.li/i4OXC
[22:16] <KGB-2> gnome-builder upstream/latest bcfd875 Kukuh Syafaat po/id.po * Update Indonesian translation * https://deb.li/WB1g
[22:16] <KGB-2> gnome-builder upstream/latest 333c5d3 Hugo Carvalho po/pt.po * Update Portuguese translation * https://deb.li/3F2xl
[22:16] <KGB-2> gnome-builder pristine-tar e8681bf Jeremy Bicha gnome-builder_44~beta.orig.tar.xz.delta gnome-builder_44~beta.orig.tar.xz.id * pristine-tar data for gnome-builder_44~beta.orig.tar.xz * https://deb.li/AXNx


[19:54] <yigal> is this room still active, I see the topic was set last year?
[19:59] <yigal> right, good to know


 I see the contents of parent dir of the actual dir instead of the contents of parent of the symlink. why? and how to change this behavior?
[18:55] <rick_h_> jrwren: add a / to the dir?
[18:55] <jrwren> rick_h_: same behavior.
[18:55] <jrwren> maybe shells always did this and I just never realized.
[18:56] <cmaloney> jrwren: Yeah, it's a pita
[18:57] <cmaloney> But it's working as expected
[18:57] <jrwren> lol. I can't believe in 20yrs I never noticed.
[18:57] <cmaloney> UNIX is the onion that keeps on peeling
[18:58] <cmaloney> and sometimes drives the tears if you're not careful
[18:58] <jrwren> *grumble*
[18:58] <jrwren> I mean, I noticed yrs ago and thought it was a bash setting I had screwed up.
[18:58] <jrwren> hrm... shit, now I i'm remembering something about the UFS paper mentioning it.
[18:58] <jrwren> its in the UFS paper that first introduced symlinks, isn't it?
[18:59]  * jrwren dies.
[18:59] <jrwren> I think I'm just having a bad day.
[18:59] <jrwren> nevermind me.
[18:59] <cmaloney> Even better: pwd will blow your mind
[18:59] <jrwren> how so?
[18:59] <cmaloney> craig@lister:~/tmp$ pwd
[18:59] <cmaloney> /home/craig/tmp
[18:59] <jrwren> that doesn't blow my mind.
[18:59] <cmaloney> lrwxrwxrwx 1 craig craig 4 Nov  9  2012 tmp -> /tmp
[19:00] <cmaloney> no?
[19:00] <cmaloney> not even a little?
[19:00] <jrwren> nope
[19:00] <jrwren> sorry.
[19:00] <cmaloney> (not even a little kid's cap gun boom?")
[19:01] <cmaloney> Then why did the .. in cwd blow your mind? :)
[19:01] <jrwren> because I could have sworn it was configurable behavior.
[19:02] <cmaloney> ah
[19:02] <jrwren> but... maybe it is because I had previously run with set -P and so if I cd into a symlink dir it resolved the symlink and took me there.
[19:02] <cmaloney> That's possible
[19:02] <cmaloney> Or you were naughty and used hard links.
[19:03] <jrwren> can you hardlink a dir?
[19:03] <jrwren> hard link not allowed for directory
[19:03] <cmaloney>        -d, -F, --directory
[19:03] <cmaloney>               allow the superuser to attempt to hard link directories (note: will probably fail due to system restrictions, even
[19:04] <cmaloney>               for the superuser)
[19:04] <jrwren> ah, naughty
[19:04] <jrwren> Operation not permitted
[19:04] <jrwren> i guess ext4 doesn't support them.


[00:04] <jsalisbury> bjf, I'm pinging bdmurray and the landscape team now.
[00:05] <jsalisbury> bjf, s/landscape/launchpad/ :-)
[00:05] <bdmurray> about what?
[00:06] <jsalisbury> bdmurray, do you know whether the lp expiration bot is running? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/399911 looks like it should have expired a while ago.
[00:06] <ubot2> Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete]
[00:06] <jsalisbury> bdmurray, from my understanding launcpad itself expires bugs, versus manual bots.
[00:06] <jsalisbury> bdmuarry, s/manual bots/bots we create/
[00:06] <bdmurray> jsalisbury: yes the launchpad janitor expires bug reports
[00:07] <bdmurray> jsalisbury: I'd expect to see "This bug can expire in xyz days" on the page
[00:08] <bdmurray> jsalisbury: for example in bug 846652 you can see this
[00:08] <ubot2> Launchpad bug 846652 in xserver-xorg-video-intel "Screen shifted right and incorrect refresh rate when switching VTs and unsuspending" [High,Incomplete] https://launchpad.net/bugs/846652
[00:08] <jsalisbury> bdmurray, could there be a bug in the expiration janitor?  Does it only trigger off of an incomplete status
[00:08] <bdmurray> jsalisbury: it must be incomplete and a not match a few other criteria
[00:09] <jsalisbury> bdmurray, yeah, maybe the number of affected people has something to do with it?
[00:09] <bdmurray> jsalisbury: that criteria is listed at https://help.launchpad.net/BugExpiry
[00:09] <bdmurray> jsalisbury: no its not that I'm thinking / looking at it
[00:09] <jsalisbury> bdmurray, thanks for the link, I'll take a look at that page.
[00:10] <bdmurray> jsalisbury: I don't see anything my only thought is it might be because date_incomplete is so old
[00:12] <jsalisbury> bdmurray, you think because it was set to incomplete back on 2009-12-10, and maybe the expiration logic was different then?
[00:14] <bdmurray> jsalisbury: no that maybe the janitor only looks at date_incomplete within the past 90 days ... I'm grasping at straws though
[00:15] <jsalisbury> bdmurray, I wonder what would happened if I marked the bug as confirmed then incomplete again?
[00:15] <bdmurray> jsalisbury: there is a bug.isExpirable method that returns False
[00:15] <bdmurray> well you'd have to wait 90 days for the actual expiration to happen
[00:16] <jsalisbury> bdmurray, I also noticed the background for Incomplete in bug 399911 is a brighter yellow compared to incomplete say in bug 846652, not sure if that actually means anything
[00:16] <ubot2> Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete] https://launchpad.net/bugs/399911
[00:16] <ubot2> Launchpad bug 846652 in xserver-xorg-video-intel "Screen shifted right and incorrect refresh rate when switching VTs and unsuspending" [High,Incomplete] https://launchpad.net/bugs/846652
[00:17] <bdmurray> jsalisbury: don't think so
[00:18] <jsalisbury> bdmurray, do you have a script, or is that one in arsenal that you used to pull the bug.isExpirable method?
[00:18] <jsalisbury> bdmurray, I guess I could just write a quick one.
[00:19] <bdmurray> jsalisbury: I just used ipython to check on that bug
[00:20] <jsalisbury> bdmurray, ahh, ok.  I wonder if it has anything to do with being assigned to someone, then reassigned to nobody.
[00:21] <jsalisbury> bdmurray, bjf, I'll dig further and maybe see if someone on the launchpad team knows.
[00:21] <bdmurray> oh, I've an idea now
[00:21] <jsalisbury> :-)
[00:23] <bdmurray> jsalisbury: I'm pretty sure its because the status for 846652 is "Incomplete w/o response" and the status for 399911 is just "Incomplete"
[00:24] <bdmurray> jsalisbury: and the API only tells you that they are Incomplete
[00:25] <jsalisbury> bdmurray, I'm not sure I understand the "Incomplete w/o response", Are comments in the bug not responses?
[00:25] <jsalisbury> bdmurray, or is it comments added after the bug was marked Incomplete?
[00:26] <bdmurray> the latter
[00:26] <jsalisbury> bdmurray, ahh, ok.
[00:28] <jsalisbury> bdmurray, and once a bug has a response after marked incomplete, it looks like it can't be forced to expire.  For bug 399911, I marked it confirmed, then incomplete again, and the message "This bug report will be marked for expiration in N" did not show up.
[00:28] <ubot2> Launchpad bug 399911 in linux "samsung x360 fn-keys work incorrectly" [Medium,Incomplete] https://launchpad.net/bugs/399911
[00:29] <jsalisbury> bdmurray, oh wait, I also see that that bug has a duplicate!
[00:30] <jsalisbury> bdmurray, but the Expiry page says that the bug must be a duplicate itself not to expire :-/
[00:30] <bdmurray> jsalisbury: having a duplicate isn't a factor
[00:30] <jsalisbury> right
[01:17] <martijn> Quick question, forgive the newbie on this, I'm trying to get the ubuntu kernel to diagnose a USB driver issue I'm having, but I run into "fatal: The remote end hung up unexpectedly" when git clone'ing from kernel.ubuntu.com - is this something really obvious I should know about?
[01:18] <martijn> (cmd was: git clone git://kernel.ubuntu.com/ubuntu/ubuntu-oneiric.git lixsrc )
[01:18] <martijn> (now trying git clone http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-oneiric.git -- will post here when/if that fails, not aware of any firewall issues between me and the inet)
[01:27] <martijn> (USB issue in question is isochronous URB reception seems to not work from userland, my suspicion is a problem in drivers/usb/core/devio.c line 1347 processcompl() and I'd like to add some printk's there to diagnose.. but that requires the kernel.)
[01:43] <bjf> martijn: there is something wrong with kernel.ubuntu.com right now
[01:44] <martijn> bjf: Thanks for the response! does the http request have any hope of succeeding or should I retry tomorrow?
[01:45] <bjf> martijn: i think there is no hope right now
[01:46] <martijn> Assuming that statement is limited to kernel.ubuntu.com, I'll try again tomorrow - thanks for the info & good luck to who is working on fixing it.
[01:59] <martijn> (http also failed as expected, tomorrow!)
[02:07] <T3CHKOMMIE> hey guys. i need some help with a kernel project im doing. Im having the hardest time and ive spent well over 40 hours trying to figure this crap out. i feel like I am missing just a small piece of the puzzel.... can someone help me?
[02:17] <T3CHKOMMIE> maybe someone can help me. i downloaded ubuntu kernel from source. did a make menuconfig and tweaked it how i liked. then did a make...
[02:17] <T3CHKOMMIE> im pretty sure that compiled the kernel. now im just trying to get it to an install CD so i can install it on my test machine. can anyone help me?
[03:15] <T3CHKOMMIE> hey guys, i still cant figure out how to "use" a kernel. i compiled one and cant figure out how to get it working. i tried using UCK and that was a miserable failure. has anyone compliled their own kernel?
[03:29] <T3CHKOMMIE> anyone?
[06:09] <semitones> hello, valorie suggested I come here from #kubuntu to ask about my bug
[06:09] <semitones> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/888415
[06:09] <ubot2> Launchpad bug 888415 in pulseaudio "Speakers do not mute when headphone jack is in use. Multimedia keys unmute speakers." [Undecided,New]
[06:09] <semitones> she said it ended up being a kernel problem for her
[06:12] <semitones> let me know if that sounds familiar -- I can idle here for a while :)
[10:44] <diwic> bjf, if you're awake - I'm trying out your kernel scripts (the alsa cod), but when try to "make source", it fails with "file not found: source/debian/control". What is the correct way to fix this problem? I notice that there is no debian/control, but debian/control.stub.in, debian/control-scripts, and control.d/
[10:44] <diwic> all exists in the debian directory
[10:48] <diwic> aha, "fakeroot debian/rules debian/control" did the trick
[11:48] <apw> diwic, likely you really wanted fakeroot debian/rules clean
[11:48] <apw> that creates all the transient debian stuff
[11:48] <diwic> apw, aha, thanks
[11:48] <apw> else you won't have a changelog later in the process
[11:49] <apw> semitones, yep that is likely a kernel issue
[11:49] <apw> diwic, do we have a good debugging guide for jack problems
[11:50] <diwic> apw, eh
[11:50] <diwic> apw, could you specify "jack problems" a little
[11:51] <apw> diwic, classic is "i insert headphones and speakers don't turn off"
[11:51] <apw> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/888415
[11:51] <ubot2> Launchpad bug 888415 in pulseaudio "Speakers do not mute when headphone jack is in use. Multimedia keys unmute speakers." [Undecided,New]
[11:51] <apw> is one we got asked about in scrollback last night
[11:51] <diwic> apw, only one of 84 open bugs for pulseaudio :-/
[11:52] <apw> heh yeah, i assume its more likely a kernel issue in this case right ?
[11:52] <apw> semitones, is this machine reallly running maverick ?
[11:52] <diwic> apw, probably, but determing that is non-trivial
[11:53] <apw> diwic, so pulse also takes a hand in jack handling ?
[11:53] <diwic> apw, hmm, since oneiric it does, but if this is maverick, it's definitely kernel
[11:54] <apw> oh ... thats news, i am unsure i want to know how pulse is involved ... yeeks
[11:54] <apw> diwic, i'll shove it over to kernel anyhow, then it can be 1/6k bugs and even more lost
[11:54] <diwic> telling user to try https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
[11:56]  * apw tells them to test an oneiric liveCD
[11:57] <diwic> heh
[11:57] <diwic> either should be just fine.
[11:57] <apw> diwic, thanks
[11:58] <apw> man maverick seems like so long ago, and yet its only a year
[12:01] <apw> diwic, i note that all of those dkms packages failed to build on i386
[12:02] <diwic> apw, fixed today, but yeah, maybe I should trigger a new build
[12:02] <diwic> apw, is this something to worry about: "package linux-alsa-driver-modules-oneiric-generic in control file but not in files list"
[12:03] <apw> its poor on our behalf but likely not an issue that stops you, thats an lbm package
[12:03] <apw> oh are you trying to start up auto builds of alsa for oneiric ?
[12:04] <apw> i suspect lbm doesn't have an alsa backport in it yet which would lead to that error
[12:04] <apw> it'd all be commented out, still in there but off
[12:08] <diwic> apw, yeah, I started off with bjf's tree for cod-natty and trying to make something launchpad based for oneiric
[12:08] <diwic> apw, as bjf's stuff is non-existent for oneiric and broken for the older
[12:18] <apw> diwic, nice, so yeah it may well be we have no alsa in lbm if that is what you are using
[12:18] <apw> though how would that differ from your dkms package ?
[12:18] <apw> if you used that against the crack of the day alsa tree ?
[12:19] <diwic> they use the same source, the dkms package is for snd-hda-* modules only and is dkms based
[12:19] <diwic> if you need all modules (i e testing something different than HDA Intel cards you'll need the full sound tree
[12:19] <apw> ahh yes, there is a lot more poo in there
[13:13] <brendand> smb - sorry to bother you, but if i were to use 'skipabi' where would i put it?
[13:14] <smb> brendand, depends a bit on what command you use to run the build I believe
[13:15] <smb> I use it rarely so it is easy to forget. Would skipabi=true dpkg-buildpackage -b ... work?
[13:15] <brendand> the instructions i am using use debian/rules
[13:16]  * smb thinks there both "skipabi=true debian/rules ..." and "debian/rules skipabi=true ..." may work
[13:19] <smb> brendand, Seems right. You can use debian/rules printenv to check what settings get used
[13:25] <brendand> smb - great, trying that now
[14:45] <ogasawara> apw, tgardner: I'm trying to remember bits from UDS, wasn't there discussion about building in SATA_AHCI?
[14:46] <tgardner> ogasawara, yep, in fact that is what I set out to do, but got confused with xhci instated.
[14:46] <apw> ogasawara, there was confusingly conversations about XHCI for usb3 and ahci as its the common sata.  they got conflated at times
[14:46] <tgardner> instead*
[14:46] <apw> ogasawara, overall though i think we should move that one boot essential
[14:46] <apw> tgardner, indeed :)
[14:47] <tgardner> ogasawara, i did build in xhci in precise though. we'll need to make sure it doesn't break suspend
[14:47] <ogasawara> tgardner: ack
[14:47]  * apw is just doing some of those annotations as it happens
[14:47] <ogasawara> apw: I'll add it as a work item so we don't forget
[14:47] <apw> ogasawara, cool thanks
[15:14]  * tgardner pours gas into ubuntu-devel
[15:15] <Kiall> Hiya - I'm trying to figure out the cause of a kernel panic, anyone about to understand the logs? ;) http://dl.dropbox.com/u/1400487/panic/IMG_20111026_040053.jpg
[15:17]  * ogasawara back in 20
[15:17] <apw> Kiall, from the log that looks like a problem in a combination use of bridging and netfilter
[15:17] <apw> Kiall, what release is this on as the kernel version is off the top on that dump
[15:18] <apw> smb, didn't we have a problem in a stable update recently in this area ?
[15:18] <apw> tgardner, ^
[15:18] <Kiall> apw: Mine is running 3.0.0-13-server on oneiric
[15:18] <smb> apw, Nothing I know of...
[15:19] <tgardner> Kiall, you have bridging enabled with iptables rules ?
[15:20] <Kiall> tgardner: yes
[15:20] <tgardner> apw, IIRC it was netfilter and lxc that had issues
[15:20] <Kiall> Its a server running OpenStack, So a combination of VLAN's, NF, Bridging and KVM (ie .. everything)
[15:21] <tgardner> Kiall, a VPN with tun/tap ?
[15:21] <Kiall> No - no VPN involved
[15:21] <Kiall> I think the tap is KVM
[15:21] <apw> its the bridge for kvm then in this case
[15:21] <tgardner> Kiall, right. I haven't setup KVM in awhile
[15:22] <tgardner> Kiall, what net filters are you using ?
[15:23] <apw> Kiall, was this the host or the VM that dumped
[15:23] <Kiall> apw: the host
[15:23] <tgardner> apw, only yhte host can see the bridge
[15:23] <apw> tgardner, point
[15:24] <Kiall> tgardner: DNAT, SNAT, and standard accept/deny rules..
[15:24] <tgardner> Kiall, nothing particularly dangerous there
[15:24] <apw> so this is a NAT bridge not a native one (that how virtmanager talks about it)
[15:25] <apw> so ... he is running a v3.0.6 base, so it'd be worth a scan of everything in stable after
[15:25] <tgardner> Kiall, is this a recent change in behavior ? and how often does it happen ?
[15:26] <Kiall> I've seen it twice, and I've just found another person who's its just happened to..
[15:26] <Kiall> Obviously, Oneiric installs so they haven’t had very long lives yet
[15:26] <apw> cirtianly worth getting a bug filed with that on it, we are bound to see it plenty as well
[15:29] <Kiall> yea, will do
[15:31] <apw> if you can reproduce it i'd like to know if its there in -12, though i suspect it is
[15:32]  * smb wonders wehter the 200+ patches pending on 3.0.y will help or do worse...
[15:32] <Kiall> Standard traffic seems to trigger it, but I haven't figured out what traffic in particular :(
[15:33] <apw> smb, yeah
[15:56] <tgardner> ogasawara, did 3.1 compat-wireless for Lucid stay on your list ?
[15:57] <ogasawara> tgardner: it did, was planning to get to it today or tomorrow.
[15:57] <tgardner> ogasawara, np, thanks
[15:57] <smb> Wasn't tomorrow a holiday over there?
[15:57] <apw> ogasawara, also do we have an alsa backport in oneiric yet ?
[15:58] <ogasawara> smb: it is, but I'm planning to swap it for another day
[15:58] <tgardner> smb, yep
[15:58] <smb> ah ok
[15:59] <ogasawara> apw: we don't
[15:59] <apw> i assume we should now/soon, i wonder if thats on -stable's radar
[16:01] <ogasawara> apw: do we have a strong need for an updated alsa in oneiric?
[16:01] <apw> a good question indeed
[16:05] <bjf> apw, did we have a backported alsa for maverick or natty ?
[16:06] <tgardner> I'm thinking we should only bother with backports to the current release and Lucid.
[16:06] <tgardner> backports being compat-wireless and possible alsa
[16:06] <tgardner> possibly*
[16:07] <apw> so current == oneiric right now ?
[16:07] <apw> bjf, another good question
[16:07] <bjf> tgardner: my question was more along the lines of, "do we regularly backport alsa to N-1?"
[16:07] <tgardner> on the other hand, with the LTS kernels, does it make sense to backport anything to Lucid ?
[16:07]  * apw was thinking the same as tgardner on lucid
[16:10] <tgardner> apw, thats one more bit of maintenance that we could shed
[16:11] <apw> if we are doiing the work to support backports then they should be sufficient in theory
[16:11] <apw> i guess the only question is whether we get alsa/wireless backports sooner than the 'next' kernel
[16:12] <apw> as they are synced to upstream releases and not ours
[16:12] <tgardner> apw, I'm sure I care about a 3 month gap
[16:12] <tgardner> I'm *not* sure
[16:12]  * apw has assumed sarcasm
[16:13]  * ppisati bails for a bit
[16:13]  * smb would be using alsa backports at least on his media pc... I could probably change to an LTS backports kernel. But assumes much whining about any support that gets dropped
[16:20] <tgardner> apw, ogasawara: whats the story on powerpc flavours ? can we drop support for the old Apple G4 ?
[16:21] <ogasawara> tgardner: I think we were meant to chat with lifeless and jk about it
[16:21] <apw> tgardner, is that the 32bit non-smp job?  didn't jk do some work to confirm we didn't really need that
[16:21] <apw> ogasawara, get a WI made perhaps then we won't forget
[16:21] <ogasawara> tgardner: bah, not lifeless, luke
[16:22] <tgardner> can you guys run that ground ?
[16:22] <apw> ogasawara, i am thinking we want to resurect our power blueprint so that cking's work is visible
[16:22] <tgardner> that to ground *
[16:22] <apw> ogasawara, also i suspect we are going to have some work on boot speed which i suspect i'll want to make a new bleuprint to track; see any problems with me doing that
[16:23] <ogasawara> apw: sounds fine
[16:23] <cking> apw, that sounds like a good idea - needs to be trackable
[16:23] <apw> cking, have you done your WIs for your stuff yet ?
[16:23] <ogasawara> cking: let me see if I can find that blueprint
[16:23] <apw> ogasawara, it was power-management or something
[16:23] <cking> apw, nope, I'm draining my HWE worklist this week
[16:23] <apw> cking, ok
[16:23] <cking> all 37 mins left of it
[16:24] <apw> cking, :)
[16:24] <cking> not that I'm counting ;-)
[16:24] <apw> rm HWE-TODO
[16:24] <cking> oh yeah
[16:24] <apw> sleep 2160; rm HWE-TODO
[16:40] <ogasawara> cking: I couldn't find the existing one so I just made you a new blueprint.  I'll let you fill it in accordingly.  https://blueprints.launchpad.net/ubuntu/+spec/hardware-p-kernel-power-management
[16:49] <cnd> bjf, do we still pull everything from upstream stable releases?
[16:49] <cnd> I've got a patch that is working its way through stable for macbook trackpads
[16:50] <tgardner> cnd, yes
[16:50] <bjf> cnd, yes
[16:50] <cnd> ok, thanks
[16:50] <bjf> cnd, which release you hoping it gets into ?
[16:50] <cking> ogasawara, thanks
[16:50] <cnd> bjf, it's in the review for the next one
[16:50] <cnd> 3.0.9 I think?
[16:50] <bjf> cnd, ok, oneiric then, yes we will pick that up
[16:51] <cnd> ok
[17:06] <bullgard4> http://kernelnewbies.org/Linux_2_6_26: "2.6.26 adds support for ... BDI statistics and parameters exposure in /sys/class/bdi, ... Linux 2.6.24 merged per-device dirty thresholds: The limits that the kernel put to the amount of memory that a process can "dirty" changed from being global to be per-device. 2.6.26 exposes a interface in /sys/class/bdi that allow to set several parameters....
[17:06] <bullgard4> ...There's another set of read-only parameters that are exposet in debugfs (debug/bdi/<bdi>/stats) " What does »BDI« stand for?
[17:14] <tgardner> bullgard4, block device interface ?
[17:14] <cnd> bullgard4, probably a debugger used for doing low level hardware bringup
[17:14] <cnd> wait, nm, that doesn't make sense given the rest of the comment
[17:14] <cnd> unless they are unrelated
[17:27] <smb> Documentation/ABI/testing/sysfs.class-bdi: "Provide a place in sysfs for the backing_dev_info object."
[17:31] <bullgard4> tgardner, cnd, smb: Thank you very much for your help. --  I will continue snooping.
[17:44] <broder> how frozen is the upstream kernel during the rc period? i have a patch i'd like to see get in (http://paste.ubuntu.com/734424/, based on https://lkml.org/lkml/2010/3/10/188), but i've never interacted with the lkml before and don't really know what i'm doing
[17:46] <broder> err, http://paste.ubuntu.com/734429/ would be the one actually rebased onto master, but whatever
[17:55] <tgardner> broder, you'll likely need to run it past the list and the maintainer.
[17:55] <tgardner> rtg@lochsa:~/proj/linux/linux-2.6$ scripts/get_maintainer.pl -f drivers/leds/led-class.c
[17:55] <tgardner> Richard Purdie<EMAIL_ADDRESS>(maintainer:LED SUBSYSTEM)
[17:55] <tgardner><EMAIL_ADDRESS>(open list)
[17:56] <broder> so just send it off and hope for the best? :)
[17:56] <tgardner> broder, you should check with Samuel Thibault that it hasn't already been reviewed
[17:57] <broder> tgardner: ok, thanks for the pointers
[18:52]  * tgardner -> lunch
[19:23] <tgardner> apw, ogasawara: can you remember any reason why CONFIG_MEMSTICK_R592 is not enabled in either Oneiric or Precise ?
[19:23] <ogasawara> tgardner: no idea
[19:24] <apw> tgardner, nothing jumps out at me, its not in any of our groups we check regularly
[19:24] <tgardner> seems like it should have popped up in our config review
[19:24] <apw> it may be one we have on our list for review
[19:24] <tgardner> apw, well, we clearly missed it in oneiric
[19:25] <tgardner> bug #238208
[19:25] <apw> we didn't have the same tooling in oneiric, but ogasawara lets add a wi to investifate it
[19:25] <ubot2> Launchpad bug 238208 in linux "Need MemoryStick driver Ricoh R5C592 (part of R5C832/822chipset)" [Wishlist,Confirmed] https://launchpad.net/bugs/238208
[19:25] <ogasawara> apw: ack
[19:25] <tgardner> apw, I'm just gonna write a patch to enable it.
[19:29] <GrueMaster> bjf: Erm, arm Lucid is EOL.  No need for Bug 888698 .
[19:29] <ubot2> Launchpad bug 888698 in linux-fsl-imx51 "linux-fsl-imx51: <version to be filled> -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/888698
[19:29] <apw> || CONFIG_MEMSTICK_R592 || n || n || n || - || - || n || n || n || n || n || n ||  '''EXPERIMENTAL''' ||
[19:29] <apw> GrueMaster, until the buildd's are transitioned off on to panda we are stuck with supporting them
[19:29] <GrueMaster> grmbl.
[19:30] <apw> GrueMaster, they have _told_ me 'weeks', we shall see
[19:30] <tgardner> apw, isn't that inconsistent with policy ?
[19:30] <apw> tgardner, its experimental and not special cased
[19:31] <apw> if the option is dependent on EXPERIMENTAL then our normal policy is to not enable it,
[19:31] <tgardner> apw, oh, I thought we _were_ turning on experimental options if they were modules.
[19:31] <tgardner> we sure seem to have turned on a bunch so far
[19:31] <apw> we have tended to if they are very definatly only going to pop up with hardware
[19:32] <tgardner> well, this one counts then
[19:32] <apw> yep, and it sounds like MEMSTICK_* is a class of exceptions
[19:33] <apw> tgardner, its a bit frightening if that option has been available since jaunty and still EXP
[19:34] <tgardner> if it breaks, I'll let 'em keep both pieces
[19:35] <apw> yep
[19:35] <apw> i'm going through the annotations so i'll look see if there are any more patterns
[19:36] <apw> ogasawara, as we'll nearly be on final kernel by rally, do we want to have a re-config review, as we already have new problems introduced by -rc2.  i'll be adding WIs for them shortly
[19:36] <apw> (at rally)
[19:36] <ogasawara> apw: sounds like a good idea
[19:37] <apw> ogasawara, added to the agenda
[19:37] <ogasawara> apw: thanks
[19:38] <bjf> apw, have we reached out to upstream stable to see if they have any plans to support 3.2 ?
[19:38] <bjf> apw, also, have you heard anything about bugzilla.kernel.org coming back ?
[19:39] <apw> bjf, the only thing i've heard in that space is what jjohansen said about 'one per year' and i think that means we miss
[19:40] <apw> bjf, not heard a thing on bugzilla, though as people are only just getting back on at all i am not supprised
[19:40] <jjohansen> apw: I don't know that is really 1 per year, but that is the talk I heard
[19:41]  * jjohansen can't remember where he heard it though
[19:44]  * herton -> eod
[20:04] <apw> jjohansen, yeah, i was likely tipsy during that conv.
[20:08] <tgardner> apw, do you have some kvm runes that work on precise ? testdrive seems to have stopped working for me
[20:08] <kirkland> tgardner: hmm, what's wrong with testdrive?
[20:09] <tgardner> kirkland, can't find a display, -vga cirrus
[20:09] <kirkland> tgardner: hrmf?  how odd
[20:09] <kirkland> tgardner: you can edit that, fwiw
[20:09] <kirkland> tgardner: sudo vi /etc/testdriverc
[20:10] <tgardner> Running the Virtual Machine...
[20:10] <tgardner> 	kvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0,boot=on -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus
[20:10] <tgardner> Could not initialize SDL(No available video device) - exiting
[20:10] <kirkland> tgardner: find the line that says "-vga cirrus"
[20:10] <kirkland> tgardner: and change it
[20:10] <kirkland> hallyn: ^
[20:10] <tgardner> to what?
[20:10] <kirkland> hallyn: what would be wrong with tgardner's kvm invocation?
[20:10] <kirkland> tgardner: you can try -vga std|vmware|cirrus
[20:10] <tgardner> I also had to figure out the pxe-virtio.bin problem
[20:10] <kirkland> tgardner: honestly, though, we need to figure out why cirrus isn't working
[20:11] <kirkland> tgardner: sudo apt-get install kvm-pxe ?
[20:12] <hallyn> kirkland, dunno "kvm -cdrom /iso/precise-mini-amd64.iso -boot d -vga cirrus" at least works for me
[20:12] <hallyn> i do have ipxe installed of course
[20:12] <tgardner> kirkland, lemme check if that fixes kvm-pxe
[20:13] <tgardner> kirkland, kvm-pxe is already the newest version. the issue is that qemu wants pxe-virtio.rom, not pxe-virtio.bin
[20:13] <kirkland> hallyn: mind troubleshooting that for tgardner ?
[20:15] <tgardner> kirkland, so hallyn's command works.
[20:15] <tgardner> even over 'ssh -X'. I also tried testdrive on the physical console.
[20:16] <hallyn> tgardner, can you remove 'boot=on' from your drive spec for hard drive in your command?
[20:17] <tgardner> hallyn, on the war kvm command? or testdrive ?
[20:17] <tgardner> raw*
[20:17] <hallyn> kvm command
[20:17] <hallyn> kvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0, -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus
[20:17] <hallyn> uh, (sigh)
[20:18] <hallyn> kvm -m 1024 -smp 2 -cdrom /home/rtg/precise-server-i386-daily.iso -drive file=/home/rtg/.cache/testdrive/img/testdrive-disk-iZzs3g.img,if=virtio,cache=writeback,index=0 -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus
[20:18] <hallyn> that
[20:18] <hallyn> tgardner, is this on an oneiric host?
[20:18] <tgardner> hallyn, precise host
[20:18] <hallyn> ok, i'm on oneiric host but with precise's kvm...
[20:19] <tgardner> so I reran 'sudo testdrive -u file://`pwd`/precise-server-i386-daily.iso' to populate the COW image and now its working.
[20:19] <tgardner> etf ?
[20:19] <tgardner> wtf?
[20:20] <hallyn> tgardner, i'll blame it on the kernel :)
[20:20] <tgardner> lemme go rerun this on the console.
[20:21] <hallyn> oh, i hadn't seen some of the history
[20:21] <hallyn> 'could not initialize SDL" - sounds like it may be an sdl lib problem then
[20:22] <hallyn> or weird perms
[20:23] <tgardner> hallyn, the console hates me, but I can run it over an 'ssh -X' session.
[20:23] <hallyn> i can try to reproduce on my precise laptop.  you just ran 'testdrive' and chose precise-i386?
[20:23] <tgardner> it paints a little slow, but its a server install so I don't really care
[20:24] <tgardner> hallyn, yes
[20:24] <tgardner> clean install from today
[20:24] <hallyn> ok, thanks.
[20:24] <tgardner> plus archive updates
[20:24] <hallyn> I really do wish I could live my live without having to itneract with SDL
[20:24] <kirkland> sdl blows
[20:25] <kirkland> tgardner: thanks for the info;  when/if you ever find testdrive broken, poke hallyn and roaksoax
[20:25] <kirkland> tgardner: hallyn maintains the kvm pieces, roaksoax testdrive itself
[20:25] <tgardner> can do
[20:25] <kirkland> tgardner: it's *supposed* to be working at all times;  if it ain't, we wanna get it fixed ;-)
[20:26] <tgardner> kirkland, I was actually trying it out in order to verify that generic-pae still worked. next I'll try the same combo on a 64 bit host
[20:26] <kirkland> k
[20:26] <tgardner> still worked in kvm-qemu taht is
[20:27] <hallyn> tgardner, oh, right, i saw that thread, was curious myself
[20:55] <matthias_> Hi there. I'd like to report a kernel problem, however the command "ubuntu-bug -p linux" does not do anything :)
[20:57] <matthias_> Should I manually file a report or is there another recommended way?
[20:57] <tgardner> matthias_, thats a good start. would the nature of your kernel bug cause ubuntu-bug to stop working?
[20:58] <matthias_> No, I do not think so.
[20:58] <matthias_> My system is running. The problem is that I frequently see a bunch of annoying messages in my syslog. I wonder whether it is a hardware problem or a kernel problem.
[20:59] <tgardner> matthias_, seems like it ought to work. what release ? oneiric ?
[20:59] <matthias_> 11.10, fresh install
[21:00] <tgardner> matthias_, other folks have been using it.
[21:00] <matthias_> The problem is: I bought a new Laptop (Thinkpad T520) and received it today. Ubuntu runs, however I see the following errors:
[21:00] <matthias_> kernel: [  781.456768] ata4: irq_stat 0x00000040, connection status changed
[21:00] <matthias_> kernel: [  781.456775] ata4: SError: { CommWake DevExch }
[21:01] <matthias_> kernel: [  781.456787] ata4: limiting SATA link speed to 1.5 Gbps
[21:01] <matthias_> kernel: [  781.456794] ata4: hard resetting link
[21:01] <matthias_> kernel: [  782.177920] ata4: SATA link down (SStatus 0 SControl 310)
[21:01] <matthias_> kernel: [  782.193880] ata4: EH complete
[21:02] <tgardner> matthias_, one time, or repeating ?
[21:02] <matthias_> repeating frequently
[21:02] <matthias_> say every 20 seconds
[21:02] <matthias_> btw, thanks for your help!
[21:03] <tgardner> you could try the 3.1 kernel: http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-3.1.0-2-generic_3.1.0-2.3_amd64.deb
[21:03] <matthias_> So if it was a hardware problem I'd return the laptop to the dealer. But somehow I guess that it is a kernel problem (since the system is running)
[21:04] <tgardner> it might be power management messing with your link.
[21:05] <matthias_> tgardner, software or hardware related?
[21:05] <tgardner> software
[21:06] <matthias_> Would you think it is worth to report a bug?
[21:06] <tgardner> matthias_, yep
[21:07] <matthias_> The interesting thing is that someone with another T520 reported a similar problem: http://comments.gmane.org/gmane.linux.kernel/1207661
[21:10] <matthias_> tgardner, would you recommend me to file the bug manually or do you have an idea how to get the "ubuntu-bug" running?
[21:10]  * ogasawara lunch
[21:10] <tgardner> matthias_, manually
[21:11] <matthias_> thanks, and sorry for the many questions ;)
[21:32] <matthias_> ok, filed the bug (#888764)
[21:37] <hallyn> tgardner, yeah i386 precise starts fine for me on just-upgraded precise
[21:37] <hallyn> (boy that was a slow iso sync)
[21:41] <tgardner> hallyn, well, I'm installing a 64bit precise host, so I'll see if that is any different
[22:05] <apw> tgardner, i have a precise install but that was an oneiric-i386 which i think upgraded it to precise
[22:06] <apw> (in a KVM i mean)
[22:06] <tgardner> apw, I've now a 64bit precise host installing a PAE server ISO
[22:06] <apw> ahh, i see
[22:06] <apw> i guess i have an early enough kernel to have generic anyhow
[22:06] <tgardner> apw, I believe this combo addresses cjwatson's concerns about qemu not working with PAE
[22:07] <apw> ahh is 32 bit only really only 32bit not pae capable, interesting
[22:07] <tgardner> apw, you've just bent my mind
[22:08] <apw> is 32bit kvm not actually pae
[22:08] <tgardner> I was really only concerned that PAE work in all cases
[22:10]  * tgardner is outta here
[23:15] <ppisati> have we ever released a kernel for the n900?
[23:32] <jjohansen> ppisati: nothing official that I know of
[23:34] <ppisati> uhm