[00:53] <bcurtiswx> BUGabundo1: got a few free minutes to help me out
[00:53] <bcurtiswx> BUGabundo: got a few free minutes to help me out
[00:54] <BUGabundo> a few
[00:54] <BUGabundo> sup?
[14:19] <nigel_nb> hggdh: are you around?
[14:19] <nigel_nb> can someone wishlist bug 493973 for me please
[14:19] <ubot4> Launchpad bug 493973 in evolution "evolution can't send messages using smtp.gmail.com with default gmail settings" [Undecided,New] https://launchpad.net/bugs/493973
[14:31] <hggdh> nigel_nb: hi, -- not being a bother, but why do you think it is a wish (*I* know why *I* would think so, but... changes in status and importance should have a comment)
[14:31] <mac_v> pedro_: hi.. when a bug which was earlier present , but seems solved by an unknown fix... should it be marked "fix released" or "invalid" ?
[14:32] <mac_v> just asking , since the stock responses has such unknown fixes to me marked as "invalid"
[14:32] <nigel_nb> hggdh: I understand the bug and its a minor and * genuine * feature request (which should be filed upstream, which I'm doing now)
[14:32] <nigel_nb> its not causing any problems, just the user needs to do it manually
[14:33] <pedro_> mac_v, invalid is ok in that particular case
[14:36] <mac_v> pedro_: so should i change this to invalid > Bug #413729 ?
[14:36] <ubot4> Launchpad bug 413729 in f-spot "f-spot.exe crashed with signal 5 in _XError()" [Medium,Fix released] https://launchpad.net/bugs/413729
[14:37]  * mac_v gets confused , since seb128 marks them fix released and a few others mark them invalid... :(
[14:37] <pedro_> mac_v, don't bother about those closed reports
[14:37] <nigel_nb> hggdh: so, am I correct?
[14:38] <mac_v> pedro_: ah.. ok.. thanks .. but in future such bugs are to be marked 'invalid' ?
[14:38] <pedro_> mac_v, if the bug was "fixed" by an unknown way, yes, set those to invalid
[14:38] <pedro_> often people reboot their machine and the bug is fixed
[14:39] <pedro_> or for what ever other reason, marking those as invalid is ok
[14:39] <mac_v> pedro_: if fixed by an update?
[14:39] <pedro_> fix released
[14:39] <mac_v> ah ok
[14:39] <seb128> mac_v, I tend to use fix released when a new version fix the issue
[14:40] <seb128> and invalid when it magically went away after a restart or on next try
[14:40] <mac_v> ah... got it
[14:52] <nigel_nb> pedro_: you're the contact for evolution?
[14:52] <pedro_> nigel_nb, i'm getting the email for the bugs upstreamed there, that'd be a yes
[14:53] <nigel_nb> pedro_: ah, just forwarded an enhancement request upstream
[14:53] <hggdh> nigel_nb: done
[14:53] <nigel_nb> saw your name come up :)
[14:53] <hggdh> nigel_nb: yes, you are correct. But we have to comment on status/importance changes
[14:54] <hggdh> poor pedro_ would really like somebody else to get Evo ;-)
[14:54] <pedro_> btw I moved the bug to Triaged, since nigel_nb sent it upstream
[14:55] <nigel_nb> pedro_: you want some help on evo? I could help
[14:55] <hggdh> oh, I updated in between, I guess
[14:55] <nigel_nb> I sort of started liking upstream gnome :)
[14:56] <hggdh> see you all this evening (US central time evening)
[14:56] <pedro_> nigel_nb, sure! help is always welcome :-)
[14:57] <pedro_> nigel_nb, if you want to send some upstream there's a few on evolution just search for bugs that need to be forwarded upstream in the advanced search
[14:57] <pedro_> there's ~10 that need to be confirmed by someone getting the issue and then be send upstream to the Gnome BTS
[14:58] <nigel_nb> I'll look into it now :)
[15:00] <pedro_> cool! gracias!
[15:01] <nigel_nb> pedro_: how do I search by package?
[15:02] <pedro_> nigel_nb, what do you mean?
[15:02] <nigel_nb> I got it
[15:03] <pedro_> ok
[15:03] <nigel_nb> I wanted to search for evolution, figured it ot
[15:29] <nigel_nb> pedro_: 403682, reported upstream, change status
[15:29] <pedro_> bug 403682
[15:29] <ubot4> Launchpad bug 403682 in evolution "Some attached emails (ie MIME digest) are empty when downloaded from IMAP" [Low,New] https://launchpad.net/bugs/403682
[15:31] <pedro_> done thank nigel_nb
[15:31] <nigel_nb> :)
[15:43] <hggdh> bddebian: boo ;-)
[15:51] <bddebian> Boo too :)
[15:58] <nigel_nb> pedro_: other upstream forwardable bugs, I'm not sure if I can confirm... :(
[15:59] <pedro_> nigel_nb, no problem, thanks for working on those! :-)
[15:59] <nigel_nb> happy to be of help :)
[16:00] <bdmurray> Hello!
[16:00] <pedro_> hola bdmurray
[16:00] <nigel_nb> hello bdmurray :)
[16:01] <andresmujica> hola a todos!  hi everyone !
[16:01] <bdmurray> So, its that time of the month ... for the bug squad meeting!
[16:01] <andresmujica> hi bdmurray hi pedro_
[16:01] <thekorn> hey bugsquad!
[16:02] <andresmujica> hi thekorn
[16:02] <bdmurray> I don't see micahg...
[16:03] <bdmurray> So we'll skip the first two things in the agenda until he shows
[16:04] <bdmurray> Moving on we have "Documented policy for revision of Wiki pages. Some of them need revamp but seems most are unsure of how to go about it."  -- cyan-spam
[16:04] <bdmurray> While I don't think they are present I think there is enough information to discuss this
[16:04] <yofel> hi folks
[16:05] <thekorn> https://wiki.ubuntu.com/BugSquad/Meeting  -- for the reference ;)
[16:05] <bdmurray> I'm personally subscribed to most of the wiki pages I care about
[16:06] <bdmurray> so I'd prefer people just edit them however, from changes of wide scope I like what qsense did with e-mailing the bugsquad
[16:06] <bdmurray> er for changes
[16:06] <bdmurray> Additionally, I believe there was one issue where pages contradicted each other or it was not clear which page was correct.
[16:07] <bdmurray> In that case again e-mailing the bug squad for clarification on a policy makes the most sense to me.
[16:07] <bdmurray> Are other ideas on that topic?
[16:07] <bdmurray> Any - even!
[16:08] <pedro_> indeed that's the best way to go
[16:08] <yofel> well, I mostly agree that the ML would be the best place to discuss propsed changes to the wiki
[16:08] <yofel> and for direct questions we have this channel
[16:09] <bdmurray> yofel: ah, yes that's a good point
[16:09] <andresmujica> subscribing the ML to the bugsquad wiki pages could work too, or would it be just too much noise??
[16:10] <bdmurray> andresmujica: that's an interesting idea as if a policy changed everyone would be notified too
[16:10] <yofel> not if ediors use the 'trivial change' checkbox when needed
[16:10] <yofel> bdmurray: +1
[16:11] <thekorn> maybe we can just give this subscribe ML to wike pages idea a try for a few month
[16:11] <thekorn> s/wike/wiki
[16:11] <andresmujica> yeap
[16:11] <bdmurray> Okay, I see 2 actions to do then.  1) Publicize wiki editing policy.  2) Check with mailing list regarding subscribing to wiki pages.
[16:12] <bdmurray> I can take #1 any volunteers for #2?
[16:12]  * hggdh is still trying to load the wiki page :-(
[16:13] <hggdh> bdmurray: I am not sure I understand #2
[16:14] <hggdh> oh, wait
[16:14] <bdmurray> propose that the bugsquad mailing list be subscribe to "key" wiki pages and run a trial of it
[16:14] <hggdh> yes. As usual, I am slow
[16:14] <bdmurray> or I'm vague ;-)
[16:14] <hggdh> I can do it
[16:14] <bdmurray> hggdh: awesome, thanks!
[16:15] <bdmurray> Are there any other topics for the meeting?
[16:16]  * hggdh apart from the additionals, no, AFAICU
[16:16] <bdmurray> hggdh: additionals?
[16:16] <pedro_> yes, just one
[16:16] <pedro_> well from me at least
[16:16] <pedro_> I'm looking for people to help to organize the next bug days
[16:16] <hggdh> defining a roadmap, single use apport, etc
[16:17] <pedro_> that means , the one for this week and the next one
[16:17] <bdmurray> hggdh: right, however micahg isn't here :-(
[16:17] <pedro_> so if you want to help: just drop your name on https://wiki.ubuntu.com/UbuntuBugDay/Planning
[16:17] <hggdh> pedro_: I am not really available right now (taking time unpaid to be here), otherwise I would be there
[16:17] <pedro_> so we can start to coordinate
[16:17] <pedro_> also, we're looking for a target for the next week
[16:18] <pedro_> so if you have *any* idea don't be shy and add it to the wiki page
[16:18] <bdmurray> pedro_: the no package bugs are quite out of hand
[16:18] <pedro_> also put your name on the organizers section so we can make sure you're going to help with that task too
[16:19] <pedro_> bdmurray, yes and those bug days are always a total success
[16:19] <pedro_> hggdh, no worries, you're having a lot over your plate right now :-)
[16:19]  * pedro_ hugs hggdh
[16:20]  * hggdh blushes, and hugs pedro_ back
[16:20] <pedro_> ok that's all i got from here
[16:20] <bdmurray> pedro_: okay, thanks!
[16:20] <thekorn> I think this daily PPA topic is an important one to discuss, what are the plan for daily PPAs and how is managing bugs in this packages planned?
[16:20] <hggdh> +1
[16:21] <hggdh> the apport one-run (force_start=1) has just been resolved via an update to Karmic
[16:21] <hggdh> thanks goes to micahg for it
[16:21] <bdmurray> hggdh: can you elaborate?
[16:22] <hggdh> apport would not start single-time on karmic due to the change to upstart
[16:22] <hggdh> Lucid was fixed, and micahg prepared a debdiff for Karmic -- and pitti approved and uploaded it yesterday
[16:22] <bdmurray> ah, thanks to micahg then!
[16:23] <hggdh> but, now, back to dailies
[16:23] <hggdh> I think this is more complex than it seems
[16:23] <hggdh> but is extremely needed -- more so given all the blueprints we had at UDS
[16:25] <bdmurray> I'd proposed an idea at https://lists.launchpad.net/ubuntu-bugcontrol/msg00496.html
[16:25] <bdmurray> I'm not sure why that thread is on the bugcontrol mailing list but whatever
[16:26] <hggdh> bdmurray: I think it is because we are the ones to set it INVALID
[16:27] <thekorn> ok, so the proposal is: marking them all (by tagging and modifieing the title) but closing most of them
[16:27] <bdmurray> right unless there is a well known call for testing
[16:28] <thekorn> only letting the one open which are part of a public announced testing iniative of a big ubuntu team
[16:28] <hggdh> and then the owners can search for their packages. The only issue is it is not easy to search for INVALID (must go to advanced/extended/whatever)
[16:29] <bdmurray> but its still possible
[16:29] <thekorn> damn, yeah
[16:29] <bdmurray> and maybe we could make a launchpadlib script to make it easier for them
[16:29] <hggdh> good idea
[16:30] <thekorn> show-me-all-my-valid-but-invalid-bugs-because-I-used-a-PPA.py
[16:30] <hggdh> perhaps a slightly smaller name ;-)
[16:30] <hggdh> :-)
[16:31] <thekorn> ;)
[16:31] <bdmurray> show-me-all-my-valid-but-invalid-bugs-because-I-used-a-PPA-and-launchpad-doesn't-have-ppa-bug-filing.py
[16:31] <pedro_> lol
[16:31] <thekorn> yeah, exactly
[16:31] <hggdh> THAT'S better. Go for broke
[16:31] <bdmurray> tab completion!
[16:32] <hggdh> so we would need to (1) update the wiki (2) get the .py, (3) publish
[16:32] <bdmurray> and announce the policy
[16:32] <hggdh> getting the py is not a critical path, though, just makes life easier
[16:33] <hggdh> so, 4 actions, the announcement being the last. Volunteers?
[16:33] <bdmurray> and maybe make a standard response that modifies ppa reports appropriately
[16:33] <hggdh> 5 actions
[16:33] <bdmurray> and... ;-)
[16:34] <hggdh> you mentees, this is a point where you can get your hands dirty ;-)
[16:34] <bdmurray> I'll do 4 and 5
[16:34] <thekorn> hey micahg
[16:35] <thekorn> I can do (2) over the next weekend
[16:35] <hggdh> morning micahg
[16:35] <nigel_nb> anyone asked for volunteer mentees?
[16:35] <hggdh> thanks, thekorn
[16:35] <micahg> hi thekorn hggdh
[16:35]  * hggdh has
[16:35] <nigel_nb> I volunteer though u'll have to tell me what about
[16:35] <hggdh> nigel_nb: we will help
[16:35] <nigel_nb> hggdh: I'm in
[16:35] <hggdh> cool
[16:36] <hggdh> bdmurray: where would we publish it? lp-improvements?
[16:36] <bdmurray> hggdh: item 2 should likely be put in ubuntu-qa-tools and pointed to from the wiki and announcement
[16:37] <bcurtiswx_> announcement of????
[16:37] <hggdh> ok, makes sense. We can assume it will be there
[16:37] <hggdh> abd prepare the wiki accordingly
[16:37] <bdmurray> announcement of the policy regarding ppa bug reports
[16:37] <thekorn> hmm, we cannot address (2) aka the script yet, easiliy and with good performance
[16:37] <bcurtiswx_> ah, for now we've been invalidating them
[16:37] <hggdh> thekorn: what gives?
[16:38] <thekorn> the API has no way to search for tasks of a user
[16:38] <thekorn> means:  launchpad.people ["thekorn"].searchTasks()
[16:38] <thekorn> is not working
[16:38] <bdmurray> we can hash this out later but I'd imagined it would search for package bugs tagged ppa
[16:39] <thekorn> haha, ok
[16:39] <thekorn> yeah, that's easy
[16:39] <hggdh> and with a given pacakge
[16:39] <bdmurray> okay, so micahg is here!
[16:39] <thekorn> this smells a bit like bughelper ;)
[16:39] <micahg> sorry I was late
[16:40] <micahg> did you get through all the items on the agenda already?
[16:40] <hggdh> thekorn: it does indeed...
[16:40] <bdmurray> micahg: no problem since we only have 20 minutes are any of your items more pressing?
[16:40] <bdmurray> micahg: we covered wiki page editing policy and bugs for daily ppas
[16:40] <micahg> what was the decision for PPAs if I may ask
[16:41] <hggdh> we will be following https://lists.launchpad.net/ubuntu-bugcontrol/msg00496.html for now
[16:41] <micahg> ok, that sounds good
[16:42] <micahg> can we make a list of packages that PPA bugs are allowed for?
[16:42] <micahg> on the wiki
[16:42] <hggdh> and we will change the wiki to reflect that, a .py will be written to facilitate the search, published on the qa-tools, and an announcement made
[16:43] <hggdh> micahg: I would expect this will be part of the wiki changes
[16:43] <bdmurray> micahg: that makes sense
[16:43] <micahg> ok, yeah, perfecrt
[16:43] <hggdh> as long as there are few such cases
[16:43] <thekorn> but this is not a static list, right?
[16:43] <hggdh> I do not see it as static. Probably a subpage
[16:44] <thekorn> so there can be short "official" testing periods for some packages
[16:44] <hggdh> +1
[16:46] <hggdh> micahg: what did you mean with "how to connect upstream bugs in LP"?
[16:46] <micahg> well, I was wondering about bugs that their upstream uses LP for bug tracking
[16:47] <hggdh> ah, good one
[16:48] <hggdh> bdmurray: how do we deal with upstream-at-LP? Do we still open an Ubuntu bug and an Upstream one? Does it even make sense?
[16:48] <thekorn> I don't get it, maybe I'm too slow, as usual ;)
[16:48] <bdmurray> hggdh: it depends on the upstream.  for ubiquity and update-manager no
[16:49] <bdmurray> hggdh: for terminator or something used by another distribution yes
[16:49] <andresmujica> hmm, i believe that usually the upstream has a project inside LP, so is a matter to add a task for the project and for the ubuntu package
[16:49] <bdmurray> andresmujica: yes
[16:49] <hggdh> so ubiquity bugs should be open against which?
[16:49] <hggdh> (for example)
[16:49] <bdmurray> hggdh: only the Ubuntu package not the project
[16:50] <hggdh> do we have a list of these packages? It would help, I think
[16:50] <andresmujica> bug 422101
[16:50] <ubot4> Launchpad bug 422101 in ubiquity "initramfs-tools package seems to fail postinstall on armel" [Undecided,Fix released] https://launchpad.net/bugs/422101
[16:50] <bdmurray> speaking of an awesome thing to do would be to review https://bugs.edge.launchpad.net/update-manager and open ubuntu tasks
[16:50] <andresmujica> this could be an example
[16:50] <micahg> so we open an upstream task vs bug?
[16:51] <mvo> bdmurray: great idea!
[16:51] <bdmurray> mvo: and maybe disable bug filing when finished?
[16:51] <thekorn> argh, this "hot bugs" overview sucks, I thought for one seconds update-manager only has 10 open bugs ;)
[16:53] <bdmurray> so generally speaking there should be a bug opened against the upstream project unless they are Ubuntu only packages like ubiquity and update-manager
[16:53] <bdmurray> There is no list of those packages that I know of
[16:54] <thekorn> what is the reason for this exception?
[16:55] <bdmurray> the package doesn't exist anywhere else and its just extra work to close the upstream task
[16:55] <thekorn> it complicates everything, and I personally don't see the positive outcome
[16:55] <bdmurray> I believe that ideally the project wouldn't allow bug filing / use lp for bug tracking
[16:56] <micahg> bdmurray: that can be set by the project owner
[16:56] <thekorn> no ideally launchpad would also close "upstream" tasks when sth. like (LP: #123456) is found in changelogs
[16:57] <micahg> thekorn: that doesn't make sense as we might have a patch that upstream doesn't
[16:58] <thekorn> hmm, good point
[16:59] <micahg> bdmurray: if those project are set for no bug tracking, a note should be on the project homepage to use the ubuntu package for bug tracking
[16:59] <micahg> also, what if another distro wants to adopt one of those packages as well
[16:59] <bdmurray> micahg: well, to use 'ubuntu-bug packagename' ;-)
[17:00] <bdmurray> micahg: well, then bug filing would be allowed again
[17:00] <micahg> bdmurray: ok
[17:01] <micahg> as we're out of time, I just wanted to make a quick note the single apport crash reports is fixed in -proposed
[17:01] <micahg> for karmic
[17:01] <thekorn> I think any policy makes sense here, as long as this policy is explained and announced somewhere
[17:01] <bdmurray> micahg: hggdh told us - that's outstanding!
[17:02] <micahg> I'm assuming it's ok to ask people to enable -proposed for the moment to generate the crash report
[17:02] <hggdh> micahg: the only thing is -proposed *may* be dangerous generically
[17:03] <hggdh> probably not, though, one hopes
[17:03] <bdmurray> well, it shouldn't be but yes ;-)
[17:03] <micahg> so we should wait until it reaches -updates before asking then?
[17:03] <bdmurray> I'm sure we can get the sru verification fast tracked
[17:03] <hggdh> we can fast-track it, yes
[17:03] <micahg> ok
[17:03] <hggdh> micahg: what was the bug #?
[17:04] <micahg> bug 476513
[17:04] <ubot4> Launchpad bug 476513 in apport "/etc/default/apport comment outdated" [Low,Fix committed] https://launchpad.net/bugs/476513
[17:04] <hggdh> thanks
[17:07] <bdmurray> Thanks everyone!
[17:08] <hggdh> am I still here?
[17:08] <micahg> hggdh: yep
[17:09]  * micahg goes to read the beginning of the meeting
[17:09] <hggdh> oh, OK. bloody wifi is slow as molasses (but then what could I expect from wardriving?)
[17:09] <thekorn> alos freenode is on fire today ;)
[17:10] <thekorn> ok, thanks everybody
[17:10] <thekorn> I'll write down some mmeting notes later today, ok?
[17:10] <hggdh> since this early morning (about 0900 UTC)
[17:10] <hggdh> thekorn: thank you
[17:11] <micahg> ah, all caught up
[17:15] <hggdh> yeee another netsplit
[17:24] <mvo> bdmurray: (sorry for the delay) - yes, disabling upstream tasks of u-m is a great idea
[17:24] <bdmurray> mvo: no problem, thanks for getting back to me
[17:40] <nperry> bug #493384
[17:40] <ubot4> Launchpad bug 493384 in nvidia-graphics-drivers-173 "xorg crashes at start with nvidia drivers. Karmic Koala. Nvidia Drivers." [Undecided,Invalid] https://launchpad.net/bugs/493384
[17:40] <nigel_nb_> hggdh: meeting is over?
[17:40] <nperry> Whats the best next step
[17:41] <nigel_nb_> I think i missed the ending due to netsplits
[17:41] <hggdh> nigel_nb_: yes, it is over. freenode is having a lot of netsplits, it seems
[17:43] <nigel_nb_> hggdh: aw, too bad, anyway what did I volunteer for?
[17:43] <nigel_nb_> I got split after that
[17:43] <hggdh> nigel_nb_: heh. You volunteered to update the wiki pages abou how we will deal (at least for now) with PPA bugs
[17:44] <hggdh> nigel_nb_: and thank you, BTW
[17:44] <nigel_nb_> hggdh: okay, that connects with the link the lists.launchpad mailing list, correct?
[17:45] <hggdh> yes -- partially. We need to state that all PPA bugs (except for a list of them) will (1) be tagged PPA; (2) have the title prepended with [PPA]; set to INVALID
[17:46] <nigel_nb_> hggdh: why are we setting to invalid?
[17:46] <nigel_nb_> so what the author can deal with it?
[17:46] <hggdh> because they are not real Ubuntu bugs -- an Ubuntu bug is a bug in an official Ubuntu package
[17:47] <hggdh> at the same time, we cannot leave then off, given all the push to PPA usage
[17:47] <hggdh> but LP still does not support PPA bugs
[17:47] <nigel_nb_> so we mark them invalid, but tag them and prepend PPA so that the authors can look for it or a script can be generated for them, correct?
[17:49] <hggdh> development will provide us with a list of PPA packages that are to be accepted (packages in transition/turmoil, like -- say -- X video drivers). We expect this list to be dynamic
[17:49] <nigel_nb_> okay :)
[17:49] <nigel_nb_> so where should I update?
[17:50] <hggdh> what you can do, if you want: look at the wiki bugsquad/bugs pages, and find where this could be put; suggest a change, and -- so that you will not feel roasting alone -- show us the changes
[17:50] <hggdh> and we will discuss, change, propose, accept in group
[17:51] <nigel_nb_> suggest a change on the mailing list?
[17:51] <hggdh> you can, if you wish. Or propose here, if no response, then ML
[17:52] <hggdh> here, via pastebin, for example
[17:52] <hggdh> or a temp page showing the changes
[17:52] <nigel_nb_> I'll do it on my sandbox
[17:53] <Wazzzaaa> Hey, I have a bug in Karmic
[17:53] <Wazzzaaa> bug #460654
[17:53] <ubot4> Launchpad bug 460654 in linux "speakers don't mute when plugging in a headphone" [Undecided,New] https://launchpad.net/bugs/460654
[17:53] <hggdh> thank you. If in doubt, ask. We will be more than happy to help. And we are very happy you volunteered :-)
[17:53] <Wazzzaaa> I'm willing to do some research in finding the cause of this bug.. But I do not know where to start
[17:55] <hggdh> Wazzzaaa: I am sorry, I personally do not do sound, but perhaps somebody else here does
[17:55] <Wazzzaaa> ok :)
[17:56] <Wazzzaaa> Im a programmer, and Im even willing to fix this bug if I can find it. Do you have pointer to sites which I can read ?
[17:56] <nigel_nb_> Wazzzaaa: it is a known issue
[17:56] <Wazzzaaa> ok
[17:56] <Wazzzaaa> so....?
[17:56] <nigel_nb_> I believe the audio team will get back to you on that one
[17:57] <Wazzzaaa> hehe, I hope it is fixed in lucid
[17:57] <nigel_nb_> I think it will be fixed in the next kernel relesae
[17:58] <Wazzzaaa> ok, is it a kernel issue?
[17:58] <nigel_nb_> no, its a alsa issue
[17:58] <nigel_nb_> what make is your laptop?
[18:10] <Wazzzaaa> make?   it is a desktop...
[18:17] <nigel_nb_> Wazzzaaa: daniel knows the details, dont worry he'll look into it when he gets time
[18:17] <nigel_nb_> he's kinda over worked, so dont worry if it takes time
[18:18] <Wazzzaaa> ok, I'll idle here...
[18:18] <Wazzzaaa> thnx voor the help
[18:19] <BUGabundo> boas
[18:41]  * BUGabundo is back
[22:04] <maco> umm im confused. what does openafs have to do with bug 453365 ?
[22:04] <ubot4> Launchpad bug 453365 in dkms "dkms should start before gdm if needed for video driver" [Undecided,In progress] https://launchpad.net/bugs/453365
[22:07] <micahg> maco: https://bugs.edge.launchpad.net/ubuntu/+source/dkms/+bug/453365/comments/9
[22:07] <ubot4> Launchpad bug 453365 in dkms "dkms should start before gdm if needed for video driver" [Undecided,In progress]
[22:08] <maco> micahg: oh. ok. i should click through instead of just going by bugmail i guess...
[22:08] <maco> i was just going "openafs... video... what?"
[22:08] <maco> micahg: thanks. and sorry
[22:08] <micahg> yep :), each task says who opened it, so you can look for their comment