[15:44] <mnaumann> hi, could someone take a quick look at https://bugs.launchpad.net/bugs/1104435 and tell me what needs to happen there next?
[15:44] <ubot2> Ubuntu bug 1104435 in xfce4-session (Ubuntu) "xfce4-session crashed with SIGSEGV in g_slice_alloc()" [High,Triaged]
[15:48]  * penguin42 reads
[15:48] <mnaumann> it's in state "triaged" and there is a patch which has been approved (using launchpad to mark it as such) by 6 people, and a couple more who just commented that it works well for them
[15:49] <mnaumann> patch + fixed package to be precise.
[15:51] <mnaumann> thanks for checking it penguin42, so what do you say?
[15:52] <penguin42> looking at the upstream bug it looks like there was a fix put in by the xfce guys - so is that fix in the latest ubuntu version in saucy?
[15:53] <penguin42> hmm no, the saucy version is the same as raring
[15:55] <bdmurray> I'd ask a patch pilot in #ubuntu-devel to review the patch and upload it to saucy
[15:56] <mnaumann> upstream 4.10.1 fixes it, but saucy still has 4.10.0
[16:00] <penguin42> bdmurray: I've just added a comment to the patch; the upstream bug talks about pushing two fixes, although I don't see the 2nd fix attached to the upstream bug
[16:03] <mnaumann> i probably have a somewhat subjective view here, but am wondering why a bug like this, which is importance high, has many duplicates and somewhat high karma, and seems ot be rather easy to fix, remains unhandled for weeks. is this something which happens more often, or is this bug just not as relevant as i (subjective view) seem to think it is?
[16:05] <mnaumann> i'm just trying to get a better idea of how serious this bug is, and to be able to tell how it relates to other bugs, something i hardly have a measure for (and would not know how to get a measure for).
[16:05] <mnaumann> by "relate" i mean in terms of (non-) urgency.
[16:06] <penguin42> mnaumann: there are lots of bugs, lots of bugs with patches even
[16:08] <penguin42> mnaumann: I guess some people would have looked at it and seen Ricardo had done that patch - and thought they would leave it to him to push it to a patch pilot, but it's quite difficult sometimes
[16:08] <penguin42> mnaumann: if none of them in -devel respond for a while try pinging one of them by name that are listed in the topic
[16:10] <mnaumann> okay, thank you
[16:10] <mnaumann> i'm just looking at https://bugs.launchpad.net/ubuntu/+patches?orderby=-importance so I see what you mean. is there also a way to sort by karma?
[16:10] <bdmurray> also have all the comments on the merge-proposal is a bit odd
[16:11] <bdmurray> if you look at http://reqorts.qa.ubuntu.com/reports/sponsoring/ you'll see there are very few with that many comments
[16:12] <mnaumann> well i asked all the people who commented to test and, if they can, approve the patch, thinking it would speed things up.
[16:12] <bdmurray> and developers looking at that report may have thought one of those approvers was handling it
[16:13] <mnaumann> hmm, i don't think anyone explicitly stated they would, though.
[16:13] <bdmurray> right but if you just scan the sponsoring report you may not click through to that thing because of it
[16:14] <bdmurray> anyway, the usual practice is for developers to comment on merge proposal and testers to comment on bugs
[16:15] <mnaumann> so asking people to test + approve was actually counter productive.
[16:15]  * penguin42 wonders why upstream isn't marked as fixed - perhaps he only does that when released
[16:16] <mnaumann> well it's released, i assume they forgot (and was wondering, too).
[16:17] <mnaumann> actually no, not released, just tagged
[16:17] <bdmurray> mnaumann: well, it may have been counter productive.  I'm just speculating.
[16:18] <mnaumann> i appreciate your speculations.
[16:21] <penguin42> mnaumann: It probably would have been easier as well if the ppa said that it was just taking an upstream fix - that's more obviously a good thing
[16:27] <mnaumann> i guess i would need to work within bug traige workflows on a daily basis to understand those things in sufficient detail to be actually of any use in speeding things up. which, like most others with a general idea of bug triage but none specific to ubuntu workflows, i do not.
[16:34] <penguin42> mnaumann: Yeh my problem is I occasionally come past and try and fix something
[16:36] <mitya57> bdmurray: re unity-mail sru — all sru information is in bug 1181558 (especially created for that purpose)
[16:36] <ubot2> Launchpad bug 1181558 in unity-mail (Ubuntu) "SRU tracking bug for 1.3.3~13.04" [Medium,Triaged] https://launchpad.net/bugs/1181558
[16:37] <mnaumann> well i do appreciate your help, penguin + bd, thank you.
[16:39] <penguin42> mnaumann: No problem
[16:41]  * penguin42 wonders if there are any plans to take pciutils 3.2.0 - it seems to have taken a patch I made for bug 690431
[16:41] <ubot2> Launchpad bug 690431 in pciutils (Ubuntu) "lspci crashed with SIGSEGV in pci_load_name_list() (with invalid parameter to -i)" [Medium,Triaged] https://launchpad.net/bugs/690431
[16:42] <bdmurray> mitya57: its missing the regression potential parts
[16:44] <mitya57> bdmurray: added
[17:20] <mnaumann> penguin42 + bdmurray: I wrote up this SRU request, it feels far from perfect, can you comment on it? https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1104435
[17:20] <ubot2> Ubuntu bug 1104435 in xfce4-session (Ubuntu Raring) "xfce4-session crashed with SIGSEGV in g_slice_alloc()" [Undecided,New]
[17:23] <bdmurray> I thought there was some mention of it appearing high on errors.ubuntu.com.  If that is the case it is worth noting in the test case perhaps as people could watch for the new version on the error bucket for that crash.
[17:30] <mnaumann> hmm, i also feel i came across such a comment, but can't seem to find it now. i'm still looking, though.
[17:31] <bdmurray> maybe its on the merge proposal
[17:37] <penguin42> it does seem to be hard to get stuff applied; I've got a bunch of small fixes I've tried to report up through debian, quite hard going
[18:03] <mnaumann> can't seem to find it, giving up.
[19:24] <shankstaBytes> is there a way i can report bugs in ubuntu?
[19:24] <Pici> !bugs
[19:24] <ubot2> If you find a bug in Ubuntu or any of its derivatives, please file a bug using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[19:25] <shankstaBytes> god that seems complicated
[19:26] <Pici> How exactly could it be simpler?
[19:26] <shankstaBytes> it is like a 20 page document for a person like me that just wants to let some one know about a reproducable bug
[19:26] <penguin42> shankstaBytes: Nah, it's just make sure you have a launchpad account (so we can come back and ask you questions) and run ubuntu-bug   then the package that the problem relates to
[19:27] <penguin42> shankstaBytes: All the rest of that doc tells you what to do when you don't know which package it is
[19:27] <shankstaBytes> i can't click on the application with ubuntu-bug -w
[19:28] <shankstaBytes> the application is missing from the tray
[19:30] <shankstaBytes> sorry i am just annoyed by this
[19:30] <shankstaBytes> i want to let some one know about this bug though
[19:31] <penguin42> shankstaBytes: OK, so what's the app?
[19:31] <shankstaBytes> I believe it is bluetooth package
[19:32] <shankstaBytes> the bluetooth system tray icon is gone
[19:32] <shankstaBytes> after waking up from sleep
[19:33] <penguin42> ok, I don't know much about bluetooth, do any of the other bluetooth tools fail as well - any command line ones?
[19:34] <shankstaBytes> penguin42: it works if i reboot it is only after i put my laptop to sleep
[19:35] <shankstaBytes> i can manually turn it back on
[19:35] <penguin42> shankstaBytes: OK, to me that sounds like a kernel problem, but difficult to tell without some command line stuff to look at bluetooth (and I don't know bluetooth) - I'd run   ubuntu-bug linux
[19:36] <shankstaBytes> its so funky
[19:36] <shankstaBytes> i have a key that disables all radio
[19:37] <shankstaBytes> i hit that key and i can turn it on and off
[19:37] <shankstaBytes> i hit it and my wifi tray icon disappeared and never came back
[19:37] <penguin42> nod
[19:37] <shankstaBytes> bluetooth i got it to come back after some sigterms and what not
[19:37] <penguin42> this stuff varies hopelessly between machines and how broken their hardware/bios/etc is
[19:39] <shankstaBytes> alright man thanks i guess ill have to look into this when i have more time
[19:39] <shankstaBytes> it would be awesome if I could fix some of this stuff myself, but i just dont have time
[19:39] <shankstaBytes> how do these open source devs do it if they dont get paid
[19:41] <penguin42> well many do get paid by various companies
[19:41] <penguin42> others do it because they also have that type of problem
[19:46] <TheLordOfTime> i know it's a security bug, but can someone with access approve the nominations for Precise, Quantal, and Raring, on https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1182586
[19:46] <ubot2> Ubuntu bug 1182586 in nginx (Ubuntu) "CVE-2013-2070: nginx proxy_pass buffer overflow vulnerability" [Medium,New]
[19:46] <TheLordOfTime> (Saucy's not affected but the others need to be updated)
[20:20] <melodie> hi
[20:23]  * TheLordOfTime waves
[20:25] <melodie> hello TheLordOfTime