[06:28] <crimsun> it's actually suffixed with _i386?
[06:30] <crimsun> (i.e., there's http://archive.ubuntu.com/ubuntu/pool/main/l/linux-source-2.6.15/linux-image-2.6.15-16-amd64-generic_2.6.15-16.23_amd64.deb)
[07:03] <lamont> BenC: your kernel hates me
[07:21] <BenC> lamont: what's up?
[07:21] <lamont> BenC: linux-image-2.6.15-16-amd64-generic_2.6.15-16.23_amd64.deb panics very early during boot, in pci_mmcfg_read
[07:21] <BenC> lamont: why can't you just dpkg-deb --extract, dpkg-deb --control, change the Arch, and dpkg-deb --build it back :)
[07:22] <BenC> what sort machine
[07:22] <lamont> and, interestingly, 2.6.12-10-amd64-generic dies (2.6.12-10.28) with a segv during initramfs
[07:22] <lamont> that's what I did do to create the _i386.deb that is installed...
[07:23] <lamont> HP pavilion a1130n
[07:23] <lamont> OTOH, since 2.6.15 has that motherboard's double-time issue from 2.6.12 fixed for i386 as well as amd64, I'm now running an i386 kernel
[07:24] <lamont> which boots, (woot), and also eliminates that pesky issue wherein the scanner didn't work (PSC 2510, ioctls had some issues with 32-user/64-kernel)
[07:24] <lamont> whcih may or may not be fixed in 2.6.15 - can't check when it doesn't boot
[07:25] <lamont> BenC: having a bootable system again (that correctly keeps time), makes it so that I'm much less grumbly - I'll try -17.24 tomorrow evening, I expect
[07:26] <lamont> I'll also work on getting my amd64 dev/test machine booted
[07:29] <BenC> ok
[07:30] <BenC> 2.6.15 is working on my Athlon 64, so that's about as much testing as I've done
[03:48] <mxpxpod> BenC: ping


[12:35] <zeroseven0183> Hi! There are at least two people agreeing that this bug should be handled as Wishlist https://bugs.launchpad.net/clamtk/+bug/637940
[12:35] <ubot4`> Launchpad bug 637940 in clamtk "Unpleasant Pixel Icon (affects: 2) (heat: 12)" [Undecided,Confirmed]
[12:36] <Abhijit> zeroseven0183, so whats the question? mark it wishlist
[12:37] <zeroseven0183> I don't have the ability to mark it as wishlist. Only someone from Bug Control can. Right?
[12:37] <Abhijit> oh
[12:41] <zeroseven0183> Here's my question. What if the reporter opted out to be including in the mailing list for the particular bug he reported? Do we 'subscribe' him in order to get updates? Or just change the status of the bug report to Invalid?
[12:58] <Ampelbein> zeroseven0183: that depends on the issue. if it's a valid report, there is no reason to close it. the bug you mentioned above (637940) is btw not reported in ubuntu, but in the upstream project. that's why even bugcontrol can't change importance.
[12:58] <zeroseven0183> Yes, I later thought of that too (bug report upstream)
[13:02] <jporsini> Hello, on the bug page, 'Link a related branch' should be set to the current code branch or can it be set to a proposed bzr branch containing the fix?
[13:03] <Ampelbein> jporsini: branch containing the fix. if you use 'bzr commit --fixes XXXX' when commiting the change, the linking is done automatically.
[13:04] <jporsini> Ampelbein, hooo I was not aware of this "--fixes" option, I am going to set it manualy. Thanks for the information
[13:05] <Ampelbein> jporsini: if you are working on a debian/ubuntu package there is even more automagic: use (LP: #XXXX) in debian/changelog and 'debcommit' to commit changes and it will add commit message and fixes automatically
[13:06] <jporsini> Ampelbein, no, it is for feature that I have requested and is very specific to Ubuntu (more exactly to unity): bug #732848 . Anyway, I have put the (LP: #) in the changelog
[13:06] <ubot4`> Launchpad bug 732848 in liferea (Ubuntu) "Feature request: add unread items count in the Unity Launcher entry (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/732848
[13:36] <hggdh> jporsini, in fact the (LP: xxxxxx) must be in the changelog for Ubuntu bugs
[13:41] <jporsini_> hggdh, yes, I have put the (LP: xxxx) in the changelog
[16:11] <patrickmw> bdmurray: what is the name of the lp greasemonkey scripts project?  (can't find it)
[16:11] <bdmurray_> patrickmw: the project or the ppa?
[16:12] <patrickmw> project
[16:12] <bdmurray_> launchpad-gm-scripts I believe
[16:12] <patrickmw> thanks!
[16:13] <patrickmw> I'm looking to create a few of my own.  Using your scripts as examples
[16:14] <bdmurray> patrickmw: I strongly suggest you don't it can be quite maddening
[16:14] <patrickmw> bdmurray: wow.  that sounds quite adamant!
[16:15] <bdmurray> patrickmw: if you are determined I could point you in the right direction and give some advice
[16:18] <patrickmw> bdmurray: I'm trying to create a weekly bug report and I have some specific criteria I want it to display.  I also want the data in a simple text format to copy.  The built in reporting in LP gets me most of the way there, but I just need to tweak it
[16:20] <bdmurray> patrickmw: so launchpad has a search criteria that returns what you are looking for?
[17:26] <micromix> 12
[17:32] <penguin42> 12?
[17:33] <charlie-tca> 42
[17:33] <penguin42> much better
[17:36] <trinikrono> charlie-tca:  can you help me with bug 701060
[17:36] <ubot4`> Launchpad bug 701060 in ubuntu "Boot failure (affects: 1) (heat: 8)" [Low,New] https://launchpad.net/bugs/701060
[17:36] <trinikrono> i am running out of ideas as to what to tell the reporter
[17:38] <trinikrono> i got him to put up the bootchart pictures
[17:38] <penguin42> trinikrono: If you don't know what to say, then say nothing!   I've seen that bug as well with .04 - it's very broken somewhere
[17:41] <charlie-tca> trinikrono: has it failed since the reporter removed "quiet splash"? I don't see anything that says it did. leave the bug alone for a month and see what develops.
[17:41] <charlie-tca> penguin42: agreed.
[17:42] <JFo> I took a quick look as well
[17:42] <penguin42> I agree the priority should be higher, I'm not sure I could justify it, but  a bug affecting a lot of people with failed boot with no diags seems higher than that to me
[17:42] <JFo> I don't see anything in it that would make me think it would benefit from being looked at by the kernel team
[17:43] <penguin42> JFo: In that case who should look at it?
[17:43] <JFo> penguin42, I would think it might benefit from a glance by cjwatson, but he is always busy
[17:44] <JFo> and the majority of the kernel guys are in London just now
[17:44] <JFo> so they are likely done for the day
[17:44] <JFo> or I would ask one of them to look anyway
[17:45] <charlie-tca> What constitutes "a lot of people" on this bug?
[17:46] <charlie-tca> I see a single person affected, the reporter
[17:46] <trinikrono> i wish it do this on my pc so i can recreate the bug though
[17:46] <charlie-tca> Just leave it alone for while. The reporter is quick to tell when it fails
[17:47] <trinikrono> will do sir
[21:11] <ikt> For ubiquity, if there is a really small screen resolution, like 320x480, does ubiquity error and suggest a bigger screen or does it just try it's best to squash everything in?
[22:01] <penguin42> hehe don't know - what are you running it on?
[22:32] <wright_> hello
[22:32] <wright_> i just found serious bug in ubuntu
[22:34] <wright_> is there anyone?
[22:36] <wright_> is this the right place to report it?
[22:38] <charlie-tca> no, bugs should be reported to launchpad
[22:38] <charlie-tca> !bugreport
[22:38] <ubot4`> Factoid 'bugreport' not found
[22:38] <charlie-tca> !bugs
[22:38] <ubot4`> If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs - Bugs in/wishes for the IRC bots (not Ubuntu) can be filed at http://bugs.launchpad.net/ubuntu-bots
[23:20] <ikt> penguin42, just as a general test case