[00:10] Hellow: around? [00:11] micahg: Sure, what's up? [00:11] Hellow: if you remove compatability.ini from your firefox profile dir and run it from the command line, does it start? [00:11] Hellow: ~/.mozilla/firefox/ [00:12] compatibility.ini [00:12] there should be a profile dir in the above dir [00:13] Testing, just a second. [00:14] Yes, firefox is starting fine now. [00:14] Hellow: thanks, I'll mark you bug as a dupe of the master [00:14] M'kay. Thanks, that issue has been a problem for me for a while. [00:17] Hellow: what the libxul issue or the not start issue? [00:18] hello everyone, I just joined bugsquad today and I am working on my first bug. Could someone take a look at this and make sure I did alright? https://bugs.launchpad.net/totem/+bug/548358 [00:18] micahg: They was attached. [00:18] Launchpad bug 548358 in totem (Ubuntu) (and 1 other project) "Screenshot option shows error while listening to music (affects: 2)" [Undecided,Confirmed] [00:18] Also, do i just wait for a bug control member to set the importance to low? [00:18] Hellow: well, firefox -g should start firefox in gdb, but it's broke and there's a bug for it [00:27] bbordwell: welcome, usually you request the triaged state here in the channel, a BC member will take care of it if they see the message [00:28] yofel, okay like this? [00:29] almost [00:29] https://bugs.launchpad.net/totem/+bug/548358 I feel this bug is ready to be marked as triaged and importance as low, can a BC member please do so? [00:29] Launchpad bug 548358 in totem (Ubuntu) (and 1 other project) "Screenshot option shows error while listening to music (affects: 2)" [Undecided,Confirmed] [00:32] bbordwell: if you add a bugwatch, can you please add a comment with the link too (so it's obvious that you were the upstreamer and new reporters might not understand the launchpad watch system yet [00:32] the command can be something like "This bug has been reported to the developers of the software. You can track it and make comments at: " add the link after that [00:34] bbordwell: oh, and all bugs against packages on this list https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs should be assigned to the 'desktop-bugs' team, don't ask me why but the desktop team wants it like that [00:36] yofel, I did so, is that correct? [00:37] bbordwell: it is, I'll mark it triaged [00:38] yofel, Thanks for the help. I should get the hang of this before long. As you can see i started with an easy bug. [00:38] np, we all started somewhere, don't hesitate to ask here if you have questions [00:41] bbordwell: also, as you can reproduce this bug too you might want to subscribe to it so are informed if something happens on the bug that might involve you [00:41] missed him [02:21] https://bugs.launchpad.net/gcalctool/+bug/548502, I belive this bug is ready to be marked as Triaged. Would a member of BC please do so? [02:21] Launchpad bug 548502 in gcalctool (Ubuntu) (and 1 other project) "+/- button missing (affects: 2)" [Undecided,Confirmed] [03:37] hello, a new bug squad member here. I am working on this bug https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/548544. Is there a certain team i should assign software-cetner bugs to? [03:37] Launchpad bug 548544 in software-center (Ubuntu) (and 1 other project) "Clicking install button still displays install option (affects: 2)" [Undecided,Confirmed] [03:38] also, I think it is ready to be marked as triaged by a BC member, with importance of either low or wishlist. [07:16] I fell this bug is ready to be marked as triaged with an importance of wishlist. Can some one from BC do so please? https://bugs.launchpad.net/evolution/+bug/543953 [07:16] Launchpad bug 543953 in evolution (Ubuntu) (and 1 other project) "no support for fullscreen (affects: 2)" [Undecided,Confirmed] [07:16] s/fell/feel [07:16] i'll take a look in a sec [07:24] * ddecator looking [07:24] ddecator, I am new to bug squad so if i made any mistakes let me know [07:33] alright, so i think the part of the bug stating that evolution should support fullscreen via f11 is good and matches the upstream bug, but i'm thinking the rest of the report (on how to make it more social) is better for ubuntu's brainstorm page since it is kind of abstract and would be a pretty major change [07:34] may i ask why you assigned ubuntu desktop bugs? [07:35] (i haven't worked with evolution before, so if you found a wiki page or something saying thats what you should do, then please let me know) [07:35] ddecator, do you know who yofel is? [07:36] bbordwell: yes, did he tell you to? [07:36] yes, he said any packages on this list (https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs) should be assigned to ubuntu-desktop-bugs [07:37] bbordwell: oh, and all bugs against packages on this list https://bugs.edge.launchpad.net/~desktop-bugs/+packagebugs should be assigned to the 'desktop-bugs' team, don't ask me why but the desktop team wants it like that [07:37] huh, never knew that...learn something new everyday [07:37] bbordwell: good enough for me =) [07:37] bbordwell: i'm assuming you looked for downstream duplicates? [07:38] ddecator, you mean other duplicates in launchpad? [07:38] bbordwell: yes [07:38] yes [07:38] good deal [07:38] bbordwell: what importance do you think this is? [07:39] ddecator, I thought wish-list to be consistent with the upstream bug report [07:39] plus it is more of a feature than a bug [07:39] bbordwell: i agree, there isn't anything inhibiting functionality, it just is requesting a new feature [07:39] bbordwell: have you seen the canned responses wiki page yet? [07:40] though i linked to the gnome usability principals on the upstream report because it is inconsistent with other gnome apps [07:40] yes, i saw that as well, it's a good point [07:40] ddecator, no, There are a couple on the how to triage page i have been using though [07:41] can you send me the link? I have a bookmark folder set up called bug squad [07:41] very useful [07:41] that's similar to what i did, haha [07:41] bbordwell: https://wiki.ubuntu.com/Bugs/Responses [07:41] Thank you [07:41] bbordwell: if you use firefox, i also recommend the lp-improvements add-on [07:42] bbordwell: ok, back to the bug [07:43] bbordwell: like i said, i feel that the ideas for making evolution more social are better for http://brainstorm.ubuntu.com/ since it's a larger project that's fairly abstract imo [07:43] bbordwell: what do you think? [07:46] yes I agree. You could comment and tell him to add that idea to brainstorm [07:48] or you could ;) i think it would be appropriate to ask him/her to report that idea on brainstorm, then update the description so it's cleaner and just discusses the request for fullscreen support and how evolution is different from other gnome applications by not having this support [07:48] ddecator, will do [07:49] bbordwell: sounds good, let me know when you're done and i'll take a look [07:50] bbordwell: might not hurt to update the title to something along the lines of "Evolution should support a fullscreen mode when F11 is pressed" [07:58] ddecator, okay I shorted the description down to the bare metal and changed the titel [07:59] also made a copy of the guys ideas and put them in a comment incase he forget them and told him to submit them to brainstorm [07:59] bbordwell: looks good to me. also, the full descriptions can be found in the activity log, so you didn't necessarily have to copy what he said into a comment. not a big deal, but just good to know for the future =) [08:00] ddecator, Ah I did not know that [08:01] ddecator, That not described well canned response will come in very handy it is hard to tell people there report sucks in an extremly nice way [08:01] e.g. GDM is broken [08:01] and thats it [08:02] bbordwell: haha, yah, that's the reason for it. i have some extra tips for you in a sec, little tricks that will make triaging easier [08:03] bbordwell: alright, i set it to triaged and wishlist, good work =) [08:03] bbordwell: do you have a minute so i can give you some extra advice? [08:03] ddecator, i have 2 hours lol [08:03] bbordwell: fair enough, haha [08:04] bbordwell: alright, this is a big one. the easiest way, imho, to look for duplicates is to go to google and search "site:bugs.launchpad.net " since this will search the descriptions of the bugs and not just the titles (launchpad's search is fairly limited) [08:06] ddecator, yes that is what i sometimes do [08:06] ddecator, alot of times i just look at all bugs filed against a certain package if there are not too many [08:06] bbordwell: that works as well, i just remember going a few weeks not knowing about the site: search, haha [08:07] bbordwell: are you using firefox? [08:07] ddecator, yes [08:09] bbordwell: then i also recommend you install firefox-lp-improvements and... [08:11] bbordwell: er, i guess that's the only package: https://launchpad.net/~gm-dev-launchpad/+archive/ppa [08:11] bbordwell: although you may want to disable the highlighting feature since it has been buggy [08:12] bbordwell: just two more things. have you thought about requesting a mentor? [08:13] ddecator, no I seem to be able to get all the help I need in IRC [08:14] bbordwell: yes, you usually do, that's how i ended up learning most things, just wanted to let you know it's an option [08:14] bbordwell: finally, have you thought about a package you might want to specialize in? [08:16] ddecator, no i have just been going through and working on the ones i feel i can actually help with [08:16] Like most of the lower level stuff such as x and the kernel i do not know enough about to help [08:16] but most of GNOME i can help with [08:17] bbordwell: alright, that's a good place to start. i was just wondering because if you were interested in a specific package i was going to point you towards a person or persons you might want to talk to about how to work on that package =) [08:18] bbordwell: but you're doing a good job, so keep up the good work! [08:18] https://bugs.launchpad.net/gnome-power/+bug/535097 [08:18] Launchpad bug 535097 in gnome-power-manager (Ubuntu) (and 1 other project) "Power Manager Brightness Applet not working (affects: 5) (dups: 2)" [Low,Confirmed] [08:19] i've seen that before [08:19] Should be ready to be marked as triaged [08:19] I have assinged two other duplicates to it [08:19] oh, maybe the one i was subscribed to is one of those, haha [08:19] one of the duplicates had a patch with it, i attached it upstream [08:19] ddecator, what is your launchpad id? [08:20] bbordwell: ddecator [08:20] nice :) [08:20] i try to stay consistent, haha [08:22] oh, the one i'm subscribed to is different [08:22] Bug #535097 [08:22] Launchpad bug 535097 in gnome-power-manager (Ubuntu) (and 1 other project) "Power Manager Brightness Applet not working (affects: 5) (dups: 2)" [Low,Confirmed] https://launchpad.net/bugs/535097 [08:22] Bug #532518 [08:22] Launchpad bug 532518 in gnome-power-manager (Ubuntu) (and 1 other project) "Brightness Applet is not usable via Mouse (affects: 2)" [Undecided,New] https://launchpad.net/bugs/532518 [08:22] Which should we make the master? [08:23] The one that already has duplicates? [08:23] /pa/part [08:24] i think the one that has the duplicates works [08:25] okay i did so [08:25] ddecator, looks like upstream has duplicates of this bug as well [08:25] bbordwell: not surprising, they should take care of that. if that patch works, it would be an easy fix [08:27] and this didn't already have a master report? i'm surprised [08:28] ddecator, Not that i saw. Mine is turning into one though lol [08:29] bbordwell: yes it is [08:29] ddecator, The wiki was serious when it said they were in need of bug squad members [08:30] bbordwell: yup, we have way more reports than triagers, haha. a lot of us get caught up in debugging and lose track of all of the reports [08:32] bbordwell: i think the title could be a little more descriptive and the description could be cleaned (i like to give a series of steps to reproduce, expected behavior, and observed behavior. easier to replicate that way) [08:33] ddecator, which bug? [08:33] i just found another duplicate of Bug #535097 [08:33] Launchpad bug 535097 in gnome-power-manager (Ubuntu) (and 1 other project) "Power Manager Brightness Applet not working (affects: 8) (dups: 4)" [Low,Confirmed] https://launchpad.net/bugs/535097 [08:33] bbordwell: the master bug, 535097 [08:33] okay [08:33] bbordwell: also, it wouldn't hurt if they ran apport-collect. have you requested that before? [08:34] not sure it's necessary since there is a proposed patch, but we don't know if it works or not, so we want to make sure there is enough info for the devs in case it doesn't [08:35] ddecator, what are the bars at the top and bottom called again? in GNOME [08:35] ahh gnome-panels [08:36] yup =) [08:39] ddecator, title and description updated [08:41] i tweeked the description a bit. i think having numbers is more clear =) [08:41] alright, looks good [08:41] already set to low, but i'm not ready to mark it triaged [08:41] bbordwell: are you familiar with apport-collect? [08:42] ddecator, somewhat [08:43] bbordwell: basically, "apport-collect " will look at whatever package the bug is assigned to, find what "hooks" are set for that package, grab the data, then automatically upload it to the bug report. this is used when the person did not use apport to report the bug in the first place [08:43] bbordwell: if apport is used, there is detailed info about their system in the description, a bunch of files attached to the report, and an "apport-collect" tag on the report [08:44] ddecator, i knew the second part [08:44] bbordwell: like i said, even though this has a proposed patch, it doesn't hurt to get the information using apport just in case the patch doesn't work and the devs want more info [08:44] bbordwell: i believe there is a canned response on that site for asking the reporter to run apport-collect [08:46] bbordwell: you just replace "BUGNUMBER" with the actual bug number of the report when you leave the comment [08:49] and i see that some of the duplicates used apport, but it's easier for the devs to just have to look at the master report =) [08:50] ddecator, I added a comment asking the reporter to do so [08:50] m0rning [08:50] BUGabundo_remote, morning [08:50] morning BUGabundo_remote [08:50] definitely morning...4:50am here, oops, haha [08:50] ddecator, I have some special interest in this bug https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/543892 [08:50] Launchpad bug 543892 in rhythmbox (Ubuntu) (and 1 other project) "Clicking "Create Audio CD" does nothing (affects: 2)" [Low,Confirmed] [08:51] 3:50 AM here [08:51] bbordwell: good, once the apport info is attached i think it will be ready to be marked triaged. as for the other bug, i really need to get to bed, so someone else will have to help you with that, haha. but never hesitate to ping me if you ever need help, especially with firefox bugs [08:52] heys guys [08:52] ddecator, alright see you later [08:53] BUGabundo_remote, hey [09:29] Could somone mark bug 545209 as triaged as this has been passed upstream [09:29] Launchpad bug 545209 in chromium-browser (Fluxbuntu) (and 2 other projects) "chromium-browser with gecko-mediaplayer hangs on KDE (affects: 1)" [Undecided,Invalid] https://launchpad.net/bugs/545209 [10:04] I belive this bug is ready to be marked as triaged, could a member of BC please do so? https://bugs.launchpad.net/gnome-panel/+bug/546759 [10:04] Launchpad bug 546759 in gnome-panel (Ubuntu) (and 1 other project) "add new panel does not work (affects: 1)" [Low,Confirmed] [10:28] I belive this bug is ready to be marked as triaged, could a BC member please do so? https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/535097 [10:28] Launchpad bug 535097 in gnome-power-manager (Ubuntu) (and 1 other project) "Power Manager Brightness not clickable (affects: 8) (dups: 4)" [Low,Confirmed] [10:56] hi there [10:57] i just installed 10.04 beta1 in vmware workstation and after the update, no keyboard input is possible. is that a known problem? [11:01] Honk_: This isn't a support channel. Your best going to #ubuntu+1 [11:01] i don't need support. i thought it was a bug and so asked here [11:02] Search on launchpad for the bug, if you can't find another one open a new bug report. [11:04] hi. an app crashed and launched apport and I accidentally closed it. now when it crashes again, apport doesn't launch. how can I cause it to launch again? [11:05] salty-horse: sudo nano /etc/default/apport change enabled from 0 to 1 [11:05] salty-horse: I believe you'd have to restart [11:06] Or if you want to run it just once and not always ask to report a crash sudo service apport start force_start=1 [11:07] it's already enabled [11:07] it runs, but won't run when this specific program runs again [11:08] salty-horse: Is the program crashing? [11:08] yes [11:09] I could report it manually, but I want the apport magic in the bug :) [11:11] run /usr/share/apport/apport-checkreports in terminal, that will output any reports in /var/crash [11:12] should I just report it manually? [11:13] oh, I see it. so I just apport ? [11:13] If its there, run /usr/share/apport/apport-gtk [11:13] apport-bug [11:16] The problem cannot be reported: [11:16] The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes. [11:16] should I delete that file and try again? [11:17] after printing that message, the apport-gtk doesn't terminate. seems like a bug in itself :) [11:55] hello [11:57] I'm using Beta 1 and my Update Manager is never showing any daily updates in the notification panel - is this normal? [12:20] In Beta 1 I have Update Manager set to "check for udpates daily" and "Install security updates without confirmation". However, even though there are lots of daily updates available, I don't seem to be getting any notification (without manually opening Update Manager) - is this a bug? [12:22] (continuing from #ubuntu+1), could be, it should pop up at some point if there are updates [12:25] yofel: ok, i will file a bug report if the behaviour continues [12:29] nperry, I eventually reported my bug in gnome, since it's a gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=614006 [12:29] Gnome bug 614006 in GtkFileChooser "File chooser crashes when creating a new folder, and new files are added to the parent" [Major,Unconfirmed] [13:44] om26er, are you around? [14:03] bug 1 [14:03] Launchpad bug 1 in tilix (and 16 other projects) "Microsoft has a majority market share (affects: 229)" [High,New] https://launchpad.net/bugs/1 [14:16] huh, didn't ubotu time out on that bug before, nperry ? === jonathan__ is now known as jjesse [14:32] Hello, I have a closed-source software here that crashes when I use lucid (yet it works fine with debian unstable), but when I strace that software, it doesn't crash, what would be the possible reason for this ? [14:34] I'm going to leave this an open discussion because I want some feedback. **Should Bug importance retain consistency through all of Ubuntu in Launchpad?** I.E. (and hggdh will know what I'm talking about) if someone who works really exceptionally well with a package and knows it in an out, decides that a bug which is a cosmetic issue and (by the Ubuntu wiki) would get a low importance, should actually be high because the cosmetic [14:34] issue actually causes package workflow confusion (i.e. missing a menu entry, but this menu entry allows users to do something much more important) [14:35] AnAnt: I would ask that in #ubuntu first [14:36] bcurtiswx_laptop: I understand the context, but a little more simple words would be nice, I'm confused [14:37] nigelb: i suck at describing things.. so don't feel bad... hmmm [14:37] bcurtiswx_laptop: I'd need a better example. The "menu entry missing" example isn't confined to the menu entry missing... the feature itself is not available, so therefore it's high importance. [14:38] Perhaps the description makes it sound minor "menu entry is missing", but in reality, it should be "feature is inaccessable" [14:39] Just because it is easy to fix doesn't mean it isn't high importance. [14:39] lemme try and think of a good example [14:43] bug #528051 what should the importance be? [14:43] Launchpad bug 528051 in software-center (Ubuntu) "'provided by Ubuntu' should be categorised (affects: 1)" [Undecided,New] https://launchpad.net/bugs/528051 [14:46] nigelb: mrad: ^^ [14:46] mrand: ^^ [14:49] weird. Just lost my X session [14:50] bcurtiswx_laptop: in general (my personal view) we should follow the published guidelines [14:50] but -- important -- the guidelines are subject to interpretation and must consider the issue at hand [14:51] hggdh: if that is the case, we should consider these kind of applications similar to giving bug control to upstream devs [14:52] hggdh: only a handful of people will know the true issue at hand, and I expect to go into a bug and see high and it should reflect the high classification on the wiki [14:52] bcurtiswx_laptop: +1 [14:52] nigelb: we *do* accept upstream devs in -control (and, in fact, encourage them to join) [14:52] hggdh: yes, I know, but they are also asked to stick to their package(s) [14:53] bcurtiswx_laptop: I agree. This is why I rephrased the requirements for -control to explicitly state one should give the proposed Importance *and* an explanation of why [14:53] if, for example, I think bug x is worthy of a High, I should explain my reasoning [14:54] hggdh: OK, I hope then, that if someone wants to go beyond the wiki guidelines, I want to see exactly why in the comments.. [14:55] bcurtiswx_laptop: *any* change in Status/Importance should be documented [14:55] hggdh: you and I both know that it rarely is.. [14:56] on the specific case, Kiwinote did not give us the reasons, and both you and I vetoed the application [14:56] bcurtiswx_laptop: yes. But I, for one, will keep on asking, and complaining === jonathan__ is now known as jjesse [14:57] (going on) *after* I read the reasons, I found myself agreeing with the suggested values for some of the bugs [14:58] On a more personal note: I think once you submit an application thats it. Try again in a couple weeks if you need to make changes.. Otherwise they won't put their changes into practice [14:58] for example, having a trial package in the free section of sofftware-centre going straight against what we hold VERY dear: free software [14:59] bcurtiswx_laptop: this is usually how I go also. But I will correct myself if I find that (by my mistake, or lack of details) the reality is a bit different [15:00] I am not grading students... and even when I did, I usually considered the responses to the questions and my talking with them about the test [15:01] bcurtiswx_laptop: sorry, had to step away. Taking the description at face value, I'd think that the above bug would be high because an unusable application impacts a large number of users. [15:03] I think after this talk, I find my view on consistency has some unique flaws. I have nothing against kiwi, but I don't think it will hurt bug triage nor kiwi if they waited another week or two and reapplies to bug control after they practice explaining importances better (which is really important in bug triage) [15:04] Thats why im going to stay -1 on the app. [15:05] bcurtiswx_laptop: no problem -- and the final decision is not mine, BTW [15:06] hggdh: i know. Just stating why i'm staying -1. Right now anyways kiwi will make it through with the surplus of +1's anyways [15:07] s/he *might*, not yet decided [15:08] (oh. I always thought consistency to be a finite phenomenon on the time axis ;-) [15:08] oh the irony of that statement [15:08] :-D [15:09] the complexity of it [15:09] :D [15:09] if you see my e-mail signature.. now THATS a complex statement [15:09] bcurtiswx_laptop: seriously -- I do not own the truth, nor I expect to be correct always (or most of the times, even) [15:10] * hggdh goes hunting for such signature [15:10] hggdh: ---------------------------------------------------------------- [15:10] The Statement Below is True [15:10] The Statement Above is False [15:10] ---------------------------------------------------------------- [15:10] sorry for the enters.. but it's appropriate [15:10] heh [15:11] I agree. Always loved these things [15:11] bcurtiswx_laptop: :) [15:11] don't think about it too long.. you may start to steam at the ears [15:11] just shows that Goedel was right [15:15] bcurtiswx_laptop: anyway. This was, I think, a good discussion to be had [15:15] hggdh: agreed. Thanks [15:16] I have followed this discussion on importance, and I am going to ask this. [15:16] Is the wiki a guideline or a rule to be followed? [15:17] I always thought it provided the guidance to help get the importance and status set, but was not a "set in stone" rule [15:18] charlie-tca: I myself see it as a strong guideline -- which means that most of the times we should follow it; sometimes we will have a special case (in our view) where it does not match [15:18] which would make it a guideline, and can be deviated from when needed [15:19] there are some things that *are* rules -- for example, we cannot provide free software without the sources [15:19] charlie-tca: i agree with hggdh: it can be deviated from, but the explanation should be concise as to why it deviates [15:19] WHAT ??? hggdh you aren't always correct???? so I can run for that spot now? KEWLLL [15:19] oh wait [15:19] I'm already vice chair [15:19] duh [15:19] * BUGabundo_remote goes back to work [15:19] BUGabundo_remote: be my guest. I am not always right, but I *do* learn ;-) [15:19] Yes, I agree it should have an explanation. But it becomes a guideline then, not a standard or rule to be followed exactly [15:20] charlie-tca: its not a rule by any means, i agree [15:20] charlie-tca: wasn't it always the case? The way I see it: if one is starting, follow it as rules; as one gains experience, use the experience to decide [15:21] **Should Bug importance retain consistency through all of Ubuntu in Launchpad?** then becomes no [15:21] but -- always -- explain the why [15:21] as in when the "why not" is explained in the bug [15:21] charlie-tca: after the discussion, i believe added to that should be "if it bears no explanation" [15:22] and that should be noted on the wiki page for importance [15:22] Personally, I believe that should be true for status and importance [15:22] Otherwise, even the guidelines are close to useless [15:25] charlie-tca: hggdh: I believe that "explanations for all bug changes" isn't preeched enough to triage beginners.. there are too many people still that don't explain why they change bug reports the way they do [15:25] completely agree. I have even requested developers come back and tell me why they changed things without the explanation [15:28] from the perspective of a simple lp user (we have the rights to change some bugs status), it is quite hard to find the explanation of the bug statuses [15:31] people don't even explain the most common bug changes (most would know why it was changed), but it needs to be documented (yes i've done this in the past) [15:31] jeanfi: I agree. We are always monitoring this channel (and the MLs) for issues and proposed changes [15:32] I agree, but 99% of the time, the user would not be changing the status [15:32] bcurtiswx_laptop: perhaps we need to emphasise this more at the Bugs/(Importance|Status)? [15:33] jeanfi: if you could expand on why you find it hard, this would helps us [15:34] hggdh: we should emphasize it more, agreed === jsalisbury_ is now known as jsalisbury [15:35] charlie-tca: maybe just because it is not easy to get the explanation [15:35] jeanfi: no, most users filing the bugs should not be changing the status [15:36] hggdh, it just miss the link to the explanation in the bug page itself [15:37] hggdh, first time I filed a bug, I have see that I can change its status (confirmed,invalid,fix,etc), so I asked myself "I am really allowed to change the status? What means 'confirmed'?etc" [15:38] jeanfi: agree [15:38] hum [15:38] and I had to google LP + ubuntu to find the page which explains what I am supposed to do [15:39] * hggdh is pretty sure there should be a LP/Malone bug on this [15:39] I guess most users don't take the time to google the page or are afraid to do a mistake [15:39] yes, I can understand you [15:39] Perhaps there should be a comment on the reporting bugs how to page that says leave the status in 'new' [15:39] * hggdh goes looking [15:40] * bcurtiswx_laptop wishes bdmurray were here to offer his opinions on this [15:40] charlie-tca: do you mean that as a simple LG user I must never change the bug status? [15:40] LG=LP [15:40] where am I? [15:40] As a bug filer, you should never change the status from new [15:40] bdmurray: WHA?? well empathy apparently has a glaring bug [15:41] hggdh, the bug for "status is too easy to change" is fixed in the upcoming LP release next wednesday. [15:41] with a confirmation dialog [15:41] charlie-tca: arf, I did it. If you don't want simple user to change status, LP should not authorize it! [15:41] deryck, Can you link to the details of this update? [15:41] jeanfi: You can't actually confirm your own bug, so the status stays in new until someone else can confirm it [15:42] charlie-tca: yes but this explanation is not in the bug report page, that's my point [15:42] bbordwell, See Bug #531963 [15:42] Launchpad bug 531963 in malone "Add a confirmation step when setting the bug status if the user is not a bug contributor (affects: 1)" [High,Fix committed] https://launchpad.net/bugs/531963 [15:42] charlie-tca: I think you mean shouldn't not can't [15:42] right [15:43] jeanfi: That´s why I said something should be added to the bug reporting page, to say it should be left in 'new' [15:45] I've haven't read the whole back log but I'd imagine this (filers changing bug status right away) is a corner-case [15:45] vish: around? [15:45] Bug #401028 [15:45] Launchpad bug 401028 in pymsn (Ubuntu Karmic) (and 4 other projects) "telepathy-butterfly crashed with TypeError in b64decode() (affects: 429) (dups: 28)" [Undecided,Invalid] https://launchpad.net/bugs/401028 [15:45] alex_mayorga: still face it? [15:46] How come this is "invalid" and apport still tells me its my bug [15:46] nigelb: yup, fully updated lucid [15:46] alex_mayorga: can give a backtrace? [15:46] bdmurray: It is that status is a block when filing the bug, and there is no explanation about what to do with it [15:47] how? [15:47] !backtrace | alex_mayorga [15:47] alex_mayorga: To get a backtrace of a failing application please read: https://wiki.ubuntu.com/Backtrace [15:47] charlie-tca: how about https://help.ubuntu.com/community/ReportingBugs ? [15:47] hi, would the color of the power off and accessibility on the login screen of lucid be considered a bug? [15:47] that is where it needs to be added [15:47] alex_mayorga: please read https://bugs.launchpad.net/ubuntu/+source/pymsn/+bug/401028/comments/60 [15:47] alex_mayorga: it's because only some 'affects' are invalid on that bug [15:47] Launchpad bug 401028 in pymsn (Ubuntu Karmic) (and 4 other projects) "telepathy-butterfly crashed with TypeError in b64decode() (affects: 429) (dups: 28)" [Undecided,Invalid] [15:48] sorry im not chirping in.. got a little busy here at work and im heading out for lunch with some colleagues [15:48] deryck: thank you :-) [15:48] nigelb: thanks, let me read all that [15:48] alex_mayorga: hehe, sorry to flood you with all that :) [15:49] charlie-tca: agree, just a link to the explanation page shoud be enough, I mean this page: https://wiki.ubuntu.com/Bugs/Status [15:49] hggdh, you're welcome :-) [15:49] I feel this bug is ready to be marked as triaged, will a member of BC please do so? https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/535097 [15:49] Launchpad bug 535097 in gnome-power-manager (Ubuntu) (and 1 other project) "Power Manager Brightness not clickable (affects: 8) (dups: 4)" [Low,Confirmed] [15:49] nigelb: no worries, glad to do my little bit of contrigution :) [15:49] err... contribution [15:49] :) [15:50] charlie-tca: I'm not following you. You don't need to do anything with status when filing a bug report. [15:50] OK, all, I added a note at the beginning of ReportingBugs (link above) about leaving a new bug as, well, New [15:50] That is what jeanfi was asking about. [15:51] bdmurray, the issue is that it is not explained directly in the bug report page, a newcomer cannot know what 'confirmed' means exactly [15:53] universal access preference button and power options button on log in screen are the same as background, can anyone confirm? [15:54] - this is in lucid [15:54] blindskull13, I will check it out brb [15:56] blindskull13, Yes it is very hard to see them [15:56] @bbordwell ok, i was wondering if that was just my system [15:57] nigelb: sorry, how would I get symbols for empaty? [15:57] @bbordwell think i should file a bug report? [15:57] https://wiki.ubuntu.com/DebuggingProgramCrash only goes up to hardy [15:57] blindskull13, yes, let post the link here when you do [15:58] ok [15:58] Im not sure what package to file that against though are you? [15:58] no [15:58] um... gdm? [15:58] hggdh: debugging symptoms is gdb? [15:59] alex_mayorga: thts for hardy and newer [15:59] blindskull13, sure, I will look into it later and if its wrong i will change it [16:00] ok [16:07] nigelb: what do you mean? [16:08] hggdh: nah, figured it out, I wanted to know how to install debugging symbols [16:09] oh, OK === deryck is now known as deryck[lunch] [16:20] nigelb: might be worth adding a note there ;) [16:21] alex_mayorga: note that its for hardy and above? [16:21] nigelb: yup [16:21] alex_mayorga: its already there "Hardy 8.04 and Newer" [16:21] nigelb: or I might learn to RTFM :( [16:21] alex_mayorga: :D [16:23] also shouldn't the apt-get change to aptitude? [16:23] nope [16:23] there is apt-get and aptitude [16:23] how are they different? n00b here, sorry [16:23] If there is a bug that involves the get help online option that is present in nearly every app what package should it be filed against? === yofel_ is now known as yofel [16:24] nigelb: o/ [16:25] alex_mayorga: oh, I dunno :D [16:30] horay! empathy runing under gdb now [16:34] nigelb: I guess I'm doing something wrong here [16:34] already have the symbols for empathy [16:34] alex_mayorga: what happened? [16:35]