[04:48] <mneptok> WOOOT! LP is back!
[04:56] <bhale> mneptok: really?
[04:56] <mneptok> bhale: well .... *mostly*
[04:56] <mneptok> :/
[04:56] <bhale> oh
[04:56] <bhale> there it is
[04:56] <mneptok> it's rather slow
[04:57] <bhale> i am still annoyed by having to dig up "ubuntu" project
[04:57] <bhale> and then my package
[05:00] <ajmitch> hello bhale, mneptok
[05:01] <bhale> hi ajmitch
[05:05] <zul> hey ajmitch and mneptok
[05:05] <ajmitch> what's up?
[05:06] <qiyong> i want to join
[05:09] <zul> ajmitch: not much just got back from the hospital again?
[05:09] <ajmitch> fun
[05:09] <zul> not particulairly
[05:19] <grayman> qiyong, join where?
[05:20] <qiyong> grayman, anything
[05:20] <grayman> ...
[05:20] <qiyong> grayman, i understand kernel well, i like C, shell
[05:21] <grayman> erm. did you read anything from what is in the topic?
[05:21] <grayman> also a nice skill :)
[05:22] <qiyong> yes, i read some from the website
[05:22] <micahcowan> qiyong, "#ubuntu-motu for getting involved with development" :)
[05:22] <qiyong> i installed a feisty amd64 on my notebook with deboostrap, etc
[05:23] <qiyong> micahcowan, seems there are for packaging mainly
[05:23] <micahcowan> qiyong, that's a huge part of what developing for Ubuntu is. Without packaging, it's just "development" (not Ubuntu-specific).
[05:24] <qiyong> micahcowan, yeah, as a distro
[05:24] <micahcowan> They do discuss more than packaging, however. In any case, that's where you go to find out how to get involved in developing for Ubuntu.
[05:24] <qiyong> packaging is ok for me too
[05:35] <psusi> is there a way I can get access to build servers for the other platforms to work on a pakage that fails to compile except on i386 and amd64 ( the two that I have )?
[05:48] <tonyyarusso> psusi: ping imbrandon
[05:49] <psusi> k
[06:03] <fabbione> morning
[06:04] <ajmitch> morning fabbione
[06:19] <Treenaks> Argh :) My modem seems to work (finally; sl-modem).. but I just ditched my analog phone line :)
[06:19] <Treenaks> so I can't test it
[08:23] <ajmitch> hey daniel
[08:24] <dholbach> good morning
[08:24] <dholbach> hey andrew
[08:25] <poningru> jdub: ping
[08:26] <poningru> nvm
[09:05] <pitti> Good morning
[09:06] <dholbach> hey pitti
[09:08] <mdke> something broken in feisty-updates with tzdata?
[09:10] <Mithrandir> morning, Pitti
[09:10] <pitti> mdke: hm? --verbose please?
[09:10] <Mithrandir> pitti: you played with noveau yesterday?  How well did it work?
[09:10] <pitti> Mithrandir: well, it came up to gdm, and then X crashed at session login
[09:11] <Mithrandir> ugh, ok.
[09:11] <pitti> Mithrandir: I need to try this again on a live system
[09:11] <Mithrandir> so Not There Yet.
[09:11] <pitti> Mithrandir: it works well for the amd64/GeForce 6600 of mh21
[09:11] <pitti> Mithrandir: they definitively do not support 3D ATM, so it might be that something triggered glx
[09:12] <mdke> pitti: upgrade-manager says:
[09:12] <pitti> Mithrandir: I'll play around with that a bit later again
[09:12] <Mithrandir> pitti: any idea if they do dualhead yet?
[09:12] <pitti> Mithrandir: no, sorry, no idea
[09:12] <mdke> pitti: damn, can't paste what it says. Anyway, it's a 404
[09:13] <pitti> mdke: indeed
[09:13] <pitti> wget http://archive.ubuntu.com/ubuntu/pool/main/t/tzdata/tzdata_2007e-0ubuntu0.7.04_all.deb -> 404
[09:13] <mdke> that's the one
[09:13] <pitti> ~prop1 still works
[09:15] <pitti> hm, I can't see anything wrong with it on drescher
[09:15] <pitti> mdke: thanks for bringing this up, I'll contact the soyuz guys
[09:15] <crimsun> <IP_ADDRESS> is the offending IP.
[09:15] <crimsun> 88.{31,42} and 89.6 are fine
[09:16] <mdke> pitti: cool
[09:16] <pitti> oh, then it's rather a mirroring problem
[09:16] <ajmitch> Mithrandir: afaik dualhead with nouveau is still some way off for many cards
[09:16] <mdke> mine is archive.u.c
[09:16] <ajmitch> morning sabdfl
[09:16] <mdke> morning sabdfl
[09:17] <sabdfl> morning all
[09:17] <pitti> hey sabdfl
[09:17] <Hobbsee> hi all
[09:17] <ajmitch> hey Hobbsee :)
[09:17] <Hobbsee> :)
[09:26] <pitti> mdke: ah, I got the RT ticket number for that: #27742, in case you want to make inquiries yourself
[09:27] <mdke> pitti: no worries, I'm happy to wait. I can't see RT tickets anyway :)
[09:28] <pitti> mdke: no, but you can ask in #c-s about them
[09:29] <mdke> pitti: ok thanks. I'm happy to wait for it to be resolved
[09:29] <pitti> great
[09:32] <siretart> keescook: thanks for handling the rdesktop issue for dapper and edgy
[09:33] <ajmitch> hi siretart
[09:33] <siretart> hi ajmitch
[09:41] <\sh> moins simira
[09:41] <\sh> aehm
[09:41] <\sh> siretart,
[09:41] <\sh> I mean
[09:42] <pitti> hey seb128
[09:43] <seb128> hey pitti
[09:44] <siretart> hi \sh
[09:45] <ion_> you.each {|person| hi person }
[09:46] <siretart> ruby?
[09:46] <ion_> That.
[09:48] <pitti>  p  Persons. hello(p)
[09:50] <ion_> :-)
[10:09] <ajmitch> it's back? yay!
[10:09] <ajmitch> now we can see what work we have to do
[10:11] <seb128> now we only need to get gutsy running ;)
[10:11] <ajmitch> "soon"
[10:11] <Hobbsee> hah
[10:14] <Treenaks> bzr.dev is 666 days old today :)
[10:21] <zyga> morning :-)
[10:21] <zyga> mvo: hey
[10:21] <mvo> hey zyga
[10:21] <zyga> mvo: I have a question about gnome-app-install
[10:21] <mvo> zyga: sure, fire
[10:21] <zyga> how did you get all the icons out?
[10:21] <zyga> I mean: there are muliple themes
[10:22] <zyga> how did you associate exact icon with each icon entry in the desktop files?
[10:22] <mvo> zyga: searching multiple directories for icons and have a order of preferences
[10:22] <zyga> mhm
[10:23] <zyga> and you extract all the icons from main and universe and pack it along with their desktop files?
[10:25] <mvo> zyga: yes
[10:26] <mvo> zyga: well, not all of them of course, only one for each application
[10:26] <lifeless> dholbach: is the motutools rename still needed ?
[10:27] <dholbach> lifeless: yes. TheMuso: ?
[10:28] <lifeless> dholbach: this will break bzr urls for everyone
[10:29] <yondie> anyone is it possible to use synaptic with a https_proxy ?
[10:29] <lifeless> sftp://bazaar.launchpad.net/~FOO/motutools/trunk will become sftp://bazaar.launchpad.net/~FOO/ubuntu-dev-tools/trunk
[10:29] <lifeless> dholbach: ready for that ?
[10:29] <mvo> yondie: if you have apt-transport-https installed, that should work, you need to set the https_proxy environ IIRC
[10:29] <StevenK> Does bzr able to easy change parent branches?
[10:30] <lifeless> StevenK: pull --remember
[10:30] <StevenK> Hrm. That sentence is gramatically interesting.
[10:30] <lifeless> StevenK: and bind to change checkouts.
[10:30] <yondie> mvo: i`ve done dat, it works with aptitude and apt-get but not really in synaptic
[10:30] <lifeless> well, bind for heavyweight checkouts
[10:31] <mvo> yondie: sounds like a bug then, could you please report it in LP?
[10:31] <pitti> Mithrandir, doko: I have tzdata fixed and properly tested for bug 108995; ok to upload?
[10:31] <ubotu> Malone bug 108995 in tzdata "Asks configuration questions at priority high on upgrade" [High,In progress]  https://launchpad.net/bugs/108995
[10:32] <StevenK> lifeless: Personally, as long as people were notified and told how to deal, I don't see it being much of a problem.
[10:32] <dholbach> lifeless: yes
[10:32] <lifeless> StevenK: sure, neither do i, but until dholbach is ready I'm not going to push the button :)
[10:32] <dholbach> StevenK: we're discussing it on the motu list atm, no?
[10:33] <StevenK> Right.
[10:33] <lifeless> dholbach: done.
[10:33] <dholbach> thanks
[10:40] <infinity> pitti: Please do.
[10:40] <StevenK> infinity!
[10:40] <StevenK> infinity: Where have you been hiding?
[10:40] <pitti> infinity: uploaded
[10:41] <infinity> StevenK: Broke all my fingers, couldn't IRC.
[10:41] <pitti> ugh, really?
[10:41] <infinity> No. :)
[10:42] <StevenK> Hah
[11:06] <siretart> mvo: how to enable unattended-upgrades on an ubuntu-server without X and gnome?
[11:07] <mvo> siretart: add 'APT::Periodic::Unattended-Upgrade "1";' to /etc/apt/apt.conf (to run it daily)
[11:07] <mvo> siretart: you can also make it mail you the logs
[11:21] <siretart> mvo: how?
[11:23] <mvo> siretart: how to mail? it should be in the README of unattended-upgrades, its just an additional apt config var that needs to go to apt.conf
[11:23] <siretart> mvo: at least the package in feisty does not ship any readme, that's why I'm asking
[11:24] <siretart> mvo: aah, there is one in the source package
[11:24] <mvo> siretart: a BUG!
[11:24] <siretart> mvo: if gutsy was open, I'd already have it "NMU'ed" ;)
[11:26] <mvo> I guess I should talk to the sru team if its ok to do a sru upload for unattneded-upgrades to include the missing README (hello pitti :)
[11:26] <ssam> bug 84918
[11:26] <ubotu> Malone bug 84918 in unattended-upgrades "package should set up sensible config" [Undecided,Confirmed]  https://launchpad.net/bugs/84918
[11:26] <pitti> mvo: hm?
[11:26] <pitti> mvo: oh, include a new file in /usr/share/doc/<package>? sounds innocent enough
[11:27] <mvo> pitti: cool, thanks. I prepare it now
[11:30] <doko> mdz, cjwatson, Mithrandir: planned the email to -announce when the packages are in the archive. this (late) afternoon
[11:31] <mdz> doko: thanks
[12:20] <`23meg> Hobbsee, the doc is finished, more or less
[12:21] <`23meg> it's on gobby, can you take a look?
[12:22] <Hobbsee> `23meg: great.  and that requires installing gobby :P
[12:22] <`23meg> oh
[12:23] <`23meg> shall i mail it if that's not convenient?
[12:23] <Hobbsee> whichever is fine
[12:23] <Hobbsee> gobby lags for me, but it hsouldnt matter if i'm not editing it in real time
[12:26] <Mithrandir> pitti: doesn't look urgent?
[12:26] <Hobbsee> THE LAG!  IT BURNS!!!!
[12:27] <Mithrandir> hiya Hobbsee
[12:27] <Hobbsee> hi Mithrandir!
[12:27] <pitti> Mithrandir: I thought the same, but Matthias said it would be better to fix it soon, otherwise every developer would see those questions
[12:28] <Mithrandir> pitti: people shouldn't upgrade to gutsy yet.
[12:28] <Mithrandir> pitti: but sure, feel free to upload and I'll make sure it gets in with the first round of builds.
[12:28] <pitti> Mithrandir: *shrug* I uploaded it to the queue after infinity's 'please do', but feel free to just leave it there
[12:29] <Mithrandir> pitti: I'll let it in once the current mess is solved.
[12:30] <pitti> thank you
[12:30] <pitti> Mithrandir: oh, it's still that messy?
[12:31] <Mithrandir> pitti: apparently something is broken right now; Adam told me about it, but I'm not sure exactly what it is.
[12:31] <StevenK> Hrm. I have two gutsy chroots, but I'm in no way attached to them.
[12:32] <StevenK> Your knee? :-P
[12:32] <Mithrandir> no, your knee.
[12:33] <Mithrandir> there, it's at least attached to you even though you don't feel attached to it.
[12:33] <StevenK> That isn't what you said. :-P
[12:33] <Mithrandir> no, but I gave an inaccurate description of what I did. :-P
[12:33] <ajmitch> english, 'tis a wonderful language
[12:34] <Hobbsee> heh
[01:10] <pitti> Riddell: bug 108969 approved, FYI
[01:10] <ubotu> Malone bug 108969 in update-manager "update-manager's KDE frontend directs bug reports to ubiquity" [High,In progress]  https://launchpad.net/bugs/108969
[01:12] <mvo> pitti: I would like to upload some more fixes, its all pretty trivial but quite a few unfortunately
[01:13] <Riddell> was about to ask that
[01:13] <mvo> pitti: should I file a debdiff for each individually or for all of them?
[01:13] <pitti> mvo: please subscribe ubuntu-sru to the relevant bugs and add a codebrowse URL, that would be best for me
[01:14] <pitti> since it's easier to tell the patches apart and verify them
[01:15] <pitti> mvo: but NB that each -proposed upload resets the time to 7 days again, so maybe the less critical issues should be done after an -updates upload?
[01:16] <mvo> pitti: how loaded are you currently? the stuff is ready, it "just" needs review
[01:17] <pitti> mvo: go ahead, I'm in the middle of SRU review anyway ;)
[01:20] <carlos> lamont: ping
[01:21] <tepsipakki> has there been talk about if upgrades from dapper are supported not only to the next LTS but the one after it?
[01:22] <rsk> tepsipakki: nope
[01:23] <ajmitch> tepsipakki: that could be a long way to support an upgrade
[01:23] <StevenK> Oh yeah.
[01:23] <StevenK> Too long, IMHO
[01:23] <tepsipakki> ajmitch: that's what I thought too
[01:24] <ajmitch> a lot could change in 4 years :)
[01:24] <tepsipakki> means that I wasn't on crack a minute ago
[01:24] <ajmitch> well I don't know about that... :)
[01:24] <tepsipakki> sent an email to debian-x.. I'm committing the Replaces/Conflicts-stuff from our drivers to git.d.o
[01:24] <tepsipakki> ajmitch: hah
[01:26] <tepsipakki> I said that those can be dropped before Lenny is released, since 8.0x is likely the next LTS
[01:26] <ajmitch> lenny might release before then
[01:26] <ajmitch> don't laugh..
[01:27] <tepsipakki> hum, it was scheduled for fall 2008?
[01:27] <StevenK> I don't like the name Lenny, but there you go.
[01:27] <ajmitch> tepsipakki: we'll see..
[01:27] <seb128> ajmitch: it's not likely
[01:28] <ajmitch> seb128: not very likely at all, no
[01:34] <mvo> pitti: https://bugs.beta.launchpad.net/ubuntu/+source/update-manager/+bug/109584
[01:34] <ubotu> Malone bug 109584 in update-manager "sru request for update-manager " [Undecided,Unconfirmed]
[01:38] <pitti> mvo: I updated bug 109564 and bug 109290; those are the ones you cared about?
[01:38] <ubotu> Malone bug 109564 in unattended-upgrades "README missing" [Low,In progress]  https://launchpad.net/bugs/109564
[01:38] <ubotu> Malone bug 109290 in update-manager "update-manager core should support proposed updates" [Medium,Needs info]  https://launchpad.net/bugs/109290
[01:39] <pitti> mvo: ah, looking at that new bug now
[01:43] <pitti> mvo: I'll review that mega-diff after lunch
[01:43] <cjwatson> tepsipakki: only to the next LTS; there's discussion of how to achieve even that scheduled for UUDS
[01:43] <cjwatson> UDS
[01:43] <mvo> pitti: sure, sorry that its so big :(
[01:43] <tepsipakki> cjwatson: ok, thanks
[02:41] <lamont> carlos: ack
[02:41] <lamont> and about to walk out the door to take kids to school...
[02:41] <lamont> will be online in about an hour or so
[03:02] <lifeless> pitti: http://code.google.com/p/google-breakpad/
[03:02] <pitti> mvo: bug #109584 updated
[03:02] <ubotu> Malone bug 109584 in update-manager "sru request for update-manager " [Undecided,Needs info]  https://launchpad.net/bugs/109584
[03:02] <pitti> hi lifeless
[03:03] <lifeless> hiya
[03:04] <pitti> lifeless: right, this came up a while ago; I plan to look at it for https://wiki.ubuntu.com/CrashReporting, it sounds promising
[03:04] <pitti> lifeless: although ISTR that Mozilla discussed this recently, I thought it was their invention
[03:04] <lifeless> ah
[03:04] <lifeless> it looks like its less magic than apport though
[03:05] <lifeless> not sure its really a win :(
[03:05] <pitti> lifeless: looks a lot like this 'airbag' project
[03:06] <pitti> lifeless: I looked at that, and it wasn't really usable for us; I hoped that this breakpad thingy would provide a crash database with a nice web UI
[03:06] <pitti> hm, but that doesn't seem to be the case from a quick glance
[03:07] <pitti> lifeless: I still didn't completely give up the hope of using Malone for this; maybe using a separate product, filing the bugs as private by default and remove core dump attachments automatically after retracing; something like that
[03:11] <bddebian> Heya
[03:19] <Riddell> what would a derived distro change to default to nvidia driver instead of nv?
[03:35] <Amaranth> Riddell: Probably some hackery in the debconf stuff in xorg
[03:35] <Riddell> I feared as much
[03:36] <seb128> Amaranth: hi, there is some unconfirmed alacarte bugs, maybe you could have a look on them? ;)
[03:36] <Amaranth> seb128: Was just heading for bed :)
[03:36] <Amaranth> Will do it when I wake up
[03:36] <seb128> thank you
[03:36] <seb128> 'night!
[03:41] <carlos> lamont: hi, are you back?
[03:44] <lamont> carlos: just now
[03:44] <lamont> carlos: what's up?
[03:45] <carlos> lamont: I wonder whether you could reactivate translations .tar.gz mirroring on rookery, at least for openoffice.org
[03:45] <carlos> the ones generated on build time
[03:46] <lamont> carlos: looks like  I can, yes.
[03:46] <lamont> I had thought that was completely obsolete....
[03:46] <carlos> lamont: that will simplify a lot doko's life
[03:47] <carlos> lamont: well, Rosetta is not using it at all
[03:47] <carlos> lamont: but oo.org needs some info that Rosetta is not using at all
[03:47] <lamont> I see.
[03:47] <carlos> that require a lot of work to regenerate
[03:47] <lamont> turning it on for just oo.o is. um, pain.
[03:47] <lamont> turning it on for everyting will fill up rookery's disks again...
[03:47] <carlos> so it simplifies a lot oo.org translations updates
[03:48] <lamont> how about I turn it on, and remove everything over 7 days old each night?
[03:48] <carlos> lamont: what about removing everything except for last month?
[03:48] <carlos> lamont: ;-)
[03:48] <carlos> lamont: ok 7 days would work, if you could leave oo.org ones for a month
[03:48] <lamont> I'll start with March 15 or so?
[03:49] <carlos> well, you could start with a fresh tree
[03:49] <lamont> and is  i386 sufficient, or do i need to fetch more?
[03:49] <carlos> i386 is enough
[03:52] <lamont> carlos: lit up and fetching
[03:52] <carlos> lamont: cool, thank you!
[03:53] <carlos> doko: ^^^
[04:15] <siretart> cjwatson: hi. I'm trying to preseed the feisty netboot image, and I wonder if there is a list of preseedable variables. I remember there was an appendix in the debian-installer manual, but I cannot find it for feisty
[04:17] <mvo> pitti: thanks for your review #109584, I updated the debdiff
[04:17] <pitti> mvo: and I just updated the bug :)
[04:19] <mvo> pitti: woah, you are fast
[04:20] <mvo> pitti: thanks!
[04:22] <lamont> carlos: I assume you want at least one set of oo.o translations there, yes?
[04:22] <carlos> lamont: latest one is enough (per distrorelease)
[04:23] <lamont> yeah. hrm.
[04:23] <lamont> I can provide doko with that file directly, I believe
[04:25] <lamont> doko: poke me when you want them, and I'll tell you where to root around from chinstrap to fetch them
[04:37] <doko> lamont: thanks
[04:39] <cjwatson> mdke: are you due to update help.ubuntu.com for feisty, or is that somebody else?
[04:39] <cjwatson> siretart: ^--
[04:40] <cjwatson> siretart: the installation guide on help.ubuntu.com for edgy should be good enough in most cases; the only particularly relevant change I know of is that you now have to preseed 'd-i partman-auto/method string regular' if you're preseeding partman-auto/disk
[04:41] <siretart> cjwatson: ok. thanks!
[05:37] <ion_> keybuk: Btw, is it already safe to upgrade an edgy box with md+lvm to feisty? :-)
[05:38] <Keybuk> see if it works
[05:40] <ion_> Perhaps i should replicate the configuration in a virtual machine to test it or something. The box in question shouldnt have any more downtime than absolutely necessary.
[05:55] <siretart> ion_: the past problems have (almost always) been races. so reproducing it in some virtual environment is not a good test to see if it works
[05:55] <siretart> ion_: better just try upgrading, and if it fails, restore your backup
[06:44] <keescook> siretart: rdesktop> sure, no problem; thank you for finding the fix for it!  :)
[06:53] <pitti> hey keescook
[06:54] <keescook> hiya pitti
[07:04] <elkbuntu> *clears her throat* there's an anxious mob awaiting a certain benevolent dictator in -classroom :)
[07:05] <pochu> sabdfl:
[07:05] <pochu> oups :)
[07:06] <pochu> btw, nice session dholbach :)
[07:06] <sabdfl> ???
[07:06] <mc44> sabdfl: open week... :)
[07:06] <dholbach> pochu: thanks a lot
[07:06] <pochu> sabdfl: it's your time in #ubuntu-classroom ;)
[07:07] <pochu> dholbach: /me likes more and more the motu community :)
[07:07] <dholbach> pochu: that's really great - hope to have you in the team soon
[07:08] <pochu> I'm in my way... but a lot to learn yet!
[07:10] <dholbach> pochu: I'm sure you'll do nicely :)
[07:13] <psusi> imbrandon: ping
[08:03] <real_ate> hey, i'm doing the rounds at the moment trying to find some help in identifing a hardware bug, anyone here know much about wireless?
[08:23] <iwj> In Python, how would I parse the output from find -print0 ?
[08:26] <jcol3> can i just stop the dbus service altogether and my apps still work?
[08:26] <jcol3> /ncik jcole
[08:26] <iwj> jcol3: Not IME.
[08:26] <iwj> But I am no expert.
[08:27] <^jcole> dbus seems flaky in feisty
[08:27] <^jcole> on my desktops and my laptop
[08:28] <^jcole> i see bugs submitted against dbus/gaim/evolution/etc. related to dbus and would like to remove dbus altogether
[08:30] <shawarma> ^jcole: Some things use dbus to work.
[08:30] <shawarma> ^jcole: Popular examples include hal.
[08:30] <shawarma> ^jcole: And hence network-manager.
[08:30] <^jcole> shawarma: was it this way in edgy?
[08:30] <shawarma> ^jcole: Yes.
[08:31] <^jcole> shawarma: something must have changed in dbus between edgy and feisty
[08:31] <shawarma> ^jcole: of course.
[08:31] <shawarma> ^jcole: Something changed in almost every package. :-)
[08:32] <^jcole> shawarma: i get grayed out windows that are not responsive... killing them and restarting them gets really annoying
[08:33] <^jcole> shawarma: i'm in gaim right now, which will most definitely freeze later on today, and it appears to also use dbus
[08:33] <shawarma> ^jcole: I haven't seen that before.
[08:34] <^jcole> shawarma: network-manager also gives me problems, which uses dbus... also evolution, which i think also uses dbus
[08:35] <^jcole> i'm really not sure what is going on or how to debug a hung application
[08:35] <^jcole> i've reverted my laptop back to edgy so i can have my stability back
[08:35] <shawarma> I'm sorry, I've got to run out. Maybe someone else can help. You can perhaps try in #ubuntu-bugs
[08:36] <shawarma> I'll be back in about half an hour.
[08:45] <psusi> anyone know what timezone imbrandon lives in?
[08:46] <psusi> i.e. when I could expect him to be on?
[09:02] <shawarma> psusi: He's in the US somewhere.
[09:05] <mvo_> iwj: if you are still interessted in the python find output parsing, let me know
[09:08] <sladen> psusi: https://launchpad.net/~imbrandon/ | grep Timezone
[09:19] <Clem92> /exit
[09:20] <Clem92> /leave
[09:21] <jcole_eat> Clem92: /quit
[09:23] <jcole_eat> has mozilla disappeared entirely from the repos?
[09:24] <jcole_eat> why isn't this in the repos?? http://www.mozilla.org/projects/seamonkey/
[09:25] <geser> jcole_eat: yes, the old mozilla suite was removed
[09:26] <jcole_eat> geser: why? and why wasn't it "replaced" with the new suite?
[09:27] <geser> it was the pre-"seamonkey" version which is abandoned and unmaintained upstream
[09:27] <geser> and for seamonkey I don't know the reason anymore why it wasn't synced from Debian
[09:28] <jcole_eat> geser: maybe it has to do with the whole firefox logo copyright drama
[09:29] <jcole_eat> or maybe it's called something else in the repos
[09:29] <geser> as Ubuntu can use the trademark (see firefox and thunderbird) it's not the reason
[09:31] <geser> nowbody moved forward to sync it from Debian (and rename it back to seamonkey)
[09:32] <jcole_eat> it's called iceape
[09:32] <jcole_eat> in debian
[09:32] <geser> I know
[09:32] <geser> perhaps nobody seen a benefit to have it in universe
[09:34] <jcole_eat> geser: i want the only wysiwyg html editor in debian/ubuntu, *composer*
[09:34] <jcole_eat> (open office puts a mess of crap in the html)
[09:35] <jcole_eat> it's probably easiest to pin and add the debian repos
[09:35] <shawarma> nvu has worked for me before.
[09:35] <geser> nvu was removed from feisty
[09:35] <jcole_eat> shawarma: ya, i like nvu, but it is now gone from ubuntu
[09:37] <shawarma> Ah, right.
[09:38] <cjwatson> it's gone from feisty, not from Ubuntu; should be possible to continue using the package in edgy
[09:39] <giskard> nvu is buggy and unmaintained i suggest you to take a look on Kompozer..a "fork" of nvu
[09:40] <jcole_eat> coolness, got "iceape" composer installed from debian :)
[09:41] <jcole_eat> ah, good ol' mozilla too :)
[09:46] <geser> cjwatson: is it possible to remove a released (and broken) package from the archive?
[09:48] <\sh> geser, why not fixing it?
[09:49] <geser> \sh: it's for bug #81996
[09:49] <ubotu> Malone bug 81996 in f-prot-installer "f-prot.com closed the FTP site" [Medium,Confirmed]  https://launchpad.net/bugs/81996
[09:50] <geser> it tries to download a file which isn't there anymore. f-prot provides now also a deb for download
[09:50] <\sh> geser, what about removing the content and creating an "empty" package with a debconf alert message?
[09:51] <Treenaks> whoo.. dapper installing inside kvm on feisty :)
[09:52] <geser> that would be only a help for those who have it already installed to let them know how to "update" the package
[09:53] <\sh> geser, also telling people that this package is obsolete and will disappear in the future (not for current release but for the next)
[09:54] <Treenaks> \sh: that should be package description, not debconf notice
[09:55] <shawarma> t
[09:55] <shawarma> whoops
[09:55] <\sh> Treenaks, no...just as a very special reminder...nobody reads apt-cache show ;)
[09:55] <shawarma> It *could* also be changed to fetch the new .deb and install it.
[09:55] <geser> I think you can't run dpkg from dpkg
[09:55] <cjwatson> you cannot
[09:55] <shawarma> No, I just thought of that too
[09:56] <cjwatson> geser: not without sounding massive alarm klaxons
[09:56] <cjwatson> very much prefer not to
[09:56] <cjwatson> (if it's in a released suite like feisty)
[09:56] <shawarma> It could fetch it and tell the user to install it like it's done with libdvdcss.
[09:56] <shawarma> Or is it still done that way?
[09:56] <shawarma> I forget.
[10:00] <geser> cjwatson: any preferred idea how to fix it? (if it should be fixed)
[10:09] <cjwatson> geser: a kludge comes to mind in which the installer package downloads the .deb and extracts files from it as if it were the tarball previously provided
[10:11] <geser> would such a massive change be suitable for a SRU?
[10:12] <mjg59> cjwatson: Any idea where keybuk and mdz might be? I was under the impression we had a tech board meeting now...
[10:16] <cjwatson> mjg59: um, dunno, I can try phoning
[10:17] <mjg59> cjwatson: I'm not in the UK right now, so if you could that would be great :)
[10:18] <cjwatson> hmm
[10:18] <cjwatson> mdz is at dinner with sabdfl and doesn't think he'll make it; no answer from Scott's phone
[10:18] <mjg59> Ok
[10:19] <cjwatson> sorry :-/
[11:01] <bogdanb> Hi! I've just finished the first draft of a proposed spec, please take a look at it and leave a comment on the wiki if you're interested. It's about the automatically and centrally gathering the data that is currently used by the System Monitor's resource usage graphs, the Power Manager, and similar tools. You can find it at https://blueprints.launchpad.net/ubuntu/+spec/unified-system-monitoring
[11:13] <mdke> cjwatson: yes
[11:14] <mdke> cjwatson: got a bit of work to do on it, should have it ready in about a week I guess. We really need to rethink the way we do online help for the next release cycle
[11:43] <Solarion> so, when is the alpha of the next release coming out?
[11:43] <Solarion> if it does xrandr1.2, I'm going to it now.  :)
[11:43] <mc44> !gutsy
[11:43] <ubotu> Gutsy Gibbon is the code name for the next release of Ubuntu (7.10). See https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-April/000276.html and https://wiki.ubuntu.com/GutsyReleaseSchedule Support in #ubuntu+1
[11:44] <Solarion> mc44: ah, danke
[11:44] <Solarion> looks like I won't have it in time for my comps presentation.  :(
[11:52] <psusi> imbrandon: ping
[11:52] <imbrandon> psusi, give me a few i'm giving a IRC talk then i'll get with yoiu
[11:52] <imbrandon> you*
[11:53] <psusi> kk
[11:53] <ajmitch> psusi: imbrandon is off being famous
[11:54] <ajmitch> psusi: was this the access to compile machines?
[11:54] <psusi> lifestyles of the rich and famous
[11:54] <psusi> ajmitch: yea
[11:54] <ajmitch> the only other ones setup right now are sparc & ppc
[12:02] <psusi> ok
[12:07] <psusi> more likely than not, if I get it compiling on those two, it will also work on ia64
[12:07] <psusi> frankly, I'm still surprised it doesn't build on ia64 seeing as how it works on amd64
[12:08] <imbrandon> psusi, what can i do for ya
[12:08] <psusi> imbrandon: I was told to ping you for access to some build machines of other architectures.... the defrag package only builds on i386 and amd64 since those are the two I have access to and I'm tired of getting email when it fails to build on the others ;)
[12:09] <imbrandon> psusi, are you a MOTU currently ( or core-dev )
[12:09] <psusi> no
[12:10] <psusi> though apparently I'm now on the new dmdraid team on launchpad... heh...
[12:10] <imbrandon> hrm i have it restricted to only MOTU for security and to keep the accounts down, but I'm sure some motu would be happy to help you with specific bugs on those arches
[12:11] <psusi> ok... maybe I'll just finally get off my ass and become a motu already...
[12:11] <imbrandon> :)
[12:11] <psusi> time to refresh my memory on what I have to do...


