[07:55] <njin> Hello to all, can we have keycodes inthe order of four hundred (470,471,472....) on a sony vaio? bug 691826 thanks
[07:55] <ubot2> Launchpad bug 691826 in linux (Ubuntu) "fn keys don't work on SONY VAIO VPCEB3J1E, Maverick (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/691826
[13:54] <njin> hello to all, can someone look if is a security vulnerability ? bug 692362
[13:54] <ubot2> Launchpad bug 692362 in ubuntu "Plugin-container WOT wont enable (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/692362
[13:56] <charlie-tca> There is a whole team set up to do just that. All we can do is recommend it if we think it might be.
[13:58] <charlie-tca> I see nothing there that tells me it is anything more than a user rant. Where are the logs to show what is happening?
[13:59] <charlie-tca> It could be nothing more than a failing drive or very insecure network connection
[13:59] <njin> charlie-tca: hello, thanks .
[14:55] <ElPasmo> Hi people, I'm looking for the azureus bug list in LP and I see a lot of bugs set as New of old versions of azureus. Should I ask if the bug is present in the actual versions and set them to incomplete? Is that the right thing to do?
[14:56] <hggdh> eeebotu will be offline for some 2 minutes for an update restart
[15:00] <greg-g> ElPasmo: you can also try reproducing the symptoms. If you can reproduce them then set it to confirmed and say what version it is and what steps you took to reproduce it.
[15:01] <greg-g> ElPasmo: if you can't reproduce it, tell the reporter you tried but if they could also try AND give a specific set of steps to reproduce it, that'd be great. (and set to incomplete)
[15:01] <ElPasmo> Ok greg-g.. thanks a lot. I'll do that
[15:01] <greg-g> np
[15:01] <ElPasmo> Another question, should I try it both in 10.04 (cuz is LTS) and 10.10 or only in Maverick?
[15:01] <hggdh> eeebotu is back online
[15:02] <greg-g> also, if there is an upstream bug tracker, and you confirmed the bug yourself (reproduced it), feel free to report it upstream as well.
[15:02] <greg-g> ElPasmo: just in 10.10 is fine
[15:02] <ElPasmo> ok greg-g thanks a lot :)
[15:02] <greg-g> no worries, thanks for helping!
[15:10] <ElPasmo> I found a bug wich is solved with the last version of the application (but the last version is not available at the ubuntu repositories. Should I set it to Fix released? I'm talking about bug 553315
[15:10] <ubot2> Launchpad bug 553315 in azureus (Ubuntu) "Vuze search doesn't work...SWT issue? (affects: 8) (heat: 41)" [Undecided,New] https://launchpad.net/bugs/553315
[15:12]  * greg-g looks
[15:12] <greg-g> ElPasmo: so, since the bug is still in maverick, but is fixed in an upstream release, the next step would be to see what version is in Natty
[15:13] <greg-g> I usually use http://packages.ubuntu.com/ to figure that out.
[15:13] <greg-g> Looks like natty has the same version as Maverick, right now http://packages.ubuntu.com/search?keywords=azureus&searchon=names&suite=all&section=all
[15:16] <ElPasmo> yes... so, how do I proceed?
[15:16] <hggdh> oh hell, I forgot to update the eeeBotu id :-(
[15:16] <greg-g> ElPasmo: I'm looking for the right documentation
[15:17] <ElPasmo> mmm thanks a lot for your time greg-g, if you can point me to the documentation I could check also
[15:19] <greg-g> ElPasmo: well, wiki.ubuntu.com is where I'm looking
[15:19] <ElPasmo> :P ok
[15:20] <joaopinto> which package should I use to file a bug for the global menu ?
[15:20] <greg-g> I'm not sure if the right workflow is: 1) go to Debian and request an updated version 2) when Debian has it request a Sync from Debian or if it is something else
[15:22] <greg-g> bdmurray_: package is outdated in both Natty and Debian Unstable, a new version fixes a lot of bugs, whats the right next step? Going to Debian and putting in a request to update (there is no related bug in bugs.debian.org) or do something more Ubuntu-centric at first?
[15:23] <charlie-tca> Anyone know who bugbot is in launchpad. It appears to be a script that leaves comments on bugs but forgets to change the status.
[15:48] <ElPasmo> greg-g, as I can see at https://wiki.ubuntu.com/SyncRequestProcess if we are before the debian import freeze is no need of an explicit sync request (we have 9 days) maybe we should proceed directly with the first option ("go to Debian and request an updated version")... don't know really :)
[15:51] <greg-g> ElPasmo: yeah, we can try. :) Have you reported a bug in Debian before, it can be daunting compared to Launchpad
[15:52] <ElPasmo> No, never, I'm trying to figure it out but no joy... I'm totally lost :P
[15:52] <greg-g> and, I don't think I have time right now to explain it, hopefully someone else watching can
[15:53] <ElPasmo> ok greg-g, thanks for all your help :)
[15:53] <ElPasmo> I'll ask at #debian, maybe I'll be lucky :)
[15:54] <greg-g> good idea
[15:55] <ElPasmo> well in fact, if I'm not wrong, Debian has an older version of the package: http://packages.debian.org/lenny/vuze
[15:55] <charlie-tca> This is a good place to start - https://wiki.ubuntu.com/Debian/Bugs
[15:56] <ElPasmo> no, my falt
[15:56] <ElPasmo> fault*
[15:56] <charlie-tca> Although, I stay away from Debian as much as I can
[15:56] <ElPasmo> ok thanks charlie-tca
[15:56]  * charlie-tca thinks "daunting" was a good word for that
[15:58] <ElPasmo> mmm if you can point me another way of do it I'll be glad to follow your lead :)
[15:59] <charlie-tca> Sorry, that's what I actually use
[15:59] <ElPasmo> hahaha :)
[16:00] <ElPasmo> Anyway, even if I manage to request a sync in Debian... how should I proceed with the launchpad bugs? set them to Fix released?
[16:01] <charlie-tca> triaged, until the sync is confirmed, then fixed
[16:03] <greg-g> ElPasmo: the status of the bug in LP is for the status of the bug in the latest version of Ubuntu, so until the package has been released to the archives and you can install it, it isn't fix released.
[16:03] <ElPasmo> Thanks charlie-tca. Another question, I found for one of the bugs and upstream bug... but they told me (at debian) to file a new wishlist bug requesting the sync. I think it's better to link to that new upstream request than to the old one... Is it ok?
[16:03] <ElPasmo> ok greg-g, I understand now
[16:04] <charlie-tca> yes
[16:05] <greg-g> (sorry, I tend to be verbose and redundant ;) )
[16:05] <charlie-tca> Since the new upstream bug will fix the issue when resolved, it's okay
[16:05] <charlie-tca> greg-g: I seem to be a little on the weak side of explaining sometimes, it's okay
[16:06] <greg-g> charlie-tca: we're a good team, then :)
[16:07] <ElPasmo> hey, you manage to make me succeed triaging bugs... you must be outstanding you two :P
[16:08] <charlie-tca> got a good student!
[16:09] <ElPasmo> don't know what to say snif snif
[16:11] <vish> pedro_ , charlie-tca , hggdh : several of the students are not subscribed to the mentoring mailing list , so I think we need to remind them again, how does this sound : http://pastebin.com/EAD5YnDD  ?
[16:11] <vish> maybe we can exclude the WE CARE part ;p
[16:12] <hggdh> I think it is good as it is
[16:12] <hggdh> and we DO care :-)
[16:13] <charlie-tca> but why are we giving them two months to start? Shouldn't they be starting THIS WEEK?
[16:14] <vish> charlie-tca: yea, we could shorten that interval, but i just named it 2 months since we have responded very late for a lot of the students
[16:14] <vish> so let me know which time limit is ideal..
[16:14] <charlie-tca> All the more reason to get them started as soon as possible. Perhaps the first week of January, this being the holiday season
[16:15] <charlie-tca> two months seems too long. We have more waiting to be added, that will be waiting that two months
[16:15] <vish> charlie-tca: oh, that 2 months is for people who have not subscribed yet..
[16:15] <vish> charlie-tca: so even for them first week of Jan ?
[16:16] <charlie-tca> I can subscribe to a mailing list in about 5 minutes
[16:16] <ElPasmo> mmm that reminds me, I ask for a menthor like... 2 weeks ago? I didn't receive any email. Is that normal?
[16:16] <charlie-tca> so, if they aren't triaging the first week of Jan, let's give the next person a chance
[16:17] <charlie-tca> ElPasmo: yes, normal for now
[16:17] <vish> charlie-tca: yup, i dont mind even deactivating them even now ;p , but some might have lost interest , i was just playing safe but sure , so Jan 8 th ?
[16:18] <charlie-tca> sure, at least in my mind.
[16:18] <charlie-tca> hggdh: any comment?
[16:19] <charlie-tca> pedro_ 's not here right now
[16:19] <vish> oh! he is on vac?
[16:19] <hggdh> I agree that we might go more agressive now in taking them out if no response
[16:19] <charlie-tca> The longer we let these people wait to start, the longer we make others wait for a mentor
[16:20] <vish> OK,  so setting Jan 8th as the date to subscribed by..
[16:20] <charlie-tca> Thanks, vish
[16:20] <vish> hggdh , charlie-tca: thanks you sir :)
[16:36] <ElPasmo> I think bug 553315 should set to Triaged with a Medium importance.
[16:36] <ubot2> Launchpad bug 553315 in azureus (Ubuntu) (and 1 other project) "Vuze search doesn't work...SWT issue? (affects: 9) (heat: 44)" [Undecided,New] https://launchpad.net/bugs/553315
[16:36] <ElPasmo> May someone do it for me please?
[16:38] <ElPasmo> Also I think bug 525304 should set to Triaged with a Low importance. May someone do it for me please?
[16:38] <ubot2> Launchpad bug 525304 in azureus (Ubuntu) (and 1 other project) "Icons of toolbar not appear (affects: 3) (heat: 18)" [Undecided,Confirmed] https://launchpad.net/bugs/525304
[16:43] <charlie-tca> ElPasmo: done
[16:43] <ElPasmo> Thanks a lot charlie-tca
[16:44] <charlie-tca> yw, keep up the good work! It is really appreciated to have someone helping out
[16:45] <ElPasmo> The bug 321922 ask for a sync that already took place. Should I set to fix released also in the debian upstream bug?
[16:45] <ubot2> Launchpad bug 321922 in azureus (Debian) (and 1 other project) "vuze 4.2 new upstream release (affects: 3) (heat: 5)" [Unknown,New] https://launchpad.net/bugs/321922
[16:45] <ElPasmo> I'm trying, lot to learn charlie-tca  :P
[16:46] <charlie-tca> just set the debian task to invalid in launchpad.
[16:46] <ElPasmo> thanks again
[16:46] <charlie-tca> ooops
[16:46] <ElPasmo> w8, why "ooops"?
[16:47] <charlie-tca> might be bad advice. Normally, we just leave the upstream task alone. It will update itself eventually.
[16:47] <charlie-tca> but it is okay
[16:47] <ElPasmo> Ok, it is 18 months old... I think it should be ok I set it to invalid
[16:48] <ElPasmo> I'll comment any way
[16:48] <charlie-tca> Since we can't manually set status without removing the bug watch, it is difficult to do much with those.
[16:49] <charlie-tca> The fact that the Ubuntu task is fixed-released should be enough to keep anyone from adding to the bug report.
[16:49] <charlie-tca> but, I do in fact change some when I get tired of looking at them
[16:51] <ElPasmo> I see...
[16:51] <ElPasmo> It'd be crazy if I ask for adopting the vuze package? Should I w8 to have more experience?
[16:56] <charlie-tca> You have the ability to maintain it if you want to. Your experience comes with time, but you pretty much know how to work those bugs, don't you?
[16:56] <charlie-tca> I think you could go ahead with adopting it, if you want to.
[16:59] <ElPasmo> Ok, thanks charlie-tca
[17:10] <ElPasmo> Well I have to go, see you people, and thanks for all the help again
[17:21] <kamusin> it's me god or gnome-system-tools are not installed by default with natty alpha1 ?
[18:07] <kklimonda> kamusin: it got removed from ubuntu-desktop for whatever reason
[18:09] <kamusin> kklimonda, oh lord.. thanks
[18:10] <kklimonda> bah, they should really link changes to ubuntu-meta to bug reports.
[18:18] <kamusin> kklimonda, do you know if there is a bug report about it?
[18:23] <kklimonda> kamusin: I don't see it mentioned in the changelog, you best bet is to ask either on #ubuntu-desktop or directly Colin Watson who can point you further.
[18:25] <kamusin> kklimonda, ;)
[21:35] <nemo> hey guys. I encountered what I'm pretty sure is:
[21:35] <nemo> https://bugzilla.redhat.com/show_bug.cgi?id=622790
[21:35] <ubot2> bugzilla.redhat.com bug 622790 in cifs-utils "Input/output error with sec=krb5" [Medium,Assigned]
[21:35] <nemo> after a NAS migration at work
[21:35] <nemo> on my ubuntu boxes
[21:35] <nemo> My question is...
[21:36] <nemo> Is there some way to see if this bug is reported in ubuntu, and what PPAs/patches/workarounds might be mentioned?
[21:37] <nemo> hm
[21:37] <nemo> actually. it can't be that bug. n/m
[21:37]  * nemo hunts for cifs + NAS bug reports w/ similar symptoms