[02:32] <wolfger> greg-g: is ubuntu-michigan back in first yet? ;-)
[03:02] <bddebian> Boo
[03:09] <RAOF> bddebian: hiss!
[03:09] <bddebian> Hi RAOF :)
[03:09] <RAOF> :)
[03:09] <RAOF> Howdie.
[08:47] <ligemeget> when is the next hug day..?
[10:43] <wolfger> bug reporter is offering to recreate a problem to assist in debug of a Gutsy install issue, has not received a response. I'm not sure what to say: Bug 177951
[11:10] <siretart> hey bugsquadders.
[11:11] <siretart> I have written up a guide for triaging xine-lib bugs: https://wiki.ubuntu.com/ReinhardTartler/DebuggingXineLib
[11:11] <siretart> could someone of you please review it and tell me if its okay to proceed that way?
[11:11] <siretart> I do care for xine, in both ubuntu and debian, and I need help with the bugs in ubuntu.
[11:13] <ligemeget> Looks good to me
[11:16] <ligemeget> siretart, in what way do you need help? Triaging? Fixing? Or both ? :)
[11:17] <siretart> ligemeget: triaging would help. I need all crashers tested with the latest upstream versions, and up-to-date backtraces, so that I can go with them to upstream
[11:17] <siretart> so, basically follow the instructions I put on the wiki
[11:18] <ligemeget> siretart, I'd be happy to crash test - what program uses xine-lib?
[11:19] <siretart> ligemeget: gxine, xine-ui, totem-xine, amarok, kaffeine, pornview, and quite some more
[11:19] <siretart> gxine is probably to easiest to handle for this task
[11:19] <ruiboon> siretart: instead of "make sure that ... 'ffmpeg-dbg' and 'libxine1-dbg' are installed" could we just phrase it as $ sudo apt-install ffmpeg-dbg libxine1-dbg ?
[11:20] <siretart> ruiboon: it's a wiki, please edit as you seem fit
[11:20] <siretart> (for that purpose I asked for review after all ;)
[11:21] <ruiboon> siretart: found it more useful if the exact command is given. thus more people can follow it
[11:22] <ruiboon> and there will be lesser "how do i go about doing it...?"
[11:22] <siretart> right
[11:23] <ligemeget> siretart, I think I'll try crashing gxine a bit when I get home, then :)
[11:23] <ligemeget> Are you a regular here on the channel?
[11:24] <ligemeget> (so I can reach you w/ feedback)
[11:24] <siretart> ligemeget: I can usually be found on #ubuntu-motu, but I try to stay here at least for a while ;)
[11:24] <ligemeget> ok :)
[11:34] <ruiboon> thanks for updating the wiki. my wiki editing skills seems to be rotting (:
[13:04] <Iulian> Hi
[13:08] <ruiboon> hi Iulian
[14:13] <rbs-tito> Can someone give me a hand; I think I can fix a bug but it is blocked by something else.
[14:13] <rbs-tito> bug 231917 depends on an alteration to libgweather
[14:13] <rbs-tito> Should a bug report for libgweather be opened to?
[14:20] <seb128> rbs-tito: that seems an upstream issue, but yes if a libgweather change is required a bug should be opened against it on bugzilla.gnome.org
[14:20] <rbs-tito> seb128: It is an upstream issue; should I not touch it?
[14:20] <seb128> rbs-tito: http://bugzilla.gnome.org/show_bug.cgi?id=520176 is already opened there
[14:21] <seb128> rbs-tito: you are welcome to work on a patch anyway, upstream welcome fixes usually and we can distro backport the change
[14:21] <rbs-tito> seb128: Would I submit the patch upstream or at launchpad?
[14:21] <seb128> upstream is better but launchpad works too
[14:22] <rbs-tito> ok, thanks
[14:22] <seb128> if you attach it on launchpad we will have to forward it upstream for you
[14:22] <seb128> but that's ok, we are used to do that ;-)
[14:22] <seb128> if you are fine sending it directly upstream that's less work for everybody though
[14:22] <rbs-tito> seb128: If I'm doing it upstream, would it be easier to use the very latest code from GNOME? Or should I use my Ubuntu version from the archive
[14:23] <seb128> I don't think the code changed much
[14:23] <seb128> ideally using svn is better
[14:23] <seb128> but most of the time using the ubuntu package is good enough
[14:23] <rbs-tito> ok, thanks for your help
[14:23] <seb128> you are welcome
[14:23] <rbs-tito> Do we have to do anything like with Debian usertagging with GNOME?
[14:26] <rbs-tito> Wait; this is ridiculous. There is no point in doing it; their formulae are wrong!
[14:27] <seb128> ?
[14:32] <rbs-tito> Upstream there are bugs saying that the times given aren't even accurate
[14:32] <rbs-tito> The time is calculated using complex astronomy calculations
[14:32] <rbs-tito> Which apparently are wrong
[14:33] <rbs-tito> And I'm no astronomer!
[15:25] <bddebian> Boo
[15:27] <marnanel> bddebian: boo.  what you need is Planet HURD, I think
[15:28] <bddebian> heh
[15:28] <marnanel> rather than a group blog.  anyway, sorry, this is OT here
[15:29] <marnanel> until that glorious day when Ubuntu ships with the HURD anyway. :)
[15:31] <rbs-tito> marnanel: ha!
[15:33] <bddebian> marnanel: gnumach/hurd/etc are in Ubuntu, they just don't build :)
[15:34] <marnanel> bddebian: we look to that glorious day!
[16:52] <pedro_> KelvinGardiner: hello, may you please add a comment to the bugs when you change the status of them?
[17:34] <dudus> how long before an incomplete bug expires?
[17:41] <qense> 60 days iirc
[17:47] <dudus> if i find a very old bug ~1 year old, and I think it is already fixed on hardy, can I mark it as Resolved? Or should I change it to Incomplete and ask confirmation from the original reporter?
[19:22] <sectech> Can bug #231976 be reviewed please... I guess I am missing the reporters point...
[19:32] <sectech> Never mind, I see what the reporter means...plus it's a dup
[21:14] <sectech> Is anyone around that can review a bug I am triaging? bug 230908
[21:15] <sectech> I am looking at the dmesg and I can't tell if I am looking at an error or if it is proper for a system resume
[21:17] <afflux> hi
[21:31] <sectech> I have no idea why gnome-do would effect a ACPI resume on a system...  I can't reproduce this
[21:38] <jarlath> I'm trying to debug an acpi related driver problem. I have no audio / video (eg totem, mplayer) on resume. What can I watch to track down the culprit?
[21:39] <sectech> jarlath,  I would watch dmesg and see what's going on
[21:39] <jarlath> Thanks sectech, I'll do that.
[21:58] <phixxor> hey can someone take a look at this bug report I just submitted
[21:58] <phixxor> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/232043
[21:58] <phixxor> see if I need to add anything else to the description, try something else
[22:19] <jarlath> I've discovered that my bug can be resolved by adding an option when the module is being loaded at boot time. Does anyone know what file this would be? It loads the intel audio module.
[22:30] <askand> Hi, will fix for bug 153572 enter hardy?
[22:32] <greg-g> jarlath: it would be best to add a comment to the bug report page with what change makes it work
[22:32] <greg-g> if there is no bug report page, search for one that describes the issue, and if you can't find one, open a new bug
[22:39] <jarlath> Hi greg-g, I actually got the fix from the launchpad page.
[22:39] <jarlath> So it is noted in the report.
[22:39] <greg-g> jarlath: ok, good deal
[22:40] <jarlath> There's just no mention of how to actually perform it. It seems the reporters are fairly advanced.
[22:42] <greg-g> well, LP is not a support forum, it is a place for people to fix bugs in the code so that they are fixed for everyone
[22:44] <jarlath> greg-g: True.