[00:27] <hggdh> question: current evolution-rss on Intrepid is 0.0.8. ./debian/control states a conflict for evolution >= 2.23.0.; currently installed evo is 2.23.91; *still* apt-get install evolution-rss installs. So. What package should I open a bug against?
[00:28] <nellery> hggdh, if it's in the evolution-rss control file, then I believe you file it against that
[00:30] <hggdh> nellery, I do not think so, since this is (at least to me) a failed check on depends. I would go to apt or dpkg, but I am unsure
[00:30] <hggdh> wait
[00:30] <hggdh> the source I am looking at does *not* match the binary package!
[00:30] <nellery> ah, I misunderstood the question
[00:31] <hggdh> the plot thickens, and takes a different route...
[00:33] <hggdh> new (revisited) question: how do we ask for a specific package version to be taken out of the binary repositories?
[00:37] <hggdh> and how does a package that has not benn built for Intrepid end up in Intrepid's repositories?
[00:44] <greg-g> hggdh: probably best to ask in #ubuntu-devel
[00:48] <niadh> Should I mark this bug as incomplete? : https://bugs.launchpad.net/ubuntu/+bug/215326
[00:51] <Hobbsee> hggdh: evolution-rss does'nt have that conflict, with it's binary control file.
[00:52] <Hobbsee> hggdh: which version do you want taken out?
[00:53] <nellery> niadh, bugs should be marked incomplete if the reporter has been asked a question
[00:53] <nellery> see https://wiki.ubuntu.com/Bugs/Status
[00:53] <niadh> Ah okies, what would you suggest I do with it?
[00:54] <niadh> Wait, I DID ask him a question
[00:54] <Hobbsee> hggdh: oh, and the reason the source package is later than the binary packages:  the binaries for that source package didn't build on all arches.
[00:54] <nellery> niadh: in that case, it should be marked as incomplete
[00:55] <Hobbsee> so it's replaced the ones that did build, and the source, but not on the arches it didn't.
[00:55] <niadh> nellery: I'm new to the bug tracking stuff, but I'm trying to do my bit.
[00:55] <sonchen> niadh, is it a bug or a feature request? I can't tell, but I may be thick.
[00:56] <sonchen> (me also very new to bug-tracking)
[00:56] <niadh> Looks like a feature demand really, but I asked him for a use case or argument as to why it should be changed.
[00:57] <sonchen> that's what i got from it tbh
[00:58] <niadh> marked as incomplete, if he gives something reasonable I'll mark it as something else.
[00:58] <sonchen> I reckon it's best to leave it for a day or too before doing anything else
[00:58] <sonchen> that last post was mangled
[00:58] <sonchen> yea i think yer probably right
[00:59] <sonchen> (by last post being I meant mine)
[01:00] <niadh> heh
[01:06] <murdok> Is this bug to be closed?
[01:06] <murdok> https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/26607
[01:09] <nellery> murdok: no, that was an automated report
[01:09] <nellery> best to just leave it as is
[01:09] <murdok> okay
[01:09] <murdok> nellery, why does it say that the fix was released for debian
[01:09] <murdok> ?
[01:10] <murdok> when the debian team couldn't reproduce it
[01:10] <murdok> as they say. and nobody has reported it neither
[01:10] <nellery> murdok: that's a bug tracker, the actual bug is at
[01:11] <nellery> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342141
[01:13] <murdok> Okay I'm wrong, some few people has could reproduce it
[01:13] <murdok> anyway I can't find where it says that the bug is fixed.
[01:14] <murdok> has it been automatically updated too?
[01:14] <niadh> Should I delete this one: https://bugs.launchpad.net/ubuntu/+bug/223662
[01:14] <LimCore> ubuntu really is not very good for laptops
[01:15] <LimCore> every time I see laptop (or also normal PC) with ubutnu - people never know how to setup sound input
[01:15] <Hobbsee> plug it in?
[01:15] <maco> heh
[01:15] <niadh> LimCore: So what if it isn't good, it's why we have bug reports ;)
[01:16] <LimCore> Hobbsee: well, even after applying this very clever solution, it doesnt work, only output
[01:16] <maco> i have to have Front unmuted for my mic to work.  i also have to put it to 0 to keep from getting feedback.
[01:16] <LimCore> niadh: its more of systemic problem, not a bug in one application
[01:16] <LimCore> maco: yeah, each time you have to play with all the strange and confusind settings in mixer untill you get it right
[01:17] <LimCore> on one box I have to set: mic=0 boost=50% digital=80% and 2 other thingies
[01:17] <LimCore> this is NOT user friendly at al
[01:18] <LimCore> otherwise it either records silence, or totally distorted noise
[01:18] <Hobbsee> murdok: what version could they reproduce it under?  The debian bug got closed as it was only found on old versions.
[01:21] <murdok> Hobbsee, sorry, I read it quickly. One person has said that the bug was also affecting him.
[01:21] <murdok> in an old version
[01:21] <murdok> you are right
[01:21] <Hobbsee> murdok: in debian, yeah.
[01:21] <Hobbsee> murdok: i'd guess that's safe to close - no one else has written anything on it in 3 years, saying they have the same issue.
[01:22] <Elbrus> LimCore: I have sound input on my laptop
[01:22] <murdok> but launchpad says that the fix has been released
[01:22] <murdok> that's what I can't understand
[01:23] <murdok> hehe
[01:23] <Hobbsee> well, presumably upstream did fix the issue, hence it's no longer happening
[01:23] <LimCore> ok I got sound now.  this was really fun. well, perhaps not for all users
[01:23] <LimCore> 1) you have to find HIDDEN (!?!?!??!) settings in the mixer (why they are not visible by default)
[01:24] <murdok> Okay I got it now. I'll mark it as invalid.
[01:24] <murdok> :-)
[01:24] <LimCore> 2) capture=30-50% (if over 50% then it records clicking sound instead..) record=front mic  digital=100%    I think this shound be easier, 90% of NEW users will just go "damn, this laptop ALSO doesnt work with linux+mic"
[01:24] <Hobbsee> murdok: upstream may have never known about the debian bug, nor have access, etc.
[01:26] <LimCore> only I am thinking that this should be done easier?
[01:26] <murdok> Hobbsee, hmm so invalid or fix released?
[01:26] <niadh> What package might this bug be attached to? https://bugs.launchpad.net/ubuntu/+bug/227886
[01:26] <Hobbsee> murdok: fix released.
[01:27] <greg-g> LimCore: possibly, I haven't dealt with it, would you be so kind as to report a bug describing the issue and all steps you took to resolve it?  At the same time trying to keep separate issues separate (the fact that a setting is hard to find is separate from sound input not working out of the box, for instance)
[01:27] <maco> LimCore: they're there, you just get to check off which ones you want to show. about 20 or so are available in gnome's mixer, you just don't have them selected. they probably show in alsamixer.
[01:27] <Hobbsee> niadh: i'd ask what type of cd drives those guys have.
[01:27] <maco> LimCore: in that case, i'd blame gnome for hiding things :P
[01:28] <murdok> Hobbsee, done, thanks
[01:28] <Hobbsee> niadh: may well be a drive problem.
[01:28] <Hobbsee> er, driver problem
[01:28] <Hobbsee> murdok: you're welcome
[01:29] <niadh> I'm not quite sure what package to attach it to though.
[01:29] <LimCore> ok I will look into it.  What to set as package/project  or where report problems that are system wide? overall in ubuntu design
[01:29] <Hobbsee> LimCore: against 'ubuntu', and someone will reroute it
[01:29] <Hobbsee> niadh: i don't think you'd be able to, yet.
[01:32] <maco> LimCore: you can tag it needs-reassignment
[01:33] <LimCore> k
[01:34]  * Hobbsee grumbles.
[01:34] <Hobbsee> three way merge by hand:  DO NOT WANT!
[01:35] <maco> Hobbsee: huh?
[01:35] <Hobbsee> maco: i'm looking at fixing a few dput bugs.
[01:36] <Hobbsee> maco: which appears that it will involve mass cherrypicking, or doing a 3 way merge, by hand.
[01:36] <Hobbsee> both being something I don't really wnat to do :)
[01:36] <maco> oh ok
[01:37] <RAOF> Hobbsee: Have you tried _meld_?  I quite like it for 3-way merges.
[01:37] <Hobbsee> RAOF: not yet.  I might try that.
[01:40] <murdok> What should I do with this bug? https://bugs.launchpad.net/ubuntu/+source/scim-chewing/+bug/57081
[01:41] <murdok> Is Dapper still maintained?
[01:42] <crimsun> LimCore: that's not an Ubuntu problem.  Blame the manufacturer of audio codecs.
[01:42] <LimCore> crimsun: lack of user friendly guide/wizard.
[01:43] <crimsun> Ubuntu could, I suppose, attempt to expose "more" mixer elements by default, but then someone will grumble, "oh god, I can't figure which of these sixty elements to change!"
[01:43] <maco> bugs in packages from hardy-backports should be reported against...what?
[01:43] <hggdh> Hobbsee, it would be evolution-rss 0.0.8
[01:43] <crimsun> LimCore: that's because there is no easy way to create a wizard to do so.
[01:43] <Hobbsee> hggdh: right.  Took a patch elsewhere, got it to build.
[01:43] <maco> crimsun: sounds like me using KDE...
[01:43] <Hobbsee> hggdh: it should be fixed now.
[01:44] <hggdh> Hobbsee, ok, then we just wait a bit for it to be published
[01:44] <crimsun> LimCore: if you'd like to maintain the quirk list for ALSA codecs, go ahead.  You'll discover just why it's an intractable problem.  And it's just going to worsen.
[01:44] <LimCore> crimsun: recording application + visual "osciloscope" + mixer (all options!!!) + hand book + some script to automatically test typical solutions + dmesg
[01:44] <hggdh> Hobbsee, thanks
[01:44] <Hobbsee> hggdh: things only get taken out if they're replaced by other bits, or done explicitly.
[01:45] <LimCore> crimsun: such ultimate sound wizard would be a big step ahead; Then, build list (even automatically - inet) list of devices -> neede settings
[01:45] <Hobbsee> LimCore: code it, then.
[01:45] <crimsun> LimCore: you misunderstand the scope of the problem.
[01:45] <hggdh> Hobbsee, I understand. I was just surprised for a more up-to-date source to be available -- after all it was FTBFS, and should not be there
[01:45] <crimsun> LimCore: it's not the feasibility of creating a wizard.  It's the maintenance nightmare.
[01:45] <Hobbsee> hggdh: it didn't FTBFS on all arches - it passed on hppa and ia64
[01:45] <LimCore> crimsun: it will AID it, not solve all possible quirks and cure cancer
[01:46] <hggdh> Hobbsee, ah, ok. sorry
[01:46] <Hobbsee> hggdh: no problem - rmadison and such don't show it.
[01:46] <crimsun> LimCore: you still misunderstand the scope.  It's not about aiding; it's about automating.  As you even said above, aiding doesn't cut it.
[01:46] <LimCore> its shure better then knowing that I have to run several applicaitions and then play with mixers to get it fixed.
[01:46] <hggdh> yup.
[01:46] <Hobbsee> hggdh: you'd probably find https://edge.launchpad.net/ubuntu/intrepid/+builds?build_text= helpful - you can search by package name, status, etc.
[01:47] <LimCore> crimsun: this application will automatically solve IF possible,  and if not, it will give tools to debug the problem.  In both cases, this is better then current "no sound... no information.. just NOTHING"
[01:47] <Hobbsee> LimCore: by all means, write one then.
[01:47] <Hobbsee> LimCore: but it's likely to be consistently out of date.
[01:47] <maco> LimCore: complaining doesn't get very far. and hobbsee's right about getting out of date quickly
[01:47] <LimCore> only the automatic solver will need to be updated
[01:48] <hggdh> Hobbsee, thanks again. How many IOUs do I have now with you? I will never be able to repay all ;-)
[01:48] <Hobbsee> hggdh: heh :)
[01:48] <Hobbsee> hggdh: it's good that you want to learn more :)
[01:48] <LimCore> ok but this is like 1 month prepartions + 2 months coding for 1-2 person
[01:48] <maco> hahaha
[01:48] <LimCore> are there some students or something to help
[01:49] <crimsun> LimCore: why does there need to be a solver?  Why can't the correct information be provided to a higher layer by the hardware?  That's precisely what is happening, BTW, with our udev work and the alsa-info.sh db.
[01:49] <LimCore> crimsun: usually all is working, only the mixer is badly configured
[01:49] <crimsun> LimCore: no, it's far worse.
[01:50] <maco> Hobbsee: where do bugs in backported packages get reported?  against the package or against something-backports?
[01:50] <Hobbsee> maco: erm, i *think* it's something-backports.  check with jdong
[01:50] <LimCore> crimsun: on most boxes I seen, evnetually, after playing wtih mixer, it was working
[01:50] <maco> jdong: ping
[01:51] <LimCore> so how this works with open source and ubuntu?
[01:51] <maco> jdong: where do bugs on backported packages go?
[01:51] <LimCore> idea for application, planning etc, and now need people to actually implement it. Any good ubutnu idea on this?
[01:52] <maco> LimCore: can't implement anything with a half-thought-out idea and no plan
[01:52] <LimCore> maco: yeap, thats what I written is needed
[01:53] <maco> LimCore: "and now need people to actually implement it" ...no, now you need a better idea, fully fleshed-out, with a complete understanding of the depth and breadth of the issue
[01:53] <Hobbsee> and actually maintain it.
[01:53] <maco> right, that too
[01:53] <maco> unmaintainable code is bad
[01:53] <maco> works for a day at most, then a bug is reported...and then well, unmaintainable, yay
[01:54] <crimsun> LimCore: pay attention to the fact that it's being addressed in a difference manner.
[01:54] <maco> crimsun: the different manner being "fixing the drivers"?
[01:54] <crimsun> I stated that upstream is using udev hints and a large user-generated troubleshooting database.
[01:54] <LimCore> crimsun: alsa driver automatically sets mixer volumes to reasonable levels or something?
[01:55] <crimsun> that's part of it.
[01:57] <maco> jdong: nevermind. crimsun told me.
[02:07] <Hobbsee> hm, well, that was less painful than expected.
[03:40] <LimCore> exim4 crashed in postconfig... known problem?
[03:42] <LimCore> just once though
[03:47] <Hobbsee> if you wanted to know if it was a known problem, why didn't you check hte bugtracker?
[07:05] <dholbach> good morning
[07:18] <Das_Auge> Hi, i am new here and would like to help.
[07:18] <Das_Auge> I'm not a programmer.
[07:19] <RAOF> !contribute
[07:19] <RAOF> Gah, lack of bot.
[07:20] <dholbach> there's https://wiki.ubuntu.com/HelpingWithBugs if you'd like to get involved in triaging bugs
[07:20] <RAOF> Das_Auge: https://wiki.ubuntu.com/ContributeToUbuntu is a good start page for overall contributions.
[07:35] <Das_Auge> thanks, dholbach and RAOF
[07:37] <dholbach> Das_Auge: if you have any other questions, be sure to ask in here :)
[07:41] <Das_Auge> Here is my first question: What package is afflicted, if my screen resolution is not detected correctly?
[07:42] <Das_Auge> xorg?
[07:43] <RAOF> Depends.  It's most likely to be in your driver package.
[07:44] <dholbach> https://help.ubuntu.com/community/DebuggingXAutoconfiguration might help too
[07:44] <RAOF> https://wiki.ubuntu.com/X/Reporting will possibly help, particularly the "troubleshooting" link.
[07:44] <dholbach> RAOF: do you think that https://wiki.ubuntu.com/DebuggingXorg and https://wiki.ubuntu.com/X/Reporting could be merged somehow?
[07:46] <RAOF> Hm.  Perhaps not merged, but X/Reporting should probably link to DebuggingXorg.
[07:46] <dholbach> *nod*
[07:46] <dholbach> also the DebuggingXAutoconfiguration link :)
[07:46] <RAOF> Oh, it does.
[07:47] <dholbach> ah ok
[07:47] <RAOF> Interesting factlet: DebuggingXorg is word-for-word duplicated at X/Backtracing it seems.
[07:48] <dholbach> #REDIRECT (or whatever it is called in the NewMoinWorldOrdeR) is your friend :-)
[07:48] <dholbach> Das_Auge: the fine people in #ubuntu-x might be able to help too
[08:16] <ara> Hello all! We remember you that today is the first Ubuntu Testing Day!
[08:16] <ara>  If you want to help with Ubuntu and don't know where to start this is the perfect occasion
[08:16] <ara> we will be testing Intrepid Alpha 6 Live sessions, so you won't need to install anything on your systems
[08:16] <ara> Here you will find the links to the ISO cd images to test: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20080922#Which%20release%20we%20will%20be%20testing?
[08:17] <ara> more information about the testing day can be found at https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20080922
[08:17] <ara> we will be at #ubuntu-testing all day to answer the questions you might have
[10:14] <dholbach> thekorn: good morning - is http://paste.ubuntu.com/49228 known already?
[10:26] <thekorn> dholbach: hi, no, never saw this before, let me try to reproduce this
[10:27] <dholbach> thekorn: the same with trunk and what's in bughelper-dev ppa
[10:27] <thekorn> dholbach: works for me, trunk an intrepid package, strange
[10:27] <dholbach> hum (hardy here)
[10:27] <dholbach> let me try again
[10:29] <dholbach> thekorn: ahh, works with trunk, not with ppa
[10:29] <dholbach> thekorn: nevermind then :)
[10:30] <thekorn> ok, will update the package in the PPA then
[10:30] <dholbach> rock :)
[10:31] <dholbach> thekorn: how's launchpadlib looking?
[10:31] <thekorn> dholbach: I think lp's API team is making good progress,
[10:32] <thekorn> but unfortunatly especially the bug bits are still missing important functionallity like searching for bugs
[10:32] <dholbach> oh, I see
[10:33] <dholbach> is anybody working on a launchpadlib connector? :)
[10:33] <thekorn> but with caching enabled launchpadlib is many times faster than py-lp-bugs
[10:33] <dholbach> or do you think there'll be a transition to launchpadlib in the long run?
[10:34] <thekorn> the launchpadlib connector I started some time ago is up-to-date regarding bug functionality
[10:34] <dholbach> woah nice
[10:34] <dholbach> more power to thekorn!
[10:34] <dholbach> :-)
[10:34] <thekorn> dholbach: lp:~thekorn/python-launchpad-bugs/launchpadlib.connector
[10:35] <thekorn> well I hope lplib can replace py-lp-bugs at one time,
[10:37] <dholbach> you're really unstoppable
[10:39] <thekorn> maybe ;)
[10:41] <thekorn> dholbach: btw, development around lplib is currently kind of blocked because of bug 239734 ;)
[10:43] <dholbach> thekorn: alright, \sh will surely do the upload soon
[10:44] <thekorn> yes, that's his plan
[12:49] <sroecker> could someone please set bug 250425 to critcal?
[15:06] <bddebian> Boo
[15:31] <Hew> asac: The abrowser command seems to be broken in 3.0.2+build6+nobinonly-0ubuntu1~asac1 which I got from your ppa. I don't think I should report this under abrowser (Ubuntu) since I believe it started happening with your build. Are you aware of this problem?
[15:33]  * Hew pings asac, just in case he disconnected earlier
[15:53] <asac> Hew: what happens?
[15:53] <Hew> exec: 118: /usr/lib/firefox-3.0.2/abrowser: not found
[15:55] <asac> Hew: ok. i think its a glitch that that link is in the firefox-3.0 package. please ensure that you have installed abrowser and abrowser-3.0-branding package
[15:55] <asac> Hew: in any case: report it and let me know about the LP id
[15:55] <Hew> asac: confirmed
[15:55] <asac> (against firefox-3.0)
[15:55] <Hew> asac: Will do
[15:56] <asac> Hew: so it gets cured when installing abrowser and abrowser-3.0-branding?
[15:56] <asac> Hew: post your findings to the bug
[15:56] <Hew> asac: I just wasn't sure if I should report it against Ubuntu since it's not a package from the Ubuntu repos
[15:56] <Hew> asac: No, I have those packages installed and the command doesn't work
[15:56] <Hew> asac: 'firefox' starts abrowser fine though
[15:57] <Hew> I think it's to do with symlinks
[15:57] <asac> Hew: yeah
[15:57] <nullack> asac : Hi :) Im a bit concerned about gnome's schedule with the final 2.24 release being close and some NM 0.7 bugs not seeming to be getting upstream fixes
[15:57] <asac> nullack: which bugs?
[15:57] <nullack> asac : Ill look up one sec pls
[15:58] <seb128> network-manager is not following the GNOME schedule
[15:58] <asac> most likely they follow fedora schedule ;)
[15:59] <nullack> Bug #258743
[15:59] <nullack> Bug #256054
[15:59] <nullack> seb128 : Hi :) Good to know theres more time
[16:00] <seb128> and intrepid will get GNOME 2.24.1 anyway
[16:00] <nullack> seb128 : saw you posting intrepid updates on sunday :) your a machine my friend !
[16:00] <seb128> I try to not working the weekend but a new stable GNOME version is a good reason for a small exception ;-)
[16:01] <asac> nullack: 256054 is something we have to fix here - though the ifupdown plugin landed upstream, i cant convince enough people to drop ifupdown ;) ... so we need a special system-config plugin that blacklists devices in ENI
[16:01] <asac> nullack: can you code C?
[16:01] <asac> ;)
[16:01] <nullack> seb128 : is libenchat  motu package? I saw the gramps people have got a workaround
[16:01] <seb128> no it's not
[16:01] <nullack> asac a little but Im not good, Im much better at consulting and testing
[16:01] <seb128> things which are in the default installation are not in universe
[16:02] <asac> nullack: the MTU fix is probably simple.
[16:02] <asac> like dan suggests in the bug
[16:02] <nullack> asac Ill look at it, I fixed some problems in a motu package with my first debdiffdoing a patch so Ill try on nm0.7
[16:03] <nullack> seb128 whos the libenchant maintaner for ubuntu?
[16:04] <seb128> nobody
[16:04] <nullack> want me to report it upstream then?
[16:04] <seb128> too many packages not enough people, nobody is actively working on this one
[16:04] <seb128> that would be nice indeed
[16:04] <nullack> I will do that and bugwatch it
[16:05] <seb128> cool
[16:06] <asac> nullack: first thing you could try is to upgrade to latest upstream snapshot
[16:06] <asac> nullack: with some luck its just one command
[16:06] <asac> nullack: if you tell me that the MTU is still not fixed i can probably do the patch
[16:06] <nullack> ppa? Or do I grab their svn head and compile?
[16:07] <asac> nullack: no ...  for a quick test you get the ubuntu.0.7 branch from https://code.launchpad.net/network-manager-applet
[16:07] <asac> then do a bzr merge lp:network-manager-applet
[16:08] <nullack> asac thanks
[16:08] <asac> and then bzr bd --merge --native --builder='debuild -b'
[16:08] <asac> or
[16:08] <asac> and then bzr bd --merge --native --builder='dpkg-buildpackage -rfakeroot -b'
[16:08] <asac> nullack: of course only if the merge worked without a conflict
[16:08] <asac> ;)
[16:09] <nullack> Ofcourse, debian/ubuntu patches are ontop of their trunk
[16:09] <asac> shouldnt be that many patches
[16:10] <asac> applet should merge well
[16:10] <asac> not sure if NM changed dbus api and some features are broken ... but you will surely see
[16:11] <nullack> Its 1;10am here now, I can test by tonight and provide feedback
[16:11] <nullack> Night all
[16:13] <asac> nullack: for the log ... the above bzr bd commands are _without_ --merge
[16:13] <asac> ;)
[16:13] <nullack> Ill resave the transc ript thx for letting me know
[16:16] <dholbach> thekorn: another thing I just noticed in bug activity logs: sometimes some elements seem to be missing from .activity: http://paste.ubuntu.com/49325
[16:16] <dholbach> (note the 'added subscrriber Ubuntu Sponsors for universe' in the first bug report, but not the second one)
[16:17] <Hew> asac: bug 273170
[16:19] <dholbach> thekorn: should I file a bug?
[16:19] <thekorn> dholbach, for me it looks like a bug in launchpad, the subscription of -sponsors is not on https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/271080/+activity
[16:20] <dholbach> errr
[16:20] <dholbach> hang on
[16:21] <dholbach> thekorn: no... it's definitely a bug in dholbach - I used the wrong bug number
[16:21] <dholbach> excusez-moi :)
[16:21] <thekorn> heheh
[16:30] <asac> Hew: thanks. triaged
[16:31] <Hew> asac: Cool, thank you :-)
[16:55] <bdmurray> mvo: did you the maintainer script failure e-mail?
[16:57] <mvo> hey bdmurray!
[16:57] <mvo> bdmurray: yes, but have not done anything about it yet
[17:19] <maco> anyone ever see launchpad saying ____ package not published in ubuntu?
[17:30] <maco> i'm trying to mark bug 272300 for madwifi since that's the driver in use, but it says "madwifi package not published in Ubuntu"...even though Launchpad shows it in the search
[17:36] <bdmurray> maco: madwifi seems to be a driver in l-r-m for 2.6.24 and may have switched to something else in 2.6.27
[17:37] <ogra> its still in l-r-m
[17:37] <ogra> though its suposed to be replaced by ath5k
[17:37] <ogra> which is the free driver but doesnt work on all devices yet
[17:43] <maco> bdmurray: oh ok. why is there still a madwifi source package?  i'm confused.
[17:46] <maco> er, ok i'm not sure what package it goes with in intrepid then. because there's no l-r-m-2.6.27 with the way things were rearranged.
[17:47] <ogra> i'm just instaling l-r-m here
[17:48] <ogra> on intrepid
[17:48] <ogra> there is definately one
[17:48] <maco> is it named something else?
[17:48] <maco> wait, is it *just* l-r-m with no kernel version number at the end?
[17:49] <ogra> linux-restricted-modules 2.6.27-4.5
[17:49] <ogra> is the latest
[17:49] <bdmurray> the package in lp is just l-r-m now
[17:50] <bdmurray> similar to how there is just linux instead of linux-2.6.27
[17:50] <ogra> the binaries are linux-restricted-modules-2.6.27-4-generic, linux-restricted-modules-2.6.27-4-server and linux-restricted-modules-common
[17:50] <maco> i see
[17:50] <maco> thanks guys
[18:00] <maco> are bugs regarding gstreamer's video playback's interaction with compositing considered the driver's fault, compiz's fault, or gstreamer's fault?
[18:00] <bdmurray> maco: I think it is the video driver but it'd be best to check in #ubuntu-x
[18:00] <maco> ok
[18:03] <joumetal> Is cve-2008-0123 right for bug 272221?
[18:15] <maco> can someone mark bug 273112 wishlist, please?
[18:20] <pwnguin> arg. apport feels like punishment
[18:21] <pwnguin> "a program has crashed. please spend the next five minutes in cpu crunch
[18:22] <maco> haha
[18:23] <maco> apport annoys me. "something crashed! please enter your password to find out what.  oh and look, it's not even an ubuntu-packaged app, so it can't go to launchpad anyway" -_-
[18:24] <maco> or rather, "please enter your password to make this annoying bubble go away" since generally it's fairly obvious exactly what crashed
[18:24] <maco> can there be an "i don't care" button?
[18:24] <greg-g> the don't report crashes from this application again button
[18:25] <maco> oo that exists? ok. i think i disabled apport to make it go away.
[18:26] <greg-g> or that
[18:26] <maco> is that button before or after it asks if you want to see the crash report and asks for the password?
[18:26] <greg-g> and apport isn't enabled in the released verion of Ubuntu, afaik
[18:26] <greg-g> I don't ever remember entering a password for apport
[18:26] <greg-g> is this intrepid?
[18:26]  * greg-g isn't using intrepid yet
[18:27] <maco> because my thinking is first say what crashed, have "show report" "ignore" buttons and if they hit "show report" *then* ask for password. right now, it's password first, questions later
[18:27] <maco> hardy
[18:27] <greg-g> hmmm
[18:27] <maco> i haven't tried intrepid yet. going through bug reports is scaring me off from it :P
[18:27] <greg-g> heh
[18:29] <maco> there's also the part where intrepid won't be adding any new hardware support for me.  2 pieces of hardware with out-of-tree drivers, but they'll have to wait for jaunty
[18:29] <maco> hardy works well for me
[19:53] <jcastro> pedro_: we're doing an OOo hugday this week right?
[19:55] <bdmurray> jcastro: we've been talking about update-manager since more people are upgrading with Alpha 6 out
[19:55] <jcastro> ok
[19:55] <bdmurray> Maybe having 2 a week is a good idea with the release imminent
[19:56] <jcastro> virt-manager is sucking, 74 open bugs, zero reported upstream.
[19:56] <jcastro> so that could be a target if you guys still need them. :D
[19:56] <bdmurray> I don't think we are out of things to work on. ;)
[19:56] <chrisccoulson> ping pedro_
[19:56] <jcastro> heh
[19:56] <pedro_> mm what about september 29?
[19:57] <pedro_> is there anything planned for that day?
[19:57] <pedro_> mmm september 30 sorry
[19:57] <bdmurray> no, that would work.  tomorrow is testing day right?
[19:57] <pedro_> we can have an OOo on 30 and a Firefox one the 02
[19:57] <pedro_> chrisccoulson: hello
[19:58] <bdmurray> sounds good to me
[19:58] <maco> bdmurray: today's testing day, i thought
[19:58] <pedro_> sounds like a plan then
[19:58] <chrisccoulson> hi pedro_, i just noticed you closed bug 272510, asking the reporter to submit a crash report
[19:58] <chrisccoulson> i don't think the reporter is going to be successful though.
[19:58] <bdmurray> doh
[19:58] <maco> bdmurray: calendar too full?
[19:58] <maco> ^_^
[19:58] <chrisccoulson> it doesn't appear that gnome-panel is crashing, but he says it hangs and he has to kill it manually
[19:58] <pedro_> chrisccoulson: well let's see, we need a backtrace anyways
[19:59] <bdmurray> maco: seems so
[19:59] <pedro_> chrisccoulson: ok so if it hangs he can also get a backtrace of that
[19:59] <pedro_> chrisccoulson: not with apport but gdb can help there
[19:59] <chrisccoulson> no problem. i'll point him to the wiki page for obtaining a backtrace
[20:00] <pedro_> chrisccoulson: rock on
[20:01] <bdmurray> pedro_: any ideas about - http://pastebin.osuosl.org/22123
[20:02] <bdmurray> I see that in /var/log/auth.log every time I log in
[20:04] <pedro_> bdmurray: looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=550756
[20:05]  * pedro_ screams at macbook center
[20:05] <bdmurray> I think I saw that one but I've no ldap or nfs
[20:05] <pedro_> my laptop is there for about 2 weeks and they still don't have news about it "sorry we don't know what's the issue with it" dammit!"·
[20:07] <bdmurray> that's no good
[20:09] <bdmurray> pedro_: I saw a Mandriva bug that looked similar - https://qa.mandriva.com/show_bug.cgi?id=42066
[20:15] <jcastro> bdmurray: Mr. QueryMaster - is there an easy way to find bugs that are linked to debian that are fixed but not fixed in ubuntu?
[20:15] <MarkusL> hi
[20:16] <jcastro> bdmurray: or do you think they show up in harvest?
[20:16] <MarkusL> i've got this straaange problem which i think is a bug since trying kernel 2.6.27 (w/ and w/o intrepid) on my aspire one.
[20:16] <jcastro> bdmurray: nevermind, they show up in harvest. (whew!)
[20:17] <MarkusL> i can't establish tcp connections through my nat router (which is a veeery old zyxel p310). ping, udp works, but tcp just sends a syn w/o answer until it fails.
[20:18] <MarkusL> older kernels work fine, other places using wrt54g/openwrt als nat router work, too.
[20:19] <MarkusL> wireless/wired doesn't matter.
[20:29] <MarkusL> oh well, i just found the solution. setting tcp_sack to 0 makes things work. now i just gotta find out why...
[21:26] <chrisccoulson>  hi, does anyone know the significance of this kernel message: "Aperture beyond 4GB. Ignoring."
[21:26] <murdok> Could someone change the importance of bug #271097 to its appropiate?
[21:40] <hggdh> murdok, what would be the importance?
[21:41] <murdok> I'm not sure between medium and high.
[21:41] <murdok> hggdh
[21:43] <hggdh> OK. A question -- what would the reporters have on their keyring? What keyring is in use (searhorse/Edit/Preferences)?
[21:43] <hggdh> murdok, ^^
[21:43] <hggdh> murdok, another point, FWIW: I have no problems...
[21:45] <murdok> hggdh: are you asking me? :?
[21:45] <hggdh> murdok, well, yes, you are asking to set the importance on the bug, I assumed you were working on it
[21:45] <murdok> no, I just confirmed it
[21:52] <murdok> hggdh: thx!
[22:29] <mrooney> is a bug in the applications menu against gnome-panel?
[22:30] <mrooney> or would that belong in one of the applets packages of gnome-panel?
[22:31] <pochu> mrooney: what's the bug?
[22:32] <mrooney> bug 196666
[22:35] <pochu> mrooney: I would blame compiz but I may well be wrong
[22:36] <mrooney> pochu: I don't see how it could be compiz since he says any other combination of items works fine
[22:38] <pochu> good point
[22:38] <pochu> mrooney: I'd ask him to run desktop-file-validate in the two .desktop files
[22:38] <pochu> perhaps there's something weird with one of them
[22:39] <mrooney> pochu: could be but it is still a bug in gnome-panel I think since it should handle invalid .desktop files in a better way than a white box :)
[22:40] <mrooney> pochu: though it would be good to find out I agree, how could I tell him to locate the desktop files?
[22:40] <pochu> mrooney: they should be in /usr/share/applications/
[22:45] <maco> is the fact that i'm seeing two months' little calendars showing in the left-side of evolution instead of the usual 1 little month calendar a bug, or is that a new feature?
[22:57] <maco> nevermind, feature apparently.