UbuntuIRC / 2008 /04 /29 /#ubuntu-bugs.txt
niansa
Initial commit
4aa5fce
=== x-spec-t is now known as Spec
=== bdmurray changed the topic of #ubuntu-bugs to: Bug Day! https://wiki.ubuntu.com/UbuntuBugDay/20080429 | Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ - http://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
[01:09] <ffm> How do I change a bugs language, like that of
[01:09] <ffm> Bug #223973
[01:09] <ffm> * https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/223973 (ubotu seems to be acting oddly today...)
[01:10] <Nafallo> ffm: do you even see him? :-)
=== golddragon24_ is now known as golddragon24
[01:13] <ffm> Nafallo: What?
[01:13] <ffm> Nafallo: Ah....
[01:13] <Nafallo> ffm: ubotu isn't here.
[01:13] <secretlondon> edit description/tags will allow you to change the description
[01:13] <secretlondon> if you speak german
[01:16] <secretlondon> Nafallo, I thought the reason why -bugs-announce was silent was because Hardy was bug free ;)
[01:19] <xee> Hi, I wanted to know how I can help with triaging bugs, I saw the list at https://wiki.ubuntu.com/UbuntuBugDay but I'm not sure what to do
[01:21] <secretlondon> xee: the list are on the 20080429 page
[01:22] <secretlondon> but they are coming up as forbidden..
[01:23] <xee> ok, I opened it, what should I do next?
[01:25] <secretlondon> https://wiki.ubuntu.com/BugSquad is the best place to start
[01:25] <secretlondon> https://wiki.ubuntu.com/DebuggingProcedures and https://wiki.ubuntu.com/Bugs/FindRightPackage
[01:25] <xee> ok, I got it, thanks a lot
[01:28] <ffm> Does the "triaged" stage come before or after "confirmed"?
[01:29] <secretlondon> after
[01:30] <secretlondon> can anyone access https://launchpad.net/bugs/223339? I'm in bug control and I get forbidden
[01:30] <secretlondon> I've tried stopping redirect to edge and still forbidden
[01:31] <ffm> secretlondon: And it indicates that the problem is in a state that it can be looked at by a developer?
[01:31] <secretlondon> Looks like apport crash bugs are broked
[01:31] <ffm> secretlondon: Example, a bug that has a non-critical feature reuquest, but also has a patch. ( https://bugs.edge.launchpad.net/ubuntu/+source/curl/+bug/223855 ) Is it already "triaged"?
[01:32] <secretlondon> ffm: https://wiki.ubuntu.com/Bugs/Status
[01:32] <secretlondon> ffm sounds like triaged, and wishlist
[01:33] <ffm> secretlondon: I can't set priority yet.
[01:33] <secretlondon> tbh I tend just to use confirmed, but that may be me
[01:33] <secretlondon> ffm sure
[01:33] <secretlondon> I've just set as wishlist for you
[01:34] <ffm> secretlondon: merci
[01:34] <secretlondon> we need debdiffs though
[01:34] <secretlondon> and then to susbcribe a sponsor team
[01:35] <ffm> kk
[01:35] * ffm has to go. Have a great bug-fixing time!
[01:40] <secretlondon> bdmurray there is a problem with perms for crash bugs. I'm in bug-control and bugs on the list are coming up as forbidden
[01:41] <secretlondon> bdmurray i've set them as red not lightgreen, as they are not fixed, just broken
[01:45] * secretlondon decides to rewrite the rules for the hugday on the grounds it's a wiki ;)
[01:49] <bdmurray> secretlondon: the red looks angry, maybe just deleting them would be easier on the eyes
[01:49] <secretlondon> bdmurray: okay, but there is something broken somewhere with permissions
[01:49] <bdmurray> secretlondon: the retracer is turned off so only the reporter and apport are subscribed to those bug reports
[01:49] <secretlondon> I suspect apport related
[01:49] <secretlondon> bdmurray: shall I just filter them out and remove them?
[01:50] <bdmurray> secretlondon: that'd be great!
[01:50] <secretlondon> bdmurray: okay will do
[01:50] <secretlondon> bdmurray: and then if we have too few we'll find some more
[01:50] <bdmurray> secretlondon: there are always more around!
[01:50] <secretlondon> oh yes!
[01:52] <mrooney> hrm, can karma go down on launchpad?
[01:52] <secretlondon> mrooney, it expires
[01:52] <secretlondon> time related
[01:52] <bdmurray> mrooney: it's a measure of your recent activity, I think over the past 90 days or so
[01:53] <mrooney> ahh I see, thanks
[02:01] <tam> hello all i have a bug
[02:02] <secretlondon> hi tam
[02:02] <tam> I am getting a gdm crash in firefox 3 when visiting ubuntuguide.org . Running AMD_64
[02:02] <tam> this is only with compiz enabled
[02:03] <tam> Apr 28 19:53:14 tam-desktop kernel: [ 1001.999561] Xorg[7042]: segfault at ff0080d427 rip 7f3389df315b rsp 7fff95e47a80 error 4
[02:03] <tam> Apr 28 19:53:14 tam-desktop kernel: [ 1002.021530] compiz.real[7282]: segfault at 16f00000000 rip 40fee0 rsp 7fff37965830 error 4
[02:03] <tam> Apr 28 19:53:14 tam-desktop gdm[7018]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
[02:03] <RAOF> tam: And you've got a nvidia card, right? There's a bug on launchpad that you'll want to search for
[02:04] <tam> yes
[02:04] <tam> do you happen to know the bugid off the top of yoru head?
[02:05] <RAOF> No; but it'll be filed against linux-restricted-modules-2.6.24
[02:06] <tam> thank you
[02:15] <secretlondon> bdmurray: all forbidden bugs removed
[02:25] <bddebian> Boo
[02:26] <jjesse> don't cry :)
[02:26] <bddebian> :)
[02:26] <secretlondon> hi bddebian
[02:27] <bddebian> Hello secretlondon
[02:28] <tam> okay so i found that bug in launchpad but it was a really old one, however there seems to be lots of segfault failures with the new glx drivers
[02:28] <tam> well segfault crashes
[02:29] <tam> is there a way for me to use the nvidia-glx that was in gutsy instead?
[03:17] * jaredbuck is working through the ubuntu bug list, some people simply don't include enough information...
[03:18] * secretlondon wonders what we do with bugs that apport hasn't retraced
[03:21] <greg-g> secretlondon: because it hasn't got to it yet or that it failed?
[03:21] <jaredbuck> one of the bugs i looked through was a guy having trouble with vmware-server not recognizing his usb devices. i suggested in the comments that he try installing the device drivers for the usb devices within the virtual environment. I've run some OSes virtually and some things didn't work unless you installed the drivers for them within the virtual environment.
[03:24] <secretlondon> greg-g I think maybe neither
[03:25] <greg-g> secretlondon: really?
[03:25] <secretlondon> greg-g there are serpentine crash bugs like https://bugs.launchpad.net/ubuntu/+source/serpentine/+bug/209599
[03:25] <secretlondon> I'm thinking I should try and retrace them here
[03:25] <secretlondon> still have core dump attached
[03:26] <secretlondon> jaredbuck many bugs are support requests (and some support requests are bugs)
[03:26] <greg-g> secretlondon: there is a tag that it uses as an identifier of bugs needing retracing
[03:26] <greg-g> I forget what it is though
[03:27] <secretlondon> well apport is off anyway, which is why we had loads of bugs that were forbidden on the hugday list
[03:27] <jaredbuck> secretlondon: I can see that, i hope the user who submitted the bug checks my comment and tries what i suggested.
[03:28] <greg-g> added the tag "need-i386-retrace"
[03:28] <secretlondon> jaredbuck: we often have to handhold
[03:28] <secretlondon> greg-g thanks
[03:28] <jaredbuck> i just joined the bugsquad today so I'm new to the bug squashing.
[03:28] <secretlondon> jaredbuck :)
[03:28] <greg-g> welcome jaredbuck
[03:29] <jaredbuck> thank you :) I joined after seeing the Bug Squad session this morning.
[03:30] <greg-g> awesome
[03:30] <greg-g> I missed that unfortunately, dang having a job ;)
[03:31] <secretlondon> I missed it as I didn't see the email about the open week until today
[03:32] <secretlondon> This https://wiki.ubuntu.com/DebuggingProgramCrash has something about "running apport-retrace as you are used to"
[03:32] <jaredbuck> i got that email yesterday and managed to wake up at 8 am (pacific time zone here). i don't often wake up that early lol.
[03:32] <secretlondon> lol
[03:33] <jaredbuck> I'll be around for most of the sessions this week. looking forward to learning new things about Ubuntu i didn't know before.
[03:34] <secretlondon> :)
[03:34] <secretlondon> there are a few serpentine crashed on boot bugs (after gutsy->hardy upgrade), of course we removed serpentine from default hardy install
[03:36] <jaredbuck> what kind of bugs?
[03:36] <jaredbuck> sure glad Ubuntu has great accessibility support because I'm legally deaf :)
[03:37] <secretlondon> :)
[03:38] <jaredbuck> ah. serpentine is one of the audio apps. then again i don't need audio LOL. still looks like it's in beta is it?
[03:39] <secretlondon> well it used to be in gutsy on the CD, and isn't in hardy. I just found one bug about it on the hug day list, and then found loads more..
[03:39] <jaredbuck> well maybe we can get around to fixing what we can on bug day tomorrow :)
[03:40] <secretlondon> jaredbuck, of course, but it becomes addictive! You get distracted by troubleshooting, and possible patterns and..
[03:40] <secretlondon> jaredbuck, it can be worse than wikipedia!
[03:41] <jaredbuck> secretlondon: haha, wikipedia? I've edited articles on there LOL. I know what can be addicting, and bug fixing sounds good to me.
[03:46] <secretlondon> :)
[03:48] <jaredbuck> i know txwikinger on here from previous association with project gutenberg. Kinda neat to find someone you know :)
[03:49] <greg-g> right on
[03:50] <jaredbuck> there's another bug class session on saturday isn't there?
[04:00] <secretlondon> jaredbuck, not sure
[04:01] <jaredbuck> i checked the schedule, it says there's one saturday morning.
[04:01] <secretlondon> I'm looking at apport-retrace but to get it to do it automatically you need to know how launchpad does authentication. cookies? the man page suggests cookies.txt, I can find a cookies.sqlite in ~/.mozilla
[04:03] <greg-g> not sure
[04:04] <secretlondon> the instructions are very general - presumably because it's expected that apport-retrace for ubuntu will be run at the data centre
[04:04] <secretlondon> although it's in the repos
[04:05] <secretlondon> I'll try saving the core file and doing it manually
[04:05] * secretlondon wants to get the bottom of this serpentine bug!
[04:10] <secretlondon> looks like apport-retrace only works with .crash files not coredumps
[04:11] <greg-g> doh
[04:11] <jaredbuck> no dumps? that'll make it a little harder to find the problem won't it?
[04:11] <greg-g> is a .crash just a .gz of those separate files?
[04:13] <secretlondon> greg-g i don't know. man apport-retrace either wants a bug number as input, or the .crash file. I can't get it to authenticate to launchpad though
[04:13] <persia> If you've the same version of the package locally, and the dbgsym loaded, try loading the core file in gdb. From there, you ought be able to generate a stacktrace locally.
[04:13] <secretlondon> persia: thanks!
[04:14] <greg-g> persia: good to know
[04:14] <persia> This was the old way to do it. apport-retrace was intended to make it easier, but it doesn't always work.
[04:15] <secretlondon> I can't see how to get it to authenticate to launchpad, so this does look easier
[04:20] <secretlondon> except that there are no dbg or dbgsym versions of serpentine
[04:20] <secretlondon> I'm gonna go really old school and build my own debug package ;)
[04:20] <secretlondon> ooh nixternal has just twittered that the intrepid toolchain is being uploaded!
[04:21] <persia> secretlondon: If you build your own debug package, you can't be guaranteed the symbols will be in the same location, so it may be difficult to read the foreign core file (in which case, you need to reproduce the bug locally, and generate your own core file).
[04:21] <persia> Also, if sepentine doesn't have debug symbols, that's another bug
[04:22] <secretlondon> persia: I think it's a gutsy->hardy upgrade bug
[04:22] <secretlondon> persia: where do I file the lack of debug symbols?
[04:23] <persia> Launchpad? Unless sepentine hasn't been updated since feisty, it likely needs someone to review debian/rules to find out why it's not generating the dbgsym package.
[04:24] <secretlondon> ah so against serpentine itself, not against a particular service
[04:25] <persia> Alternately, if it was last uploaded in gutsy, and there is a dbgsym package in gutsy, but not in hardy, you ought be able to debug with the gutsy dbgsym, but it would indicate an issue with the service (for which, I'm less sure how to file the report).
[04:26] <persia> No, it was uploaded in hardy. It's a bug in serpentine. It's not calling the pkg-create-dbgsym hook somehow.
[04:26] <secretlondon> it may be connected to the move from main ->universe
[04:26] <secretlondon> persia: thanks
[04:27] <persia> Possibly, but then the dbgsym package ought be in ddebs.ubuntu.com hardy main, and would likely still be available.
[04:43] <gnomefreak> persia: you have a minute?
[04:44] <persia> gnomefreak: About that. Why?
[04:44] <gnomefreak> im up for renewal ubuntu memebership i missed last meeting, what do i need to do to go about it?
[04:46] <persia> gnomefreak: I'm not really up on the procedures for membership renewal. I think you just need to still be active and involved. Maybe someone else can answer, or I'll let you know when I find out.
[04:46] <gnomefreak> persia: ok thanks i saw you on list and here so i thought i would try
[04:47] <persia> gnomefreak: No problem. I'm just very new at that, so still learning :)
[04:48] <gnomefreak> persia: good luck with it :)
[04:48] <mrooney> oh boy ubuntu membership
[04:48] <mrooney> I aspire to apply for that at some point in the not-too-distant future
[04:51] <secretlondon> mrooney, me too at some point
[04:52] <jaredbuck> I would like that at some point too.
=== RAOF_ is now known as RAOF
[04:57] <secretlondon> anyone know what error 104 is on the applet?
[04:59] <jaredbuck> not I.
[04:59] <secretlondon> I've got it for both bugs I tried to submit
[05:00] * secretlondon hasn't been able to submit a bug to 5-a-day for about a month now
[05:02] <jaredbuck> i'm trying to google for an answer to that question.
[05:03] <secretlondon> I suspect it is a bzr error
[05:03] <secretlondon> someone like james_w or thekorn will know
[05:03] <jaredbuck> probably. sometimes searching for the answer can be difficult.
[05:07] <gnomefreak> persia: nevermind i found the email click link and done :)
[05:07] <persia> gnomefreak: Ah. Self-renewal. Thanks: that's easier ;)
[05:08] <gnomefreak> looking to see if it was updated but didnt look like it when i checked before
[05:22] <secretlondon> anyone know where fglrx comes from?
[05:22] <secretlondon> restricted-modules?
[05:23] <RAOF> Yup.
[05:24] <secretlondon> ty
=== JaredB is now known as jaredbuck
[06:20] <secretlondon> bah bug has references to nvidia and flash player!
[06:20] <secretlondon> how exactly we are supposed to fix this I dunno
[06:21] <jaredbuck> what exactly does the person posting the bug have a problem with regarding those?
[06:21] * lucent facepalms
[06:22] <secretlondon> oh it's a crash, looks like flash caused a crash in nvidia
[06:22] <lucent> to be fair, it's very difficult for vendors to create stable proprietary software for *nix platform
[06:22] <jaredbuck> true, that.
[06:23] <secretlondon> true
[06:23] <secretlondon> I'm just trying to work out which package to allocate it to
[06:24] <secretlondon> nspluginwrapper and npviewer
[06:24] <lucent> audio and context bugs have been known to crash Xorg when flash player does bad things
[06:25] <jaredbuck> flash is quite buggy on linux, it crashes some websites i visit.
[06:25] <lucent> these are particularly painful with nvidia drivers which implement their own GART layer
[06:28] <gnomefreak> jaredbuck: run locate libflashsupport.so and if its in /usr/share/mozilla/...... than remove it that should help with some crashes if not all
[08:52] <kahrytan> Can anyone fix the bug #220952 by setting up a xorg config for displayconfig-gtk to support the monitor?
[08:53] <persia> kahrytan: Re bug 220952: While it can be done in displayconfig-gtk, oughtn't it rather be done in X itself?
[08:53] <kahrytan> you were just waiting for that werent you
[08:54] <kahrytan> persia, true but someone else may have trouble and then displayconfig-gtk can detect it better
[08:54] <persia> kahrytan: Actually for the join, but you've caught me :)
[08:55] <kahrytan> In essence, it makes sure no one else has the same problem
[08:55] <persia> kahrytan: Oh sure, but I think it ought be chased in both places. Firstly, X shouldn't try to use that frequency for that equipment at that resolution, and secondly, the device ought be available in displayconfig-gtk.
[08:55] <kahrytan> Add the config to bug?
[08:56] <persia> The linux-restricted-modules task is probably a good place for now. I'm really not sure whether that sort of adjustment belongs in the driver or somewhere else in the X stack.
[08:56] <kahrytan> It doesnt have to do with nvidia though.
[08:57] <persia> Are you sure? Have you tested with the same monitor and a different video card? I'm just not sure which piece is responsible for assigning the autodetected scan rate.
[08:58] <kahrytan> persia, i did turn off the driver.
[08:58] <persia> Oh. If you can replicate with both nv and nvidia, then I agree the linux-restricted-modules task is probably assigned to the wrong package.
[08:59] <kahrytan> How would i use nv instead .. from noob point of view.
[09:00] <persia> The answer used to be to switch it in /etc/X11/xorg.conf. I don't know how to do it for hardy.
[09:00] <kahrytan> oh yeah xserver-xorg-video-nv
[09:00] <kahrytan> thats the driver?
[09:01] <persia> I think so. On the other hand, that driver doesn't support 3D, so you might encounter a different bug when you test with it.
[09:01] <kahrytan> I would just use screen resolutions applet
[09:01] <kahrytan> change to 800x600 w/ bad rate
[09:02] <persia> If that breaks, that ought confirm the driver isn't responsible.
[09:02] <kahrytan> brb
[09:05] <kahrytan> Back. Tried with Screen Resolutions and 800x600 65hz. It broke.
[09:05] <kahrytan> NV driver
[09:06] <persia> Excellent. Please update the description of the bug to more clearly blame the resolution and scan rate, rather than the games (update description is on the upper left).
[09:06] <kahrytan> I think its any scan rate other then whats reccomended.
[09:06] <persia> Also, it's clearly not a linux-restricted-modules bug. Probably best to update that task (little arrow thingy next to the name), and change the source package to xorg.
[09:07] <kahrytan> How do i test is better w/o applet?
[09:07] <persia> Likely. Screens tend to be sensitive: it's not like the old days where one was only adjusting fine parameters for a particle-ray
[09:08] <kahrytan> On the other hand, NV fixed my gdm issue
[09:08] <kahrytan> it didnt scale well
[09:08] <kahrytan> persia, isnt this easy to fix?
[09:09] <persia> kahrytan: I'm not sure. I'm not familiar with either X autodetection or displayconfig-gtk
[09:09] <kahrytan> proper xorg config shouldnt be to hard but over my head.
[09:09] <persia> It's the "shouldn't" that is the sticky bit :)
[09:09] <kahrytan> I did think to include monitor specs.
[09:11] <kahrytan> change restricted to xorg?
[09:11] <persia> That's likely useful. With the updates outlined above, it ought get feedback from someone more familiar with triaging X bugs, and they'll ask for any other required information. Eventually, there'll be enough there the developers can get it fixed.
[09:11] <persia> kahrytan: Yes, change that. Since you've confirmed you can repeat the bug with two different drivers, it's not going to be the kernel modules, but just X.
[09:12] <kahrytan> there is a pdf of monitor specs
[09:12] <kahrytan> considered attaching the pdf
[09:12] <persia> If it's available from the manufacturer, you might just provide a link to it, rather than attaching it.
[09:17] <kahrytan> I realized the value of oSSnv driver over nvidia
[09:19] <kahrytan> persia, https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/220952 ?
[09:21] <persia> kahrytan: That looks better. You might want to check https://help.ubuntu.com/community/DebuggingXAutoconfiguration and https://wiki.ubuntu.com/DebuggingXorg to see if there is other information you could add to help identify the issue.
[09:23] <dejv_ntb> hello
[09:24] <persia> dejv_ntb: Welcome
[09:24] <kahrytan> I cant use gnome w/ sudo dpkg-reconfigure xserver-xorg?
[09:25] <dejv_ntb> can somebody guide me to provide information for bug #223835, please?
[09:25] <persia> kahrytan: I think you'd do better to do that from console
[09:26] <dejv_ntb> https://bugs.launchpad.net/ubuntu/+source/gnome-volume-manager/+bug/223835
[09:26] <kahrytan> I tried it and it skipped video config.
[09:27] <persia> Umm. Aren't we supposed to indicate the source of the duplicate bug when describing a bug as duplicate? How is one to know when it is addressed?
[09:28] <kahrytan> i found another bug on desktop icons
[09:29] <kahrytan> might be nvidia or compiz? sometimes trash icon doesnt show as full
[09:35] <kahrytan> persia, You really thing someone will need all that information on xorg?
[09:36] <persia> kahrytan: Possibly. My experience for the bugs I've fixed is that where I can't reproduce it locally, I need lots & lots of information to be sure of what I'm doing. I suppose you could just give your computer to a developer, if they were sufficiently interested :)
[09:38] <thekorn> good morning.
[09:40] <kahrytan> persia, discover doesnt even work
[09:42] <kahrytan> persia, Someone added a Mandriva related bug too
[09:43] <qense> happy bug day!
[09:44] <kahrytan> but not so happy when you got one.
[09:50] <kahrytan> qense, what do you do
[09:50] <qense> I'm a bug triager
[09:50] <qense> (and a web developer, but not for Ubuntu)
[09:52] <kahrytan> darn
[09:52] <qense> why?
[09:52] <kahrytan> i was gonna mention start.ubuntu.com/8.04 issue
[09:52] <kahrytan> it searches google uk...
[09:53] <james_w> kahrytan: you can file bugs against ubuntu-website
[09:55] <kahrytan> james_w, i thought about it.. but to lazy for simple issue
[10:02] <kahrytan> persia, Whenever I see a glitch or possible bug. I try to reproduce it. Often cant and move on
[10:12] <jpatrick> kahrytan, james_w: you may wish to hilight web problems at #ubuntu-website
[10:12] <james_w> jpatrick: ah, didn't know about that channel, thanks.
[10:12] <kahrytan> jpatrick, I'll add that to my list of round-to-its
[10:12] <jpatrick> james_w: it's newish
[10:54] <iulian> G'morning
[10:54] <lucent> argh
[10:54] <lucent> I'm getting bit by bug #8497
[10:59] <kahrytan> lucent, be sure to put on some bug screen
=== __Czessi is now known as Czessi
=== asac_ is now known as asac
[15:40] <bddebian> Boo
[15:42] <afflux> mornin
=== x-spec-t is now known as Spec
[16:08] <bdmurray> mvo: could you look at bug 223619 with me?
[16:13] <james_w> bdmurray: isn't that fixed?
[16:15] <bdmurray> james_w: the stale firefox tab got me
[16:16] <james_w> bddebian: btw, is there a hug day this week?
[16:16] <bdmurray> james_w: there is a no package one today, I'm not sure what pedro_ has planned for Thursday
[16:17] <james_w> we had a suggestion for one we could do if there is a free slot sometime. I should have proposed it for today, but forgot.
[16:17] <pedro_> nothing for this week, I've prefer to let people go to open week rather
[16:17] <bdmurray> Is that the reviewing patches one?
[16:17] <james_w> bdmurray: yup
[16:18] <james_w> pedro_: that sounds like a good idea.
[16:18] <bdmurray> maybe we should try out reviewing patches ourselves on Thursday then?
[16:18] <bdmurray> to get an idea of the workflow etc
[16:18] <james_w> as it's something new that might be a good idea.
[16:20] * afflux volunteers to help reviewing patches, as long as I understand what they do :)
[16:21] <james_w> afflux: as a first step we just want to weed out the things that aren't patches, e.g. screenshots
[16:21] <afflux> ah I see
[16:21] <james_w> it appears as though some people just check the box without realising what it means, and so it is hard to know whether there is a real patch to review for a bug.
[16:22] <james_w> we could at the same time weed out the patches that add "rm -rf /" or other things that won't get in
[16:22] <bdmurray> getting numbers on not patches might help getting a launchpad change made
[16:23] <james_w> and obviously any time you want to spend reviewing patches would be hugely appreciated, but it's not really something we can run a hug day on.
[16:23] <afflux> can't we use bughelper or at least py-lp-bugs to get the attachment files that end on like .png or similar? (or even have a wrong mime-type != text/plain)
[16:23] <afflux> yeah right
[16:23] <james_w> that sounds like a good idea
=== x-spec-t is now known as Spec
[16:24] <afflux> bughelper at least spits out the URLs of attachments when they matched a search pattern so I think there should be some way
[16:26] <persia> If there is a patch review day, it might be worth cross-posting the announcement to ubuntu-motu@, and announcing when there's a good looking patch during the day so someone can wrap it into a candidate for upload.
[16:26] <persia> On the other hand, that might be an argument for delaying a patch review day until the archives are open
[16:27] <persia> Oh, and sometimes a .png is a patch (e.g. problems with an icon) :)
[16:27] <bdmurray> This is why I think we should have a test run so we can evaluate the workflow and criteria of what is and isn't a patch
[16:27] <bdmurray> As far as I know that isn't documented
[16:28] <persia> Makes sense. Have a test-run day, and then do a patch-push day sometime next month.
[16:28] <james_w> I don't think it's explicit, and what makes a good patch certainly isn't.
[16:29] <persia> I generally think of a patch as anything which, when added to the source, is a significant part of the solution.
[16:30] <james_w> using bughelper would probably be a good idea anyway, as it's currently a pain to find out which of the attachments is actually marked as a patch as far as I can see
[16:31] <persia> And there are a fair number of non-patches marked patches, and patches not marked (or were last time I spent a day doing patch review)
[16:56] <afflux> james_w: looks like py-lp-bugs sets the mime type to text/plain when the patch button is selected
[16:56] <afflux> see https://bugs.launchpad.net/ubuntu/+source/uswsusp/+bug/114688/comments/2
[16:57] <afflux> err, py-lp-bugs does that in its sources, but LP seems to do so also, that's what the link shows
[16:58] <thekorn> all patches are automatically set to text/plain by lp
=== x-spec-t is now known as Spec
[16:59] <thekorn> and py-lp-bugs adopts this behaviour
[17:00] <afflux> thekorn: that keeps us from using the mime type for checking whether an attachment is likely to be a patch or not
[17:01] <afflux> I mean to check it when it is flagged as a patch
[17:02] <thekorn> I think this is an issue in launchpad, there is no way to see if an attachment is an patch or not
[17:03] <thekorn> besides clicking on 'edit' and check if the patch field is checked
[17:03] <afflux> ah I see
[17:04] * thekorn suggests a HUGE "I'm a patch" icon for patches
[17:04] <afflux> malone is the bugtracker, right?
[17:05] <seb128> it's called launchpad bugs now
[17:05] <afflux> ah okay, the project's identifier is malone
[17:05] <seb128> where?
[17:06] <afflux> in lp itself: https://launchpad.net/malone/
[17:07] <seb128> ah, right
[17:08] <afflux> thekorn: just found bug 172507
[17:10] <ffm> Hey, can someone check whether Bug #149181 has anything private in it?
[17:11] <ffm> https://bugs.edge.launchpad.net/ubuntu/+source/workrave/+bug/149181 (only people in ~ubuntu-bugcontrol can see ATM)
[17:11] <thekorn> afflux, I subscribed myself to this bug, when this is fixed I will modify the Attachment.is_patch() function
[17:12] <afflux> thanks
[17:13] <afflux> ffm: not sure about the string in DistributionManager::log, besides it looks okay for me
[17:14] <afflux> *the strings
[17:15] <thekorn> I think james_w started a thread on the ubuntu-bugsquad ML about patches
=== x-spec-t is now known as SPec
=== SPec is now known as Spec
[17:18] <ffm> afflux: where?
[17:19] <afflux> ffm: oops, the stacktrace in https://bugs.edge.launchpad.net/ubuntu/+source/workrave/+bug/149181/comments/2
[17:20] <ffm> afflux: I don't see anything...
[17:21] <ffm> (anything dangerous, anyway.
[17:21] <afflux> yes, it just looked long and I have no idea what the content means, so maybe thats safe ;)
[17:22] <ffm> afflux: Oh, that's my social security number in EBDIC!
[17:22] <ffm> ;)
[17:22] <afflux> hehe :P
[17:33] <mvo> bdmurray: re 223619> I fixed that earlier (I think) - but its not uplaoded yet
[17:33] <mvo> bdmurray: (sorry, I was at dinner when you pinged me)
[17:34] <bdmurray> mvo: no problem, I didn't realize you had seen it already
[17:35] <mvo> I was doing a lot of triage/testing for u-m yesterday and today, its really hard work
[17:35] <mvo> and I'm a bit unhappy on how many maintainer script failure and similar issues are still left in hardy
[17:37] <bdmurray> right, I'm sure. have you seen bug 222278?
[17:45] <mvo> bdmurray: yes, I have currently no idea were it comes from :( I have seen a few duplicates of it, but haven't seen it myself yet
[17:47] <bdmurray> mvo: what sould be helpful in debugging it?
=== x-spec-t is now known as Spec
[17:53] <KelvinGardiner> Hi, I came across this bug in launchpad 223186.
[17:53] <mvo> bdmurray: that is really difficult, the code where it seems to hang is pretty small and I can not explain why it might hang there
[17:54] <KelvinGardiner> I don't think it is a bug. As the sorting order can be changed.
[17:54] <mvo> bdmurray: having someone available on irc with a system where the hang happens would be cool - or good instructions how to reproduce the hang in a VM would be even better
[17:54] <KelvinGardiner> Should it be marked as invalid?
[17:57] <pedro_> KelvinGardiner: i'm not into gtodo, but if you tested what the reporter said and it works fine, i'd say invalid
[17:58] <KelvinGardiner> pedro_: ok, thanks
[17:59] <bdmurray> mvo: I found the debugging info the reporter and I went over at http://irclogs.ubuntu.com/2008/04/26/%23ubuntu-bugs.html
[17:59] <bdmurray> mvo: it's at about 03:5x
[18:01] <mvo> bdmurray: is he around sometimes?
[18:01] <bdmurray> mvo: I haven't seen him since that day. I wonder if it has something to do with -proposed and -backports though
[18:37] <kp5150> any status on the problem with browsing Windows shares?
[18:39] <kp5150> anyone? is this the right forum for this question?
[18:40] <seb128_> no change
[18:40] <kp5150> thanks
[18:40] <seb128_> the issues are known but that's not trivial to fix or rather we lack people knowing the code and upstream is not responsive
[18:41] <kp5150> understood. Just trying to get some info as the web forums have several threads about the same thing each with no answer
[18:42] <kp5150> it's kind of a big deal as I was planning on a test roll out for one of my clients as a Windows alternative. I will wait
[18:43] <kp5150> is this just with Gnome? Will Kubuntu/Xubuntu work?
[18:45] <seb128_> that's just GNOME, or rather gvfs
[18:45] <seb128_> we know that's an issue
[18:46] <seb128_> and it's recommended to wait for 8.04.1 if you need to deploy something polished, we will keep focussing on fixing hardy issues for a while
[18:46] <kp5150> I can wait, thanks for the info! Much appreciated.
[18:48] <seb128_> you are welcome
[20:10] <sroecker> do patches that are fixed now get into hardy, oder hardy-proposed etc?
[20:11] <bdmurray> sroecker: I'm not sure I understand the question. Is there a specific bug you are looking at?
[20:11] <sroecker> bdmurray, yes Bug 206921
[20:16] <bdmurray> sroecker: this bug isn't currently going through the SRU process but I think it could
[20:18] <sroecker> bdmurray, ah, SRU, thats what I need to know, thx. Do bugs that don't get into SRU go into proposed or backports?
[20:18] <bdmurray> -proposed is for packages in the SRU process after they are verified as fixing the bug and not causing regressions then get moved from -proposed to -updates
[20:19] <sroecker> thanks
[20:19] <bdmurray> sroecker: I'll work on getting it fixed
[20:19] <bdmurray> thanks for bringing it up
[20:20] <sroecker> yeah, I thought nobody looked at it and it's a one line patch
[20:23] <bdmurray> it's hard to keep track of every change to every bug and I really do appreciate your bringing it up
[20:34] <ffm> Can someone set the priority of https://bugs.edge.launchpad.net/ubuntu/+source/vinagre/+bug/224248 to wishlist for me?
[20:37] <ffm> And how do I add an upstream link from https://bugs.edge.launchpad.net/ubuntu/+source/curl/+bug/223855 to http://sourceforge.net/tracker/index.php?func=detail&aid=1953732&group_id=976&atid=350976 ?
[20:38] <bdmurray> ffm: Have you seen http://wiki.ubuntu.com/Bugs/Watches ?
[20:43] <bodinux> Hi, I'm looking for someone printing on a network printer. Anyone ?
[20:51] <jaredbuck> Hi all, i'm woken up now LOL.
=== never|mobi is now known as neversfelde|mobi
[21:53] <rohan> can someone please confirm this bug? https://bugs.launchpad.net/bugs/222567
[21:54] <rohan> or is it occurring only for me?
[21:55] <crimsun> I don't have that symptom here, but I doubt I'm in your environment
[21:55] <crimsun> (for starters, I use the -server kernel)
[21:56] <rohan> crimsun: ok, can you give me any more hints? should i provide more info?
[21:56] <jaredbuck> i've had a few problems with apt-get hanging when i install certain packages.
[21:56] <crimsun> you can use strace, oprofile, and/or systemtap to help debug.
[21:56] <rohan> crimsun: could you guide me through the process, please?
[21:57] <crimsun> rohan: sorry, I'm pretty busy ATM
[21:57] <rohan> crimsun: ok, i'll try to catch you some time later when you're not :)
[21:58] <rohan> or maybe if you could post the instructions on that bug report, it'd be great
[21:58] <crimsun> please don't block on me - there are pretty decent tutorials online
[21:58] <rohan> ok, i'll try to search there
[22:00] <pjoul> rohan: start here -> Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs
[22:00] <jaredbuck> I helped with a couple of bugs yesterday, offered some suggestions for people to try for problems they were having :)
[22:01] <rohan> jaredbuck: are you having the same problem as me? this happens everytime i use aptitude or apt
[22:01] <rohan> and not just "install", some other operations too
[22:02] <jaredbuck> rohan: i had a couple problems with packages i installed yesterday, i don't remember which ones, but i used adept and synaptic for install, on a few of those it hung when it processed some stuff, i had to use dpkg to finish installing packages.
[22:05] <rohan> oh, then your problem is different from mine
[22:05] <jaredbuck> i guess so. but your problem is still perhaps a bug that can be fixed.
[22:11] * jaredbuck needs a bigger hard drive; 120 GB ain't enough these days.
[22:12] <rohan> let's hope so :-s
[22:13] <Tscheesy> Hi.. i try to connect for 5-a-day and get a sshkey error : http://pastebin.kubuntu-de.org/52
[22:14] <jaredbuck> I'm interested in joining the documentation team, i'll attend their session later this week. for now I'm a junior bug quasher :-p
[22:15] <rohan> crimsun: one last question - do you think "apt" is the right package to file the bug against?
=== seb128_ is now known as seb128
[22:20] <Tscheesy> yes-ehm about the error above - i'm.. stuck. i tried with a second key in LP - same message.
=== wolfger_ is now known as wolfger
[22:59] <chvn> http://pastebin.com/m1cfe084 ---> why is it impossible to get hardy online to this router, its a belkin (BG and N ...), in 7.10 it works like a dream but in hardy its impossible to get online, all other networks ive tried sofare works perfekt..
=== chvn is now known as e\spen
[23:03] <es\epen> ??