[00:55] * bkerensa thinks blueyed might be able to help me sort it or greg-g [00:55] :D [01:49] I found a bug, but not sure which package it should go against nor how to determine which package... I suspect the calendar component of the panel [01:50] the issue is that if I double click a specific date Evolution opens up but goes to 1970 instead of the date clicked [01:50] if I say add event it comes up today's date which is normal... so it would appear information is being sent incorrectly from the double-click [01:50] any hints on how to narrow that down or report it? [02:20] cprofitt: Could run system monitor and see what is running and not idle [02:20] to narrow it down [02:20] bkerensa: good suggestion [02:21] cprofitt: I'm hoping bdmurray might be able to figure out the Boinc bug or pass it upstream... [02:22] Boinc? [02:23] yeah [02:23] distributed computing platform used by 400-500 Team Ubuntu Distributed Computing people [02:23] :P [02:24] yeah that would be important [02:26] bkerensa: do you have any links to the previous fixes for that bug? [04:39] bdmurray: Yeah let me grab it [04:39] bdmurray: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/585547 [04:39] Launchpad bug 585547 in boinc (Ubuntu) "boinc-client bad signature for URL (affects: 9) (heat: 11)" [Medium,Fix released] [04:39] Unsure if it is the exact cause but the effect is essentially the same between the two bugs [04:40] Boinc is rendered useless in amd64 11.10 while it works just fine in i386 [04:40] I also reached out to two other people who run the amd64 iso of 11.10 and asked them to test and they experienced the same issue [06:36] hello [06:49] hello ulysses [06:49] cyphermox: Do you know about the proxy settings bug? [06:49] I marked a bug as Invalid, how should I mark that in the wiki? [06:50] this one: https://bugs.launchpad.net/ubuntu/+bug/876606 [06:50] Launchpad bug 876606 in ubuntu "kubuntu kmix in oneiric has no PA support (affects: 1) (heat: 10)" [Undecided,Invalid] [06:59] Ok, I found it, one bug hugged === ara is now known as Guest79243 [10:23] Hi all, is it possible to assign a bug to an individual or specific PPA. I have turned a question into a bug report which should be filed against https://launchpad.net/~ondrej/+archive/redmine but not sure how to do it. The bug is bug/878090 (sorry to repeat my question but I haven't received a response yet). [11:30] bkerensa: define proxy settings bug? :) [12:19] Hi all, is it possible to assign a bug to an individual or specific PPA. I have turned a question into a bug report which should be filed against https://launchpad.net/~ondrej/+archive/redmine but not sure how to do it. The bug is bug/878090 (sorry to repeat my question but I haven't received a response yet). [12:37] oh oh today is a bug day [12:37] time to change the topic === pedro_ changed the topic of #ubuntu-bugs to: Today is a Bug day! Join us : http://t.co/1HWnfGQl | Ubuntu Bug Squad - next meeting 10/20/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [12:43] SwitchDK - The bug 878090 is about the PPA? [12:43] Launchpad bug 878090 in update-manager (Ubuntu) "Upgrade from 11.04 to 11.10 fails when using dpkg-1.16.1~natty+1 (affects: 1) (heat: 139)" [Undecided,Fix released] https://launchpad.net/bugs/878090 [12:45] brendand: thanks for replying and looking into it. It was originally a question which had been answered and I determined there is a bug in the specific dpkg that has been released on the Redmine PPA. Since the dpkg is specific to that PPA and doesn't have anything to do the official dpkg I was uncertain how to deal with it === ryan is now known as Guest83760 [12:46] multiple users were affected, well at least I had received confirmation from 2 other individuals and I was able to reproduce the problem myself [12:47] SwitchDK - Have you read the PPA description? [12:48] yes, that the owner is aware of it being broken? [12:49] brendand: i might of course have missed something [12:50] SwitchDK - There is nothing to fix in code (I guess) so the best you can do is contact the owner, though he seems aware of the problem already [12:50] king hggdh, are you there? [12:51] kamusin: unfortunately yes ;-) [12:51] brendand: so should the bug not be logged against that PPA? [12:52] kamusin: good, but I just started the day -- it is cold(ish), and the bed was really nicier than the office [12:52] SwitchDK - PPAs don't have any way to file bugs against them. In fact I think the general policy on them is that they carry no guarantees [12:53] I know what you mean heh [12:53] brendand: that makes sense, I was just uncertain about how to report the problem dpkg specifically developed for Redmine as all users who are trying to install packages with the "broken" dpkg will have problems [12:54] hello kamusin brendand hggdh! [12:55] hola :) [12:55] good morning pedro_ kamusin brendand :-) [12:55] SwitchDK - All I can say is contact ondrej directly. PPAs have nothing to do with Ubuntu per se so there's really nothing further to do. PPAs are advertised as 'use at your own risk, take what you're given' [12:56] brendand: ok, thanks, what should be done with the bug report? [12:57] SwitchDK - That particular one? Well, there is no issue in any official package so you can just leave it. The correct status is 'Invalid' but 'Fix Released' doesn't do any harm either (from bug triagers point of view it's closed) [12:58] brendand: ok, many thanks for your help. I will also drop the PPA owner a friendly email with the bug number? [12:59] brendand: sorry that was a question [12:59] SwitchDK - Maybe ondrej has a bug opened or can indicate a project which he would be happy you moving the bug to. That's the best case scenario. [12:59] SwitchDK - As long as it's friendly ;) [13:00] brendand: no need to be differently [13:00] and hi to hggdh, pedro_ and kamusin [13:00] hggdh, pedro_ - shall i be seeing you both next week? [13:00] well. This is one of the risks on PPAs. But we need to adjust it a bit, how we (do not) deal with them [13:01] brendand: certainly :-) [13:03] hggdh - i don't know how wise it is to start putting guarantees around PPAs. AFAIK the sole purpose is an easier way than build from source to provide testers access to *pre-release* *unwarranted* software (not that any software is really warranted ;) ) [13:05] brendand: indeed. But given the way folks go (based on my own experience), they tend to forget about having used a PPA, and then disaster happens. [13:05] brendand: we could *check* is the install is kosher before upgrading [13:06] hggdh - well, i have to agree with you there. hope mvo has a bug open on update-manager :) [13:06] PPAs by its nature, are a contract between the maintainer and the user, not with Ubuntu [13:07] hggdh: the problem with this bug is at least three developers didn't associate the Redmine PPA with a dpkg problem and the Redmine PPA has a customised version of the dpkg (which of course is not official) [13:07] hggdh: I wish you could make them more selective - e.g. only allow certain packages to be installed from a given PPA [13:08] penguin42: like a list of trusted/do NOT Change packages? [13:08] SwitchDK: Yes; I trust this PPA to have these packages, but if anything else crops up then ask me [13:08] hggdh: so yes I agree with you hggdh [13:09] penguin42: I do understand it but no, there are *NO* limits on what you can put in a PPA. How could you limit? [13:09] a PPA can be opened by anyone [13:09] hggdh: Oh I mean when you add a PPA on your client you restrict what you'll let apt get from there [13:10] penguin42: ah. Yes, this could work [13:10] hggdh: Taking the initial list when you add it as a starter say [13:10] penguin42: like pinning everything in there, and you select what you want (unpin) [13:10] penguin42, hggdg: i like that idea [13:11] this will at least give you a fleeting feeling of control [13:11] hggdh: Well I might be happy to let the ppa owner upgrade the version, but it's if they add another package that would worry me [13:11] some syntax like this in sources.list would be good: [13:11] hggdh: Having said that, it doesn't really provide much control - a ppa owner could always change an innocuous package to overwrite a different file [13:12] penguin42: there you go... [13:12] deb http://ppa.launchpad.net/ondrej/redmine/ubuntu oneiric main redmine ruby-mocha [13:12] it is still a contract based on trust, not on knowledge [13:13] hggdh: Problem is it's getting a bit dangerous - people install a lot of PPAs and I doubt people understand who they are trusting, especially when there are some Ubuntu ppa's (like the edgers etc) and some random people [13:14] penguin42: I agree, and this is why I would really like some sort of control, at least on upgrades [13:14] nod [13:15] hggdh - you could say that use of PPAs by Canonical somewhat sends out the wrong message [13:21] hggdh: Perhaps something could monitor PPAs and just check whether there are any surprising changes in which set of files is included in each package? [13:21] just a general question which is indirectly related to bugs: Some bug reports are rant/vent/complaints and some are kudos/well dones etc. Is there a way to sent kudos on to the Ubuntu/Canonical team [13:22] ooh I don't think I've seen a well done bug report [13:22] i would be happy to create one :D [13:23] Isn't that what testimonials are for, rather? [13:26] arand: most likely, I just hadn't thought about Testimonials. My thought was also more about short quick kudos [13:29] there is a testimonial mechanism? [13:30] from the ubuntu.com page there is.. [13:34] penguin42: Or, hmm, was... [13:34] arand: i might need new glasses but I can't find any? Would you have a link [13:35] SwitchDK: They're just in a forums section atm it seems [13:35] arand: Thanks I found them now on the forum [13:47] * penguin42 wonders how to prod bug 877403 at someone - it's security ish [13:47] Launchpad bug 877403 in upstart (Ubuntu) "crypttab LUKS password shown in cleartext (affects: 1) (heat: 8)" [Medium,New] https://launchpad.net/bugs/877403 [13:50] if it is real, it should be critical [13:50] that would be a big security issue [13:51] penguin42: I've never had that. [13:51] penguin42: And I've been using that feature for ages. [13:51] jpds: It's not something I have setup, but it does seem serious if he is getting it [13:52] i will test it later, i am using a luks setup here [13:52] untl now its not confirmed [13:54] let me check the bug if i can reproduce it [13:56] * penguin42 suspects it may be only in his no-splash setup [13:56] guess so too [13:56] but a check doesnt hurt [13:56] nod [13:56] is anybody using the hugday tools today? [13:57] I get an AssertionError when using "hugday list" === zyga is now known as zyga-afk [14:06] SwitchDK - the package one or the source branch? [14:27] brendand: sorry was called away, the one part of "ubuntu-qa-tools" package [14:28] ah hugday tool doesn't work here ither [14:28] either even [14:28] is returning 0 results when doing hugday list [14:38] brendand: I get the AssertionError with both source branch and package :( [14:41] brendand: it is working now :D All I did was to the "hugday current --remember" command again. Not sure if something has changed on the back end though [14:42] pedro_: does it work for you? [14:42] nope [14:42] we should file a bug about it.. [14:42] pedro_, indeed ;) [14:44] pedro_, I tried the hugday tools from the branch and they seem to work [14:52] hggdh, great session :-) [14:53] pedro_: I lost my bloody notes for it, and had to improvise [15:27] jibel: bug 878585 [15:27] Launchpad bug 878585 in update-manager (Ubuntu Natty) (and 1 other project) "update apport package hook in natty (affects: 1) (heat: 10)" [High,Fix committed] https://launchpad.net/bugs/878585 [15:34] bug 875571 is a mess, it's a bunch of people with different panics [15:34] Launchpad bug 875571 in linux (Ubuntu) ""Panic occurred, switch back to text console" and freezes - On 11.10 (affects: 6) (heat: 34)" [Undecided,Confirmed] https://launchpad.net/bugs/875571 [15:35] * penguin42 has just flipped it to linux and put a note in the description asking people to file separate bugs === dshufelt is now known as dsmitty === zyga-afk is now known as zyga [17:11] is there a BugSquad team meeting today? [17:21] yes the date is todays. switchDk [17:22] bil21al: thanks, was just wondering if we were starting the meeting or it had been canceled (or I got the time zone conversion wrong) [17:24] switchDK: yes bec i m in asia here the time is too much different i was also waiting for that somebdy say some thing [17:25] bdmurray : has the metting held ? [17:26] bil21al: no, not yet [17:27] I seem to have lost track of the time [17:28] bdmurry same here [17:28] pedro_, hggdh: bug squad meeting? [17:29] aye [17:29] bdmurray: -meeting? [17:30] i think they didnt remember it was metting today [17:30] How about here as I don't know what is on the calendar. [17:32] oh is it today? [17:32] * pedro_ blame google calendar [17:32] well it was supposed to be last week [17:33] so lets have at it? [17:34] sure [17:34] The Agenda can be found at https://wiki.ubuntu.com/BugSquad/Meeting [17:34] There were some actions from the previous meeting [17:34] bdmurray tag bugs with 'TEST CASE' in description testcase: IN PROGRESS [17:35] I started to do this but noticed some complaints in ubuntu-devel so I am doing it as I, or my bugbot, see bugs matching this criteria [17:35] so the actions are batched together [17:36] Please help using the testcase tag though - if you see a bug with a test case in the description [17:36] bdmurray make 'testcase' an official bug tag: DONE [17:36] that was completed [17:36] bdmurray recommend people modify description with 'TEST CASE' words if steps to reproduce exist in bug description or in comments: DONE [17:36] and so was that [17:36] hggdh to review all bug workflows that result with an "Invalid" status and see if using "Incomplete" makes more sense and email bugsquad regarding results [17:36] is that still there? :-P [17:36] hggdh: how is that? I seem to recall a wiki notification email about it [17:36] done; I could not find any such instance [17:37] great! [17:37] hggdh to email mentorship group alpha with questions regarding value of the program and what mentees are looking for: DONE [17:37] hggdh: could you remind us of the results of that? [17:37] done; we do havce to review the current status [17:37] right now we are not providing what mentees expect -- hand-holding, basically [17:38] I emailed -control, -bugsquad, and the mentorship-alpha with what I found [17:39] So it seems there is a disconnect between what mentees want and what mentors want to do or were doing? [17:39] I think so. We expected them to be more open -- and active -- with an exclusive ML, and such; they seem to expect us to be more hand-holding [17:40] they, generically, are not active [17:40] sorry ML? [17:40] Mailing List [17:40] right so we expect mentees to ask questions [17:41] and they want to be told what to do? [17:41] yep. One of our expectations was that mentors would be, ah, 'switchable': any available mentor could do the trick [17:41] this seems not to have happened: mentees, pretty much, do nothing if not helped to it [17:41] okay so this leads into the next item [17:42] bdmurray to create spec for UDS P regarding mentorship program [17:42] the only exceptions are these that are active in the #ubuntu-bugs channel [17:42] I've not done this but it still seems like a useful discussion to have. Agreed? [17:42] which, again, reinforces the feeling that mentees *MUST* be present here [17:42] +1 [17:42] oh yes [17:42] ++1 [17:43] pedro_: +2? [17:43] according to my crazy keyboard, yes haha [17:43] <---- newbie, what does UDS P mean? [17:43] okay so I'll write something and get it scheduled [17:43] SwitchDK: Ubuntu Development Summit, Precise [17:44] SwitchDK: the new Ubuntu version [17:44] bdmurray: please mark me as required [17:44] hggdh: thanks trying to keep up with the acronyms [17:44] hggdh: okay [17:44] so that's it for action items [17:44] who are able to set the importance of the bug and why in my launchpad account there us no options of triaged and wont fix?? [17:44] and I think we can skip any mentorship discussion for UDS [17:44] yes [17:45] There are no recent new bug control members so skipping that [17:45] which leads to open discussions [17:45] where we can answer bil21al's question [17:45] \o [17:45] bil21al: you need to be a member of ubuntu bug control to set those statuses and the importance for Ubuntu bug tasks [17:45] I also have a couple of things I would like to bring up in the Open Discussion section [17:46] bil21al: see http://wiki.ubuntu.com/UbuntuBugControl [17:46] hmm so i need to be more perfect bdmurry [17:46] hggdh: did you have something? [17:46] yes [17:46] bil21al: yes and you could start by putting an 'a' in my nick. ;-) [17:46] hggdh: go ahead [17:47] just a comment -- I am doing a clean-up on requests to join Bug Control [17:47] ok ok bdmurray no nice?? [17:47] now nice [17:47] ? [17:47] and I will, from now, on, summarily reject applications without the submission to the mailing list [17:48] bil21al: yes, thanks [17:48] bdmurray its my pleasue you are my ceniour [17:48] hggdh: you'll give them a wee bit of time though between applying and receiving the application? [17:49] hggdh: actually I wonder if we should just make it a closed team [17:50] I mean we just manually add people anyway [17:50] one thing i want to disscuss that which are the people who accept the membership request and suggest the members? [17:50] bdmurray, the only diff between moderated and closed is the way people gets added to the team? [17:51] I'm pretty sure [17:51] is there any special team for it? [17:51] bdmurray: I do, usually a week [17:51] Why don't we create an action of researching launchpad team types and closing team if possible. [17:51] +1 [17:52] bil21al: we'll get to you after SwitchDK [17:52] https://launchpad.net/+help/team-subscription-policy.html <- found the policy for teams [17:52] bil21al: any current -control member can vote on an application [17:52] well there half way done [17:52] we need to test it though, so we don't have any surprise [17:52] I say make it restricted as it'll save work [17:52] hggdh ok [17:54] pedro_: I think if the dev teams use restricted ones it'll be fine [17:55] SwitchDK: Did you have something to discuss? [17:55] bdmurray, oh right, then sure [17:55] thanks, as I very new member to the BugSquad I was hoping/waiting for a mentor [17:55] i didn't remember they're using that [17:55] but it seems the team is "less" functional [17:56] so you mentioned before that new members should just ask questions in this chat instead [17:56] or on the bug squad mailing list if nobody happens to be around yes [17:56] and that is fine with me (once I am getting used to it), but wouldn't it be worthwhile to update the Wiki pages accordingly [17:57] currently the wiki pages say that new members should/can apply for a mentor [17:57] yes -- but we will discuss mentorship during UDS (again) [17:57] well we plan to discuss the future of the mentorship program the week of the 31st [17:57] SwitchDK: do you have specific change in mind that would help though? If so feel free to just make that change [17:57] ok, sure, sorry I'm still trying to understand the lingo [17:58] if it is decided that references to mentors should be removed I would be happy to help out. [17:58] SwitchDK: no problem, we all started not knowing :-) [17:58] right now I just find it confusing since I was waiting for a mentor to be assigned before attempting traiging [17:59] but then asking in this channel it was clarified that I shouldn't wait [17:59] so once you have a decision on the topic from your meeting on UDS it would be great if it could be circulated [18:00] that was my only question [18:00] hggdh: I removed the bannder in ~ubuntu-bugcontrol changed the team to restricted and set it so people can renew their own memberships [18:00] it certainly will; additionally, the UDS sessions have live audio, and IRC channels available for remote users [18:00] bdmurray: perfect, thank you [18:01] hggdh oh ok, didn't know that, thank you [18:01] SwitchDK: yes, we will definitely update documentation and email the bugsquad mailing list with results of our discussion [18:01] Okay are there any more questions / topics for discussion? [18:01] bdmurray thank you that would be great and as I said I would be happy to help with wiki updates [18:02] not from me, thank you [18:03] Okay, thanks everyone and sorry for the delay in getting the meeting going. [18:03] no problem [18:04] back to hugging a bug :P [18:04] bdmurray: thank you [18:04] thanks all [18:04] ok bdmurray see you and really switchdk reminds us about the metting [18:04] SwitchDK: if you have any questions please let us know, or if you are looking for something to work on we might find something for you [18:05] thanks for your time bdmurray, pedro_ and hggdh [18:05] bdmurray thank you very kind, i am trying to do a bug on the list pedro_ sent out [18:05] bdmurray so i will probably ask once I get more stuck than I already am [18:08] SwitchDK, if you have questions just ask here in teh channel :-) [18:08] will do, thanks pedro_ [18:09] pedro_ give me some thing too i m free bro [18:10] bil21al, check at the bug day page there's plenty of bugs there: https://wiki.ubuntu.com/UbuntuBugDay/20111020 [18:11] ok thanks i will check [18:12] and I just updated https://wiki.ubuntu.com/UbuntuBugControl taking out the references to request membership [18:13] hm, what's the current way of using the hugday tools? I'm getting: RuntimeError: Error while parsing 'https://wiki.ubuntu.com/UbuntuBugDay/20111020' [18:17] yofel, i had problems with the tool but it seems to work if you use the one from the branch [18:17] that *is* from lp:ubuntu-qa-tools [18:18] yofel: try lp:hugday-tools instead [18:18] same error [18:19] yofel, is that when you use "./hugday-tools current" ? [18:19] no, hugday close is what doesn't work [18:19] current works fine [18:20] yofel, ok I haven't made it that far yet so don't know if it works for me [18:24] bil21al are you working on bug 875061 [18:24] Launchpad bug 875061 in gnome-control-center (Ubuntu) "11.10 doesn't remember screen brightness setting after every reboot (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/875061 [18:25] yes [18:25] bil21al i just updated it a moment ago [18:25] bil21al so refresh your screen before continuing [18:25] yes yes i am watching [18:25] ok [18:25] u carry on [18:25] bil21al i wasn't able to reproduce the problem on my machine unfortunately [18:26] ohh man i have seen this many times [18:26] when every i start my system [18:26] bil21al could you then please update the bug with some more technical details please [18:27] k [18:30] pedro_ bdmurray once a incomplete bug has been updated on the BugDay list should I mark it as done on the BugDay list? [18:35] SwitchDK: which bug? [18:37] bdmurray 875061 [18:38] bdmurray i have asked for more information [18:38] bug 875061 [18:38] Launchpad bug 875061 in gnome-control-center (Ubuntu) "11.10 doesn't remember screen brightness setting after every reboot (affects: 3) (heat: 16)" [Undecided,Confirmed] https://launchpad.net/bugs/875061 [18:39] If the bug needs more information it should be incomplete [18:39] hggdh ah you have to put "bug" in front of it [18:39] I find it a bit strange that the package is gnome-control-center but you mention debugging instructions for gnome-power-manager [18:40] bdmurray missed the "incomplete" part, it has been updated [18:41] SwitchDK: great, thanks [18:41] bdmurray you are right but the power manager information is useful for trouble shooting this [18:41] bdmurray and not sure where else to go with "dim" trouble shooting [18:41] bdmurray since it has changed in Unity (well at least I think it has) [18:43] bdmurray would it be better to change the package to gnome-power-manager? [18:44] SwitchDK: I would think so yes [18:45] bdmurray thank you I will update it now. [18:50] bdmurray based on changing that information should it then be marked completed on the BugDay list? althought it is not complete yet [18:50] bdmurray: Do you know any way I might workaround this bug [18:50] https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/878571 [18:50] Launchpad bug 878571 in boinc (Ubuntu) "boinc-client bad signature for URL (affects: 1) (heat: 14)" [Undecided,Confirmed] [18:54] SwitchDK: the bug day list is just recording that an action took place [18:55] SwitchDK: and you acted on that bug and no one else needs to yet so yes it can be marked done [18:57] bkerensa: I wonder if installing the i386 version on the package on amd64 would work around it [18:58] bdmurray: Yeah but I tried doing that and am getting some error with the i386 package even though I was running it on 32bit fine [18:58] idk something is broke [18:59] "This seems to indicate that the XML received by the RPC was corrupted somehow. As you can see in the XML you PM-ed me, there is no value host_uhntiiccaator in it." [19:00] bdmurray, SwitchDK, pedro_: gnome-power-manager is deprecated in oneiric, the instruction for debugging should be updated [19:00] bkerensa: didn't you say something about having a web proxy? [19:00] bdmurray: Yeah proxy settings on 11.10 are broke [19:00] it only ships the statistics ui [19:00] cant set a proxy [19:00] 11.10 ignores settings :( [19:00] the other features got moved to gnome-settings-daemon and gnome-power-manager [19:00] bkerensa: right isn't it possible your network is screwing up the boinc traffic? [19:01] the other features got moved to gnome-settings-daemon and *gnome-control-center* [19:03] seb128, bdmurray SwitchDK i'll update those debugging instructions [19:03] pedro_, thanks [19:03] you're welcome [19:04] pedro_, you can probably drop all the "before 9.04 instructions" while you are at it, it's just confusing nowadays [19:04] we are not interested to get bug about those versions ;-) [19:09] bdmurray: I have no proxies set right now [19:09] bdmurray: and I have had other people who run 64bit Ubuntu confirm this bug [19:16] has any body seen this bug or having this ?? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/874348 [19:16] Launchpad bug 874348 in unity (Ubuntu) "when we change the theme some icons from the launcher vanished (affects: 1) (heat: 6)" [Undecided,New] [19:22] Evening all. I've seen some bug reports requesting newer versions of programs which since the report was filed has been included in Ubuntu. Would it be ok to close these as fix released and leave a comment like "version x is in ubuntu release foo" or should I add some more information? [19:24] you can use one of these responses: https://wiki.ubuntu.com/Bugs/Responses#Fixed_in_Development_release_while_still_existing_in_a_previous_release [19:28] jtaylor: ok. thanks :) [19:43] pedro_ [19:44] if the bug is to much older like some people says that boot is failed in ubuntu and talks about alpha or beta 1 version so can we invaid it? [19:47] any other bdmurray: [19:48] bil21al: I would mark it incomplete and ask them to check it in the release [19:48] ok [19:49] bil21al: But don't be too hasty on things - there are some bugs that are years old; the fact they are old doesn't necessarily mean they are invalid! [19:50] yes yes ok i understand. [19:56] seb128 pedro_ thanks for letting me know about the changes to debug info. Would you recommend I change the associated package to "gnome-control-center" [19:57] seb128 predr_ sorry I should clarify that I am referring to bug 875061 [19:57] Launchpad bug 875061 in gnome-power-manager (Ubuntu) "11.10 doesn't remember screen brightness setting after every reboot (affects: 3) (heat: 16)" [Undecided,Incomplete] https://launchpad.net/bugs/875061 [19:58] SwitchDK, i think i've seen that bug before [19:59] one sec [19:59] yofel did you manage to fix the runtimeerror problem when closing a bug on the bugday list [19:59] nope === yofel_ is now known as yofel [19:59] SwitchDK, https://bugzilla.gnome.org/show_bug.cgi?id=661586 [19:59] Gnome bug 661586 in Other Preferences "[screen] Remember brightness level across reboots" [Enhancement,Unconfirmed] [19:59] yofel_ :( [19:59] which is bug 870805 on lp [19:59] Launchpad bug 870805 in gnome-control-center (Ubuntu) (and 1 other project) "Screen dialog won't remember brightness setting (affects: 1) (heat: 54)" [Low,Triaged] https://launchpad.net/bugs/870805 [20:00] SwitchDK, feel free to mark it as a duplicate [20:00] pedro_ wow how to you remember that, i will update to mark it as duplicate [20:00] pedro_ thanks [20:00] you're welcome [20:02] pedro_ how would I mark a bug "completed" on the BugDay list when the hugday tool won't allow me to? [20:02] edit the wiki page by hand [20:03] edit the wiki [20:03] yeah as yofel said [20:03] some people assign their bug to themselves even they are not a programmer so what to do with that?? [20:03] yofel_ yofel pedro_ ok that simple I thought there was something more complicated [20:05] Could a control member please mark bug #879038 as triaged? It's a simple documentation issue and I believe all of the necessary information is there for an ubuntu-docs team member to work on it. [20:05] Launchpad bug 879038 in ubuntu-docs (Ubuntu) "help.ubuntu.com lists 11.04 as Natty and as Oneiric. (affects: 2) (dups: 1) (heat: 16)" [Undecided,Confirmed] https://launchpad.net/bugs/879038 [20:06] I *think* that should be filed agains the ubuntu-website project [20:06] it's certainly not the docs package in the archive [20:06] *against [20:07] pedro_ some people assign bug to them selves even they are not a programer than what to do ?? [20:07] i assign my self and than un assign do i roght ?? [20:07] right [20:07] ? [20:08] any body tell me plz [20:08] bil21al, Do not assign bugs to yourself unless you're planning to fix the issue [20:08] if you want to receive emails when the reporter replies to you , then subscribe to the email [20:08] yofel: Hmm, thats a good point. But Bug 590932 described something similar and its packaging seemed correct. [20:08] Launchpad bug 590932 in ubuntu-docs (Ubuntu Natty) (and 3 other projects) "broken link to ubuntu licensing page (affects: 1) (heat: 1)" [Undecided,Fix released] https://launchpad.net/bugs/590932 [20:09] s/email/bug [20:09] pedro_ yes i know that but some people who dnt knw about that assign to themselves than what to do with that before marking incomplete?? [20:10] phil93: true, then I have no idea, sorry [20:10] bil21al, unassign if you sure that they're not planning to work on the issue [20:11] bil21al, if unsure ask with the bug number here in the channel [20:11]