[02:22] <dohboy> is anyone else having trouble with their wifi card with the latest build?
[02:23] <secretlondon> it's unlikely to affect all wificards, if we do have a prob it's much more likely to affect specific chipsets
[02:23] <crimsun> "latest build"?
[02:23] <crimsun> if you're running hardy, see the topic of #ubuntu+1.
[02:23] <secretlondon> I presume he means currently updated
[02:23] <dohboy> thx
[02:24] <secretlondon> ah that would be useful to know here too
[02:24] <dohboy> ah, the topic in #ubuntu+1 explains everything.. thanks :)
[02:26] <crimsun> yep, that's why I set it.
[03:07] <secretlondon> crimsun: is there a main bug for "network manager in hardy is broken"?
[03:09] <crimsun> yes
[03:11] <secretlondon> 198971?
[03:11] <secretlondon> bug #198971
[03:11] <ubotu> Launchpad bug 198971 in network-manager "[Hardy] Wireless broken with latests updates" [Undecided,Fix released] https://launchpad.net/bugs/198971
[03:12] <crimsun> (yes, I just triaged it and its dupe)
[03:13] <secretlondon> ok I've just set priority to 'high' on it to take it easier to find
[03:13] <secretlondon> it'll take a while for the fix to get out so we'll prob get loads of dupes
[03:13] <crimsun> thanks :)
[03:16] <Jimerson> Good evening all.
[03:18] <secretlondon> evening
[03:19] <Jimerson> I have been reading through the wiki and I am interested in trying to help with bug Triaging.
[03:19] <secretlondon> cool
[03:19] <Jimerson> I was wondering how I could go about finding a mentor..
[03:20] <secretlondon> there isn't a formal mentoring process although this channel is a good place to ask questions
[03:20] <secretlondon> there is a hug day tomorrow which is a day dedicated to squashing bugs on particular packages
[03:21] <Jimerson> I was reading about that.
[03:21] <secretlondon> there will be more people around in the channel
[03:21] <Jimerson> Can you point me in a good place to get started?
[03:22] <Jimerson> All the bugs I have seen so far someone has responded to.
[03:22] <secretlondon> tomorrow there will be a list of bugs to work through
[03:23] <secretlondon> I think a hug day is a good place to start
[03:23] <Jimerson> Sounds good.
[03:45] <secretlondon> ogra: main inclusion request filed on sdlpango to fix tuxtype ftbfs
[03:58]  * techno_freak visits #ubuntu-bugs-announce
=== keescook_ is now known as keescook
=== boomer` is now known as boomer
[05:21] <greg-g> bug 162470
[05:21] <ubotu> Launchpad bug 162470 in amarok "Amarok can't fast-forward FLAC files." [Undecided,Confirmed] https://launchpad.net/bugs/162470
=== bdmurray changed the topic of #ubuntu-bugs to: Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20080306 | Ubuntu BugSquad | Bug announcements have moved to #ubuntu-bugs-announce | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ - http://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
=== bigon` is now known as bigon
[09:43] <elmargol> bug #191512
[09:43] <ubotu> Launchpad bug 191512 in nautilus "gnome displays nfs mounts on the desktop" [Undecided,New] https://launchpad.net/bugs/191512
[09:43] <elmargol> very anoying bug
=== doko_ is now known as doko
[10:19] <dholbach> bdmurray, thekorn: hey guys, could it be that LPTask.remote is always 'False' in textbugs?
[10:23] <thekorn> dholbach, hi, yes that's true,
[10:23] <thekorn> i did not know the text interface gives us this information
[10:24] <dholbach> thekorn: oh I don't know either if that information is available :)
[10:24] <dholbach> there's    watch: <url>
[10:28] <thekorn> dholbach, ok, I will try to add this to the text mode
[10:28]  * dholbach hugs thekorn
[10:28] <dholbach> bring it on!
[10:28]  * thekorn hugs dholbach
[10:43] <thekorn> dholbach, I think that's it: http://paste.ubuntu-nl.org/58584/
[10:46] <dholbach> thekorn: that looks great
[10:47] <thekorn> ok, let me commit it
[10:47] <dholbach> rock on
[10:49] <thekorn> bdmurray, dholbach: pushed as revision 73
[10:50] <dholbach> thanks thekorn :)
[11:47] <Iulian> Hi
[12:06] <techno_freak> Iulian, hi
[12:09] <Iulian> Heya techno_freak
[12:09] <Iulian> And heno
[12:10] <heno> hey Iulian
[12:14] <Iulian> heno: Btw, did you get my last mail?
[12:14] <Iulian> Uhmm, I didn't see pedro recently, is he on vacation?
[12:15] <heno> Iulian: I did. I'll activate it now
[12:16] <heno> pedro is at a FOSS conference in Peru I think
[12:17] <Iulian> Makes sense now.
[12:17] <Iulian> heno: Thanks.
[13:03] <Iulian> Woahh!
[13:04] <Iulian> elmargol: Please fix your connection.
[13:08] <techno_freak> he he
[13:51] <qense> happy hug day!
[13:57] <Gnine> system > preferences > screen resolution INOP | system > administration > screens and graphics INOP | 8.04 2.6.24-11-generic amd64 x86_64
[13:58] <Gnine> nvidia proprietary driver in use
[14:01] <afflux> morning
[14:08] <qense> test: bug #1
[14:08] <ubotu> Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/1
[14:08] <qense> that still works
[14:12] <Iulian> It works in all Ubuntu channels.
[14:13] <qense> ok
[14:13] <qense> I didn't know that :), thx
[14:43] <afflux> How to handle a bug in the kernel that has been fixed in 2.6.24 but someone likes to see a fix for 2.6.22?
[14:48] <james_w> afflux: you mean in gutsy?
[14:49] <afflux> I think so
[14:49] <james_w> afflux: what's the bug number?
[14:49] <afflux> james_w: bug 196340
[14:49] <ubotu> Launchpad bug 196340 in linux-source-2.6.22 "Unable to handle kernel paging request" [Undecided,New] https://launchpad.net/bugs/196340
[14:54] <james_w> afflux: yeah, that's gutsy. That would require an SRU
[14:55] <james_w> I'm not sure what the kernel teams SRU policies are.
[14:56] <afflux> ah, just found "KernelUpdates" in the wik
[14:56] <afflux> *wiki
[16:32] <bdmurray> Hello bug huggers!  It sure is nice and quiet here
[16:32] <bdmurray> I meant w/o ubotu
[16:33] <bdmurray> afflux: did you get your question about kernel SRUs answered?
[16:34] <afflux> hi brian
[16:35] <bdmurray> hello
[16:35] <afflux> basicly, yes. however I wasn't entirely sure how to handle this in the bug and I ran out of time
[16:37] <bdmurray> It sounds to me like they are running their own kernel, even with 2.6.22.  Did you get that impression?
[16:40] <bdmurray> Okay, I read more.
[16:42] <bdmurray> Anyway, kernel SRUs are very rare as a regression could impact everyone.
[16:45] <Iulian> bdmurray: Yes, indeed, much better without ubotu messages. :)
[16:48] <afflux> bdmurray: the custom kernel was my impression, too.
[16:49] <bdmurray> I'm not certain how important it is in this case as he says its fixed in 2.6.24 and it isn't sru worthy.
[16:50] <bdmurray> One thing that might be interesting to know is which specifc kernel flavors he tested as they have different config options.
[17:12] <bdmurray> ogasawara: you just touched bug 196340 - can you tell from the oops report if the crash is specific to the vserver patches?
[17:12] <ubotu> Launchpad bug 196340 in linux "Unable to handle kernel paging request" [Undecided,Fix released] https://launchpad.net/bugs/196340
[17:14] <ogasawara> bdmurray: I can't tell with any certainty
[17:16] <bdmurray> ogasawara: okay, it seems like we would have heard about this before. would the specific kernel version matter or is generic sufficient?
[17:17] <ogasawara> bdmurray: I think he commented about the specific version
[17:18] <ogasawara> 2.6.22-14.47
[17:18] <bdmurray> Did I mean kernel flavor?
[17:19] <bdmurray> That changes the build options right?
[17:19] <ogasawara> bdmurray: yes, but I think generic should be fine
[17:20] <bdmurray> okay, thanks!
[17:48] <bdmurray> crimsun: does the alsa-info script reveal whether or not someone has l-u-m installed?
[18:01] <bdmurray> ogasawara: is there a xen version of 2.6.24 yet?  Where would I check myself?
[18:02] <ogasawara> there is - linux-image-2.6.24-11-xen
[18:02] <ogasawara> bdmurray: ^^^
[18:05] <bdmurray> ogasawara: but there is no live CD with that kernel so they'd have to install to test hardy...
[18:05] <ogasawara> bdmurray: unfortunately yes
[18:06] <bdmurray> mabye we should add that under the stock reply on the hug day wiki page then
[18:06] <ogasawara> bdmurray: good idea
[18:07] <bdmurray> what about -rt that should be on ubuntu studio right?
[18:07] <ogasawara> bdmurray: not sure on that one, but I can check
[18:08] <bdmurray> I'm not sure what their build cycle in regards to images is like
[18:09] <ogasawara> bdmurray: just checked the manifest and it looks like -rt is used
[18:15] <bdmurray> ogasawara: Uh, overclocking == weird things can happen right?
[18:16] <ogasawara> bdmurray: I'd think so
[18:59] <bdmurray> ogasawara: does "NCQ disabled due to excessive errors" sound familiar to you?
[19:00] <ogasawara> bdmurray: it does - which bug?
[19:00] <bdmurray> bug 156669 and bug 121273
[19:00] <ubotu> Launchpad bug 156669 in linux-source-2.6.22 "SATA drive freezes when using LVM over dm-crypt" [Undecided,New] https://launchpad.net/bugs/156669
[19:00] <ubotu> Launchpad bug 121273 in linux-source-2.6.22 "kernel panic with dm-crypt/luks + lvm + xfs + ubuntu kernel" [Undecided,New] https://launchpad.net/bugs/121273
[19:39] <bdmurray> ogasawara: I found bug 147858 related to ncq do you know what rtg's changelog comment means? "Add WD WD800ADFS NCQ horkage quirk support"
[19:39] <ubotu> Launchpad bug 147858 in linux "western digital WD800ADFS ncq problems" [Low,Fix released] https://launchpad.net/bugs/147858
[19:40] <ogasawara> bdmurray: was added to the blacklist
[19:40] <ogasawara> bdmurray: that was the NCQ bug I was thinking of which seemed different from the two you referenced
=== ember_ is now known as ember
=== stefanb_l is now known as smb_l
[21:38]  * secretlondon has had some pizza and is ready to start on bugs :)
[21:38] <greg-g> pizza and bugs, a powerful combination
[21:38] <secretlondon> indeed!
[21:39]  * Iulian is starving
[21:39] <bdmurray> mmm pizza
[21:39] <greg-g> look what you started secretlondon!
[21:39] <secretlondon> :)
[21:39] <Nafallo> ugh
[21:40] <Nafallo> !pizza
[21:40] <ubotu> Sorry, I don't know anything about pizza - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[21:40] <Iulian> Yeah, you shouldn't say anything about it!
[21:40] <Iulian> Bad bad!
[21:40] <Nafallo> stupid bot :-P
[21:40] <secretlondon> Nafallo you said you had pizza yesterday
[21:40] <Nafallo> secretlondon: yea, exactly.
[21:40] <Nafallo> secretlondon: ! == not
[21:40]  * secretlondon will be having pizza tomorrow too!
[21:40] <secretlondon> as I bought a big one
[21:42] <bdmurray> ogasawara: is there a pattern bad memory exhibits in a kernel call trace?
[21:42] <ogasawara> bdmurray: I don't know of any
[21:54] <crimsun> bdmurray: (RE: "does the alsa-info script reveal whether or not someone has l-u-m installed") yes, it does, but not directly
[21:55] <crimsun> bdmurray: it's normally fairly straightforward to ferret out by inspecting the reported kernel and alsa-driver versions
[21:56] <crimsun> bdmurray: granted, now that alsa is completely in l-u-m, we'll have to revisit the logic.  But for gutsy, at least, we can tell whether l-u-m and/or l-b-m are/is installed.
[22:06] <bdmurray> crimsun: okay, I don't recall which bug I was specifically looking at
[22:34] <bdmurray> ogasawara: how do I know if a driver is in l-u-m or not?
[22:35] <ogasawara> bdmurray: you can look at the lum git tree
[22:37] <bdmurray> gitweb is hard
[22:38] <ogra_cmpc> bdmurray, dpkg -S /path/to/.ko
[22:39] <bdmurray> ogra_cmpc: thanks, that's a bit better
[22:45] <bdmurray> ogasawara: How would I check the upstream kernel to see if a PCI ID is supported by a driver?
[22:46] <ogasawara> bdmurray: I usually just inspect the driver in the upstream git tree
[22:46] <ogasawara> bdmurray: which driver and which pci id are you looking for?
[22:47] <bdmurray> ogasawara: and you have it checked out I guess?  cx88 and 1822:0023
[22:47] <ogasawara> bdmurray: yup
[22:48] <ogasawara> bdmurray: just a sec, pulling in the latest changes
[22:55] <ogasawara> bdmurray: I'm not seeing it
[22:55] <bdmurray> and what about 1421 0334
[22:56] <ogasawara> bdmurray:                  .subvendor = 0x1421,
[22:56] <ogasawara>                 .subdevice = 0x0334,
[22:56] <ogasawara>                 .card      = CX88_BOARD_ADSTECH_DVB_T_PCI,
[22:57] <bdmurray> that's in cx88-core?
[22:57] <ogasawara> bdmurray: cx88-cards.c
[22:57] <bdmurray> right, I misclicked
[22:59] <bdmurray> don't most drivers use the vendor and device id - not the subsystem?
[23:06] <bdmurray> ogasawara: what about 1002:00f9 ?
[23:07] <ogasawara> bdmurray: I don't see that vendor id, what vendor is it?
[23:08] <ogasawara> bdmurray: PCI_VENDOR_ID_ATI?
[23:08] <bdmurray> yeah, 14f1:8800
[23:09] <ogasawara> bdmurray: I don't see 00f9, only 00f8
[23:09] <ogasawara>                 .subvendor = PCI_VENDOR_ID_ATI,
[23:09] <ogasawara>                 .subdevice = 0x00f8,
[23:09] <ogasawara>                 .card      = CX88_BOARD_ATI_WONDER_PRO,
[23:10] <ogasawara> bdmurray: 14f1:8800 I don't see
[23:21] <bdmurray> ogasawara: do you have stock needs upstream reporting reply?
[23:22] <ogasawara> bdmurray: sorta, https://wiki.ubuntu.com/KernelTeamBugPolicies - last few sentences of the "Reporting Bugs Upstream" section
[23:22] <ogasawara> bdmurray: last few sentences of the first paragraph
[23:23] <ogasawara> bdmurray: are you wanting to add the new device id's?
[23:23] <ogasawara> bdmurray: I know the kernel guys will sometimes add them and then push the patch back upstream
[23:24] <bdmurray> yeah, there is one I'm 90% certain of
[23:24] <bdmurray> I mean I know it doesn't exist and it seems like it should
[23:24] <ogasawara> bdmurray: if you can post a comment summarizing id's should be added then let me know the lp bug # I'll add it to the kernel list for next week
[23:31] <bdmurray> ogasawara: its bug 115719
[23:31] <ubotu> Launchpad bug 115719 in linux-source-2.6.20 "CX23880 PCI Video and Audio Decoder insmod failure" [Undecided,Won't fix] https://launchpad.net/bugs/115719
[23:31] <bdmurray> eh, I'll fix the summary too
[23:42] <bdmurray> ogasawara: I've found a bug that is fixed post 2.6.20.  Do you think it is worthing opening other affects for it just showing that it is fixed?
[23:42] <ogasawara> bdmurray: yah.  I typically open the task it was fixed against and mark it so
[23:43] <ogasawara> bdmurray: then I usually "won't fix" the older task assuming it's not a sru candidate