[02:00] <andresmujica> hi, i'm gonna use move-duplicates.py from python-launchpad-scripts but i've got a doubt, i should mark each bug to move or just checking the main bug it would move the dupes as dupes for the newmaster?
[02:11] <andresmujica> it seems that it would work... only if i can make the script authenticate....
[03:14] <Elbrus> I just added bug 306751, can somebody at least mark it wishlist?
[04:33] <DanielEads> Quick question...  Are kernel bugs being filed against the "linux" package still?
[04:50] <mrooney> DanielEads: Yes I do believe!
[04:55] <DanielEads> mrooney:  Thanks  :)
[06:24] <d-b> hi there there is a bug in ebox on ubuntu 8.10 - it is not installable
[06:31] <d-b> also does anyone know about the status of reportbug on ubuntu -> it still report to debian right ? is this ok / by design / does it go to another area now ?
[06:38] <crimsun> d-b: yes, the ebox uninstallable due to non-existent libapache-authcookie-perl is known
[06:39] <d-b> yes. i saw that crimsun but why is this still the case ? is there a problem in including that package / copying it from a previous release into 8.10
[06:39] <crimsun> 8.10 is frozen.  Anything added must be to intrepid-backports.
[06:40] <d-b>  / the newer ebox put in ubuntu-backports
[06:41] <crimsun> so yes, there is a problem due to that technical detail
[06:42] <d-b> ok and re reportbug
[06:42] <crimsun> also, 0.12.3 is not available yet in jaunty, so it can't be backported to intrepid-backports
[06:42] <crimsun> (however, have you seen http://ebox-platform.com/download/ ?)
[06:42] <d-b> crimsun: fair enough. crimsun yeah.
[06:43] <crimsun> by default, report bug sends to the ubuntu-users mailing list
[06:43] <crimsun> reportbug*
[06:44] <d-b> crimsun: the the description of the package shown by apt-cache show reportbug is wrong.
[06:44] <d-b> or not accurate
[06:45] <crimsun> d-b: please file a bug against it in Launchpad, then
[06:45] <d-b> ah sorry i might have missed the bottom part Bugs: mailto:ubuntu-users@lists.ubuntu.com
[06:45] <d-b> is that re the package as it is included in ubuntu - i assume.
[06:46] <crimsun> that's the default address for bug reports for Ubuntu packages, yes.
[07:15] <d-b> also how can you report bugs in ubuntu from the command line, is it possible if you are just a user and not a devel / higher up in ubuntu.
[07:25] <crimsun> d-b: yes, you can just use reportbug
[07:27] <d-b> crimsun: not to ubuntu i can't
[07:28] <d-b> * i can't to ubuntu
[07:28] <d-b> the server rejects it -> its a known bug
[07:31] <d-b> https://bugs.edge.launchpad.net/ubuntu/+source/reportbug/+bug/123414
[07:35] <crimsun> d-b: you can work around it.
[07:35] <d-b> oh ?
[07:35] <crimsun> also, do you have a gpg key, and have you signed the Ubuntu Code of Conduct on Launchpad?
[07:36] <crimsun> if so, you can use the e-mail interface to LP
[07:36] <d-b> crimsun: mmm i think so. let me check
[07:36] <d-b> yes i believe i have - i had to do that to become an ubuntero no ?
[07:36] <crimsun> yes
[07:36] <d-b> yep. i have signed it.
[07:37] <d-b> ah ... i'm not putting my gpg key on my server to simply report a bug.
[07:39] <d-b> but for my machine- how would i do it -> just set it up to sign mail from me ?
[07:40] <maco> crimsun: um, i cant get the email interface to work
[07:40] <maco> crimsun: and ive certainly done both of those
[07:41] <maco> d-b: yeah, it should work if you sign all your emails
[07:41] <maco> i can use it to send comments to bugs just fine
[07:41] <maco> i cant change status and such through email for some reason though
[07:42] <d-b> wait so there is a filter that is checking if a gpg sig is valid on all mails ?
[07:42] <maco> yes
[07:42] <maco> i believe so
[07:56] <crimsun> maco: where is it breaking?
[07:58] <maco> crimsun: dunno. if i try to set affects...it doesnt get set. it shows up in the body of the comment sent to jp
[07:58] <maco> *lp
[10:36] <wolfger> morning, folks
[10:37] <maco> hi
[10:37] <wolfger> Just saw an update on Bug 113657 that makes me think it should be invalidated (bug reporter fixed problem by changing hardware). What say you all?
[10:38] <maco> is there enough info to work with?
[10:38] <maco> if not...then yeah, id invalidate it
[10:38] <maco> theres also th chance he's got hardware of the same quality as mine ;)
[10:39] <maco> which is to say: broken
[10:39] <wolfger> well, it's filed against 3 packages. One is marked incomplete, so that's an easy invalidate (they clearly don't have enough info). One is confirmed and one new
[10:40] <wolfger> but in a hardware-specific bug, I'm wondering "what are the odds we'll ever know if it's fixed?" if the reporter got new hardware.
[10:41] <wolfger> and maco, do you *ever* sleep?  You seem to be up all night every night
[10:41] <wolfger> and I know you're in my time zone
[10:44] <maco> my classes start at 1420 every day :)
[10:44] <maco> i wake up around 1400
[10:44] <wolfger> dang. Must be nice. I could never get a class schedule that didn't start by 0900
[10:44] <maco> invalidate it, i think. it doesnt sound like its got the info needed
[10:44] <maco> perpetual freshman?
[10:45] <wolfger> OK, thanks.
[10:45] <wolfger> I stalled out somewhere between sophmore and junior.
[10:46] <maco> ah. yeah upperclassmen get afternoon classes here, it seems
[10:49] <LEsinnlos> how i can usw ubuntu-bug to show hin bugs ? i have many errors from wine
[11:15] <danage> jerone: in bug 282207 in your last comment you talk about a different issue with sierra cards where network manager asks the network password. do you mean that it keeps asking for the PIN? because that is the issue i am having with mine - manually entering the pin via terminal works
[16:05] <danage> jerone: ping
[16:41] <MrKanister> Hi. I have a question about the bug #304145 . Would it help If I made a patch and debdiff a debdiff?
[17:02] <crimsun> MrKanister: if you're asking if you need both, the answer is no, you don't need both.  Either will suffice.
[17:04] <MrKanister> crimsun: Thank you. I just wanted to know if it would help the bug. Do you know a good ressource about making patches to source code? Maybe a wiki page?
[17:06] <crimsun> MrKanister: there's https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff for debdiffs
[17:06] <crimsun> just ping if you have questions; I'm in a session ATM
[17:06] <MrKanister> ok...thanks a lot
[17:21] <Hobbsee> !ping
[17:22] <BUGabundo_work> hi Hobbsee
[17:22] <BUGabundo_work> is UDS runnig well?
[17:24] <Hobbsee> BUGabundo_work: hey there.  Seems to be :)
[19:27] <calc> can anyone close a bug as invalid?
[19:28]  * calc thinks maybe just ubuntu bug users should be able to close bugs
[19:28] <calc> some nut is going through OOo bugs and is closing upstream bugs as 'this is not a ubuntu bug, this is a openoffice problem
[19:28]  * calc wonders if the user is a 5-a-day abuser or something similiarly crack
[19:29] <crimsun> calc: check the activity log
[19:30] <calc> he's closed at least 3 bugs in OOo alone for bad reasons
[19:31] <calc> crimsun: user activity or something else?
[19:31] <calc> user activity would be good to see to revert problems like this user
[19:31] <calc> https://bugs.launchpad.net/~sebastiancobaleda
[19:32] <thekorn> he is not doind 5-a-day
[19:32] <calc> thekorn: ok
[19:32] <calc> i think we are lucky then ;-)
[19:32] <calc> otherwise 5 new 'invalid' bugs a day :\
[19:33] <thekorn> I think we should try to contact and ask user why they are doing things the wrong way,
[19:34] <thekorn> is there some bad documentation,
[19:34] <thekorn> or understanding of docs
[19:34] <calc> thekorn: yea, i just told him in a bug report not to do it anymore, but someone more accustomed to dealing with new people should talk to him :)
[19:35] <thekorn> hehe, ok can you give me some bug numbers?
[19:41] <calc> 306925
[19:41] <calc> i'll see if i can get the others quickly
[19:42] <thekorn> 220703
[19:42] <rockstar> calc, I don't see anything out of the ordinary in that one.
[19:42] <thekorn> is the one with your comment ;)
[19:42] <calc> thekorn: yea i just found that one again
[19:42] <calc> thekorn: i wasn't completely calm but refrained from getting myself in trouble ;-)
[19:43] <calc> rockstar: he closed it invalid with his comment, i reopened it already
[19:43] <calc> now if it is actually fixed in 3.0 which is still waiting in jaunty to build then it can be closed at that point
[19:43] <calc> but it shouldn't have been closed already telling the user to just install 3.0
[19:44] <calc> and it should have been closed as fix released instead of invalid if it is indeed fixed
[19:45] <maco> want me to install 3.0 and see if it breaks with normal usage patterns established at least 15 years ago that say if you want to retain ratio, you hold down shift while resizing?
[19:45] <calc> and resizing images that way in 3.0 doesn't keep aspect ratio either, at least afaict
[19:45] <calc> maco: ah shift?
[19:46] <calc> yea shift works :)
[19:46] <maco> yes, shift has always been the way to keep ratio
[19:46] <maco> going back to microsoft paint for win95 at least
[19:47] <calc> maco: ah i don't do much with word processing myself just developer stuff
[19:47] <calc> maco: but yes it works with 3.0 in the ppa
[19:47] <calc> so i updated and documented the shift bit in the bug, thanks!
[19:47] <maco> shift works with 2.4 as wll
[19:47] <calc> oh it does? hmm then no bug at all then i guess
[19:48] <maco> if there's a bug at all, its that the help doesnt say it
[19:48] <maco> so we just need to see if the help says it
[19:48] <calc> marked invalid again explaining why it is invalid (that it already works in 2.4.1 in Intrepid)
[19:49]  * calc probably should go back to paying attention to the UDS session he is in
[19:49] <crimsun> calc: mostly settled
[19:50] <calc> crimsun: ok
[20:16] <sschoonmaker> I think this is a glx bug here:  http://paste.ubuntu.com/83677/
[20:19] <sschoonmaker> this worked fine in 8.04 before I upgraded to 8.10
[20:19] <sschoonmaker> now it won't open any glx windows whatsoever
[22:12] <Flare183> bug 306974
[22:12] <Flare183> Hass anyone looked at that one yet?
[23:12] <azimout> has anyone ever encountered squashfs errors from the livecd that were not hardware failures?
[23:15] <maco> azimout: does the cd being a bad burn count as a hardware failure?
[23:15] <maco> because bad cd and bad cd drive are the only reasons ive encountered
[23:16] <azimout> yes, everything under https://help.ubuntu.com/community/SquashfsErrors
[23:40] <_Zeus_> hey, what should I do with this? https://bugs.launchpad.net/homebank/+bug/306967
[23:40] <_Zeus_> I was thinking to politely tell him that this is the wrong place to report it, but then i thought maybe we oculd upstream it
[23:40] <_Zeus_> what should i do?
[23:41] <chrisccoulson> Homebank upstream uses launchpad as its bug tracker
[23:41] <maco> _Zeus_: just upstream it
[23:41] <chrisccoulson> and that bug only has an upstream task
[23:41] <_Zeus_> ok, how do i do that?  subscribe someone else?
[23:41] <chrisccoulson> its not registered against ubuntu at all
[23:42] <_Zeus_> right, i noticed that
[23:42] <_Zeus_> he used getbed
[23:42] <_Zeus_> *getdeb
[23:42] <_Zeus_> wait, so how do i upstream it?
[23:42] <chrisccoulson> its already upstream
[23:43] <_Zeus_> oh, so i don't need to touch it
[23:43] <chrisccoulson> the bug is already reported against homebank upstream, which just happens to use launchpad as its bug tracker
[23:43] <azimout> homebank is in intrepid universe
[23:43] <chrisccoulson> you don't need to do anything with it
[23:43] <_Zeus_> ty
[23:44] <_Zeus_> what is this?  https://bugs.launchpad.net/launchpad-bazaar/+bug/307010  he says that 'the link succeded on the second try'
[23:45] <_Zeus_> is that a bug?
[23:45] <maco> _Zeus_: see how it doesnt say "ubuntu" in the link?
[23:45] <maco> you can ignore it
[23:46] <_Zeus_> oops
[23:46] <chrisccoulson> maco is right - that's not an ubuntu bug either
[23:46] <chrisccoulson> you should leave that one, as other projects have different rules and may not appreciate us messing around with their bug reports
[23:46] <_Zeus_> i did, didn't notice that