[12:58] <Toroman> hi!  I have an usb wifi dongle (usr805422), when i try to boot up ubuntu with my usr805422, I receive host system error and I cant use my dongle until next reboot....   it only works when i boot up my ubuntu without usb dongle and wait to load desktop manager and ndiswrapper :(    http://pastebin.com/me5a7918   here is more inf. please help me
[12:59] <defcon> belkin ralink rt73 wifi dongle causes a kernel panic when I plug it in
[01:00] <defcon> Toroman, same problem here, kernel panic my caps/scroll lock blink
[01:00] <defcon> everything worked fine in feisty
[01:01] <Toroman> with usr805422 no kernel panic problem but only my usb host dies :D
[01:04] <Toroman> i try my dongle with other distros such as pardus, no problem occured...
[01:06] <JanC> many ralink drivers heave issues with multiprocessing
[01:07] <JanC> so if you have a multi-core/multithreading CPU...
[01:08] <Toroman> I'v very very single and old core :D
[01:09] <JanC> so then there is another issue...  ;)
[01:12] <Toroman> i try this dongle with 3 different computers but they all deliver same error
[01:13] <mjg59> amitk_: http://www.codon.org.uk/~mjg59/tmp/usb_autosuspend
[01:15] <Toroman> I have to unplug my dongle and boot my comp wait  ndiswrapper loads then plug my dongle
[03:25] <defcon> ikm having an issue with gutsy and the 2.6.22-9 kernel, when I plug in my belkins usb wifi dongle I get an instant kernel panic
[03:29] <lamont`> defcon: neato.  what exactly is the panic?>
[03:30] <defcon> how do I debug this and properly report it
[03:30] <\x6e\x65\x72\x64> Hi, I'm trying to compile a dapper kernel on a feisty machine, because the feisty machine is faster, but I'm getting some errors, do I have to make any special changes for this to work?
[03:30] <defcon> it instantly freezes my box and blinks caps lock/scroll lock
[03:32] <defcon> lamont, I have tried -rt and it doesnt panic but I am unable to modprobe the module rt73.ko from serialmonkey, and cannot use the supplied drivers with ubuntu
[03:32] <defcon> 2.6.22-9-386 got the same issue
[03:35] <lamont`> defcon: and the actual panic message is????
[03:35] <lamont`> ah - it freezes the machine, rather than panicing... got it
[03:35] <defcon> i didnt write it down, should there be a log of it
[03:36] <defcon> apon boot it does the same
[03:36] <lamont`> given that panic doesn't trust anything, it tends to only record the info on the console....
[03:36] <defcon> wont boot when initializing interfaces
[03:36] <lamont`> that makes sense
[03:36] <defcon> capslock/scroll lock blink
[03:37] <defcon> what does that mean
[03:37] <lamont`> OTOH, without knowing what the panic message was, life sucks.  If there's no panic message, then life gets more interesting for tracking things down
[03:37] <lamont`> defcon: dunno what the blinking stuff means
[03:38] <mjg59> Blinking means that the kernel has oopsed
[03:38] <defcon> ok so I'll reinstall the kernel and try again supplying u with an error message, I only get it during recovery mode
[03:38] <lamont`> mjg59: cool.  I'll remember that
[03:39] <defcon> am i in the right place for this to be resolved?
[03:39] <lamont`> defcon: I'm close to running out the door for home, and will be gone for at least an hour at that point.  I'll read scrollback when I get there.
[03:39] <lamont`> defcon: either here, or (better yet), all the detail you can provide, into a bug filed in launchpad
[03:39] <defcon> lamont, ok
[03:39] <lamont`> that way it gets some tracking.
[03:40] <lamont`> and actually, this is the right channel to be discussing your fix for the bug, to make sure that it's implemented correctly, etc.  rather than a support channel....
[03:40] <lamont`> likewise, discussions on figuring out how to best debug the problem are on topic.
[03:40] <lamont`> "fix my bug please, kthxbye" would be off topic. :-)
[03:41] <lamont`> at least, that's how i read things...
[03:41] <defcon> cool
[03:41] <defcon> I appreciate it lamont
[03:41] <defcon> i'll work on this
[03:41] <defcon> dling/installing the kernel now
[03:42] <defcon> going to reboot now and write this down
[03:42] <defcon> bbl
[03:52] <defcon_> lamont,  lamont` gotta type this out now
[03:54] <defcon_> [39.928296]  kobject_add failed for :d-0000008 with -EEXIST dont try to register things with the same name in the same directory
[03:54] <defcon_> [39.928660]  Kernel Panic - not syncing Creation of kmalloc slab kmalloc_dma-2 size=2 failed
[03:55] <defcon_> where can I post this on launchpad
[03:55] <mjg59> Sounds like a bug in p54
[03:55] <mjg59> defcon_: There should be several other lines as well
[03:56] <defcon_> keep in mind this is a belkins F5D7050 USB wifi card
[03:56] <defcon_> if that matters
[04:08] <defcon_> new bug https://bugs.launchpad.net/ubuntu/+bug/130078
[04:11] <mjg59> defcon_: We need the rest of the message
[04:13] <defcon_> thats where it froze
[04:13] <defcon_> it didnt give any more
[04:14] <mjg59> defcon_: What are the lines before that?
[04:16] <defcon_> I dont remember, let me try and think, it all looked normal
[04:17] <defcon_> something about b**** doesnt have a config file, I know its an app for security policies
[04:17] <defcon_> but I didnt enable it
[04:19] <defcon_> I know
[04:19] <defcon_> bastille does not have a configuration file
[04:19] <defcon_> thats it
[04:20] <defcon_> I did not set anything for bastille, so it shouldnt effect anything I dont think
[04:20] <defcon_> I just removed bastille
[05:17] <bullgard4> kern.log prints: "pnp: Failed to activate device 00:06." How can I determine what '00:06' stands for?
[05:19] <johanbr> lspci
[05:22] <mjg59> No
[05:25] <bullgard4> johanbr: My lspci -vv outputs in the format xxxx:yy:zz.z. How does this format map to the pnp format aa::bb?
[05:25] <bullgard4> aa:bb
[05:26] <mjg59> It doesn't
[05:26] <johanbr> x=a and y=b, I think.
[05:26] <kylem> no.
[05:26] <kylem> god.
[05:26] <mjg59> That output isn't from the pci system
[05:27] <kylem> bullgard4, install pnputils and run lspnp.
[05:27] <johanbr> Oh... sorry for spreading misinformation.
[05:58] <bullgard4> kylem: lspnp prints: "00:06 PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support)." --  Thank you very much.
[05:58] <kylem> bullgard4, no problemo.
[05:58] <lamont> EE: Missing modules (start begging for mercy)
[06:02] <lamont> kylem: so are we already committed to -9.26?
[06:02] <kylem> pardon?
[06:02] <lamont> hppa64.modules was also incorrect.
[06:02] <lamont> mind you, I'm happy just pushing -9.25hppa1 for the moment, in my archive
[06:03] <lamont> as long as we make sure things get right in -9.26 when it does hit...
[06:03] <kylem> i have a few patches i want in tribe4, but they're likely abi-breaking, so i'll have to schedule them with Ben.
[06:04] <lamont> build takes a couple hours, so we'll know in the morning if it's any good.
[06:05] <kylem> if it's just a simple patch, please just post it to kernel-team (instead of asking for a pull for just a single commit)
[06:05] <lamont> I'll post the diff, although it's basically a "replace hppa64.modules with the good one"
[06:05] <kylem> ok.
[06:06] <lamont> I wonder... if it's -9.25hppa1 do I want it to be abi/2.6.22-9.25 or abi/2.6.22-9.24?
[06:07] <lamont> 25
[06:27] <defcon_> lamont, https://bugs.launchpad.net/ubuntu/+bug/130078
[06:28] <lamont> defcon_: and what did it say _before_ those two lines?
[06:28] <lamont> full context is kinda important...
[06:28] <defcon_> before it said that it said cannot load bastille config, I never configured it so I dont believe thats a problem
[06:29] <defcon_> I had to write down then type that out whats on there hehe
[06:29] <defcon_> before that it said loading network interfaces
[06:29] <defcon_> and thats it
[06:29] <defcon_> brb
[06:32] <lamont> ok
[07:35] <defcon_> lamont, is there a way to get the log without writing it all down
[07:35] <defcon_> or a script or something to log it all
[07:36] <lamont> defcon_: personally, I tend to use a camera
[07:36] <defcon_> hehe
[07:36] <lamont> serial consoles are also kinda cool
[07:38] <defcon_> i could enable bootlogd
[07:38] <defcon_> ./etc/default/bootlogd
[07:38] <defcon_> im suprised it is disabled by default
[07:42] <lamont> kylem: fwiw, the diff is 5kb, 500 lines, all of it hppa64.modules
[07:42] <lamont> short enough to just email to the list
[07:42] <lamont> once the build succeeds
[07:42] <infinity> s/once/if/
[07:43] <infinity> Although I have every confidence in your test building process, LaMont. :P
[07:43] <defcon_> brb reboot
[07:43] <lamont> infinity: heh./
[07:43] <lamont> the only oddity is that it's test-building -9.25hppa1 instead of -9.26
[07:45] <lamont> it's doing hppa64/modules build right now... I wish it'd hurry up
[07:46] <lamont> hrm.. should be OTOO 40 minutes
[08:15] <defcon> I see bootlogd is disabled, and broken
[08:15] <defcon> any other app to log the boot seq so I can get a kernel log of it Panicing
[08:15] <defcon> I dont have a digital camera to snap it
[08:33] <defcon> new kernel update still bombs when it see's my belkin usb dongle
[08:44] <defcon> will a kern.log help with a kernel panic
[11:04] <Nafallo> mjg59: http://paste.ubuntu-nl.org/32346/ <-- that's what I could save from the serial window booting with apic=debug
[11:05] <Nafallo> mjg59: http://home.nafallo.info/bugs/sata_nv_take2.txt <-- and that's with the drives at ports 3 and 4.
[01:15] <mjg59> Nafallo: Does acpi_use_timer_override work?
[01:16] <Nafallo> mjg59: instead of noacpi?
[01:16] <Nafallo> apic even
[01:18] <mjg59> Yes
[01:20] <Nafallo> we shall see. brb.
[01:28] <Nafallo> http://paste.ubuntu-nl.org/32360/
[01:28] <Nafallo> http://paste.ubuntu-nl.org/32361/
[01:29] <Nafallo> the first one without apic=debug
[01:35] <Nafallo> http://home.nafallo.info/bugs/sata_nv_take3.txt
[01:35] <Nafallo> mjg59: any ideas? :-)
[01:38] <Nafallo> putting current gutsy -server on there should work, right?
[01:53] <Nafallo> well, that didn't work... :-P
[02:04] <mjg59> Wow. Your hardware is impressively broken.
[02:05] <Nafallo> ASA M2N-E
[02:05] <Nafallo> ASUS even
[02:06] <Nafallo> mjg59: so. what can I do? :-)
[02:07] <mjg59> Get a new motherboard?
[02:07] <Nafallo> ouch
[02:07] <mjg59> Hm. apic=debug doesn't seem to have helped much.
[02:08] <Nafallo> indeed it didn't :-/
[02:09] <mjg59> There ought to have been a dump of the apic mappings
[02:11] <Nafallo> can I force it to do that on the running system or somethiing? :-)
[02:12] <mjg59> Oh, wait, I see the output now
[02:16] <Nafallo> mjg59: I found logcheck have nice logs. do you want all the latest reboots? ;-)
[02:23] <mjg59> No, I don't think that would really help
[02:24] <Nafallo> ehrm. I think you might want to see this one... what's you mailaddress?
[02:27] <Nafallo> ah, no. seems the .txt on the server has the info.
[02:29] <mjg59> Nafallo: It, uh, seems to have the same problem?
[02:30] <Nafallo> they all have :-P
[02:31] <Nafallo> hmm. a friend told me to remove the disabling code from spurious.c :-P
[02:33] <mjg59> Nafallo: So why would I want to look at that one especially?
[02:33] <mjg59> I suspect your machine just has wrong IRQ routing for the noapic case
[02:33] <mjg59> You could try pci=noacpi
[02:34] <mjg59> But it would be more interesting to fix the actual bug (the fact that it doesn't seem willing to boot with the apic)
[02:34] <mjg59> Have you tried the 64-bit version?
[02:34] <Nafallo> I agree. but what more can I do to nail down the cause?
[02:35] <Nafallo> yes. when I removed all drives except the raptors and installed gutsy tribe-3 x86_64 server
[02:35] <ivoks> mjg59: (sorry for distraction) could you take a look at bug 119130 when you have time; it has a solution, so it should be an easy one...
[02:37] <mjg59> Nafallo: And?
[02:39] <Nafallo> mjg59: same thing.
[02:39] <mjg59> Nafallo: Which same thing?
[02:40] <Nafallo> the irq 7: nobody cared thing
[02:40] <mjg59> Nafallo: And without noapic?
[02:40] <Nafallo> and had to boot with noapic
[02:40] <mjg59> ivoks: I don't really have time to deal with acpi-support right now
[02:40] <mjg59> With the same failure message?
[02:40] <Nafallo> yes.
[02:40] <Nafallo> dapper worked though :-)
[02:40] <ivoks> mjg59: ok
[02:41] <Nafallo> with noapic...
[02:41] <Nafallo> so "worked"
[02:42] <Nafallo> atleast I didn't get the irq7 on 2.6.15 :-)
[03:52] <BenC> Anyone else have a Turion x2 laptop that they are running or have tried to run gutsy on?
[03:53] <BenC> rtg: I'm going to start a new thread on lkml about this problem...it's pretty serious regression for us
[03:54] <rtg> BenC: There are several LP reports that I think are related.
[03:57] <BenC> rtg: any pointers?
[03:59] <rtg> I'll see if I can round 'em up.
[04:11] <lamont> BenC: btw, more hppa tweaks for .26 :-(
[04:14] <BenC> rtg: Cc'd you
[04:15] <lamont> imagelist=$(cat kernel-versions | grep ^hppa | awk '{print $4}') && \
[04:15] <lamont>         for i in $imagelist; do \
[04:15] <lamont>           dpkg -x $(ls ../linux-image-$i\_*hppa.deb) \
[04:15] <lamont>                 debian/d-i-hppa; \
[04:15] <lamont>         done
[04:15] <lamont> dpkg-deb: --extract takes at most two arguments (.deb and directory)
[04:24] <BenC> Nafallo: override the PCI slot IRQ's in the BIOS?
[04:25] <BenC> Nafallo: in a lot of cases, the "irqX and nobody care" is a symptom of a broken BIOS, so check for an update on that as well
[04:25] <Nafallo> BenC: thanks :-)
[04:26] <Nafallo> a slightly more expensive solution is PCI-E 3ware RAID1 ;-)
[04:26] <Nafallo> but I'll check this one out first :-)
[04:26] <Nafallo> I should have PNPOS installed in BIOS, right? :-)
[04:27] <BenC> should, yes
[04:30] <Nafallo> well, I'll look soon enough then.
[04:30] <Nafallo> need to put VGA in the box again :-P
[04:33] <Nafallo> hmm. beta bios? ;-)
[04:33] <Nafallo> http://support.asus.com/download/download.aspx?SLanguage=en-us&model=M2N-E <-- /me is confused
[05:12] <abogani> BenC: Could you enable linux-image-debug build for rt? Thanks.
[05:12] <BenC> abogani: can't, the custom-binary builds don't support that
[05:13] <abogani> BenC: Uh, sorry!
[05:29] <BenC> kylem: Do you have a Turion laptop?
[05:29] <kylem> nope.
[05:29] <kylem> i only have one amd box these days.
[05:32] <mjg59> BenC: There's a discussion about missing timer interrupts on mobile AMDs on lkml right now
[05:42] <BenC> mjg59: ah, that's exactly what I need, thanks
[05:43] <BenC> mjg59: subject?
[05:46] <mjg59>  ACPI on Averatec 2370
[05:46] <mjg59> nolapic_timer ought to work if it's the same issue
[05:50] <kylem> Regarding the issue described above that Frank and I are having, I've
[05:50] <kylem> narrowed it down to commit e9e2cdb4[1] : [PATCH]  clockevents: i386 drivers
[05:50] <kylem> heh, must be the same problem.
[05:52] <BenC> mjg59: It didn't work for me
[05:52] <BenC> kylem: same commit that Tim and I came up with
[05:52] <BenC> so three of us separately bisected to the same one
[05:53] <kylem> check out the message from Linus there.
[05:53] <BenC> yeah, I'm about to test that
[05:53] <BenC> kylem: data point, x86_64 kernel boots fine for me
[05:53] <kylem> BenC, it would, it uses completely different code.
[05:54] <BenC> another reason to merge i386/x86_64 :/
[05:54] <mjg59> Andi insists on maintaining different timer code because, erm, well.
[05:55] <kylem> BenC, well, x86_64 hasn't got the new time code yet, because it's still buggy. (clearly. :)
[06:13] <amitk_> mjg59: Patch looks good. Can you send it with a sign-off?
[06:13] <mjg59> amitk_: Didn't it have one?
[06:14] <mjg59> amitk_: Oh - I tried to mail you, but<EMAIL_ADDRESS>doesn't work
[06:14] <mjg59> It's on lkml and usb-dev
[06:14] <kylem> mjg59, it's just amit@
[06:17] <amitk_> mjg59: thanks
[06:22] <BenC> rebooting to test the amd broken timer thing
[06:29] <BenC> sweet, it worked
[06:32] <kylem> yeah, i figured it would. the probelm seems to be with nohz, you can't turn off the lapic timer
[06:33] <BenC> I wonder if "nolapic nohz=on" would work
[06:33] <BenC> err nohz=off
[06:34] <BenC> kylem: do you think forcing "return 1" is a good work around for us to use?
[06:34] <BenC> in production I mean
[06:35] <BenC> kylem: does a broken lapic timer mean that kernel disabled nohz?
[06:35] <kylem> i say we add the proper define in now (test the cpuid) and reevaluate the decision after before -rc?
[06:35] <kylem> a lot of testing should happen for beta, so we can see if the issue reoccurs now that we know what to do...
[06:36] <BenC> kylem: you sounds like you're on top of this...can you get a patch in, and a new kernel today (or before Monday)?
[06:37] <kylem> BenC, er, well, need info from you or tim first.
[06:37] <BenC> let me know what you need and I can get it
[06:37] <kylem>  (b) make that function print out the values it uses for debugging (ie the
[06:37] <kylem>      xtended family and model numbers, and the MSR_K8_ENABLE_C1E MSR
[06:37] <BenC> I assume cpuid
[06:37] <kylem>      values)?
[06:37] <kylem> right.
[06:37] <BenC> ok
[08:00] <Nafallo> BenC, mjg59: I think the damn upgrade fixed it.
[08:00] <Nafallo> BIOS
[08:00] <mjg59> Nafallo: Hurrah. Does it work without noapic now?
[08:00] <Nafallo> mjg59: I think so. I'll check my commandline :-)
[08:01] <Nafallo> [   64.748254]  Kernel command line: root=/dev/md1 ro console=tty0 console=ttyS0,38400n8 break=premount
[08:01] <Nafallo> :-D
[08:01] <mjg59> Excellent.
[08:01] <Nafallo> too easy :-P
[08:01] <Nafallo> why didn't I think about this before? :-)
[08:12] <rtg> BenC or mjg59: Am I smoking crack on this one: https://bugs.launchpad.net/ubuntu/+bug/129477 ? What does a Synaptics touchpad do under windows that these guys expect?
[08:13] <mjg59> rtg: It's a new-model ALPS pad. The kernel doesn't recognise it.
[08:13] <rtg> mjg59: So PS/2 emulation is the best we can expect w/Feisty, right?
[08:13] <mjg59> With Feisty, yes
[08:14] <rtg> mjg59: Thanks.
[08:15] <mjg59> rtg: In PS/2 emulation mode it only reports relative motion. In native mode it gives absolute coordinates which give the synaptics userspace driver the ability to implement additional functionality (like scrolling)
[08:15] <rtg> I guess I've never used a touchpad like taht.
[08:16] <mjg59> Basically everything (other than very old stuff and bleeding-edge alps) works like that in Linux
[08:19] <Nafallo> http://home.nafallo.info/bugs/sata_nv.txt btw :-)
[08:19] <Nafallo> I can't see anything weird :-)
[08:21] <mjg59> Yeah, looks fine
[08:21] <mjg59> Note how stuff is all on different interrupts now
[08:26] <gnomefreak> we are tptally against putting 2.6.23 in multiverse right?
[08:26] <gnomefreak> totally even
[08:26] <mjg59> Do you mean universe?
[08:27] <gnomefreak> yeah sorry
[08:27] <mjg59> And I suspect the answer is yes
[08:27] <gnomefreak> someone asked this this morning im getting around to it now
[08:27] <zul> i am against it
[08:27] <gnomefreak> once gutsy stable we cant really touch it
[08:28] <infinity> We've had newer kernels in universe before, and it was a complete disaster.
[08:29] <infinity> So, yeah, we're pretty firmly against repeating that fiasco.
[08:30] <mjg59> Oh, yes, I'd forgotten that
[08:30] <mjg59> 2.6.11, wasn't it?
[08:30] <mjg59> Back in Hoary
[08:30] <infinity> Yeah.
[09:24] <rtg> mjg59: I'm about to instrument a Feisty kernel to extract the Dell 1420 ALPS touchpad E7 report. Is there an easier way? Do you think simply adding alps_model_info will enable the scroll bars?
[09:25] <mjg59> rtg: The issue came up on lkml - simply adding the device to the table didn't seem to work, so I suspect the protocol has changed slightly
[09:25] <rtg> mjg59: drat.