[02:31] does anyone here have issues logging in to gnome-shell? [02:31] it always hangs for me, for times ranging from a few seconds to minutes [03:21] bdmurray: Can I mark bug #1 as fix released? http://irclogs.ubuntu.com/2012/05/01/%23ubuntu-classroom.html#t21:50 [03:21] lfaraone: https://bugs.launchpad.net/ubuntu/+bug/1 (Not reporting large bug) [03:23] lfaraone: nope, you cant do anything with bugs for now [03:23] the LP site is broken with bugs and package pages [03:24] according to the launchpad channel, its been escalated internally within the canonical peoples. we're kinda stuck until then, afaict [03:24] haha [03:25] fascinating. [06:21] hello, wich package manage ASPEED driver ? xf86-video-ast is not existing as package in ubuntu. thanks [12:57] Hello, which package manage 'aspeed' drivers, xf86-video-ast isnot an ubuntu package, can I assign to xserver-xorg-video-all ?? thanks [13:04] Hi there I am trying to track a bug down which has been apparent on my system from atleast 10.04LTS, and is still with me in 12.04LTS. Its to do with the wireless and the failure to associate with an accesspoint first try, it will only connect if I first connect to another AP then back again. In the WPA suplicant logs the only difference I can see is the failure to receive a second MLME event frame === zyga_ is now known as zyga === yofel_ is now known as yofel [15:02] hi all [15:03] I have a big problem with pbuilder [15:03] I can package a program, but i do not see it [15:03] can some one help me? [15:13] please help me... how can I solve it? [15:14] alo21: what do you mean by do not see it? [15:15] roadmr: I Cannot find the .deb file [15:15] alo21: also, it sounds like the folks in #ubuntu-devel may be more knowledgeable about packaging, unless you think it's an actual bug [15:15] roadmr: i try there.. thanks [15:16] alo21: per the doc, the products (binary and source packages) are in /var/cache/pbuilder/result [15:17] alo21: I don't know, just what I read here: https://wiki.ubuntu.com/PbuilderHowto === zyga_ is now known as zyga [16:11] anyone here on bugcontrol able to handle an importance chagne?> [16:14] EvilResistance: sure, whatcha need? [16:14] if someone on bugcontrol can handle this, that'd be awesome (This was originally pointed at in #ubuntu-server, approx. 5 minute before i posted this here): LP Bug 932064. Importance change to: High. Reasoning: (1) PRevents the application from working and operating. (2) Has a severe impact on a small number of ubuntu (server) users. [16:14] Launchpad bug 932064 in amanda "amtape crash" [Undecided,Confirmed] https://launchpad.net/bugs/932064 [16:14] roadmr: that [16:15] refer to #ubuntu-server logs for about 5 minutes ago to see where this was poked upwards (since i lurk there, i intercepted it) [16:16] (my LP id if it makes any difference is trekcaptainusa-tw, in case you want to refer that this was recommended by myself) [16:16] EvilResistance: done, set to high :) [16:16] thanks much [16:17] no prob :) [16:18] there are days where i'd love to have bugcontrol :P [16:19] but i dont have the qualifications yet :P [16:19] EvilResistance: I've handled two importance changes for you and I agree completely with your criteria, keep track of those reports and I'm sure you'll be able to showcase them when you apply [16:22] roadmr: micahg also handled one of my importance change requests, too, so eventually i'll apply when i feel i've got enough credentials for applying :) [16:22] EvilResistance: awesome! [16:22] and before that i've had a few triage handling requests done, but those weren't logged with my IRC name or LP ID [16:23] oh :/ [16:23] now if only I could get wifi on the train, today, then i could continue to do bugsquad duties :P [16:23] hehe thanks for the help :) [16:23] indeed [16:26] roadmr: to be frank, i could just download the past month's logs for here, and grep them for any time i've said anything, since all the triage recommendations, and bug importance change reocmmendations exist in those logs [16:26] and my LP profile shows this as one of my IRC nicks on freenode :p [16:30] roadmr: quick question, if i may [16:31] EvilResistance: sure! [16:32] if/when I do choose to apply to bugcontrol, where is the methodology for applying listed? [16:32] EvilResistance: see here: https://wiki.ubuntu.com/UbuntuBugControl [16:32] EvilResistance: all needed information is there :) [16:33] mmkay, and one last question (I brought this up with micahg during UDS, but it may need an additional person to push it through in the next bug squad meeting) [16:33] regarding this: https://wiki.ubuntu.com/Bugs/Importance [16:33] and regarding all references to "Core application" vs "Non-core Application" [16:33] what is a core application defined as? [16:33] * EvilResistance hasnt found any clear definition yet [16:34] hehe yes, I haven't found a definition, I basically consider any application that's included in the default install and apply some additional criteria (i.e. some included apps are not so useful so I don't consider them core) [16:35] then as a general rule-of-thumb, should i consider anything in universe or multiverse non-core, and main as core (unless i hear otherwise)? [16:37] and if its in the default installs, its definitely core :P [16:37] (also, this should be better defined, IMO, in the bugs documentations) [16:37] s/bugs documentations/documentation about bugs/ [16:38] roadmr: and one final question: [16:39] if a bug has been filed against a package, but that bug later turns out to not be a bug, but some other issue which would make the bug "Invalid", but the bug is marked as Confirmed because someone else marked it as having affected them, what should I do? [16:39] or rather, what would be recommended [16:40] change it to invalid, change it to opinion, or leave it as confirmed? [16:40] (hypothetical that happened to come up recently)\ [16:45] EvilResistance: I agree that we need better definitions for coreness. Are you in the bugsquad mailing list? that's a good place to bring it up and start a friendly discussion [16:45] EvilResistance: if the bug is indeed invalid, I'd set as such, and add a note explaining why it's invalid, which should help other affected users fix their situation [16:46] even if its set to "Confirmed' by the time i get to it? [16:48] (and of course, if its invalid against a specific package, but valid against another, then changing what the "affects" so the correct package is filed against would be the fix) === zyga_ is now known as zyga-afk [16:56] EvilResistance: yes, a confirmed bug can be set as invalid [16:56] EvilResistance: even more so when automatic confirmation is done for bugs affecting multiple users; if the bug turns out to be invalid, it takes a human to make that call but it's not outright incorrect [16:57] EvilResistance: the statuses call for using "invalid" with caution, but if you're sure it *is* invalid, there's no problem with it [16:57] EvilResistance: of course, if it's invalid for one package but valid for another, the status should reflect that, either by moving the bug to the appropriate package, or by having several affected packages [16:57] indeed. what about bugs that just arent bugs, like bugs which are filed but are really just requests for support and not actual bugs [16:57] mhm [16:58] EvilResistance: hmm those should be converted to questions on answers.launchpad.net, or pointed to askubuntu.com, but the bug itself should be marked invalid if it's determined it's not an actual bug [18:42] https://bugs.launchpad.net/ubuntu/+bug/999386 [18:42] Launchpad bug 999386 in ubuntu "Disk access locking whole PC" [Undecided,New] [18:42] How do I set it to "ubuntu-bug storage" as suggested by the wiki? [18:43] (https://wiki.ubuntu.com/Bugs/FindRightPackage) [18:48] SloggerKhan: you can set the package to linux (this is the kernel itself) and then run 'apport-collect 999386' [18:48] or you can _open_ a bug with 'ubuntu-bug storage' === jbicha_ is now known as jbicha [20:50] almost 1.000.000 bugs :O [20:50] did anyone get the confetti machines for this exciting milestone? :P === Ursinha` is now known as Ursinha === Ursinha is now known as Guest8786 === zyga_ is now known as zyga [21:27] * hggdh shudders [21:28] the price of success, I guess [21:30] apports to blame ._. [21:33] only 80 left! [21:35] err, ~60 or less [21:36] actually, even less now https://bugs.launchpad.net/ [21:37] 999953 bugs reported [21:37] * greg-g was going off of what was in #ubuntu-bugs-announce [21:42] * highvoltage is excited [21:44] me too! I mean, we're all geeks, we love fun number milestones, right? [21:45] yeah :D [21:46] Can someone please assign Bug #973096? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096 [21:46] Launchpad bug 973096 in nvidia-graphics-drivers "Nvidia driver causes xorg crash" [High,Confirmed] [21:46] Launchpad bug 973096 in nvidia-graphics-drivers "Nvidia driver causes xorg crash" [High,Confirmed] https://launchpad.net/bugs/973096 [21:46] We have a lot of frustrated users out there... === zyga__ is now known as zyga === zyga is now known as _zyga [21:58] greg-g: I want to make the 1000000th bug. :P [21:58] * Logan_ will do a wishlist or something. [21:59] bug 100000 [21:59] Launchpad bug 100000 in launchpad "There are still too many bug reports" [Undecided,Invalid] https://launchpad.net/bugs/100000 [21:59] bug 1000 [21:59] Launchpad bug 1000 in null "There are too many bug reports in Malone" [Medium,Invalid] https://launchpad.net/bugs/1000 [22:00] haha [22:00] bug 1000000 [22:03] Pici: :) thanks [22:03] * highvoltage wonders whether but #1m is hardcoded or whether one of the people gunning for it will make it [22:04] no, it isn't hard coded :) [22:05] awesome. === Logan_ is now known as eating === eating is now known as Logan_