=== BUGabundo is now known as BUGabundo_TBBT
[02:57] <nigelb> micahg: poke
[02:58] <micahg> nigelb: ow ;)
[02:58] <nigelb> micahg: hehe, for the removed from distro bugs, I'm thinking of a page where we can show package name, where it was removed from and the list of bugs in that package
[02:59] <nigelb> *removed from distro discusssion
[02:59] <micahg> nigelb: I think a link to bugs is better than a list
[02:59] <nigelb> that works too
[03:00] <nigelb> the idea is to have a single place to refer to
[03:00] <nigelb> I'll take a poke on it over the weekend, perhaps I should have an early alpha by monday
[03:02] <micahg> nigelb: good idea, one place to find work to do :)
[03:02] <nigelb> hehe :)
[03:03] <micahg> nigelb: in a similar vein, I just made a post to the bugsquad list regarding the bug day and a lot of bugs we can clear out
=== nixternal_ is now known as nixternal
[03:36] <nigelb> micahg: um, you posted to bug control by mistake I guess instead of bug squad
[03:36] <micahg> nigelb: I posted to both I thought
[03:37] <nigelb> ah, cc :)
[04:30] <stenten> ...does adding a duplicate to a bug really not add an additional "This bug affects me too"?
[04:31] <micahg> stenten: what do you mean?
[04:31] <ddecator> i don't believe it does
[04:32] <stenten> micahg: the "This bug affects 1 person. Does this bug affect you?" part.
[04:32] <stenten> right below the title.
[04:32] <micahg> stenten: bug 343110
[04:32] <ubot2> Launchpad bug 343110 in malone "UI: When the bug that affects you is a duplicate the master doesn't affect you (affects: 14) (dups: 5) (heat: 90)" [Low,Triaged] https://launchpad.net/bugs/343110
[04:33] <stenten> micahg: thanks.
[07:16] <zus> good evening everyone
[08:53] <BUGabundo_remote> humm...the smell of metal breakdown!does tap water fix that? /o\
[09:50] <arand> Could someone please change back Bug #553745  to "triaged" (someone random set it to comitted, erroneously if I've understood things correctly).
[09:50] <ubot2> Launchpad bug 553745 in plymouth (Ubuntu Lucid) (and 2 other projects) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() (affects: 340) (dups: 59) (heat: 1862)" [High,Triaged] https://launchpad.net/bugs/553745
=== schmidtm_ is now known as schmidtm
=== radoe_ is now known as radoe
[10:33] <BUGabundo_remote> t
[11:48] <joumetal> Is https://bugzilla.gnome.org/show_bug.cgi?id=376925 correct upstream report for bug #563415 ?
[11:48] <ubot2> Launchpad bug 563415 in epiphany-browser (Ubuntu) "Cacert.org Certificate Creation broken (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/563415
[11:48] <ubot2> Gnome bug 376925 in Backend:Mozilla "cacert.org root certificate inclusion" [Enhancement,Unconfirmed]
[12:22] <xelister> hi, is this a bug in iptables? or what
[12:22] <xelister> $ iptables -A scan_chk -j REJECT --reject-with host-unreach -m random --average 10
[12:23] <xelister> iptables v1.4.4: Couldn't load match `random':/lib/xtables/libipt_random.so: cannot open shared object file: No such file or directory
[12:23] <xelister> in IP tables packaging.
[12:24] <xelister> ah
[12:25] <xelister> it should be:     -m statistic --mode random --probability 0.1    I think such example would be nice to put in manpage, since a lot of googled examples are in old format (confusing)https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/116257
[12:25] <ubot2> Launchpad bug 116257 in iptables (Ubuntu) "Any chance for iptables random module? (dups: 1) (heat: 10)" [Undecided,Fix released]
[13:03] <arand> Could someone please change back Bug #553745  to "triaged" (someone random set it to comitted, erroneously if I've understood things correctly).
[13:03] <ubot2> Launchpad bug 553745 in plymouth (Ubuntu Lucid) (and 2 other projects) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() (affects: 340) (dups: 59) (heat: 1862)" [High,Triaged] https://launchpad.net/bugs/553745
[13:54] <ddecator> good morning
[13:55] <kermiac> hey ddecator :)
[13:55] <ddecator> hey mate
[13:55] <ddecator> hggdh: ping
[13:59] <hggdh> ddecator: good morning
[13:59] <ddecator> hggdh: good morning to you as well
[14:00] <hggdh> oh. kermiac is also around...
[14:00] <kermiac> hi hggdh
[14:00] <ddecator> yup
[14:00] <hggdh> ok. let me grab a coffee. 1 Min
[14:00] <kermiac> ok, sounds like a good plan :)
[14:01] <ddecator> yah, i'm gonna have to make some soon..
[14:02] <BUGabundo_remote> hey ddecator, kermiac, hggdh
[14:02] <ddecator> morning BUGabundo_remote
[14:02] <BUGabundo_remote> after lunch, actually
[14:02] <ddecator> morning here :)
[14:03] <hggdh> morning, BUGabundo_remote
[14:03] <hggdh> OK
[14:03] <kermiac> hey BUGabundo_remote :)
[14:03] <hggdh> kermiac, ddecator: here's the tale
[14:03] <hggdh> some time ago, I think during the Feisty cycle, I started writing an apport hook for evolution
[14:04] <hggdh> simple thing, no major deal. Except I wanted to clean up the GDB traces
[14:04] <hggdh> and *there* I had some issues
[14:05] <hggdh> opened a bug on them, etc, etc, piti stated he would look at it in the future, etc, etc
[14:05] <hggdh> but time passeth
[14:06] <hggdh> and the bloody apport hook not only is not complete, but we still have stacktraces with private dta
[14:06] <hggdh> so
[14:06] <hggdh> given you are full of {energy, ideas, ideals, whatever}, and given that I am old and tired...
[14:07] <hggdh> what about doing apport utilities for cleaning stacktraces?
[14:07] <hggdh> kermiac, ddecator, this is the point where you both say YES!
[14:07]  * hggdh awaits
[14:07] <ddecator> yes!
[14:08] <hggdh> hum. lower-case yes ;-)
[14:08] <kermiac> haha... yes too
[14:08] <ddecator> hggdh: mr. picky :p
[14:08] <hggdh> hum. huuummm. Not even exclamation point at the end
[14:08] <hggdh> THANK YOU BOTH
[14:08] <kermiac> I'm just thinking of how to do it :)
[14:09] <hggdh> I approached it in the wrong way when I started -- I made the *Evo* hook do the cleanup
[14:09] <ddecator> so you want a general hook then?
[14:10] <hggdh> yes, it should be an integral part of the apport utilities -- when apport starts, it should load the correct hook, so far so good
[14:11] <hggdh> but when it *generates* a GDB BT, if should call a sanitiser utility, *as long as* the hook initialised it
[14:11] <ddecator> ok..
[14:11] <hggdh> My Evo hook is using REs to do the cleanup
[14:12] <hggdh> and I will put it in a bzr under ~hggdh2/+junk/evo-hook
[14:12] <ddecator> danke
[14:12] <kermiac> ok
[14:12] <hggdh> bitte
[14:13] <hggdh> notice that for such a cleaner to work, the hook *must* give it variable names to look for, and etc, etc
[14:13] <hggdh> for evo I poured thru some 300 BTs looking for them
[14:13] <ddecator> the cleaning part shouldn't be too hard if private data tends to show up in certain ways (password:_____, etc), getting it to start at the right time will be tricky, at least for me haha, bug we can look into it :)
[14:13] <ddecator> s/bug/but
[14:14] <hggdh> ddecator: this is the bauty of regular expressions
[14:14] <hggdh> (RE)
[14:14] <hggdh> dammit
[14:14] <hggdh> s/bauty/beauty/
[14:14] <ddecator> ah, that's what RE stood for..
[14:14] <hggdh> yes, very sorry
[14:14] <ddecator> haha, no prob
[14:14] <ddecator> hggdh: so is there a time frame for this, or "before maverick"?
[14:15] <hggdh> hum. Not really, but the sooner the better
[14:15] <kermiac> hggdh: does the hook you started have a list of some of these RE's? Just to avoid us doubling up where you have already started
[14:15] <hggdh> (it has been in the back-oven since feisty, can wait a bit longer ;-)
[14:16] <kermiac> then we can look for others
[14:16] <ddecator> right. i won't have too much time to work on stuff for the next two weeks because of finals, but i'll definitely try to work on it and will have more time after school is done
[14:16] <zus> good a of m everyone
[14:16] <hggdh> kermiac: yes, my evo hook has the REs, and it is cleaning up IP addresses, FQDN, and variables
[14:16] <ddecator> morning zus
[14:16] <kermiac> ddecator: that's good timing for me too as I need to finish this indicator-applet hook first
[14:16] <ddecator> kermiac: good deal :)
[14:16] <zus> ddecator,  :)
[14:16] <hggdh> morn zus
[14:17] <kermiac> hey zus - sorry, I couldn't help it ;)
[14:17] <ddecator> that will give us a chance to look into it a bit and then start working on it in a couple of weeks
[14:17] <kermiac> yup, sounds like a good plan dray :)
[14:17] <hggdh> marvelous. Excellent. Fantastic
[14:17]  * hggdh runs out of praise, not used to
[14:17] <kermiac> haha.. don't thank us yet hggdh ;)
[14:18] <hggdh> oh. Yes, sorry. Rather wait and see ;-)
[14:18] <zus> kermiac,  yeah its a play on my name...funny thing is i got an award with hey zeus written as my name when i was in grade school
[14:19] <zus> so i am excited to be officially on the bug squad. - just have a few things to sort out here on my machine and i should be ready to go...
[14:19] <ddecator> zus: good to hear :)
[14:20] <kermiac> ok hggdh, can you pls ping us when you've uploaded the evo hook so we can look over what you've already done?
[14:20] <kermiac> obviously there's no rush as we probably wont be able to start it for a cpl of weeks
[14:20] <ddecator> yes please
[14:22] <ddecator> i think i'll review this -control app this morning..
[14:23] <hggdh> ddecator, kermiac: yes, I will do. I will also email both of you with an attachment -- a CSV file with all Evo bugs -- so that you can play and test
[14:23] <ddecator> hggdh: perfect, thanks :)
[14:23] <kermiac> thanks hggdh :)
[14:27] <kermiac> hggdh: just to clariify - do you want this hook to only clear private data from evolution-related BT's?
[14:28] <ddecator> i'm guessing all stacktraces?
[14:29] <hggdh> kermiac: no, I would rather have a generic apport utility (function|class)
[14:29] <hggdh> ddecator: yes indeed
[14:29] <kermiac> ok, evolution was just an example. thanks :)
[14:29] <ddecator> if we can pull this off, it will make triaging crashes a lot easier :)
[14:29] <hggdh> kermiac: it all started with Evo
[14:30] <hggdh> another point: apport bugs with sanitised stacktraces could be born public (instead of private)
[14:31] <arand> Could someone please change back Bug #553745  to "triaged" (someone random set it to comitted, erroneously if I've understood things correctly).
[14:31] <ubot2> Launchpad bug 553745 in plymouth (Ubuntu Lucid) (and 2 other projects) "plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() (affects: 340) (dups: 59) (heat: 1862)" [High,Triaged] https://launchpad.net/bugs/553745
[14:32] <kermiac> ok, so basically it *should* mostly be about finding out what RE's we need to sanitise
[14:32] <ddecator> hggdh: except when it's a crash with a coredump i'm assuming
[14:35] <ddecator> arand: it was a dev that set it to fix committed and the branch is linked
[14:46] <hggdh> ddecator: an apport bug still with a coredump mean either apport-retracer has not gotten to it, or that
[14:46] <hggdh> apport-retracing failed
[14:46] <arand> ddecator: No, the branch and earlier fix commited was done by a dev, but it was set back to triaged by a dev since that fix didn't work this was also when the lp branch was added, back in mid-april, the current suggested plymouth patch is nowhere comitted (apart from in my PPA), and it should probably neither, taking the last commets by Gilles regarding it.
[14:46] <ddecator> hggdh: right, i just mean that it shouldn't be public right away
[14:48] <ddecator> arand: ah, you're right. i'll set it back
[14:53] <arand> ddecator: cheers
[15:10] <hggdh> kermiac, ddecator: branch created, bzr pull lp:~hggdh2/+junk/apport-bt-sanitiser
[15:10] <ddecator> hggdh: great, thanks!
=== jdstrand_ is now known as jdstrand
[15:26] <slicer> Hi. Is there a way to mark bugs so that they'll automatically transition from "Fix Committed" to "Fix Released" once version x.y.z of a package is uploaded?
[15:27] <ddecator> if the bug is mentioned in the changelog, yes
[15:28] <arand> slicer: stick "LP: #nnnnnn" somewhere in the changelog.
[15:28] <slicer> Yes.. This is mumble, which is imported from Debian, and they're not really all that keen on mentioning LP bug # in the Debian changelog for some reason.
[15:29] <slicer> I also plan to fix this in the upstream so I don't really know if it belongs in the changelog. I certainly wouldn't put the change in there if it didn't match a bug/feature request posted on launchpad :)
[15:29] <ddecator> is there a separate changelog for the branch that imports it?
[15:29] <slicer> ddecator: Not that I know of, it's a straight import.
[15:32] <slicer> Guess I'll need to go back and update it manually once it is sync'd.
[15:39] <xoen> hi all
[15:43] <ddecator> hi xoen
[15:48] <atrus> the ubuntu help center's "free support" link in yelp links to http://www.ubuntu.com/support/free, which apparantly doesn't exist. any idea what that should be filed against?
[15:50] <greg-g> atrus: https://bugs.edge.launchpad.net/ubuntu-website
[15:50] <greg-g> atrus: there are a ton of broken links now that the website was redesigned.
[15:50] <atrus> this one is straight off of system:help and support on the panel
[15:50] <greg-g> apparently redirects or care for stable URLs wasn't taken into account :/
[15:50] <atrus> in lucid no less. :/
[15:51] <greg-g> yeah, epiphany's start page has broken links as well
[16:06] <xelister> HELP
[16:07] <xelister> nopomuku still forces me to do sepuku :/
[16:07] <xelister> why each time I start a kde application I have to see some **** about nepomuk? I really dont care I just want to use my kmail god damnit ;)
[16:08] <dholbach> mdeslaur will give a Packaging Training session about "Preparing Security Updates" in #ubuntu-classroom at 18:00 UTC
[16:16] <nigelb> pedro_: can you renew my bug control membership please?
[16:16] <pedro_> nigelb, yeap one sec
[16:20] <xoen> hi, I have a problem with mysql-server. Service doesn't start anymore. I've removed it and /etc/mysql/ /etc/init.d/mysql and /var/lib/mysql/ and now reinstalled it but I get this error: http://pastebin.com/AMfwY34c
[16:23] <pedro_> nigelb, renewed
[16:24] <nigelb> pedro_: thanks :)
[16:24] <pedro_> np ;-)
=== marcel is now known as marcela
[16:56] <dyllan> Any help needed?
[16:56] <jpds> All the time.
[16:56] <dyllan> Got basic python skills and good linux background.
[16:57] <jpds> dyllan: I suggest reading: http://wiki.ubuntu.com/HelpingWithBugs
[16:57] <jpds> And feel free to ask questions in here.
[16:58] <dyllan> Ok.
[17:36] <zorton> i'm having a terrible time finding out if the issue closed by bug #554010 is going tob e pushed down to lucid
[17:36] <ubot2> Launchpad bug 554010 in kopete (Ubuntu) "Unable to connect to GTalk on port 443 (affects: 1) (heat: 6)" [Undecided,Invalid] https://launchpad.net/bugs/554010
[17:40] <zorton> sounds like that's the debian bug number
[17:42] <hggdh> zorton: are you sure this is the correct bug #?
[17:42] <zorton> turns out it was the debian bug number
[17:42] <zorton> pretty bad break though, kill pam_tally2 on lucid
[17:42] <zorton> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554010
[17:42] <ubot2> Debian bug 554010 in libpam-modules "libpam-modules: pam_tally2 binary not declared to be installed" [Important,Fixed]
[17:42] <hggdh> debian 554010
[17:44] <hggdh> zorton: is there an Ubuntu bug about it?
[17:44] <zorton> i'm new to the bug system so not sure
[17:44] <zorton> found: https://launchpad.net/ubuntu/+source/pam/1.1.1-3ubuntu1/
[17:46] <hggdh> zorton: search for it (it should be under pam: https://bugs.edge.launchpad.net/ubuntu/+source/pam); if there is none, open one, and refer to the debian bug there
[17:46] <zorton> k, just found that page
[17:46] <hggdh> heh
[17:47] <hggdh> zorton: OK, this is the Maverick (ubuntu+1) package. If you need it on Lucid, you will have to request a SRU
[17:48] <hggdh> (if it is there)
[17:48] <zorton> SRU?
[17:49] <vish> !sru | zorton
[17:49] <ubot2> zorton: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[17:49] <zorton> thank you
[17:49] <vish> np.
[17:51] <zorton> someone already has apparently, so that's cool but it's been sitting there for 14 days
[17:52] <hggdh> zorton: what is the bug #?
[17:53] <zorton> well teh bug that got it into SRU is #579826
[17:53] <hggdh> zorton: and, unfortunately, it can sit there for much longer...
[17:53] <hggdh> bug #579826
[17:53] <ubot2> Launchpad bug 579826 in pam (Ubuntu Maverick) (and 2 other projects) "pam-auth-update loses user-specified module options if the module name has a digit in it (pam_krb5) (affects: 2) (heat: 16)" [Medium,Fix released] https://launchpad.net/bugs/579826
[17:54] <skybon> hi all
[17:54] <zorton> file another SRU request to get it moving?
[17:54] <hggdh> zorton: I do not follow you -- the bug *has* been worked on, and a fix is in lucid-proposed
[17:55] <hggdh> where it will stay until someone affected by it installs the proposed fix, and confirms in the bug it does indeed fix the issue, and does not create new problems
[17:55] <zorton> fix is for an issue not related to the missing pam_tally module though
=== jjesse_ is now known as jjesse
[17:57] <hggdh> zorton: so there is no SRU request for your issue...
[17:57] <zorton> yeah I would say so
[17:57] <Pici> It looks like that bug is for a different issue.. right?
[17:58] <zorton> Pici: yeah
[17:58] <hggdh> indeed
[17:58] <hggdh> and the version is *not* the fixed one, anyways
[17:58] <hggdh> zorton: please open a bug for it, and ask for cherry-picking this issue
[17:59] <zorton> let me get started
=== deryck is now known as deryck[lunch]
[18:21] <zorton> is there a special way to request cherry picking or just throw it in the report using the magic incantation "cherry-picking requested"
[18:23] <hggdh> zorton: it could be someting like "please fix debian xxxx on 10.04 LTS" and then explain why it is important to do so
[18:23] <zorton> k, just wanted to make sure I didn't need to put a tag or something in
[18:25] <hggdh> zorton: did it work on Karmic?
[18:26] <zorton> only just switched over to Ubuntu for lucid
[18:27] <zorton> switched from debian stable mainly for these type of issues, 5.0 dosen't have pam_tally2 and pam_tally acts like it works but dosen't enforce
[18:31] <hggdh> ok. Then just open the bug, no tags needed
[18:31] <balachmar> The installer of 10.04 says it has encountered an unrecoverable error and that a desktop session will be started, so that I can investigate it. What should I do?
[18:32] <hggdh> balachmar: I guess investigate... collect data, and then open a bug on it
[18:33] <balachmar> ok, but I asked here, because I have no clue where to start investigating :)
[18:43] <balachmar> hggdh: well one thing I find is a buffer I/O error on sr0 in the kern.log. Is that the dvd drive?
[18:45] <hggdh> balachmar: yes, probably it is the CD/DVD
[18:46] <balachmar> hggdh: but I did let it do a selfcheck already...
=== deryck[lunch] is now known as deryck
[20:33] <optix> I believe bug #586499 should be updated to wishlist.
[20:33] <ubot2> Launchpad bug 586499 in evolution (Ubuntu) "Making a search in evolution keep search keywords even after reboot (affects: 1)" [Undecided,New] https://launchpad.net/bugs/586499
[20:34] <xteejx> Hey guys. After speaking to a few people in #ubuntu it seems that the disappearing nm-applet in the top panel has returned with a vengence
[20:34] <optix> Can someone help me update it to wishlist?
[20:34] <xteejx> I haven't experienced it yet, but how can users connect with iwconfig to wifi without using the nm-applet?
[20:36] <hggdh> optix: done
[20:36] <optix> hggdh: thanks
[20:55] <teurastaja> i have a permanent graphics address remapping table bug with possible asic involvement
[20:56] <teurastaja> its very impeding
[20:56] <teurastaja> its not just annoying: its disabling
[20:58] <teurastaja> the most helpful hint i have is the kernel tries to force the gart to 32M just after chainloading
[20:59] <ChogyDan> teurastaja: I know someone suggested you to go here, but I think this room is more about launchpad bug reports.  If you want it fixed in Ubuntu, I would file a bug, and then maybe ask in #ubuntu-devel  (not that I really know)
[20:59] <teurastaja> it says [drm:rs400_gart_adjust_size] *ERROR*
[21:01] <teurastaja> well it totally prevents sidebar interaction with running programs
[21:05] <stenten> teurastaja: from what you're saying on ubuntu-devel, it sounds like you should 'ubuntu-bug linux'.
[21:09] <teurastaja> what?
[21:10] <teurastaja> am i saying anything wrong?
=== BUGabundo is now known as BUGabundo_fewd
[21:11] <stenten> no, it's just that if you file a bug, it has a chance of being seriously looked at and fixed. By just talking about it on irc, you only get whoever is looking at the screen at the time. And they have no way to track it.
[21:12] <teurastaja> ok
[21:12] <teurastaja> i hate this bug it wont go away damn it
[21:12] <stenten> it becomes more of an afterthought on irc. But if it's a bug, it's not going to go away when you close your irc client :)
[21:14] <teurastaja> :(
[21:15] <teurastaja> there are weird shiny bars appearing and disappearing on my screen
[21:18] <teurastaja> damn it things are moved back and forth on both desktops
[21:19] <teurastaja> and windows pop away forever
[21:19] <teurastaja> i cant use the menu properly only thing that seems to work is xchat
[21:20] <teurastaja> and thats because i made a shortcut on another bar before
[21:21] <teurastaja> this is by far the most serious bug i ever dreamed of and its real
[21:24] <teurastaja> could "reparamerating" the bios to fix ram usage help?
[21:25] <teurastaja> ok fuck this the whole installation is affected im reinstalling ubuntu
=== BUGabundo_fewd is now known as BUGabundo
[21:49] <tawmas> Hi! I need some help with bugs #578894 and #578909. They were marked Incomplete by an automated script, but I believe I had provided the required information...
[21:49] <ubot2> Launchpad bug 578894 in linux (Ubuntu) "Cannot detect AC adapter status and battery charge status on Acer Aspire 4820TG (affects: 3) (dups: 1) (heat: 112)" [Undecided,Incomplete] https://launchpad.net/bugs/578894
[21:49] <ubot2> Launchpad bug 578909 in linux (Ubuntu) "acer_wmi blocks wlan rfkill status to disabled on Acer Aspire 4820TG (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/578909
[21:49] <tawmas> Please, help me understand if there's anything more I can do...
[21:50] <micahg> JFo: ^^^
[22:00] <vish> tawmas: you can set it back to "new" [as indicated in the comment] the script needs some work ;)
[22:03] <tawmas> vish: thanks, I'm doing that right now
[22:06] <tawmas1> sorry, my router is flaky these days
=== andre___ is now known as andre__
[22:13] <vish> tawmas1: you might have selected the wrong option while submitting the bug , hence got tagged wrong .. [script seems to have correctly found the bug since it was was tagged needs testing]
[22:15]  * vish has occasionally found the script be a bit over-zealous
[22:15] <tawmas1> vish: I think apport just adds that tag without asking questions... ;-)
[22:16] <vish> tawmas1: nah , there *is* a question , but too many questions that you might have just clicked "next" ;)
[22:16] <tawmas1> vish: maybe
[22:17] <tawmas1> vish: I know for sure I was asked questions that made me go puzzled...
[22:18] <tawmas1> vish: is there anything I can do to have those bugs make more progress? I'm totally at loss with kernel bugs, but I might try reporting upstream if it's useful
[22:20] <vish> tawmas1: JFo is the right person , i'v just noticed the apport/script problems since i have reported a few kernel bugs ;p
[22:20] <JFo> vish, what script problems
[22:20] <JFo> they are working just like i want them to
[22:20] <JFo> :)
[22:21] <JFo> tawmas1, what bugs?
[22:21] <tawmas1> JFo: #578894 and #578909
[22:21] <vish> JFo: hehe , i have occasionally found them a bit over-zealous in marking bugs incomplete , but it might have been improved now :D
[22:22] <JFo> vish, when was that? they have undergone 4 revisions in the last 6 months?
[22:23] <vish> JFo: must have been a couple of months ago , not recent from what i recall
[22:23] <tawmas1> JFo: the comment should hint about setting the bug back to New...
[22:23] <JFo> hmmm, ok :)
[22:23] <JFo> tawmas1, that is because i don't want them set to new
[22:24] <JFo> they are by definition not new
[22:24] <tawmas1> JFo: sorry, that's what I was just told to do...
[22:25] <JFo> it's cool
[22:25] <vish> JFo: if tested upstream , one should set it to "confirmed" ?
[22:26] <JFo> yeah, I prefer that over new
[22:26] <JFo> I am writing out the new rules now, but they aren't done
[22:26] <vish> ah, cool
[22:26] <JFo> plus I am asking for some new statuses from LP
[22:27] <JFo> tawmas1, you and I have done all we can do. It is on to the subsystem reviewers now
[22:28] <tawmas1> JFo: cool...
[22:28] <JFo> :)
[22:31] <tawmas1> JFo: I can try to forward the bug upstream if it's useful... Would be my first time with the kernel, but probably I won't die in the attempt ;-)
[22:32] <JFo> heh, well, it mostly depends on whether it already exists in some form upstream
[22:32] <JFo> may be worthwhile to look
[22:32] <JFo> the guys prefer to grab things from stable branch, but they aren't against pre stable
[22:32] <tawmas1> JFo: OK, I'll wait and see then
[22:33] <JFo> cool
[22:34] <tawmas1> thank you guys, I think I'll go to bed now... ;-)
[22:49] <stenten> Man. I wish we could delete comments sometimes. So many superfluous "me too"s....
[23:04] <xelister> I just hate when computer tries to be smarter then me
[23:04] <xelister> yeah kmail I dont give ***** that this openpgp key expired, please please please just allow me to sign using it anyways...
[23:16] <xelister> does this proble seem like something that can be fixed?  is it more of a bug or wish?
[23:18] <charlie-tca> the pgp key?
[23:18] <charlie-tca> wish; probably invalid, since it is doing what it should be doing if you use a signature key
[23:36] <hggdh> agreed