/srv/irclogs.ubuntu.com/2012/07/20/#ubuntu-bugs.txt

=== TJSmith_ is now known as TJSmith
=== zyga-afk is now known as zyga
=== mapreri is now known as mapreri_
=== mapreri_ is now known as mapreri
LoTso, i was looking through "NEW" ubuntu bugs, and we have a significant number... some that are just *ancient*13:15
LoThggdh: happen to be alive?13:17
LoTwho in their right mind nominated this for "Ubuntu" directly four days ago, if its already "Fix Released"13:22
LoThttps://bugs.launchpad.net/ubuntu/+bug/73845313:22
ubot2Ubuntu bug 738453 in avant-window-navigator "[natty] taskmanager applet crashes on right click" [Medium,Fix released]13:22
LoTits an old bug too13:26
* LoT goes to poke the LP people13:26
penguin42LoT: You do get some random sets of changes in bugs and I can never figure it out, I've seen a few bugs which have just had loads of random changes, the best explanation is it's just new users not understanding, but I don't know13:28
LoTpenguin42: i've undone their fails, but i'm starting to think we need some type of a restriction for bugs13:28
LoTPERSONALLY...13:29
LoTi believe that people should be required to sign the CoC in order to *edit* bugs "affects"13:29
LoTthat way there's the requirements of a PGP key and a digital signature before they randomly modify bugs13:29
LoTmy main concern is that this user is *literally* brand new.13:29
LoTMember since:2012-07-0713:30
penguin42LoT: Yeh I've seen it on a few, it'svery odd13:30
LoTthis user only modified that one bug, too...13:30
LoThttps://bugs.launchpad.net/~xerotonin#show_id=true&show_information_type=false&show_tag=false&show_reporter=false&show_targetname=true&show_assignee=false&show_date_last_updated=false&show_datecreated=false&show_importance=true&show_heat=true&show_milestone_name=false&show_status=true&batch_key=%5B%22-importance%22%2Cnull%2Ctrue%2C0%5D13:30
LoTBLEH EVIL LINK!13:30
LoTanyways13:30
LoTi did state in my comment that if they think it was *not* fixed, then rather than reassigning the bug to "Ubuntu", they should comment "This error showed up again" or "This bug showed up again in $version"13:31
* LoT at least has the patience today to not rant at these people beyond that of typical LoT opinion0stating13:31
penguin42LoT: I've sene it before, and I've wondered if it's on purpose, but I don't get it13:32
LoTpenguin42: might be a bot13:33
LoTbut i'm thinking its something i bring up on the bugsquad mailing list13:33
LoTthis happens pretty oftenish13:33
penguin42LoT: Yeh I did a while ago13:33
LoTand i dont like it13:33
LoTpenguin42: i didnt see that, must've been before i joined13:33
LoTgot the archive?13:33
penguin42LoT: Let me see, it was in April, I was commenting on the changes to bug 80466213:34
ubot2Launchpad bug 804662 in jockey "jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 must contain only strings" [High,Fix released] https://launchpad.net/bugs/80466213:34
penguin42LoT: https://lists.launchpad.net/ubuntu-bugcontrol/msg03696.html13:34
LoTpenguin42: yeah i joined at the very very end of april :P13:34
LoTpenguin42: ah, i wasnt subscribed to bugcontrol then (wasnt a member)13:35
LoTexplains why i didnt see it xD13:35
LoTbut yeah, i think its both an issue of PEBKAC and spam13:36
LoTthat' Enki" name is familiar, but i cant place it...13:36
penguin42hey 4 letters being familiar....13:36
LoTwhere do i know that from...13:37
LoTi know it from somewhere important... was it from when i opered another network...?13:37
* LoT digs around in 5-year-old files13:38
LoTpenguin42: its mildly annoying when stuff that shows "Fix Confirmed" actually shows up in the "New" list, and its old and stale :/13:54
LoTi mean, there's this old bug in the 300ks and its still applicable for "oneiric", but apparently nobody fixed it13:55
LoT(originally reported in 9.04)13:55
penguin42LoT: Yeh there are lots of old bugs; if it annoys you, fix it :-)13:56
LoTpenguin42: if they're still applicable, i'm not touching them :P13:57
LoTbut old "Fix Released" stuff... :p13:57
LoTthat shouldnt be messed with and if it IS messed with, well...13:58
LoT*booM*13:58
LoTi'll be on it :P13:58
LoT(if/when i see it)13:58
LoTokay, now i'm more annoyed with the general userbase... :/13:58
penguin42LoT: hehe yeh, the most common reason fix released stuff gets fiddled with is that people find the same bug coming up again13:58
LoTbecause apparently people think that every failed config file they set up is a bug13:58
penguin42LoT: Now now, can't get annoyed with them!13:58
* LoT grabs the invalidation keys for the teams he's on13:59
LoTthese "invalid" bugs are not bugs!13:59
LoT(they're on projects, which i manage, so... not bugcontrol or ubuntu)13:59
LoTpenguin42: when you see twelve bugs that arent bugs on an upstream project, all within a minute of each other...13:59
LoTand they're random failed config files that the users wrote...14:00
* LoT shrugs14:00
LoTi've never seen that much spam hit my inbox at once though14:00
LoT(and when i have, its only ever been when the Russians bombarded my email server, and the spam filters couldnt keep up14:00
LoT_14:01
LoTBLEH, keyboard's on the fritz again14:01
penguin42LoT: OK, so why are the users making so many config screwups and reporting them as bugs - are the error messages it creates not helpful enough?14:01
LoTpenguin42: you mean like "$configargument is not valid within a $container section of the configuration"?14:01
LoTwhere $configargument is some random item14:01
LoTand $container is a block of config that relates to a specific part of the program14:02
LoTbecause that's the errors they're getting.. but the error even says it cant be used14:02
LoTand it also says refer to documentation14:02
penguin42ah, not much you can do about that then :-)14:02
LoTnope14:02
LoTexcept mark the bugs as notbugs and then convert to questions, then say "Please refer to the documentation, as the error states."14:03
LoTand then they email me and are like "But I followed the docs..."14:03
LoT"Did you read the section that says "Valid only in"?14:03
LoT"Ohh.... no...?"14:03
LoT*facepalm*  "Go read it"14:04
LoT(typical post-convert-to-question email chain)14:04
hggdhLoT: I am here now :-)14:05
LoThggdh: heh, was going to ask you for the link to the source for your bot's "Announce" function, but then i dug up something that works better14:06
hggdhheh14:06
LoThggdh: was in this channel instead of the -announce channel (irssi is evil that way)14:06
* penguin42 goes to get a new audio lead - just being able to hear the left channel is annoying14:09
LoToh god, this playlist came up again :/14:09
LoTi dont like this playlist much, its great for when i'm playing first person shooters...14:11
LoTbut that's because this playlist makes me a tad more evil (perfect for FPS games)14:11
penguin42ah stereo16:34
LoTpenguin42: enjoy it while it lasts16:39
LoT:P16:39
penguin42LoT: With these leads probably not too long :-(16:43
=== jdstrand_ is now known as jdstrand
PaddyLandauHello. I have reported bugs before using ubuntu-bug. However, how do I report a bug when it is about the installation itself?18:46
penguin42PaddyLandau: Report it against the package ubiquity18:48
penguin42PaddyLandau: How far does the installation get?18:49
penguin42(and which install image are you using?)18:50
PaddyLandauI am installing 12.10 alpha. It is only a minor problem.18:55
PaddyLandauCosmetic, not a show-stopper.18:55
PaddyLandauThe image is the 64-bit standard desktop.18:55
penguin42ok, cool, then I'd probably do it after installation, just do an   ubuntu-bug ubiquity18:56
PaddyLandauThank you. I'll do that.18:56
penguin42np18:56
njinhallo, can someone verify if bug 1027207 is a dup of bug 1012906 (private) for me ? thanks in advance19:58
ubot2Launchpad bug 1027207 in ubiquity "Ubiquity 2.11.17 (oem-config) crash in console-setup" [Undecided,New] https://launchpad.net/bugs/102720719:58
=== yofel_ is now known as yofel

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!