[00:03] i cant edit bug statuses from within intrepid. works fine on hardy. anyone else? [00:03] not me [00:04] it does the load-forever-then-blank-page thing [00:04] I'm not familiar with that thing [00:05] does it happen a lot? [00:06] its sort of a timeout, i guess. the +editstatus page just doesn't load sometimes. does't load at all on intrepid [00:06] the vm does reach the internet though. i can get to google. [00:07] the info doesnt get submitted [00:10] Hm I am not familiar with that issue either, maco [00:16] does cups-pdf and printing work for anyone? [00:16] on Intrepid [00:17] hrm ive had hardy do that before, but refreshing usually fixes it, sometimes with a launchpad oops page (in that case, one more refresh, and it submits) [00:22] bug 273912 [00:22] Launchpad bug 273912 in cups "CUPS not printing images" [Undecided,New] https://launchpad.net/bugs/273912 [00:34] restarted firefox, still can't submit changes to bugs [00:34] maco: in a vm? [00:34] I have no issue here using an "on the hardware" install [00:35] greg-g: yeah, in a vm [00:35] the vm doesn't detect that it's online because network manager suddenly decided between reboots that my interface is unmanaged [00:35] but i took ff out of offline mode manually and i can load pages just fine...but can't submit edits on bugs [00:36] i have no idea how to make nm manage the interface again. 0.7 has an all-sorts-of-jacked-up UI [00:37] bdmurray: I just printed a PNG from EOG to PDF just fine. [00:37] maco: kill your edits to interfaces(5), log out and back in [00:38] mrooney: I'm trying to recreate 273912 - firefox to cups-pdf [00:39] bdmurray: cups-pdf is the PDF radiobox option in the "Print to file", right? [00:39] crimsun: i havent edited anything having to do with interfaces [00:40] mrooney: no, it's a separate package [00:40] maco: no idea about that, weird [00:40] mrooney: it makes PDF be an option for what printer to use [00:41] greg-g: ive had it happen on hardy before, at random. intrepid does it constantly :-/ [00:41] maco: reproduce it in an intrepid chroot [00:41] maco: oh, what is the rationale to install that over using Print to File/PDF [00:42] mrooney: easier than remembering to hit Print to File? dunno... [00:42] crimsun: woosh [00:42] maco: come again? [00:42] mrooney: it'll print to ~/PDF ? [00:42] crimsun: over my head [00:42] maco: later. [00:42] bdmurray: hm, ok [00:45] "roviding a PDF printer on the central fileserver" [00:47] mrooney: you dont have to have a real printer configured in order to use it [00:48] you can print without printing! [00:49] but, isn't that what the "Print to File" default printer does?/ [00:49] mrooney: i think you need to have a real printer setup to do that though... [00:49] mrooney: not every app has that [00:49] I thought the PDF printer was removed in Intrepid because the PDF option was added to Print to File [00:49] crimsun: bug 280417 [00:49] Launchpad bug 280417 in network-manager "Network Manager claims devices are unmanaged" [Undecided,Confirmed] https://launchpad.net/bugs/280417 [00:49] crimsun: thatd be the one i was talking about [00:50] james_w: oh I see, things that don't use the native print dialog, perhaps? [00:50] mrooney: hmm, that'd be interesting to try and figure out [00:50] mrooney: yeah, and command line apps I guess. [00:50] pong asac ~ [00:50] hrm, would network manager refusing to use any interfaces be High or Critical? [00:51] mrooney: ah, from main to universe in intrepid [00:51] thanks! [00:51] Awsoonn: hi. [00:51] Awsoonn: i think i said all. i added some info the wiki page :) [00:52] hi there~ right on! [00:52] maco: if you have something in /etc/network/interfaces you could try to set managed=true in /etc/NetworkManager/nm-system-settings.conf [00:52] and killall nm-system-settings :) [00:53] .... uh, ok intrepid + launchpad in my vm is majorly broken. i cant commit to 5-a-day [00:54] maco: and it is only launchpad, no other sites are exhibiting this issue? [00:54] greg-g: google's fine [00:55] maco: try to edit a wikipedia article (just to confirm the act of sending POSTS and such via http) [00:55] facebook's fine [00:55] or ubuntu wiki [00:55] i was able to login to launchpad [00:55] and i can send POST to login to facebook [00:56] dunno [00:56] hmm, seems like a lot of people in Intrepid are getting bug 145360, although someone combined a ton of the dupes into one bug report, I am not sure properly [00:56] Launchpad bug 145360 in compiz "compiz.real crashed with SIGSEGV" [Unknown,Confirmed] https://launchpad.net/bugs/145360 [00:56] asac: set managed=true? where? there's nothing anywhere about managed= anything [00:57] maco: i wrote everything above ;) [00:57] e.g. in which file [00:58] asac: doh missed the in.... part [00:58] if its nm 0.6 then its not applicable. i guessed you are talking about latest NM 0.7 [00:58] yeah, intrepid's NM after the last updates started claiming all devices were unmanaged [01:00] mrooney: could you add that to the release meeting discussion? [01:08] asac: ok that makes NM behave and now 5-a-day works. firefox is still being stupid. [01:08] well, by 5-a-day works, i mean it reaches the server...i have to figure out how this bzr break lock thing works now [01:09] login first, or use bzr+ssh://maco.m@bazaar.launchpad.net/~maco.m/foobarbaz explicitly [01:11] crimsun: oh ok thanks [01:14] crimsun: at some point i need to learn more how this bzr stuff works [01:35] bdmurray: sure, where might I find this, is it a wiki page? [01:35] google and wiki search is unable to help me, apparently [01:37] mrooney: sorry - https://wiki.ubuntu.com/QATeam/ReleaseReports [01:37] actually the page is unmade for this week's meeting [01:37] well I can make it based on the last one [01:37] without those bugs, of course [01:37] thanks! [01:40] bdmurray: it is 10/10, I assume? [01:40] 10-4 [01:40] ;) [01:48] uh oh, and now she lost all internet connection [01:49] she has to eat dinner [01:51] ah, that sounds like a good idea [01:53] oh whoops I did it as 10/10, can you rename a wiki page? [01:54] ...got it. [01:57] bdmurray: wait, what is going on, 10-04 already happened [01:57] a gig of free memory is not enough to analyze the problem and report it to launchpad? Is that what you are saying apport? [01:57] * mrooney head explodes [01:57] mrooney: 10-4 as in "ok" [01:57] or "yes" [01:58] greg-g: oooh, I see! haha [01:58] yep :) [01:58] I think I would have gotten it in any context OTHER than in answer to an early october date [01:58] right, which is why it was a good pun :) [01:59] are lots of people getting bug 280417? [01:59] Launchpad bug 280417 in network-manager "Network Manager claims devices are unmanaged" [Critical,Triaged] https://launchpad.net/bugs/280417 [01:59] it doesn't seem critical otherwise [02:03] all, has the flashplugin-nonfree update that was in intrepid today been backported to hardy? [02:04] since both use FF3 [02:07] i see in packages.ubuntu.com that hardy backports and intrepid main have both a very similar version number for the flashplugin-nonfree package. [02:08] So since its in backports, is it smart to tell the bug reporter to download the backported update, or is there too big of a risk ? [02:11] it shouldn't be much of a risk [02:12] seeing as it should be the same package, if they have very similar versions [02:12] ok [02:12] ty [02:31] Will Bug Triage please set bug #278405 to low priority [02:31] Launchpad bug 278405 in firefox-3.0 "problem in URL form when press ESC" [Undecided,Confirmed] https://launchpad.net/bugs/278405 [02:37] bcurtiswx: done! thanks for confirming. [02:38] mrooney, thanks! [03:03] has anyone noticed that the blank screensaver fades to black and then goes away right when the cursor would normally disappear and blank? [03:03] for example if I set my screensaver to activate after 1 minute of idle, it will fade to black and then pop back to normal right after, once every minute [03:11] yup [03:12] mrooney, yes [03:12] it can be fairly entertaining when you're extremely bored though [03:13] * Hobbsee is sure games exist for that purpose. Try wesnoth. [03:13] haha :P [03:15] hm, I wonder then, if anyone CAN'T confirm it [03:15] I can confrim it, is there a bug? [03:15] :) [03:15] Anyone who doesn't have "unredirect fullscreen windows" enabled won't be able to reproduce it :) [03:16] ah, so I see SOMEONE knows what causes it ;) [03:17] Not so much what causes it, but what triggers it. [03:17] right [03:18] wait, why do I have two screensaver entries in System->Prefs ? [03:18] because one isn't enoguh! [03:19] Could someone please change bug 263560 from 'undecided' to 'wishlist'? [03:19] Launchpad bug 263560 in ubuntu "[needs-packaging] arachnophilia" [Undecided,Confirmed] https://launchpad.net/bugs/263560 [03:21] greg-g: Because xscreensaver got pulled in by recommends again. [03:21] greg-g good question.. me too [03:21] you report, i'll confirm [03:22] Except it's already been reported, and fixed in the last run. [03:22] good [03:22] my fingers are hurtin [03:22] im participating in the hugday [03:22] Also, could someone please change bug 268677 from 'undecided' to 'wishlist'? [03:22] Launchpad bug 268677 in ubuntu "[need-packaging] Evolution Remove Attachments Plugin" [Undecided,Confirmed] https://launchpad.net/bugs/268677 [03:22] Well, it won't actually _fix_ it for you; you'll need to remove xscreensaver yourself. But it will no longer be automatically pulled in. [03:24] Aha! Another! Could someone please change bug 271575 from 'undecided' to 'wishlist'? [03:24] Launchpad bug 271575 in ubuntu "[needs-packaging] Q Light Controller - full featured control DMX512 for stage lighting and devices - Excellent" [Undecided,Confirmed] https://launchpad.net/bugs/271575 [03:26] RAOF: is there already a bug for the screensaver fullscreen redirect issue? [03:26] mrooney: There is indeed. [03:26] Oh. I should check out whether the Compiz ppa packages fix it. [03:28] yeah, so, in simply trying to change my monitor's refresh rate, I have now lost the ability to run compiz [03:28] :( [03:28] Hurray for nvidia? [03:28] RAOF: thanks, removed xscreensaver [03:29] yep [03:30] any magical insights into this issue, RAOF ? [03:30] fairies are good. [03:30] hmmm, now where did I put them? [03:32] ok, brb, restarting, I reinstalled the driver (in jockey, or whatever it is called now) [03:35] Hmmm. bug 177104 is a great wishlist item, but for which package or project? [03:35] Launchpad bug 177104 in ubuntu "Linux, LSB and Ubuntu need a system wide units setting (imperial/metric)" [Undecided,New] https://launchpad.net/bugs/177104 [03:35] that's already been discussed on the ML, sort of [03:36] ok, back, with a happy display again. Thank you nvidia. [03:38] Isn't there alreayd a system wide units setting? [03:38] Sorry, there isn't, is there. Neither should there be! [03:39] SI 4eva! [03:53] RAOF: any link on that bug? :) [04:06] mrooney: The compiz-screensaver bug? [04:06] weird, gnome-do doesn't show anything that's in the application menu :s [04:08] RAOF: yeah [04:08] haha there it goes again [04:09] if you could set your screensaver to less than one minute, it really WOULD be a fun game [04:09] techno_freak: Yeah, that's bug something or other. Updating right now should fix it for you. [04:09] You could watch movies in strobe-light vision. [04:10] RAOF, or should I get it from the PPA? I am trying out on a fresh install of intrepid beta [04:10] techno_freak: Gnome-do? Please test Intrepid's packages. [04:10] RAOF, ok, will try again :) [04:11] You need the new libgnomedesktop2.20-cil; the previous upload was broken(ish). [04:11] Ooooh Gnome-Do works again! [04:15] http://launchpadlibrarian.net/18298913/lp-bug-Guest_Session-annoyingbeep.avi [04:19] bdmurray: Hi, thanks for letting into bug control Brian [04:19] mrooney: You were after the screensaver bug? [04:20] mrooney: bug #278112 is somewhere in the duplicate chain :) [04:20] Launchpad bug 278112 in compiz "Screensaver doesn't start" [Medium,In progress] https://launchpad.net/bugs/278112 [04:20] nullack: no problem sorry for the delay, things are quite busy [04:21] :) [04:22] RAOF, it works now :) [04:23] Well, at least that gnome-desktop-sharp bug clears one thing up: the lack of bugs filed against gnome-do isn't because we don't have any intrepid testers! [04:23] RAOF: gnome-desktop-sharp? [04:23] maco: The package which caused Do to fail to index applications. [04:25] Srill looking for help changing bug 263560, bug 268677, and bug 271575 to 'wishlist' [04:25] Launchpad bug 263560 in ubuntu "[needs-packaging] arachnophilia" [Undecided,Confirmed] https://launchpad.net/bugs/263560 [04:25] Launchpad bug 268677 in ubuntu "[need-packaging] Evolution Remove Attachments Plugin" [Undecided,Confirmed] https://launchpad.net/bugs/268677 [04:25] Launchpad bug 271575 in ubuntu "[needs-packaging] Q Light Controller - full featured control DMX512 for stage lighting and devices - Excellent" [Undecided,Confirmed] https://launchpad.net/bugs/271575 [04:28] RAOF: oh [04:29] bucket529: got 'em [04:44] maco: Thanks [04:50] mrooney: did you submit an update-manager stalled bug? we were talking about it this morning [04:51] nope I didn't make a bug for that [04:54] hmm, I've just had it happen again [04:57] bdmurray: do you think the m-a bugs are worthy of adding as one item to the ReleaseReports, specifically that Pidgin is listed as Gaim and Firefox 3 migrations don't work? [04:59] mrooney: I think there is an ubuntu-releasenotes project you could add a task for it to get someone's opinion [05:05] Interesting, okay [05:06] I just feel like not being able to migrate Firefox 3 bookmarks (when it implies that it can) is kind of a killer at this point of Firefox 3's popularity, relative to Firefox users. [05:09] I think documenting it would be good but it's ultimately up to the release team. Adding the text to the wiki page for them already would be helpful I'm sure. [05:11] bdmurray: okay, and when you say wiki page are you referring to the ReleaseReports page I created, or a different one? [05:12] cant migrate firefox 3 bookmarks? [05:12] what do you mean? [05:18] maco: in migration-assistant, it offers to import things such as Firefox bookmarks [05:18] but importing from Firefox 3 isn't implemented AFAIK [05:18] it was written for Firefox 2 [05:19] mrooney: oh ok. does migration-assistant do migrations from linux yet, or still just windows? [05:21] maco: it does linux and windows, though has more options for Windows generally [05:22] which seems funny since it is basically copying directories from ~/ [05:23] [wishlist] have a migration-assistant option to move ~/.mozilla and ~/.thunderbird-3.0 to ~/Private/. [05:23] I suggested to evand to just copy .mozilla and .purple for the linux migrations [05:23] crimsun: yeah but it doesn't even do that, that belongs more in the dist-upgrade doesn't it [05:24] i need to figure out how to make ~/Private on Hardy so i can avoid intrepid [05:24] even if there was any other big thing i wanted from intrepid, the fact that it kernel panics on my wireless card makes it a no-go [05:26] maco: ouch, I assume you filed a bug? [05:27] mrooney: oh i havent tried it on my hardware. i know about the bug's existence, so i'm staying away [05:27] mrooney: it's the iwlagn causes kernel panic one [05:29] maco: ahh, bug 276990? should probably be confirmed [05:29] Launchpad bug 276990 in linux "iwlagn causes kernel panic on 802.11n wifi" [High,New] https://launchpad.net/bugs/276990 [05:29] comment 7 seems to agree so I'll Confirm [05:31] mrooney: in the known issues section of https://wiki.ubuntu.com/IntrepidIbex/TechnicalOverview [05:33] ahh, great, thanks! [05:33] bdmurray: is bug 276990 something ogasawara should take a peek at? [05:33] Launchpad bug 276990 in linux "iwlagn causes kernel panic on 802.11n wifi" [High,Confirmed] https://launchpad.net/bugs/276990 [05:36] mrooney: it still seems a bit incomplete - I see no log of the kernel panic [05:37] bdmurray: okay, perchance I can take a peek at it more tomorrow [05:37] good night for now! [05:37] I'll keep the tab open too [05:40] bdmurray: how does one log a kernel panic? [05:40] bdmurray: i get kernel panics every few days, but nothing's ever in any log i've seen [05:42] kind of suspect they might be related to hardy's driver for the same hardware [05:42] I was thinking of oopses [05:43] OOPSes will (well, should) be in /var/log/kern.log at the least [05:43] if you're pedantic enough to have a serial console for debugging, you may get more [05:43] crimsun: and a serial port [05:43] also: [05:43] linux-backports-modules-2.6.24-21-generic | 2.6.24-21.27 | hardy-proposed | amd64, i386 [05:44] i dont think my VGA port counts, even if VGA and serial are similarly shaped [05:44] you probably want to give that a twirl for your nic{,s} [05:46] crimsun: will try [05:57] crimsun: libasound2-plugins and then asoundconf set-pulseaudio for flash+PA on intrepid, right? [05:58] bug 263555 [05:58] Launchpad bug 263555 in linux "[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk" [Critical,Fix released] https://launchpad.net/bugs/263555 [05:59] anyone know how to fix eeprom/nvm ? [05:59] even its get fixed in new kernel .. but mine still can make it work .. [06:02] e-jat: you mean you have the damaged rom and want to figure out how to repair it? [06:02] :( [06:03] to i need to flash/update my bios? [06:03] do* [06:04] maco, kind of i think .. coz i can fixed it even upgrade to 2.6.27-6 [06:04] e-jat: maybe? i think there were some reports that bios updates could rewrite the rom, but it's not guaranteed [06:04] you can fixed it? [06:04] nope .. i think if my rom damaged .. how could windows doesnt get any prob with it .. [06:04] im wonder y .. [06:05] ah ok, are you testing with the beta CD or is it installed? [06:05] the beta cd has the driver disabled because it wasnt fixed as of the beta's release [06:05] if you grab a daily cd, the driver is re-enabled [06:06] maco .. i upgrade it since alpha4 [06:09] maco, until now i get this -> http://paste.ubuntu.com/55515/ [06:10] now survive using wifi .. [06:12] someone ? [06:12] dunno === bdmurray changed the topic of #ubuntu-bugs to: Firefox Hug Day! https://wiki.ubuntu.com/UbuntuBugDay/20081009 | Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [07:49] If I triage a hug day big today, is there a tag I should add or something? [07:54] what's the right thing to do on a bug that's ready to expire? [07:54] highvoltage: for 5-a-day? [07:54] highvoltage: or in launchpad? in launchpad, no [07:54] highvoltage: for 5-a-day, it's on the hug day page [07:54] lp [07:55] MTecknology, Generally try harder to triage it. If it's incomplete, and unresponded, and been that way for a long time, it may be that it would benefit from another poke to the submitter. [07:55] MTecknology: i'd prompt them to provide the information requested with a warning that it'd be closed soon if they didn't. then make a note to come back to it and check [07:55] This bug report was marked for expiration 330 days ago. (find out why) [07:56] MTecknology, which bug? [07:56] maco: ok [07:56] but 139562 [07:56] bug* [07:57] I just saw it and wanted to do something to do something - but I wanna make sure I know I'm doing the right thing [08:02] persia: what can I do with that bug? [08:09] MTecknology, I'm really not sure. I'd probably ignore it and leave it for the Ubuntero.org team. Based on their webpage, it seems there's some plan to relaunch in the future differently. [08:10] oh - oops [08:12] I should just give up trying to help with bugs for a while [08:13] MTecknology, No, it's good to help, but it's easier to get good advice from this channel when chasing bugs in Ubuntu :) [08:27] persia: what is the right thing to do with an abandoned bug? say 6 months of no activity about not being able to connect to wireless or something where an update has most likely been released and the issue has a near 0% chance of still being a problem? [08:28] MTecknology, what is its current status? [08:29] Incomplete, marked for expiration for over 150 days [08:30] MTecknology, It depends. If the bug is against a still supported release, it may be valid. Asking for retest with Hardy or Intrepid may be sensible. [08:31] what if it's not valid anymore? [08:31] MTecknology, it is better to ask the reporter(s) to check if the issue still exists in intrepid [08:31] aight [08:32] What if they don't respond to that after a while? [08:34] say, if it expires again? [08:34] MTecknology, the bug is incomplete, so if they dont reply it expires [08:34] MTecknology, If the reporter won't help troubleshoot the bug, and you can't reproduce either in the previous environment, or the current environment, and it's been a couple months, you can set it to invalid. [08:35] persia: oh - invalid bugs make me sad :( I like to assume the problem's been fixed and everybody's happy [08:36] does anything happen to invalid bugs after x days? [08:38] No. They just sit there. I also don't like invalid bugs, but when there's not enough information, and no prospect of getting enough information, it's hard to defend keeping it around. [08:39] I like the idea of saying that new versions were released so i'm marking it to fix released and they can set it back to new if it's still an issue. Then changing it back to new at least has it readdressed - afaik [08:39] just my thought [08:40] MTecknology: well the stock response for invalidating seemingly-abandoned bugs says that they should reopen it if it's still an issue [08:42] maco: so is doing what I said ok? [08:44] MTecknology: as a general rule, dont mark bugs "fix released" unless you can point to the version that had the fix [08:45] otherwise you end up with other triagers going "what the...where did THAT come from????" [08:45] oh [08:45] :( [08:45] so I just need to do invalid and wait for somebody that knows more to clean it up? [08:46] fix released should be accompanied by a comment saying something to the effect "fixed in version _______" [08:46] otherwise do invalid and wait for somebody that knows the version to do it? [08:46] good to ask the reporter if it's still a problem and wait a few weeks before marking invalid if they dont reply or if they say it magically disappeared [08:47] i think "no longer reproducible" is considered "invalid" [08:47] aight [08:47] fix released really is for bugs where we know what happened to fix it [08:47] ok [08:48] Invalid: [08:48] * This status should be used when the bug report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter [08:48] from the wiki [08:48] so magically works now and no idea what was wrong or what fixed it....invalid [08:49] MTecknology, Please don't set anything "Fix Released" unless it's confirmed that one can replicate in an earlier environment, and can no longer replicate in a later environment. [08:50] so when looking at what's fixed etc, the invalid and fix released are pretty much considered the same? [08:50] maco, I disagree : I'm happy to set "Fix Released" for "Magically works now". I only use "Invalid" for "We don't have enough information to consider this a bug report". [08:50] MTecknology, No. Something going from Fix Released to New is a regression, and becomes a concern. Something going from Invalid to New only means we don't understand it yet. [08:51] maco, To expand on that: note that I only set Fix Released for magically works now when I can replicate it in an earlier release, but not in the current release. [08:53] What I meant is, when a person looks at how many bugs still exist, are invalid and fix released considered the same? [08:53] persia: ok yeah, but then you can say "known working in this version" which is different than the reporter saying "magically works now" without anyone knowing what happened or why [08:53] MTecknology: they're considered not to exist, i think [08:53] maco, Oh, certainly :) [08:54] MTecknology, Interesting bugs are New, Incomplete, Confirmed, and Triaged. [08:54] In some rare cases Fix Committed bugs may be interesting, especially the desktop team bugs, but I think that's a misuse of the status value. [08:55] invalid are considered not-a-bug, won't-fix is kind of "yeah, it could be considered a bug depending on your workflow, but this is a design decision" and "fix released" is "it was a bug, but it works now, so we don't have to think about it anymore" [08:55] ok :) [08:55] "design decision" is the only reason i can think of for "won't fix" [08:55] makes perfectly clear sense now :) [08:56] thanks for helping me out :) [08:56] is there any other? [08:56] persia: ? [08:56] nap time - 3am and class soon [08:56] macd__, Certainly. Lots. [08:56] boo tab complete! [08:57] I can think of a couple reasons, where i workd (microsoft type company) won't fix also meant "we don't care" [08:57] Say someone wants something where there's a licensing issue, or something where upstream protests strongly, or something where Ubuntu just doesn't have resources to do it. [08:57] (an example of the latter might be : Please include a local cache of the entire internet in firefox) [08:57] .... O_o [08:57] * macd__ mutters like libgems ... [08:58] macd__: sorry, s/he meant to ping me [08:58] MTecknology, "We don't care" is best expressed as "Confirmed" for > 1 year. [08:58] If anyone really wanted to fix it, they'd submit a patch. [08:58] persia: or triaged > 1 yaar [08:58] maco, I know, I just felt the urge to drop my 2 cents too [08:58] macd__: happens a lot, i know [08:58] maco, Sure. I don't meaningfully distinguish Confirmed from Triaged for most bugs. [08:58] or include ubuntu-restricted-extras in standard install ?? [08:59] persia: given the tons of triaged-with-patch-but-not-committed bugs.... [08:59] MTecknology: yeah... [08:59] maco I just realized you are macogw ;) that was the other one that got me all the time [08:59] persia: i saw a bug today and wanted to mark it won't fix [08:59] macd__: yes, that's me [08:59] maco, Which bug? [09:00] persia: crimsun said leave it as "new" ...they didnt like upstream gimp's design decision to have the empty window [09:00] Oh, yeah, it's not worth having an argument about that. [09:00] bug 280384 [09:00] Launchpad bug 280384 in gimp "Please make X button mean Quit in Gimp when a file is still open" [Wishlist,New] https://launchpad.net/bugs/280384 [09:00] "Won't Fix" is only useful when you're 100% certain that it shouldn't be done, and you're willing to argue the case. [09:00] Ubuntu "6206 incomplete bugs can expire" I wanna mark every one over 90 days old as invalid if there hasn't been anything about I'll try this in intrepid or somthing... [09:01] MTecknology: you could try to reproduce them in intrepid first [09:01] MTecknology: but i did spend a few days combing through old bugs one day about 2 months ago [09:01] MTecknology, Please give each of them another triage swing before marking invalid. Some may have open questions unanswered, and can be invalidated, but others may just not have gotten a look after the reported answered a question. [09:01] I can't wait to install it. I keep doing things from a like cd so I haven't gone to it yet [09:02] MTecknology: ive got an intrepid vm open [09:02] im doing my bug work in there now. [09:02] still have irssi in the hardy host though [09:02] what does triage mean? [09:02] MTecknology: ever watch ER? [09:02] MTecknology, It's close enough that if you're not using it for production purposes, and you've a willingness to chase bugs, it's probably OK to upgrade. [09:02] I used to think that meant "we're working on it" [09:02] !triage [09:02] Sorry, I don't know anything about triage [09:02] Bother. [09:02] MTecknology: it means figure out what the heck's wrong with it [09:03] get all the information and make a diagnosis [09:03] Any hints how I can debug this bug #278029 [09:03] Well, rather to get a rough idea, and sort things that need immediate attention, things that can wait a bit, and things that don't matter so much or can be fixed trivially. [09:03] Launchpad bug 278029 in nvidia-graphics-drivers-177 "Xserver crashes, scrambled terminals random lines and patterns (dup-of: 270617)" [Undecided,New] https://launchpad.net/bugs/278029 [09:03] Launchpad bug 270617 in nvidia-graphics-drivers-177 "Display corruption after short period" [Undecided,Confirmed] https://launchpad.net/bugs/270617 [09:03] that's what nurses do. then they get the doctors to actually fix it. the devs are the doctors in this case [09:03] meaning "ok let's try to figure this bad boy out" ? [09:04] sounds good - always was a foreign word until now [09:04] the "Triaged" status means there's enough there to fix it (or even a patch there that is known to work) and now just need to get someone with upload rights to take the patch or a developer to make a patch from all the gathered info [09:05] persia: My servers will stay lts, but my laptop will upgrade - maybe my home desktop/server too [09:05] unfortunately, there's this silly rule that we need a debdiff of all the patches, which means all of us that can work C but go O_O when told to try packaging have our patches ignored [09:06] wow - fun [09:06] screw me trying to do that :P [09:06] kernel accepts git changesets though :D no silly debdiff requirement [09:06] maco, There's no such rule, it's just that the sponsors won't sponsor stuff that's not debdiffs. [09:06] Arbitrary packagers might. [09:07]