[00:50] <mrooney> is there a way to search for bugs WITHOUT a tag on launchpad?
[00:58] <bdmurray> mrooney: nope, what are you looking for specifically?
[00:59] <mrooney> bdmurray: well, I wanted to see if there we any needs-packaging bugs that weren't tagged
[00:59] <mrooney> based on title
[01:01] <bdmurray> mrooney: oh, I've something that checks for that already ;)
[01:01] <mrooney> bdmurray: ahh okay, I had a guess that you might :)
[01:01] <bdmurray> I think I ran it last week or so
[01:02] <mrooney> I figured I could do a search for needs packaging bugs based on title, and then the same search with the tag, and take the difference
[01:02] <mrooney> is that how you do it?
[01:02] <bdmurray> bugs w/o a package, title like [n-p] and n-p not in tags via py-lp-b
[01:04] <mrooney> bdmurray: by the way, did you ever take a peek at https://wiki.ubuntu.com/MikeRooney/EeeBotuSpec and see if I missed any use cases under Subscriptions?
[01:09] <bdmurray> mrooney: bugs newly targetted to a release and recently assigned an importance
[01:10] <hggdh> bdmurray, hi
[01:11] <bdmurray> hggdh: hello
[01:13] <mrooney> bdmurray: when you say newly targeted and recently assigned, do you mean...new bugs?
[01:14] <mrooney> bdmurray: ahh, I see, I guess EeeBotu could also read the recently changed bugs to get things like that
[01:14] <bdmurray> mrooney: a bug that just had an importance of High assigned to it
[01:14] <mrooney> though currently it only looks at new bugs
[01:14] <mrooney> so you have opened up a whole new world of ideas
[01:14] <hggdh> yes!
[01:15] <bdmurray> mrooney: the old bot used the mailing list I believe
[01:15] <bdmurray> and that would have changes like that
[01:15] <mrooney> hm I thought it was only new bugs...
[01:15] <mrooney> I suppose you would know better than I, however
[01:15] <hggdh> bdmurray, you mean parsing the emails sent to -bugs?
[01:15] <bdmurray> That's correct
[01:16] <hggdh> kees, not really that difficult
[01:18] <hggdh> so, probably 3 threads: one reads email, one reads RSS, and one communicates with IRC
[01:18] <hggdh> probably more...
[01:18] <hggdh> dammit, again I pinged k ees, instead of OK
[01:19] <hggdh> I am going to take out this expansion... I am tired of it
[01:19] <mrooney> hggdh: expansion?
[01:19] <hggdh> xchat auto expands k to the first nick that matches
[01:20] <hggdh> if at the beginning of a new line
[01:21] <pwnguin> is there a way to discover the debian QA URL for a package from the name itself?
[01:21] <pwnguin> something like     * error fetching http://packages.qa.debian.org/l/liferea/news/rss20.xml (404 Not Found)
[01:21] <pwnguin> doh
[01:22] <pwnguin> http://packages.qa.debian.org/l/liferea/news.rss20.xml
[01:22] <pwnguin> something like that; im guessing it's not always just a single letter?
[02:37] <mrooney> bdmurray: still around?
[03:21] <hggdh> nullack, check your mail
[03:22] <nullack> hggdh : Wow, thanks heaps :)
[03:22] <nullack> I note your points and Im looking at it in detail now
[03:22] <hggdh> yes, I would like more comments on it indeed
[03:23] <emma> test
[03:23] <hggdh> test echo
[03:37] <emma> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/270357
[03:51] <lifeless> bug 269168
[03:51] <mrooney> lifeless: mentioning that bug for any reason?
[03:52] <lifeless> yes, to get the link quickly, before I follow up
[03:52] <mrooney> okay, I was just seeing if you wanted feedback or help
[03:53] <lifeless> trying to get my dad engaged with Ubuntu, and 'pedro' has unhelpfully marked the bug as invalid, even though the topic is entirely accurate :)
[03:54] <mrooney> lifeless: well the issue is that you described two issues in the same bug, which isn't helpful to developers and triagers
[03:55] <mrooney> your description seems mainly about the background color, which as Pedro says is invalid as this is controlled by your theme
[03:55] <mrooney> however the documentation is apparently incorrect so I would either transform that bug only into being about that, or make a new one
[03:59] <lifeless> mrooney: thats my dads description FWIW. As he isn't upstream, he can't really tell a-priori that there were two issues or one (and arguably its one issue - the docs are wrong; they should point at the theme)
[04:00] <lifeless> mrooney: pedro, the triager that touched it should have transformed it rather than closing it invalid; round-trips are not efficient use of anyones time.
[04:01] <hggdh> lifeless, the same can be said about more than one issue per bug... but, anyway, you can re-open & edit the tile and description
[04:01] <lifeless> hggdh: a) I have already, and b) its only one issue
[04:02] <hggdh> lifeless, then I am lost. What is the problem?
[04:02] <lifeless> hggdh: don't know?
[04:02] <lifeless>       ^I
[04:05] <mrooney> lifeless: I understand where initially it doesn't seem efficient to ask you to do the work that he understands better, but the problem is that he couldn't do all that work for every single bug, so it is better to at least get a process started than do nothing
[04:07] <lifeless> mrooney: I think your understanding on queuing and scaling is a little broken, but thats ok, I have code to write up right now
[04:08] <lifeless> particular with respect to new community members that we want to engage with not drive away
[04:08] <lifeless> ciao for now
[04:09] <hggdh> mrooney, not worth the time
[04:11] <mrooney> hggdh: :)
[04:22] <j-b> hello
[04:23] <persia> j-b: Welcome
[04:23] <j-b> :)
[04:23] <j-b> sorry
[04:23] <j-b> I am upstream developer of VLC media player
[04:23] <persia> Excellent!
[04:23] <j-b> and trying to make some cleanness
[04:23] <j-b> in the vlc bug page
[04:23] <j-b> we just released 0.9.2 which fixes more than a few bugs
[04:24] <mrooney> hggdh: I feel like we should have wiki pages for such things, to explain philosophies and workflows in an end-user oriented way, perhaps
[04:24] <j-b> having a fixed_upstream tag would help
[04:25] <mrooney> j-b: well you could link them to your upstream track and mark then as fixed there, perhaps?
[04:25] <mrooney> *upstream bug tracker
[04:25] <mrooney> that seems ideal
[04:25] <j-b> no, because we don't have those bugs in our tracker
[04:25] <persia> j-b: Do you want those bugs in your tracker?
[04:26] <j-b> no
[04:26] <j-b> :)
[04:26] <persia> Ah.  That makes it trickier. :)
[04:26] <mrooney> what about a tag like fixed-vlc-092 or something?
[04:26] <j-b> I could
[04:26] <j-b> mrooney: can I do that ?
[04:27] <j-b> moreover most bugs are NOT vlc bugs
[04:27] <j-b> but this is another subject
[04:27] <mrooney> tags are arbitrary and merely convention, as I understand them
[04:27] <persia> I think it'd be better to just report which bugs are fixed by 0.9.2 in bug #262705
[04:27] <j-b> ok
[04:27] <j-b> neat
[04:27] <persia> That's the bug that is being tracked for the upgrade, so the developer who ends up looking after the upgrade will probably look there.
[04:27] <j-b> persia: in fact, to tell you the truth, it is complex, since  we removed one module
[04:28] <persia> (mind you, it's also out of date, but that's different)
[04:28] <j-b> that was very crashy
[04:28] <j-b> so we don't want those bugs in our tracker
[04:28] <j-b> persia: this bug is about 0.8.6i not 0.9.2
[04:28] <hggdh> mrooney, he is not a newcomer
[04:28] <mrooney> hggdh: oh...
[04:28] <persia> j-b: If you scroll down, you'll notice that someone suggested going to 0.9.2.  Which version do you think should be shipped?
[04:29] <j-b> persia: when ?
[04:29] <persia> j-b: October.
[04:29] <j-b> persia: to fix security issues and those bugs ? 0.9.2
[04:29] <j-b> or 0.9.3
[04:29] <j-b> but this is just my opinion
[04:29] <persia> j-b: RIght :).  Someone just needs to update the title of 262705 to show the right version :)
[04:29] <mrooney> j-b: must developers always want their latest version shipped :)
[04:29] <j-b> and since vlc should be in multiverse now...
[04:29] <mrooney> *most
[04:29] <persia> j-b: You're likely at least as qualified as anyone else to determine which version is best to ship.
[04:30] <j-b> mrooney: well, I don't really care, I use mine
[04:30] <j-b> mrooney: and I don't use my program, I code it :D
[04:30] <hggdh> mrooney, and his aggressiveness very much put me off
[04:30] <j-b> persia: so you are sure that I don't create a new ticket for 0.9.2 ?
[04:31] <persia> j-b: Yep.  There's no value in a new ticket, as the old one is out of date.  If there is an upgrade to 0.9.2, there's no point to also upgrading to 0.8.6.u.
[04:31] <persia> s/u/i
[04:31] <mrooney> persia: shouldn't it really be two bugs, not one for both hardy and intrepid?
[04:31] <j-b> j :D
[04:31] <j-b> true
[04:31] <mrooney> wouldn't you want a hardy backport request and an intrepid sync, or something?
[04:32] <j-b> hardy security should have 0.8.6j
[04:32] <j-b> intrepid should have 0.9.2
[04:32] <persia> mrooney: backports should be separate bugs, but against the $(release)-backports project, not against Ubuntu.
[04:32] <j-b> "This bug has 8 duplicates " :D
[04:32] <persia> jdong: !
[04:32] <mrooney> persia: ah, right
[04:32] <j-b> nice job, jb
[04:32]  * jdong was told to spawn here
[04:32] <persia> jdong: Please provide guidance on bug #262705
[04:33] <mrooney> persia: but still the 0.8.6j hardy security bug as j-b said should be separate from the 0.9.2 intrepid one, right?
[04:33] <persia> Looks like we need a backport/sru/security update for 0.8.6.j and some upstream bugs were fixed in 0.9.2 for intrepid.
[04:33] <jdong> j-b: I'm interested in doing the VLC update to 0.9.2; I spent a few minutes earlier trying to understand the changes to 0.9.2 and what we need to do with our packaging
[04:33] <j-b> persia: yes.
[04:33] <persia> jdong: j-b is upstream VLC, and has *all* the details.
[04:33] <j-b> jdong: ok
[04:33] <j-b> jdong: you need to remove libwx
[04:34] <j-b> and  depend on libqt4-core libqt4-devel
[04:34] <j-b> jdong: but maybe you are interested in our debian/rules
[04:34] <jdong> I already got wx and libqt4-dev fixed
[04:34] <j-b> :)
[04:34] <jdong> j-b: yeah your debian/rules would be helpful
[04:34] <j-b> jdong: give me a second
[04:34] <jdong> I also got the various other build-deps that ./configure bails on
[04:34] <j-b> really ?
[04:34] <jdong> yeah, as I said, I was tinkering with it a lil bit earlier today
[04:35] <jdong> I believe they were dts->dca, libxpm/libxt-dev
[04:35] <j-b> http://www.jbkempf.com/blog/post/2008/03/28/Build-VLC-media-player-under-Ubuntu-Hardy-804 is still my configure, that i use
[04:35] <j-b> jdong: yes, but you need libass, which is in debian NEW
[04:35] <jdong> j-b: I believe it's in intrepid
[04:35] <jdong> https://edge.launchpad.net/ubuntu/+source/libass
[04:35] <j-b> and qgtkstyle is more than recommanded
[04:35] <j-b> jdong: great
[04:36] <j-b> http://nightlies.videolan.org/build/intrepid-i386/
[04:36] <jdong> j-b: thanks; I'll take a look at the debian dir in that packaging
[04:37] <j-b> jdong: do you have libscroedinger-dev on interpid ?
[04:37] <j-b> jdong: maybe we shouldn't discuss this on this chan
[04:37] <mrooney> it sure is incredibly interesting to me
[04:37] <mrooney> :)
[04:38] <mrooney> I doubt anyone cares in such a low traffic channel
[04:38] <j-b> jdong: the bigger changes I would say are: qt4, schroedinger, liboil,
[04:38] <j-b> taglib
[04:38] <jdong> got it.
[04:38] <j-b> mpeg2 MUST be update
[04:38] <j-b> mpeg2 MUST be updated
[04:38] <jdong> updated from where?
[04:38] <j-b> https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/97721 has already 8 duplicates of this MPEG2 issue
[04:38] <j-b> upstream
[04:39] <j-b> this bug is not a vlc bug
[04:40] <jdong> ok, I'll put those on my TODO list.
[04:40] <jdong> thanks for the advice, j-b. I need to call it a night and continue tomorrow
[04:40] <jdong> j-b: I'll be working on the packaging and updating the status on bug 270404 if you'd like to subscribe
[04:41] <mrooney> jdong: so do you think that bug 262705 should be just for hardy? to track the security update
[04:41] <j-b> arf
[04:41] <mrooney> and then the 0.9.2 for intrepid?
[04:42] <j-b> I modified 262705
[04:42] <j-b> jdong: ok
[04:42] <mrooney> :]
[04:42] <jdong> mrooney: hmm 262705 should be hardy for now, preferably a backport of the patch. looking at this the changes needed for 0.9.2 are a bit intrusive for hardy
[04:42] <j-b> jdong: I just created my launchpad account
[04:42] <jdong> j-b: awesome
[04:43] <jdong> j-b: thanks for coming here; it's always great to have upstream around for tasks like this :)
[04:44] <j-b> well, my g/f, my parents have been switched to ubuntu :D
[04:44] <mrooney> jdong: but should 262705 be a backports request or a security update sru? j-b mentioned it contains security updates
[04:44] <jdong> mrooney: it's a security update
[04:44] <mrooney> sorry to keep you up for another minute :)
[04:44] <jdong> mrooney: the issue mentioned is pretty serious
[04:44] <j-b> jdong: don't ship i
[04:44] <j-b> ship j
[04:44] <j-b> seriously
[04:45] <jdong> j-b: you mean for Intrepid?
[04:45] <jdong> or for hardy's update?
[04:45] <j-b> hardy update
[04:45] <jdong> ok
[04:45] <j-b> anyway
[04:45] <j-b> how do I link from one bug to another ?
[04:45] <mrooney> okay so threefold probably? 1. hardy security to 0.8.6j, 2. hardy backport for 0.9.2 and, 3. intrepid sync for 0.9.2 ?
[04:45] <jdong> if you just say bug #12345, it'll be turned into a link automatically
[04:45] <jdong> oops :)
[04:46] <mrooney> j-b: just mention it in a comment like jdong said
[04:46] <persia> If you put in the comment something of the form "bug #123456" it will automatically create a link on display.
[04:46] <j-b> hardy backport is difficult task
[04:46] <jdong> mrooney: hardy-security to j or the equivalent of j, intrepid packaging of 0.9.2.
[04:46] <jdong> mrooney: I'm not sure if a hardy backport of 0.9.2 will be possible but we can evaluate that once we have intrepid packages.
[04:46] <mrooney> yes those seem like the important ones
[04:48] <j-b> jdong: for #107899, you need 0.9.2+ a patch
[04:49] <j-b> https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/270404/comments/9 at least those bugs
[04:49] <jdong> j-b: ok I'll have to look into the mpeg2 update and see what I can do with the release team
[04:50] <j-b> what do I do about bugs that are NOT vlc ?
[04:50] <j-b> like ffmpeg ?
[04:50] <jdong> j-b: you can use Also Affects, distribution Ubuntu, package ffmpeg
[04:50] <j-b> like #104671
[04:50] <jdong> and mark the bug invalid for VLC And confirmed for ffmpeg
[04:50] <j-b> well, I cannot until I have a sample to test
[04:51] <j-b> else, ffmpeg is going to send it back :D
[04:51] <j-b> but I am really sure
[04:51] <jdong> ok, I really need to sleep; early morning classes and long day ahead
[04:52] <jdong> you can almost always find me in #ubuntu-motu in case something else comes up :)
[04:52] <greg-g> j-b: a "cleaner" way of changing the assigned package is to simply edit the current assigned (ie: not adding a new one and invalidating the old, just change the current one).
[04:53] <j-b> https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/270404/comments/9
[04:53] <j-b> thos don't move to links
[04:53] <j-b> greg-g: maybe
[04:54] <greg-g> need the word "[bB]ug" before the numbers :)
[04:55] <j-b> and of course, I cannot edit my comments :)
[04:55] <j-b> can I tag as invalid if description is incorrect ?
[04:57] <greg-g> what do you mean description is incorrect (sorry, I haven't been following the whole conversation)
[04:58] <greg-g> if the bug is invalid (NOTABUG) then yeah, mark as invalid.  If it is just assigned to the wrong package, reassign it.
[05:00] <j-b> ok
[05:00] <j-b> if I need a Stacktrace ?
[05:00] <mrooney> j-b: if you want to make changes you are pretty sure of and keep a list, I will be happy to review them tomorrow!
[05:01] <j-b> mrooney: well, codecs crashes are not really in FFmpeg
[05:01] <greg-g> then comment and say what you need and mark as incomplete
[05:01] <j-b> not really in vlc, but more in Ffmpeg
[05:05] <nullack> siretart said that there wont be an ffmpeg update for Intrepid, and that means any VLC upgrade done properly wont be achieved either
[05:05] <j-b> :)
[05:05] <mrooney> j-b: but anyway I would recommend keeping a list and posting it here so that a bugcontrol member or someone similar can make sure they are all kosher and save you some work
[05:05] <j-b> I was sure of that
[05:06] <j-b> but at least, it will not be our fault
[05:07] <j-b> We will link to your bug and redirect the already numerous users who ask
[05:08] <mrooney> j-b:  :)
[05:08] <j-b> seriously
[05:08] <j-b> some security issues are only in 0.9.2
[05:08] <j-b> and 0.9 will fixe more than a couple dozen of your bugs
[05:15] <techno_freak> bug 270356 - can someone check and mark this as wishlist?
[05:27] <j-b> jdong: ping
[05:37] <greg-g> techno_freak: set to wishlist and I found the upstream bug report
[05:39] <techno_freak> greg-g, thanks :)
[05:42] <greg-g> techno_freak: no problem
[05:50] <j-b> greg-g: mrooney: nullack: jdong: tahnks and good luc
[05:50] <j-b> luck
[05:56] <dholbach> good morning
[06:00] <thekorn> morgen dholbach
[06:01] <dholbach> hiya thekorn
[06:01] <dholbach> up early? :)
[06:02] <techno_freak> morning dholbach
[06:03] <thekorn> yes, way too early
[06:05] <dholbach> hi techno_freak! :)
[06:05] <dholbach> thekorn: what happened? who woke you up?
[06:07] <thekorn> dholbach, nothing special, just have to catch the bus in a few
[06:09] <dholbach> ah ok - leaves you some time to wake up :)
[06:10] <thekorn> yes, I definitely need this
[07:09] <persia> Anyone read Russian well enough to understand whether bug #270773 is valid?
[07:12] <maco> persia: i could tell ya how to pronounce it, but that's about it, sorry
[07:13] <persia> maco: I'm a little better than that, but not enough to know if these patches are interesting :(
[07:18] <dholbach> persia: I'm sure pitti can help with that - he maintains postgres AND learned Russian at school! :)
[07:24] <persia> dholbach: Excellent.  Very low requirement for triage then :)
[07:24] <dholbach> :-)
[07:40] <maco> bdmurray: ehlo?
[09:49] <danage> seb128: you just closed my bug and i wanted to apologize for not updating the info. will do soon. it _is_ a bug
[09:49] <seb128> danage: which one?
[09:50] <danage> gvfs doesn't do active ftp connections
[09:50] <seb128> ah
[09:50] <danage> 260334
[09:50] <seb128> maybe you could open it on bugzilla.gnome.org too ;-)
[09:50] <seb128> that's for sure an upstream issue
[09:51] <danage> i might need to subscribe. i will add to the description but i am not sure what other information would be helpful. it simply connects as passive every time (i _think_)
[09:51] <danage> and some server firewalls don't like that
[09:51] <seb128> right, we just get hundred of bugs every week and we can't spend one hour or each so detailled description are welcome
[09:52] <danage> yeah, i see. i will do some testing and maybe give a paste of the ftp command that get issued and those that should be issued.
[09:52] <danage> *commands
[09:52] <seb128> better if somebody having access to a configuration triggering the bug can sent it upstream too
[09:52] <danage> i can set one up, it's easy
[09:52] <seb128> rather than waiting on a bug triager to set up a configuration he has no idea about just to validate the bug and copy it upstream
[09:53] <seb128> alright
[09:54] <danage> thanks seb128
[11:00]  * popey goes "ugh" at bug 270796
[11:04] <danage> lol
[11:14] <persia> I think it's Invalid.  There's no legal reason for us to remove it, and we'd have to take extra steps to blacklist it being imported from Debian.
[11:16] <danage> the question is: how far does open go
[11:16] <danage> it's like the problem the pirate bay has, when people ask them to take down stuff
[11:19] <ogra> danage, well, if an israel company would ask us to tear out the ubuntume packages from the archive because they provide different religious views, would you agree to pull it out ?
[11:20] <danage> i am not trying to display a certain opinion, i am just saying it's a controversial issue
[11:20] <ogra> its not
[11:21] <ogra> we simly have to stay neutral unless a package has legal issues
[11:21] <ogra> the content of the package is freely available on the internet ... people can just pull it if tehy want to
[11:22] <ogra> i agree that we shouldnt pul it to main for various reasons ... but there is no reason to pull it out the archive ...
[11:23]  * ogra is reminded of the bouncing cow screensaver issue he had to solve years ago in hoary
[11:24] <persia> Bouncing cow?  What about that load meter that was a stripper.
[11:25] <danage> lol
[11:28] <ogra> persia, i never had complaints about that one :)
[11:28] <ogra> but i got a lot of upset indian users about the bouncing cow :)
[11:29] <danage> ogra: how can you say it's not when two people file bug reports on it
[11:29] <ogra> the screenaver packages always got me the most entertaining bugs :)
[11:30] <ogra> danage, they ar free to not install it :) as they are free to not use the internet
[11:31] <persia> ogra: Ah ha!  I get it now.  I think that the stripper was blocked from Debian after several months of argument on d-d
[11:31] <ogra> we wot rip out packages from the archive because people dislike them ... not moving them into the suported set is something else though... anarchism will surely never show up on a official ubuntu CD as the buncing cow screensaver will
[11:31] <ogra> s/will/will never do/
[11:32] <ogra> persia, i had complaints about GLsnake ... and had to patch out the names for "penis" and "vulva" shapes from it :)
[11:32] <persia> http://lwn.net/Articles/113644/ is a good discussion of it.
[11:33] <ogra> heh, yeah i remember reading about it
[11:33] <persia> ogra: screensavers are a thankless thing to maintain :)
[11:33] <ogra> its a lot of fun
[11:33] <ogra> the only drawback is that you have to handle triaging all the bugs for the X team as well
[11:34] <ogra> since users often dont get that its not the screensavers fault that their system locks up
[11:34] <persia> heh.  Of course, one can never be clean.  Somebody will always be offended by something, even if that something is only the absence of something.
[11:44] <nullack> ping bdmurray
[11:47] <james_w> nullack: it's very early for Brian
[11:50] <nullack> james_w: Right, no worries
[11:55] <mrooney> timezone-appropriate greeting!
[11:58] <persia> mrooney: timezone-appropriate response!
[12:01] <mrooney> I wonder if a PPA for vlc 0.9.2 will pop up for hardy
[12:10] <ahmadtarek> Hi every body, I think #270639 should be changed to wishlist
[12:15] <persia> mrooney: j-b seemed to think there would be some issues backporting that, and recommended 8.6.j
[12:15] <persia> bug #270639
[12:16] <persia> ahmadtarek: Have you reviewed the bugs fixed upstream?  Are any of them greater than wishlist?
[12:19] <ahmadtarek> persia: what do you mean by greater than wishlist?
[12:19] <ahmadtarek> persia: (I'm still new to working with bugs :) .. so don't panic)
[12:28] <persia> ahmadtarek: Well, that bug contains a link to a bunch of bugs that were fixed in the update release.  While the desire to update is wishlist, it may be that something more important will be fixed by the upgrade.  When you have a handy list like that, it's good to review it to see.
[12:38] <Hew> Bug 270639 is a dupe. I just fixed it.
[12:38] <Hew> Was anyone triaging bug 270796, or should I take care of it?
[12:41] <ahmadtarek> persia: thank you .. I think it is handled now
[12:42] <persia> ahmadtarek: Indeed.  Once a bug is In-Progress, it's best not to adjust the Importance (unless you're the assignee) :)
[12:43] <persia> Hew: I think nobody wanted to touch it, as it's likely to be an involved discussion.
[12:58] <nullack> Ive got some low severity bugs here someone might like to confirm : bug 263819 and bug 263817
[12:59] <nullack> Hi pedro
[13:00] <pedro_> morning nullack
[13:01] <nullack> Also while anyone's at it, bug 263153 crashes the gstreamer ffmpeg plugin if anyone wants to confirm that too :)
[13:26] <hggdh> Hew, you beat me to it...
[13:27] <hggdh> (bug 270796)
[13:29] <Hobbsee> hggdh: i think you should remove all packages from ubuntu, as they can be used to create spam, allow people to write programs to fire nuclear missiles, and other highly dangerous disasters.
[13:31] <hggdh> Hobbsee, hey, good idea: they are really dangerous. Actually, let's just remove the Linux kernel: nobody will be able to run anything dangerous anymore!
[13:31] <Hobbsee> hggdh: *grin*.
[13:31]  * hggdh sadly smiles
[13:31] <Hobbsee> hggdh: and anything that writes text - so no new text can be written, to create bad programs.
[13:31] <Hew> hggdh: :P
[13:32] <hggdh> and video monitors: nobody will be able to see them bad texts anymore!
[13:32] <hggdh> now, for disabling sound, all we need is to install pulseaudio ;-)
[13:33] <Hobbsee> :P
[13:33] <Hobbsee> pa works fine for me.
[13:33] <Hew> Perhaps add the iTunes EULA that forbids using applications as nuclear, chemical or biological weapons?
[13:33] <hggdh> LOL
[13:34] <hggdh> I have been battling pa for a while... yesterday it was working, today it is not anymore. Ah well. Will look at it later, during lulls at work
[13:34] <hggdh> and... speaking of which... gotta go earn me some money
[14:12] <pedro_> is anyone running empathy?
[14:12] <pedro_> oh my gosh
[14:12] <nullack> webkit or the other one?
[14:12] <pedro_> uff not so bad netsplit it seems
[14:13] <pedro_> nullack: empathy with webkit?
[14:13] <pedro_> nono you're maybe confusing it with epiphany :-P
[14:13] <nullack> pedro_ Very true : Its 11:13 pm here I should goto bed :)
[14:15] <pedro_> hehe
[14:53] <bddebian> Boo
[14:55] <pedro_> buuu!!
[14:57] <Bassetts> hello, I have found a bug that is more a feature request. What do I do with it?
[14:58] <james_w> Bassetts: you can ask to have it marked as "wishlist"
[14:58] <james_w> what's the bug number?
[14:59] <Bassetts> 270895
[15:01] <james_w> bug 270895
[15:10] <james_w> Bassetts: done, thank you
[15:10] <james_w> Bassetts: please see my comment in the bug report, you may wish to forward this bug for the reporter if you are vaguely familiar with pidgin
[16:03] <Flimm> Hello, if I bug is set to invalid, why can't I convert it to a question?
[16:06] <Bassetts> james_w: thanks, am I allowed to mark that as one of my 5-a-day?
[16:07] <james_w> Bassetts: I guess so :-)
[16:07] <Bassetts> thanks =)
[16:07] <techno_freak> Flimm, which nug?
[16:08] <techno_freak> err.. bug*
[16:18] <seb128> does anybody knows if there is an easy way to check if a launchpad url is a valid one or a placeholder for a wrong url?
[16:19] <bdmurray> seb128: what url?
[16:20] <seb128> bdmurray: https://edge.launchpad.net/bugs/1234567 for example
[16:21] <bdmurray> I think that is a placeholder since it redirects you to bugs.launchpad.net/project/+bug/number
[16:21] <seb128> right
[16:21] <seb128> so what I'm trying to do is to have a small piece of code which goes through a list of bugs
[16:21] <seb128> and open those which have a https://bugs.edge.launchpad.net/bugs/bugtrackers/gnome-bugs/nnnnnn url
[16:22] <seb128> that's to list bugs closed in a new tarball version for example, upstream list bugzilla numbers and using this url either return an ubuntu bug number or the placeholder webpage
[16:23] <seb128> opening just valid ones would be nicer
[16:25] <bdmurray> seb128: I think this should be possible with py-lp-b
[16:32] <Flimm> techno_freak: https://bugs.launchpad.net/ubuntu/+bug/270149 is a bug that I wanted to turn into a question, I ended up not doing so
[16:46] <Flimm> h
[16:48] <bdmurray> mvo: what do you with update-manager bugs regarding mirrors?
[17:19] <chrisccoulson> hi, would someone mind helping me out with a bug against gnome-applets please? (bug 270123)
[17:19] <chrisccoulson> the battery status applet indicates the wrong battery status, but gnome-power-manager and hal are correct
[17:20] <chrisccoulson> i don't know where the battery status applet gets the information from
[17:20] <chrisccoulson> so i don't know if the bug is in gnome-applets, or the kernel (or something else)
[17:21] <seb128> chrisccoulson: what about acpi on a command line?
[17:22] <chrisccoulson> i think he did that - but the results look inconsistent with the applet
[17:23] <chrisccoulson> although he doesn't specify under which conditions he ran acpi on the command line (AC power present/not-present)
[17:23] <seb128> chrisccoulson: the applet uses /proc/acpi/battery
[17:23] <chrisccoulson> and hal uses /sys/devices....something, which is probably where the difference is
[17:24] <chrisccoulson> so if /proc/acpi/battery is wrong, i should assign it as a kernel bug instead i think?
[17:25] <seb128> chrisccoulson: or acpi, not sure about how those are working exactly
[17:27] <chrisccoulson> i think the acpi source package only contains the command line utilities for looking at the stuff in /proc/acpi. so i think it would be a kernel bug if the information exported to /proc/acpi is wrong
[17:27] <chrisccoulson> thanks for your help
[17:27] <seb128> you're welcome
[17:29] <persia> chrisccoulson: The contents of both /sys and /proc *should* be provided by the kernel, rather than any other package, although it might end up as some modules package, depending.
[17:31] <chrisccoulson> yeah, I agree. although the number of packages containing modules likely to provide this information is probably quite limited isn't it?
[17:31] <seb128> I'm wondering why people still use the old battstat applet though
[17:31] <seb128> we should probably stop building it
[17:32] <persia> For acpi, I know it's just the linux package.  It's just that since kernel modules can be in other packages, and can adjust the contents of /proc and /sys, I figured it was worth mentioning.
[17:32] <chrisccoulson> seb128: you're probably right. the alternative would be to migrate it to sysfs or build it with HAL support
[17:32] <chrisccoulson> at least it would be consistent then
[17:33] <chrisccoulson> persia - thanks:)
[17:33] <persia> seb128: It's the standard choice when one chooses "Add to Panel".  If it's deprecated, it oughtn't be shipped (or at least, not by default)
[17:34] <ogra> seb128, hal/g-p-m moved away from /proc completely
[17:34] <ogra> it only uses sysfs
[17:35] <ogra> if battstat uses /proc/acpi it should be changed to sysfs or be dropped
[17:35] <chrisccoulson> isn't /proc/acpi deprecated anyway? its virtually empty on my machine now
[17:35] <ogra> (/me would go for the latter)
[17:35] <ogra> yes
[17:35] <seb128> right, I know that
[20:06] <mvo> bdmurray: re mirror problem> I asked the sysadmins earlier about this but got no reply
[20:56] <ronny> yo
[20:57] <ronny> anything known about wpa breakage in intrepid after the last update (nobody in #ubuntu+1 answers, and i couldnt figure how the heck to use the bts)
[21:00] <Brucevdk> Question. After returning from standby I am plagued with severe rendering problems. Transparant areas, pages won't render in Firefox, windows diseappearing when being moved and only redrawing when Alt-Tabbing (focus in/out). This is using Metacity, when using Compiz the screen stays blank. Restarting xserver does not help. Unsure which package to file a bug against, can't find a similar bug (Bug #173190 seems Fx specific).
[21:05] <Brucevdk> Hmm looks like this might be Bug #60882
[21:06] <Brucevdk> But that's from 2006, I had no problems at all in the previous releases.
[21:06] <Brucevdk> Regression maybe, or driver problem, or I-don't-know-what
[21:08] <Brucevdk> Think I might just file it against xserver-xorg-video-i810
[21:13] <Brucevdk> Might be back, might not. Trying out some workarounds mentioned in the bug report.
[21:19] <Brucevdk> Toggling SAVE_VBE_STATE to false in /etc/default/acpi-support solves/prevents the rendering issues
[21:23] <Brucevdk> On to the next bug, scripts in /etc/acpi/* not being executed.
[21:23] <Brucevdk> I gots a long night ahead it seems :-)
[21:57] <Ampelbein> hmm, is there something wrong with the automatic retracers?
[22:02] <emgent> bug #270707
[22:06] <pochu> Ampelbein: they are moving to a different datacenter AFAIK
[22:07] <pochu> (at least the intrepid one)
[22:07] <Ampelbein> ah, ok.
[22:09] <seb128> Ampelbein: why? they should be running again
[22:10] <seb128> Ampelbein: for technical reason the hardy ones are not running, don't bother duplicating those manually (I noticed you did that for some of gvfs-fuse-daemon crashes), they will be retraced when those are running
[22:10] <Ampelbein> ok. thats why i was asking
[23:38] <mrooney> james_w, persia: yeah, I guess it needs to have smarter "affects" detection