[00:38] Found a workaround.... [00:38] pci=nomsi [00:39] I am not into kernel options or hardware much so I don't really know how it will impact my system... [00:39] but it works at least [00:47] hi [00:47] hi [00:47] is the bug in gedit fixed or in Snipets plugin? [00:48] you most manual add shortcut for tags list [00:48] zyx386, do you know what number it was? [00:48] wait [00:51] 136876 [00:51] bug #136876 [00:51] Launchpad bug 136876 in gedit "Snippets plugin doesn't work" [Medium,Fix released] https://launchpad.net/bugs/136876 [00:52] isnot fixed [00:52] that worked no more [00:52] http://www.youtube.com/watch?v=yuAR6NxiEgQ [00:53] you most add manual the shortcute [00:53] zyx386, are you using gutsy or hardy? [00:53] hardy [00:54] is it the same bug? I have no idea how that is supposed to work [00:54] i report new bug [00:55] zyx386, okay. I do not know the program so I cannot say if you have the same bug [01:02] i do it :) [01:02] bug #228006 [01:02] Launchpad bug 228006 in gedit "Snippets plugin manager dos't Work more in Hardy" [Undecided,New] https://launchpad.net/bugs/228006 === jjesse_ is now known as jjesse [03:35] bug 478135 [03:35] bug #478135 [03:35] secretlondon, thanks [03:35] uhm, probably it is not on lp? [03:35] waits for the bot.. [03:36] not one of our bugs? [03:36] trying to update util-linux apt-listbugs lists two bugs on it [03:36] #478135 - util-linux: CVE-2008-1926 argument injection passed to audit (Fixed: util-linux/2.13.1.1-1) [03:36] #479131 - util-linux: hwclock always uses UTC regardless of the config in /etc/default/rcS [03:36] I don't know where they are reported [03:37] I think ubottu should have responded even if it's not our bug [03:39] for all util-linux bugs: https://bugs.launchpad.net/ubuntu/+source/util-linux/ [03:40] debian bug for the first one [03:40] http://groups.google.se/group/linux.debian.bugs.rc/browse_thread/thread/157a0f5c82bba92d?fwc=1 [03:40] and for the second (found via google) [03:41] http://news.gmane.org/group/gmane.linux.debian.devel.bugs.general/last=/force_load=t [03:41] ah yeah, they aren't in Launchpad [03:41] thanks secretlondon, I wonder if ubuntu package is affected too, probably it is not [03:42] for the first one with the cve we should def check [03:44] we have a list of cve bugs [03:45] according to http://security-tracker.debian.net/tracker/CVE-2008-1926 it was fixed in 2.13.1-3, we have -5 [03:46] wait, that might be wrong... [03:47] sid has 2.13.1.1-1, hardy-updates has 2.13.1-5ubuntu2 [03:47] http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=commitdiff_plain;h=8ccf0b253ac0f4f58d64bc9674de18bff5a88782 [03:48] to verify the problem try to login appending addr=xyz.com [03:50] our package doesn't seem to be affected [03:52] good deal === asac_ is now known as asac [06:55] How might I further triage https://bugs.launchpad.net/php/+bug/218891 [06:55] Launchpad bug 218891 in php5 "converting some doubles to strings yields trailing colon" [Undecided,Confirmed] [07:37] rpedro_: I've tried forwarding bug 117382 upstream - am I doing it right? [07:37] Launchpad bug 117382 in gnome-user-docs "Usability of 'Manually Mounting and Unmounting File Systems'" [Undecided,Confirmed] https://launchpad.net/bugs/117382 [07:41] ligemeget: I'm probably not the person your looking for? :) [07:41] Damn, where's the other Pedro, then? :) [07:42] Oops, I was looking for pedro_ :D [07:47] Q: What to do with a bug like bug 152657 ? [07:47] Launchpad bug 152657 in gnome-user-docs "Introduction to the Desktop" [Undecided,New] https://launchpad.net/bugs/152657 [07:56] anyone? [07:58] hej awen_ [07:59] hey ligemeget [09:31] james_w, i do all the merges with my name next to it on merges.ubuntu.com, so yes, i did tuxpaint, sadly there is some mess with the .desktop file i need to clean up to fix a ftbfs [09:32] ogra: cool, thanks. [09:33] i actually wanted to ask secretlondon if she has anythink that i consider for SRU in hardy for the tux* stuff (she'S so deep into it :) i trust her more with these packages than myself ) [09:33] *that i should consider [09:44] good morning, bug squishers [09:44] morning [09:44] I'd like to convert https://answers.launchpad.net/ubuntu/+question/4272 to a bug... any suggestions? [09:45] is that a kernel issue? [09:46] wolfger: looks like one to me, but I'm no kernel expert.# [09:46] looks like the sort of thing that may already have a bug reported, I don't know. [09:49] wolfger: USB support kind of sucks, I mean generally [09:49] I know you're looking for a decision on whether it's a kernel bug or not [09:49] In my experience, this is most definitely a kernel bug, or malfunctioning hardware [09:49] it doesn't look like user error to me [09:50] so, rule out hardware error first [09:51] well, the same hardware worked for me on Gutsy [09:51] wolfger: one particular USB keyboard I own on a certain USB powered hub, will cause these messages on my own computer [09:51] only after upgrading to hardy did I have this issue [09:51] it only happened since a kernel update sometime last year [09:51] also for me, my media reader stopped working completely since a kernel update 2 years ago [09:52] I've been too lazy to follow up with LKML about this [09:52] and my issue is slightly different from the one in the question, but the same solution fixed me, so... same issue [09:52] yeah [09:52] what you'd have to do is find the regression [09:52] I don't think another person will do that work for you [09:52] I should probably search for an existing bug on this, though. there probably is one [09:53] alright, thanks === Great_Briton_ is now known as Great_Briton [10:50] morning [10:51] tach afflux === thekorn_ is now known as thekorn [11:00] hello [11:03] morning qense and thekorn [11:03] hey qense [11:06] is hardy doing well? (low number of critical bugs?) [11:15] I didn't hear much complaints from my friends, except that one onboard network card just doesn't work. === janet is now known as pschulz01 === fdd-0 is now known as fdd [13:36] hey folks today is hug day so feel free to grab any bug out the list: https://wiki.ubuntu.com/UbuntuBugDay/20080508 === sectech_ is now known as sectech [14:05] is someone around that can review a bug for me? bug#227397... I am currently triaging it and I'm not sure what package to assign it to... [14:05] It has nothing to do with the title, I am changing that now [14:28] sectech: use bug 227397 so that ubottu can give us the link [14:28] Launchpad bug 227397 in ubuntu "Display windows are not being rendereded with the correct colors" [Undecided,Incomplete] https://launchpad.net/bugs/227397 [14:28] sorry about that. [14:30] norsetto, I won't know until the reporter answers the latest questions I posted but this looks like it could be directly related to the nvidia non-free driver... In which case we really can't do too much about. [14:30] it [14:31] sectech: we can report it upstream though [14:32] norsetto, if it does seem like it is the case is there anything special I need to do to report it upsteam (I am a new bug triager) [14:33] sectech: just check if there is a similar bug uupstream already (or in Debian if applicable), if not report it in the upstream bug tracker and link it to the LP bug report [14:34] Okay I'll start with Debian and see if there is anything there [14:36] Hi bugsquad [14:37] could someone at bugcontrol switch importance of bug 159362 to wishlist. Thanks [14:37] Launchpad bug 159362 in network-manager "Selecting WIRED network does not turn off WIRELESS RADIO" [Undecided,Confirmed] https://launchpad.net/bugs/159362 [14:38] I can do that :) [14:39] norsetto, I don't see anything similar in debian... I can report it there if it's appropriate though? [14:39] sectech: no need in this case [14:40] norsetto, I can't assign it to nvidia though in Ubuntu... [14:40] and right now I removed the assignment because it isn't an openoffice problem [14:41] sectech: that would be restricted-drivers [14:41] ahhh thank you! [14:44] Anybody working on the evolution-alarm-notify bug? [14:44] I have some info that might help [14:46] norsetto, I assigned it to linux-restricted-modules-2.6.24 [14:54] don't forget the hug day https://wiki.ubuntu.com/UbuntuBugDay/20080508 :-) [14:54] Hey indeed... today is a hug day [14:56] pedro_, I don't think I have access to make the changes to hug a bug, do I? [14:56] sectech: you need to login first :-) [14:56] I am logged in... lol [14:56] everybody with a lp account is able to make changes to that wiki page [14:57] maybe someone else is writing on it [14:58] come on wiki, don't die on me. [14:58] haha [14:58] I might follow a few bugs to see how other triagers work before I make any major changes.... [14:58] sectech: editmoin is a pretty good tool for edit the wiki pages [15:00] * Hobbsee asks if https://wiki.ubuntu.com/Bugs/HowToTriage#head-89f23324471028da4ff2dc496f0bdd299d72c093 in general makes sense to people [15:00] pedro_, I might be a little too new to this.... at the moment I have to be very selective on which bugs to triage just because of lack of experience.... Some I can triage with no problems, others I don't know what to ask for sometimes. [15:02] I have picked up a lot though over the few days I have been doing this... [15:02] that's totally ok :-) [15:02] It will be a while before I start asking for access to mark bugs as triaged myself ;) [15:03] Hobbsee: How about "Please promote to " and "Please demote to "? [15:03] persia: ahhh, good. [15:03] persia: what's the mir team name? [15:03] ubuntu-mir? [15:03] https://launchpad.net/~ubuntu-mir [15:04] Hobbsee: nice. Thanks for doing that. [15:05] james_w: no problem. that should stop people fiddling with thsoe bugs, i hope. [15:05] Hi, I games like supertux2, chromium and fishfillets hang when I try to shut them down. [15:05] It at least provides a reference regarding the issue, as opposed to the previous assumption that it would be understood by osmosis. [15:06] They also consume a lot of cpu then, also a game written with pygame hangs on shutdown as well. [15:06] Balachmar: can you get an strace of the apps? [15:06] james_w: How would I do that? [15:06] Balachmar: if you have one hanging now then you need to open a terminal, and run "ps aux | grep " [15:07] persia: well, yeah. it was always supposed to be fixed. [15:07] Balachmar: note the number in the second column of the row that corresponds to the game [15:07] Balachmar: and then run "strace -o dump.txt -p " [15:08] Balachmar: you can then put "dump.txt" in a pastebin [15:08] Is there a wiki on how to setup your system for bug testing? I just bought a new sata drive yesterday just so I could have some VM's going for this.... [15:08] I'll be setting them up today [15:08] ran into some stupid sata error yesterday... easy work around though [15:09] It says interupt to quit, should I kill the proces now? [15:09] or rather fix not work around [15:09] Balachmar: yup, should be enough. If it's not you can run the process from the start under strace. [15:10] this is the trace: http://pastebin.com/m731069d1 [15:10] Not much in there [15:11] yup, not too helpful as we don't know what that futex is. [15:11] Balachmar: can you please run "strace -o dump.txt " and then quit and kill it after a few seconds of hanging [15:11] Balachmar: not that it will run a lot slower like this [15:12] Boo [15:16] james_w: hmmm it seems that if I run them from the terminal that they are not as likely to hang... [15:17] james_w: that assumption was wrong :) [15:19] james_w: the whole dump is too long for pastbin [15:19] whould I just send the last bit? [15:20] Balachmar: yeah, start with the last bit, it may be enough. [15:22] james_w: http://pastebin.com/m7fdb6ad8 [15:23] Balachmar: that's still not enough to say really [15:24] Balachmar: can you run "grep b63e1bd8 dump.txt > dump2.txt" and pastebin the second file please? [15:25] james_w: http://pastebin.com/d541b0930 [15:25] Balachmar: thanks. [15:26] Can you try the strace command again, this time with "-f" as well? [15:26] Well, you are helping me out :) [15:26] sure [15:26] it tells it to follow children as well, and it looks like it might be a problem in a child. [15:26] the last bit of the trace will hopefully all that is needed from this one. [15:27] so I don't need to do the grep stuff [15:28] http://pastebin.com/m3be4c4aa [15:30] james_w: It only happens if I close the window with the cross instead of the quit game option [15:31] Balachmar: ok, so this time we need to grep for " = 5", would you do that please? It might be a lot more lines this time though, but we are looking for a particular one, so I may need to see them all. [15:31] If it is loads then we can probably trim it down though. [15:31] Balachmar: that's interesting. Is there some similarity in these games, you mentioned pygame, do all of the games use that? [15:32] I don't know, the ones I am experiencing problems with so far are: Chromium, supertux2, fishfillets and my own, but that is still in development === thekorn_ is now known as thekorn [15:33] mvo_: is ther ean easy way to lock a package version with apt. i did it with synaptic but it doesnt apply to apt it seems [15:33] http://pastebin.com/m641a83d2 [15:35] james_w: Actually with fish fillets it does end nicely with the cross, but not with the in game option... [15:36] Balachmar: there's not enough there I'm afraid, can you email me the trace? [15:37] * DShepherd is now bug man [15:37] the last one, and then the full version? ofcourse [15:37] I want the one you created with -f please [15:38] yes, I meant that one [15:40] https://wiki.ubuntu.com/Bugs/Responses -- is it ok if i use these as a guideline in responding to bug reports? [15:40] james_w: it is 34 MB... [15:40] DShepherd, that's what I was told to use [15:40] sectech, i guess that is a yes then :-) [15:41] sectech, thanks [15:41] * DShepherd calls on the power of ten bug-men! [15:41] I'll put it online and send you the link [15:41] Balachmar: that works too. Feel free to compress it [15:42] *slams himself on the head* compress it, smart thinking! [15:44] james_w: you've got mail... [15:45] why, yes I do, thank you. [15:47] james_w: Well, thank you! I have to go now, but I will be back. Or you can always mail me for more info [15:47] sure, ping me when you're back [15:48] it won't be today though... [15:49] no problem [15:49] Well, thanks for the help, bye [16:23] Hey [16:27] hey [16:27] Hi DShepherd [16:28] Hi Iulian [16:28] no boo? [16:38] anyone know what's going on here? http://bobthegnome.blogspot.com/2008/05/apportbug-buddy-disabled-in-ubuntu-804.html [16:39] I didn't think bug-buddy would be active on any Ubuntu systems. [16:45] hi. may i know when a bug has a strace attached and the way to reproduce the bug is stated, what should its status be? [16:48] ruiboon: that depends on other things [16:48] ruiboon: probably New or Confirmed, depending on whether anyone else has seen it yet. [16:48] ruiboon: do you have a bug number so that I can have a look? [16:49] https://bugs.launchpad.net/ubuntu/+source/roxterm/+bug/227685 [16:49] Launchpad bug 227685 in roxterm "Segmentation fault when started with the --directory option" [Undecided,Incomplete] [16:49] james_w: i have tagged it as incomplete at first as there was not enough information. [16:50] james_w: but i am not sure of what to do now since there is a strace file attached. [16:51] james_w: the submitter is also not using the latest version of the program. should we ask him to update it? [16:51] ruiboon: what we really want is a backtrace [16:51] it appears to be the most recent to me, 1.8.0-1 [16:52] james_w: erm... the latest release at the left side of the launchpad page seems to mention that it is 1.11.1-1 [16:53] james_w: will ask the submitter for a copy of the backtrace [16:54] !newpackage | Belisarivs [16:54] Belisarivs: The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [16:54] ruiboon: that's probably intrepid, [16:54] ruiboon: I'd keep it as incomplete until they can provide a backtrace [16:54] https://wiki.ubuntu.com/Backtrace [16:54] https://wiki.ubuntu.com/DebuggingProgramCrash [16:54] are the two links that are useful there. [16:55] james_w: ok. [16:55] james_w: Thanks for your help! [16:55] no problem. [17:02] * Hobbsee fumes [17:02] james_w: wiki edit reverted :( [17:02] james_w: so you'll just have to guess over what you're supposed to do, or not. [17:03] Hobbsee: why? [17:03] james_w: see the ubuntu-bugs ML. [17:04] Hobbsee: ah, I see. That's a shame. [17:04] james_w: a shame is one phrase for it. that wasn't the one i was thinking of. [17:06] hi all [17:06] hi thekorn [17:06] hey james_w [17:06] Hello thekorn [17:06] and Iulian [17:07] * Hobbsee wasn't aware that missing documentation now required going through a canonical QA review. [17:07] seeing as most people are following it anyway, and all. [17:08] * Hobbsee is sure heno will do well in finding all the solutions at UDS, with those who go. [17:08] <_stink_> is the ubuntu-bugs ML archived anywhere? https://lists.ubuntu.com/archives/ubuntu-bugs/ only shows months up to March 2007, and many/all of the directories are empty anyway. [17:09] Hobbsee: you are welcome to participate by phone [17:09] heno: at very early hours of the morning, yes. [17:11] _stink_: it should be, I'm not sure if it has fallen behind for some reason. [17:15] * Hobbsee also thought that the 'discussion' had moved onto triaging tools to make it easier for triagers, with the greasemonkey scripts, and wasn't talking about policy anymore. [17:15] apparently not. [17:25] _stink_: no, they're not because the bugs are also in Launchpad and there were disk space issues IIRC with the archives. but the mailing list we were talking about isn't ubuntu-bugs, but ubuntu-bugsquad [17:28] heno: btw, https://blueprints.edge.launchpad.net/soyuz/+spec/sync-workflows should remove the need of using the bug tracker for syncs... except for those people needing sponsorship, but those are very few I believe and we could look at some other way to track them [17:29] pochu: what about merges / removals / everything else listed there? [17:29] Hobbsee: we could change the policy of the involved teams to assign those bugs to those teams [17:30] if that's appropriate... [17:30] I can't see why not, but I guess there may be a reason why that's not the case right now :) [17:30] pochu: there are reasons. [17:31] There needs to be some better process than just 'stay away from of bug types' [17:31] that way the policy change is minor (s/subscribe/assign/g) [17:31] pochu: mainly being that a particular member actually does the merge, etc, nto someone in the group, so it's easier to track that way. [17:31] heno: well, people have mentioned if the bug has an assignee or is InProgress, the bugs won't be listen in the triagers searches, so assigning the teams which will need to approve/reject/do the work sounds like a possible solution to me [17:32] pochu: so, you really can't say "someone in the group is working on this, (like, the contributor), but we need the release team to be subscribed, to give an ack. [17:32] at teh end of the day, the contributor is responsible for the bug, once they have their ack. [17:32] ah, I see the case for the release team [17:32] pochu: sponsorship teams are similar. [17:32] I was mostly thinking in u-u-s/u-m-s [17:33] pochu: mir's are also similar. [17:33] pochu: I agree that could work [17:33] well, in that case then the team is subscribed, there's a debdiff attached [17:33] and for mirs, the mir team is actually doing the work [17:33] sometimes. depends if it's been bumped back for more info, but i see your point. [17:33] do any of the teams use a status change in their work? [17:33] so assigning the bug to them sounds reasonably to me (I don't know what the team members would think though) [17:33] they do the final override. [17:34] pochu: it breaks filters and doc and stuff, every time you change the workflow. [17:34] sure, I know... but not switching it will mean we won't solve this issue [17:34] so there's a need to fix this, one way or another [17:35] this is not 'lets change the policy for the sake of changing it!' :) [17:35] pochu: also, it breaks the sponsorship case where people rely on email only, and so think, once the team has been unsubscribed (that the team is no longer the assignee), that there's been no progress on the bug - whereas that's not the case - it's a sponsor that has taken it out of the queue, and has done it. [17:35] pochu: these are the main reasons for subscription, which is, in fact, more painful than an assignee (more screens). [17:36] <_stink_> pochu: thanks for the mailing list info [17:36] heno: would the list really grow that large? [17:37] Hobbsee: not everything is covered by that list though unfortunately. [17:37] Hobbsee: sorry, I didn't understand how it breaks the sponsorship case... I'm no native speaker :( [17:37] Hobbsee: don't know, but it has been growing since the discussion started [17:38] there was a case the other day where a developer had filed a quick report on friday so they could attach a debdiff and apply for an SRU on monday, and over the weekend there was nothing to indicate that it was going to be an SRU bug [17:38] pochu: some people process the queue only by email. [17:38] oh [17:38] pochu: assigning a team, instead of subscribing them, breaks. [17:38] pochu: saves launchpad loads, etc. [17:38] so, while we use bug reports for this sort of thing we are probably always going to have some cases where it is not obvious. [17:39] james_w: true. i guess you're relying on the fact that a triager probably won't find your particular bug, in a stream of otherwise important bugs. [17:39] so you mean that since the team would still be assigned even if the bug is 'Incomplete', the ML would still receive mean which should mean that the bug needs sponsorship, were actually it means the bug needs more work in that specific case? [17:39] surely sponsorship requests would be 'In progress' or at least Triaged [17:39] pochu: no, if the assignee would be changed to be who was actually uploading it, i presume. seeing as they're responsible now. [17:40] pochu: which would stop the bugmail to the team for that bug. [17:40] heno: except when the sponsor asks the contributor to fix some things or change others... [17:40] Hobbsee: yep, or make it clear what you are doing, or set an appropriate status. [17:40] james_w: i like triaged for that. it speaks of "leave my bugs alone, i'm in -qa" [17:40] hi secretlondon [17:40] (whether it's actually triaged or not, if people aren't supposed to modify it) [17:40] hi james [17:41] hi james_w [17:41] But if it's being worked on at that level the problem itself is generally understood, so at least Triaged [17:41] Hobbsee: ah, right, then we are good? [17:41] heno: bugsquaders were still picking off triaged bugs, afaik. [17:41] Hobbsee: yeah, I think triaged would be fine. We have to rely on developers to set it in that case, but it would work fine. [17:41] secretlondon: ogra was wondering if you knew of any tuxpaint related bugs that would be worthy of an SRU in to hardy. [17:41] Hobbsee: interesting. examples? [17:42] heno: people setting the wishlist flag on sync requests. [17:42] * ogra waves to secretlondon [17:42] triagers should tend to focus on the New -> Triaged region [17:42] i think that some of them may have been motu hopefulls, but i don't think they all were. [17:42] james_w not really, we are two versions behind anyway [17:42] * secretlondon waves at ogra [17:43] james_w and I caught them before freeze anyway [17:43] secretlondon: great, nice work. [17:43] great :) [17:43] asking triagers to generally not modify Triaged state bugs sounds like sensible policy [17:43] Hobbsee: I'm not trying to be argumentative, but does the wishlist flag for a sync request affect the workflow, or is it just noise for those subscribed? [17:44] but asking them to not touch New bugs doesn't IMO [17:44] james_w: it's needless noise. [17:44] Hobbsee: yep [17:45] heno: that's going to lead to abuse of triaged, though, where the bug does require more information. [17:45] heno: obviously, the mir team, archive teams, etc, are only going to look at triaged and above [17:45] that sounds like an LP email handling or filtering problem (the noise) [17:45] heno: how do you then propose to differentiate between triaged-so-bug-squad-leaves-it-alone-but-not-ready-yet, and triaged-has-all-information? [17:46] Hobbsee: abuse how? It can only be set by bug-control who should read the triage docs [17:46] heno: by the developers filing workflow bugs, going "please leave this alone" [17:46] Hobbsee: why should those be different? [17:47] heno: to the triagers? they shouldn't. to the archive admins, and those who are processing the bugs if they're in a ready state? htey do. [17:47] that's not an appropriate use of the bug tracking system IMO [17:47] heno: so, what do you propose as a way of saying "leave this alone", which doesn't involve a tag? [17:48] seeing as your last proposal was "set it as triaged", afaik. [17:48] Triaged, In Progress or Wishlist [17:48] granted. [17:48] but the question still stands. [17:48] ok, so we are agreed :) [17:49] what question? [17:49] [02:48] heno: so, what do you propose as a way of saying "leave this alone", which doesn't involve a tag? [17:49] Triaged, In Progress or Wishlist [17:49] oh, you're saying to stick all bugs as in progress, if we don't want bugsquad to touch them [17:49] may i know why the use of tags are not preferred? [17:49] if it needs more info that can go in the description [17:50] Hobbsee: yes [17:50] ruiboon: because they suck, they add to the tag cloud, and it requires yet another screen to actually add them. in addition, you can't add tags while filing a bug, on the standard form. [17:50] Hello all, I have a process (pidgin/14629) that takes all CPU available, seems to ignore SIGTERM, SIGKILL, and which I don't see the window on X. [17:50] When it happened I had firefox and virtualbox opened, since I suppose there is a bug somewhere I didn't stop virtualbox in order to get more information. [17:50] I come to you because `gcore 14629` with sudo says "ptrace: Operation not permitted." [17:50] This is the output of `ps -f 14629` : [17:50] UID PID PPID C STIME TTY STAT TIME CMD [17:50] gautier 14629 1 29 08:54 ? Dl 161:59 pidgin [17:50] (I use Ubuntu 8.04, with linux 2.6.24-16-generic). [17:50] because it's easier to educate a smaller group [17:51] and we are talking about the fringe exception cases here [17:52] * Hobbsee fails to see how a sync request being thrown back, so set to 'in progress' is a valid use of that state, either. [17:52] or merge or removal request, or anything else. [17:52] Hobbsee: i see the issue [17:53] because it may well not *be* in progress, if the OP does not do anything about it. [17:53] These workflow tickets are not bugs. If they are going to live in the bugtracker anyway they must be adjusted to coexist peacefully with the bulk use case of the tracker [17:53] and surely, if it's thrown back, the OP should be the one sayign "i'm working on this now, or real soon now", not whoever threw it back. [17:54] not teach the whole world to take special consideration of these non-bugs [17:55] heno: i presume you have a better place that they should go. [17:56] heno: and, i presume you don't mean that as soon as something si a debdiff, it no longer is a bug, but a workflow ticket, and so should be in that better place, too.... [17:56] Hobbsee: no. but I can live with Triaged, In Progress or Wishlist [17:57] heno: what do you think about putting the team/person working on the bug as the assignee? would that work for the bugsquad? [17:57] debdiff should never be New right? [17:57] pochu: probably [17:57] no [17:57] but it may well be incomplete, if it's wrong, and requires more info. [17:58] nor is it legitimately a wishlist either, as it fixes a bug, so is not a wish, imo. [17:58] so it needs more triage ... [17:58] not by bugsquad, though. [17:58] unless a requirement of bugsquad is to contribute code fixes too now. [17:59] asking again for the requested info is valid triage [17:59] which the sponsor has already done, no? [18:00] oh, presumably this falls in the newfangled "requested info, no response" thing. [18:02] it's not new [18:04] newish. [18:05] it's since the "launchpad took upwards of 40 seconds to load, so i didn't do much bugwork in it, and turned more to email", so classes as new in my books :) [18:09] In my opinion all this problems can be easily solved by adding an option to launchpad to restrict the write-access to bug tasks [18:11] thekorn: but that would only work for SRUs, not for sync/merges/mirs/removals/etc... [18:11] thekorn: i was thinking an "i know what i'm doing" checkbox. [18:11] but yes [18:11] since those don't have stable tasks [18:12] I guess that checkbox won't actually work [18:13] since either you make it public to everyone, in which case it will be abused, or you restrict it to some special team, in which case people needing sponsor teams may not have access to it [18:13]