[00:26] <bdmurray> crimsun: what are you saying in bug 532586?  is the alsa-driver task invalid?  are a.tom's comment's relevant to that bug?
[00:26] <ubot4> Launchpad bug 532586 in pulseaudio (Ubuntu) (and 1 other project) "pa_stream_writable_size() failed: Connection terminated errors not caught by apport (affects: 4) (heat: 20)" [Undecided,Incomplete] https://launchpad.net/bugs/532586
[00:33] <crimsun> bdmurray: I don't know offhand if the alsa-driver task is invalid for the OR, but I'm not pleased that a.tom decided to spew crap into that bug report.
[00:33] <crimsun> this is yet another example of "oh, the symptom appears to be mine, too, so let's spew garbage into someone else's bug report"
[00:34] <crimsun> for sound bugs, particularly because the underlying hardware is usually quite different, we want new bugs, not stuff being littered into others' reports
[00:37] <bdmurray> one thing the X team does is put hardware information in the bug title I wonder if that has had any affect on that issue
[00:38] <crimsun> it's done for the symptom now, i.e., ubuntu-bug audio
[00:42] <bdmurray> do you think the same should be done for pulseaudio?
[00:49] <crimsun> bdmurray: I don't see why not, but I'm not going to do it in time for 10.04 LTS since I have $crapton other bugs to look at.
[02:20] <Darrell> hey i don't really know what im doing
[02:48] <Soultaker> Anybody active here and know about the x.org bug?
[02:52] <micahg> Soultaker: https://wiki.ubuntu.com/X/Testing/GEMLeak
[02:54] <Soultaker> ah... excellent... thanks
[03:01] <zeroseven0183> Does anyone know if this is a bug in Bazaar or really just a connection error? I'm trying to download the project files of Ubuntu Manual last night via "bzr branch lp:ubuntu-manual" then I cancelled it. Now I'm not able to continue or restart the downloading
[03:02] <zeroseven0183> The error message I receive is "bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist."
[03:03] <micahg> zeroseven0183: branch into a new folder
[03:04] <zeroseven0183> I've tried that with a different folder name, but I still have the same problem
[03:04] <zeroseven0183> I've tried also into a new folder with the same name
[03:07] <micahg> zeroseven0183: idk, check in #bzr
[03:07] <zeroseven0183> I did "bzr launchpad-login zeroseven0183" and "bzr whoami" just to make sure
[03:07] <zeroseven0183> Alright
[03:07] <zeroseven0183> Thanks
[04:09] <zeroseven0183> ping micahg
[04:09] <zeroseven0183> micahg, I've worked with the people in #bzr
[04:10] <zeroseven0183> Now it's OK. I can now download the Ubuntu Manual project files again
[04:10] <zeroseven0183> It turns out that it's looking for the public key file that it's not in the ~/.ssh directory
[04:10] <micahg> zeroseven0183: great
[04:11] <zeroseven0183> Looking at the command line "progress bar", I see that it's not changing
[04:11] <zeroseven0183> [#########-          ]     97KB    51KB/s | Fetching revisions:Insert <-- slow connection, maybe?
[04:12] <zeroseven0183> or impatient, I am?
[04:12] <persia> impatient.
[04:13] <persia> I find that bzr speed is entirely unrelatd to bandwidth available.  it gets better with every release, but takes a while for initial branching.
[04:13] <zeroseven0183> Hahaha I knew someone would say that. Correct!
[04:14] <zeroseven0183> So I guess I don't have to worry then even if I'm downloading torrents
[04:14] <zeroseven0183> +1 for patience
[04:15] <zeroseven0183> Thanks guys
[04:16] <persia> Well, if your connection is *really* full, that can degrade bandwidth available to bzr, but if you can still IRC without painful lag, you probably have available bandwidth.
[04:17] <zeroseven0183> Yes, persia. Thanks
[09:10] <BUGabundo_remote> Get up on your Horse, and Ride till the Sunset 0/
[15:47] <miked595> is there a know issue with an upgrade from ubuntu 9.10 to 10.04 and the boot failing due to usbfs?
[15:47] <miked595> i had to comment out "none /proc/bus/usb usbfs devgid=125,devmode=664 0 0" in my /etc/fstab
[15:53] <genii> I thought /proc/bus/usb mounting was deprecated sometime in .. like... 2008
[15:53] <miked595> not sure.. it was in there
[15:54] <miked595> I have gone throug ha few dist upgrades
[15:54] <miked595> s/ha/a/
[15:54] <genii> miked595: Ah. Likely a remnant from Something prior to 8.04 then
[15:55] <mrand> Either that, or maybe you added it for virtualbox usb support?
[15:56] <miked595> genii: I wonder if the upgrade break because if it. is that something they should comment out automatically?
[15:56] <jibel> miked595, yes, I don't remember the bug number. It's used by virtualbox to unable usb support if I remember
[15:56] <miked595> virtualbox is installed.. i dont use it though.. vmware works better. should prob remove it, jibel
[16:00] <yofel> bug 507881 ?
[16:00] <ubot4> yofel: Bug 507881 on http://launchpad.net/bugs/507881 is private
[16:00] <yofel> bug 507881
[16:00] <ubot4> Launchpad bug 507881 in plymouth (Ubuntu Lucid) (and 3 other projects) "Plymouth doesn't show messages sent before the splash screen is visible (affects: 36) (dups: 4) (heat: 228)" [High,Fix committed] https://launchpad.net/bugs/507881
[16:00] <yofel> miked595: ^
[16:02] <jibel> yofel, that's the one I was looking for. Thanks.
[16:02] <miked595> yofel: guess that's it. thanx. since it's a known issue no need to worry
[16:25] <qense> We should make it more obvious how to attach files to bug reports.
[16:26] <qense> Again someone posted his logfiles in a comment...
[16:27] <yofel> move the 'Add attachment or patch' above the comment box?
[16:27] <yofel> would look a bit out of place though
[16:28] <thekorn> if len(comment) > 500: msg_box("are your sure about adding such a huge comment? [yes/no] what about adding your information as an attachment, and only quote relevant parts in the comment itself?")
[16:28] <qense> thekorn: That sounds like the best solution..
[16:28] <yofel> +1
[16:29] <thekorn> I know ;)
[16:29] <qense> Is there a blueprint for the UDS somewhere we could stick this suggestion on?
[16:31] <thekorn> I don't know, maybe there is a "get in touch with the lp devs"-session again this time
[16:31] <qense> Would be nice.
[16:33] <yofel> well, we should have a meeting before uds-m too so adding it to the agenda would be an option too
[16:39] <micahg> yofel: meeting is scheduled for after UDS
[16:40] <yofel> ah
[16:41] <yofel> oh right, it would be in the same week...
[17:09] <kklimonda> heh, nothing like getting a bug that is in fact 9 different issues..
[17:10] <BUGabundo_remote> ahah
[17:10] <BUGabundo_remote> really?
[17:10] <BUGabundo_remote> what was is it kklimonda?
[17:11] <kklimonda> bug 568322
[17:11] <ubot4> Launchpad bug 568322 in transmission (Ubuntu) "Some functions aren't working like they should (see description) (affects: 2) (heat: 10)" [Undecided,Confirmed] https://launchpad.net/bugs/568322
[17:11] <kklimonda> and it's already confirmed -.-
[17:14] <charlie-tca> but confirmed by another user. That doesn't mean there is enough information to triage it
[17:14] <kklimonda> I know :)
[17:16] <charlie-tca> I knew you knew, too ;-)
[17:17] <charlie-tca> but you got to admit, it does keep things interesting to see one like that occassionally
[17:17] <kklimonda> charlie-tca: It's a mother of all bugs ;)
[17:18] <charlie-tca> yay!
[17:18] <kklimonda> charlie-tca: it's funny that someone took time to find and describe all the issues but didn't check how to report bugs
[17:18] <charlie-tca> yup, but it happens a lot, or used to, anyway ;-)
[17:21] <yofel> that reminds me of the comments about the bug filing link redirection, where all say they can't file bugs but probably took more time to find the bug to comment on than reading the wiki page would have taken...
[17:22] <BUGabundo_remote> kklimonda: should htat be marked as invalid
[17:22] <BUGabundo_remote> and new fork bugs filled
[17:22] <BUGabundo_remote> ?
[17:24] <kklimonda> BUGabundo_remote: I'd say it depends on the bugs reported - if they are worth keeping track of then yes - new bugs should be opened for each issue and the metabug should be closed.
[17:24] <kklimonda> BUGabundo_remote: but in this case I think it's easier to just respond to each issue and say that it works as intended ;)
[17:26] <kklimonda> at least one issue is a duplicate
[17:27] <kklimonda> BUGabundo_remote: it can also be converted into one of detailed reports so you don't have to close it.
[17:41] <candtalan> hi, I have just downloaded, burned and run the lucid RC live CD, and a crash occurred which cannot be reported in the usual way
[17:42] <candtalan> Report window: sorry the program 'gdu-notification-daemon' closed unexpectedly
[17:43] <candtalan> This happens on two different machines
[17:45] <charlie-tca> candtalan: you could file it using this - https://help.ubuntu.com/community/ReportingBugs#Filing%20bugs%20at%20Launchpad.net with
[17:45] <charlie-tca> the logs from the crash
[17:45] <yofel> candtalan: wait, you do get a crash notification? why can't you report it?
[17:46] <candtalan> when I tried alt F2   an duse th epackage name etc etc it says th eitem is not running
[17:48] <yofel> candtalan: can't you report it from the crash notification?
[17:48] <yofel> candtalan: and do you get a .crash file in /var/crash/ after the crash?
[17:48] <candtalan> yofel: no it says it is not possible
[17:49] <yofel> what reason?
[17:49] <candtalan> log - will look
[17:50] <candtalan> crash: /var/crash yes: _usr_lib_gnome-disk-utility_gdu-notification-daemon.999.crash
[17:51] <yofel> candtalan: ok, and what happens if you run 'ubuntu-bug /var/crash/*.crash' ?
[17:53] <candtalan> yofel: reason: I click on Report problem, apport starts collecting, then says: problem in gnome disc utility, the problem cannot be reported, The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.
[17:53] <candtalan> I note that I am using th eRC LiveCD
[17:54] <yofel> ah, then there was an assertion failure and apport failed to get the assertion failure message, such a report would be useless indeed
[17:54] <candtalan> charlie-tca: i will try to report as suggested
[17:54] <yofel> maybe something got logged in ~/.xsession-errors
[17:58] <bdmurray> thekorn: do you still use ipython?
[17:58] <thekorn> bdmurray, yes
[17:58] <thekorn> of course!
[17:59] <bdmurray> Does bug 384713 affect you?
[17:59] <ubot4> Launchpad bug 384713 in ipython (Ubuntu) (and 1 other project) "print statement does autocall inside interactive indented blocks (affects: 9) (dups: 2) (heat: 19)" [High,Triaged] https://launchpad.net/bugs/384713
[17:59] <nigelbabu> bdmurray: did you get time to hack on the graph script?  (if not I can take a stab today :) )
[18:00] <thekorn> looking
[18:01] <bdmurray> nigelbabu: not yet, if I remember the discussion correctly it'd be best if the new columns were added to the end of the csv
[18:01] <nigelbabu> bdmurray: I'll work on it tonight.  anway u-u-s and u-m-s needs to go
[18:04] <thekorn> bdmurray, yes, I can confirm this bug with ipython and python2.6 (in lucid and karmic)
[18:05] <thekorn> however with python2.{4,5} it is working correctly, no indention error
[18:06] <bdmurray> thekorn: oh hey, its fixed in trunk
[18:07] <bdmurray> I wish my bzr foo was beter so I could find the change
[18:11] <thekorn> bdmurray, cool, getting the branch now, maybe I can help you to find the relvant change
[18:12] <bdmurray> thekorn: If we could find the patch I'd upload it in a heartbeat! ;-)
[18:21] <mrand> bdmurray: any chance there is a bug somewhere that left a bread crumb for what the change number was?  If all else fails, I sometimes try bzr log | grep X
[18:22] <mrand>      ^^^^^^^^^^^^^^^^^^^  pet peeve of mine
[18:26] <bdmurray> mrand: thanks I think I got it bug 414967
[18:26] <ubot4> Launchpad bug 414967 in ipython (Ubuntu) (and 1 other project) "print statements get incorrectly mangled by the autocall feature under Python 2.6 (affects: 12) (dups: 5) (heat: 71)" [Undecided,New] https://launchpad.net/bugs/414967
[18:26] <bdmurray> via searching for for other upstream bugs
[18:28] <bdmurray> well maybe not if it isn't fixed yet
[18:29] <mrand> bdmurray: but it says "merged", so someone cleaned it up.  Or do you mean not fixed upstream?
[18:30] <bdmurray> well the upstream bug is in progress
[18:30] <bdmurray> and I'm not certain the branch is related
[18:33] <bdmurray> yeah the branch linked just has the emacs tab completion patch
[18:34] <thekorn> bdmurray, I think this two bugs are not related
[18:34] <thekorn> your one is about idention level in the history is not parsed correctly
[18:35] <thekorn> where the second one is about print(1,2) not giving the correct result in python2.6
[18:35] <thekorn> it should return "1 2", but it prints "(1, 2)
[18:38] <bdmurray> thekorn: ah right
[19:40] <vish> genii: hi.. if you run into any doubts just ask here , if someone is around they will answer :)
[19:41] <genii> vish: ?
[19:41] <vish> oops! it was genux ^ :s
[19:42] <vish> genii: tab fail :(
[19:42] <genux> hi vish..
[19:42] <genii> vish: Ah, no worries then
[19:43] <genux> I was just wondering if I could "watch" someone doing a triage.
[19:44] <vish> genux: you mean like follow another triager and keep track of him/her or... just watch and learn?
[19:44] <ddecator> vish: i almost did the same thing =p
[19:44] <ddecator> genux: you could apply for a mentor
[19:44] <genux> yeah.. just to watch and learn
[19:45] <vish> genux: then can apply for the mentor.. i believe ddecator is  part of the mentors ...
[19:45] <ddecator> vish: yes sir =)
[19:46] <vish> :)
[19:46] <genux> k.. shall do :). thanks vish and ddecator
[19:46] <ddecator> genux: no problem!
[19:47] <genux> I have just requested on the bugsquad mentorship :).
[19:49] <vish> genux: sweet! , and thanks in advance for helping out with the bugs :)
[19:50] <ddecator> genux: what time zone are you in?
[19:51] <genux> nps.. vish .. it would be great to be part of it :)
[19:51] <genux> ddecator: I live in the UK (Norwich at present) so UTC
[19:51] <ddecator> hm, so idk if our time would match up well =\
[19:54] <genux> so.. do not follow ? ddecator what is idk ?
[19:54] <genux> so =soz
[19:54] <ddecator> idk = i don't know
[19:56] <genux> oh ? why is that ? what time zone do you live in ?
[19:56] <semmy> Hello, I'm looking to learn how to triage bugs!
[19:56] <persia> semmy: Great.  Have you read the links in the /topic?  Do you have questions?
[19:57] <ddecator> i live in chicago, so CST. i usually work on triage from 0200-0500 UTC (9:00pm-12:00am CST)
[19:57] <micahg> ddecator: that should be (9:00pm-12:00am CDT) :)
[19:58] <ddecator> micahg: is it? i thought is was Central Standard Time o.o
[19:58] <micahg> ddecator: CST is UTC -6, CDT is UTC -5
[19:58] <ddecator> micahg: oh, right...
[19:58] <ddecator> so CDT then =p
[19:59] <genux> arh.. k.. I would have to be up early then ;).. I do have a daugther that wakes at 5:30 UTC lol..
[20:00] <ddecator> no problem, there are others on the team that can help you out =)
[20:05] <semmy> persia: Yes, I've read the triage-guide, and I think I've finished all of the other requirements for membership on the bugsquad.  I'm hoping to get started with evince today -- how do I know which version of evince to use?  Also, I'm still running Karmic; should I upgrade to lucid to get started?
[20:06] <ddecator> you can still triage on karmic
[20:06] <persia> semmy: You can triage bugs in karmic, but yeah, at this point upgrading to lucid will probably be beneficial.
[20:06] <persia> Release is in a week, so there really shouldn't be any showstoppers left (I've been running lucid for a while, happily).
[20:06] <persia> But ddecator is right: the key is more being able to read and test, than what you run.
[21:24] <mf__> hi all
[21:25] <mf__> i have a problem whith new ubuntu
[21:25] <mf__> no popup indicator
[21:27] <mf__> when LCD brightness buttons pressed
[21:27] <mf__> and xev not detect it
[21:27] <mf__> laptop asus a6VM