[00:14] <Nashenas> Hey guys. I was wondering if anyone has heard about a bug related to kernel panics and wireless network use
[00:16] <jmarsden> Nashenas: You'll need to be a lot more specific than that!  Haev you searched Launchpad for similar bugs?
[00:16] <Nashenas> I've been having some trouble searching for related bugs
[00:18] <jmarsden> So you searched LP for the keywords wireless, kernel and the wireles chipset concerned, and what did that show you?  Or do you need help figuring out how to search?
[00:18] <Nashenas> pretty much what happens is I'll be connected to some wireless network, and after some random amount of time, my computer freezes, and my keyboard lights are flashing, and this will happen no matter how much information I'm sending through the network
[00:18] <Nashenas> well I haven't searched launchpad, I was using google
[00:18] <Nashenas> is it just launchpad.com?
[00:20] <jmarsden> That should work, or www.launchpad.com
[00:20] <jmarsden> So go ahead and search there, come back here and ask again if you can't find anything similar to your bug.
[00:22] <Nashenas> ok i think i found something related, but just to be sure how do I check if I have a certian driver installed? (the one in question is iwlagn)
[00:34] <angusthefuzz> Nashenas: it should be visible in lsmod if its currently active
[00:35] <Nashenas> angusthefuzz: thanks
[00:36] <Bassetts> hello, I have a rather big showstopper but on intrepid and have been searching for it on launchpad for a while before I submit it myself. I have finally found the exact bug that has already been reported and would like to comment that I have the same problem as the OP. Are there any files I should include to aid with fixing it?
[00:37] <angusthefuzz> Bassetts: what is the bug number
[00:37] <Bassetts> the bug I am looking at is 272247
[00:37] <angusthefuzz> bug #272247
[00:38] <hggdh> Bassetts, yes, depends on what the bug is about. You can check https://wiki.ubuntu.com/DebuggingProcedures
[00:38] <hggdh> ah we now have a bug number
[00:39] <angusthefuzz> Bassetts: that bug seems to be very well taken care of, and has many log files attached, do you see where it says "This Bug doesnt affect me" at the top under the title?
[00:39] <angusthefuzz> Bassetts: you could select the change link in parentheses
[00:39] <Bassetts> yes
[00:39] <Bassetts> so just subscribe to the bug?
[00:40] <angusthefuzz> Bassetts: you should also subscribe yes, so you get updates
[00:40] <Bassetts> thanks
[00:40] <hggdh> sigh... another bug full with "me too" and other issues
[00:40] <angusthefuzz> no problem!
[00:40] <angusthefuzz> yeah, i wish everyone would ask here first :-)
[00:41] <Bassetts> I also saw they was mentioning doing a "kernel bisect" but the OP did not have much time to carry this out, would it be worth me offering to help out as I have a few days off college each week lately
[00:41] <hggdh> Bassetts, angusthefuzz is correct -- the bug has already been confirmed upstream. It may be that, in between the comments, there is a workaround
[00:42] <hggdh> Bassetts, if you know what a bisect means, yes. I strongly suggest checking the upstream bug for developer comments
[00:42] <Bassetts> right ok, hggdh I saw a lot are reporting booting with nolapic works so I will try that
[00:43] <Bassetts> hggdh: I have no idea what it means but would be more than willing to attempt it if it helps out
[00:43] <hggdh> :-)
[00:43] <hggdh> this is finding a change within git, the upstream source code control system
[00:44] <Bassetts> I will go find my intrepid liveusb and see if nolapic works, I have been using noacpi and acpi=off but that causes the problem of power manager not working
[00:44] <hggdh> probably not something you want to face if you are starting
[00:44] <hggdh> yes. nolapic may cause some other things to break, though.
[00:45] <Bassetts> hggdh: I am not just starting, been around a few years but I am far from a fully competent user =p
[00:45] <hggdh> Bassetts, sorry, I meant starting on kernel debug and git
[00:46] <Bassetts> ahh, yeh that I have never attempted or read about
[00:46] <hggdh> anyway -- strongly suggested to look at the upstream bug
[00:46] <angusthefuzz> Bassetts: this could be your moment to rise to the top and join the elite group who have successfully performed a kernel bisect
[00:46] <Bassetts> angusthefuzz: I will if I can find some nice person who would help me out
[00:46] <Bassetts> seems a bit daunting
[00:47] <hggdh> no, upstream still has the bug as new
[00:47] <ScottK> Seems that way because it is.
[00:47] <hggdh> try a boot without usplash
[00:47] <hggdh> if it works, you have a workaround
[00:47] <Bassetts> hggdh: that does not help
[00:48] <hggdh> Bassetts, it does not help in what sense?
[00:49] <Bassetts> as in the problem persists
[00:49] <Bassetts> with no splash you get the "Loading..." (or something similar) text and that just sits there
[00:49] <hggdh> I agree. This is why I stated "workaround", not solution.
[00:49] <hggdh> take out usplash and quiet
[00:49] <Bassetts> until you press a key then you get some messages until you let go and it hangs again, so its the exact same problem
[00:50] <Bassetts> hggdh: you still have to hold a key down for it to boot =(
[00:50] <Bassetts> the only difference is you have a text loader rather than a graphical
[00:51] <Bassetts> what is the best course of action for me to take in order to help get it fixed as fast as possible
[00:51] <hggdh> so usplash is just noise in the bug comments
[00:52] <hggdh> 1. try nolapic
[00:52] <Bassetts> indeed
[00:52] <Bassetts> just setting up my liveusb to try that hggdh, seems I buggered it slightly
[00:52] <hggdh> 2. read the whole thread, weeding out the useless comments
[00:53] <Bassetts> also doing =)
[00:56] <hggdh> Bassetts, may I ask a favour, then?
[00:57] <Bassetts> hggdh: ok
[00:57] <hggdh> when you have the thing summarised, please add a comment on what you found -- we will, then, change the description to point to it
[00:58]  * hggdh *has* to get to dinner or S.O. will have a fit
[00:58] <Bassetts> hggdh: so once I have waded through the amazing amount of poor quality comments and found the truth from it and uncovered a workaround just post my findings on launcpad?
[00:58] <Nashenas> hey guys, I'm back again, turns out the bug I thought I had was something different
[00:59] <hggdh> yes -- welcome to the triage hard work ;-)
[00:59] <Nashenas> any tips on narrowing down a search?
[00:59] <Bassetts> hggdh: thanks =)
[00:59] <hggdh> sorry, Bassetts... welcome to the grind
[00:59] <angusthefuzz> Bassetts: if you uncover a workaround I would definitely post it, also come back here and tell one of us so we can put it in the bug description (to save people reading the comments)
[00:59] <Nashenas> right now I have "kernel panic iwl3945 2.6.27-7" but it's also including links to some that don't include all of those keywords
[00:59] <Flare183> Any bugs, that you guys want me to take a look at?
[01:00] <Bassetts> angusthefuzz: would specifying a boot flag be considered a work around?
[01:00] <hggdh|away> if it works yes!
[01:00] <Nashenas> Bassetts: yes
[01:00] <angusthefuzz> Bassetts: anything is considered a workaround if it makes it work
[01:00] <Bassetts> ok =)
[01:00] <Bassetts> just checking
[01:00] <angusthefuzz> Bassetts: except for things involving a soldering iron
[01:01] <Bassetts> damn
[01:02] <hggdh|away> or a hammer
[01:02]  * hggdh|away is really gone now
[01:02] <angusthefuzz> Flare183: you could take a look at bug #220501
[01:02] <angusthefuzz> Flare183: all those people are experiencing kernel panics, probably each have a different reason
[01:02] <Flare183> umm let me see...
[01:02] <Nashenas> ubottu: isn't that a kernel panic?
[01:03] <Nashenas> that's like ... exactly the problem I'm having
[01:04] <angusthefuzz> that bug is going to take some serious triaging to get each of them to file new reports with the correct logs
[01:04] <Nashenas> angusthefuzz: any idea how to figure out what's causing a kernel panic?
[01:05] <Nashenas> angusthefuzz: because I have one, but I'm having lots of trouble trying to figure out what's causing it.
[01:05] <angusthefuzz> Nashenas: certainly, start here: https://wiki.ubuntu.com/KernelTeamBugPolicies
[01:13] <Nashenas> angusthefuzz: I read that page, but before posting I wanted to make sure I'm not creating a new report if one already exists. is there any way I could narrow down my search on launchpad, since "kernel panic iwl3945 2.6.27-7" gives me 798 matches...
[01:14] <angusthefuzz> Nashenas: one moment
[01:16] <angusthefuzz> Nashenas: its really easy for a triager to create a duplicate later, since kernel panics can be pretty system specific, you should create a new bug against the linux package with all the required files found in the debugging guides
[01:16] <angusthefuzz> Nashenas: let a kernel triager decide if the bug is a duplicate and at least the info you added can be included when helping the devs
[01:17] <Nashenas> angusthefuzz: should I put one up on launchpad too?
[01:18] <angusthefuzz> Nashenas: thats what i mean, file a launchpad bug
[01:18] <angusthefuzz> for the linux package
[01:18] <Nashenas> angusthefuzz: ok thanks for the help
[01:19] <angusthefuzz> Nashenas: good luck, panics are tough for everyone
[01:21] <Nashenas> angusthefuzz: is there anyway to upload more than one file per submission?
[01:21] <angusthefuzz> Nashenas: when the bug is created just go in and add the rest of the files
[01:22] <Nashenas> angusthefuzz: thanks
[01:26] <Nashenas> thanks, it's bug 296578 now
[06:42] <dholbach> good morning
[08:17] <thekorn> good morning
[11:15] <reic> hi there, i could use some help triaging a bug
[11:18] <arno_b> reic: what is your problem?
[11:18] <reic> i'm trying to help triage the following bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/295414
[11:19] <reic> now i could use some help, i'm not sure whether i chose the right package for this bug (i.e. possibly network-manager?) and i don't know whether i can confirm this bug right now
[11:23] <arno_b> reic: it is a duplicate, I am looking for the original report*
[11:24] <reic> thank you
[11:32] <arno_b> reic: finally, i found: see bug 292054
[11:32] <arno_b> reic: i have the same problem at work :s
[11:33] <reic> thx, I'll have a look (sry for your trouble at work though ;) )
[11:33] <arno_b> reic: and it is not a linux problem, but a network-manager problem (you may change the related package)
[11:34] <reic> k
[11:40] <LimCore> gnome keyring fails epically to store password. Report it against which package?
[11:41] <LimCore> oh, there IS a gnome-keyring.  silly me.. nm :)
[11:42] <Hobbsee> WFM.
[11:42] <Hobbsee> afaik, anyway
[11:54] <LimCore> It seems like 8.10 is really having growing-pains now.
[11:55]  * LimCore found epic bugs regaring password storage in both gnome and kde; and problems with upgrade from 8.04. Also, some packages seem broken (dependencies)
[11:55] <LimCore> on the other hand,  the G3 and wifi support is good
[11:56] <LimCore> 1) There is no package name 'nm-applet' published in Ubuntu
[11:57] <LimCore> 2) but:  [Select a Package] nm-applet  This is a transitional package to provide early a...
[11:57] <LimCore> ^-- is this a bug in launchpad?
[14:38] <LimCore> any G3 modem owner?  Need to confirm: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/296741
[15:16] <xteejx> bug 186347: Should the status on the alsa part of this bug also be changed to Fix Released?
[15:21] <bddebian> Boo
[15:22] <hggdh> pedro_, ping
[15:22] <pedro_> hggdh: hey hey
[15:22] <hggdh> good morning to you (or whatever)
[15:23] <pedro_> to you too :-P
[15:23] <hggdh> got a question re. bug 205999
[15:24] <hggdh> upstream (mcrha) has put out a tentative patch for it, but the new version is requiring EDS 2.25.2
[15:24] <hggdh> originally I was trying to get it for Hardy (2.22.x), and Intrepid (2.24.x)
[15:25] <hggdh> we can still adjust somewhat either the new one, or the old patch (not perfect, but solves the problem).
[15:25] <hggdh> so the question: what is the standard operating procedure on this type of situation?
[15:26] <pedro_> mm the patch introduce a new string
[15:26] <hggdh> not only the string, but the prereq on eds trunk
[15:27] <pedro_> we probably have to wait till jaunty to have that fixed because of the requirements
[15:28] <hggdh> the problem is -- for hardy and intrepid -- this means users will be unable to send attachments to Outlook adn GMail
[15:28] <hggdh> which is -- methinks -- bad
[15:28] <pedro_> doesn't look ok to make an sru for something that introduce new strings and depends on a newer version of eds
[15:29] <hggdh> no, I cannot see a SRU -- too many dependencies
[15:29] <persia> Does it *really* need eds trunk, or can a complimentary patch be extracted for EDS?
[15:29] <persia> There's a fair history of complimentary patches if the regression risk is sufficiently low, and the exposure sufficiently high.
[15:29] <hggdh> persia, I am checking on that right now (building trunk, making sure it works, then adjusting to 2.22 and 2.24
[15:30] <hggdh> or, at least, 2.24
[15:30]  * persia would have started by reading the EDS commit log to see which might be the interesting bit, but isn't going to argue over workflows :)
[15:31] <hggdh> heh :-)
[15:31] <hggdh> there are two tracks here: (1) make sure the patch resolves the issue on trunk; (2) backporting it, or something like it...
[15:31] <hggdh> I am on the (1) right now
[15:32] <persia> Ah, yeah, fixing the current devel release should always be the priority :)
[15:32] <hggdh> well, until this version of the patch, we were testing on 2.22 and 2.24
[15:32] <hggdh> not on trunk
[15:33] <hggdh> we did publish test packages (in my PPA) for users to try it
[15:36] <hggdh> and it does not make sense for me to start backporting the patch before being sure it works...
[15:37] <hggdh> so this is why I am raising the issue here. We can bypass the whole mess by using the previous patch on 2.22 and 2.24
[15:37] <hggdh> but there are some sonsequences
[15:38] <hggdh> s/sonse/conse/
[15:39] <persia> consequences tend to reduce the chance of SRU.
[15:40] <hggdh> yes... the issue is the previous patch makes it default for Evo to code attachment filenames out of rfc2231
[15:41] <hggdh> (the original issue was -- when using extended charsets, either ISO-8859-x or UTF-8, Outlook and gmail would not be able to correctly parse the MIME headers
[15:42] <hggdh> so, on Outcrap you at "ATxxxxxx.dat", unknown MIME
[15:44] <hggdh> for Hardy, going to 2.25 Evo right now is extremely riscky -- the move to SQLite on 2.24 has added some serious issues, not yet resolved
[15:44] <hggdh> just for that, I cannot see a SRU there
[15:45] <hggdh> so: I would really welcome ideas or options. I would still like to solve the attachment issue for Hardy, at least
[15:46] <pedro_> well the change in eds doesn't look that bad
[15:47] <pedro_> hggdh: let's raise this with seb128 tomorrow, he's on holiday today
[15:47] <hggdh> seems rather small indeed (forgetting the strings issue).
[15:47] <hggdh> ah, that's why I could not find him... yes.
[15:47] <pedro_> yeah but i think we can avoid the glade string changes and just accept the ones going at gconf
[15:48] <hggdh> hum
[15:48] <pedro_> s/gconf/gconf schemas
[15:49] <hggdh> or accept them untraslatable?
[15:49] <pedro_> but anyways let's ask seb about it
[15:49] <persia> More untranslatable strings would be bad.
[15:49] <pedro_> yeah indeed
[15:49] <persia> On the other hand, coordinating the update with the translations team can work if you *really* need to change strings.
[15:50]  * hggdh bows to the sages, and humbly thanks the input
[15:56] <xteejx> hey hggdh, I resent that email with the bug numbers on it :) Hope its alright
[15:57] <hggdh> xteejx, yes, I saw it, just did not have time to go through. Will do, though. Thank you, and I hope you undesrtood why I asked for it.
[15:57] <xteejx> Hey guys, you see bug 186347, its kinda old, does the alsa part need set as fixed released as well if the linux bit is, and this just wasn't changed or is it to be left?
[15:58] <xteejx> hggdh: I did yeah, thanks :)
[16:00] <hggdh> xteejx, it seems it is resolved. You can ping crimsun to check, but it seems he forgot to close the alsa-driver invalid
[16:02] <xteejx> hggdh ok will do
[16:36] <samuraipengui1> Hey, so, if i wanted to assist in a specific pet-peeve bug (109289), what can i do?
[16:38] <samuraipengui1> It's just a matter of using a new version from the developer.
[16:49] <hggdh> bug 109289
[16:52] <persia> samuraipengui1, If you think the best solution is to use the newest upstream version, and you want to help, I'd recommend trying to package the new upstream, attaching the updated diff.gz to the bug, and subscribing the sponsors team.  The team in #ubuntu-motu might be able to help.
[16:52] <samuraipengui1> Persia: cool.  I was just reading the wiki page on packaging.  I'll try my hand at it.
[16:52] <persia> samuraipenguin, Good luck.
[16:53] <persia> I think there's a special page with a guide for updating a package somewhere in there, although I'm not finding it right now.
[16:56] <jmarsden> https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[17:06] <nhandler> samuraipenguin: They also have: https://wiki.ubuntu.com/MeetingLogs/devweek0809/PackageUpdates which talks about updating a package
[17:08] <persia> That's precisely the page I sought.  Thanks nhandler
[17:11] <nhandler> You're welcome persia
[17:44] <xteejx> I've seen people reporting bug in Jaunty, how is this possible?
[17:45] <xteejx> *bugs
[17:45] <greg-g> xteejx: because development has (kinda) started on it
[17:46] <xteejx> greg-g: Oh right, is there any way to upgrade to it or help test it?
[17:46] <greg-g> the repositories are open
[17:46] <greg-g> heh, I wouldn't right now if I were you
[17:46] <greg-g> unless you want all kinds of breakage
[17:46] <xteejx> Nah its kool I got an old dev installation anyway spare :)
[17:46] <greg-g> you can do it in a Virtual Machine, but I would personally wait until after UDS (second week of December)
[17:46] <xteejx> Oh the big meeting?
[17:47] <greg-g> yeah
[17:47] <Pici> I wouldn't even put it on a dev machine now.
[17:47] <xteejx> How do you get to go to these things anyway?
[17:47] <xteejx> Probably not many normal users, if any lol
[17:48] <xteejx> Is there any way I can do it anyway, just to see :)
[17:48] <Pici> Do what?
[17:48] <xteejx> I'm intrigued
[17:48] <xteejx> Get Jaunty
[17:48] <xteejx> Do I just change the repos in sources.list to jaunty?
[17:52] <persia> Well, don't do it now : it's very broken.  https://wiki.ubuntu.com/JauntyReleaseSchedule says that the first test images are expected next week, at which point it might be safe to test a little.  Before then is extra risky.
[17:52] <xteejx> oh right ok, as of next week then i'll start helping out with that too :)
[17:56] <persia> It's still going to be *extremely* unstable next week, but it ought to at least install.
[17:59] <samuraipenguin> xteejx: i don't mean to sound harsh, but if you want the absolute latest packages, why not use a distro with a rolling release schedule like debian Sid or Archlinux?
[18:01] <greg-g> samuraipenguin: I think he is more interested in helping with bug triaging, not exactly getting the latest packages for use.  But yes, you are right.
[18:01]  * greg-g made an assumption on gender, my apologies if incorrect
[18:01] <samuraipenguin> Ah, yeah, you're probably right.
[18:02] <persia> samuraipenguin, Is there a specific reason why Ubuntu can't also fill that niche?  Except during archive freeze, and in the first couple weeks after archive open, it's just as unreliably variable as any average rolling-release distro.
[18:04] <samuraipenguin> persia: i'd point to this moment in time as an example.  intrepid is released, and major package updates won't be coming down the pipe in usable form for at least another few weeks.
[18:06] <persia> samuraipenguin, Hrm?  That's mostly a side-effect of the Debian Lenny freeze, rather than because of how Ubuntu works.
[18:06] <persia> sid isn't currently rolling.
[18:06] <persia> If it were, Ubuntu would be pulling it all right now.
[18:07] <samuraipenguin> Oh?  I admit my newbishness on this side of things, but I thought sid was debian's eternal-testing release?
[18:08] <samuraipenguin> (sorry, i didn't mean to pull the channel OT)
[18:19] <persia> samuraipenguin, sid is Debian's eternal testing release.  It's currently not very active because most of the Debian developers are focusing on the impending release.  Ubuntu is currently pulling every upload from either directly into the archives, or into the merge management tools.
[18:20] <persia> Because of the disruption this causes, it's risky to upgrade immediately after archive open, as the backlog from the freeze is building.  After that, it's somewhat more testable, although Alpha milestones of Ubuntu are at least as likely to break as sid, and when that happens, you get to keep both pieces :)
[18:40] <bucket529> Bug 245074 is a sync request frum July 08 - but rmadison currently shows Jaunty and Debian match (already looks synced). Should I close the bug? Or leave it alone?
[18:42] <chrisccoulson> it should be closed if it has been sync'd and debian doesn't have a newer version
[18:43] <persia> There's a lot of autosync that happens at the beginning of each cycle, and sometimes there's leftovers like that.  Always best to close them (it's one of the few cases of the "workflow" bugs where the participants in the workflow will thank you for the adjustment).
[18:43] <bucket529> Thanks, closing it.
[18:50] <ScottK> Mark it fix released.
[18:52] <samuraipenguin> so, re: bug 109289 I'm a bit confused.  In different places, i'm advised to build the .dsc and .deb, or just diff the source tarballs and upload that diff to the bug.
[19:34] <hggdh> samuraipenguin, I guess you can do either. You can also build the fixed package and publish on your PPA
[19:34] <hggdh> there has been talk about requiring a debdiff, or just a diff
[19:39] <samuraipenguin> hm, okay.  I'm going to run through it one more time to make sure i've got it right and then upload the debdiff.  Thanks!
[19:42] <hggdh> samuraipenguin, it might be a good idea to build it locally and see if it works before uploading the diff
[19:43] <samuraipenguin> hggdh: indeed.  That's what i'm doing
[19:52] <unenough> my intrepid has random mouse clicks and scrolles. it's really annoying. using toshiba a215, that has a Synaptics Touchpad
[19:52] <unenough> scrolles=scrolls :)
[19:52] <unenough> this didn't happen in Hardy
[19:54] <unenough> i turned off vertical/horizontal scrolling and tapping using the touchpad but it still happens
[19:57] <hggdh> samuraipenguin, thank you, and sorry for stating the obvious
[20:18] <balachmar> Hi, I guess I just experienced bug 279192 But I don't know if I can add some more info to the report that can be helpful. Maybe someone could have a look at it?
[20:55] <crimsun> xteejx: #186347 doesn't affect alsa-driver; we don't backport fixes to alsa-driver (to end up in alsa-source), only l-u-m or linux.
[21:10] <drguildo> should i bugs i encounter to launchpad or upstream?
[21:10] <drguildo> *report
[21:16] <crimsun> drguildo: bugs in what?
[21:18] <drguildo> heheh
[21:18] <drguildo> a few things
[21:18] <drguildo> alsa/pulseaudio mostly
[21:18] <drguildo> but i'm also getting graphical corruption when using the compiz stuff
[21:19] <drguildo> and i don't seem to be able to skip in mp3 files in rhythmbox
[21:21] <drguildo> sound is uber-broken for me in 8.10
[21:25] <crimsun> drguildo: generally, file them in launchpad.
[21:25] <crimsun> drguildo: what specific issues are you having with alsa and pulseaudio?
[21:25] <crimsun> drguildo: (for support, we can migrate to #ubuntu or #ubuntu-audio-help instead of using this channel)
[21:26] <drguildo> the reason i ask is that a lot of the stuff i report gets ignored for loooong periods of time and i'm wondering if i'm filing stuff in the wrong place or doing something else wrong
[21:27] <drguildo> #ubuntu-audio-help sounds good
[21:29] <crimsun> drguildo: ignored is perhaps the wrong word, though I understand an end user's perspective.  It's more that there really are only two people who triage audio bugs for all of Ubuntu, and really we're extremely taxed on resources.
[21:29] <drguildo> oh ok
[21:29] <crimsun> drguildo: (also, the audio stack mess takes a while to dig through)
[21:29] <drguildo> i can imagine
[22:08] <rrittenhouse> Does anyone here use Twitux on Ibex?
[22:38] <chadwik> can someone set bug 296773 to wishlist status pls
[22:40] <wolfger> Looking at Bug 185334. It's marked fix released for linux, but incomplete for the specified kernel version. Should that be an invalid/won't-fix?
[22:57] <jibel> chadwik: instead of changing the behavior of fsck for this corner case it would be wise to suggest to the user to disable time-dependent checking
[22:58] <jibel> chadwik: according to man tune2fs it's something like /tune2fs -i 0 /dev/sdX /
[22:58] <chadwik> jibel: hi yeh i did mention that aswell, should i just set it to inactive then?
[23:00] <chadwik> err invalid i mean :)
[23:02] <mrooney1> could be more of a wontfix, perhaps
[23:03] <jibel> chadwik: oh, ok I had seen the standard response and not the last part of it. I would set it to incomplete and wait for his answer. If he is ok with the workaround then close it.
[23:03] <jibel> chadwik: it is not a bug with fsck but with his system indeed.
[23:03] <chadwik> jibel: ok thanks
[23:07] <sparr> how can i find out what version this wants but cannot find? if the version it wants doesn't exist, is that a dependency bug?  "E: Build-Depends dependency for gcc-avr cannot be satisfied because no available versions of package binutils-avr can satisfy version requirements"
[23:09] <TiMiDo> yes indeed sparr that looks. like a bug
[23:11] <sparr> my repositories and apt preferences are...  non-trivial, can anyone confirm with a normal setup?
[23:12] <sparr> i need to install vanilla ubuntu on something for testing stuff like that
[23:19] <chrisccoulson> sparr - what are you trying to do?
[23:24] <sparr> apt-get build-dep gcc-avr
[23:24] <chrisccoulson> 1 seocnd
[23:24] <chrisccoulson> 1 second, even
[23:26] <chrisccoulson> bizarre
[23:27] <chrisccoulson> gcc-avr depends on binutils-avr >= 2.18-4, but Intrepid only have 2.18-3
[23:27] <chrisccoulson> don't know how it ever built
[23:28] <chrisccoulson> ah
[23:28] <chrisccoulson> ok, it has never actually built. it is sat at dep wait on binutils-avr
[23:30] <chrisccoulson> that's actually fixed in jaunty btw, but the package still failed to build