[03:40] <MoLE_> what's do I need to do next to progress bug 595784
[03:40] <ubot2> Launchpad bug 595784 in ubuntuone-client "latest ubuntuone beta client for karmic must be started manually to work. (affects: 1) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/595784
[03:41] <MoLE_> Any takers?
[03:44]  * MoLE_ listens for the crickets
[03:44] <micahg> MoLE_: that's not a bug in Ubuntu, you'll need someone from the Ubuntu One team
[03:44] <MoLE_> micahg, thank you I didn't realise there was a difference
[03:46] <micahg> maybe someone else knows if they have a channel
[03:46] <MoLE_> I found the #ubuntuone channel thanks
[10:42] <vish> what happened to menu item Help > Report a problem?  it seems missing in Lucid
[10:43] <seb128> vish, stable users usually want to get help not to report a bug, they are not technical enough for bugs
[10:43] <vish> seb128: agreed , just wondering what happened.. has it always been removed after a release?
[10:44] <seb128> no, we decided to try that in lucid
[10:44] <vish> ah , cool.
[10:44] <sense> seb128: Do you happen to be aware of plans to redirect 'regular' users to Launchpad Answers instead of Bugs?
[10:45] <vish> seb128: thanks
[10:45] <seb128> sense, I don't
[10:45] <vish> .. maybe we should modify the response template as well
[10:45] <seb128> sense, out of the fact that we have a "get help" menu item for the menu tracker in stable versions and not one to open bugs
[10:45] <sense> seb128: Ah, then it never really left the stage of extensively debated idea in the Bug Squad.
[10:45] <seb128> "the answer tracker"
[10:46] <sense> yes
[10:46] <seb128> which is sort of directing users there...
[10:46] <sense> seb128: it was suggested and investigated to let the users report their problems there, that way they can be helped in their own language and we'd be less swamped with bug reports. Also: multiple users might have different support needs for one bug report, espexcially when there are a lot fo duplicates.
[10:46] <sense> seb128: But it never got off the ground, really.
[10:46] <seb128> seems a nice idea though
[10:47] <vish> bdmurray: hggdh: ^^ due to the item being removed , shall i edit: https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package  ?
[10:47] <seb128> would be worth trying
[10:47] <sense> seb128: Something for UDS-N? :)
[10:47] <seb128> I guess ;-)
[10:49] <vish> sense: "get help" option redirects to answer tracker.. is that not what you mention?
[10:51] <sense> vish: Yes, a bit. But not fully since we don't redirect people to report their problems there, and the Answer tracker might require some modifications to be optimal for this use, and the Bug Squad and LoCos aren't set to this behaviour.
[10:51] <sense> So everyone is still encouraged to use bug reports.
[10:53] <vish> sense: they can ask the question ,which is sorta "report their problems there" if it is a bug , we can convert it to bug? but local translations is a problem
[10:53] <sense> vish: That's why we need the LoCos.
[10:54] <vish> righto..
[10:54] <sense> vish: It's the "How do I write a proper defect report"-support request thing.
[10:54] <sense> vish: And getting the LoCos might of course be a problem. Maybe not so much for French, but for less often spoken languages.
[10:55] <sense> vish: We would need good duplicate detection as well.
[10:55] <sense> because we'd have multiple places in multiple languages that would contain the bug.
[11:46] <kermiac> hggdh: did you get a chance to look at the arsenal scripts mate?
[13:35] <bcurtiswx> vish: do you know if Ken's patch to empathy for auto-scrolling chat rooms only applies if you aren't already at the bottom of the chat window?
[14:45] <hggdh> kermiac: sorry, got busy, will look at it now
[15:13] <vish> bcurtiswx: -> U-desktop
[17:16] <njin> hello. In Lucid wich app sustitute jscalibrator ? thanks
[17:17] <devildante> !support | njin
[17:17] <ubot2> njin: The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[18:25] <brummbaer> greetings. new to bug processing, hoping someone can comment on general strategy on a bug i'm using to get oriented. https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/612620
[18:25] <ubot2> Ubuntu bug 612620 in pidgin (Ubuntu) "I have set up an account at Yahoo, but cannot access with Pidgin (affects: 1) (heat: 8)" [Undecided,New]
[19:29] <JoshuaL> Hello, I have a bug in 10.10 where after an reboot my sound gets muted. What package should be used in the bug report?
[19:30] <charlie-tca> Ubuntu or Xubuntu?
[19:30] <JoshuaL> Ubuntu
[19:30] <JoshuaL> And how can I "bump" a bug i reported a few months ago without an answer?
[19:31] <charlie-tca> alsa-driver
[19:31] <charlie-tca> but it might be bug 455420
[19:31] <ubot2> Launchpad bug 455420 in alsa-driver (Ubuntu) "Sound is muted at log-in (affects: 3) (heat: 16)" [Low,Confirmed] https://launchpad.net/bugs/455420
[19:31] <JoshuaL> Let me check
[19:31] <charlie-tca> You can put a comment on a bug asking if there is any more information needed
[19:32] <charlie-tca> That bumps them nicely
[19:32] <JoshuaL> charlie-tca, thats the one :)
[19:32] <charlie-tca> I got one right?
[19:33] <JoshuaL> charlie-tca, bug 455420 was the same as i have now indeed :)
[19:33] <ubot2> Launchpad bug 455420 in alsa-driver (Ubuntu) "Sound is muted at log-in (affects: 3) (heat: 16)" [Low,Confirmed] https://launchpad.net/bugs/455420
[19:34] <JoshuaL> charlie-tca, the bug i want to bump is bug 569335
[19:34] <ubot2> Launchpad bug 569335 in network-manager-applet (Ubuntu) "Network manager applet does not display the current connection (affects: 2) (heat: 43)" [Undecided,New] https://launchpad.net/bugs/569335
[19:34] <charlie-tca> that is confirmed, so see if there is any other information asked for. If not, just a "this also affects me" on tip is good
[19:35] <JoshuaL> charlie-tca, already marked myself as affects me too :) ty
[19:35] <charlie-tca> Great
[19:35] <charlie-tca> I'm looking at the network manager bug now
[19:36] <charlie-tca> I bumped it
[19:36] <JoshuaL> ty
[19:36] <charlie-tca> You are welcome
[19:37] <JoshuaL> i also have another bug i would like to report, not sure what package it reflects and how to describe it
[19:38] <JoshuaL> but there are some "graphical" issues with compiz enabled. for example: i have the stack applet, it shows some weird white "image" when moving over the stack items. The same happens with gnome-do. As if it doesnt handle transparancy or something like that.
[19:38] <JoshuaL> cant explain it that good
[19:38] <charlie-tca> That's been report, I think
[19:38] <charlie-tca> Just don't know the number
[19:39] <JoshuaL> i cant think of a good summary so im unable to find it
[19:39] <JoshuaL> english is not my first language :(
[19:41] <JoshuaL> And there was something else, I created a shared folder in 10.10, however it told me i had to install some kind of services. it also told me it would need a session restart, which i did. but the folder was not shared afterwards. had to do it again. i would like to make a suggestion to improve this behavior. any idea how i can do this best?
[19:42] <JoshuaL> and sorry for the amount of questions :P
[19:42] <vish> JoshuaL: Q: do you have any other applets on the panel?
[19:43] <vish> JoshuaL: i dont think it is a nm applet bug , i'v a similar problem , the panel just gets stuck and does not render
[19:43] <charlie-tca> Questions are no problem. the shared thing will most likely happen before/at the beta testing time
[19:43] <JoshuaL> vish, with an default install it still occurred
[19:43] <JoshuaL> charlie-tca, ok cool
[19:44] <vish> JoshuaL: is the applet 'stuck' now? and displaying wrong icon?
[19:44] <JoshuaL> vish, it shows the wireless icon with an red !
[19:44] <JoshuaL> however, when connecting to other networks at another location it works perfectly well
[19:44] <vish> JoshuaL: now , right-click on panel , select properties
[19:45] <vish> JoshuaL: in the background tab which option is selected?
[19:45] <JoshuaL> None (use system theme)
[19:46] <vish> JoshuaL: select solid color
[19:46] <JoshuaL> Done, however it does not seem to repaint the right part of the panel (where those icons are located)
[19:47] <vish> hmm..
[19:47] <vish> JoshuaL: select a different theme
[19:48] <JoshuaL> hmm, thats odd. switching from Radiance to New wave result in a theme named Custom. Borders from Radiance stay, except diffrent colors for the controls and panels..
[19:48] <JoshuaL> and the nm-applet icon stays the same
[19:49] <vish> JoshuaL: panel background changed and the icon is still showing disconnect...
[19:49] <vish> odd , then not the same bug :D
[19:49] <JoshuaL> ok
[19:50] <JoshuaL> vish, however now (i guess) found another bug. the theme changes all of the sudden in a theme named Custom with some weird mixes of the previous theme
[19:51] <vish> JoshuaL: sometimes it happens , when not all the theme settings change it shows custom , try selecting the theme again it will be correct now
[19:51] <vish> or if the change is not quick too it shows custom..
[19:51] <JoshuaL> vish, then it still uses the wrong borders :)
[19:52] <JoshuaL> no mather what theme i select (except Radiance)
[19:57] <charlie-tca> vish is good with themes and stuff. He knows how to fix things
[20:00] <JoshuaL> cant record it with istanbul, results in a crash too lol
[20:03] <vish> JoshuaL: just try changing the window borders manually , some remnant setting in your .gnome folder might be messing things :s
[20:05] <JoshuaL> vish, it was an clean install
[20:05] <JoshuaL> vish, the theme i use now works fine, thought it might affect other people too
[20:05] <vish> JoshuaL: hrm , changing the window border manually also does not change the theme border?
[20:07] <JoshuaL> vish, that seems to work, it keeps remembering the window border from the old theme (only the default ubuntu themes installed)
[20:12] <kc7zzv> I'm trying collect information about bug 601159 using apport, but the bug I'm reporting causes the ethernet card to not work.  I can fix the ethernet card with a workaround, but I'm worried that will change the information apport will collect.  Any advice?
[20:12] <ubot2> Launchpad bug 601159 in linux (Ubuntu) "e1000 ethernet port intermitently works (affects: 1) (heat: 119)" [Undecided,Incomplete] https://launchpad.net/bugs/601159
[20:12] <kc7zzv> Also, is this the right place to ask?
[20:12] <vish> !debugging
[20:12] <ubot2> For help debugging your program, please see https://wiki.ubuntu.com/DebuggingProcedures
[20:13] <vish> kc7zzv: https://wiki.ubuntu.com/DebuggingNetworkManager  , might be helpful
[20:13] <hggdh> kc7zzv: you can always wait until you have the issue, and then collect the data; then reconnect, and upload it
[20:14] <vish> hggdh: did you get my earlier ping? about the help > report bug item being removed?
[20:14] <vish> we should update the reply templates..
[20:15] <hggdh> vish: hum. Do not remember, can you summarise it again?
[20:15] <hggdh> what about the reply templates?
[20:15] <JoshuaL> vish, do you think my issue is a bug or just an individual issue which i need to solve myself? :)
[20:16] <vish> hggdh: for this > https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package  we mention to use Help > Report a problem
[20:16] <hggdh> oh, but there is no report a problem currently
[20:16] <hggdh> is that it?
[20:16] <vish> yup
[20:17] <vish> JoshuaL: the window border issue? you can file a bug ..
[20:17] <hggdh> vish: yeah, let's remove this reference, good point
[20:17] <micahg> hggdh: well, it's removed from the stable releases
[20:17] <vish> JoshuaL: but wouldnt hold my breath :)
[20:17] <hggdh> micahg: yes -- that's what I meant. But it is so frequently misused...
[20:18] <JoshuaL> vish, ill do a bug report and see what it brings me. any suggestions for a summary (and what package it should be reported against)
[20:18] <micahg> hggdh: which is why I think they disabled it in stable releases :)
[20:18] <hggdh> like a firefox bug -- it is ffox cuz they used the ffox report-a-problem
[20:18] <micahg> which is about to disappear in Lucid :)
[20:18] <hggdh> :-)
[20:18] <vish> JoshuaL: gnome-setting-daemon
[20:19] <JoshuaL> vish, ok ty :)
[20:19] <vish> JoshuaL: gnome-settings-daemon , missed a "s"
[20:19] <JoshuaL> vish, :)
[20:19] <hggdh> micahg: so my view is that if it did not work, let's completely take it out (otherwise we will have to say 'if on a dev release... otherwise ...'
[20:20] <vish> heh , if someone is using a dev release let them learn ubuntu-bug *atleast*
[20:20] <hggdh> vish: +1
[20:20] <micahg> hggdh: yeah, I guess is makes sense, we want to push people towards ubuntu-bug or answers.lp
[20:21] <JoshuaL> vish, got an idea for a nice summary due my limited english :(
[20:21] <hggdh> yeah. COOL! I got two to agree with me!
[20:21]  * hggdh is getting unused to find agreement
[20:22]  * vish yay! removes line
[20:22] <charlie-tca> vish: +1 ont he dev release
[20:22] <charlie-tca> they shouldn't be using it if they can't learn that
[20:23] <hggdh> wow. now 3 aqree with my views!
[20:23] <hggdh> or perhaps *I* am the one agreeing with them?
[20:23] <hggdh> hum
[20:23] <charlie-tca> I thought it was just me
[20:23] <vish> JoshuaL: "theme settings do not apply fully" , but first search for any similar bugs :)
[20:24]  * hggdh goes to think about philosophy impact in the world
[20:24] <JoshuaL> vish, i will of course, thanks :)
[20:25] <sense> micahg: I'm thinking about proposing a UDS-N session about Answers as primary bug inlet, but not sure where to start the discussion about such a sesison.
[20:26] <micahg> sense: no, answers is for support, bugs is for bugs
[20:26] <sense> micahg: But most bugs are support requests for writing a proper defect report, and when people have a bug they also often want to know how to handle the thing around it: the report itself, the workaround, etc
[20:26] <charlie-tca> That will really make a mess of it, sense
[20:27] <charlie-tca> We will be the ones having to make all those questions into bugs
[20:27] <micahg> sense: that's why we removed the report a problem link from stable releases
[20:27] <hggdh> but we really should think about scaling the current process
[20:28] <hggdh> it dos not scale well -- see #ubuntu
[20:28] <sense> charlie-tca: it might make a mess, but it would also make it possible for many more people (LoCos) to help. It would limit the inflow of useless bugs to Malone
[20:28] <charlie-tca> Forums, IRC, mailing lists are all for the questions of how to, bug reports are not. We should not double the triage work to reflect it is
[20:28] <sense> charlie-tca: A lot of bug reports are questions of how to, though.
[20:28] <charlie-tca> Can't locos learn to triage?
[20:28] <micahg> sense: not too many bugs filed against malone anymore
[20:29] <micahg> charlie-tca: nah, they're too crazy :-)
[20:29] <vish> we already have "get help online" which points to answers.lp , the only problem i see is translations..
[20:29] <vish> sense: push for lp translations instead :)
[20:29] <charlie-tca> Let them look at the bugs and turn them into questions, if that is what they are.
[20:30] <charlie-tca> If you turn all bug reports into questions first, you better find twice as many bug triage people to handle it
[20:31] <micahg> sense: this should have been mostly fixed since report a problem was removed from the stable release except for Firefox which will be fixed soon
[20:31] <sense> micahg: That doesn't stop people from going to Launchpad to file the bug there.
[20:31] <JoshuaL> vish, charlie-tca thanks for the help :D
[20:31] <micahg> sense: that's why we disabled the report a bug link except for bug control members
[20:32] <yofel> sense: but that will at least show them the 'howtoreport' page
[20:32] <charlie-tca> You already have a shortage of people to sort the bugs out. Why add to that workload. The real answer is to get the information out to the users, not give them bad advice when it comes to filing a real bug.
[20:32] <sense> micahg: and there are a lot of those bugs coming from people running the development release, which does have Apport enabled.
[20:32] <sense> charlie-tca: I do agree with you that migrating to Answers could cause a horrible mess and a lot of work for the people who provide support.
[20:32] <vish> charlie-tca: teach to fish! +1
[20:33] <sense> So if we would ever do such a thing we should be very careful.
[20:33] <micahg> sense: I think we've done all we can in that regard, we need ways for people to file real bugs, that's ubuntu-bug, the fact that people don't DTRT is an education issue
[20:33] <yofel> sense: how is apport not enabled in the devel release?
[20:33] <yofel> erm, nvm
[20:33] <yofel> I'm getting tired
[20:33] <sense> yofel: So am I. ;)
[20:33] <charlie-tca> Careful is the wrong thing here! teach the users what to use, instead of teaching them to use the wrong tool for the job.
[20:35] <charlie-tca> +1 micahg
[20:37] <yofel> bdmurray: can you resync the gm script responses with the new one btw? https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[20:39] <JoshuaL> i always use apport-bug to report a bug
[20:40] <yofel> JoshuaL: ubuntu-bug is a linkt to apport-bug so they're exactly the same
[20:40] <yofel> *link
[20:40] <JoshuaL> ah ok :D
[20:44] <vish> we need to edit this as well https://help.ubuntu.com/community/ReportingBugs
[20:44] <vish> "Use the menu - try this first!" hehe!
[20:45] <JoshuaL> lol
[20:45] <JoshuaL> I find it easier to ask for help here, makes it easier to explain my situation :)
[20:59] <kc7zzv> I'm trying to collect information for a bug report, but the bug is causing my internet connection not to work.  I tried using "apport-cli -f -p linux -u 601159" but it's telling me "This is not a genuine Ubuntu package".  Is this because I'm using the 10.10 nightly build?
[21:01] <yofel> kc7zzv: tried running apt-get update?
[21:01] <vish> kc7zzv: did you download the mainline kernel?
[21:01] <kc7zzv> kc7zzv: I didn't get the mainline kernel yet.  That's my next step.
[21:01] <yofel> apport really needs to get a more detailed error message :/
[21:02] <kc7zzv> vish: Should I be doing that first?
[21:02] <vish> kc7zzv: nah , just wondering since the message mentioned  "This is not a genuine Ubuntu package"
[21:02] <vish> bug 601159
[21:02] <ubot2> Launchpad bug 601159 in linux (Ubuntu) "e1000 ethernet port intermitently works (affects: 1) (heat: 119)" [Undecided,Incomplete] https://launchpad.net/bugs/601159
[21:03] <yofel> kc7zzv: just to make sure that's not an issue with apport, what does 'apt-cache policy linux-image-$(uname -r)' give you?
[21:04] <kc7zzv> yofel: The problem happens about 50% of the time.  Should I reboot, run "apt-get update" and then get the bug again?
[21:05] <yofel> kc7zzv: apport requires you to use a kernel that is available in the archive, like right now in maverick -13 is an obsolete kernel since -14 is available in the archive
[21:06] <micahg> bug 562964 is probably it
[21:06] <ubot2> Launchpad bug 562964 in apport (Ubuntu) "ubuntu-bug "This is not a genuine Ubuntu package" message is misleading (affects: 2) (dups: 2) (heat: 39)" [Wishlist,Triaged] https://launchpad.net/bugs/562964
[21:06] <yofel> right
[21:07] <kc7zzv> vish: Installed: 2.6.35-14.19 \n Candidate: 2.6.35-14.19 \n Version table: \n *** 2.6.35-14.19 0 \n 100 /var/lib/dpkg/status
[21:08] <yofel> that's right except for the missing mirror line, like '500 http://ftp-stud.hs-esslingen.de/ubuntu/ maverick/main Packages' and thus apport fails, try to refresh the package cache
[21:08] <yofel> ... somehow
[21:08] <kc7zzv> With "apt-get update"?
[21:09] <yofel> yes
[21:09] <kc7zzv> Ok.  It may take me a few reboots to get it working.  I'll get back to you.
[21:10] <micahg> yofel: that won't help, that's not the issue
[21:10] <micahg> the issue is the one I linked to
[21:10] <micahg> in that once a package is obsoleted, the message is misleading
[21:10] <bdmurray> yofel: http://bazaar.launchpad.net/~canonical-qa/canonical-qa-tracking/main/annotate/head%3A/gm-xml-files/bugsquad-replies.xml
[21:13] <kc7zzv> micahg: So if that bug is the problem, my problem with apport should be fixed after "apt-get update && apt-get -y upgrade"?
[21:14] <micahg> kc7zzv: no
[21:15] <micahg> kc7zzv: well, if you upgrade to the new kernel maybe
[21:16] <kc7zzv> Because if I run "apt-get upgrade" won't I them be using what ever superseded my current package?
[21:16] <kc7zzv> Sorry, I know a bit about Linux, but not much about
[21:16] <kc7zzv> *about Ubuntu.
[21:17] <hggdh> kc7zzv: if you upgrade, yes, you would be using the current linux-image (to keep in with your issue)
[21:17] <yofel> micahg: it should fix it in this case as -14 is the newest kernel, it's just that his package cache doesn't reflect that
[21:18] <yofel> bdmurray: will you change it or should I change it and file a merge request?
[21:20] <kc7zzv> yofel: Running "apt-get update" fixed it.  Thanks.
[21:20] <yofel> np
[21:35] <bdmurray> yofel: I'm at debconf at the moment so a merge proposal would be quicker
[21:35] <yofel> ok, will do
[21:36] <bdmurray> yofel: great, thanks
[21:38] <kc7zzv> yofel: Ok.  I've got the apport, and I uploaded it with ubuntu-bug, but it doesn't remember that I told apport-cli that it's an existing bug, and when I click "Yes, this is the bug I'm trying to report"
[21:39] <kc7zzv> it throws away the report instead of adding it to the bug.
[21:39] <hggdh> kc7zzv: how did you run ubuntu-bug? Exact command, please
[21:40] <kc7zzv> "ubuntu-bug /tmp/apport.linux-image-2.6.35-14-generic.UV_yqM.apport"
[21:41] <hggdh> kc7zzv: yes, this will create a new bug
[21:42] <hggdh> hum
[21:42]  * hggdh refuses, right now, to look at the code
[21:42] <kc7zzv> hggdh: I don't think it did create a new bug because I told bugs.launchpad.net that this is an existing bug.
[21:43] <hggdh> kc7zzv: it *would* create a new bug
[21:44] <hggdh> kc7zzv: try ubuntu-bug -u <bug#> -c <crashFile>
[21:44] <hggdh> not sure it will work
[21:44]  * hggdh now goes to look at the code
[21:50] <kc7zzv> hggdh: The program didn't complain, but it doesn't seem to be using the bug report.
[21:50] <hggdh> kc7zzv: yeah, I sort of expected that
[21:50] <hggdh> did it update the bug?
[21:51] <kc7zzv> I didn't send it because the bug isn't happening right now so dmesg is wrong.  Should I send it?
[21:53] <hggdh> I am not sure there is a way of updating a bug with a saved report... we might need a bug against apport on that
[21:55] <kc7zzv> What about creating a new bug and copying the information from the old.  Then setting the old bug as a duplicate?
[22:02] <kc7zzv> hggdh: Can you think of a better way?
[22:03] <hggdh> kc7zzv: just open a new bug, and refer to the old one. This is better
[22:04] <hggdh> oops. Gone
[22:05] <kc7zzv> hggdh: What?
[22:06] <yofel> [23:03:50] <hggdh> kc7zzv: just open a new bug, and refer to the old one. This is better
[22:06] <kc7zzv> Ah.  Thanks.
[22:24] <hggdh> kc7zzv: even more because the kernel team would rather have individual bugs, and then they will weed out duplicates
[22:25] <hggdh> it is not that easy to have the exact same configuration
[22:30] <kc7zzv> hggdh: Ok.  I've got the new bug posted, and both bugs have links to each other.  Now, do I leave the status of the original bug as "Incomplete", or do I change it?
[22:30] <hggdh> kc7zzv: leave the original as is, and yours as New
[22:30] <kc7zzv> hggdh: Does is make a difference if both bugs are mine?
[22:31] <hggdh> oh
[22:32] <hggdh> well, yes. Same issue?
[22:32] <hggdh> kc7zzv: ^
[22:33] <kc7zzv> hggdh: Same issue and same computer.  There's not much information on the first one because at that time, no one could tell me how to upload a apport report if the computer has no internet connection.
[22:34] <hggdh> kc7zzv: then you can close the old bug INVALID (superseeded by the new one)
[22:34] <hggdh> kc7zzv: and thnak you for your patience :-)
[22:35] <kc7zzv> hggdh: Ok.  Thanks.  I have to go now, but I'll get to it later today.
[23:41] <Mathuin> Does anyone know whether the next "bug day" has been scheduled?  The wiki shows the most recent one as July 15 for pidgin.
[23:41] <micahg> Mathuin: when someone organizes one
[23:42] <Mathuin> Okay, so it's when someone gets a bug up their butt, so to speak, not a regularly scheduled monthly/quarterly/whatever sort of thing?
[23:43] <micahg> Mathuin: well, it was almost weekly, but I think people got busy
[23:43] <Mathuin> One of the reasons I switched to Ubuntu was because FreeBSD didn't respond to bugs.  I wanted to set aside calendar time for a bug day to help keep that from happening.
[23:43] <micahg> Mathuin: that's great!, but you don't have to wait for a bug day, find a package you care about, look at the bugs, and come in here and ask questions
[23:45] <Mathuin> The package that inspired me to check in here is Empathy.  The documentation seems a little crazy.  I think it's more a Gnome thing than an Ubuntu thing, though.  What's the best way to reach out to those folks when IRC doesn't seem to be attended?
[23:48] <micahg> Mathuin: bcurtiswx is familiar with empathy
[23:49] <Mathuin> bcurtiswx: if you have any tips on who I can contact to learn more about hopefully helping with the documentation for Empathy, I'd really appreciate it.
[23:59] <Mathuin> The other project on my radar is "screenlets".  The maintenance seems to be spotty and scattered, and there's one particular bug that really affects me, so I'm taking the leap of applying to the dev team in hopes of being able to fix the bug and help with others.  Whee.