[00:22] <xteejx> how can i grab a backtrace if a package doesnt have -dbgsym or -dbg packages?
[00:23] <xteejx> gdb?
[00:23] <persia> xteejx, gdb can help, but which package?
[00:25] <xteejx> balazarbrothers
[00:26] <persia> xteejx, It looks like that's in python, so the gdb output would be confusing and not so helpful.
[00:26] <persia> You might do better to run under the python debugger, or just try to get a python trace
[00:28] <xteejx> persia: Cool will try thanks :)
[00:28] <persia> More generally, it's worth looking at which language is used by a given package, and using a debugger optimised for that language.  gdb is great of C, C++, ObjC, and a host of other languages, but the results are often too low-level for Python, Java, perl, or similar sorts of code.
[00:31] <xteejx> OK, stupid question, is there a Debugging wiki page for python as there is for gdb etc?
[00:32] <persia> I've not seen one.  man python suggests -d
[00:33] <xteejx> hmmm
[00:38] <xteejx> persia: I've grabbed what I could from the terminal - bug 304977 - let me know if/how I can get anything else - if you wouldnt mind having a quick look please :)
[00:39]  * persia isn't much of a python person, but looks
[00:39] <persia> Oh, Soya.
[00:41] <persia> Does it work with --no-sound or are you reproducing Debian bug #453107 if you do that?
[00:43] <persia> xteejx, Other than that, seems like you have enough of an indicator for someone to look at it.
[00:44] <persia> The "Traceback" section is the interesting part.  The next step would be to get the source, and look at line 103 of sound.pyx to try to figure out why there is an error.
[00:44] <xteejx> ermmmm.....pass, i'm not much use with code lol
[00:46] <xteejx> well its easily reproducible so hopefully itll be ok as it is
[00:51] <persia> Well, OK.  Wait until you get a bug that annoys you enough then.
[00:51] <persia> Sometimes it's just a simple thing that anyone can see, except the poor programmer who wrote it at 5am.  Sometimes it's really hard.
[00:52] <xteejx> persia: Shame coding cant be checked automatically for every single possible bug by a script :( no such luck as it being developed
[00:53] <persia> Well, there are scripts that try to do that, but they aren't human-equivalent, and still make lots of mistakes/
[00:53] <xteejx> Ahh I see
[00:54] <xteejx> Well its way past my bed time so catch you all tomorrow, thanks again persia for the help - much appreciated :)
[00:55] <persia> The code-checking programs are actually better than humans for some types of bugs, but for others, it's just a silly mistake like using -1 instead of +1, when either might be right, but only one has the desired behaviour.
[00:55] <xteejx> lol typical computers :)
[00:55] <xteejx> still....see you all tomorrow good night all :)
[03:39]  * tcole returns
[03:54] <pckchem> OK, this is a bit weird. Can someone explain to me bug 303403 ?
[03:56] <pckchem> I think it's just gibberish, but it may be some sort of work flow thing I've never seen before.
[03:56] <pckchem> All reported by https://bugs.edge.launchpad.net/~maurizio-live
[03:57] <Hobbsee> pckchem: no, that would be a spammer.  launchpad hasn't got the functionality to properly kill accounts, yet.
[03:57] <pckchem> Should I just invalidate all the junk? And who the heck would want to spam launchpad...
[03:58] <Hobbsee> yeah - although if it's private, it's mostly ignorable.
[03:58] <Hobbsee> someone who has no life
[03:58] <pckchem> True enough. Just clogging up my "to triage" linky
[03:58] <Hobbsee> yup
[03:58] <pckchem> Alright well thanks Hobbsee
[03:58] <Hobbsee> pckchem: you're welcome
[03:59] <Hobbsee> pckchem: with any luck, the next rollout will contain the fixes required, so he can't keep going.
[04:21] <hggdh> ah well. rutadeevacuacion is back, I see
[04:21] <pckchem> ?
[04:21] <Hobbsee> pckchem: he's hte spammer
[04:21] <pckchem> Yeah, I'm not very perceptive tonight.
[04:21] <Hobbsee> hggdh: he'll always be back until launchpad gets their bugs fixed, and the next rollout happens about it
[04:22] <pckchem> I just invalidated all his submissions with an email to malone
[04:22] <pckchem> Was actually kicking around the idea of writing a script to scrape all of the bug numbers from a users page to make it easier in the future.
[04:22] <hggdh> Hobbsee, yes. We wait and play this guy's game, meanwhile. But these were the bugs we talked about yesterday
[04:23] <Hobbsee> oh, those were filed yesterday?
[04:23] <Hobbsee> pckchem: you can probably do that with launchpadlib
[04:23] <Hobbsee> (somehow)
[04:23] <hggdh> no, it seems last week
[04:23] <pckchem> I'll look into it.
[04:25] <pckchem> Nice, python. Should make my job easier.
[04:25] <hggdh> and I cannot help but to think of steganography
[04:29] <pckchem> Heh thanks for the tip hobsee, this lib will actually make this pretty darn easy.
[04:29] <Hobbsee> pckchem: oh, and ho<tab> is also useful - means you spell people's nicks right, which tends to actually highlight them
[04:29] <Hobbsee> (works for other nicks too)
[04:29] <Hobbsee> and you're welcome
[14:49] <thekorn> hi \sh! - any good reason you are not in #leonov ;)
[15:20] <xteejx> guys, can someone point me in the right direction - i want to start packaging or at least try and do just the 1 to broaden my knowledge, is there a wiki page or list of procedures/walkthrough on how to do this? btw I'm a triager
[15:21] <BUGabundo_work> xteejx: I don't know of the top of my head
[15:21] <xteejx> Also, if you wouldn't mind can someone high up in the Bug Control team review my application please? :) I'd be grateful.
[15:21] <bddebian> Boo
[15:21] <BUGabundo_work> but did you search for it on help.ubuntu.com ?
[15:21] <nhandler> xteejx: https://wiki.ubuntu.com/PackagingGuide/Complete should get you started
[15:21] <xteejx> Thanks :)
[15:22] <nhandler> You're welcome
[15:29] <xteejx> Question: bug 237859 is a dupe of 230446, but there is already one bug 249719, but I cannot mark the second as dupe of third one as it HAS a duplicate, but the third one has the most info....what do I do? Sorry to confuse, you'll see what I mean if you look :)
[15:30] <BUGabundo_work> xteejx: unmark all the dupes and mark all again against the correct one
[15:30] <BUGabundo_work> LP should make this easier, but still doesn't
[15:30] <xteejx> Bugabundo: How do I unmark a dupe? :S
[15:31] <xteejx> I've never seen an option for it on L{
[15:31] <BUGabundo_work> https://bugs.launchpad.net/ubuntu/+bug/237859/+duplicate
[15:31] <xteejx> *LP
[15:31] <BUGabundo_work> go there and remove it
[15:32] <xteejx> ahhhhhhhhhh :) hehe thanks :)
[15:32] <BUGabundo_work> I've done thatr
[15:32] <BUGabundo_work> do the next ones
[15:32] <xteejx> will do thanks
[15:32] <BUGabundo_work> it would be great if LP would just allow to enter the new dupe, and mark all descent too
[15:33] <xteejx> All done, but yeah I agree, its quite erm...fiddly
[15:34] <BUGabundo_work> nag them on #launchpad
[15:34] <BUGabundo_work> lol
[15:34] <BUGabundo_work> there is a bug about it
[15:34]  * BUGabundo_work opens search
[15:35] <BUGabundo_work> https://bugs.edge.launchpad.net/malone/+bug/78596
[15:36] <xteejx> lol i think i might
[15:43] <xteejx> They're all asleep
[15:58] <MrKanister> Hi. I think the bug https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/305183 is clearly a question. Can I just convert it to one?
[16:00] <BUGabundo_work> MrKanister: yeah, I agree with you
[16:00] <BUGabundo_work> use the https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/305183/+create-question
[16:01] <MrKanister> BUGabundo_work: Ok, thank you. I'll convert it.
[16:22] <xteejx> What do we do with needs-packaging bugs that haven't released any development versions or anything, are they to be marked Invalid, and also the defunct projects or broken links/sites etc are they also to be marked Invalid?
[16:25] <xteejx> Anyone? :)
[16:27] <xteejx> Come on guys wake up lol
[16:27] <bdmurray> It doesn't hurt to have n-p bugs for the former.  For the defunct ones check with the reporter to see if they are following the project and set it to Incomplete, then possibly invalid.
[16:28] <bdmurray> I was typing as fast as I could! ;-)
[16:28] <xteejx> lol I'll let you off bd :)
[16:28] <xteejx> Thats fine though I'll follow that then cheers B :)
[16:30] <persia> For defunct projects, it might also be worth looking at the project.  There's a few things that got done right once, and appear dead, but really work just fine.
[16:31] <xteejx> persia: A majority of the np bugs (I'm working in reverse chrono order) - the pages on sourceforge or the actual website is gone, or there are no links to get the source/binary packages
[16:31] <xteejx> I'm Invalidating them ones
[16:32] <xteejx> bdmurray: btw have you had a chance to look at the bug control app? :)
[16:32] <xteejx> don't mean to rush it or say hurry up or anything, just asking :)
[16:34] <bdmurray> xteejx: Not, yet.
[16:34] <xteejx> bd: Thats kool mate no probs
[16:35] <persia> xteejx, Oh, yeah, if there's no place to download the source, it's invalid.  Being able to download binary but not source is usually invalid as well, except in very special circumstances
[16:35] <xteejx> persia: Ok, just wanted to double check :) thank you
[17:59] <xteejx> Can someone change bug 239751 to Wishlist for me please?
[18:08] <chrisccoulson> xteej - done, thanks
[18:09] <chrisccoulson> 1 comment though - there is no mention of the license in the bug description (unless i just missed it whilst skimming through). it would be great if you could edit the bug description and add the license that the software is released under :)
[18:38] <[1]dynamite> hey people... im getting a really weird error when i boot up... anyone have a minute?
[18:42] <BUGabundo> [1]dynamite: what is it?
[18:43] <[1]dynamite> well im getting a Server Authentication error from GDM... i think its cuz my root filesystem is mounted as read only (at least from the info i've researched)
[18:46] <BUGabundo> it shouldn't
[18:46] <BUGabundo> why is it read only?
[18:47] <[1]dynamite> not sure... been tinkering around with dual booting with xp... xp works fine, nut ubuntu doesnt
[18:49] <BUGabundo>  !pastebin
[18:49] <BUGabundo> [1]dynamite: use pastebin and show us the result of mount and sudo fdisk -l
[18:50] <[1]dynamite> oki
[18:51] <BUGabundo> why the heck did I go way? reboot?
[22:03] <xteejx> chriscoulson: Are you still here I went into suspend just as you sent a message
[22:15] <declan> hey I'm interested in joinging the bug squad
[22:24] <bdmurray> declan: great do you need any help?
[22:26] <declan> Well, I'm just looking at some bugs that I need to match with packages, so I'm trying to figure out how to categorize them
[22:27] <bdmurray> I'd be happy to work on one with you
[22:27] <declan> awesome!
[22:27] <declan> so, how could I start?
[22:28] <bdmurray> Well, you said you were looking at a bug what bug?
[22:28] <declan> would you like a number?
[22:28] <bdmurray> Sure if there is one you've been looking at
[22:29] <declan> 241751
[22:29] <bdmurray> bug 241751
[22:29] <declan> yep. thats the one
[22:30] <declan> so, how should I start assigning it a package?
[22:32] <bdmurray> it's missing some useful information like what release of Ubuntu they are using
[22:32] <declan> ahh, so does that mean that it's not doable?
[22:32] <declan> should I maybe start with any easier one?
[22:33] <bdmurray> Well, its an older bug report and the way input devices are handled has changed a fair bit since Hardy.
[22:34] <bdmurray> However, you could look at https://wiki.ubuntu.com/DebuggingProcedures
[22:34] <bdmurray> and find https://wiki.ubuntu.com/DebuggingKeyboardDetection
[22:34] <xteejx> brian, if theres a bug repor and the reporters name is greyed out, does that mean their account on LP is gone?
[22:34] <bdmurray> Then read those about what information to gather
[22:34] <xteejx> *reporter
[22:34] <declan> I'm so happy that I could just sign on and you would help me. Thanks.
[22:35] <xteejx> That's what we're all here for ;)
[22:35] <bdmurray> xteejx: I believe that means that their account is deactivated, but that doesn't always make a bug less valid.
[22:36] <xteejx> Well its bug 241688 - not exactly a bug report as such anyway - Invalidate?
[22:38] <xteejx> I was going to invalidate it, as its a one-liner "bug" and should go thru brainstorm anyway
[22:39] <bdmurray> xteejx: Why should they go through brainstorm for it?
[22:39] <xteejx> Not sure, I thought it was an idea/request
[22:40] <bdmurray> I'm not quite sure what the reporter means but I don't think it is an idea of great scope
[22:40] <xteejx> Hmm...shame the reporter's accounts removed, I can't ask what he wanted
[22:41] <bdmurray> We can't definitively say it is incomplete so I would recommend leaving it open.
[22:42] <xteejx> Ok sure - thanks again for the wisdom :)
[22:43] <bdmurray> and there's enough info to start doing some research into what they are looking for
[22:45] <xteejx> bdmurray: I haven't the faintest idea what it is to be honest, I think I better leave it lol
[22:47] <xteejx> I'm gonna go through the searches see if anything similar sticks out
[22:48] <xteejx> it looks like binfmt_misc is a kernel module
[22:49] <bdmurray> right, you could also try locate binfmt_misc on your system
[22:49] <xteejx> modprobe?
[22:49] <bdmurray> no 'locate binfmt_misc'
[22:50] <xteejx> ok i can see it's in the /fs kernel module folder
[22:51] <xteejx> how do you open .ko files
[22:51] <bdmurray> right, so the kernel would be a more appropriate place for that bug then someone with more knowledge in that area can comment on it
[22:52]  * xteejx thinks bdmurray is a genius :)
[22:53] <xteejx> As its for linux am I right in thinkin I assign the Kernel Team?
[22:55] <bdmurray> Only Confirmed bugs should be assigned to the kernel team
[22:55] <bdmurray> well confirmed or triaged
[22:55] <xteejx> ok :)
[22:57] <xteejx> phew this can be hard work sometimes...well not hard, just tricky finding things :)
[22:57] <xteejx> but i like a challenge so..
[22:57] <bdmurray> It can require some great detective work
[22:58] <sectech> Good evening
[22:59] <bdmurray> sectech: Hi
[23:01] <xteejx> bdmurray: Also sorry for keep bugging you (no pun intended), but you see with Hardy, Gutsy, etc., I know it says to ask if they can try with Intrepid, but what about LTS? It's one thing that's been confusing me.
[23:02] <bdmurray> Its always good to find out if a bug in Hardy still exists in later releases
[23:02] <xteejx> What I mean is are we not meant to support 3 versions at the mo?
[23:03] <bdmurray> Dapper, Gutsy, Hardy, Intrepid, Jaunty so five really ;-)
[23:03] <xteejx> I see, so its more the case of test in Intepid/Jaunty/K***, etc and then possibly backport it?
[23:03] <xteejx> You're still supporting dapper? bloody hell
[23:04] <bdmurray> Stable Release Update depending on the severity
[23:04] <xteejx> That's the same thing as backports isn't it (for a simple mind like myself)
[23:06] <xteejx> lol ermmm it would never be possible to automount and autodetect floopy drives would it?
[23:08] <xteejx> ref bug 242108 : I can't see it happening, surely the drive would have to be constantly spinning?
[23:20] <chrisccoulson> xteejx - to automount floppy drives, HAL would have to probe the drive (in a similar way as it does with CD drives)
[23:20] <chrisccoulson> that would mean spinning the floppy drive up every 2s (or however often the drive is polled)
[23:22] <xteejx> chriscoulson: That's what I thought, too many people would be annoyed at having to listen to the crunch of a floppy drive every few seconds
[23:23] <xteejx> I ended up suggesting on the report to brainstorm it, as its a feature request anyway
[23:24] <chrisccoulson> i think hal was inadvertently set to poll floppy discs at some point, which was rapidly disabled. if you search through the really old hal bugs, you might find something
[23:24] <chrisccoulson> i would leave a comment in the bug report telling them not to bother cluttering brainstorm with the idea;)
[23:25] <xteejx> ok will do :)
[23:58] <sectech> What are kernel bugs being filed under for 2.6.24?
[23:58] <sectech> ... driver issue
[23:58] <sectech> Usually I would pick kernel-source.......whatever version
[23:59] <bdmurray> sectech: it's just linux now
[23:59] <sectech> ok