[00:01] <bdmurray> soonick_cancun: is there a particular area that you are interested in?
[00:03] <nhandler> Does anyone know how to update the 5-a-day stats page with my recent bug activity? I'm using the 5-a-day-applet to add my bugs. If I look at ~/.5-a-day-data/nhandler, It shows 8 bugs. However, the stats page says I only have 6. The page was just updated, so it should have all 8 of my bugs listed. Any advice?
[00:04] <bdmurray> I believe 5-a-day only commits from your local system hourly to avoid locking issues
[00:05] <soonick_cancun> bdmurray: well i dont know, i want to start with the easiest :P
[00:05] <bdmurray> soonick_cancun: okay, is there a particular piece of software in Ubunut that interests you?
[00:07] <soonick_cancun> i dont know how to answer that question. There are a lot of applications i like. Should i choose a single application to start?
[00:08] <nhandler> bdmurray: Ok, I didn't know that. I thought that they only updated the stats page hourly. I didn't know that they also only submitted your data hourly. Is there any way to figure out the last time data was submitted? Or is there a way to figure out the next time data will be submitted?
[00:09] <bdmurray> soonick_cancun: We could look at some random package but I thought it'd be more interesting to you to choose something you like / use
[00:09] <bdmurray> nhandler: possibly via add-5-a-day and some bug number
[00:10] <soonick_cancun> bdmurray: thats true. I think i would like to make abiword better
[00:12] <nhandler> bdmurray: Is add-5-a-day the same as 5-a-day? I did a '5-a-day --add bug#', but it just told me that the bug has already been submitted today. It didn't give any time
[00:13] <bdmurray> nhandler: hunh, yeah it looks the same
[00:13] <bdmurray> soonick_cancun: you can find abiword bugs at https://bugs.launchpad.net/ubuntu/+source/abiword/+bugs
[00:13] <bdmurray> nhandler: if you add a new bug it'll give you info about when your last upload was I believe
[00:14] <nhandler> bdmurray: Ok. I was hoping there was another way. Like I said, I use the applet normally, and the applet doesn't show a time. Is there a way to force an update?
[00:15] <bdmurray> nhandler: not that I know of
[00:15] <nhandler> bdmurray: Ok, thanks for your help
[00:15] <soonick_cancun> bdmurray: ok, so what should i do when in that page?
[00:16] <bdmurray> soonick_cancun: at the bottom of the list we have some new bug reports that haven't been touched
[00:16] <soonick_cancun> bdmurray: the ones that say Undecided and New?
[00:17] <bdmurray> soonick_cancun: let's look at bug 200636
[00:17] <bdmurray> soonick_cancun: that's correct
[00:18] <soonick_cancun> ok, i have clicked one. Bug #234755. What should i do then?
[00:18] <bdmurray> if we could look at bug 200636 instead I'd appreciate it
[00:18] <soonick_cancun> ok
[00:19] <soonick_cancun> sorry, i hadnt read that
[00:19] <bdmurray> that's okay
[00:20] <soonick_cancun> bdmurray: im there. What should i do?
[00:21] <bdmurray> so reading the bug report we have a pretty good description of the problem
[00:21] <bdmurray> which release of Ubuntu are you running?
[00:21] <soonick_cancun> hardy heron
[00:22] <soonick_cancun> should i get 7.04 to work with this bug?
[00:22] <bdmurray> no, this is something that would benefit from testing in Hardy
[00:24] <soonick_cancun> ok, so how should i start? should i install abiword and see if the bug happens?
[00:24] <bdmurray> If you don't have it installed yet give me a minute
[00:25] <bdmurray> You'd want to install just abiword and not abiword-gnome to recreate their situation
[00:26] <soonick_cancun> should i use synaptic or compile the package?
[00:27] <bdmurray> soonick_cancun: synaptic so we are using the ubuntu package
[00:27] <soonick_cancun> ok, im installing it
[00:30] <soonick_cancun> bdmurray: ok, I click report a bug and nothing happens
[00:30] <bdmurray> soonick_cancun: do you have a browser open?  it opens a new tab in firefox for me
[00:31] <soonick_cancun> yes i have firefox open, but nothing happens
[00:31] <soonick_cancun> my version is in spanish. Could that make a diference?
[00:31] <bdmurray> that's unlikely
[00:32] <bdmurray> are you using gnome?
[00:32] <soonick_cancun> yes
[00:32] <bdmurray> is firefox your preferred browser?
[00:32] <soonick_cancun> yes
[00:33] <bdmurray> are you using firefox 2.0 or 3.0?
[00:34] <soonick_cancun> the beta version that comes with hardy
[00:35] <soonick_cancun> that is 3.0b5
[00:36] <bdmurray> can you pastebin the results of "dpkg -l abiword*"?
[00:37] <soonick_cancun> should i paste it in here?
[00:37] <bdmurray> !pastebin
[00:39] <bdmurray> soonick_cancun: so at paste.ubuntu.com would be good
[00:40] <soonick_cancun> bdmurray: done - http://paste.ubuntu.com/17023/
[00:41] <bdmurray> soonick_cancun: so comparing your output to mine it seems I have abiword-plugins installed and you don't.  Could you install that?
[00:42] <bdmurray> I also have abiword-help installed but I'm guessing its -plugins
[00:46] <soonick_cancun> i installed the plugins but nothing happened. Should i intall the help files?
[00:46] <bdmurray> soonick_cancun: that'd be great!
[00:48] <soonick_cancun> bdmurray: still nothing happens
[00:48] <pwnguin> im helping a guy with a bug who can make the current kernel freeze
[00:50] <bdmurray> soonick_cancun: did you restart abiword?
[00:50] <pwnguin> is there a ppa with an intrepid kernel backported he should try?
[00:50] <soonick_cancun> yes
[00:51] <ogasawara> pwnguin: there is, I'm just not sure if it's finished building successfully.  I'll check
[00:51] <soonick_cancun> bdmurray: i restarted it again. But still nothing
[00:52] <bdmurray> soonick_cancun: what about display credits?
[00:52] <ogasawara> pwnguin: https://edge.launchpad.net/~kernel-ppa/+archive
[00:53] <ogasawara> pwnguin: but it looks like it's still failing to build
[00:53] <pwnguin> ok
[00:53] <ogasawara> pwnguin: the kernel team is working on it though so should maybe be a day or two I'm guessing
[00:53] <pwnguin> well, actually, im not sure it matters
[00:53] <soonick_cancun> bdmurray: it opens a tab in firefox with the credits
[00:54] <pwnguin> its a wacom thing
[00:54] <pwnguin> ogasawara: did you know wacom-tools includes a kernel module?
[00:54] <bdmurray> soonick_cancun: hunh, that's weird. what about check for updates?
[00:54] <ogasawara> pwnguin: dunno
[00:54] <pwnguin> i just realized that now
[00:54] <pwnguin> upgrading probably wont help here =/
[00:55] <soonick_cancun> bdmurray: it opens a tab too
[00:57] <bdmurray> soonick_cancun: okay, well I'm at a loss here as to *what* is wrong but we've done a lot of valuable work on the bug
[00:58] <soonick_cancun> bdmurray: so then the bug doesnt happen at your machine?
[00:58] <bdmurray> And we should add that information to the bug report
[00:58] <bdmurray> soonick_cancun: no it doesn't happen to me
[00:59] <bdmurray> I'd speculate that it is failing trying to gather some information about your system
[01:00] <soonick_cancun> so what should we do now?
[01:01] <bdmurray> soonick_cancun: adding a comment regarding the fact you were able to recreate the bug with Hardy Heron and the specific package version, which you pastebin'ed earlier, would be helpful
[01:02] <bdmurray> soonick_cancun: you can also set the status to Confirmed
[01:06] <soonick_cancun> bdmurray: i did what you told me. Did i do it well?
[01:08] <soonick_cancun> bdmurray: i have to go for 10 minutes. Ill be back to comfirm
[01:10] <soonick_cancun> bdmurray: plans canceled. Ill stay :P
[01:10] <soonick_cancun> bdmurray: did i do it well?
[01:11] <bdmurray> soonick_cancun: yes, that look good
[01:12] <bdmurray> I think it'd be good to also note that the other menu items succesfully open a browser tab to help narrow it down
[01:13] <ffm> Hey!
[01:13] <soonick_cancun> should i write another comment?
[01:13] <bdmurray> soonick_cancun: yeah, that's be great
[01:17] <soonick_cancun> bdmurray: ok. Ive done that
[01:18] <soonick_cancun> bdmurray: how long does my pastebin lasts online?
[01:18] <bdmurray> I'm not certain with that site but if you think it is relevant, which it kind of is, just add it to the bug report
[01:19] <soonick_cancun> can i copy and paste it? or should i attach it?
[01:20] <bdmurray> copy and paste but change the command to 'dpkg -l abiword* | cat' because some of it gets truncated
[01:26] <soonick_cancun> bdmurray: i pasted it. but it doesnt look very well
[01:31] <bdmurray> that's fine at least the complete versions are there
[01:31] <bdmurray> you've subscribed to the bug report which is good in case someone needs to contact you
[01:32] <soonick_cancun> bdmurray: ok, so is this a day?
[01:33] <bdmurray> soonick_cancun: pardon?
[01:34] <soonick_cancun> bdmurray: sorry, i was trying to ask if this was all for today
[01:35] <bdmurray> soonick_cancun: yes, that's all I can help you with at the moment.  however, we've gone over some good things I think.  How to recreate a bug, how to confirm a bug report, and useful information to add in a comment.
[01:36] <soonick_cancun> bdmurray: thank you very much, you helped me a lot
[01:37] <bdmurray> great! there are also a wide variety of resources available in the wiki
[01:38] <soonick_cancun> but what is the next step i should take?
[01:38] <bdmurray> soonick_cancun: with that bug or another one?
[01:39] <soonick_cancun> i dont know i think i could do the same with other bugs. But what should i do after i recreated it. Should i try to fix it?
[01:39] <bdmurray> moving a bug from the New status to Confirmed is very helpful
[01:40] <bdmurray> additionally if we could have proved the bug was fixed in Hardy we could have changed the bug to Fix Released because 7.04 wouldn't be updated for that kind of bug report
[01:42] <bdmurray> looking briefly at the list again we find bug 215845
[01:42] <soonick_cancun> bdmurray: so i should stick to chaging the status of bugs for now?
[01:43] <bdmurray> soonick_cancun: yes, changing the status and making bug reports more complete
[01:43] <bdmurray> soonick_cancun: but if you know how to fix it by all means add that in too!
[01:44] <soonick_cancun> thank you very much bdmurray. Ill then keep working on that
[01:44] <bdmurray> soonick_cancun: great! and thank you for helping to make Ubuntu better.
[01:45] <soonick_cancun> thank you. Hope to see you another day.
[01:46] <bdmurray> I'm here fairly regularly. ;)
[01:46] <soonick_cancun> ok. See you ;)
[06:05] <Gralco> ﻿how do i make my laptop's physical volume control control PCM?
[11:22] <leoquant> : https://help.ubuntu.com/community/HardyUpgrades  the LTS upgrade howto info isn´t correct. there are some bugs related to this wiki. the LTS upgrade doesn´t work is this way.
[11:23] <persia> leoquant: are you sure?  I thought it did work that way, but that the LTS upgrade availability message hadn't been sent yet.
[11:24] <persia> leoquant: compare http://changelogs.ubuntu.com/meta-release and http://changelogs.ubuntu.com/meta-release-lts
[11:24] <ogra> which step doesnt work for you ?
[11:25] <persia> ogra: Step 4 doesn't happen yet.
[11:25] <persia> Err. 5
[11:26] <leoquant> only in the july version of 8.04 ¨(service pack :P¨) it will work that way
[11:27] <ogra> well, the wording might be different yet, but the process is as we tested it for about a month with a good bunch of testers
[11:28] <ogra> you can look it up on the isotesting tracker, it holds the upgrade results as well
[11:29] <ogra> (and 8.04.1 is only some weeks away)
[11:44] <leoquant> persia exactly: step 4 and 5 doesn´t happen.
[11:44] <persia> leoquant: As ogra says, it's just a matter of time.  It will work, once the trigger file is updatd.
[11:45] <persia> Do you think there ought be some different explanatory text on that page?
[11:46] <leoquant> persia i agree with ogra.
[11:47] <leoquant> its a matter of time (2/3 weeks?)
[11:47] <persia> leoquant: Then we are all in agreement :)
[11:47] <leoquant> :)
[11:47] <ogra> :)
[15:40] <afflux> thekorn: I want to search in all "apport-package" tagged bugs for the string "scrollkeeper-update: corrupted double-linked list". will the following command work? bughelper -l https://bugs.launchpad.net/ubuntu/+bugs?field.tag=apport-package -T scrollkeeper "scrollkeeper-update: corrupted double-linked list" "asdf"
[15:41] <thekorn> afflux, yes I think so
[15:42] <afflux> let's hope it does. This will probably take until tomorrow ;)
[15:44] <thekorn> afflux, I'm wondering why you search in all ubuntu bugs,
[15:44] <thekorn> and not only in the scrollkeeper ones
[15:44] <afflux> thekorn: because some packages fail upgrading because of this one, and the crash itself does not seem to generate crash reports
[15:45] <thekorn> ok
[15:45] <afflux> eg. bug 237633 is in ubuntu-docs and is a duplicate of bug 218049
[15:49] <thekorn> afflux, you need to run bughelper with -A to also search in attachment
[15:49] <thekorn> +s
[15:49] <thekorn> otherwise you won't find bugs like 237633
[15:52] <afflux> oh, right. Thanks for the hint!
[15:55] <emgent> Bug #237348
[16:20] <bdmurray> afflux: if you'd like a search done more quickly I might be able to assist
[16:20] <afflux> bdmurray: hi! it looks like it just finished.
[16:21] <bdmurray> afflux: okay, I thought you'd said you expected it to finish tomorrow. ;)
[16:21] <afflux> hehe, looks like launchpad started to like me :)
[16:21] <sectech> Well that was annoying,  I had to go through my entire bug list to see what happened while I was gone for the last 2 weeks...
[16:50] <bddebian> Boo
[18:41] <sectech> Bug 237690...  Does that get set to invalid as per the firefox team?
[18:41] <sectech> I know they get get all the updates before we do
[18:42] <Iulian> Hi
[18:44] <pwnguin> i have to say, closing a dup as "invalid" is pretty bogus
[18:44] <pwnguin> is this really acceptable?
[18:44] <sectech> ?
[18:45] <sectech> pwnguin,  The bug I just mentioned? or another?
[18:45] <pwnguin> bug #221795
[18:45] <sectech> Hmm.,..
[18:45] <sectech> It's not marked as invalid though
[18:46] <pwnguin> i fixed it
[18:46] <sectech> your right though,  invalid isn't appropriate...
[18:47] <pwnguin> and then seb jumps in defending the action because triaging is too hard
[18:48] <sectech> hmm....
[18:49] <hggdh> pwnguin: you can always help, as pedor and se pointe out
[18:49] <hggdh> shoot, this was a very weird mistype :-)
[18:50] <pwnguin> hggdh: i do help
[18:50] <sectech> Crap.... why do I think I just closed out a work flow bug...
[18:50] <hggdh> :-D
[18:50] <persia> sectech: Which bug?
[18:50] <pedro_> hello pwnguin
[18:50] <pwnguin> hi
[18:50] <hggdh> sectech: which one?
[18:50] <sectech> Bug 237690
[18:50] <sectech> I just looked at the reports profile...
[18:51] <sectech> err reporter.
[18:51] <hggdh> sectech: this one does *not* look like a request to update, it is more like "it's there, do what should be done"
[18:52] <hggdh> Hobbsee: ping
[18:52] <bdmurray> sectech: that wasn't a 'workflow' report given the criteria we've been provided
[18:52] <pwnguin> theres no way the firefox people dont know about RC2
[18:52] <bdmurray> However, I wouldn't have invalidated it
[18:52] <sectech> I brought up the issue with RC1 when it came out.... saying that I am surprised no one posted a bug stating to update.... I was told to close out any requests like that because they have there own methods
[18:53] <hggdh> let's play it safe, and ask one dev...
[18:53] <sectech> I think it was gnomefreak who told me to invalidate them.... but I am not 100% on that
[18:54] <hggdh> bdmurray: I feel like I am working government... if unsure do nothing at all ;-)
[18:54] <sectech> heh... that fits with Canada's policies...
[18:55] <bdmurray> hggdh: I personally think that makes it hard to learn
[18:55] <hggdh> +1, for reasons we have already discussed here
[18:56] <persia> Where it's not firefox, we used to tag those with the "update" tag, collect the dupes, and they would eventually turn into a workflow bug, either upstrem refresh, merge, or sync.
[18:56] <persia> For mozilla-team apps, it's less interesting to track.
[18:56] <persia> And few developers will complain if we miss them.
[18:57] <persia> On the other hand, some of them are good user input, and sometimes we miss a good update for a release, which causes strife (e,g, a game client where the primary servers have all upgraded to the new version)
[18:57] <hggdh> pwnguin: I did not mean you do not help, sorry if I gave this, huh, feeling
[18:57] <sectech> Can someone verify bug 237695... I found the package the reporter was stating... but I am running 64 bit
[18:57] <hggdh> persia -- this is why we need very clear documentation on what is, or is not, a workflow item
[18:57] <persia> sectech: You ought be able to run virtualbox in 32-bit guest mode on a 64-bit host.
[18:58] <persia> hggdh: Well, maybe.  I don't think "workflow" is a meaningful category, really.
[18:58] <sectech> persia,  you can... the reporter is saying he can't find the package in the repository though, I found it without any problems though...but I am on a 64 bit platform
[18:58] <hggdh> persia, I agree 100%. We are overloading a BTS with tasks
[18:58] <bdmurray> I think with this one bug it is still a valid bug, it is just that the bug report may not be necessary.
[18:58] <persia> In the case of upgrade bugs, they start as a user request, and if the person working on them doesn't have upload rights, become just a token to store work.
[18:58] <persia> LP needs a better review/sponsoring interface.
[18:59] <sectech> Okay...noted... Don't invalidate those kinds of bugs then
[18:59] <hggdh> LP needs to distinghish between problem recognition/validation and fix efforts
[19:00] <hggdh> these are completely different actions (not to talk about QA, and regression testing)
[19:00] <persia> hggdh: Well, maybe.  Some things go back and forth.  Sometimes I see bugs get all the way to a package in -proposed or in the development repositories, and then go back to incomplete because it turns out it wasn't properly understood, even though someone had a patch and uploaded it.
[19:01] <persia> (and yes, bug reports are different than quality engineering, compliance testing, regression testing, etc.)
[19:02] <pwnguin> bug reports are different than QA?
[19:02] <hggdh> indeed. There is continuous contact between first-level responders and maintainers. Every place I worked on either dev or support we needed it -- and things would start to go shouth when this contact was lost or extremely constrained
[19:02] <hggdh> QA is a different activity
[19:03] <persia> QA and support might generate bugs, but management of bugs is all about understanding problems.  good developers should be part of this bug management, and there needs to be a thick interface between bug managers and developers.
[19:03] <persia> QA and development can be more separate, as long as both groups are well connected to the bug coordinators.
[19:03] <hggdh> (assuming a bug report is valid) the process goes like this: bug reported, bug analysed & understood, necessary docs collected, maintainer action, eventual code fix, QA, deployment (with eventual return to bug reporting, if there was a misunderstand)
[19:04] <hggdh> and the process needs very clear steps. You might look at all of this as a finite state machine, and then you will probably get is better
[19:05] <persia> I disagree entirely.  I like it squishy.
[19:05] <hggdh> :-)
[19:05] <persia> bug reported.  Review by team including QA, developers, other logical thinkers.
[19:06] <hggdh> persia, every system must allow for adjustments
[19:06] <persia> The result may be changes to QA tests, changes to code, or changes to features expected.
[19:06] <persia> Not such a clear handoff between roles.
[19:07] <hggdh> there never is. I have had disagreements with Level 1 and 2 support when I was level 3 or dev, and the other way around. It is a question of talking with peers. The problem is the current dev perception that if I only do BTS, then I am not a peer
[19:09] <persia> hggdh: I don't think that's true.
[19:10] <persia> I think there are a large number of developers who consider many members of bugsquad peers.
[19:10] <hggdh> persia, responses like we had when the whole thing unravelled show it to be not completely false
[19:10] <persia> Further I think there are a number of new developers who are much less experienced with either code or troubleshooting than most of bugsquad.
[19:11] <persia> hggdh: I think there is a vocal minority, and I think that there are communications issues.
[19:11] <persia> These are both soluable.
[19:11] <hggdh> I think it is all a question of trust. If you and I get to work together, eventually you will trust me (or not), and I will trust you (or not). After that, what you say to me (or vice versa) will be heard with much more care.
[19:12] <persia> hggdh: Right.  I think a few new people came, and made some mistakes.
[19:12] <persia> In an atmosphere of poor communication, this led to annoyance.
[19:13] <persia> Hence the discussions.
[19:13] <pwnguin> heh. the perception I get is that if i dont do BTS, the bugsquad doesn't view me as a peer ;)
[19:13] <persia> I think that most of the discussions went fairly well, and there is now greater communication.
[19:14] <hggdh> sigh... pigdin completely froze on me...
[19:15] <hggdh> persia, ,indeed.  Hopefully we will get over it
[19:15] <persia> hggdh: Do you need a repeat of anything?
[19:16] <bdmurray> sectech: did you see what happened to that bug you originall brought up?
[19:17] <sectech> yeah... I noticed that
[19:17] <sectech> They want it open as a tracking bug.
[19:17] <sectech> no problem...
[19:17] <bdmurray> That was more action than I would have expected. ;)
[19:18] <sectech> Yeah reallhy
[19:19] <persia> Sorry.  I don't mean to be disruptive.  Based on past communications, I think sectech did the right thing.
[19:20] <sectech> That's the thing...  You are probably going to get 2 or 3 different answers for every 5 people you ask... I guess it's just a matter of taking the best one and going with it
[19:23] <hggdh> persia -- the last few conversations would be nice
[19:23] <hggdh> I eventually had to reboot... (when nothing else works, power off, count to ten, power on again ;-)
[19:25] <sectech> New bug report:   "Computer makes me count to ten"
[19:25] <sectech> j/k
[19:25] <persia> sectech: Yep.  That's where the expertise of the bug management team comes into play.  Neither QA people nor developers are always right (although those in both groups who also do bug management are more likely to be so).
[19:27] <hggdh> well, this at least will make be able to count to ten. probably
[19:34] <sectech> Can someone fire off the link to the bugcontrol application to me please?
[19:36] <hggdh> sectech: what do you mean? launchpad?
[19:36] <sectech> hggdh,  I clicked on apply for bug control... but it says there is an application that is suppose to go with the process
[19:37] <hggdh> link of where you were?
[19:37] <sectech> https://launchpad.net/~ubuntu-bugcontrol
[19:37] <hggdh> so I can look for it... after the reboot I feel slow
[19:38] <sectech> I have no intention of deviating from what I already do... If I don't know what to do with an issue, I ask...
[19:39] <hggdh> sectech: you will receive an email from bdmurray or ogasawara with the questions
[19:39] <hggdh> or pedor
[19:39] <pedro_> sectech: https://wiki.ubuntu.com/UbuntuBugControl
[19:39] <sectech> Okay thanks
[19:39] <hggdh> pedro. Bloody dyslexia...
[19:41] <sectech> pedro_,  and I submit the application to bdmurray or ogasawara by email?
[19:41] <pedro_> sectech: yep by email to bdmurray
[19:41] <sectech> awesome...
[20:16] <pwnguin> I've got a bug filed against wacom-tools that I think is a kernel bug -- what should I do to hand it off to the right kernel people?
[20:17] <bdmurray> pwnguin: make the bug affect the kernel too?
[20:18] <bdmurray> yuriy: I was gonna make a typo fix to https://wiki.kubuntu.org/DebuggingKDE but don't seem to have an account there
[20:18] <bdmurray> yuriy: I'm not particularly motivated to set one up either
[20:19] <yuriy> bdmurray: wiki.kubuntu.org = wiki.ubuntu.com. it's the same thing, just a DNS alias (I think)
[20:20] <persia> yuriy: If you have an LP account, you have a wiki account.  You may need to use the wiki.ubuntu.com address to log in.
[20:20] <persia> yuriy: Sorry.
[20:20] <persia> bdmurray: ^^
[20:20] <yuriy> o_O
[20:21] <Gralco> can someone help me with installing think finger
[20:23] <bdmurray> yuriy, persia - thanks
[20:24] <persia> Gralco: For installation support, you'd do better in #ubuntu
[20:33] <sectech> There... I think that application went pretty well... Now if I could only do job interviews as good
[22:29] <sectech> ffm, you around?
[22:40] <sectech> Can someone wishlist bug #209258 please?
[22:53] <ffm> sectech: yes/
[22:53] <ffm> sectech: why?
[22:53] <sectech> ffm I was able to get some more symbols for the bug you reported and was able to confirm it
[22:54] <ffm> sectech: cool.
[22:54] <ffm> sectech: I saw your comment, if its in a state that the devels can work on it, isn't it "triaged"?
[22:55] <sectech> It is, but I haven't been approved for bugcontrol yet... so the best I can do is confirmed
[22:55] <ffm> sectech: ah. same here.
[23:06]  * ffm pokes bdmurray ;)
[23:06] <ffm> By the way, whens the next hug day that's on a thursday?
[23:07] <bdmurray> Pedro has been setting up the Thursday hug days
[23:07] <ffm> bdmurray: hrm?
[23:07] <bdmurray> I take care of the Tuesday hug days and Pedro takes care of Thursday so ask pedro ;)
[23:09] <bdmurray> I'd imagine next week though
[23:15] <ffm> kk
[23:19] <persia> bdmurray: Great work on the transparency & governance :)
[23:21] <bdmurray> persia: thanks! that means a lot to me
[23:41] <hggdh> sectech: ping
[23:41] <sectech> hggdh, pong
[23:41] <hggdh> sectech: why wishlist bug 209258?
[23:42] <sectech> hggdh,  The feature is actually acting the way that it should (technically)... It's just very hard to move a bunch of bookmarks at a time....
[23:42] <sectech> So it's more or less a design issue (at least to me)
[23:43] <hggdh> I see asac opened it for ff-3; better ping asac on that
[23:44] <sectech> asac, you around?
[23:44] <persia> hggdh: Aren't feature requests almost always Wishlist regardless of who opened them?
[23:45] <sectech> I imagine he was just assigning it to the right package...
[23:45] <hggdh> persia, methinks so, but asac touched it and did not put is as such
[23:45] <hggdh> so I wonder why
[23:46] <persia> hggdh: Probably interface.  It's two extra page loads to create a bug and set the importance.  I know I've skipped sometimes when I needed a quick bug to remind myself to do something.
[23:47] <persia> I try and go back and fix them when I have time.
[23:47] <hggdh> OK. I tried to ping him on #ubuntu-ddesktop, but he is probably gone for the day (huh, night). I will set it as wish
[23:48] <sectech> Do you Canonical employees work from home?
[23:48] <persia> Ah.  I see why.  He's set it to Invalid on the Ubuntu task, but hasn't set a value upstream (probably waiting for the upstream response)
[23:49] <persia> It could be Invalid/Wishlist, but once Invalid it doesn't really matter.
[23:50] <bdmurray> sectech: asac is in germany and its around midnight there
[23:50] <hggdh> sounds like it, and this is why I wanted to ping him. But to wish it goes ;-)
[23:50] <sectech> bdmurray, that would do it...
[23:51] <hggdh> sectech: wishlisted it
[23:52] <sectech> hggdh,  thank you kindly...
[23:52] <hggdh> sectech: only Canonical people can answer if they work from home ;-)
[23:52] <hggdh> I know *I* do, but I have my own outfit
[23:52] <hggdh> so it is either home or on the road
[23:53] <sectech> I would love to do this as a job... Probably everyone and there dog applies to them though.
[23:53] <sectech> Looking around my local area for QA jobs
[23:53] <hggdh> I am known to have dogs barking on teleconferences :-)
[23:53] <bdmurray> Yes, the vast majority of us work from home.
[23:53] <sectech> lol...
[23:54] <sectech> bdmurray, is it hard to get associated with them?
[23:54] <bdmurray> sectech: associated with Canonical?
[23:55] <sectech> so they recognize you...
[23:55] <bdmurray> I recognize you. ;)
[23:55] <sectech> Guess I am already associated, I am doing triaging.
[23:55] <sectech> heh...  bdmurray I mean for a job...
[23:56] <bdmurray> Ah, there currently any open positions on the distribution QA team.  I think there might be one for the Launchpad QA team though.
[23:57] <sectech> Some day... lol...
[23:57] <sectech> Oh speaking of which,  I submitted my application to bug-control...
[23:58] <bdmurray> I meant aren't for distro qa
[23:58] <sectech> that's what I would want... distro QA.