[00:05] hi rusivi [00:05] hggdh: hello [00:09] rusivi: I cannot find your mentorship request -- do you have a date to give me? [00:09] i.e., when you sent it in [00:10] hggdh: must have mis-sent [00:12] hggdh: I just sent a fresh request 2 secs ago via https://launchpad.net/%7Ebugsquad-mentorship/+contactuser [00:13] rusivi: cool, thank you. [00:13] rusivi: one of us will get it ;-) [00:14] hggdh: np === evilnhandler is now known as nhandler [00:22] interesting. I get a bug email every so often -- so far, so good. Then, suddenly I get 50/70 of them [00:23] usually by EOD (Texas-style) [00:24] hggdh: 80/20 theory [00:24] heh [00:24] Also explained my Murphy's law of inbox [00:24] hggdh: ^^ [00:24] rofl === nhandler_ is now known as nhandler [00:25] s/my/by [00:28] yeeee, thunderstorm arriving [00:28] plars: Did you get the calendar stuff taken care of? [00:28] Is there an alternative to `recordMyDesktop` for recording how the desktop is behaving? [00:28] err hggdh ^^^ [00:29] nhandler: no, I did not (yet) [00:29] hggdh: What needs to get changed? [00:29] nhandler: mind to update the bugsquad meeting to 1700UTC? [00:30] intrader: there is byzanz iirc [00:31] yofel, I will look that up, `recordMyDesktop` is not useful . Where should I find it, and why iirc? [00:32] hggdh: Check it out now [00:34] intrader: haven't used it in ages, but iirc byzanz did desktop recording [00:35] nhandler: excellent, thank you [00:35] * hggdh owes nhandler. Again. Pretty big tab now :-) [00:35] yofel, I am unable to find it - what is 'iirc byzanz'. I find lots of BMWs with that brand [00:36] If I Recall Correctly [00:36] hggdh: Don't worry about it ;) [00:37] lifeless: thanks, my fault [00:37] !info byzanz [00:37] yofel: byzanz (source: byzanz): Small screencast creator. In component universe, is optional. Version 0.1.1-4 (lucid), package size 79 kB, installed size 408 kB [00:42] yofel, I am unable to do `info byzanz` - must have no info on it. I will try the Synaptic Package Manager [00:42] intrader: '!info' was a bot command, the application is simply called 'byzanz' [00:44] yofel, `which byzanz` gives me nothing, and the package manager shows it installed. [00:45] dpkg -L byzanz shows: [00:45] /usr/bin/byzanz-record [00:45] /usr/bin/byzanz-playback [00:50] yofel, `dpkg -l byzanz` gives a whole slew of stuff, and /usr/bin/byzanz-playback is not there. [00:51] ok, let me check lucid, I'm using maverick here [00:51] also it's '-L' not '-l' [00:52] hm, seems like lucid only has byzanz-record [01:08] yofel, it does record (but no sound), The playback is by 'Eye of Gnome' - whatever that is. [01:09] eye of gnome = eog = the default image viewer in ubuntu [01:10] maco, never had heard of it, thanks - it is able to see the animation by byzanz [01:20] yofel, how do I upload the file for your viewing of highlighting problem [01:22] yofel, I will add it to the bug report - let me know of another way, thanks [01:32] yofel, the bug is 631130 - I have unloaded a recording of the 'hightlight bug' [01:33] yofel, I wil try to record the problem with the scrollbar. [01:36] http://forums.opensuse.org/english/get-help-here/pre-release-beta/419673-about-kde-kmix-pulseaudio.html [01:37] so how can I have the ubuntu desktop installed and not have pulse ocnflicts running kubuntu 10.04 [01:37] conflicts [01:42] my sound is always muted upon reboot and the kmix volume slider is quarky at best [01:43] tes [01:43] t [01:53] Jofel, I have also recorded the 'scrollbar problem' and uploaded to bug 631130. [01:53] Launchpad bug 631130 in opensuse (and 3 other projects) "In all apps, slow UI since 10.04 install (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/631130 [01:53] Hi can somebody mark bug #638540 as wishlist please? [01:53] Launchpad bug 638540 in openoffice.org (Ubuntu) "Incorrect use of quotes in OpenOffice dialogs (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/638540 [01:54] oh hey, that's a handy little bot [02:19] so when looking for bugs to triage should I just look through the ones marked as new or what? I'm kind of new at this [02:20] Can someone please check bug 44374 for Won't Fix status? [02:20] Launchpad bug 44374 in multisync (Ubuntu) "multisync can't connect to evolution (heat: 14)" [Medium,Incomplete] https://launchpad.net/bugs/44374 [02:26] Pizack: wishlisted, and yes, we look at new bugs, if you're new to triaging, start with packages you're familiar with [02:38] bug 638524 [02:38] Launchpad bug 638524 in coreutils (Ubuntu) "The size of a named pipe created by mknod or mkfifo always zero. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/638524 [02:38] er, what? [03:51] rusivi: hi [03:51] rusivi: baltix is not Ubuntu [03:51] rusivi: oh, sorry, I see the bug has too many subscribers, ignore my comment. But is triaged in Ubuntu, so Im' not sure why you're just asking on it. (https://bugs.edge.launchpad.net/ubuntu/+source/gdm/+bug/41170) [03:51] Launchpad bug 41170 in baltix (and 2 other projects) "The typical user will not know how to make some free disk space when he cannot log into a graphical desktop (affects: 4) (dups: 2) (heat: 44)" [Undecided,Incomplete] [03:52] lifeless: np [03:52] lifeless: ty for reviewing my changes! [03:52] I'm pretty sure you shouldn't be changing the Baltix bug status when asking about Mverick [03:52] baltix is not Ubuntu [03:53] also, asking about triaged bugs isn't helpful. [03:53] *testing* triaged bugs is helpful. [03:55] lifeless: hmmmm I checked out their Overview page and it seems Baltix is a language translation of Ubuntu? [03:55] It is a separate project. [03:55] its a different distro [03:55] Yes, it builds on Ubuntu, but it has its own releases and so on. [03:56] lifeless: Shouldn't they have their own website like Sabily, Linux Mint or similar Ubuntu derivative? [03:56] rusivi: they do; but they use Launchpad for bug tracking. [03:56] lifeless: ah [03:56] rusivi: launchpad is for much much more than just Ubuntu. [03:56] lifeless: Couldn't they just use Sourceforge? [03:56] rusivi: they can use Launchpad [03:56] rusivi: why couldn't they use LP? [03:57] rusivi: why would they want to use Sourceforge instead? [03:57] rusivi: lp serves the same purpose as sourceforge [03:57] i use lp for my project... dont like cvs or svn, so why would i use sf? and git.kde.org isnt up yet... i like bzr, so i use lp [03:58] lifeless: hehe I'm not trying to exclude anyone from Launchpad... just trying to understand where Baltix has it's place on Launchpad [03:58] rusivi: one thing is actually very important (what lifeless already said): LP is for many other projects, out of Ubuntu [03:58] Ubuntu is just one of them. We have to be careful not to step on bugs from other projects [03:58] hggdh: Got it. I'll avoid their packages for the time being. [03:59] hggdh: Got it. I'll avoid their bugs for the time being. [04:01] rusivi: I think its important you start looking into bugs. Not just asking 'is it fixed in maverick'. [04:01] rusivi: *most open bugs are not fixed in maverick* [04:01] rusivi: you are wasting many many peoples time just asking if the problem still exists. [04:03] lifeless: I only ask that if the underlying package bugged has been updated since the last time someone commented about it in the Ubuntu version mentioned. [04:03] rusivi: do you try reproducing it yourself first? [04:04] maco: If I can I do. If eq dependent looking for reporter to test. [04:04] maco: or whomever else has same/similar eq [04:04] eq? [04:05] maco: equipment, ex. samsung mobile phone trying to bluetooth sync [04:05] ah ok [04:05] * maco read "equaliser" ;-) [04:05] I don't have one so on the reporter or whomever has one needs to step up and let us know if still a problem [04:05] maco: hehe [04:05] rusivi: actually its the other way around [04:05] rusivi: because *most* bugs are not closed in each release [04:05] rusivi: we know statistically that *most bugs still exist* [04:06] we should look for evidence from *our side* that the bug is fixed before asking for confirmation. [04:06] rusivi: otherwise we're just wasting the reporters time. [04:06] rusivi: I'm really glad you want to help. [04:06] lifeless: yes, I was flamed for marking fixed without testing myself, I have stopped doing this. [04:06] rusivi: good. please stop asking 'is it fixed yet' too. [04:06] If its hardware dependent, check the driver code to see if its fixed before asking. [04:07] if its not hardware dependent, check it yourself. [04:07] lifeless: Well I'm not just spamming them for an update. I'm just checking if fixed if new package has been pushed out. [04:07] Yes, this means you will touch less bugs. [04:07] rusivi: trust me, you're spamming. [04:08] lifeless: I understand your viewpoint on this, but if the reporter has more knowledge on this issue, it seems wasteful to reinvent the wheel and try to reproduce when they are experiencing it firsthand and know what to look for. [04:08] launchpad is totally capable of sending out a mass email to every bug that has had a new package upload asking for confirmatio that its still a bug, if we thought that was a useful thing to do. [04:08] rusivi: Unless we have reason to believe that its fixed, we're *wasting their time*. [04:09] lifeless: Understood but not doing so doesn't get the bug addressed/fixed faster :P [04:09] rusivi: I've had several folk thank me for following up on *just one* of the bugs you commented on - and I bet you haven't even seen the comment because you're not subscribed to it. [04:09] rusivi: no, but if more people complain it will get you locked out of launchpad. [04:10] rusivi: which would be sad, because you want to help, and I want you to help. [04:11] lifeless: hmmm, I am definitely trying to be judicious in my bug zapping. If someone considers it spam that a bug that is years old had someone ask if this is fixed in a new package seems duly noted but at least someone is addressing it! [04:11] but asking if its fixed is -not- addressing it. [04:11] checking if it is fixed by *testing* is addressing it. [04:12] lifeless: I understand your viewpoint on this but I disagree with it. The reporter does have some responsibility to fix the bug they bugged in the first place unless they don't have the capability to do so. [04:12] lifeless: if that's the case it's usually where the devs takeover and work on it for them. [04:13] I don't think you understand how bugs in Ubuntu generally progress [04:13] :( [04:13] lifeless: when I make a bug anytime someone asks for info I'm on it like white on rice, either giving them info desired or explain outside of my sphere of knowledge. [04:13] yes, reporters are responsible for confirming that a fix is indeed a fix. [04:13] rusivi: that's not the viewpoint of Ubuntu Bug Control, if there is sufficient information to reproduce, we try not to bother the reporter unless we need more information [04:14] micahg: is this posted in one of the Ubuntu doctrines I missed or just creating on the fly? [04:14] rusivi: but if we don't know that its fixed, or even have reason to *think* its fixed, then we're just going to annoy the reporter and they will unsubscribe/close it - and the defect *will still be there* [04:15] rusivi: https://wiki.ubuntu.com/Bugs/HowToTriage#Actions [04:15] micahg: i'll review again sec [04:17] micahg: As per provided link: "There will be a few bug reporters who never get back to you and there is not enough information for the bug to be worked on. You will also want to mark those bugs as Invalid. " [04:17] rusivi: *if* there is not enough information [04:18] micahg: it sounds like we're boiling down to opinion, not my unfamiliarity with the doctrines linked [04:18] rusivi: no, with policy and this is almost becoming a CoC issue IMHO [04:18] : Granted, I think you guys are the pros, I'm the newb and I try to defer to you. [04:18] micahg: CoC? [04:18] rusivi: Code of Conduct [04:20] micahg: Well I'm definitely trying to cooperate with you but you have referenced links that are vague regarding the issues mentioned recently. [04:20] micahg: it's a little RTFM/gentoo'ish to be quite honest ;) [04:20] rusivi: one of the questions for confirming a bug is if there is can you reproduce the bug yourself (which means to try to reproduce) [04:21] rusivi: the section you quoted was for 'incomplete bugs' [04:21] rusivi: not 'confirmed' or 'triaged' [04:22] rusivi: you are asking these questions on 'confirmed' and 'triaged' bugs. [04:22] lifeless: regarding triaged bugs I changed my bad I stopped doing that :D [04:22] lifeless: Duly noted won't happen anymore on the triaged ones :) [04:22] rusivi: we believe everyone's time is valuable, ours and the reporter's, therefore, if the reporter was kind enough to give us steps to reproduce, we attempt to do so [04:23] lifeless: I took micahg's advice and I am only focusing on New or Invalid bugs not in wishlist status without patches [04:23] if the triage documentation implies otherwise, please let us know where so we can fix it [04:24] rusivi: I was responding here to a change to a confirmed bug [04:25] rusivi: this might help as well: https://wiki.ubuntu.com/Bugs/HowToTriage/Charts [04:26] micahg: duly noted. [04:26] micahg: good chart [04:28] Indeed. [04:29] It seems a place should exist for a different type of bug zapping. Below triage'ers but above spammers [04:29] Has this been discussed anywhere? [04:32] Otherwise I'm gonna grind a while on way few less bugs instead of providing more tailored above-spam, below triaging "advice" [04:32] Not triage but bug advice or something like that [04:34] Does this topic fit more a Brainstorm or is their another platform for disputing Triaging procedures? [04:35] rusivi: disputing procedures? You can bring it up in the bugsquad mailing list [04:35] micahg: k well do for sure [04:36] micahg: I like the mechanisms set in place I just see the "advice" idea being very helpful in moving bugs forward to Fixed Release status [04:36] micahg: for those who are not in a position to triage [04:37] rusivi: what do you mean? [04:39] micahg: well the "no equipment equivalent to reporter available", End of Life release bugs, old package issues, years of inactivity, just to name a few [04:40] years of inactivity just means years of inactivity [04:40] its got no deeper meaning. [04:40] rusivi: no equivalent equipment you skip, end of life you evaluate if the bug still applies [04:40] micahg: k [04:41] rusivi: there should be responses on the responses page for these types of bugs https://wiki.ubuntu.com/Bugs/Responses [04:42] micahg: let me check that [05:08] micahg: just installed firefox-lp-improvements holy cow this is well done! [05:10] rusivi: you might want to check the responses page first for the prerequisites for the responses before using then until you are familiar with the preconditions for them [05:11] micahg: yes their is a small pop-up when one hovers the mouse icon over each response [05:11] micahg: I'm definitely reviewing for sure [05:11] yes, that just lets you see the text though [05:56] rusivi: for the version specific tasks, once the release is EOL, the task is Invalid or Won't Fix [05:57] micahg: got it! [06:04] (or decline, if it was nominated) [06:07] Can someone please look at bug 78182 for wishlist or triage? [06:07] Launchpad bug 78182 in mc (Ubuntu) "mc should warn prior to attempting to copy a file >4 GB to vfat partition instead of crashing (dups: 1) (heat: 13)" [Low,New] https://launchpad.net/bugs/78182 [06:13] rusivi: can you check to see if it's still the case? [06:13] or rather doesn't warn [06:16] actually, the upstream dev is subscribed, I should ask in the bug if this is still needed [06:17] micahg :) [06:17] rusivi: or you could ask the upstream dev, Yury V. Zaytsev in the bug if this is still needed and should be upstreamed [06:18] micahg I can ask if you like no big deal [06:18] rusivi: I can do it, just offering you the chance if you like [06:19] Sure I'll ask one sec [06:21] micahg: done [06:21] thanks [07:45] rusivi: why are you trying to use a standard reply on a debian bug task? [07:48] micahg: your asking about bug 638681 ? [07:48] Launchpad bug 638681 in launchpad-gm-scripts "firefox-lp-improvements does not input standard or custom replies (affects: 1) (heat: 6)" [Undecided,Invalid] https://launchpad.net/bugs/638681 [07:49] yep, just added a comment [07:52] micahg: Well whether I applied a custom or standard reply does not seem the issue. I was unable to apply either to it. Problem exists in firefox-lp-improvements [07:52] rusivi: yes, but standard comments shouldn't be needed on upstream tasks where launchpad isn't the tracker [07:52] or any lengthy comments for that matter [07:53] micahg: Fair enough on that. I'll avoid the debian bugs moving forward. Won't someone who works on these bugs find a custom script helpful? [07:53] rusivi: they're just linked, no one "works" on them per se [07:53] Debian has their own tracker [07:54] micahg: bug 11743 does not have an upstream bug link... [07:54] Launchpad bug 11743 in linux-restricted-modules-2.6.15 (Debian) (and 1 other project) "nvidia-glx-config suggests invalid command (heat: 4)" [Undecided,Invalid] https://launchpad.net/bugs/11743 [07:55] rusivi: yes, someone added a task seemingly for no reason [07:56] or wanted it upstreamed, but never did [07:56] micahg: looks like I was right for the wrong reason?! [07:57] rusivi: you were correct to set to invalid, just the lengthy comment wasn't necessary, you could've just said, this is an old bug and there doesn't seem to be a need to upstream it anymore [07:57] micahg: I'll leave the script bug invalid unless someone else who works on debian bugs feels compelled to speak or I ever get to the point where I'm working on deb bugs [07:57] or something to that effect, Closing Debian bug task due to age and no bug linked [07:58] rusivi: debian bugs aren't triaged in LP, just linked [07:58] micahg: k [08:17] hey everyone [08:17] https://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly/+bug/622777 was fixed upstream! [08:17] Launchpad bug 622777 in telepathy-butterfly (Ubuntu) (and 1 other project) "telepathy-butterfly crashed with UnicodeDecodeError in _handle_UBX() (affects: 67) (dups: 21) (heat: 378)" [Medium,Triaged] [08:18] how do we get the fix on the updater? [08:32] sorry had to reboot [08:32] Tetsuo55: hey, [08:32] so what can we do about 622777 [08:32] I just updated the bugreport you mentioned a few minutes ago [08:32] ok thanks [08:33] in short, the issue should be already fixed in maverick [08:33] ok so the updates that just made me reboot should have the fix [08:33] nice [08:34] then that just leaves the flash crashes and then maverick will be stable for me [08:38] the bug is still half open, is that normalo? [08:44] its still open for the other packadge thekorn [08:44] Tetsuo55: what do you mean? [08:45] if you look at the ticket again [08:45] only the upstream bug watch is not closed [08:45] yes that [08:45] it will be closed by one of the next automatic updates [08:45] but the package task is closed [08:45] and that's the only important bit for ubuntu [08:45] ahh ok [08:53] rusivi: please don't close bugs just because the version reported is EOL [08:55] micahg: You told me earlier that I can mark invalid or won't fix due to EoL... [08:55] rusivi: no [08:55] micahg: Ok. What would you rather see? [08:55] rusivi: I said if the task is version specific (i.e. Ubuntu Dapper) [08:56] rusivi: if there are steps to reproduce, try to reproduce, otherwise, there's a response on the repsonses page [08:56] rusivi: and even Dapper isn't EOL except for desktop [08:57] micahg: My mistake, misunderstood. I did notice that Dapper Server still supported [09:01] rusivi: regarding bug 85531 why would you mark it Fix Released on a package that no longer existed? [09:01] Launchpad bug 85531 in libflash (Ubuntu) (and 1 other project) "Firefox Crashes with no warning after load web page (heat: 10)" [Undecided,Fix released] https://launchpad.net/bugs/85531 [09:03] micahg: sorry, this was pre-being flamed for not checking bug fixed myself, I stopped that. [09:06] so ndiswrapper is a 64bit shell around 32bit binary flash? [09:06] Tetsuo55: yes [09:06] does that mean that its crashes are fixable on the ndiswrapper side? [09:06] oops [09:06] Tetsuo55: you mean nspluginwrapper? [09:06] yeah [09:06] ndiswrapper is a wrapper around windows drivers [09:07] so its wrapping the 32bit windows flash binary [09:07] :S [09:09] Tetsuo55: no, the 32 bit linux flash binary [09:11] ok [09:14] i wonder if we can simply use the chromium built in flash [09:15] Tetsuo55: no, we don't use the chrome flash AFAIK [09:18] rusivi, same comment than micahg for bug 103073. You should have reproduced it and see that it's still an issue instead of closing it as invalid. [09:18] Launchpad bug 103073 in debconf (Ubuntu) "terminal used for package configuration blocks (heat: 2)" [Low,Confirmed] https://launchpad.net/bugs/103073 [09:19] rusivi, the right action for this bug is to 1. Reproduce (that's easy, simply configure a package with a debconf question and the dialog frontend) [09:19] jibel: sorry, this was pre-flame [09:19] rusivi, 2. The description need to be updated because it doesn't describe the problem very well. [09:19] jibel: I stopped it [09:20] rusivi, don't hesitate to ask, we are here to help. [09:20] jibel: ty [09:20] jibel: what description do you recommend? [09:23] rusivi, something like "debconf doesn't display which key to press" [09:24] jibel: Sounds good to me. Would you like me to change the description? [09:24] rusivi, yes please do. [09:25] jibel: done [09:27] rusivi, thank you for your help. [09:27] jibel: :D [09:31] rusivi: just out of curiosity.. how many bugs did you comment on in he past one day? :) [09:31] in the* [09:32] rusivi, also, you should subscribe to the bugs you are touching. [09:32] rusivi, this way you can follow up with the commenters. [09:34] jibel: ty for your suggestion [09:35] rusivi: have you applied for mentorship? [09:36] vish: I did send a fresh application today [09:36] ah.. cool! [09:36] vish: 700+ [09:36] * vish checks [09:36] vish: sorry that's over the last 3 days [09:36] vish: sooooo ~ 333 [09:37] rusivi: its nice to see some active members , i think we should get you a mentor right now.. :) [09:37] vish: Well if you say so! [09:39] rusivi: i checked your lp for approving your membership in the mentoring program.. but we need some info to assign you a mentor.. [09:39] rusivi: have you read the wiki: https://wiki.ubuntu.com/BugSquad/Mentors ? [09:39] rusivi: "How To Request a Mentor" section? [09:40] vish: I did, the only thing I noticed I thought I was missing was a wiki [09:41] rusivi: the yeah wiki is important , since it needs to be filled with the time available info [09:41] rusivi: once we know the time available , we can assign you a mentor [09:42] vish: Yeah, that's gonna be tough b/c I'm not looking to make such a firm commitment. I'm on a 2 week vacation (started 3 days ago) so I'm willing to go strong for the entire time. After that, I'm only going to focus on those bugs I touched/bugged personally or know how to fix. [09:43] vish: sorry but Canonical doesn't pay my bills :P [09:43] vish: jk [09:44] rusivi: np.. ok.. i think 2weeks with amount of activity you are doing can still benefit from a mentor.. [09:44] vish: I agree. [09:44] rusivi: btw, its not a commitment ;) [09:44] hi [09:44] rusivi [09:44] jwb_: hello [09:45] vish: I'm not even going as far as time available [09:45] can you kindly go back on all those dozens of bugs you set to incomplete and set them back to confirmed where they belong? [09:45] because it's really really really super annoying to have to do it myself [09:45] jwb_ can you give me an example of one which should not have been marked incomplete? [09:45] #19125 [09:46] #11899 [09:46] etc [09:46] bug 19125 [09:46] Launchpad bug 19125 in cdparanoia (Debian) (and 1 other project) "Package libcdparanoia0-dev pollutes /usr/include with ambiguously-named header files (affects: 1) (heat: 8)" [Unknown,Confirmed] https://launchpad.net/bugs/19125 [09:46] they all have perfectly obvious steps to reproduce which you did not bother trying before setting them to incomplete [09:47] if the bug has steps to reproduce, you should try it before setting them to incomplete. a confirmed bug is confirmed until it can no longer be reproduced [09:47] how did you eve decide to set these to incomplete? just because they are old? [09:48] Honestly, I've been flamed by micahg about Debian bugs, I'm avoiding those altogether moving forward. [09:48] rusivi: I did not flame you [09:49] micahg: jk [09:49] i am honestly curious why you thought screwing up my bugs was a great idea [09:51] jwb_ hey sorry didn't mean to get you all worked up about it :) I'm a little new to bug zapping as you noticed [09:52] micahg: this is an example of where that "advice" scenario fits in nicely [09:52] rusivi: I still don't get what you mean [09:53] micahg: above spam, below triage [09:53] ? [09:53] micahg: sub-triaging bugs [09:53] micahg: but not just spamming for updates [09:54] rusivi: we give guidance in here when people ask [09:55] jwb_ It's really not that big of a deal, your the professional and reporter, just wanted to see if this was still active [09:55] i don't want to have to play whack-a-mole with all my launchpad reports just because there's a new version of ubuntu [09:55] bugs should only change state for a _reason_ [09:56] jwb_: we tell that to people when they come and ask [09:56] reasons including no longer reproducible, or someone committed code that we reasonable expect fixed the problem [09:57] i'm picking on rusivi but it's actually a project-wide problem of people setting bugs to incomplete for no particular reason [09:57] jwb_ I agree that just b/c a new ubuntu comes up, a status update should be asked for. However, regarding 19125 no comments since Intrepid, and current version in Lucid that was my reasoning [09:57] jwb_ please pick on me helps me learn ;) [09:58] jwb_ I mean just b/c new ubuntu, a status updates should not be asked for. [09:58] jwb_ mistyped [10:00] jwb_ current version = current package version [10:00] ok rebooting into maverick [10:00] bye [10:20] bug #11899 [10:20] Launchpad bug 11899 in vim (Ubuntu) "Cannot recover unsaved email after system crash (heat: 8)" [Medium,Confirmed] https://launchpad.net/bugs/11899 [10:49] uhm, i have a doubt [10:49] i'm gonna report one (actually more) bug about unity [10:50] ubuntu-bug is only for ubuntu bugs, right? [10:51] if that's so... should i use some apport-collect program/something to collect information about my system for these bugs? [10:51] Tiibiidii: ubuntu-bug is for anything in the ubuntu repositories [10:51] i remember that the instruction for using apport-collect where present in the bug reporting page, but it seems that for unity it's missing [10:52] ok, but unity is a separate project [10:52] so, shouldn't the unity project be used as the first stop for reporting bugs? [10:53] should all the bugs be reported to the ubuntu package of unity and then (optionally?) add this also to the unity project? [10:54] rusivi: why are you still asking if bugs are still occuring when there are steps to reproduce? [10:55] micahg: which bug specifically? [10:55] bug 111231 [10:55] Launchpad bug 111231 in thunderbird (Ubuntu) (and 1 other project) "Sending an attachment from the command line with a "ë or ä" in the filename does not work! (heat: 2)" [Low,Incomplete] https://launchpad.net/bugs/111231 [10:58] micahg: sorry about that, will attempt to reproduce moving forward [11:20] === ivoks-afk is now known as ivoks [14:04] Guys? [14:04] ironicdemise [14:04] Hey, sorry a bit new to the IRc [14:07] I don't want to sound stupid or anything, this is my first time on the irc. [14:07] Can anybody tell me why registering my nick won't work because my emails are invalid? [14:07] As in, they are valid and irc won't accept them. [14:20] ironicdemise, don't know... actually i find irc outdated and crappy [14:21] i don't know what your email address is, but keep in mind that validating an email address is almost impossible to do correctly: [14:21] http://haacked.com/archive/2007/08/21/i-knew-how-to-validate-an-email-address-until-i.aspx [14:21] Well outdated it must be, but I guess it's got some uses and I don't want to just "assume" it's not worth my time... [14:22] (in the meaning that, almost every validator is too strict, and at the end you have to assume it works, and try that mail on the field) [14:22] Well outdated it must be, but I guess it's got some uses and I don't want to just "assume" it's not worth my time... <-- yesyes, that's the problem... everybody's using it ;) [14:23] however, tipically you don't register the nick with "irc" [14:23] you register the nick with a bot managed by the guys who keep the irc server online [14:23] bye? [14:24] that is, the NickServ [14:24] lol, xchat crashed [14:24] aha, so do I just register the nick each time? [14:24] (using pidgin) [14:24] mhn, no [14:24] i don't use pidgin [14:25] it was quite bad for irc as far as i remember [14:25] yeah nickserv just shot a "invalid email" at me [14:25] it "seems" fine so far, but I don't know what to expect [14:25] mhn, i don't know... that's all it says? "invalid email"? [14:25] there are no strange characters? [14:26] maybe you're better off trying to ask in #freenode [14:26] flamm, have you tried doing your nick yet? [14:26] it's got a period [14:26] I will do, I will do. [14:26]