[00:01] <peitschie> hello everyone :)
[00:01] <peitschie> i was wondering if anyone knows who is best to talk to about getting a patch into the python launchpad integration source?
[00:01] <kermiac> hi peitschie :)
[00:02] <peitschie> hi kermiac :)
[00:03] <kermiac> peitschie: There should be a team contact listed on the project's launchpad page
[00:09] <peitschie> kermiac: thanks heaps :)
[00:10] <kermiac> np peitschie :)
[00:27] <kermiac> bug 532633 - sorry, checking if the "me too's" from dupes are included
[00:27] <ubot4> Launchpad bug 532633 in light-themes (Ubuntu) "[light-theme] please revert the order of the window controls back to "menu:minimize,maximize,close" (affects: 135) (dups: 9)" [Wishlist,Triaged] https://launchpad.net/bugs/532633
[01:45] <mrburns> hi all i am new to triaging and would like someone to check my work on a bug.  I was thinking about setting the status to "incomplete", and reply with the default response for "Debugging GNOME Power Manager" for this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/538120
[01:45] <ubot4> Launchpad bug 538120 in gnome-power-manager (Ubuntu) ""+" and "-" buttons and the slider not working in lcd brightness applet (affects: 1)" [Undecided,New]
[01:46]  * ddecator looking
[01:48] <ddecator> well now that is interesting...
[01:50] <ddecator> mrburns, well, i can confirm it on my system. have you looked for dupes yet?
[01:53] <mrburns> ddecator: well i have tried a little.  i am new to finding duplicates.  i have gone to list open bugs then did some searches but didn't find anything like this.  do you have a better method?
[01:54] <ddecator> mrburns, the best thing that has worked for me is using google, just search for "site:bugs.launchpad.net <search terms>"
[01:55] <mrburns> ok i can do that
[01:56] <ddecator> mrburns, if you find anything, just let us know. i just feel like this would have been reported before...seems like a lot of people might run into it. if you don't find anything, then we can figure out the best way to approach the report =)
[01:57] <mrburns> ddecator: bug 532518 is close do you think this is the same thing?
[01:57] <ubot4> Launchpad bug 532518 in gnome-power-manager (Ubuntu) (and 1 other project) "Brightness Applet is not usable via Mouse (affects: 1)" [Undecided,New] https://launchpad.net/bugs/532518
[02:00] <ddecator> mrburns, both describe the behavior i'm seeing, but the first report you found doesn't say specifically that the applet disappears when they try to click the buttons or the slider bar. sooooo...maybe set it to incomplete and ask if that is the behavior they are experiencing and mention the bug in the comment so they reporter can see if and it will be easier to mark as a dupe if it's the same? what do you think?
[02:00] <ddecator> mrburns, (the first report that is)
[02:01] <mrburns> ddecator: that sounds good
[02:02] <ddecator> mrburns, sounds good to me too =). why don't you go ahead and do that? i'll subscribe so i can see how it goes
[02:11] <mrburns> ddecator: thanks for helping me out
[02:14] <ddecator> mrburns, no problem, that's one of the main purposes for this channel. just let us know if you have any other questions
[02:15] <mrburns> ddecator: will do i am trying to get more involved and work on a bug a day to start with
[02:15] <ddecator> mrburns, good place to start. we appreciate the help =)
[02:24] <ddecator> anyone on right now know if i'm supposed to add myself to the mentor wiki page once i've been approved to be a mentor? i also need admin rights in the group, but not sure who is supposed to do that (pedro?)
[02:44] <zeroseven0183> Hi! Where can I find the minutes of the last meeting? It's not in the https://wiki.ubuntu.com/BugSquad/Meeting/Minutes
[02:48] <kermiac> zeroseven0183: http://irclogs.ubuntu.com/2010/03/09/%23ubuntu-bugs.html
[02:51] <zeroseven0183> Thank you very much
[02:51] <kermiac> np zeroseven0183 :)
[03:47] <Damascene> hello
[03:48] <Damascene> channel is officially logged at http://irclogs.ubuntu.com/
 hello
 apport-collect -p linux 527369
