[02:24] <psusi> bdmurray, I have been seeing bugs the last day or two that have been filed, and then I can not access.. apparently this is because ubuntu-foundations-bugbot flags them as private, and does not subscribe ubuntu-crashes-universe, which seems like a bug, and I was told to ask you about it
[02:27] <psusi> bdmurray, a specific example is bug #1000959, which from the initial email I got, has no reason to be private at all, let alone flagged private, and inaccessible to ubuntu-bugcontrol members
[03:32] <sary> Could someone please triagger Bug #1001066
[03:32] <ubot2> Launchpad bug 1001066 in xorg "X freezes with a forced log out." [Undecided,New] https://launchpad.net/bugs/1001066
=== jbicha is now known as Guest10547
=== sm1 is now known as Sary
[06:41] <bullgard6> '~$ ubuntu-bug mc' does not open Launchpad on Firefox so that I can report a SIGSEV bug. The only reaction of this computer that I can see is that the hard disk LED flashes for a short time. How to fix the incomplete reaction to this command? [Ubuntu 12.04 GNOME Shell 3.4]
[07:07] <Sary> Try to set Firefox as the default browser .
=== Sary is now known as s1
=== yofel_ is now known as yofel
[11:55] <alo21> hi all
[11:56] <alo21> In what package we work to fix bugs usyally? Develpèment or stable?
[11:57] <jtaylor> both
[11:57] <jtaylor> but bugs must be fixed in development first
[11:57] <jtaylor> (except security issues)
[11:59] <alo21> jtaylor: Is a plasure to see you again :)
[12:10] <alo21> what does this error mean:  error: cannot call constructor 'wxFont::wxFont' directly [-fpermissive]
=== plars_ is now known as plars
[15:14] <psusi> bdmurray, I have been seeing bugs the last day or two that have been filed, and then I can not access.. apparently this is because ubuntu-foundations-bugbot flags them as private, and does not subscribe ubuntu-crashes-universe, which seems like a bug, and I was told to ask you about it
[16:46] <LordOfTime> if i'm a member of the upstream team that tracks bugs for a package in ubuntu on LP, and the bug is filed against the package in Ubuntu, does the Bugs/Status and Bugs/Importance still apply?
[16:46] <LordOfTime> as determined by the Bug Squad policies
[16:50] <micahg> LordOfTime: Ubuntu bug tasks should follow Ubuntu bug policies
[16:50] <LordOfTime> indeed
[16:51] <Daekdroom> They apply for the Ubuntu project. If you file it against the upstream project, then you can follow whatever policies the project has.
[16:51] <LordOfTime> the bug refers to a typo in the package description in debian/control
[16:51] <LordOfTime> lemme get you that
[16:51] <LordOfTime> LP Bug #1000940
[16:51] <ubot2> Launchpad bug 1000940 in nginx "Typo in nginx-light package description" [Undecided,New] https://launchpad.net/bugs/1000940
[16:52] <LordOfTime> i'm on the nginx team on LP, they're targeting that against Oneiric 11.10.
[16:52] <micahg> LordOfTime: upstream it to Debian, once it's fixed there we can sync to quantal
[16:53] <LordOfTime> micahg:  right, remind me how to do that again
[16:53] <LordOfTime> since Debian has not *once* accepted any bug filing requests i've done
[16:53] <LordOfTime> *ever*
[16:53] <micahg> LordOfTime: reportbug -Bdebian nginx-light
[16:55] <micahg> LordOfTime: nevermind, the text has been altered in the latest version
[16:55] <micahg> http://packages.debian.org/sid/nginx-light
[16:55] <LordOfTime> ah wonder...
[16:55] <LordOfTime> ... bleh
[16:56]  * LordOfTime just was reminded that needs fixing in the nginx team's ppas.... >.<
[16:56] <micahg> LordOfTime: OT, if you fix the CVEs for nginx, this fix can be a ridealong :)
[16:57] <LordOfTime> there're CVEs?
[16:57]  * LordOfTime hasnt recieved notifications of those
[16:57] <micahg> LordOfTime: http://people.canonical.com/~ubuntu-security/cve/pkg/nginx.html
[16:58] <LordOfTime> uhm....
[16:58] <LordOfTime> i think some of these were already fixed...
[16:59] <LordOfTime> micahg:  http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1180.html  <-- Precise has 1.1.19
[16:59] <ubot2> LordOfTime: Use-after-free vulnerability in nginx before 1.0.14 and 1.1.x before 1.1.17 allows remote HTTP servers to obtain sensitive information from process memory via a crafted backend response, in conjunction with a client request. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-1180)
[16:59] <LordOfTime> released (1.1.17) <--
[17:00] <LordOfTime> its not valid against Precise since Precise has 1.1.19
[17:00] <LordOfTime> did nobody check that...?
[17:01] <micahg> LordOfTime: you can ask the person in /topic in #ubuntu-hardened to update the tracker for you for CVEs
[17:14] <LordOfTime> micahg:  can you check this one, see if it was ever handled/synced?  https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/981969
[17:14] <ubot2> Launchpad bug 981969 in nginx "[FFE] sync nginx 1.1.19-1 from Debian unstable" [High,Triaged]
[17:15] <LordOfTime> pretty sure it was
[17:16] <micahg> yes, it was
[17:17] <LordOfTime> should be Fix Released, then, no?
[17:17] <micahg> done
[17:17] <LordOfTime> thanks
[17:17] <micahg> LordOfTime: rmadison is your friend
[17:17] <LordOfTime> micahg:  rmadison is still installing right now
[17:17] <LordOfTime> (slow installation because of slow  internet today)
[17:22] <wxwok> Is there any workaround for this bug? I'm often crashed out from logined user and re-login is needed. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/980519     syslog: kernel: [ 4252.501359] NVRM: Xid (0000:01:00): 6, PE0001
[17:22] <ubot2> Launchpad bug 980519 in xorg "Random log off in Ubuntu 12.04 LTS (dup-of: 973096)" [Undecided,Confirmed]
[17:22] <ubot2> Launchpad bug 973096 in nvidia-graphics-drivers "Nvidia driver causes xorg crash" [High,Triaged]
[18:46] <alo21> hi all
[18:47] <alo21> If I checked that a bug was fixed, can I put it as "fixed release"?
[18:47] <alo21> fix released*
[18:48] <alo21> ?
[18:49] <roadmr> alo21: how did you check the bug is fixed?
[18:50] <alo21> roadmr: I checked it from the source of a package for quantal
[18:53] <roadmr> alo21: so if I install quantal and upgrade to the latest version of the package, the bug will be fixed?
[18:53] <roadmr> alo21: usually bugs get automatically marked "fix released" when a package with the fix is built and published
[18:54] <alo21> roadmr: ok... I do not change the status...
[18:54] <roadmr> alo21: if the fix is in the code but you don't know if the package is published yet, you could potentially set as Fix Committed (note, committed but not necessarily released yet)
[18:55] <alo21> roadmr: one more information, where can I find a full list of packages which need to be packaged?
[18:57] <roadmr> alo21: hm, packages which need to be packaged? what do you mean? :)
[18:57] <alo21> roadmr: to be build
[18:59] <roadmr> alo21: oh! I don't know :/ you can see a list of packages being built at the moment here: https://launchpad.net/builders but I don't know where to see a queue of pending packages
[18:59] <jtaylor> alo21: search for needs-packaging tagged bugs
[19:00] <jtaylor> alo21: or in debian http://www.debian.org/devel/wnpp/
[19:01] <alo21> jtaylor: I can not find the filter... thanks
[19:01] <alo21> roadmr: thank you
[19:01] <jtaylor> https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&fi
[19:01] <jtaylor> eld.component-empty-marker=1&field.tag=needs-packaging&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints
[19:01] <jtaylor> =on
[19:01] <jtaylor> urk
[19:02] <jtaylor> the tags search box is at the bottom of the page
[20:57] <roadmr> jsalisbury: re: bug 994685, audio seems fixed on 3.4-rc4 (as per comment #4), do you still want me to test 3.4-rc6?
[20:57] <ubot2> Launchpad bug 994685 in alsa-driver "[Dell Inspiron 17] Headphone jack outputs no sound" [Medium,Incomplete] https://launchpad.net/bugs/994685
[20:57] <jsalisbury> roadmr, no need to text rc6 if it's fixed in rc4.  Thanks for testing.
[20:58] <roadmr> jsalisbury: ok, thanks for clarifying :) do let me know if I need to run any more tests on this system
[20:58] <jsalisbury> roadmr, great, thanks
[20:59] <jsalisbury> roadmr, if possible, do you think you can test some of the earlier v3.4 rc candidates, to find the earliest kernel version this bug is fixed in?
[21:00] <roadmr> jsalisbury: sure, that'll take a bit more time but I should have something early next week (almost EOD here and the system is in the lab, can't take it home )
[21:01] <jsalisbury> roadmr, thanks so much.  No rush, just when you have time.  At some point we could bisect and find the exact commit that fixed this bug, then work on submitting the fix for a SRU(Stable Release Update).
[21:01] <roadmr> jsalisbury: awesome! so OK, I'll try to find the first known good commit and work from there. It'd also be interesting to find the first *bad* commit where this broke in the 3.2 series :)
[21:02] <jsalisbury> roadmr, yes, correct.  Once we find the last know working and first non-working kernels, I can assist you with a bisect
[21:05] <roadmr> jsalisbury: thanks :) that sounds god
[21:05] <roadmr> good
[21:05] <jsalisbury> roadmr, thanks