=== Sikon is now known as LucidFox
[14:42] <BUGabundo1> andersk: ping
=== stooj_ is now known as StooJ
=== jgoguen_ is now known as jgoguen
[16:52] <BUGabundo1> can some one help triage this bug https://bugs.edge.launchpad.net/netbook-remix/+bug/361143/
[16:52] <BUGabundo1> thanks
[16:52] <ubottu> Launchpad bug 361143 in netbook-remix "Gnome main menus disappear after changing GUI to "Desktop Classic"" [Undecided,New]
[17:10] <BUGabundo1> ogasawara: ping
[17:19] <ogasawara> BUGabundo1: something you need?  it's best to add some context when you ping.
[17:32] <BUGabundo1> ogasawara: sorry... got distracted...
[17:32] <BUGabundo1> ogasawara: trying to improve the data at bug 359231
[17:32] <ubottu> Launchpad bug 359231 in xorg "system freeze and kernel panic" [Undecided,New] https://launchpad.net/bugs/359231
[17:33] <ogasawara> BUGabundo1: a few questions, have you tried disabling compiz and see if that shows any improvements
[17:34] <ogasawara> BUGabundo1: also, do you recall specifically doing a kernel upgrade prior to getting these panics?  just curious which previous kernel was not problematic
[17:35] <BUGabundo1> ogasawara: yes! I'm running it with metacity and NV
[17:36] <BUGabundo1> only the latest kernel started happening
[17:36] <BUGabundo1> I added the apt change logs
=== maco_ is now known as maco
[19:40] <BUGabundo1> bye
=== davmor21 is now known as davmor2
[21:02] <thekorn> bug 325101
[21:02] <ubottu> Launchpad bug 325101 in wacom-tools "x11 won't start after upgrade to jaunty" [High,Incomplete] https://launchpad.net/bugs/325101
[21:04] <pwnguin> thekorn: what about it?
[21:05] <thekorn> pwnguin, sorry, posting it here was just the easiest way for me to get the url of this bugreport
[21:05] <pwnguin> if i could duplicate it, i'd patch it and beat upstream with it
[21:06] <pwnguin> but wacom's been working nicely for me thus far
[21:07] <thekorn> pwnguin, I'm in a chat with the reporter of bug 359960 and I was wondering if these two are duplicates
[21:07] <ubottu> Launchpad bug 359960 in xorg "xorg segfaults if /etc/hal/fdi/policy/10-wacom.fdi is present" [Undecided,New] https://launchpad.net/bugs/359960
[21:07] <thekorn> which is obviously not true
[21:15] <blueyed> Can somebody confirm bug 361275, before I report this upstream, please? (really easy to reproduce, if you have KMail on Jaunty installed)
[21:15] <ubottu> Launchpad bug 361275 in kdepim "KMail composer: Ctrl-Del does not delete next word anymore, if prefixed by whitespace" [Undecided,New] https://launchpad.net/bugs/361275
[21:21]  * e-jat guys .. i think .. i need to offline .. since it already 4.20 am in MY :) .... c u guys later ..
[22:08] <andol> Regarding bug #333620. Could someone with suitible powers set the status of the upstream bug as "Fixed commited". LP doesn't seem to be able to read the SF status.
[22:09] <ubottu> Error: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/333620/+text)
[22:12] <Ampelbein> andol: the bugwatches didn't get updated lately.
[22:13] <Ampelbein> andol: i'd set the status for the ubuntu-task to "Fix Commited" so the next updater can easily see what has been fixed.
[22:13] <andol> Ampelbein: Yes, but in this case there is an explicit error message, which has been for a while.
[22:14] <andol> Ampelbein: But wouldn't setting that status on the Ubuntu task imply that there is a debdiff, and that the actual Ubuntu package is about to be fixed?
[22:14] <Ampelbein> andol: from https://wiki.ubuntu.com/Bugs/Status : Fix Committed:
[22:14] <Ampelbein>     * For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place
[22:19] <andol> Ampelbein: Yes, but isn't that for the upstream task?
[22:20] <Ampelbein> andol: no, it's for the ubuntu-task. the upstream-task watch usually gets updated by the bugwatch. and should be set to "FixReleased"
[22:39] <HammerHead66> is anyone else having problems looking at bugs on launch pad?
[22:41] <HammerHead66> can anyone see the bugs from the "Bugs" tab?
[22:42] <HammerHead66> the only thing I get it my browser keeps acting like it's loading but it never loads anything
=== Flare183_ is now known as Flare183
[22:49] <HammerHead66> is anyone alive in this room?
[22:49] <stpere> not totally..
[22:50] <HammerHead66> stpere: are you able to look at bugs on Launchpad?
[22:50] <Ampelbein> HammerHead66: better place for such questions is #launchpad. and yes, i can view bugs.
[23:05] <hggdh> Ampelbein, actually, there has been some discussion about the "fix committed" thingy
[23:06] <Ampelbein> hggdh: oh. what was the outcome? i find it quite handy to see which bugs could be closed by updating version of a package.
[23:08] <hggdh> Ampelbein, the outcome is (for me) still a mistery. But I was, quite strongly, told that fix committed for an Ubuntu task is only when a package is in -proposed
[23:08] <hggdh> which I find rather unhelpful
[23:08]  * Ampelbein agrees
[23:09] <Ampelbein> then there should be another bugstatus like resolved-upstream
[23:09] <hggdh> also, it seems that the bugs feed is again dead... no updates on #ubuntu-bugs-announce for the last 2.5 hours or so
[23:09] <hggdh> I agree. If you are willing to go for it, I will join forces. But I will not raise this again alone
[23:09] <Ampelbein> hggdh: you already pinged in #launchpad about that
[23:09] <Ampelbein> ?
[23:10] <hggdh> no, just found it, and I am still to look at the eeebotu logs
[23:10] <Ampelbein> the atom-feed is not updated.
[23:10] <Ampelbein> http://feeds.launchpad.net/ubuntu/latest-bugs.atom
[23:11] <hggdh> yes, but I want to be double-sure
[23:11] <hggdh> #lp, there we go...
[23:11] <charlie-tca> hggdh: bug 319342 get fixed?
[23:11] <ubottu> Launchpad bug 319342 in xchat "xchat dies with a SIGABRT" [Medium,Triaged] https://launchpad.net/bugs/319342
[23:12] <charlie-tca> I haven't seen the SIGABRT in quite a while now.
[23:12] <hggdh> charlie-tca, not to my knowledge -- but I have not experineced it again
[23:12] <charlie-tca> thanks
[23:12] <hggdh> so it may be that it was fixed by an unknown update
[23:13] <charlie-tca> That is what I am thinking. I want to sign it off, but maybe I will wait a week or two yet
[23:13] <Ampelbein> hggdh: i will rise the question on "FixCommited" on bugsquad-mailinglist.
[23:14] <hggdh> Ampelbein, thanks. I will chime in
[23:15] <charlie-tca> me too, again.
[23:16] <hggdh> charlie-tca, I added a comment to the xchat bug stating I will close it in one week
[23:17] <charlie-tca> Thanks
[23:18] <hggdh> Ampelbein, I raised the issue on #lp, so now we wait for someone there to comment
[23:18] <hggdh> (i.e., the feed issue)
[23:21] <hggdh> charlie-tca, back to the correct channel -- it does not matter if you use it or not, some of the PA libraries are depends on a series of pacakges
[23:22] <charlie-tca> Then that could be it. There have been a lot of changes to PA
[23:22] <hggdh> dtchen, bug 319342
[23:22] <ubottu> Error: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/319342/+text)
[23:23] <hggdh> what is going on with LP? or ubottu?
[23:24] <charlie-tca> It works part-time
[23:24] <hggdh> :-)
[23:24] <dtchen> that's not an unknown update, and yes, it's PA-related.
[23:24] <dtchen> it's also linux-related.
[23:25] <hggdh> dtchen, do you have the bug# so that I can put it as a dup?
[23:25] <dtchen> it's not a dupe
[23:26] <dtchen> the precise cause is hw_ptr being erratic (linux)
[23:26] <hggdh> ah, OK
[23:27] <dtchen> that was largely tweaked (but not perfect) in #330814
[23:27] <dtchen> i'm testing building further fixes that will land in a linux SRU
[23:28] <dtchen> i'm pretty sure i fixed the PA side in 0.9.14-0ubuntu11
[23:28] <hggdh> I will, then, add a reference to this bug on the xchat one
[23:30] <hggdh> bug 330814
[23:30] <ubottu> Launchpad bug 330814 in linux "snd_pcm_avail_update() returning absurd values causes PulseAudio to abort" [High,Fix released] https://launchpad.net/bugs/330814
=== asac_ is now known as asac