[00:47] <MOSHU> Hi! I have some problems after upgrading Ubuntu from 10.04 to 12.04..... One is upgraded MySQL 5.5 (from 5.1) didn't start.... Can anyone help me, please?
[00:52] <dlentz> MOSHU, please use #ubuntu for support
[00:53] <MOSHU> Why? It's an apparmor upgrade bug
[00:54] <MOSHU> Anyway... The bug is reported since april, so.... sleep well, guys.
[05:57] <lotuspsychje> i have this bug thats been unsolved for years now, and affects many users in different forms..can i paste this here?
[05:59] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/556782
[05:59] <ubot2`> Ubuntu bug 556782 in linux "[rs690m] Graphics corruption with ati x1200" [Critical,Confirmed]
[13:10] <paul_> Having bug issue with Display on a new Samsung laptop. It revolves around the brightness changing on the Display.
[15:40] <TheLordOfTime> if a bug being filed is a regression between oneiric and precise, should it be tagged `regression`?
[15:41] <TheLordOfTime> (or precise and quantal, or other such regressions that only show up between releases)
[15:50] <brendand> regression-release (i believe)
[16:19] <micahg> TheLordOfTime: regression-release with a task added
[16:19] <micahg> and the release the regression is in as a tag as well
[16:20] <TheLordOfTime> micahg:  ah, i see.
[16:20] <TheLordOfTime> well, considering the bug that *is* a regression between oneiric and precise is already awaiting SRU team approval, i don't think that'd be necessary, but now i know what to do :P
[17:12] <cousteau> bug #919899 is marked as a duplicate of bug #961741 but I think it shouldn't; could someone confirm this?
[17:12] <ubot2`> Launchpad bug 919899 in console-setup "Compose sequence apostrophe+c produces a cedilla instead of acute (dup-of: 961741)" [Undecided,Confirmed] https://launchpad.net/bugs/919899
[17:12] <ubot2`> Launchpad bug 961741 in unity "REGRESSION: can't type characters with accent (dead keys)" [Medium,Fix released] https://launchpad.net/bugs/961741
[17:13] <cousteau> first one is about a compose sequence printing a different character than it used to;  2nd one is about dead keys not working on Dash
[17:16] <cousteau> hmm...  I just clicked "Remove duplicate link" and the duplicate notice just disappeared.  Is it that easy to remove duplicate notices?
[17:23] <mapreri> cousteau: yep, it is so easy :) LP is for lazy people :)
[17:24] <cousteau> wouldn't that lead to dupe/undupe wars?
[17:25] <cousteau> user A thinks bug is a duplicate and marks it, user B thinks it isn't and unmarks it, user A considers B didn't understand the problem and marks it, user B is "what's A doing??" and unmarks it, etc
[17:29] <mapreri> cousteau: we hope users wil follow the CoC also if they don't sign it
[17:30] <cousteau> (which reminds me, maybe I should sign it...)
[17:35] <cousteau> ok, thanks for the help  :)
[20:06] <Logan_> Can somebody please make Bug 1044429 public, assuming that it doesn't contain any private information?
[20:24] <jibel> Logan_, done
[20:24] <Logan_> jibel: Thanks. :)
[23:15] <phillw> hi, any staffers in from ubuntu bugs?
[23:15] <phillw> I have a complaint from QA that I'd like resolvng,
[23:16] <hggdh_> phillw: try it -- perhaps we can help
[23:19] <phillw> hggdh_: one of the testers has complained that his bug report has been marked as a dupe to a private bug report. This means he can not access it to update it. This is not a wise step to do for a ubuntu tester. It does cause them to raise a complaint with me & my having to come here.,
[23:20] <jtaylor> which bug?
[23:20] <hggdh_> well, this can indeed happen. But instead of a complaint, they could have pointed it out. When this happens, we look at the bug, and decide if there is private data justifying keeping the bug private
[23:20] <phillw> jtaylor: hggdh_https://bugs.launchpad.net/bugs/1024202
[23:20] <ubot2`> phillw: Error: <Bugtracker.plugin.Launchpad instance at 0xa2d980c> bug 1024202 not found
[23:20] <hggdh_> but, as jtaylor pointed out, we need the bug number
[23:21] <phillw> https://bugs.launchpad.net/bugs/1041007
[23:21] <ubot2`> phillw: Error: <Bugtracker.plugin.Launchpad instance at 0xa2d980c> bug 1041007 not found
[23:21] <phillw> they have been marked private
[23:22] <hggdh_> stacktrace bugs are born private
[23:23] <hggdh> but, for apport, I doubt there will be private data. The stacktrace does not have it
[23:23] <phillw> I've asked the tester to attend
[23:23] <hggdh> I marked it public
[23:24] <hggdh> but, ideally, they should point out the bug is private here. It will happen, and it will still happen, at least for a while
[23:24] <phillw> hi guys, can you please explain in simple language to nm_geo and myself why he cannot access his own bug report?
[23:24] <hggdh> oops
[23:24] <nm_geo> yes please
[23:25] <hggdh> his *own* bug report he certainly can
[23:25] <nm_geo> no the private that mine was dupped too
[23:25] <hggdh> somebody else's bug report -- like a bug _yours_ was dupped against -- is a completely different thing
[23:26] <hggdh> nm_geo: OK. Here's what happens:
[23:26] <nm_geo> I do understand that
[23:26] <jtaylor> it was automatically dupped
[23:26] <nm_geo> That is what I thought
[23:27] <hggdh> when a stacktrace bug is opened (an apport bug, specifically), this bug is opened private. Apport then goes, and GDBs it, and prints out a nice formatted stacktrace
[23:27] <phillw> and how do you dupe a public bug into private so he can no longer access it? I guess we have to come here and ask you guys?
[23:27] <hggdh> the problem is there *may* be private data being shown on the output of 'thread apply all bt full'
[23:28] <nm_geo> That is why I test using test as a password
[23:28] <hggdh> so apport leaves the bug private, pending someone with crash access to look and release
[23:28] <hggdh> nm_geo: it is good you test with throw-away private data. But not all bugs are from tests, some are from real usage :-)
[23:29] <nm_geo> Well I decide to Public mine hoping it would help but then it got dupped
[23:29] <jtaylor> you can remove the duplicate status
[23:29] <hggdh> whenever that happens (a private bug, with dups against it), then the best option is to come in this channel, and ask for someone to look at it
[23:29] <nm_geo> jtaylor: ok
[23:29] <jtaylor> but its better to ping someone here to make the master bug public
[23:30] <nm_geo> I will do that in the future if it appears to be needed bug Thank you guys
[23:30] <hggdh> nm_geo: and this is what I did -- I went into the bug, and looked at the potentially-private areas, saw nothing critical, made it public
[23:31] <hggdh> nm_geo: BTW, thank you for helping :-)
[23:31] <nm_geo> Hey you guys are the ones that have the tough job I just try to find them
[23:31] <TJ-> Whilst we're on the subject of bug reports going private I had a similar issue recently. I was actively working on a bug that I'd assigned to myself, I'd attached a debdiff patch and subscribed sponsors, and then next time I tried to get into the report to add my linked lp bazaar branch, the bug was no longer accessible. I'm a member of bug-control. It is/was bug #1008289
[23:32] <hggdh> TJ-: I also get a message stating there is no such bug. Was it a security issue?
[23:33] <TJ-> hggdh: It was apt sending a truncated token for auth to the private PPAs for purchased apps, so it could have become that I guess. I got no notification as a bug subscriber though
[23:33] <hggdh> nm_geo: you would be amazed, then, to find out that *we* really appreciate your help. Really.
[23:33] <nm_geo> Some day when phillw and Lubuntu get tired of me I might try on the bug-squad
[23:33] <TJ-> hggdh: And as I was assigned to it last time I looked I was very confused for a while!
[23:34] <hggdh> TJ-: this is indeed weird. Perhaps you should ping the folks at #ubuntu-hardened
[23:34] <jtaylor> you could ask in -hardened
[23:34] <hggdh> (cuz I also have no access to security bugs)
[23:34] <TJ-> hggdh: Oh that's encouraging! If you think it's weird too :D
[23:34] <hggdh> :-)
[23:34] <jtaylor> if its no security issue then its probably a bug for #launchpad
[23:34] <TJ-> hggdh: It would be nice if, at least, the bug owner and anyone assigned got a courtesy email telling them the big was being made secure and who to contact about it
[23:34] <hggdh> yeah
[23:35] <hggdh> TJ-: usually it is very difficult to re-bag the cat once it is out of the first bag
[23:35] <TJ-> Oh I dunno... I'm a farmboy... never had any problems with that here :D
[23:35] <hggdh> one can always try a larger bag, but still..
[23:36] <phillw> hggdh: would you prefer me to update the QA area for this answer, or can you guys put it up on bug wiki?
[23:36]  * hggdh now goes to bed, 44 hours up & running are starting to tell me I am not young anymore
[23:37] <hggdh> phillw: if you could, yes, I would really appreciate
[23:37] <hggdh> I am tired as hell
[23:37] <jtaylor> I got to get to bed too, n8
[23:37] <hggdh> heh
[23:37] <phillw> hggdh: I'll catch you after we have sleep :)
[23:38] <hggdh> phillw: tomorrow morning, US CDT time :-)
[23:38] <phillw> I'm on 24:38 GMT / UTC
[23:40] <TJ-> 44 hours is a slow train wreck! Get some sleep!!
[23:40] <phillw> hggdh: remind me at phillw@ubuntu.com
[23:51] <BHO1> I just installed Xbuntu yesterday.  Today I forgot to plug in my laptop and it died.  Ever since it died, my screen has been dim and i can not figure out how to brighten it.
[23:57] <phillw> BHO1: join #xubuntu that is where the support team is