[00:06] <darthanubis> Bug #237801
[00:07] <afflux> just checked, the behaviour of gtk_file_chooser_get_filename indeed changed. In hardy it returned the full path, now only the filename. Not sure if that was intended though, as some examples in gtk docs still rely on the old behaviour.
[04:32] <bdmurray> persia: I said "working on" in the mail I believe
[04:32] <bdmurray> I'll make it clearer in the wiki though page though
[10:38] <afflux> morning
[10:39] <afflux> oh I hate it. SRU-testing bugday and I'm going to leave for vacation exactly on that day. :(
[10:51] <thekorn> good morning afflux, vacation without internet access sounds like a bad plan ;)
[10:51] <afflux> hehe
[10:52] <afflux> bicycle trekking tour :P
[10:52]  * afflux does not own a laptop (yet?)
[10:52] <afflux> morning by the way
[10:54] <thekorn> wow, did you already plan a route?
[10:56] <afflux> yup, going to follow the Main from the spring onwards. We're softies, we don't like hills :P
[10:58] <thekorn> super, have a lot of fun!
[10:58] <afflux> thanks ;)
[10:59] <thekorn> but anyway, you can start sru-verifications right now, no need to wait until tuesday :)
[10:59] <afflux> sounds like a good idea
[11:01] <afflux> does bug 242079 qualify for "high"?
[11:01] <thekorn> unfortunatly not all of the listed bugs have TESTCASEs (yet?)
[11:10] <thekorn> afflux, "high" makes sense to me, if it was unintentional and it might have impact on other apps
[11:12] <afflux> okay, thanks
[11:20] <persia> bdmurray: You did indeed cache it with an appropriate number of qualifiers, but I'm not sure how well that translates for some people.  Thanks for the wiki clarification :)
[12:13] <afflux> thekorn: are you familiar with the SRU bugday? (how exactly) Should I remark negative testing on the wikipage?
[12:22] <thekorn> afflux, I've no idea, and I dont think there is any procedure for this set, because this is the very first SRU bugday, so I suggest
[12:23] <thekorn> adding a comment like "-1, see commt #xxx of the bugreport"
[12:23] <afflux> okay, will do that, thanks
[12:24] <thekorn> to the tester column would be great
[12:37] <persia> afflux: If you test an SRU candidate and find a negative effect, please also put it in the bug report.
[12:37] <afflux> did that, of course ;)
[13:05] <_gunni_> How can i accelerate, as user, that a bug gets fixed upstream thats 3 month old, and fix is easy and in bug report?
[13:26] <persia> _gunni_: You can play developer for a day.  Which bug?
[13:26] <_gunni_> https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/204624
[13:33] <Hobbsee> bdmurray: is there any chance the hug day mail stuff can go on it's own list?
[13:34] <Hobbsee> bdmurray: i'm getting bored of receiving many, many copies about it each time
[13:34] <Hobbsee> (kubuntu-devel, ubuntu-motu or ubuntu-bugs, ubuntu-devel or -discuss (or both), and u-d-a)
[13:35] <Hobbsee> and i get the feeling i'm not alone on this, particularly after there was a mail referencing the duplication.
[13:35] <persia> _gunni_: Looks like a kernel bug.  You might find https://wiki.ubuntu.com/KernelMaintenance https://wiki.ubuntu.com/KernelMaintenanceStarter and https://wiki.ubuntu.com/KernelTeam/Contacts good links to explain who to contact, and how to prepare the patch for inclusion.
[13:35] <persia> Hobbsee: Does your mail client not collapse mail with the same Message-ID?
[13:36] <Hobbsee> persia: not if it's all gone into folders first, no.
[13:36] <Hobbsee> oh, i only get 4 copies of it now.
[13:36] <Hobbsee> so it's been slightly de-duplicated.
[13:37] <persia> Hobbsee: Ah.  I believe in collapse before foldering, but then I don't folder before reading.
[13:37] <Hobbsee> persia: i use folder-based addressing, so don't have that luxury :(
[13:37] <Hobbsee> ie, kubuntu.ubuntu-devel@hobbsee.com and such.
[13:38] <persia> Maybe it's worth filing a bug in your mail client that it should mark a given Message-ID as read globally whenever it is read?
[13:38] <persia> (this would of course be wishlist, and likely need upstream input, but...)
[13:39] <persia> I think it's a misfeature that it doesn't track that, as it forces you to read things twice, even in the simple case of mail being sent to you and a list for broken reply-to-all + nonfiltering listserv.
[13:49] <_gunni_> persia: I will have a look at the links you gave me
[13:50] <persia> _gunni_: Good luck.  If you can be the developer to fix this bug, you've a good chance of getting it done.  If not, you ought at least be able to get in touch with the right people to make sure the bug gets attention.
[13:50] <persia> One thing that makes that specific bug a little tricky is that the patch is inline, rather than being an attachment, so it doesn't show up in searches for patches.
[13:51] <_gunni_> Thats because i do not know if the patch is in correct format. And is the first "patch" i ever made :)
[13:52] <persia> _gunni_: Makes sense, and is reasonable caution.  Perhaps the links will help with that.  (I'm not a kernel person, so I'm not exactly sure what is required).
[13:53] <_gunni_> For me it looks like only one line needs the change from "strncpy" to "lib_strncpy" ... seems quite simple
[13:54] <persia> It might well be simple, it just needs the right people to review, test, and confirm.
[13:57] <persia> There's almost 50,000 open bugs.  Of those, about 1500 are known to be fixed somewhere, and another thousand or so have known good patches.  The issue is mostly getting the already solved ones identified so they can be uploaded to the repositories.
[13:58] <persia> Of course, there's the 45,000 bugs that aren't so well understood, which have different issues, but at least for bugs like yours.
[14:15] <_gunni_> persia: From the links and FAQ inside, i get a bit afraid of contacting one of the mentioned people ...
[14:25] <persia> _gunni_: Hmm.  Maybe something there (or on a related page) has suggetions about things that can be done with the bug to make it appear in default searches by the team?
[14:26] <_gunni_> I will have a deeper look
[17:06] <Nightrose> techno_freak: why are you changing amarok bugs from incomplete to invaid?
[17:07] <Nightrose> we set them to incomplete because the reporter might still provide more information
[17:07] <Nightrose> and if they don't it will expire
[17:07] <Nightrose> no harm done
[17:07] <Nightrose> but marking a bug as invalid is something the reporter will not like
[21:28] <jibel> bug #155668 is a small issue in kdebase specific to kubuntu. Do I file it under kdebase or is there something to indicates that this is only related to kubuntu ?
[21:31] <yuriy> jibel: kdebase
[21:32] <yuriy> if something is *not* specific to kubuntu, then you should file it against the right package, then also file it on bugs.kde.org, and add an upstream link with "Also affects project..."
[21:33] <jibel> got it. thanks.
[21:34] <yuriy> jibel: though that bug may actually be in kubuntu-default-settings
[21:36] <yuriy> jibel: where is this theme.rc?
[21:39] <jibel> yuriy: you're right that's kubuntu-default-settings
[21:41] <jibel> I was not aware of this package.
[21:44] <jibel> the culprit is in this package under ubuntu/artwork/ksplash/
[22:42] <Susana> hi, what is the correct launchpad project for the ubuntu.com website?
[22:43] <Pici> Susana: ubuntu-website
[22:44] <greg-g> link for ease: https://launchpad.net/ubuntu-website
[22:45] <Susana> thanks :)