[00:23] <mrooney> wgrant: it is indeed. although I have been pretty impressed with .27 so far
[00:28] <Hamra> except for hibernate working, i never notice anything in the dozens of kernels i tried in kubuntu from the days of feisty till now
[00:28] <Hamra> they're all the same for me
[01:28] <mrooney> ahh, hibernate and suspend, that's a good thing for me to try in Intrepid
[01:29] <mrooney> oh that's right, I can't use my power button for that.
[02:41] <mrooney> bryce: haha, what a patch
[02:42] <bryce> http://bryceharrington.org/ubuntu/evdev/xserver-xorg-input-evdev_2.0.99+git20080912-0ubuntu2_i386.deb
[02:42] <bryce> give it a try
[02:42] <mrooney> and that's why, you always close your files
[02:42] <bryce> ;-)
[02:42] <mrooney> I hope that doesn't take my password and send it to your email :)
[02:43] <bryce> hope you have a big limit on your credit card ;-)
[02:43] <mrooney> haha
[02:43] <mrooney> bryce: what is required for it to be in place after installing, should I restart X?
[02:43] <bryce> yep
[02:44] <e-jat> bryce, when will the 8.10-beta release? cant wait for its :) waiting some of the bugs fixed in it
[02:44] <bryce> e-jat: "are we there yet??"  ;-)
[02:45] <bryce> e-jat: no idea myself, but slangasek is probably working hard on it.
[02:45] <e-jat> thanks bryce
[02:45] <e-jat> since it already 2nd oct ... no worries .. i still can wait for it ..
[02:45] <bryce> it's still 1st oct for slangasek and I
[02:46] <bryce> you future person you
[02:47]  * wgrant destroys bryce from the future.
[02:47] <e-jat> timezone differ :">
[02:47] <bryce> :-)
[02:48] <wgrant> e-jat: Where are you?
[02:48] <e-jat> MY
[02:48]  * wgrant bashes g-p-m with a "I refuse to let you increment over 1000 times" stick.
[02:48]  * wgrant is .au.
[02:48] <wgrant> Yay, I can safely unplug AC now.
[02:49] <bryce> oops, those debs didn't have the patch attached; hang on if you're testing
[02:50] <e-jat> wgrant, :)
[02:50] <mrooney> bryce: no dice :[
[02:50] <mrooney> I gave it a full restart for good measure, still get the same thing
[02:50] <bryce> mrooney: yeah I found an error in my build.  one sec, I'll have new debs
[02:50] <mrooney> ok
[02:50] <mrooney> after restarting X, F7 was still by old one, and F8 became the new one, I had no idea it worked like that!
[02:50] <mrooney> *my old one
[02:51] <mrooney> so I got confused and restarted since at that point it seemed ambiguous which X might get what
[02:52] <bryce> I usuallyt restart via '/etc/init.d/gdm restart', to avoid any such messiness.  But logging out and back in ought to be sufficient
[02:52] <bryce> ok, new debs are posted.  Same links
[02:53] <mrooney> mm, that link doesn't exist anywhere on this system, as it turns out
[02:53] <mrooney> no IM or Firefox logging
[02:54] <mrooney> unless, did you post it on the bug?
[02:55] <mrooney> bryce: hm, I don't see it there, can you re-link?
[02:56] <bryce> http://bryceharrington.org/ubuntu/evdev/xserver-xorg-input-evdev_2.0.99+git20080912-0ubuntu2_amd64.deb
[02:56] <bryce> http://bryceharrington.org/ubuntu/evdev/xserver-xorg-input-evdev_2.0.99+git20080912-0ubuntu2_i386.deb
[02:57] <bryce> ok, got one confirmation on #xorg-devel that it's fixed with that deb
[02:57] <mrooney> let me see if I can give you another!
[03:00] <mrooney> bryce: looks perfect!
[03:00] <bryce> sweet
[03:00] <mrooney> no annoying mouse window moving behavior either
[03:01] <Hobbsee> bug 276955
[03:04] <bdmurray> bryce: works for me too
[03:08] <bryce> ok, once beta-freeze is over I'll upload
[03:09] <Hobbsee> bryce: you can upload it now - just nothing will happen to it :P
[03:10] <bryce> hm, guess that's true
[06:57] <dholbach> good morning
[07:03] <thekorn> good morning dholbach
[07:03] <dholbach> hey thekorn
[07:43] <elmargol> Any Ideas on bug
[07:43] <elmargol> bug #274357
[07:44] <RAOF> It's probably the same bug that keeps crashing my jockey-gtk, and is unlikely to have anything happen to it until after beta?
[07:45] <elmargol> I have this bug 2 weeks now :(
[07:49] <elmargol> Does this mean it works for every user except us two?
[08:05] <bs68> someone reported a bug in gnumeric, but find that it is actually a problem/feature in yelp. how should i deal with status flag for the gnumeric package??
[08:05] <bs68> https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/268845
[08:06] <bs68> the yelp status should be changed from medium to low in my oppinion, but i dont have enough rights for that.
[08:11] <yuriy> bs68: if it doesn't apply to the package, then invalid
[08:11] <bs68> yuriy: ty
[08:12] <bs68> is there any way to show a changelog/version history of a bug in launchpad (ie who changed what and when)?
[08:13] <yuriy> bs68: activity log
[08:13] <bs68> yuriy: re ty
[08:13] <yuriy> top right, next to reported by...
[09:55] <ahmadtarek> Hi All, I think bug #277027 should be changed to wishlist
[09:59] <wgrant> ahmadtarek: Done.
[09:59] <ahmadtarek> wgrant: thanks
[10:44] <ziroday> Hi, I am new to triaging and sorry If I am asking a silly question. I am looking at https://bugs.launchpad.net/ubuntu/+source/xchat/+bug/276981 which is a wishlist item. How do I notify the xchat maintainers of this?
[10:55] <bs66> ziro: intrepid also includes 2.8.4, but i dunno why.
[10:57] <ziroday> bs66: sure, but what do I mark or comment about?
[10:58] <ziroday> as I can't set the importance to wishlist
[10:58] <maco> ziroday: there isn't a specific xchat maintainer. i'll set the importance
[10:58] <ziroday> maco: thanks
[11:00] <ziroday> so I would just say something along the lines of "Thank you for filing this bug, this is a wishlist item and has been set so"?
[11:00] <maco> ziroday: sure
[11:01] <ziroday> maco: alright, and what would I set the Status?
[11:01] <maco> ziroday: also if you refresh, you can see that i set the title to start with [needs-packaging] and marked that in the tags. when you find one like this, that's what you do.
[11:01] <maco> you do those with the "update description/tags" link
[11:02] <ziroday> ah
[11:02] <ziroday> maco: I was wondering how you were correctly meant to do it
[11:02] <maco> im not sure about status for needs-packaging
[11:02] <maco> or if you see a request to add some new application
[11:02] <maco> that's also needs-packaging
[11:02] <ziroday> maco: hmm alright
[11:03] <maco> i suppose confirmed works for the status
[11:03] <ziroday> okay
[11:03] <maco> though you should probably check that the version they're asking about isn't already packaged in ubuntu
[11:03] <maco> before marking it confirmed
[11:03] <wgrant> maco, ziroday: needs-packaging is for new packages...
[11:03] <wgrant> For upgrades, there is no specific summary snippet and the tag is 'upgrade'
[11:03] <wgrant> Confirmed/Wishlist
[11:03] <maco> wgrant: oh. ok i fail.
[11:04] <wgrant> If it's already in Debian or there is a bug filed in Debian, add a Debian task and either link to the bug or mark it as Fix Released as appropriate.
[11:04] <maco> ziroday: well, the devscripts package includes one called "rmadison" and if you run "rmadison -uqa <package>" you can see what debian and ubuntu repositories have it packaged and what versions they have
[11:04] <ziroday> just checked and in intrepid its been updated to 2.8.6
[11:05] <wgrant> !info xchat intrepid
[11:05] <ziroday> according to packages.ubuntu.com
[11:05] <maco> ziroday: that's considered fix released then, i believe
[11:05] <wgrant> ziroday: https://launchpad.net/ubuntu/+source/xchat is the canonical reference.
[11:05] <wgrant> maco: Correct.
[11:05] <ziroday> okay thanks maco and wgrant, you're awesome
[11:06] <maco> wgrant: i the update tag isn't listed on the Bugs/Tags page
[11:06]  * ziroday continues to struggle along with his 5-a-day
[11:06] <wgrant> maco: upgrade
[11:06] <maco> oh it's upgrade
[11:06] <maco> heh
[11:06] <maco> an annoying distinction
[11:07] <wgrant> Those bugs shouldn't really exist.
[11:07] <maco> which?
[11:07] <maco> update requests?
[11:07] <wgrant> Yes.
[11:07] <maco> debian sometimes gets very behind so the sync doesn't help
[11:07] <wgrant> Right.
[11:08] <maco> gsynaptics was at, i think a year or 2 old version
[11:08] <maco> finally a new one is in intrepid
[11:08] <wgrant> Right, but gsynaptics needs to die.
[11:08]  * wgrant will obsolete it.
[11:08] <maco> but...crap someone needs to test it without having used synclient before
[11:08] <wgrant> Why?
[11:08] <maco> i patched in minspeed/maxspeed/accel a while back
[11:08] <maco> and i set some sane defaults
[11:09] <maco> only i didnt tell it to check the current setting and switch to that if one is set
[11:09] <maco> someone else patched it to use teh current settings for those
[11:09] <wgrant> Not much point in fixing things too much.
[11:09] <maco> only they didn't check to see what happens if there's nothing set yet.  the result is the touchpad stops working completely because if nothing's set, the the min speed, max speed, and acceleration are all 0
[11:10] <wgrant> Aha.
[11:10] <wgrant> maco: Ubuntu-specific or Debian QA-maintained packages should show up on my http://qa.ubuntuwire.com/uehs/
[11:10] <wgrant> Er, if they're out of date.
[11:12] <maco> wgrant: hm the bug is asking for an SRU. i dont think it'll get it
[11:13] <wgrant> maco: I would certainly deny it.
[11:13] <wgrant> We don't issue SRUs just because upstream feels like it.,
[11:13] <maco> wgrant: the one he linked, i mean. they say that since hardy's LTS it should be updated, but hardware support, sure...major bugs, yeah...."i like bleeding edge!" ??
[11:13] <wgrant> maco: Right. I was speaking of that bug.
[11:15] <maco> im perfectly content to just backport anything i want from intrepid. crimsun taught me to use pbuilder (as dumb as that sounds)
[11:16] <maco> i dont expect him to ever stop teasing me about "pbuilder build"
[11:16]  * wgrant just runs $DEVELOPMENT_RELEASE from a couple of weeks in.
[11:21] <maco> wgrant: i usually would from like alpha 3, but hardy's so nice
[11:22] <wgrant> Hardy is really nice, I'll give you that...
[11:22] <wgrant> It's rather close to perfect.
[11:22] <maco> yes, it is
[11:23] <maco> its as close to perfect as intrepid would be on my hardware
[11:23] <maco> probably closer given intrepid's suspend issues
[11:23] <wgrant> Hm?
[11:23] <wgrant> Ah.
[11:23] <wgrant> Works fine for me.
[11:23] <wgrant> But kernels have been pretty much flawless on my hardware since ~Feisty.
[11:23] <maco> i have two non-working pieces of hardware. intrepid doesn't have drivers or a new enough version of libusb for me to compile the drivers, so it has no advantage for me
[11:24] <maco> i hope well actually
[11:24] <maco> one driver requires a newer libusb. the other requires not-2.6.27
[11:24] <maco> i have no idea what the "i hope" line was
[11:25] <maco> i think it was "i hope jaunty will"
[11:25] <wgrant> Ah.
[11:25] <wgrant> That makes a bit more sense :P
[11:26] <maco> sometimes i hit the scroll part of the touchpad and it scrolls up to another line and combines them in irssi
[11:26] <wgrant> Same.
[11:26] <maco> k so its not just something about how i type
[11:38] <maco> ah, i was saying "i hope jaunty does" and then "well actually, one requires.."
[11:41] <wgrant> Ahh.
[11:44] <maco> wgrant: i know usability bugs are usually Low, but if it's a string that isn't translatable on the installer, does that get higher priority (like medium) or stay Low?
[11:49] <wgrant> maco: What kind of string?
[11:50] <wgrant> Probably at least Medium.
[11:50] <maco> wgrant: "install server edition" when the cd first pops up
[11:52] <wgrant> Ugly.
[11:52] <wgrant> Medium should do.
[11:53] <maco> what package is that?
[11:53] <wgrant> I suspect gfxboot.
[11:53] <maco> they put gfx-boot-theme but that sounds wrong
[11:53] <wgrant> Hmm.
[11:53] <wgrant> Might be the theme.
[11:53] <maco> ok....theme seemed wrong
[11:54] <wgrant> Bug #212491 isn't dissimilar.
[11:54] <wgrant> It's against both.
[11:54] <wgrant> Though for different reasons.
[11:55] <maco> oh i never saw those lock icons before
[11:55] <wgrant> Looks like the theme is the right place.
[11:55] <wgrant> Lock icons?
[11:55] <maco> private bug reports
[11:55] <wgrant> Ah. There are a lot of them around for crashes.
[11:55] <maco> yeah
[12:00] <maco> wgrant: does apport make crashers automatically medium?
[12:01] <maco> wgrant: bug 276990 is a reason i can't use intrepid
[12:02] <wgrant> maco: In some circumstances I think so.
[12:03] <wgrant> I'm not entirely sure.
[12:03] <wgrant> maco: You might want to attach the information RAOF requested, even though you're not the reporter.
[12:04] <maco> wgrant: i'm not using intrepid
[12:04] <maco> draft n is disabled in hardy's kernel
[12:04] <maco> and ive got a nice draft n router and everything
[12:05] <wgrant> maco: Well, we'll have a beta release in a few hours.
[12:07] <maco> ah ok, live cd
[12:08] <maco> i'm trying to figure out how to install intrepid in kvm with ubuntu-vm-builder
[12:09] <maco> i dont get the point of having u-v-b only be able to handle *old* versions. it's biggest area of usefulness is letting people like me test without changing their production system too much
[12:16] <maco> wgrant: when checking for sensitive info in a coredump, is running strings on it and going through sufficient, or is there a better way?
[12:16] <wgrant> maco: Doesn't apport normally remove the coredump?
[12:17] <wgrant> The retracer bots, that is.
[14:10] <ahmadtarek> I have a question, In bug #277021, should it be marked as invalid, Fix Released or changed to question?
[14:12] <pedro_> ahmadtarek: close it as Invalid, it wasn't a bug after all
[14:12] <askand> I reported a bug but now it has been removed..
[14:12] <pedro_> removed?
[14:13] <askand> from launchpad.. >:o
[14:14] <pedro_> what was the number?
[14:14] <askand> Hm I dont know.. it was about firefox having a bad size on the livecd
[14:14] <askand> when starting it
[14:15] <pedro_> I think i saw that, just a sec
[14:16] <ahmadtarek> pedro_: thank you
[14:16] <pedro_> askand: what's your lp id?
[14:16] <askand> pedro_:  olskar
[14:16] <pedro_> olskar?
[14:16] <pedro_> found it
[14:16] <askand> yay
[14:16] <pedro_> bug 276439
[14:17] <pedro_> askand: it was marked as a duplicate of 257947, it wasn't "removed" from lp
[14:42] <charlie-tca> Is bug 253599 valid? If it is, I'll go ahead and confirm all the themes.
[14:48] <charlie-tca> A little help, please
[14:49] <charlie-tca> bug 275328 is marked Importance - Wishlist, Declined for Intrepid, Status - New
[14:50] <charlie-tca> What is the correct status for bugs declined for the next release? Should it be confirmed or invalid?
[14:52] <cody-somerville> charlie-tca, hmm?
[15:14] <charlie-tca> I need some advice here, I just don't know
[15:14] <Hobbsee> charlie-tca: probably don't mark as invalid - it may get implemented in jaunty.
[15:15] <charlie-tca> Confirmed should be good then, right? Shouldn't have to stay at new, should it?
[15:15] <Hobbsee> for a wishlist?  no idea.
[15:15] <Hobbsee> probably safer to leave it.
[15:15] <Hobbsee> confirmed / new is pretty much the same thing for wishlists
[15:16] <charlie-tca> Yea, but I hate new... It makes me keep looking at them to see if they can be confirmed
[15:17] <charlie-tca> Thanks though. I appreciate your advice.
[15:19] <cody-somerville> we mark wishlists as confirmed, yea
[15:19] <charlie-tca> Thanks cody-somerville :)
[16:00] <bddebian> Boo
[16:01] <jjesse> dont cry i didn't mean to scare you
[16:01] <bddebian> :)
[16:18] <weboide> Hi everyone, im starting in the bugsquad team and I wanted to know what should .debdiffs for new version packages be built into? intrepid? is there now any point in building for hardy?
[16:20] <bdmurray> weboide: a debdiff for a newer package than the only currently in Hardy?
[16:20] <bdmurray> er, Intrepid
[16:20] <jdong> weboide: they should go for intrepid, unless you intend on fixing the bug for hardy that qualifies with SRU guidelines
[16:20] <jdong> (i.e. critical bugfixes)
[16:21] <weboide> that's because i'm starting with doing "update requests" bugs
[16:21] <jdong> weboide: update requests likely won't be honored at this point in the release cycle
[16:21] <jdong> I'd encourage you to look at bugs that need fixing in existing versions instead
[16:22] <weboide> so new updates won't make it into backports even?
[16:22] <jdong> weboide: yes they will make it into  backports once jaunty opens.
[16:22] <weboide> oh okay
[16:22] <jdong> backports doesn't accept packages newer than the latest Ubuntu development release due to obvious upgrade headaches :)
[16:23] <weboide> so there's no real point in doing updates, even for intrepid right now?
[16:25] <weboide> jdong: I should try fix bugs for hardy and intrepid  instead?
[16:25] <jjesse> does the bug in an odler version still exist in hardy/intrepid?
[16:26] <jdong> weboide: at this point I'd really recommend trying to fix bugs for intrepid
[16:26] <jdong> that's where we need the most help
[16:26] <weboide> jdong: alright, that's what ill do ;)
[16:26] <jdong> weboide: fixing bugs for hardy and other already-released versions requires a longer process (the Stable Release Update) that's a bit more difficult to follow
[16:26] <weboide> jdong: I see.
[16:27] <weboide> Thanks for your help jdong
[16:28] <jdong> sure thing
[18:15] <maco> did i handle this right? bug 215604 There's an out-of-tree driver for the webcam listed, rejected for Intrepid. There's also a regression in 2.6.27 that makes the out-of-tree driver not work on Intrepid. i marked it triaged for the existence of an out of tree driver
[18:21] <persia> maco: I'd call it Triaged as well, but I think it's only one bug: it's not included.
[18:21] <persia> The fact that the out-of-tree driver isn't keeping up with the Ubuntu trunk is somewhat external, and not something we can likely address or fix.
[18:22] <persia> Further, while a regression may be seen, wihout some clear understanding of exactly which bit regressed (more than just "Doesn't compile againt the new kernel", it may not be worth considering it.
[18:22] <maco> persia: that's what i meant by "very very unlikely the kernel team's going to help him"
[18:23] <maco> persia: actually if you check out Nol's comment he says teh regression...or at least links to it
[18:23] <maco> persia: not in lp, i mean. http://www.gossamer-threads.com/lists/linux/kernel/951452
[18:24] <maco> persia: there's a patch in there too
[18:24] <persia> Yeah, I'm reading that, but it appears to be for avr32 and mips.  I'm not sure how that affects Ubuntu, but I could be mistaken (and don't really understand kernel)
[18:26] <maco> persia: well it says those are examples...i dont have intrepid to try compiling it on *grumble at ubuntu-vm-builder*
[18:27] <persia> Hrm.  Yeah.  It also looks like code-cleanup stuff, rather than deep changes.  Dunno.  Bug could be kernel-side (regression) or driver-side (needs porting).
[18:29] <maco> persia: yeah it seems they did code-cleanup upstream and broke backwards compatibility
[18:30] <persia> I'm just not sure whether that should be fixed by undoing the code cleanup (kernel bug), or adjusting the driver to use the cleaned code (driver bug).
[18:30] <chrisccoulson> does anyone know who SWITALSKI ALexandre is?
[18:30] <persia> Since it's an out-of-Ubuntu driver (even more than just out-of-tree), the latter case may not be a bug.
[18:33] <Hamra> chrisccoulson: no idea, why?
[18:33] <chrisccoulson> they just removed a link to an upstream bug report that i'm assigned too, with no comment
[18:33] <chrisccoulson> bug 182345
[18:33] <chrisccoulson> its fixed upstream, but they just deleted the link a couple of minutes ago
[18:34] <chrisccoulson> i've just re-added it ahain
[18:36] <asomething> hi all! any one know where to file a bug against: http://qa.ubuntuwire.com/bugs/rcbugs/
[18:36] <maco> persia: good point
[18:37] <persia> asomething: What's the bug?
[18:38] <asomething> just a wish list item, i think it would be much easier to read if the background varied every other line
[18:38] <persia> Oh.  Hmm.  There ought be a way to report that.
[18:39] <asomething> not a real problem, but I keep almost posting comments on the wrong line...
[18:39] <persia> asomething: Why don't you report it at https://bugs.launchpad.net/ubuntuwire-website/ for now.  I'm sure there's a better place, but at least that way it doesn't get lost.
[18:39] <asomething> sounds good. thanks!
[18:40] <chrisccoulson> persia - that sounds like the correct place actually
[18:40]  * persia suspects that the code lives somewhere under some Ubuntu Quality branch, but the people who know are likely to be away now.
[18:41] <persia> chrisccoulson: No, actually I *know* that's not the correct place, because I have commit access to that project, and it doesn't include the QA tools.
[18:41] <persia> I just forget the name of the QA tools projects, and can't be bothered to look them up with more than a cursory search right now: filing it there is basically a reminder to me to go put it in the right place when I'm more awake and less busy.
[18:42] <chrisccoulson> ah, ok!
[18:42] <asomething> I'll look around a bit more first, just thought someone here might know off hand
[18:47] <persia> asomething: No, really, file it there.  I'm only 60% sure there is a better place: fixing it might be a matter of poking the maintainer on IRC.
[18:47] <persia> (something I'm happy to assign myself)
[18:47] <asomething> persia: ok, thanks again
[19:01] <bdmurray> pedro_: have you seen anything like bug 276582?
[19:27] <persia> bdmurray: That's a known issue with that chipset : it doesn't export things the way pulse expects.
[19:28] <persia> I forget the details, but something about not having a default stereo PCM registered.
[19:28] <persia> (and no, unfortunately I don't know if there is a master bug or anything)
[19:34] <pedro_> bdmurray: nope sorry
[19:43] <persia> Found it.  I think the problem is bug #178442, although that's a different expression of the issue than I've previously seen
[21:29] <bucket529> Request Bug#271900 change from New to Wishlist - it's a packaging request
[21:29] <chrisccoulson> bug 271900
[21:32] <bucket529> ﻿Request bug 208406 change from New to Wishlist - another packaging request
[21:39] <bucket529> ﻿Request bug 261768 change from New to Wishlist - another packaging request
[21:41] <chrisccoulson> bucket529 - i've altered the first bug reports description to fit the general format for new package requests
[21:41] <chrisccoulson> i've added the license information, as it was missing that
[21:46] <bucket529> Want to learn - what is the general format for new package requests? There's a bunch of them sitting in Ubuntu/New/Undecided
[21:46] <chrisccoulson> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages/ExamplePackageRequest
[21:46] <chrisccoulson> thats an example
[21:46] <chrisccoulson> this gives some more info: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages/
[21:47] <bucket529> chriscoulson: Thanks - I'll try to digest them
[21:49] <jStefan> if any webmaster is around, bug 277235
[21:57] <Hamra> jStefan: why not confirm it? that's not how anchor links are supposed to work
[21:58] <jStefan> Hamra, didn't think i could confirm my own bug
[21:58] <chrisccoulson> thats right, you shouldn't confirm;)
[21:58] <chrisccoulson> done it for you
[21:59] <jStefan> thanks
[21:59] <Hamra> ah, didn't know it's you who posted it
[22:00] <bdmurray> it's being fixed as we speak
[22:03] <jStefan> looks like fully fixed now
[22:12] <bucket529> ﻿Request bug 262044 change from New/Undecided to Wishlist - another packaging request
[22:14] <murdok> what to do when a new bug has a patch, triage?
[22:14] <seb128_> hey hggdh
[22:15] <seb128_> hggdh: onetime bugs should probably be closed if they don't have useful informations
[22:15] <hggdh> hi seb128
[22:15] <hggdh> I understand. I decided to tag it onetime to be able to keep an eye on it
[22:16] <hggdh> andre___, still, it would match: one single occurrence, nobody able to replicate, and mchra states he cannot understand how it happened
[22:16] <hggdh> s/andre __/and/
[22:16] <hggdh> bloody autocompletion
[22:17] <andre___> hmm? ah :)
[22:17] <hggdh> sorry andre___
[22:18] <hggdh> seb128_, see above; if you think this is a worng usage of onetime, I will take it out
[22:20] <murdok> anyone? :/
[22:20] <seb128_> hggdh: not the wrong usage but we have so many bugs that I would not care about tagging those, I would just close if nobody else got the issue and that was a one time bug for the submitter
[22:21] <hggdh> seb128_, OK. I have been thinking about how difficult is to find out all the possible reasons of an INVALID closure. This was an experiment (which fired off back very fast ;-)
[22:22] <seb128_> oh I don't want to stop you, I was just curious
[22:22] <seb128_> I would not spend efforts on that but tags are free to use ;-)
[22:22] <hggdh> I wanted to be able to distinguish between real invalid, notabug, notUbuntu, onetimers, etc
[22:26] <seb128_> understable
[22:26] <seb128_> I prefer to spend my effort on open bugs rather than looking at why bugs have been closed though ;-)
[22:29] <hggdh> LOL
[22:29] <hggdh> I hear you, I hear you...
[22:33] <bucket529> Trying to learn: bug 267380 is a Ubuntu/New/Undecided package request, a PPA at https://launchpad.net/~adrian5632/+archive has the very package. If I were truly wise and zen, what should I do with the bug?
[22:36] <hggdh> bucket529, you can add a comment stating the package is on this PPA; it still needs to be formally accepted/rejected
[22:36] <chrisccoulson> does anyone in here use kubuntu?
[22:37] <hggdh> chrisccoulson, every so often. I can re-login in KDE if needed
[22:37] <chrisccoulson> i was just wondering what the KDE equivalent of gnome-power-manager was?
[22:38] <hggdh> guidance-power-manager?
[22:38] <chrisccoulson> thanks. i'm slightly confused now though
[22:38] <hggdh> on what?
[22:39]  * hggdh normal status is confused
[22:39] <chrisccoulson> if someone presses the standby button on their laptop, ACPID runs the /etc/acpi/sleep.sh script, which is meant to bomb out if gnome-power-manager or kpowersave exists
[22:39] <chrisccoulson> this lets them take over the handling of the power-management policy
[22:40] <chrisccoulson> do i understand that correct? and kpowersave doesn't exist on a standard kubuntu install>?
[22:41] <bucket529> Recommend bug 267380 change from New/Undecided to Wishlist
[22:41] <Hamra> kpowersave? no it soesn't come installed by default
[22:41] <Hamra> doesn't *
[22:42] <hggdh> chrisccoulson, kpowersave was KDE 3
[22:42] <chrisccoulson> so if this is the case, then does /etc/acpi/sleep.sh try to put the machine to sleep, in addition to guidance-power-manager in KDE4? the reason i ask is because i'm looking at a bug from a kubuntu user, where they get a crash on resume from suspend. he can run "pm-suspend" and everything works fine, but if he presses the standby button (which also appears to run pm-suspend), then if fails on resume
[22:42] <chrisccoulson> just got me thinking
[22:43] <hggdh> it might be related, yes. Check if the reporter have both packages installed
[22:43] <chrisccoulson> i will do - thanks
[22:45] <hggdh> bucket529, you may also want to check https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs
[22:45] <hggdh> then we can mark it wishlist
[22:49] <hggdh> bucket529, BTW -- thank you for helping out
[22:52] <bucket529> hggdh, I was just in the process of bookmarking that page, thanks.
[22:53] <bucket529> hggdh, I meant that *section*. I've been becoming a good friend of rmadison -u
[22:59] <bdmurray> bucket529: you might be interested in http://people.ubuntu.com/~brian/reports/needs-packaging/latest-needs-packaging.html
[23:02] <bucket529> bdmurray: Thanks.
[23:02] <bdmurray> that report will have the results of rmadsion and some debian bug searches
[23:09] <chrisccoulson> asac - would you mind taking a look at bug 273633 please? the reporter has provided some information i requested, but my limited knowledge of network-manager makes it difficult for me to take it any further ;)
[23:10] <asac> chrisccoulson: not sure. launchpad appears t be down somehow
[23:13] <chrisccoulson> asac - thanks. that's odd, i can still access LP at the moment
[23:13] <hggdh> ditto from here
[23:18] <Hamra> LP is working here :S but i have no idea about wireless
[23:18] <bucket529> Recommend bug 268714 change from New/Undecided to Wishlist
[23:57] <maco> bucket529: got it
[23:57] <maco> if a bug has apport failed retrace, what should one do?