/srv/irclogs.ubuntu.com/2009/04/14/#ubuntu-bugs.txt

=== Sikon is now known as LucidFox
BUGabundo1andersk: ping14:42
=== stooj_ is now known as StooJ
=== jgoguen_ is now known as jgoguen
BUGabundo1can some one help triage this bug https://bugs.edge.launchpad.net/netbook-remix/+bug/361143/16:52
BUGabundo1thanks16:52
ubottuLaunchpad bug 361143 in netbook-remix "Gnome main menus disappear after changing GUI to "Desktop Classic"" [Undecided,New]16:52
BUGabundo1ogasawara: ping17:10
ogasawaraBUGabundo1: something you need?  it's best to add some context when you ping.17:19
BUGabundo1ogasawara: sorry... got distracted...17:32
BUGabundo1ogasawara: trying to improve the data at bug 35923117:32
ubottuLaunchpad bug 359231 in xorg "system freeze and kernel panic" [Undecided,New] https://launchpad.net/bugs/35923117:32
ogasawaraBUGabundo1: a few questions, have you tried disabling compiz and see if that shows any improvements17:33
ogasawaraBUGabundo1: also, do you recall specifically doing a kernel upgrade prior to getting these panics?  just curious which previous kernel was not problematic17:34
BUGabundo1ogasawara: yes! I'm running it with metacity and NV17:35
BUGabundo1only the latest kernel started happening17:36
BUGabundo1I added the apt change logs17:36
=== maco_ is now known as maco
BUGabundo1bye19:40
=== davmor21 is now known as davmor2
thekornbug 32510121:02
ubottuLaunchpad bug 325101 in wacom-tools "x11 won't start after upgrade to jaunty" [High,Incomplete] https://launchpad.net/bugs/32510121:02
pwnguinthekorn: what about it?21:04
thekornpwnguin, sorry, posting it here was just the easiest way for me to get the url of this bugreport21:05
pwnguinif i could duplicate it, i'd patch it and beat upstream with it21:05
pwnguinbut wacom's been working nicely for me thus far21:06
thekornpwnguin, I'm in a chat with the reporter of bug 359960 and I was wondering if these two are duplicates21:07
ubottuLaunchpad bug 359960 in xorg "xorg segfaults if /etc/hal/fdi/policy/10-wacom.fdi is present" [Undecided,New] https://launchpad.net/bugs/35996021:07
thekornwhich is obviously not true21:07
blueyedCan somebody confirm bug 361275, before I report this upstream, please? (really easy to reproduce, if you have KMail on Jaunty installed)21:15
ubottuLaunchpad bug 361275 in kdepim "KMail composer: Ctrl-Del does not delete next word anymore, if prefixed by whitespace" [Undecided,New] https://launchpad.net/bugs/36127521:15
* e-jat guys .. i think .. i need to offline .. since it already 4.20 am in MY :) .... c u guys later ..21:21
andolRegarding 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:08
ubottuError: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/333620/+text)22:09
Ampelbeinandol: the bugwatches didn't get updated lately.22:12
Ampelbeinandol: 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
andolAmpelbein: Yes, but in this case there is an explicit error message, which has been for a while.22:13
andolAmpelbein: 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
Ampelbeinandol: 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 place22:14
andolAmpelbein: Yes, but isn't that for the upstream task?22:19
Ampelbeinandol: no, it's for the ubuntu-task. the upstream-task watch usually gets updated by the bugwatch. and should be set to "FixReleased"22:20
HammerHead66is anyone else having problems looking at bugs on launch pad?22:39
HammerHead66can anyone see the bugs from the "Bugs" tab?22:41
HammerHead66the only thing I get it my browser keeps acting like it's loading but it never loads anything22:42
=== Flare183_ is now known as Flare183
HammerHead66is anyone alive in this room?22:49
stperenot totally..22:49
HammerHead66stpere: are you able to look at bugs on Launchpad?22:50
AmpelbeinHammerHead66: better place for such questions is #launchpad. and yes, i can view bugs.22:50
hggdhAmpelbein, actually, there has been some discussion about the "fix committed" thingy23:05
Ampelbeinhggdh: oh. what was the outcome? i find it quite handy to see which bugs could be closed by updating version of a package.23:06
hggdhAmpelbein, 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 -proposed23:08
hggdhwhich I find rather unhelpful23:08
* Ampelbein agrees23:08
Ampelbeinthen there should be another bugstatus like resolved-upstream23:09
hggdhalso, it seems that the bugs feed is again dead... no updates on #ubuntu-bugs-announce for the last 2.5 hours or so23:09
hggdhI agree. If you are willing to go for it, I will join forces. But I will not raise this again alone23:09
Ampelbeinhggdh: you already pinged in #launchpad about that23:09
Ampelbein?23:09
hggdhno, just found it, and I am still to look at the eeebotu logs23:10
Ampelbeinthe atom-feed is not updated.23:10
Ampelbeinhttp://feeds.launchpad.net/ubuntu/latest-bugs.atom23:10
hggdhyes, but I want to be double-sure23:11
hggdh#lp, there we go...23:11
charlie-tcahggdh: bug 319342 get fixed?23:11
ubottuLaunchpad bug 319342 in xchat "xchat dies with a SIGABRT" [Medium,Triaged] https://launchpad.net/bugs/31934223:11
charlie-tcaI haven't seen the SIGABRT in quite a while now.23:12
hggdhcharlie-tca, not to my knowledge -- but I have not experineced it again23:12
charlie-tcathanks23:12
hggdhso it may be that it was fixed by an unknown update23:12
charlie-tcaThat is what I am thinking. I want to sign it off, but maybe I will wait a week or two yet23:13
Ampelbeinhggdh: i will rise the question on "FixCommited" on bugsquad-mailinglist.23:13
hggdhAmpelbein, thanks. I will chime in23:14
charlie-tcame too, again.23:15
hggdhcharlie-tca, I added a comment to the xchat bug stating I will close it in one week23:16
charlie-tcaThanks23:17
hggdhAmpelbein, I raised the issue on #lp, so now we wait for someone there to comment23:18
hggdh(i.e., the feed issue)23:18
hggdhcharlie-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 pacakges23:21
charlie-tcaThen that could be it. There have been a lot of changes to PA23:22
hggdhdtchen, bug 31934223:22
ubottuError: Could not parse data returned by Launchpad: timed out (https://launchpad.net/bugs/319342/+text)23:22
hggdhwhat is going on with LP? or ubottu?23:23
charlie-tcaIt works part-time23:24
hggdh:-)23:24
dtchenthat's not an unknown update, and yes, it's PA-related.23:24
dtchenit's also linux-related.23:24
hggdhdtchen, do you have the bug# so that I can put it as a dup?23:25
dtchenit's not a dupe23:25
dtchenthe precise cause is hw_ptr being erratic (linux)23:26
hggdhah, OK23:26
dtchenthat was largely tweaked (but not perfect) in #33081423:27
dtcheni'm testing building further fixes that will land in a linux SRU23:27
dtcheni'm pretty sure i fixed the PA side in 0.9.14-0ubuntu1123:28
hggdhI will, then, add a reference to this bug on the xchat one23:28
hggdhbug 33081423:30
ubottuLaunchpad bug 330814 in linux "snd_pcm_avail_update() returning absurd values causes PulseAudio to abort" [High,Fix released] https://launchpad.net/bugs/33081423:30
=== asac_ is now known as asac

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!