[00:58] <hggdh> mrooney, ping
[00:59] <mrooney> hggdh: hi!
[01:01] <hggdh> hi, I will sftp it over to xibiu
[01:06] <hggdh> mrooney, it is under /tmp/eeebotu
[01:07] <hggdh> mrooney, you will have to adjust the settings
[01:22] <mrooney> hggdh: okay!
[01:22] <dupondje> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/267612
[01:22] <dupondje> any id's ?
[07:30] <thekorn> good morning :)
[08:32] <nullack> Ping seb128 : I havent bugged the ffmpeg gstreamer plugin update as were involved in improving the process. Would you like to me help with writing a freeze exception rationale for this?
[08:32] <seb128> nullack: no
[08:33] <seb128> I've no clue of why ffmpeg should be updated
[08:33] <seb128> and I've too much to do without having to work on that
[08:33] <nullack> seb128: Im talking about the gstreamer plugin for ffmpeg
[08:33] <nullack> You did the good and ugly plugins recently
[08:33] <seb128> gst-ffmpeg uses the system ffmpeg on debian and ubuntu
[08:33] <seb128> you probably want ffmpeg updated
[08:34] <nullack> So to upgrade the plugin we need to upgrade all of ffmpeg?
[08:34] <seb128> not sure what plugins you want to update
[08:34] <seb128> but if you want to update the ffmpeg codecs you need to update ffmpeg-debian
[08:34] <nullack> The gstreamer plugin for ffmpeg
[08:35] <seb128> it's not clear what you are trying to get changed there
[08:35] <nullack> http://packages.ubuntu.com/intrepid/gstreamer0.10-ffmpeg
[08:36] <seb128> what is the issue exactly?
[08:36] <seb128> well, you can update gstreamer0.10-ffmpeg
[08:36] <nullack> Gstreamer released updates to their plugin which fixes numerous bufs
[08:36] <seb128> I'm not sure it'll bring anything though
[08:36] <nullack> I am
[08:36] <seb128> the package is built using --with-system-ffmpeg
[08:36] <seb128> are you sure those plugins are used in this case?
[08:37] <nullack> Im not sure about build specifics on Ubuntu but I am sure of improvements the new revision brings to our users
[08:37] <seb128> the ffmpeg-debian ones should be used rather
[08:37] <seb128> did you try it?
[08:37] <Drag0nLord> anyone ran into the MP-Bios Timer Not Connected To IO_APIC error?
[08:37] <seb128> it looks like you are advocating for a new ffmpeg
[08:38] <nullack> Mate I had hoped to not have to advocate the whole thing, just the gstreamer part
[08:38] <seb128> but since gstreamer0.10-ffmpeg uses ffmpeg-debian and not ithe gstreamer0.10-ffmpeg copy on debian and ubuntu upgrading gstreamer0.10-ffmpeg will not likely achieve what you want
[08:38] <nullack> But....ffmpeg is very old in the intrepid repos
[08:39] <nullack> Whos the maintainer of ffmpeg in Ubuntu? Not you I assume Sebastien?
[08:39] <seb128> not me no
[08:39] <seb128> I suggested you to ping siretart the other day no?
[08:39] <nullack> Yes I havent seen him so far
[08:39] <seb128> you can also try to talk to slomo but I think he's on holidays
[08:39] <seb128> maybe mail them
[08:39] <nullack> Right, stariek and slomo
[08:39] <nullack> Thanks Sebastien, have a good day
[08:40] <seb128> you're welcome
[08:40] <seb128> you might also want to start a discussion on the ubuntu-devel list about ffmpeg being outdated in ubuntu
[08:40] <nullack> I'll do that too, good suggestion
[08:41] <Drag0nLord> no one with the MP-BIOS error: Timer not connected to IO-APIC?
[08:42] <Drag0nLord> i recently upgraded to Intrepid, and had a question about that particular bug
[08:43] <seb128> no but maybe search on launchpad
[08:43] <Drag0nLord> searched for hours....found alot
[08:43] <RAOF> Drag0nLord: No, although my laptop won't boot on battery.  Your error's probably easy to search for.
[08:43] <Drag0nLord> lol
[08:44] <Drag0nLord> i'm on a desktop pc
[08:44] <Drag0nLord> i was going to mention, that after upgrading to Intrepid, i saw something a bit different
[08:45] <Drag0nLord> without using any workarounds, straight after upgrade, i notice that the IO-APIC is actually found in Intrepid
[08:45] <dholbach> good morning
[08:45] <RAOF> Morning dholbach.  I'm obviously home early!
[08:46] <dholbach> hi RAOF
[08:46]  * dholbach is late today :-)
[08:47] <RAOF> Heh.
[14:08] <mrooney> So let's say Intrepid has very slow wireless which often drops, and ath5k_pci uses inordinate amounts of CPU, which package might that be? Just linux?
[14:13] <Hobbsee> whatever distributes that driver, which is probably linux, yes.
[14:53] <hggdh> Hobbsee, ping -- need help with bug 267763
[14:56] <bddebian> Boo
[14:56] <jjesse> don't cry i didn't mean to scare you
[14:57] <bddebian> :)
[14:59] <Hobbsee> hggdh: as long as it isn't that nutcase who doesn't understand paragraphs...
[15:00] <hggdh> Hobbsee, well, in terms... its mesself, so one might look at it as a nutcase
[15:00] <Hobbsee> hggdh: you don't hold a candle to the bug reports i saw earlier....
[15:00] <hggdh> Hobbsee, it seems I cannot add a bug watch to Gnome...
[15:01] <hggdh> Hobbsee, which bug? now I am curious
[15:01] <Hobbsee> hggdh: looks like someone else has
[15:02] <hggdh> Hobbsee, no that was myself. I wanted to add a gnome watch, and I cannot get it to work (requires a distribution)
[15:02] <Hobbsee> hggdh: as for why it didn't work for you, i've no idea.  the upstream section tends to confuse the hell out of me, so i actively avoid it :)
[15:02] <Hobbsee> oh - i think you wanted the other option, then.
[15:03] <hggdh> which one? they changed LP, and I am lost now :-(
[15:03] <Hobbsee> i'm not sure.  i always get lost there nwo too
[15:03] <hggdh> :-)
[15:03] <Hobbsee> also affects project, i think
[15:03] <Hobbsee> hmm
[15:03] <hggdh> Saint pedro_  did it...
[15:04] <Hobbsee> you can't just dump the URL in the the bottom half, and let it figure itself out?
[15:04] <Hobbsee> Bug #267328
[15:04] <hggdh> I tried, but the blasted page errored out
[15:04] <Hobbsee> hggdh: welcome to launchpad...
[15:05] <Hobbsee> hggdh: although i've no idea why it worked for pedro after, then.
[15:05] <Hobbsee> hggdh: see ^
[15:05]  * Hobbsee has already changed the description and such.
[15:06] <hggdh> Hobbsee, saw the bug... succeeded on reading the first two lines, and then gave up
[15:06] <hggdh> Saint pedro_ , how did you add the bug watch on the bug?
[15:06] <pedro_> hggdh: to which one ?
[15:07] <pedro_> bug 267763?
[15:07] <hggdh> yes
[15:07] <pedro_> i didn't
[15:07] <pedro_> Filed here by:  	 Adam Buchbinder <-
[15:08] <hggdh> yes... just saw it...
[15:08] <hggdh> OK, no matter. How does one add a bug watch for Gnome nowadays?
[15:09] <pedro_> same way as before, I've added a few this morning didn't encounter any issues
[15:09] <hggdh> also affects distribution?
[15:09] <Ampelbein> hggdh: also affects project
[15:09] <pedro_> no, also affects project
[15:10] <pedro_> right
[15:10] <hggdh> dammit
[15:10] <seb128> hggdh: that's the same label for ages in launchpad
[15:11] <hggdh> seb128, I just woke up, I guess I am still half off :-(
[15:11] <seb128> hggdh: good morning then ;-)
[15:11] <hggdh> (meaning the upper half)
[15:12]  * hggdh *knew* the bed was the best place for today... :-(
[15:13] <hggdh> anyways, now to earn a bit of money... see you all later.
[15:20]  * pochu waves at pedro_ 
[15:20] <pedro_> hey pochu!
[15:20]  * pedro_ hugs pochu
[15:21]  * pochu hugs pedro_ back :)
[15:22] <pochu> pedro_: how are you doing?
[15:22] <pedro_> pochu: I'm great, how about you, how's the university going?
[15:23] <pochu> pedro_: just finished my exams today :) so I'm able to contribute to Ubuntu again
[15:23] <pedro_> woohoo!
[15:23] <seb128> pochu: want some updates to do? ;-)
[15:23] <pedro_> bonjour seb128!
[15:23] <pochu> seb128: why not? :)
[15:24] <seb128> hey pedro_
[15:24] <pochu> seb128: I'm trying to make a patch for pygobject right now but I can do updates too
[15:24] <seb128> pochu: what needs patching?
[15:24] <pochu> seb128: http://bugzilla.gnome.org/show_bug.cgi?id=550235
[15:25] <pochu> lool made a patch but it's not optimal
[15:25] <seb128> pochu: lool fixed that in the ubuntu package already no?
[15:26] <pochu> yeah, but in /usr/lib/pygobject/ which means things linking to it will have an RPATH
[15:26] <pochu> so upstream prefers something like /usr/lib/libpyglib-python2.X.so or something like that
[16:23] <bdmurray> Awsoonn_: Do you have something planned for Thursday?  I'd really us to take a look at the Confirmed bugs without a package and would like to run it on the 11th.
[16:24] <mrooney> bdmurray: while you are here, do you have any thoughts on what the next step is for bug 224797
[16:25] <mrooney> it seems poor from a QA standpoint, and probably not that hard to fix, either
[16:25] <bdmurray> mrooney: update the title?
[16:25] <mrooney> bdmurray: okay, to include Intrepid?
[16:25] <bdmurray> mrooney: right, and I'd also ping evand in #ubuntu-installer since he assigned it to himself
[16:26] <mrooney> he has assigned a lot of migration-assistant bugs to himself :)
[16:26] <bdmurray> mrooney: well, he did write it. ;)
[16:26]  * mrooney waves at asac_
[16:27] <mrooney> bdmurray: okay I will do that. I thought though that putting the release in the title is not the proper way. doesn't seb128 always complain about that
[16:27]  * asac_ waves back
[16:27] <mrooney> or maybe that was putting the application name in the title that I am thinking of...
[16:27] <bdmurray> mrooney: okay, then just remove the hardy bit - I'm indifferent.  It just seems misleading as it stand
[16:27] <bdmurray> s
[16:28] <mrooney> I'll add it to the title, I think I was confused between release name and app name :)
[16:28] <seb128> mrooney: putting the version is the title is proper way when a bug is specific about this version, not when you have a bug on a version and no clue about other versions or didn't try those
[16:28] <seb128> ie "hardy to intrepid nautilus upgrade bug" is a proper title
[16:29] <mrooney> seb128: okay, I guess I will put Hardy/Intrepid. it obviously doesn't apply to older releases since Gaim was not the incorrect name then
[16:29] <seb128> mrooney: if the bug happens on intrepid put no title
[16:29] <seb128> no version in the title
[16:29] <mrooney> okay
[16:39] <mrooney> okay, thanks bdmurray and seb128, I think I got it all sorted out!
[17:08] <Awsoonn_> bdmurray: Sounds like a great idea to me.
[17:12] <bdmurray> Awsoonn: okay, great I'll set that up for the 11th then
[17:18] <Konstigt> Bug 153801 isn't set to any package. I would like to change it to tvtime and mark it as confirmed but I'm unsure if that's correct. Stéphane Loeuillet is claiming on 2007-10-31 that it isn't tvtimes fault but I disagree.
[17:32] <bdmurray> ogasawara: bug 266989 seems to be a regression from Hardy to Intrepid
[17:34] <ogasawara> bdmurray: ok, I'll take a look
[17:34] <bdmurray> ogasawara: wrt fixed-2.6.27 should that only be used if it was confirmed broken in 2.6.26?
[17:35] <ogasawara> bdmurray: right
[17:35] <ogasawara> bdmurray: no sorry, I read that too fast
[17:35] <ogasawara> bdmurray: fixed-2.6.27 is for any bugs fixed with 2.6.27 regardless if broken on 2.6.26
[17:36] <bdmurray> ogasawara: okay, thanks
[18:12] <bdmurray> pedro_: Do you think bug 221759 is gnome or xorg related?
[18:16] <seb128> [ 4490.491791] Xgl[6988]: segfault at 000001a6 eip 0818db66 esp bfc5b000 error 4
[18:16] <seb128> that's an xgl bug
[18:17] <seb128> xserver-xgl which is deprecated in intrepid
[18:17] <bdmurray> You think all those people had it installed?
[18:18] <seb128> you can ask but one guy wrote that and the next one confirmed that uninstalling xgl fixed the issue
[18:30] <bdmurray> thekorn: Is there a bug refresh function in python-launchpad-bugs?
[18:30] <thekorn> bdmurray, no, unfortunatly not,
[18:31] <thekorn> there is a open bug about this,
[18:31] <thekorn> but I never found a smart way to fix this
[18:33] <thekorn> bdmurray, it's bug 138837
[18:33] <thekorn> at least it is related
[18:39] <bdmurray> thekorn: hmm, okay
[18:39] <bdmurray> thekorn: what is the status of the nominations branch?
[18:43] <thekorn> bdmurray, no big progress in the last few days,
[18:43] <thekorn> so committing nominations requests and accepting them does not work yet
[18:44] <thekorn> one problem where I got stuck was that Nominations requested by a driver of a project are auto-accepted
[18:45] <thekorn> and I have no clue how to reflect this scheme
[18:48] <bdmurray> Personally, I'm less concerned with requesting than accepting.
[18:51] <thekorn> ok, I will have a look at it again in a bit
[18:54] <Ampelbein> hmm. what is the right package for bugs in xkb? like bug #224649 ?
[18:57] <Ampelbein> is it just xorg? or xserver-xorg-input-keyboard?
[19:04] <ogra> Ampelbein, well, you answered your own question *with* your first question :)
[19:04]  * ogra would suggest kbd 
[19:05] <ogra> oh, you said xkb ... i read kbd :)
[19:06] <thekorn> bdmurray, ok, just read the code again, I think I have a good idea how to support nominations, I will do some coding after a break
[21:14] <chrisccoulson> are we using launchpad to track issues with the Intrepid NewHuman theme?
[21:14] <chrisccoulson> i've just seen a new report describing a problem with the theme
[21:15] <chrisccoulson> but i've also seen this comment suggesting that issues with the theme should be discussed on the wiki page: https://bugs.edge.launchpad.net/ubuntu/+source/human-theme/+bug/243957/comments/12
[21:17] <seb128> chrisccoulson: using launchpad is always a good idea
[21:18] <seb128> chrisccoulson: you might want to note the issue on the wiki too if some team uses that too but milestoned bugs are what are used to track issue in ubuntu
[21:18] <chrisccoulson> thanks seb128. i was looking specifically at bug 267883, which is actually a known problem according to this page: https://wiki.ubuntu.com/Artwork/NewHumanTesting
[21:19] <seb128> chrisccoulson: could be, still better to have a milestoned bug on launchpad for tracking
[21:19] <seb128> dunno about this specific issue but I'm not working on art things
[21:19] <chrisccoulson> no problem! thanks
[21:49] <yusuf_> hi, have only 1 month experience with ubuntu, would love to help, where should I start?
[21:49] <crimsun> yusuf_: http://wiki.ubuntu.com/HelpingWithBugs is a good place to start reading.
[21:59] <jdstrand> hi! I'm trying to get the url right for listing all In Progress bugs for a particular team or person
[21:59] <jdstrand> I tried: https://bugs.launchpad.net/~ubuntu-security/+bugs-text?orderby=status&field.status%3Alist=INPROGRESS
[21:59] <jdstrand> but that doesn't seem to work. this does though: https://bugs.launchpad.net/ubuntu/+bugs-text?orderby=status&field.status%3Alist=INPROGRESS
[22:00] <jdstrand> I'm not a p-l-b guru yet, so not sure where to find info on how to do that...
[22:01] <bdmurray> jdstrand: there are no text listings for teams
[22:01] <jdstrand> that's a bummer
[22:01] <jdstrand> bdmurray: is there another way to accomplish the same type of thing?
[22:01] <bdmurray> jdstrand: use the html listing?
[22:01] <jdstrand> you mean screen-scrape?
[22:02] <jdstrand> (I was trying to avoid that)
[22:02] <bdmurray> I guess I'm confused are you using py-lp-b or not?
[22:02] <yusuf_> I have have had a look at the url provided but i am still lost, could u give me an easy task to start with
[22:02] <jdstrand> bdmurray: I am before using p-l-b yet. I looked in /usr/share/doc/p-l-b/examples and saw the bugs-text example
[22:03] <jdstrand> bdmurray: so thought I could adapt it (ta-bug.py specifically)
[22:03] <jdstrand> tag-bug.py
[22:03] <bdmurray> jdstrand: if you are using py-lp-b - ConnectBugList("html") should do it
[22:04] <jdstrand> bdmurray: oh right. now I know what you mean. is the api for p-l-b documented conveniently?
[22:05] <jdstrand> bdmurray: I always struggle to come up with the right invocation, etc
[22:05] <bdmurray> https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/BugList
[22:05] <bdmurray> and https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Bug
[22:05] <jdstrand> bdmurray: oh those are excellent. thanks!
[22:06] <bdmurray> jdstrand: no problem
[22:30] <dvhart> I'm trying submit a proper bug report against evolution, but when it crashes, apport doesnt start... how do I get apport to pay attention?
[22:31] <dupondje> apport-clu
[22:31] <dupondje> apport-cli
[22:31] <dupondje> :)
[22:31] <dvhart> I've found the command... but there is nothing in/var/crash
[22:33] <dvhart> dupondje, that documentation on the web says it ought to start automatically after an application crash?
[22:34] <dupondje> it SHOULD :)
[22:34] <Ampelbein> dvhart: try running with G_DEBUG=fatal_criticals evolution
[22:35] <dvhart> Ampelbein, still nothing
[22:35] <dvhart> and /var/crash is empty
[22:35] <dvhart> I ran once in gdb and got a bt
[22:35] <dvhart> I've found the same bug in launchpad, but it was closed because the submitter didn't provide all the apport details...
[22:36] <dvhart> so I'm reluncant to proceed without it
[22:36] <bdmurray> dvhart: wheich release are you on?
[22:36] <dvhart> Ubuntu 8.04.1
[22:36] <bdmurray> dvhart: apport is disabled since that is a stable release - it is only turned on by default in development releases
[22:37] <dvhart> hah
[22:37]  * dvhart wouldn't call hardy stable.... but I digress, I know what you mean :-)
[22:37] <dvhart> is it possibly for me to turn it on?
[22:37] <bdmurray> dvhart: you can find instructions regarding enabling apport at https://wiki.ubuntu.com/Testing/EnableProposed
[22:37] <bdmurray> Disregard the whole proposed bit
[22:38] <dvhart> ah ok
[22:39] <dvhart> was wondering what that had to do with it :-)
[22:40] <bdmurray> yeah, the only important bit is enabling apport
[22:40] <dvhart> shall I still run with fatal_criticals?
[22:40] <dvhart> or try without options first?
[22:40] <bdmurray> try w/o first
[22:41] <dvhart> nice thanks!
[22:42] <dvhart> heh, ok and I see my bug is now reported twice by others
[22:43] <dvhart> the context looked different when I read them before
[22:43] <dvhart> but the text summary apport used is identical
[22:44] <dvhart> thanks for the help folkds
[22:44]  * dvhart disables apport
[22:45] <Ampelbein> dvhart: if the context looks too different, file the bug anyway. it can still be marked a duplicate later after reviewing the stacktraces.
[22:47] <dvhart> ack
[22:54] <dvhart> done, thanks for the assistance
[23:12] <wgrant> bdmurray: Warning: that "thomas delbeke" that you replied to on launchpad-users is the one who filed a bug with a 2000 word paragraph yesterday asserting that it wasn't a duplicate of another when it clearly was, and that it was somehow a security issue because he typed his sudo password somewhere where it wasn't hidden. I'm not sure you've much hope.
[23:13] <bdmurray> wgrant: hmmm, thanks for the info
[23:14] <wgrant> It was an impressive wall of text.
[23:14] <bdmurray> I can only imagine
[23:52] <owh> I'm looking at bug #113919 which applies to Hardy - and earlier. The suggested patch to fix is now in Intrepid. How do I request a backport so that Hardy users can benefit?
[23:53] <owh> Or do I just create a new backport request and ignore that this bug exists?