[03:48] <Damascene>  is there anything wrong in the syntax
[03:48] <Damascene> sorry
[03:48] <ddecator> not that i can see. is it not working?
[03:48] <Damascene> apport-gtk: error: no such option: -p
[03:49] <ddecator> -p is just used to define a specific package...maybe you can't do that with just "linux" in general?
[03:50] <Damascene> I just followed bug 527369
[03:50] <ubot4> Launchpad bug 527369 in linux (Ubuntu Lucid) (and 1 other project) "sudo lshw causes console to turn blue on dell inspiron 1011 (affects: 2)" [High,Confirmed] https://launchpad.net/bugs/527369
[03:51] <persia> "linux" is a package name, also
[03:52] <ddecator> persia, true
[03:52] <Damascene> so?
[03:53] <vish> Damascene: try without the -p
[03:54] <vish> there is also an apport bug recently , it is not working or something , it might be that too
[03:54] <Damascene> really? it asks for kernel log I think
[03:54] <vish> Damascene: i meant $ apport-collect linux 527369
[03:54] <Damascene> ok
[03:55] <Damascene> apport-collect linux 527369
[03:55] <Damascene> apport-gtk: error: You need to specify a report number to update
[03:56] <vish> Damascene: hmm , Try $ apport-collect 527369
[03:56] <ddecator> the report is marked as affecting linux, so just 'apport-collect 527369' should work
[03:56] <vish> since there is only one package it should pick up the right package'
[03:57] <ddecator> haha, couldn't type fast enough =p
[03:57] <Damascene> do you think doing apport-collect -p linux -u 527369 would help?
[03:57] <vish> ;)
[03:57] <Damascene> it's in the man page
[03:58] <vish> Damascene: this should work , $ apport-collect 527369   , since there is only one package , no need to specify
[03:58] <Damascene> ok
[04:00] <ddecator> vish, so you've seen reports about apport not working lately?
[04:00] <Damascene> You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.
[04:00] <Damascene> Please create a new report using "apport-bug"
[04:00] <vish> ddecator: i havent seen the bug , but yeah , people have been complaining apport is not able to report crashes
[04:01] <ddecator> vish, huh, all i've seen are some related to firefox, which was an ubufox problem...
[04:01] <vish> ddecator: unrealted to firefox , this is something new
[04:02] <ddecator> vish, interesting...good to know
[04:05] <Damascene> A bug is considered a regression if the issue did not exist on a previous kernel.  Is this a regression?
[04:05] <Damascene> ??
[04:06] <crimsun> generally, yes
[04:06] <crimsun> devil's in the details, as always
[04:12] <Damascene> how to check if every thing went well I don't notice any change in the bug report
[04:29] <ddecator> hggdh, are you around by chance?
[04:35] <hggdh> ddecator: briefly...
[04:35] <ddecator> hggdh, just wondering if i'm supposed to add myself to the mentor wiki or if someone is in charge of maintaining it
[04:36] <hggdh> ddecator: you are supposed to add yourself, yes
[04:36] <ddecator> hggdh, thanks, that's all i needed =)
[04:36] <hggdh> and to look at the queue of candidates for membership on the -membership, and select a victim
[04:37] <ddecator> do i need to be an admin for that, or just look at the approved members on lp?
[04:38] <hggdh> you should be an admin to be able to approve a candidate. If you are still not one (only pedro can do it), I will ask pedro next Monday
[04:38] <ddecator> hggdh, i can send him an email, i need to check up with him on something anyway
[04:38] <hggdh> ddecator: excellent, even better
[04:39] <TheNewAndy> is ubuntu-bug broken for anyone else, I'm trying to submit a tomboy bug, and I get:
[04:39] <TheNewAndy> "Cannot connect to crash database, please check your Internet connection."
[04:39] <TheNewAndy> every time.
[04:39] <ddecator> well that's not good...
[04:40] <persia> You might want to follow bug #538097 until there is a solution
[04:40] <ubot4> Launchpad bug 538097 in apport (Ubuntu) "Apport cannot connect to crash database (affects: 19) (dups: 1)" [Undecided,Confirmed] https://launchpad.net/bugs/538097
[04:40]  * hggdh over and out
[04:41] <TheNewAndy> thanks :)
[04:42] <persia> TheNewAndy: PLease press the "Also affects me" button :)
[09:24] <kklimonda> good mornin
[09:24] <kklimonda> g
[09:59] <qense> Where can I find the log files of telepathy-butterfly?
[13:57] <hernejj_> I've confirmed a bug that i believe is ready for Triage: https://bugs.launchpad.net/nautilus/+bug/538327
[13:57] <ubot4> Launchpad bug 538327 in nautilus (Ubuntu) (and 1 other project) "file management preferences does not fit 800x600 screens (affects: 1)" [Undecided,Confirmed]
[13:58] <yofel> hernejj_: what importance would you give it?
[13:59] <hernejj_> Medium, I think.
[14:02] <yofel> hm, there is a workaround: 'press alt and left click and move the window'. That might not work though if moving the window under the top panel is disabled or if alt+move is disabled
[14:03] <yofel> I'll set it to medium for now
[14:03] <hernejj_> yofel: Correct :) And since the default virtual desktop configuration is "2 in a row" it is likely that user's will not be able to immediately apply that work around.
[14:07] <yofel> hernejj_: can you please add the 'lucid' tag to the report? Apport usually does that but it's broken right now
[14:09] <yofel> hernejj_: oh, and can you please assign the bug to the 'desktop-bug', they seem to want it like that https://wiki.ubuntu.com/DesktopTeam/Bugs
[14:10] <yofel> err... 'desktop-bugs' team, not desktop-bug
[14:14] <yofel> hernejj_: ping?
[14:17] <hernejj_> yofel: Sorry for the delay. Yes, I'll do both of those.
[14:19] <hernejj_> yofel: It has been done :)
[14:20] <yofel> hernejj_: thanks for helping :)
[15:00] <Dawgmatix> i wanted to bring attention to a bug that has existed for sometime and is causing me much grief - two of my hard drives are not beeing recognized
[15:00] <Dawgmatix> theres an open bug for this at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/501950
[15:00] <ubot4> Launchpad bug 501950 in linux (Ubuntu) "Randomly missing harddrive on reboot : dmesg -> "model number mismatch" (affects: 2)" [Medium,Triaged]
[15:01] <Dawgmatix> i was hoping that lucid would fix this issue, but sadly its present in lucid too
[15:01] <Jeruvy> looks good that it's been triaged.
[15:02] <Dawgmatix> its been in that state for over two months
[15:02] <Dawgmatix> i am a fairly technical user, if theres something i can do to resolve this issue i would be glad to help
[15:05] <yofel> Dawgmatix: as the bug is triaged I doubt there's much that can be done from our (bugsquad) side, maybe ask in  #ubuntu-kernel if you can be of assistance
[15:05] <Dawgmatix> okay
[15:05] <Dawgmatix> thanks :)
[15:06] <yofel> Dawgmatix: but be patient, they usually take their time to answer
[15:06] <Dawgmatix> sure, thats no issue
[15:06] <Dawgmatix> i was just looking to make sure that this issue reaches the right people
[16:02] <BUGabundo> bRoas
[18:44] <Damascene> https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/527369 should  be triaged I think
[18:44] <ubot4> Launchpad bug 527369 in linux (Ubuntu Lucid) (and 1 other project) "sudo lshw causes console to turn blue on dell inspiron 1011 (affects: 2)" [High,Confirmed]
[19:57] <hernejj> I believe that https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/538494 is ready to be triaged Importance: Low
[19:57] <ubot4> Launchpad bug 538494 in indicator-sound (Ubuntu) "Slider item does not highlight like other items (affects: 1)" [Undecided,Confirmed]
[19:58] <crimsun> eh? it does here.
[19:58] <crimsun> (0.1.3.1-0ubuntu1)
[19:59] <hernejj> crimsun: Can you send me a screenshot? Also what theme are you using?
[19:59] <crimsun> radiance
[19:59] <hernejj>  crimsun: I'm using radiance as well. I was able to confirm no highlight. Interesting :)
[20:00] <greg-g> crimsun: same verion here, same theme, it does not visibly highlight the slider for me.
[20:01] <greg-g> crimsun: I can adjust the volume level with my keyboard (thus it is 'active') but I can't visually tell that
[20:02] <crimsun> I don't know what you mean by that last statement
[20:02] <hernejj> crimsun: Take a look at the screen shots I attached to that bug. They illustrate the difference.
[20:03] <crimsun> hernejj: I would if I could
[20:03] <greg-g> crimsun: so, open the indicator sound applet, press down once, Mute All is visually highlight, press down again, the slider is not visually highlighted (but I am, however, able to adjust that slider using my right-left arrow keys)
[20:03] <greg-g> did that make sense? sorry I'm not :/
[20:03] <crimsun> ah!
[20:03] <crimsun> ok, yeah, I can reproduce that
[20:04] <greg-g> cool, damn language getting in the way! :)
[20:04] <crimsun> I thought you meant the elliptical widget itself wasn't being highlighted
[20:05] <greg-g> status/importance updated
[20:05] <hernejj> Thank you :)
[20:06] <greg-g> yw
[20:08] <greg-g> oh uh, it was just marked as a duplicate
[20:12] <greg-g> hah, mpt had reported the bug twice ;)
[20:17] <vish> lol , mpt filed his own dup :D
[20:22] <ceauke> hi guys
[20:23] <persia> Hey ceauke : thanks for helping with testing.  As I mentioned there, some folks here might be better able to help you find the right package for your bug than I.
[20:27] <ceauke> Hi persia. yeah, I'm a bit lost with the technicalities. can anyone on this channel help me to find out which package is causing my hibernation issue?
[20:27] <ceauke> when I click on hibernate on the session conroll button on the top menu, the hibernation fails.
[20:29] <yofel> ceauke: where does it fail? it does nothing/ locks screen instead/ doesn't wake up/ ...?
[20:31] <ceauke> it seems to sleep only for a milisecond.
[20:32] <ceauke> the screen goes blank, backlik still on and hdd still working
[20:32] <ceauke> then after some time (a few secs) it finally switches off the backlit (at which time I'd expect a proper sleep) but then immediately it resumes from hibernation
[20:32] <ceauke> and then I can unlock the system and everything else works again
[20:33] <ceauke> so it kinda autoresumes
[20:34] <yofel> o.O
[20:34] <yofel> I would probably file a bug against linux, but I'm not sure why it should autoresume...
[20:35] <yofel> anyone else got a better idea?
[20:37] <ceauke> I saw some bugs on hibernate where it said that the wifi made it autoresume (apparently it disconnects the wifi and then wakes itself) but even with network disabled it still doesn't work
[20:37] <ceauke> I even disabled my USB power in the bios to make sure the computer sleeps well but to no avail.
[20:40] <hernejj> I believe https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/538504 is ready for triage. Importance: Low
[20:40] <ubot4> Launchpad bug 538504 in transmission (Ubuntu) "transmission measures bandwidth in KB/s instead of kB/s (affects: 1)" [Undecided,New]
[20:43] <crimsun> done
[20:44] <yofel> ceauke: if nobody else answers you: file a bug against 'linux' once apport works again (database access broken atm). That should add most of the interesting hardware information to the report. And the kernel team should know if it's a bug in the kernel or not
[20:45] <ceauke> thanks yofel will to
[20:45] <ceauke> do
[20:47] <ceauke> sorry, noob question. does that mean the package is "linux(ubuntu)"
[20:47] <crimsun> yes
[20:57] <ceauke> exit
[20:58] <hernejj> crimsun: Sorry to bug you, I noticed you marked 538504 as confirmed instead of Triaged. While I was verifying that I had remembered to do everything I noticed I forgot to open the bug upstream. This is done now and I believe the bug is ready for triage this time :)
[20:59] <crimsun> done.
[21:00] <hernejj> Thank you.
[21:00] <crimsun> yw, thank *you*
[21:39] <jarlath> I'd like to contribute to the bug-triaging effort. Are there any low-hanging-fruit, like following up on old and inactive reports to see if they can be closed?
[21:41] <jarlath> That would require the least technical knowledge, as I see it.
[21:42] <persia> Absolutely.
[21:42] <persia> Take a look at the wiki pages in the /topic
[21:42] <persia> Ask if you have any questions at all.
[21:42] <persia> And thanks for helping out!
[21:42] <jarlath> Will do. Thanks persia
[22:07] <jarlath> So, this bug has had nothing conclusive since November 2008. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/223061
[22:07] <ubot4> Launchpad bug 223061 in linux (Ubuntu) "upgraded to hardy heron from gutsy and now sound card does not work, no sound is being emmited" [Undecided,Incomplete]
[22:08] <jarlath> I'm thinking; ask if it's still an issue and if no reply within the 2 weeks, mark as invalid.
[22:08] <persia> I think 2 weeks is kinda short, but that's the right sort of idea.
[22:09] <persia> If you go for a short timeframe, warn the user that you're going to close it if they don't get back with more information.
[22:11] <jarlath> Ok, well - I don't have the skills to follow it up with a solution if there are still users experiencing problems.
[22:12] <jarlath> So should I consider that also?
[22:12] <persia> No.
[22:12] <persia> You're part of a very large team.
[22:12] <persia> If you get stuck, ask for help.
[22:13] <persia> You have lots of backup, so don't worry if you're not sure, but always ask before taking actions when you're unsure.
[22:13] <persia> The key things to keep in mind are providing a good experience for reporters, and trying to make a clear and effective bug report for develoeprs.
[22:14] <persia> You'll surely learn something along the way, but it's generally better to ask here than to ask in the bug report unless you need information from the reporter.
[22:14] <jarlath> Great.
[22:15] <persia> It can also sometimes be helpful to look at the profiles of recent commenters.  This may help you to determine if someone works with a lot of bugs, or only a few, and the areas in which they tend to work.
[22:17] <jarlath> So, instead of trying to close out as many old bugs as possible, should I instead be prepared to follow through with further direction / assistance to the reporter?
[22:19] <jarlath> Instead of a wham-bam thank you ma'am approach of just clarifiying whether or not it can be closed out before moving on to the next report.
[22:21] <persia> Well, it depends.
[22:21] <persia> There are lots of ways to triage well.
[22:22] <persia> Sometimes I'll pick a package, try to understand all the bugs, change everything to the correct status, etc., and move on, with minimal followup (but I generally don't ask questions of reporters in that case, because I've been testing hard, and know what I can replicate, etc.)
[22:22] <persia> Sometimes I'll pick only a few, confusing, bugs, and ask lots of questions for detailed follow-up.
[22:23] <persia> Some folk develop relationships with the original software developers, and spend a lot of time forwarding bugs and helping reporters talk to the authors directly.
[22:23] <persia> Other folks look for bugs that aren't set to a package and figure out the right package.
[22:23] <persia> For both of those cases, there's often very little communication with the reporter required.
[22:26] <jarlath> Ok, that's great. Many ways to get involved with varying levels of background work / commitment.
[22:26] <persia> Really, the best way to be involved, is the way that gives you the most enjoyment.
[22:26] <persia> As long as you avoid annoying the users or the developers, you're probably safe.
[22:27] <jarlath> Hehe, yes. I think keeping interruptions to the essential minimum is important.
[22:28] <persia> Right.  So you want to ask clear questions, and ones where the answer will help the bug to be understood.
[22:29] <persia> For example, it's not useful to ask "Does this bug still happen to you in the latest release" unless you've already checked, and it doesn't happen for you, because this differentiates general issues from issues that may be related to the users' environment (architecture, language, other software installed, etc.).
[22:29] <jarlath> Ah okay
[22:29] <persia> If you can still get the bug, then maybe check to see if you can understand it and add more detail, or if not, make sure it's confirmed, and move on to find another bug.
[22:31] <persia> Not that the gutsy-hardy upgrade bug related to specific sound hardware is a tricky example to reproduce.  If you don't have that hardware, it's a good candidate to just ask about.
[22:31] <persia> Especially because there are some workarounds posted: if it's fixed in the reporter's system, and fixed on a fresh install (indicated by the developer comment), then it can maybe be closed.  We may not understand *why* it happened, but we also don't have a good test case to track it down.
[22:32] <persia> Err, *Note* that ...
[22:34] <jarlath> So, one concern I have with that report is that if I ask if it's still an issue, and a reproter says it still is ... then they see no more progress - am I not sort of wasting their time?
[22:37] <persia> If you aren't getting any useful information out of the question, yes.
[22:38] <persia> So it's bascially a matter of determining if there is any information to collect.
[22:38] <jarlath> Ah, gotcha
[22:38] <persia> For instance, in the bug you cite, it would be interesting to know if the user is still running hardy.  If they are, they still have an issue that needs work (but you'd want to try to track it down in detail).
[22:38] <persia> If they aren't, we'll never be able to solve the bug, so we may as well mark it "Invalid".
[22:39] <persia> (this isn't true for all bugs, but this one appears to affect only some of the people who have one specific piece of hardware).
[22:40] <persia> Well, let me restate: if they aren't running hardy anymore *and* they don't have the problem anymore, then there's little that can be done.
[22:40] <persia> If they are running hardy, or they do have the problem, then we can investigate.
[22:43] <jarlath> Ok, so if the bug looks like something I'd be uncomfortable following through on (getting familiar with relevant attachments and learning and communicating debug processes for the app), I should probably just sit it out?
[22:47] <jarlath> Actually, that's a yes for me at the moment.
[22:49] <jarlath> Ok, thanks persia. I'll spend time watching and get back here before I do anything controversial :)
[22:50] <persia> good luck!
[22:50] <jarlath> Thanks
[23:40] <mikelifeguard> Hi, I'm looking at bugs.launchpad.net -- where do I click to submit a bug report to launchpad?
[23:40] <bcurtiswx_> mikelifeguard: it's better to type "ubuntu-bug <package name>" in a terminal
[23:41] <mikelifeguard> bcurtiswx_: that doesn't work, else I would be doing so
[23:41] <bcurtiswx_> mikelifeguard: what program?
[23:41] <mikelifeguard> screen
[23:43] <bcurtiswx_> i got ubuntu-bug screen to work on my terminal
[23:43] <bcurtiswx_> but using the GUI from launchpad
[23:43] <bcurtiswx_> https://edge.launchpad.net/ubuntu/+source/screen
[23:43] <bcurtiswx_> on the right hand side click "report a bug"
[23:44] <mikelifeguard> as it turns out, my bug has already been reported
[23:44] <mikelifeguard> but it is amazing that the main page has no link to submit a bug
[23:44] <bcurtiswx_> mikelifeguard: good, you can click "this bug effects me too" on that bug
[23:44] <mikelifeguard> especially considering canonical prides itself on being good at UI stuff :\
[23:45] <mikelifeguard> I'd file a bug for that, but guess what?! it's too goddamned hard :)
[23:45] <crimsun> what is "the main page",mikelifeguard?
[23:45] <mikelifeguard> crimsun: bugs.launchpad.net
[23:45] <bcurtiswx_> mikelifeguard: launchpad isn't the bug reporter.. its the bug tracker
[23:46] <bcurtiswx_> mikelifeguard: you need to know what you are reporting in first that being Ubuntu hence why http://launchpad.net/ubuntu has a "report a bug" link
[23:46] <crimsun> mikelifeguard: you can't report a bug against a non-project
[23:47] <crimsun> mikelifeguard: at the bugs.lp level, you haven't entered a project
[23:47] <crimsun> ubuntu is just one of many projects hosted on lp
[23:47] <mikelifeguard> so? Obviously you put a textarea with ajax search so the user can choose O.o
[23:47] <greg-g> in other words: Launchpad is not just for ubuntu
[23:47] <crimsun> mikelifeguard: I think the appropriate venue for voicing concern is #launchpad
[23:48] <mikelifeguard> *nod*