[01:20] <Awsoonn> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/45167
[01:21] <Awsoonn> I am waiting on info, should I set all 3 packages to 'incomplete'?
[01:24] <RAOF> Probably, yes.  On the other hand, I'm pretty sure those bugs _don't_ apply to Hardy - note comment 6: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/45167/comments/6
[01:26] <Awsoonn> indeed, but I just want to confirm. in the case it is fixed, should all three be invalidated?
[01:27] <Awsoonn> with the 'linux' package set to 'Fix Released'?
[01:27] <RAOF> Well, maybe.  I'm not totally sure, honestly.
[01:27] <RAOF> linux -> "Fix released" is most obviously correct.
[01:28] <RAOF> But the problems still exist in the other packages; it's just that Hardy (or Gutsy, or Feisty) no longer have those packages.
[01:28] <Awsoonn> I doubt it would be backported that far afterall.
[01:30] <RAOF> Edgy's out of support, anyway.
[03:44] <josephpiche> I'm not sure if this would be better asked in #ubuntu or here, but just ran into bug 63418 on a fresh 8.04.1 install
[03:44] <josephpiche> even though this bug is marked as fixed
[03:45] <LaserJock> josephpiche: if you really did have the same bug I'd leave a comment on that bug report
[03:45] <LaserJock> it's pretty important to know if we think we've fixed a bug but really didn't get it all
[03:45] <josephpiche> should i also link it to the kernel in hardy?
[03:46] <LaserJock> "link"?
[03:46] <josephpiche> sorry, mark it as affecting 2.6.24
[03:47] <LaserJock> oh hmm
[03:48] <LaserJock> josephpiche: I guess I wouldn't yet, but put it in your comment
[03:49] <LaserJock> I don't know a lot about how the kernel team does triage
[03:49] <josephpiche> okay, thanks
[09:59] <broonie> Is there no facility for wishlist bugs in LP?
[10:00] <RAOF> Yes.  Marking a bug as 'wishlist'.  I think that requires special super-powers, though.
[10:00] <Iulian> Yes, you have to be a member of the Ubuntu Bug Control team.
[10:01] <broonie> Yes, the priority stuff does.
[10:01] <broonie> In that case could someone reopen https://bugs.launchpad.net/bugs/246322 and mark it as wishlist?
[10:01]  * Iulian is looking
[10:01] <broonie> It got closed in triage due to being a wishlist request but it's a perfectly sensible (good, even) idea.
[10:03] <Iulian> broonie: Done.
[10:04] <Iulian> broonie: You don't need any super-powers to change the Status of a bug.
[10:04] <broonie> Iulian: Thanks.
[10:04] <broonie> Iulian: I wanted to check that this wasn't the Ubuntu policy on how to deal with wishlists before doing that.
[10:04] <broonie> Since I'm not a bugsquad member I can't view the available severities.
[10:05] <bliZZardz> w.r.t bug 144492 , does this solicit a backport?
[10:07] <Iulian> broonie: Oh sure, but keep in mind that everyone can change the status of a bug. You don't have to be a member of the bugsquad to do that.
[10:07] <Iulian> broonie: Please have a look at https://wiki.ubuntu.com/Bugs/Importance
[10:13] <broonie> Iulian: Sure, I'm awaer of that - I'd have done that if it were a clear bug rather than wishlist.
[13:35] <thekorn> hi all!
[13:48] <Iulian> Hello thekorn
[13:53] <thekorn> hey Iulian
[14:41] <RainCT> If an upload to hardy-proposed causes some problem, should it be reported as a new bug or be followed up directly in the report about the SRU?
[14:55] <persia> RainCT: Follow up in the SRU while it is still in -proposed.  Once it goes to -updates, in a new bug.
[14:57] <RainCT> persia: thanks
[15:01] <bddebian> Boo
[15:11] <jonpackard> I was trying to set up LTSP with Intrepid and ran into problems.. should this be reported as a bug?
[15:12] <jonpackard> ﻿ltsp-build-client fails with intrepid.. http://pastebin.com/f3341ddcf for details
[15:14] <Iulian> bddebian: b00!
[15:14] <ogra> jonpackard, can you file that as a bug ?
[15:14] <ogra> https://bugs.launchpad.net/ubuntu/+source/ltsp/+filebug
[15:18] <bddebian> Hello Iulian :)
[15:21] <jonpackard> ﻿ogra: Sure. Thanks!
[15:23] <ogra> thanks for filing it :)
[15:35] <jonpackard> Bug 246615 filed. You're welcome. :)
[16:11] <someone_1> Hi! I posted this bug : https://bugs.launchpad.net/ubuntu/+source/pam/+bug/246549
[16:11] <someone_1> can anyone help me with it?
[16:12] <someone_1> well, may be it's more of a problem than bug
[16:12] <someone_1> but I am desperate to fix it
[16:19] <someone_1> anyone?
[16:41] <psyke83> tjaalton, just a quick heads up. The latest upload of the intel drivers in Intrepid doesn't work - it segfaults on some libexa code. I narrowed the problem down to the "force greedy" patch, when I recompiled the driver without it, everything works perfectly. Are you aware of the problem or will I file a bug with logs?
[16:41] <tjaalton> psyke83: fix uploaded
[16:41] <psyke83> tjaalton, awesome, thanks. I thought it'd be best to check with you here before filing a bug
[16:42] <tjaalton> there already was a bug ;)
[16:42] <psyke83> ah, I didn't even look :)
[16:45] <psyke83> tjaalton: I don't know if you've been following, but xserver 1.5 has better exa optimizations and the parameter "ExaOptimizeMigration" is on by default. This makes the "always" migrationheuristic as fast as "greedy" in some cases, apparently. I'm curious if your latest upload still forces "greedy" pixmap migration? It would be ideal to set "greedy" as the default but allow it to be changed in the xorg.conf
[16:46] <tjaalton> it just disables the patch
[16:46] <psyke83> ok, thanks
[17:52] <yuriy> anybody around for kubuntu hug day?
[17:52] <yuriy> LMK if you need something tested on Intrepid
[18:22] <jonpackard> Could anybody please set bug 246067 to "Confirmed"? I reported the bug and two other people have reported they are getting the same results. Thanks in advance! :)
[18:29] <bdmurray> jonpackard: in the event the other commenters have the same panic you could set it to confirmed yourself
[18:35] <gnomefreak> there was a new version of -3 uploaded today maybe late lastnight does this not fix it?
[18:55] <apachelogger> yuriy: apparently everyone thinks we should just dump all KDE 3 bugs ;-)
[18:58] <yuriy> apachelogger: hmm?
[18:58] <yuriy> who is everyone
[18:59] <apachelogger> me :P
[19:20] <jonpackard> ﻿bdmurray: Thanks! I read in the wiki "Do not confirm your own bugs!".. I guess I took that too literally. =)
[19:22] <bdmurray> jonpackard: those other people might not know the process for confirming bug reports
[20:13] <yuriy> hmm 5-a-day seems to be broken here
[20:14] <bdmurray> I'd noticed that too
[20:23]  * yuriy hugs NickNak, thanks for participating!
[20:33] <NickNak> don't mention it!
[22:09] <NickNak> I've just reproduced bug #71273 on both Hardy and Intrepid and it appears to be well described, so could someone mark it as Triaged?
[22:21] <yuriy> NickNak: done
[22:24] <Nightrose> yuriy: 5-a-day is b0rked here as well