[01:02] <Rocket2DMn> hey, if a bug report has a .crash attached, is there generally enough information in it to finish the triage?
[01:02] <Rocket2DMn> see bug 315623
[01:02] <Rocket2DMn> or do we need a full backtrace too?
[01:03] <crimsun> the more pertinent info, the better
[01:04] <Rocket2DMn> lol well yeah, but is it needed?
[01:04] <crimsun> yes, absolutely
[01:05] <Rocket2DMn> ok, ill ask him to get one then, thanks
[02:12] <hggdh> Rocket2DMn, actually a .crash will not help much -- it is better to have apport process the .crash and open a bug with the results
[02:13] <Rocket2DMn> ok, thanks
[02:14] <hggdh> of course, if the reporter posts a nice backtrace/stacktrace, then it should be a good step, but the apport-generated data is usually more complete
[02:14] <PrivateVoid> hey guys...
[02:14] <nhandler> Hey PrivateVoid
[02:15] <PrivateVoid> For the global bug jam I am thinking of running it at a local book store
[02:15] <PrivateVoid> with a projector display of the bugs we are working on..
[02:15] <PrivateVoid> and thinking of making it like a telethon...
[02:15] <PrivateVoid> make sense?
[02:16] <nhandler> Yeah, it makes sense PrivateVoid
[02:16] <PrivateVoid> I assume we can project the 5-A-Day stats in addition to the bug list...
[02:16] <PrivateVoid> We get three TVs and a giant projector screen.
[02:16] <nhandler> PrivateVoid: Just open http://daniel.holba.ch/5-a-day-stats/ in a browser
[02:18] <PrivateVoid> cool
[02:18] <nhandler> PrivateVoid: Do they have internet access and outlets?
[02:18] <PrivateVoid> yes and yes
[02:18] <nhandler> Then you are good to go
[02:18] <PrivateVoid> plus the projectors and three TVs that can be used to display things
[02:18] <nhandler> Sounds awesome. What bookstore is this?
[02:19] <PrivateVoid> https://wiki.ubuntu.com/NewYorkTeam/Events/20090108
[02:19] <PrivateVoid> Barnes & Noble
[02:19] <PrivateVoid> the TVs are not in the picture
[02:19] <PrivateVoid> but are on the side walls and just outside the glass doors above the entrance
[02:20] <nhandler> PrivateVoid: That B&N looks awesome. I wounder if the one by me has a room like that
[02:20] <PrivateVoid> You should check it out...
[02:20] <PrivateVoid> it is a nice public place with exposure...
[02:20] <PrivateVoid> I need to get some posters made to display when we are there
[02:20] <nhandler> PrivateVoid: Thanks, but I don't think I will be flying out to NY to see a B&N
[02:20] <PrivateVoid> No, I mean the one near you
[02:21] <PrivateVoid> you should check that one out
[02:21] <PrivateVoid> to see if it has a room like that
[02:21] <nhandler> Yeah, I will the next time I am there. I know they have a large Starbucks inside, but I don't remember seeing a conference room
[02:22] <PrivateVoid> almost all of them have a 'meeting' room...
[02:22] <PrivateVoid> but they might look a bit different
[02:22] <PrivateVoid> and not all of them have free wireless
[04:38] <crimsun> Lupine: please don't triage general "no sound" bugs to affect alsa-driver. use 'linux' instead.
[04:39] <crimsun> Lupine: this policy is noted at the top of https://wiki.ubuntu.com/DebuggingSoundProblems and greatly assists the audio team
[04:40] <crimsun> (otherwise i end up losing quite a few resources retriaging)
[11:37] <Java_Head> bug #315637 i think the bug should be set to 'wishlist'
[11:39] <Tycho451> Hi everybody, I installed the libc6-i686 upgrade that came up last night (~10h ago), which failed and now I can't boot. chroot from a rescue cd brings a segmentation fault and the forums are down :(
[11:39] <Tycho451> Can anybody here help me or point me in the right direction?
[11:41] <def13b> Tycho451: the ubuntu channel is the one your after I think
[11:52] <Tycho451> Thank you
[11:58] <Lupine> crimsun, will do....thx for the info!
[12:00] <afflux> Java_Head: needs-packaging bugs are usually nothing for brainstorm.
[12:12] <afflux> Java_Head: https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs, I updated to bug accordingly
[12:14] <Java_Head> Bug #315740 I think the bug should be set to 'wishlist'
[12:15] <persia> I don't think 315740 should be "wishlist".  Users of that keyboard will have a hard time.  I'd suggest Low or Medium.
[12:32] <afflux> I just received a mail from a user asking me to fix bug 205364. This doesn't seem to be known to upstream yet. Should I report it to upstream and wait until they fix it?
[12:38] <Hobbsee> afflux: that'd be a good start.
[22:28] <Rocket2DMn> bdmurray, you told me initially that ubuntu-bug existed in Intrepid, but I also saw it in Hardy.  Is it not in Hardy by default (like, did I get it with another package at some point)?
[22:28] <Rocket2DMn> I just finished adding a tidbit about ubuntu-bug to my beginners guide
[22:35] <Rocket2DMn> bdmurray, or is it just that in intrepid you don't need the -p option?
[22:54] <bdmurray> Rocket2DMn: I was checking on a hardy server, I think it is in Hardy desktop
[22:55] <Rocket2DMn> alright, i wasnt entirely sure so i just said an up-to-date Hardy
[22:55] <Rocket2DMn> i saw that there is a newer version of apport hardy-updates
[22:55] <Rocket2DMn> thought it may have come with that
[23:17] <LimCore> https://bugs.launchpad.net/ubuntu/+source/tor/+bug/314585 - is anyone working on it, or sohuld I make it public to give it more attention or what?
[23:17] <LimCore> tor crashes for me
[23:17]  * LimCore also reports it upstream
[23:17] <Rocket2DMn> not allowed to view that
[23:18] <Ryan52> it should only be private if it contains information that the submitter doesn't want other (untrustable) people to see.
[23:18] <Ryan52> so if you're fine with all the information in the attachements being public, and you're the submitter, then make it public.
[23:18] <LimCore> so far just the backtrace of coredump of crash
[23:18] <Ryan52> okay, but does that contain anything that you don't want other people to see?
[23:18] <LimCore> well it crashed quickly, so if it is indeed exploit (DoS?) then its probably well known already
[23:19] <Ryan52> (passwords, bank numbers, etc etc)
[23:19] <LimCore> since I didnt attache the core, therefore no
[23:19] <persia> As long as the coredump itself is done, and the backtrace doesn't contain something like your credit-card number, it ought be safe.
[23:19] <persia> s/done/gone/
[23:19] <LimCore> well, with tor, and running as a relay, full dump would contain some private keys
[23:20]  * Ryan52 nods
[23:20] <persia> RIght, but the backtrace might not: you'd have to examine the files to determine if they are safe.
[23:20] <LimCore> hmm ok I will just report to upstream.. but I guess they will say "zomfg 0.1.x ??? why not 0.2.x"
[23:21] <LimCore> if I will remove some information from bug report, and then make it public,  then the older version will remain private etc?
[23:21] <persia> Not really.  The deleted information becomes deleted.
[23:22] <persia> I believe it may be possible for the LP admins to restore it, but that's not the same as the old report being private.
[23:22] <LimCore> oh well it looks like its fine. private key is probably longer then 40 char string
[23:22] <LimCore> https://bugs.launchpad.net/ubuntu/+source/tor/+bug/314585
[23:22] <Ryan52> here's a stupid question: why can't I see the bug?
[23:23] <LimCore> well it is now public
[23:23] <Ryan52> I'm bug control, I think..
[23:23] <LimCore> Ryan52: perhaps you have to be in security team?
[23:23] <Ryan52> oh.
[23:23] <Ryan52> makes sense.
[23:23] <LimCore> dunno, guessing.. :) it is now public
[23:46] <LimCore> why my bug above is no longer considered security issue?
[23:47] <Ryan52> check the activity log, ask the person who changed it?
[23:48] <kees> I made it not a security bug -- it's only a crash from what I can see
[23:50] <persia> The trick is that if one has a crash in something like tor or revelation or gnupg, it's not a security bug, although it may well be a security issue.  That a crash bug may make a system insecure is different from a securityy bug.
[23:51]  * LimCore thinks of last epic rsa/dsa ssh bug an shutters
[23:52] <LimCore> if it would be up to me I would tread all bugs as security in openpgp, ssh, tor, iptables and few related
[23:53] <kees> if this is more than a crash, I'm all ears.  :)
[23:54] <LimCore> well no idea :)
[23:55] <LimCore> I will wait what upstream says
[23:56] <LimCore> kees: is such imortant program crashes, I would lost my trust in it's quality, and think it may as well have other insecure places leading to real exploit not just some crash
[23:56] <LimCore> also, if one is able to crash tor relay nodes (on ubuntu) then this is bad for secuiryt
[23:57] <LimCore> would it be anyway possible to use more up to date version of tor?
[23:57] <kees> I'm not very familiar with tor myself.  are you able to crash tor with special traffic?
[23:58] <LimCore> I dont know that yet. but it craashed very faslty, in like first 10 hours of operation, so something seems really wrong
[23:59]  * Hobbsee wonders if LimCore has been drinking too much tonight.
[23:59] <Hobbsee> fastly?