=== Spec is now known as x-spec-t
[01:42] <Nattgew> when and why is a bug assigned to someone?
[01:43] <jjesse> when someone takes a bug?
[01:43] <jjesse> an example i am going to work on a bug so i asign it to me
[01:47] <Nattgew> work on it like fix it or triage it
[01:48] <greg-g> fix it
[01:48] <jjesse> both
[01:48] <greg-g> if you are just triaging a bug, do NOT assign it to yourself (or another triager)
[01:48] <greg-g> no
[01:48] <greg-g> no
[01:48] <greg-g> that signifies that someone is working on fixing the problem
[01:48]  * greg-g apologizes for the repeated no
[01:49] <jjesse> np
[01:49] <Nattgew> so if someone randomly assigns a bug to me...?
[01:49] <greg-g> Nattgew: and you didn't say you were gonig to fix it, then feel free to remove the assignment
[01:49] <greg-g> which bug?
[01:50] <Nattgew> https://bugs.launchpad.net/ubuntu/+source/xsensors/+bug/183330
[01:50] <ubotu> Launchpad bug 183330 in xsensors "xsensors lacks support for coretemp module" [Undecided,New]
[01:50] <greg-g> jjesse: you are from Michigan yes?  I'm not sure if we have met, I'm Greg, the current team whip for Michigan
[01:50] <Nattgew> no, i'm not from michigan, but I've been there
[01:51] <Nattgew> oh, nvm, misread that
[01:52] <greg-g> Nattgew: I do believe there was talk of that being how we did things before, but now we aren't assigning triagers to bugs, just to reduce the confusion regarding who is really working on a fix for the bug
[01:52] <Nattgew> okay thanks
[01:52] <greg-g> yep, no prob
[03:04] <juaniv_a> hi i'm new in this lands
[03:05] <juaniv_a> i have recently signed to launchpad and the code of conduct
[03:05] <juaniv_a> i have recently applied for ubuntu-bugs team too
[03:06] <catterly> juaniv_a: hello and welcome!
[03:06] <juaniv_a> thanks
[03:07] <techno_freak> welcome juaniv_a
[03:07] <juaniv_a> I'm 20 years old and I'm from Argentina
[03:07] <juaniv_a> I've been using ubuntu for a year
[03:08] <juaniv_a> and I've been thinking that it would be nice if i can cooperate to make ubuntu better
[03:08] <juaniv_a> so that's why I'm here
[03:14] <catterly> juaniv_a: that is a pretty good reason, decided it was time to give back to the project?
[03:14] <catterly> that is why I came here as well, just yesterday or the other day, to help triage bugs for the upcoming release
[03:16] <JohnPhys> It's why I started running hardy on a spare partition
[03:17] <juaniv_a> yes it was to time to give back :)
[03:18] <juaniv_a> i read about the bug team
[03:18] <juaniv_a> but i don't understand quite well what do I have to do
[03:19] <catterly> well, basically you can follow this and #ubuntu-bugs-announce, which announces new bugs as they happen
[03:19] <catterly> from there you can mark bugs as duplicate, confirm them, and comment asking users for more information when necessary
[03:20] <catterly> all as appropriate
[03:20] <catterly> there is probably a wiki page somewhere...hmm...
[03:21] <yuriy> in /topic
[03:22] <catterly> oh, yes :]
[03:23] <juaniv_a> ok i'm reading :)
[03:27] <catterly> the HelpingWithBugs page seems to be an excellent resource!
[03:29] <techno_freak>  catterly https://wiki.ubuntu.com/Bugs/HowToTriage is your friend
[03:30] <juaniv_a> thank you
[03:39] <juaniv_a> where are you from?
[03:41] <yuriy> juaniv_a: US here. you should see about an Argentina local community team
[03:42] <yuriy> juaniv_a: https://wiki.ubuntu.com/ArgentinaTeam
[03:43] <juaniv_a> thank you, I am in the argentina team mailing list
[03:43] <yuriy> great :)
[04:07] <snerfu> I am new to submitting bus on launchpad, how do I make my bug non private?
[04:08] <snerfu> It has this lock icon up in the top right corner.
[04:08] <techno_freak> snerfu, bugs are non private by default
[04:09] <savvas> snerfu: there's a 'set privacy' on the left menu :)
[04:09] <snerfu> ah, ok thanks.
[04:10] <snerfu> There we go, non private. sweet.
[04:10] <savvas> be careful though, sometimes private bugs contain personal info
[04:11] <snerfu> I looked through all the logs included in it, I don't think it does. But I don't really have much personal info on there.  Hopefully enough to contact me if they need  more information.
[04:12] <savvas> I meant if you were doing anything bank-related or editing passwords and such :)
[04:12] <snerfu> Ahh, I got ya. Thanks for the tip.
[04:13] <snerfu> This was a minor glitch in soundconverter.
[04:43] <juaniv_a> I have a problem here
[04:44] <juaniv_a> rhythmbox doesn't make my tag changes
[04:44] <juaniv_a> for example i change artist tag
[04:44] <juaniv_a> and then it comes back as it was
[04:44] <juaniv_a> before
[05:23] <techno_freak> phew! my share for the bug bug is done :)
[05:23] <techno_freak> bug hug*
[05:29]  * yuriy hugs techno_freak 
[05:30]  * techno_freak hugs yuriy 
[05:30]  * yuriy hasn't done anything yet
[05:30] <techno_freak> yuriy, there are lot of edgy dapper bugs in them, i managed to clear some, you have more left
[05:31] <techno_freak> and before secretlondon arrives, we need a dupe-hunter ;)
[07:02] <techno_freak> ah here comes the dupe-hunter ;)
[07:03] <secretlondon> ;)
=== secretlondo is now known as secretlondon
=== Qbix is now known as QbixAway
[07:51] <jussi01> Is ubiquity bug day still going on?
[07:53] <techno_freak> juaniv_a, think it just started ;)
[07:53] <techno_freak> err.. jussi01 ^^
[07:54] <jussi01> techno_freak: ok, great :D
=== secretlondo is now known as secretlondon
[07:56] <jussi01> Hmmm, Ive no Idea where to start on this, but it would be great if we can get some work done on: https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/95886
[07:56] <ubotu> Launchpad bug 95886 in ubiquity "Wrong keyboard layout after installation (US instead of FI)" [Low,Confirmed]
[09:00] <gggggig> hi
=== secretlondo is now known as secretlondon
[09:01] <gggggig> A game (fretsonfire) freezes my 2.6.24-12 kernel
[09:02] <gggggig> I tried to run it from ssh but it doesn't work, any ideas how to debug it?
[09:02] <secretlondon> gggggig, have you submitted a bug?
[09:02] <gggggig> secretlondon: no
[09:02] <secretlondon> gggggig, please submit a bug first
[09:03] <gggggig> secretlondon: I'd like to collect some data before.. do you know where to find some interestng log?
[09:04] <secretlondon> gggggig, if it actually freezes yours system then debugging system crash on the wiki
[09:05] <gggggig> secretlondon: do you have a link?
[09:05] <secretlondon> i can find one
[09:06]  * secretlondon has poor internet so it'll take a few seconds
[09:07] <secretlondon> gggggig, https://wiki.ubuntu.com/DebuggingSystemCrash
[09:07] <gggggig> secretlondon: ok, thanks
[09:09] <secretlondon> gggggig, also if its a game you may find stuff in ~.xsession-errors
[09:32] <secretlondon> https://wiki.ubuntu.com/UbuntuBugDay/20080325
[09:43] <gggggig> https://bugs.launchpad.net/ubuntu/+bug/206437
[09:43] <ubotu> Launchpad bug 206437 in ubuntu "kernel 2.6.24-12-generic freezes with nvidia" [Undecided,New]
[09:44] <gggggig> I tried DebuggingSystemCrash but I don't get any useful error
[09:44] <gggggig> .xsession-error has nothing releated to this bug
[09:45] <techno_freak> gggggig, xsession-errors will have errors related to X-session crashes
[09:45] <techno_freak> gggggig, the bug you show is a kernel bug
[09:45] <secretlondon> techno_freak, he said it was a crash with a game
[09:45] <secretlondon> techno_freak, sdl games tend to output a lot of xsession-errors
[09:46] <techno_freak> secretlondon, he is referring "kernel 2.6.24-12-generic freezes with nvidia"
[09:46] <gggggig> it could be an nvidia bug..
[09:46] <secretlondon> techno_freak, I know, but he originally told me it was a bug with fretsonfire, which is why I suggested xsession errors
[09:46] <gggggig> but in the but I got something in the dmesg
[09:46] <techno_freak> secretlondon, i agree to what you told :)
[09:47] <secretlondon> fretsonfire has loads of unloved bugs
[09:47] <techno_freak> secretlondon, may be he is generalizing all bugs to xsession-errors ;)
[09:47]  * secretlondon is now working through them
[09:47] <techno_freak> hmm
[09:48] <secretlondon> xsession-errors is useful for debugging games issues in my experience
[09:48] <gggggig> I played some day ago with Glest and I had no problem
[09:48] <gggggig> maybe is something related to f1 f2,.. keys
[09:48] <gggggig> even if I'm using metacity
[09:49] <secretlondon> I don't know, my laptop freezes every so often and I can't pin it down. could be hardware/software/anything
[09:49] <secretlondon> very annoying bugs
[09:56] <gggggig> see you later
[09:59] <secretlondon> bye
=== secretlondo is now known as secretlondon
[10:53] <rgrig> james_w, thanks for the pointer to edos. it turns out we did the same thing :(. the output is a little bit different but that may be because of _our_ bugs :)
[10:54] <james_w> rgrig: no problem, did you take the same approach?
[10:55] <rgrig> james_w, yeah, there are only small differences (such as that we reuse minisat, while they reimplement it form the minisat paper)
[10:55] <james_w> ah, interesting that you came to the same solution.
[10:56] <rgrig> a little disappointing that we are one year late, though :)
[11:02] <james_w> can someone on hardy open rhythmbox and got to the Jamendo tab and see if they get any tracks please?
[11:05] <seb128> james_w: I get some text explaining what jamendo is
[11:05] <james_w> seb128: and does that disappear and show a track list?
[11:06] <seb128> james_w: do you get https://bugs.launchpad.net/bugs/203428?
[11:06] <ubotu> Launchpad bug 203428 in rhythmbox "jamendo no loading catalogue" [Medium,Invalid]
[11:06] <james_w> it appears as though Jamendo have changed the format of the dbdump file that rhythmbox uses to get the track information, so it shows no tracks.
[11:07] <james_w> it's different to that bug, but I think it's the same cause.
[11:07] <pedro_> morning
[11:07] <seb128> the bug states that's what jamendo sends is buggy though
[11:07] <seb128> hey hey pedro_
[11:08] <pedro_> bonjour seb128
=== asac_ is now known as asac
[11:22] <secretlondon> hi pedro_
[11:22] <secretlondon> pedro_, do you have the perms to update the /topic with today's hug day?
[11:23] <pedro_> secretlondon: hello, no sadly i don't :-(
[11:23] <secretlondon> I've updated the wiki
[11:39] <salty-horse> hi. is anyone upgrading from gutsy->hardy any time soon? I'd like to reproduce a problem with date&time configuration migration
[11:44] <heno> salty-horse: please ask liw in #ubuntu-testing. He's starting on a series of upgrade tests now
[11:45] <salty-horse> great. thanks!
[12:28] <dako3256> test
[12:28] <ogra_cmpc> failed
=== chuck_ is now known as zul
[12:34] <Iulian> Hey
[12:39] <hammera> Hello! My name is Attila Hammer. My hardy beta installation is good, except the final restart. the installer not restart my computer.
[12:39] <hammera> Possible because I launch ubiquity with terminal?
=== MarioH is now known as MarioHock_ger
[13:15] <urc_jim> morning all
[13:16] <catterly> good morning!
[14:12]  * heno waves to simira
[14:13] <heno> *** HUG DAY TIP ***: Here is a good place to find exiting bugs for duplicate candidates: http://people.ubuntu.com/~brian/reports/gt5comments/ubiquity.html
[14:13] <heno> and http://people.ubuntu.com/~brian/reports/gt5subscribers/ubiquity.html also
[14:14] <Iulian> Awesome
[14:16] <pascal80> How should translation related bugs be handled?
[14:16] <pascal80> E.g. bug #206524
[14:16] <ubotu> Launchpad bug 206524 in ubuntu "Upgrade to 8.04 window has incoherent messages" [Undecided,New] https://launchpad.net/bugs/206524
[14:19] <pedro_> pascal80: that's french right? you may want to assign it to the language-pack-fr then
[14:21] <Iulian> Hi pedro_
[14:21] <pedro_> hey Iulian, how are you today?
[14:22] <Iulian> I'm doing fine, thanks. What about you?
[14:23] <pascal80> pedro_: Yes that's French, I subscribed ubuntu-l10n-fr
[14:23] <pascal80> pedro_: Was this the right thing to do?
[14:23] <pedro_> Iulian: pretty good also, enjoying the day ;-)
[14:24] <seb128> reassigning to language-pack-gnome-fr too
[14:24] <pedro_> pascal80: yes, language-pack-fr would work
[14:24] <pedro_> ah yes what seb128 said too
[14:30] <pedro_> sourcercito: does it works now?
[14:30] <sourcercito> pedro_, i'm actually waiting until some page with a problematic image loads
[14:31] <sourcercito> you know, me and my great ISP
[14:31] <sourcercito> :P
[14:31] <pedro_> lol
[14:32] <sourcercito> yup, seems to work just fine here :P
[14:35] <pedro_> cool
[14:58] <afflux> morning
[14:58] <bicyclist> Good morning.
[14:58] <bicyclist> does anyone else have those weird pink shadows in compiz when running Hardy Heron ?
[14:59] <afflux> bicyclist: I don't. Do you have a screenshot?
[15:00] <bicyclist> Well yes.
[15:00] <Iulian> That bug is already reported to LP, let me search it.
[15:01] <bicyclist> I am just wondering is it a thing that will be fixed in by the bugsquad or do we have to wait for a reaction of NVidia ?
[15:02] <Iulian> See bug 186382
[15:02] <ubotu> Launchpad bug 186382 in linux-restricted-modules-2.6.24 "[nvidia 169.xx] gtk window decorator somtimes draws decoration ugly or not at all" [Low,Confirmed] https://launchpad.net/bugs/186382
[15:02] <Iulian> Is it the same bug that you have?
[15:09] <sourcercito> secretlondon, could you please free the lock at 5-a-day repo
[15:10] <sourcercito> entering to ~/.5-a-day-data and executing "bzr break-lock" will do the trick
[15:11] <james_w> sourcercito, secretlondon: bzr break-lock remote-url is probably what you want.
[15:12] <sourcercito> sure, that would work too :D, if you can remember the url ;)
[15:12] <james_w> bzr break-lock bzr+ssh://secretlondon@bazaar.launchpad.net/~E5-a-day/5-a-day-data/main/
[15:13] <bicyclis1> But it is the bug that marcelo reports. OTher than the pink shadows all my windows are just fine !
[15:13] <juaniv_a> hi
[15:16] <juaniv_a> what do I have to do if I assign a bug to myself?
[15:16] <bicyclis1> juaniv_a I assume... fix it ?
[15:17] <juaniv_a> I supposed
[15:17] <juaniv_a> mmm so it's nobody :P
[15:17] <juaniv_a> i don't know how to fix it
[15:17] <juaniv_a> i'm new sorry for my questions :P
[15:18] <sourcercito> juaniv_a, hi there
[15:18] <qense> hello
[15:18] <bicyclis1> Hey, no offense meant
[15:18] <bicyclis1> besides fixing it can also mean finding out who can help with the code.
[15:19] <bicyclis1> Or if there is a workaround to be documented.
[15:19] <sourcercito> if you can't solve the bug yourself, you could ask any relevant information there is to it, so when all the information is provided the source of the problem can be easily identified
[15:20] <bicyclis1> Has anyone any idea why camorama states it cannot open /dev/video0 yet Camera Monitor informs me that the cam has been activated  Everything works fine with cheese.
[15:21] <afflux> bicyclis1: camorama -D
[15:21] <qense> happy hug day btw
[15:21] <afflux> uh, hugday o.o
[15:22] <afflux> it's holidays for me, so I forgot the date :)
[15:24] <afflux> bicyclis1: depending on the debug output, it could be a duplicate of bug 201030
[15:24] <ubotu> Launchpad bug 201030 in camorama "[7.10] Could not connect to video device (/dev/video0)" [Medium,New] https://launchpad.net/bugs/201030
[15:28] <qense> BUg 206031 indicates that there could be a problem with the CD upgrading. But does anyone know what things could help solving this?
[15:28] <ubotu> Launchpad bug 206031 in console-tools "package console-tools 1:0.2.3dbs-65ubuntu5 failed to install/upgrade: " [Undecided,Confirmed] https://launchpad.net/bugs/206031
=== x-spec-t is now known as Spec
[15:39] <bicyclis1> Yupp, ubotu, that is the bug i have, have provided my information as requested in the bug report
[15:41] <afflux> bicyclis1: ubotu is a bot :)
[15:42] <bicyclis1> Grin, i once studied ai so i am still polite to any "artificial intelligence" ;)
[15:42] <afflux> hehe
[15:42] <afflux> bicyclis1: what webcam are you using?
[15:42] <bicyclis1> Well, you never know when they rule the world ;)
[15:43] <bicyclis1> The Webcam built in to my Sony Vaio VGN-FZ31J. Sony Motion Eye webcam, which needs the ricoh drivers.
[15:43] <afflux> what's the device name reported by camorama -D?
[15:43] <bicyclis1> One good point about Hardy Heron already. In Gutsy i had to compile them myself, hardy detected the cam.
[15:43] <afflux> or maybe you can even attach your "camorama -D"
[15:44] <bicyclis1> it is video0 which is recognized by skype and cheese but not camorama
[15:45] <bicyclis1> I adde camorama -D output to the bug report
[15:46] <afflux> thank you very much
[15:47] <bicyclis1> The pleasure is on my side. Love to make a very good ubuntu release even better ;)
[15:47] <pedro_> uh uh have the same camera on my sony vaio
[15:48] <afflux> pedro_: same?
[15:48] <pedro_> not it's broken sadly :-/
[15:48] <pedro_> too much travel i guess...
[15:48] <qense> Does anyone know more about the CD upgrades to help with bug 206031?
[15:48] <ubotu> Launchpad bug 206031 in console-tools "package console-tools 1:0.2.3dbs-65ubuntu5 failed to install/upgrade: " [Undecided,Confirmed] https://launchpad.net/bugs/206031
[15:49] <afflux> bicyclis1: looking at the debug output it seems quite different
[15:49] <pedro_> qense: liw is doing some upgrade testing you can ask him at #ubuntu-testing
[15:50] <qense> ok, thx
[15:50] <afflux> bicyclis1: I think you should report a new bug against "camorama" with "'could not set window info' on Sony Motion Eye", and attach the output and you description, (eg. versions etc.)
[15:50] <afflux> bicyclis1: sorry for the confusion :)
[15:51] <bicyclis1> Ok, no problem will open a new bug !
[15:56] <bicyclis1> afflux: New bug has been reported ;)
[15:57] <afflux> bicyclis1: perfect
[15:57] <bicyclis1> Now continuing the hunt for new ones :)
[15:59] <afflux> bicyclis1: does the cam show up in lsusb?
[16:00] <bicyclis1> Yes:Bus 006 Device 002: ID 05ca:183b Ricoh Co., Ltd
[16:00] <bicyclis1> And it works with motion, cheese and skype.
[16:00] <afflux> bicyclis1: can you attach lsusb -v as a seperate file?
[16:01] <bicyclis1> Sure:
[16:04] <afflux> bicyclis1: I'm going to have a coffee now, I'll mark your bug when I get back
[16:04] <bicyclis1> Ok, attachment is being provided.
[16:38] <Nattgew> if i have a program crashing, and apport isn't coming up, is there any way to make apport handle the crash?
[16:43] <bddebian> Boo
[16:45] <afflux> morning brian
[16:46] <afflux> * bddebian
[16:46] <pochu> Nattgew: double-click the crash in nautilus in /var/crash/
[16:46] <bddebian> Hello afflux
[16:47] <Iulian> Heheh
[16:47] <Iulian> Hi there bddebian :)
[16:48] <afflux> is the 5-a-day branchs unlocked again?
[16:49] <Nattgew> ah pochu thanks but if it doesn't leave anything in /var/crash?
[16:50] <pochu> oh, it should AFAIK
[16:50] <pochu> ls /var/crash/
[16:50] <pochu> language-pack-en.0.crash  _usr_bin_terminator.1000.crash
[16:51] <Nattgew> yeah i did find something in there but it's gksu and i'm looking for evolution
[16:51] <bddebian> Hello Iulian
[17:08] <bicyclist> afflux: Information concerning camorama has been added.
[17:08] <afflux> bicyclist: ah right
[17:10] <afflux> bicyclist: marked the bug as triaged
[17:10] <bicyclist> Good, it is not very important to me but another bug probably fixed ;)
[17:11] <afflux> hm?
[17:12] <bicyclist> A bug found is often a bug fixed ..
=== eretamales_ is now known as eduardo_
[18:11] <CarlFK> how do I report a bug against  https://launchpad.net/ubuntu/hardy/i386/linux-restricted-modules-2.6.24-12-386/2.6.24.11-12.31
[18:11] <CarlFK> the bug is the %d in [54691.507105] wifi%d: unable to attach hardware: 'Hardware didn't respond as expected' (HAL status 3)
[18:12] <CarlFK> just the cosmettics of the %d, not that it doesn't work.
[18:12] <bicyclist> Hmm, just found that there exists a new version of envy named envyng. Will try to install it now and see if i can fix de shadow bugs in gnome with that install.
[18:20] <bicyclist> Hmm, ok. Envy NG will not fix the pink shadow bug .. :(
[18:36] <secretlondon> james_w been out
[18:36] <secretlondon> no idea why it was locked
[18:37] <james_w> secretlondon: it may have crashed during a commit at some point.
[18:37] <secretlondon> bzr: ERROR: Not a branch: "bzr+ssh://secretlondon@bazaar.launchpad.net/~E5-a-day/5-a-day-data/main/".
[18:37] <james_w> I hope you had a good day though.
[18:37] <secretlondon> been applying for jobs
[18:37] <secretlondon> I'm more productive out of the flat
[18:38] <james_w> Ah, sorry, I edited wrong "bzr break-lock bzr+ssh://secretlondon@bazaar.launchpad.net/~5-a-day/5-a-day-data/main/"
[18:38] <james_w> extra "E" before.
[18:38] <james_w> any good ones today?
[18:40] <secretlondon> james_w, well it's hopefully done something
[18:41] <secretlondon> I think the 5 a day applet needs rewriting if one person can break it
[18:41] <secretlondon> james_w I may have a job, I find out on thurs
[18:42] <james_w> cool, good luck!
[18:50] <bicyclist> Could the energy control applet be broken ? It doesn't show a single line above 0 %
[18:53] <greg-g> anybody having problems submitting to 5-a-day? http://www.paste2.org/p/17423
[18:53] <secretlondon> I unlocked it, apparently I'd crashed it or something..
[18:53] <secretlondon> been out for 6 hours
[18:54] <greg-g> everybody is getting that error?
[18:54] <greg-g> hmmm
[18:54] <secretlondon> I dunno
[18:55] <greg-g> others apparently are committing fine (looking at the launchpad page)
[18:56] <james_w> greg-g: try 'cd ~/.5-a-day-data/ && bzr update && bzr ci -m "update"'
[18:56] <greg-g> ci -m ?
[18:56] <greg-g> just curious what is it
[18:57] <thekorn> alias for 'commit'
[18:57] <greg-g> ah
[18:59] <greg-g> no errors, we'll see what the codebrowse says
[19:02] <greg-g> and verified, thanks james_w / thekorn
[19:02] <james_w> no problem
[19:44] <qense> is bug 203262 a high or medium?
[19:44] <ubotu> Launchpad bug 203262 in hwtest "hwtest fails preconfigure" [Undecided,Confirmed] https://launchpad.net/bugs/203262
[19:44] <qense> I think high since it prevents a lot of people from upgrading but I am not sure since high is a very high importance
[19:53] <qense> I'm marking it as high now
[19:55] <bicyclist> hmm getting cd bzr: ERROR: extra argument to command checkout: /home/uwe/.5-a-day-data
[19:55] <bicyclist> bzr failed with error code 768
[19:55] <bicyclist> from add-5-a-day
[19:56] <shaya> sort of wondering why the vmsplice() security hole hasn't been fixed in gutsy?
[19:57] <james_w> bicyclist: do you have the most recent version?
[19:58] <bicyclist> i think so, installed it today.
[19:58] <bicyclist> my launchpad user is my email adress, right ?
[19:58] <james_w> bicyclist: your ~/.bzr.log should have some more information.
[19:59] <james_w> bicyclist: no, mine is james-w
[19:59] <secretlondon> no its you launchpad name
[19:59] <james_w> if you log in to launchpad and click on your name in the top right you will be taken to your home page
[19:59] <secretlondon> so mine is secretlondon, and not my real name
[19:59] <secretlondon> after ~
[19:59] <james_w> the bit after "~" is your username
[20:00] <bicyclist> hmm ok, mine is Uwe Hauck. Does taht mean the thing has a problem with the space ?
[20:00] <qense> does the username can have spaces?
[20:01] <bicyclist> Well mine has !
[20:01] <greg-g> what is in the location bar of your browser?
[20:01] <bicyclist> ah ok, mixed Display name with name.. Its getting late over here.
[20:01] <greg-g> :)
[20:02] <keescook> shaya: why do you think it hasn't been fixed?
[20:03] <shaya> cause I just got a gutsy laptop from dell, did an update w/ security updates and ran the exploit and got root
[20:03] <shaya> hmm
[20:03] <shaya> nevermind
[20:03] <shaya> I'm probably an idiot
[20:03] <keescook> shaya: did you reboot?
[20:03] <shaya> <shaya> I'm probably an idiot
[20:03] <bicyclist> bzr: ERROR: No WorkingTree exists for "file:///home/uwe/.5-a-day-data/.bzr/checkout/".
[20:03] <bicyclist> bzr failed with error code 768
[20:03] <bicyclist> is what i get now
[20:04] <keescook> well, I'd like to make sure.  My tested showed it as fixed.
[20:04] <shaya> though dell is shipping the laptop buggy, probably not the best thing
[20:04] <qense> shaya: you could try at #ubuntu-devel
[20:04] <keescook> shaya: so, it is fixed for you?
[20:04] <shaya> cant reboot right now
[20:05] <keescook> shaya: okay, so you're running the old kernel?
[20:05] <shaya> believe so
[20:05] <shaya> whatever the laptop shipped with
[20:05]  * keescook nods
[20:05] <keescook> do a   cat /proc/version_signature
[20:05] <shaya> yea Oct 14
[20:05] <shaya> so as I said, I'm an idiot
[20:05] <keescook> okay, no problem.  :)
[20:06] <shaya> on a temporary laptop as my thinkpad is having issues, it generally runs ubuntu+1 so was a bit confused
[20:08] <qense> you' re not an idiot, you're using Ubuntu ;)
=== Spec is now known as x-spec-t
[21:55] <blueyed> keescook: why have you changed the status of 195691? I need to re-do those diffs, as mentioned in the last comment. Will do so now.
[21:55] <blueyed> bug 195691
[21:55] <ubotu> Launchpad bug 195691 in dspam "[dspam] [CVE-2007-6418] programming error leading to information disclosure" [Medium,Fix released] https://launchpad.net/bugs/195691
[22:01] <josephpiche> I believe bug 3868 should be marked as a duplicate of bug 7560, but since these are low number bugs, I want to get someone else's opinion
[22:01] <ubotu> Launchpad bug 3868 in nautilus "Emptying trash should really empty trash" [Medium,Confirmed] https://launchpad.net/bugs/3868
[22:01] <ubotu> Launchpad bug 7560 in nautilus "Wastebasket fails with read only directories" [Unknown,Confirmed] https://launchpad.net/bugs/7560
[22:05] <keescook> blueyed: we've been using "In Progress" to mean there are patches ready for sponsoring.
[22:06] <keescook> blueyed: so when I run through the queue and there is a bug marked "In Progress", I flip it back to "Triaged" if it's ready
[22:06] <keescook> er, not ready
[22:06] <blueyed> keescook: really? for security related bugs?
[22:06] <blueyed> so, when the patch is ready I should mark it "in progress"? sounds strange..
[22:07] <keescook> blueyed: yeah.  we needed a way to map to "actual problem" (confirmed), "fix known" (triaged), "needs sponsorship" (in progress), "has been uploaded" (fix committed), and "published in the archive" (fix released)
[22:08]  * DOOM_NX gn all! - Battery Empty
[22:15]  * calc uses In Progress on OOo bugs to mean i need to fix it for the next upload if at all possible, heh
[22:16] <keescook> yeah, the status usage for security is a bit odd
[22:19] <seb128> keescook: "has been uploaded" (fix committed), do you guys really use that?
[22:21] <seb128> I guess it makes sense for security uploads to make sure they have been built and published everywhere
[22:27] <keescook> seb128: yeah, we need it due to the dak/soyuz split
[22:38] <grovers> hello - I have a patched package, I'm just trying to figure out the process to get it into the next upload
[22:39] <secretlondon> you need to make a debdiff
[22:41] <grovers> so, following the packaging guide from here on out? I ask just because the bug fixing article doesn't point anywhere after making the new package
[22:43] <secretlondon> it's probably on the motu miki pages somewhere
[22:43] <secretlondon> I'm not sure from there
[22:44] <grovers> i've got it, thanks, found another good wiki page
[23:06] <blueyed> keescook: /me refreshed/fixed the diffs for bug 195691 and set the status to in progress (unassigning myself).
[23:06] <ubotu> Launchpad bug 195691 in dspam "[dspam] [CVE-2007-6418] programming error leading to information disclosure" [Medium,In progress] https://launchpad.net/bugs/195691
[23:07] <keescook> blueyed: great! thanks.  I will probably get to them tomorrow.  I'm currently building/testing the ruby1.8 updates