[01:38]  * greg-g still keeps forgeting to set some bugs to "Triaged" after he sends them upstream.
[01:52] <greg-g> Does launchpad know if more than one LP Bug has been linked to a single upstream bug? (ie: a way to make sure there aren't duplicate bugs both pointing to the upstream bug)
[01:52]  * greg-g asks in #launchpad
[02:26] <pochu> greg-g: there's one:
[02:26] <pochu> (04:42:41 PM) pedro_: what we are going to do is : go to https://bugs.launchpad.net/bugs/bugtrackers/gnome-bugs/#bugnumber
[02:27] <pochu> (04:42:53 PM) pedro_: and replace #bugnumber for the bug number of the upstream one
[02:27] <pochu> (change gnome-bugs to the upstream bug tracker you want)
[02:30] <greg-g> pochu: interesting, So the functionality is there to have a 'check if already linked' feature or something.  It probably wouldn't be that useful, actually, as I heard that LP warns you already if there is already a link to the remote bug.
[02:36] <greg-g> would bug 263656 be a Tomboy issue or a window manager issue?
[02:38] <charlie-tca> I'm going to suggest it is not Tomboy specific because Geany does this also
[02:39] <greg-g> charlie-tca: yeah, definitely not tomboy specific, but I'm not sure where the fix would be applied.
[02:39] <charlie-tca> I don't know, just thought it might be helpful information
[02:40] <maco> see now, they're reporting a bug opposite one i saw yesterday
[02:40] <geeter> it's not a wm issue.
[02:40] <maco> because yesterday someone filed a bug because firefox summons you to its desktop when you open a link
[02:40] <geeter> it's yet another case of "conflicting user expectations"
[02:40] <maco> that person thinks the app shouldn't take over
[02:40] <maco> this one thinks it should
[02:40] <geeter> yeah, maco and I just discussed that
[02:40] <maco> -_- crimsun why are you using an odd name?
[02:40] <greg-g> maco: that isn't it exactly
[02:41] <greg-g> more, if I click on a note that is already opened on desktop 1 and I'm on desktop 3 it should move from 1 to 3.
[02:41] <greg-g> but yeah, similar situation
[02:41] <geeter> this bug is arguing that the app should migrate a child window to the focused desktop
[02:41] <maco> should it move the note or move you?
[02:42] <greg-g> they want it to move the note
[02:42] <greg-g> not sure what "should" happen :)
[02:42] <maco> and currently it moves you?
[02:42] <geeter> it currently does neither
[02:42] <greg-g> currently it just makes it blink in the task bar
[02:42] <geeter> it updates the child windows on the "other" desktop
[02:42] <geeter> thus, it is not a wm issue but an app issue
[02:43] <greg-g> you stay on 3, it is on 1, but it is blinking in taskbar, you click on that blinky and you are taken to desktop 1
[02:43] <charlie-tca> My two cents, it becomes painful when you have the app open in two windows, and have to go look where it opened the
[02:43] <charlie-tca> nesxt item
[02:44] <greg-g> geeter: ok, so the bug is staying assigned to tomboy.  I'll forward upstream with a caveat that the "correct" behavior is up to debate
[02:44] <greg-g> thanks maco / geeter / charlie-tca for the input
[02:44] <geeter> (np)
[02:45] <charlie-tca> :)
[02:45] <greg-g> go team! ;)
[03:25] <crimsun_> it would be great if 5-A-Day were to honour additional bzr command options (e.g., --local)
[03:25] <crimsun_> `commit --local' would be dandy right about now...
[03:27] <greg-g> crimsun_: +1
[03:28] <greg-g> ok, 11 bugs and I'm done for tonight
[03:28] <greg-g> helped Tomboy out a lot, honestly due to the fact that one of the devs has been a great responder upstream
[03:29]  * wgrant got some of your bugmail.
[03:29] <greg-g> crimsun_: 110 bugs today????
[03:30] <greg-g> wgrant: sorry about that :)
[03:30] <wgrant> greg-g: Terrible.
[03:30] <maco> can someone mark bug 272540 a wishlist?
[03:31] <greg-g> maco: done
[03:31] <maco> greg-g: thanks
[03:31] <wgrant> That should probably be against update-manager.
[03:32] <greg-g> wgrant: yeah, that would be obvious time to tell the user
[03:32] <maco> greg-g: i think he did 240 yesterday...
[03:32] <wgrant> Only the dist-upgrader would need to do that, as we don't remove things post-release.
[03:32] <greg-g> wgrant: wanna comment on the bug your thoughts?
[03:32] <greg-g> I don't want to steal your words ;)
[03:33] <greg-g> maco: that is CRAZY!
[03:33] <maco> and i also have to say +1 on --local as i'm sitting right next to crimsun_ in Cosi where they don't allow anything but 80 and 443, and they do deep-packet inspection so you can't tunnel anything over them either :(
[03:33] <wgrant> greg-g: Please steal my words, I can't start Firefox right now... building this security update is making my HDD angry.
[03:33] <greg-g> wgrant: will do.
[03:33] <wgrant> maco: One can't deep-packet-inspect HTTPS.
[03:33] <maco> greg-g: i dont usually do over 80 in a day.  if i decide to stop and try to write a patch for one of the ones i see that's bitesize, i'll only do about 30
[03:34] <maco> wgrant: hrm maybe we can try that then....
[03:34]  * wgrant used to be a super-person like maco and crimsun, but then uni and security stuff took over.
[03:34] <wgrant> maco: I regularly tunnel SSH through restrictive HTTPS proxies.
[03:34] <maco> i have this awful habit of going "hmm....homework...or bugwork...bugwork."
[03:35] <wgrant> maco: Unfortunately that doesn't always make for excellent marks.
[03:35] <maco> i was supposed to be studying for midterms when i decided to work on gsynaptics and get my first patch. i was supposed to be working on finals and final projects when i spent a weekend poking at seahorse.
[03:35] <maco> yeah, that's a problem
[03:36]  * wgrant will hopefully murder gsynaptics for Jaunty.
[03:36] <greg-g> that is when I had my highest 5-a-day stats, during finals last year :)
[03:36] <maco> wgrant: why?
[03:36] <wgrant> maco: It can be replaced by gnome-mouse-properties in the default install, since we have XInput properties.
[03:36] <maco> wgrant: i have a patch in the works for it to do 2-finger-scroll (like on a mac)
[03:36] <maco> oh
[03:36] <maco> ok
[03:37] <wgrant> maco: That option can be added to the default installation with about 4 lines of code, if you want.
[03:37] <maco> er...oh wait, no...i wasnt careful checking out a "trunk" and overwrote it
[03:37] <maco> oh i wasnt the one that wanted it. one of my friends, when i mentioned having added speed/accel to it, asked for 2-finger-scroll
[03:38] <maco> i know synclient can do it
[03:38] <greg-g> well, time for a movie, later all, have a pleasent night/day
[03:38] <maco> night night
[03:38] <wgrant> synclient can hopefully go away soon, too. We can change lots of settings without needing the awfulness of SHMConfig. <3 XInput properties.
[03:38] <maco> yay!
[03:38] <maco> no more shared memory craziness?
[03:39] <maco> i was hoping there was a way to get rid of that
[03:39] <maco> hey guys, mozilla decided against the EULA thing, right?
[03:40] <wgrant> maco: Yes, sort of.
[03:40] <wgrant> My bug is now the 4th most commented on LP, so it's not surprising.
[03:40] <maco> sort of?
[03:40] <wgrant> We still have to have something, but it's not quite as bad.
[03:40] <maco> what do we have to have?
[03:40] <wgrant> Examples were attached to the bug overnight.
[03:40] <maco> bug 272647
[03:40] <wgrant> Not that one.
[03:40] <wgrant> Ah.
[03:40] <wgrant> I see.
[03:41] <maco> that's why i'm wondering
[03:41] <wgrant> Bug #269656
[03:41] <wgrant> Watch out, it's huge.
[03:41] <maco> lol @ summary
[03:43] <wgrant> I got quite some hatemail for that :(
[10:03] <mcas> hello
[10:04] <mcas> i have a problem with a bug
[10:04] <mcas> bug 272586
[10:05] <mcas> the bug is confirmed under hardy but it seems to be solved under intrepid
[10:05] <mcas> how should i handle this?
[10:05] <Hobbsee> mcas: mark it as fix released, with a comment along those lines?
[10:06] <mcas> ok that was my first idea, too
[10:14] <madsrh> Hi. Where do I file a bug about the GDM log-in?
[10:38] <umangme> Bug #272683 should be "Wishlist"
[11:17] <Arby> morning all, I got an e-mail saying my membership of bug-control has expired
[11:18] <Arby> who do I need to speak to for it to be renewed?
[11:25] <thekorn> Arby, you need to get in contact with one of the administrators
[11:26] <thekorn> https://edge.launchpad.net/~ubuntu-bugcontrol/+members
[11:26] <Arby> thekorn: thanks
[13:24] <murdok> hello! how can I debug eog?
[13:24] <murdok> I have tried with export DEB_BUILD_OPTIONS but I don't have any aditional information
[13:29] <pochu> murdok: what's the problem? a crash?
[13:29] <murdok> yes
[13:30] <pochu> then install the eog-dbg package and get a backtrace with gdb
[13:30] <pochu> !backtrace
[13:30] <murdok> good idea :þ
[14:04] <murdok> Could someone please mark bug #270335 as wishlist?
[14:07] <thekorn> murdok, it has an upstream task and no one in ubuntu, so only pitti can change the importance
[14:08] <murdok> oh, okay thanks
[16:25] <lfaraone> Hey, are bugs with ACPI (in this case, fans) kernel bugs?
[16:25] <_Zeus_> umm, i guess?
[16:25] <_Zeus_> why??
[16:26] <lfaraone> _Zeus_: I'm trying to FindRightPackage for a user who is unable to use their fan (ACPI spouts an error0
[16:28] <_Zeus_> ohh
[16:28] <_Zeus_> have they tried acpitool?
[16:30] <lfaraone> _Zeus_: not afaict.
[16:30] <lfaraone> _Zeus_: bug 272537
[16:30] <_Zeus_> gotcha
[16:32] <_Zeus_> check it out
[16:32] <_Zeus_> what i said might fix it
[16:34] <pochu> hmm, nautilus is consuming 524MB here (after a week running)
[16:35] <_Zeus_> whoa
[16:36] <_Zeus_> just kill it and restart?
[16:36] <_Zeus_> it must have a memory leak
[16:36] <pochu> yeah, I'm looking at bugzilla to see if there's any reported
[16:37] <nhandler> If a bug gets fixed upstream, what should the status of the bug be set to? Fix Committed?
[16:38] <pochu> the desktop team does that, but others don't, so I guess it depends...
[16:38] <pochu> nhandler: what's the package?
[16:38] <nhandler> pochu: The bug you patched upstream in emesene
[16:38] <pochu> heh
[16:39] <_Zeus_> nhandler: if the fix isn't out yet, then yes
[16:39] <_Zeus_> if it's out, then fix released
[16:39] <pochu> well, it's an Ubuntu task
[16:39] <greg-g> pochu: yeah, which is why I was "corrected" by someone once when I set it to fix committed even though I KNEW I was following someone paid by Canonical's lead ;)
[16:39] <nhandler> _Zeus_: It is only out in the upstream SVN, not in Ubuntu
[16:39] <_Zeus_> anyone?
[16:39] <_Zeus_> not sure
[16:39] <pochu> greg-g: yeah, it's happened to me too :)
[16:40] <pochu> nhandler: either fix committed or triaged
[16:41] <nhandler> pochu: I thought triaged meant that a bug had enough information for a dev to start fixing it. Fix Committed seems more logical to me
[16:41] <_Zeus_> normal users can't set triaged, i thin
[16:41] <greg-g> pochu: do you know if there is a desire to reconcile the difference?
[16:41] <nhandler> _Zeus_: I'm Bug Control, so I can
[16:41] <_Zeus_> ahh
[16:41] <_Zeus_> so you can
[16:45] <pochu> nhandler: true that
[16:45] <pochu> nhandler: so fix committed. also https://wiki.ubuntu.com/Bugs/Status says fix committed is appropriate
[16:46] <pochu> greg-g: I don't really know
[16:46] <pochu> hmm
[16:46] <pochu> nope, fix committed doesn't look appropriate
[16:47] <pochu> bah, just use it and be done :)
[16:47] <pochu> also I'm the maintainer, and I promise not to revert your change ;-)
[16:49] <nhandler> pochu: I changed it to Fix Committed.
[16:50] <nhandler> pochu: This is why I feel that they should add more Statuses on Launchpad. That would make things a lot clearer. maybe a Fixed Upstream status ;)
[16:51] <pochu> nhandler: they want to remove statuses, not add them, though :P
[16:51] <pochu> they want to remove 'confirmed' in favour of a 'me too!' button
[16:52] <pochu> or something like that
[16:52] <nhandler> pochu: I know. persia and I have had long discussions about this ;)
[16:53] <persia> Please *don't* set the status of bugs against Ubuntu to "Fix Committed" when they are fixed upstream.  This hides them from display, and doesn't set the Fixed Upstream flag.
[16:54] <pochu> err, fix committed bugs aren't shown by default??
[16:54] <persia> Better is to set an upstream task.  Use "Fix Committed" for the upstream task when it goes into upstream's VCS, and "Fix Released" for the upstream task when it goes into an upstream release tarball.
[16:54] <persia> pochu: Nope.
[16:54] <pochu> I thought that was just for invalid, wontfix and fix released
[16:54] <greg-g> I tohught they were
[16:54] <persia> And Fix Committed.
[16:54] <pochu> https://edge.launchpad.net/ubuntu/+source/emesene/+bugs shows one fix committed bug
[16:54] <persia> Unless something changed and I didn't notice.
[16:54] <nhandler> persia: But you can only add a bug watch if there is an upstream bug
[16:55]  * persia looks at the specific bug to try to understand
[16:55] <greg-g> it shows fix committed by default
[16:55] <greg-g> https://bugs.edge.launchpad.net/ubuntu/+source/network-manager
[16:55] <persia> That's different (and good).
[16:55] <persia> nhandler: Which bug?
[16:56]  * nhandler goes to find it
[16:56] <nhandler> persia: https://bugs.edge.launchpad.net/ubuntu/+source/emesene/+bug/246817
[16:57] <greg-g> a bug could be marked as "Fix Released" for the upstream task and still only Triaged for the Ubuntu task, and that would be logical
[16:57] <nhandler> greg-g: But you can not create an upstream task without an upstream bug
[16:58] <persia> nhandler: How is this not an upstream bug that was fixed?
[16:58] <greg-g> aye, then make a comment with the pertinant info (revision number with the fix, changelog).  As it isn't in Ubuntu yet, it probably should be "fix committed"
[16:58] <persia> "Fixed upstream in the stable and trunk branches" is a fairly clear indicator.
[16:59] <greg-g> an upstream bug without an upstream bug report
[16:59] <persia> You can create an upstream bug without an upstream bug report.
[16:59]  * persia does so now
[16:59] <greg-g> oh righ!
[16:59] <greg-g> t
[16:59] <nhandler> persia: I forgot that you can manually change the status of an upstream bug watch if you do not specify a bug number
[17:00] <greg-g> I never do that, so I forget that you dont need a link
[17:00] <greg-g> well done persia  ;)
[17:00] <persia> It's important to have the status correct for each project.
[17:00]  * greg-g nods
[17:00] <persia> The current status shows it fixed upstream, and still needing a fix in Ubuntu.
[17:00] <persia> If we push the fix for intrepid, nifty.  If not, we'll get it for free when we pull a new upstream.
[17:01] <persia> This also puts it in the "Fixed Upstream" reports, which people look at for several different reasons, and so it's likely to keep getting triaged properly.
[17:01] <nhandler> persia: Shouldn't it be Fix Committed for upstream. It has only been fixed in the svn.
[17:02] <persia> nhandler: Indeed :)  Please fix.  That's entirely a mistake in understanding on my part.
[17:02] <persia> Might set the Importance whilst you're at it.
[17:02] <nhandler> persia: Fixed ;)
[17:02] <persia> Thank you.  Sorry to have gotten it wrong.
[17:03] <nhandler> I can't set the importance for the upstream bug. I think pochu might be able to though
[17:03] <nhandler> Bug Control can only change the importance for bugs in Ubuntu packages
[17:03] <persia> pochu: Is it worth applying the debdiff for intrepid, and dropping when jaunty opens?
[17:03] <nhandler> persia: My debdiff won't work (as stated in the LP bug)
[17:04] <pochu> persia: it would have to patch all the translations, then rebuild all the .mo files, so I don't think so
[17:04] <persia> pochu: Makes sense.
[17:04] <nhandler> pochu: Can you change the importance for the upstream bug watch?
[17:04] <pochu> already done :)
[17:04] <persia> nhandler: True, but if pochu had said "Sounds like a good idea: please proceed" then you could prepare a new debdiff.
[17:05] <greg-g> now that bug looks better
[17:05] <nhandler> persia: I know. I just wanted to make sure you were aware (so you didn't go and upload it as-is).
[17:05] <persia> Yep.  We just have to let it age for two or three months, and it should be ready to close :)
[17:06] <persia> nhandler: It's too late here for me to be sponsoring, and I don't typically do that based on traffic in this channel anyway.  I was more seeking information towards progressing the bug :)
[17:06] <nhandler> persia: That is good to hear. But, like the saying goes, "Better safe than sorry".
[17:07] <nhandler> Alright, now that we have this triaging task figured out, I am going to go and get some work done.
[17:07] <persia> Anyway, for those lurking: it's only good practice to create an untracked upstream bug (as we've just done) when it's already known fixed upstream, but not filed.  This helps Ubuntu tracking, and doesn't tend to annoy upstream too much (as opposed to opening bugs already fixed upstream just for tracking purposes).
[17:08] <persia> Yep.  Always good to be safe :)
[17:08] <pochu> I wonder why you can create upstream tasks without bug watches if the upstream project is configured not to use launchpad bug tracker
[17:08] <persia> pochu: For just the case I outlined in the previous overview statement.
[17:08] <pochu> It sounds like a bug/bad design in Launchpad
[17:09] <persia> You think it'd be better to force upstream to track the issue in their bug tracker directly?
[17:09] <pochu> oh
[17:09] <pochu> nope
[17:09] <pochu> I think it would be better to have a good status which showed what's happening
[17:09] <persia> If the dream of having all bugtrackers everywhere interface and feed bugs to each other ever happens, it would make sense to not support this, but as long as this hasn't happened, it helps this use case.
[17:10] <pochu> but if I set the upstream project not to use malone, it shouldn't use it
[17:10] <persia> Yeah, well, status is hard.  Status is *especially* hard when trying to use the same bugtracker for both distros and projects.
[17:10] <pochu> so why is there a check box to use malone or not if it doesn't really disable it?
[17:11] <pochu> persia: ack, but it sounds like bad design. I disabled malone, yet people can report bugs...
[17:11] <persia> pochu: That's just useless UI, as far as I can tell.
[17:12] <persia> Mind you, it might provide a useful hint to users, that filing bugs in Malone against that project won't necessarily get upstream attention.
[17:12] <persia> Personally, I'd rather drop the UI than enforce it, as otherwise we can't accurately represent the state of bugs like this one.
[17:13] <persia> We could add extra status values like "Committed Upstream" and "Fixed Upstream", but those are only meaningful for distros, and there's only three or four distros that use LP for bug tracking (as opposed to a much larger number of projects)
[17:14] <pochu> right
[21:59] <crimsun> ugh, bug 86683 is nasty.  Tagging it for myself.
[22:00] <crimsun> note: it has been reproducible since edgy.