[00:08] <greg-g> just so I make sure I'm not an idiot: GNOME's bugzilla requires you to be a member of their bug squad to mark bugs as duplicates, right?
[00:09] <pedro_> no necessary a member of the bug squad, but you need to ask for permissions, yes
[00:11] <greg-g> pedro_: k, I asked a bug to marked a duplicate of another in #bugs on irc.gnome, no response all day, so just making sure I wasn't asking for something I could do myself.
[00:11] <pedro_> greg-g: which one?
[00:12] <greg-g> http://bugzilla.gnome.org/show_bug.cgi?id=547090 shoudl be a dupe of http://bugzilla.gnome.org/show_bug.cgi?id=536655
[00:14] <pedro_> greg-g: right, done, thanks you
[00:14] <greg-g> pedro_: thank you.
[00:14] <angusthefuzz> pedro_: thanks for correcting some of my bug triaging recently
[00:15] <pedro_> angusthefuzz: you're welcome, thanks a lot for helping!
[00:15] <angusthefuzz> pedro_: I hope it has not grown annoying to mark duplicates (every time you change something I get a sinking feeling)
[00:18] <Hobbsee> pedro_: got any specs for UDS?
[00:23] <pedro_> Hobbsee: not yet, need to discuss that during these weeks
[00:24] <Hobbsee> pedro_: please discuss quickly, people are trying to schedule stuff, and subscribe to stuff.
[00:25] <pedro_> angusthefuzz: nah, you're doing a great work, keep up doing it, if you have any doubts or not sure about doing something just ping me or just ask in the channel, there's a lot of members of the bugsquad willing to help ;-)
[00:25] <angusthefuzz> pedro_: definitely, just checking to make sure i was still being helpful, thanks for the encouragement
[00:26] <Hobbsee> pedro_: the slower people are at getting the specs up are, the more people who do multiple-tracked stuff get clashes, and it'd be great to avoid that...
[00:35] <stgraber> Sounds like I'll have to work on mine too one of these days :) I need to schedule some ISO testing, testing tracker and maybe a few more QA-related ones + all of my usual LTSP+edu ones
[00:35] <Hobbsee> stgraber: sweet.  Get going :)
[00:35] <Hobbsee> stgraber: do them by thurs? :)
[00:43] <mok0> Bug 68825
[00:43] <mok0> Bug 71053
[00:45] <Hobbsee> yes?
[00:45] <mok0> That last one should be expired
[00:45] <Hobbsee> mok0: why?
[00:45] <greg-g> it is a dupe, yes?
[00:46] <mok0> Because it's a duplicate of one that's fixed, and because we don't support edgy anymore
[00:46] <greg-g> (and marked as such)
[00:46] <greg-g> mok0: it is marked as a duplicate of the other.
[00:46] <Hobbsee> mok0: duplicates don't show on the default stuff anyway.
[00:46] <Hobbsee> mok0: so it doesn't add to the bug count, etc.
[00:47] <mok0> OK, I was checking all bugs associated with ksensors
[00:47] <mok0> ... and it turned up as New which I thought was strange
[00:48] <greg-g> mok0: what list are you looking at? link?
[00:48] <mok0> greg-g: 2 secs
[00:49]  * greg-g nods
[00:49] <mok0> https://bugs.edge.launchpad.net/ubuntu/+source/ksensors/+bugs?search=Search&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed&field.status=Fix+Released&field.status=Invalid&field.status=Won%27t+Fix&field.omit_dupes.used=
[00:51] <mok0> greg-g: It's the link "All bugs every reported" from here: https://bugs.edge.launchpad.net/ubuntu/+source/ksensors
[00:52] <Hobbsee> mok0: well, that does mean "all bugs, including dupes"
[00:52] <hggdh> you have unmarked the omit duplicates in the extended search
[00:52] <mok0> Hobbsee: right, but I would expect it to be "Fix released"
[00:53] <Hobbsee> mok0: nah - the dupes don't automatically get marked like that.
[00:53] <mok0> hggdh: the search is hardwired
[00:53] <greg-g> mok0: the status of a bug which is marked as a duplicate does not change, it would cause unneeded bug mail
[00:53] <Hobbsee> or at least, didn't then.  They may do now.
[00:53] <Hobbsee> greg-g: ++
[00:53]  * greg-g knew that statement would please Hobbsee :)
[00:53] <hggdh> mok0, mine is hardwired to omit duplicates
[00:54] <Hobbsee> greg-g: :P.  I actually have a filter now for most launchpad mail, to a folder called Black Hole.
[00:54] <mok0> hggdh: this is the link "All bugs ever reported" from https://bugs.edge.launchpad.net/ubuntu/+source/ksensors
[00:54] <Hobbsee> greg-g: actually, it bothers me getting mail more now than it used to - when i'd get hundreds in a week, so had no chance of reading them all
[00:54] <hggdh> ah, OK. then yes, dups are not omitted --
[00:55] <mok0> Hobbsee: man procmail
[00:55] <greg-g> mok0: why would you want to look at closed bugs?
[00:55] <Hobbsee> mok0: someone else hosts my email. but yes ;)
[00:55] <Hobbsee> that's what happens
[00:55] <mok0> greg-g: I just checked to see all bugs with ksensors, and the fact that it was "New" confused me
[00:55] <greg-g> mok0: gotcha, I can see how a bug which is a duplicate being still "New" is confusing.
[00:56] <mok0> greg-g: that's it
[00:56] <greg-g> just remember, if it is marked as a duplicate, consider it dead.
[00:56] <mok0> greg-g: got it
[00:56] <greg-g> :)
[00:56] <mok0> Thanks all
[00:57] <hggdh> and it is. There was a discussion about it some time ago, but it did not reach (for me) a good end -- as moko, I would like duplicates to be given a, er, good state -- like invalid
[00:58] <mok0> hggdh: I think that once two bugs are linked via "duplicates" their settings should synchronize
[00:58] <hggdh> or, even better, a status of duplicate
[00:58]  * greg-g nods
[00:58] <hggdh> mok0, they do
[00:58] <greg-g> umm
[00:59] <mok0> hggdh: err? That's the whole point of this discussion
[00:59] <hggdh> the master bug has a list of all duplicates; each duplicate points to the master
[00:59] <hggdh> oh, byr settings you meant status
[01:00] <mok0> bug 68825 bug 41053
[01:00] <greg-g> hggdh: he said a status of "duplicate" instead of "new" "fixed released"etc
[01:00] <mok0> bug 68825 bug 71053
[01:00] <hggdh> +1 from me. And sorry for the confusion
[01:00] <greg-g> :) it tends to get that way sometimes (confusing)
[01:01] <hggdh> well, one can always open a bug against malone on that
[01:01]  * hggdh will ponder about it
[01:02] <mok0> hggdh: I haven't had much luck with bugs reported against malone :-/
[01:02] <mok0> hggdh: they're usually invalidated
[01:02] <hggdh> neither I, neither I... they do grind, but slow and in different ways
[01:03] <mok0> heh
[01:03] <greg-g> hggdh: you wanna see if it has been reported already?
[01:04] <hggdh> looking at it right now, greg-g
[01:05] <angusthefuzz> is there a master bug for the "." to "," switch people are experiencing?
[01:08] <mok0> Nothing quite like it
[01:08] <hggdh> bug 3796
[01:09] <hggdh> so old not even ubotuu can read it
[01:09] <hggdh> https://bugs.edge.launchpad.net/malone/+bug/3796
[01:10] <greg-g> haha, nice
[01:10] <mok0> hggdh: not quite the same
[01:11] <hggdh> mok0, beginning of description
[01:11] <mok0> "Duplicate bugs should inherit the status, importance of "master" bug"
[01:11] <hggdh> Marking a bug as duplicate should change the status to Duplicate, so that the status shows up a listing of bugs.
[01:11] <mok0> hggdh: ok yes
[01:12] <mok0> hggdh: that seems to get lost in the discussion though
[01:12] <hggdh> of course, this is how it started, 3 years ago. Now, tempus fugit... and it is now a different thingy
[01:13] <greg-g> well, it is in there, and they linked to those two bluprints of what Malone should do in the future, which address your concerns
[01:14] <hggdh> :-)
[01:14] <mok0> I guess the triager needs to give Invalid status before marking as a duplicate
[01:14] <hggdh> greg-g, correct tense is "will address", or "woullon address"
[01:14] <hggdh> mok0, I used to do that
[01:15] <greg-g> hggdh: the blueprints actively address the issues :)
[01:15] <mok0> hggdh: but it could happen automatically
[01:15] <greg-g> but what if the bug is not a duplicate, and when you un-dupe it, it should go back to the status it was before (New, Incomplete, whatever)
[01:16] <mok0> Can you "unduplicate" it? I don't see how
[01:16] <hggdh> mok0, yes, just select "mark as a duplicate" and clear the field
[01:17] <greg-g> that issue is referenced i nthat malone bug you linked to
[01:17] <mok0> So would it be relevant to updupe, -> Invalid, -> Dupe ?
[01:17] <hggdh> greg-g, this is not really a critical requirement (but can be done): if you un-dup a bug, you can also reset the status and importance given the new knowledge that led to un-dupping the beast to begin with
[01:18] <mok0> I am talking about bug 71053
[01:18] <greg-g> just to be clear: you want to undupe a bug, then mark it invalid, then redupe it again? no, please don't do that
[01:18] <hggdh> no
[01:18] <mok0> OK, but you can't change the status otherwise
[01:18] <greg-g> that is a lot of unneeded work
[01:18] <greg-g> you don't need to
[01:19] <hggdh> if I want to un-dup a bug it is because I concluded it is not a dup. Based on this new bit of knowledge, I can also reset the status to whatever I think is needed
[01:19] <greg-g> hggdh: true
[01:19] <greg-g> hggdh: it was just something referenced in that malone bug.
[01:21] <mok0> Hmm, well something is fishy, because ubotu says both bugs are "Fix released" but if you go to the bug page, it says "New" for 71053.
[01:22] <mok0> So their statuses are linked somehow
[01:22] <mok0> Just not on the bug page
[01:22] <hggdh> misterious are the ways of Malone
[01:22] <mok0> heh
[01:23] <mok0> Ah, I will file a bug, so let's see what the devs say
[01:24] <greg-g> that must be something in ubottu knowing to look at the master for the status, as this doesn't show anything about the Ubuntu task being "Fix released" https://bugs.edge.launchpad.net/ubuntu/+source/ksensors/+bug/71053/+text
[01:34] <mok0> bug 299283
[01:34] <mok0> (Who gets to file number 300000????)
[01:38] <storrgie> I just filed a bug report, could anyone review it and tell me if I need to make some changes? https://bugs.launchpad.net/ubuntu/+bug/299284
[01:41] <hggdh> storrgie, good. But I think it may be a duplicate... I remember commenting on a nm bug about that
[01:41] <hggdh> storrgie, but the package is wrong...
[01:41] <storrgie> hggdh: I would LOVE to have a link to that, this bug is kicking my rear.... I am sick of dealing with the issue
[01:42] <storrgie> hggdh: I couldnt find the right package
[01:42] <mok0> OK, time for bed, see you later!
[01:43] <hggdh> network-manager?
[01:43] <hggdh> or network-manager-gnome
[01:46] <storrgie> hggdh: how do i change that?
[01:47] <storrgie> hggdh: did you find the similar problem?
[01:48] <storrgie> hggdh: i figured out how to add the package
[01:52] <hggdh> storrgie, no, not yet. Still looking
[01:56] <hggdh> storrgie, bug 277063
[02:01] <hggdh> but since it was closed fix release, I do not know what exactly was fixed
[02:01] <hggdh> (and I had the same problem as you -- my wired connected to my internal LAN, and the wireless to the Internet
[02:02] <storrgie> yea
[02:02] <storrgie> how did you resolve your problem?
[02:05] <storrgie> so fix released
[02:05] <storrgie> but its still a problem in ubuntu?
[02:38] <hggdh> storrgie, I did not yet resolved it -- since then I have been pretty much on the road
[02:38] <hggdh> storrgie, if you are running the fixed version of nm, then your case still stands
[02:38] <hggdh> (and mine)
[02:46] <Elbrus> I just confirm bug 226629. It is a minor issue, but I filed the appropriate bug in the Debian bug tracker. Could somebody mark it triaged and set the severity to minor?
[02:47] <Elbrus> It's minor because the package contains html documentation
[02:49] <hggdh|away> Elbrus, done
[02:49] <hggdh|away> thanks
[02:49]  * hggdh|away goes to bed now
[02:50]  * Hobbsee wonders if PDFs are allowed.
[02:51] <hggdh|away> Hobbsee, huh?
[02:51] <Hobbsee> hggdh|away: i'm not sure if pdf's actually classify as free, as they don't include the source to build them, usually
[02:52] <hggdh|away> hum. Good point. Ah, the fine details of the law :-(
[02:53] <omegamormegil> I've been working on this bug:  https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/299214  I'm trying to learn to triage.  Could someone take a look and let me know if it needs anything else?
[02:53] <hggdh|away> well, the debian folks will certainly (correctly) determine is this is the case
[02:53] <Elbrus> Hobbsee,hggdh|away: I guess the source COULD be included and that the package builds the pdf
[02:54] <Elbrus> right?
[02:54] <mrooney> what determines whether things get installed in /usr/share or /usr/local/share, anyone know? is that a distro thing?
[02:54] <Elbrus> I tried to use unoconv for that, but have not succeeded yet
[02:54] <Hobbsee> mrooney: who installs it, usually.
[02:54] <hggdh|away> mrooney, we do not use /usr/local; it is usually reserved to local admin things
[02:55] <Hobbsee> hggdh|away:++
[02:55] <Elbrus> and hggdh|away: thanks of course
[02:55] <mrooney> okay, thanks Hobbsee and hggdh|away!
[02:56] <Hobbsee> you're welcome :)
[02:56] <hggdh|away> Elbrus, if the source for the PDF is included, then there is no issue (but this is not the same as reverse-eng it)
[03:01] <jmarsden> mrooney: For the full details on what files should go where, see Debian Policy 9.1.1 http://www.debian.org/doc/debian-policy/ch-opersys.html#s-fhs and the FHS itself http://www.pathname.com/fhs/
[03:05] <Elbrus> hggdh|away: right... I am the maintainer of a package which includes pdf documentation made from an Open_office file. Unfortunately, I cannot get the pdf to be created during package build.
[03:05] <Elbrus> (The source is included in the package source thou.)
[03:06] <hggdh|away> Elbrus, then (I guess) this is enough: you could even pre-prepare the PDF for the package (adding it as a binary), and it would still be good
[03:07] <hggdh|away> 'cause the source is there
[03:07] <Elbrus> Thats what I do at the moment...
[03:08] <hggdh|away> but I would defer to Hobbsee on this: I am not overly familiar with the Ubuntu/Debian policies for this
[03:08]  * Hobbsee defers to persia, also being uncertain.
[03:09] <hggdh|away> and a graph is born...
[03:11] <persia> pitti tends to demand that PDFs are built from source.
[03:28] <mtholdenss> in 8.10 when switching tabs in firefox, sometimes the title bar disappears or goes white
[03:41] <Hobbsee> !dvd
[04:15] <Elbrus> persia: in general, how to build pdf from source? I guess that depends on the source right. I could not get unoconv to convert my Ooo file to pdf
[04:15] <persia> Elbrus, Indeed, it depends on the source.  I have no idea how to do it from an OO.o file.
[04:15] <Elbrus> pity...
[04:48] <Elbrus> I am looking at bug 293955. having installation fail because "dpkg: error processing fp-units-gfx (--configure): package fp-units-gfx is already installed and configured". Could that be caused by the package itself, or is this something of dpkg?
[06:22] <dholbach> good morning
[07:19] <persia> Ryan52, https://wiki.ubuntu.com/BugSquad is probably the best place to start.
[07:20] <persia> Ryan52, https://wiki.ubuntu.com/UbuntuBugControl has requirements for bug-control, but you'll want to have excelled in bugsquad first.
[07:22] <Ryan52> what if I just want to be able to mess with the bugs in packages I maintain in Debian? do I really have to go through this process?
[07:27] <Ryan52> it seems like kind of a pain considering the fact that I don't even use ubuntu, and don't really want to (directly) contribute to ubuntu. i just want to be able to take care of and manage the bugs in "my" packages.
[07:27] <persia> No.
[07:27] <persia> If you're a Debian Developer, there's a shortcut.
[07:27] <Ryan52> I am not.
[07:27] <persia> bdmurray, Can you help Ryan52 ?
[07:29] <persia> But you maintain packages in Debian, and have a history of bug management for those packages in Debian?
[07:30] <Ryan52> yes, maintain (very new to it), but have not yet done any bug management.
[07:30] <Ryan52> other than closing bugs through a changelog entry.
[07:30] <persia> Oh.  You might need to have some history before you can be approved.
[07:30] <persia> Well, that counts.
[07:30] <persia> In the meantime, if you'd like to suggest importance for bugs, just ask here, and someone will probably adjust it.
[07:31] <Ryan52> okay.
[07:43] <Ryan52> oh, would that mean that if I did get "approved" I would get all the ubuntu bugs in my email?
[07:44] <wgrant> No.
[07:44] <Ryan52> oh, ok, good.
[07:45] <Ryan52> thanks for answering all of my seemingly stupid questions! :)
[08:01] <persia> Ryan52, That's the purpose of this channel :)
[08:29] <mr-russ> what does the following error mean when attempting to add a "Also affects distribution/package"
[08:29] <mr-russ> This bug is already on Debian. Please specify an affected package in which the bug has not yet been reported.
[08:33] <persia> mr-russ, For which bug?
[08:34] <mr-russ> bug #286851
[08:34] <mr-russ> I might be trying to do the wrong thing :)
[08:34] <mr-russ> maybe I should refile this bug as 3 bugs.
[08:35] <persia> Yeah.
[08:35] <persia> If you want to track 3 Debian bugs, you want 3 launchpad bugs.
[08:36] <mr-russ> how best do I complete that move?
[08:37] <mr-russ> I know I can just create 3 and mark this as invalid, but how will people be notified it's now 3 bugs?
[08:38] <persia> Hrm.  I'd recommend seeking advice from the security team for that.
[08:39] <mr-russ> Do I just email them?
[08:39] <persia> In this case, where there is a DSA, and a bug, it's probably sensible to have just one Ubuntu bug for the USN, even though that breaks tracking with Debian bugs.
[08:39] <persia> But I'm not on the security team, so I may be mistaken.
[08:39] <mr-russ> I much newer at this than you :)
[09:52] <danage> asac: re bug 286859 - i have it running now. i have no way to testing jerones patch, but i have manually done all the configuration for my 3g card now and it definately needs to be talked to on ttyUSB2 instead of ttyUSB0
[10:04] <danage> asac: gotta go. i updated the bug comments as to reflect my findings. i think this bug relates to others that can't set the APN or PIN (i found about 4-5 that weren't marked as duplicates on launchpad)
[10:19] <gnomefreak> anyone have the firefox/hotmail bug # for the master bug or one that has been marked aas a dupe of master bug?
[10:20]  * gnomefreak been looking for a while since i loged one this morning
[10:20] <gnomefreak> win 10
[15:08] <bddebian> Boo
[18:38] <krychek> hi, could anyone look at bug 225251 ?
[18:38] <krychek> "tracking bug"
[18:39] <chrisccoulson> thats a nonsense bug
[18:39] <chrisccoulson> there is a usability tag for tracking usability related bugs
[18:39] <chrisccoulson> we don't need a 'tracking' bug for those
[18:40] <krychek> thats what im saying
[18:40] <chrisccoulson> i'd be tempted to just close it and leave a comment explaining why
[18:40] <krychek> will you close it now?
[18:40] <krychek> sure.. why not?
[18:41] <chrisccoulson> you can close it if you like
[18:41] <krychek> ok
[18:41] <chrisccoulson> make sure you explain why though
[18:42] <krychek> sure
[18:42] <chrisccoulson> you could point them to here: https://edge.launchpad.net/ubuntu/+bugs?field.tag=usability
[18:46] <krychek> closed
[18:46] <chrisccoulson> thanks
[18:47] <krychek> i have another one: bug 231508
[18:48] <chrisccoulson> you should ask them to provide a screenshot if you can't reproduce it
[18:50] <krychek> I and l are almost the same in many cases, also in windows
[18:51] <krychek> but i dont remember ever having a problem reading because of this
[18:57] <persia> krychek, I've had lots of complaints when telling people to run `lintian -iIv`
[18:57] <persia> On the other hand, I'm not sure that's a fixable bug, as some people like it that way, especially for sans-serif.
[19:09] <krychek> high importance, long time incomplete, feisty bugs can be closed?
[19:17] <persia> krychek, Best to see if you can determine if they are fixed, but there's a good chance, especially if there's not enough information to even get an idea of the problem.
[22:01] <bucket529> Added a patch for bug 73954. Could someone take a look and tell me if it makes sense?
[22:24] <bdmurray> bucket529: what do you mean by makes sense?
[22:32] <hggdh> bucket529, looks correct
[22:33] <hggdh> bdmurray, he would like to know if it is what upstream Evolution would like to receive
[22:33] <hggdh> bucket529, did you build (i.e. checked it is actually working)?
[22:34] <bdmurray> hggdh: okay
[22:36] <hggdh> bucket529, I see you submitted it upstream already -- thanks (but the question still remains: did you test it?)
[22:36] <bdmurray> hggdh: there is an upstream comment that says yes
[22:38] <hggdh> indeed... I only looked at the last entry <shame/>
[22:39] <hggdh> asking for approval and commit -- we will have a new release of evo stable in about one week, might make into it
[23:07] <askand> Can someoone with the right privlegies set an importance on  bug 3235? forum threads about it: http://ubuntuforums.org/showthread.php?t=985918 and http://ubuntuforums.org/showthread.php?p=6036030
[23:10] <chrisccoulson> there's a duplicate of that one somewhere
[23:10] <chrisccoulson> you might like to search for it
[23:12] <chrisccoulson> and that bug isn't filed against nautilus in the Ubuntu project, but instead against the Nautilus project. That's normally used for adding links to the upstream bug tracker
[23:15] <askand> chrisccoulson: do you mean bug 10435?
[23:16] <chrisccoulson> no, the bug you linked to only has an upstream task
[23:16] <chrisccoulson> it doesn't have an ubuntu task
[23:17] <askand> chrisccoulson: yes but did you mean the second bug I linked was a dublicate of the first?
[23:17] <askand> or should I create a new one?
[23:17] <chrisccoulson> this bug has been discussed upstream, and it basically isn't going to happen. The problem is that Nautilus only currently supports a per-user Templates directory, and doesn't support a system-wide Templates directly. To implement your suggestion, Nautilus would need to support a system-wide Templates directory, and upstream have already said that they won;t implement it
[23:18] <askand> chrisccoulson: Ok, I see.. then the best thing to do is perhaps either inform the users what that folder is in a good way or hide it so it wont confuse them
[23:20] <chrisccoulson> the per-user Templates folder exists to allow users to add templates. Unfortunately, for distributions to ship a common-set of templates files, Nautilus needs to support a system-wide Templates folder (otherwise you'd have to create a copy of the templates files for each user profile)
[23:20] <chrisccoulson> i'm trying to find the upstream discussion for you
[23:21] <askand> chrisccoulson: thanks, persia hade an idea about creating a blueprint for a structure by which there can be system installed templates in Nautilus , and file bugs against packages that have document formats to have them provide templates to this system location, linked to the blueprint.
[23:22] <chrisccoulson> yeah, that's the problem though. Nautilus doesn't support system-installed templates. It only installs user installed templates
[23:22] <askand> chrisccoulson: oh sorry now I understand
[23:24] <askand> chrisccoulson: I have to go to work now but if you like, if you find the upstreamdiscussion, it would be nice if you post the link in the discussionthread in the forums http://ubuntuforums.org/showthread.php?t=985918
[23:24] <chrisccoulson> i'll try and do that
[23:45] <alex-weej> every now and again i see chipcardd4 using some nontrivial amount of CPU
[23:45] <alex-weej> wtf is it?
[23:46] <angusthefuzz> alex-weej: its for a flashcard reader, see bug 277412
[23:49] <alex-weej> angusthefuzz: thanks.
[23:49] <alex-weej> and it's gone :)
[23:50] <bdmurray> Since the Ubuntu bug is linked to a debian bug and that debian bug is Fixed the ubuntu bug should be confirmed or triaged.