[13:53] <codeadi> I am troubleshooting this launchpad bug #1245150 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245150 which is related to bluetooth being disabled in system settings.. The summary is that this is a problem in upstream linux kernel... The last known mainline kernel which works is v3.9 series and the problem starts with v3.10 onwards... I have found that bug #60824 on Kernel Bug Tracker is similar to my problem: https://bugzilla.kernel.org/show_
[13:53] <codeadi> bug.cgi?id=60824 There is a patch provided in comment #6 which has solved the issue for others... I would like some help with applying this patch and would appreciate some hand-holding with this one...
[13:53] <ubot2> Launchpad bug 1245150 in linux (Ubuntu) "0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work after upgrading to Saucy" [Medium,Incomplete]
[13:53] <ubot2> Launchpad bug 60824 in Evolution "the calendar export feature should have a menu item" [Wishlist,New] https://launchpad.net/bugs/60824
[16:13] <smola> could someone triage this? https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1059722 <-- it's a long standing bug (+1 year) in Ubuntu Precise that only requires a re-build of the package
[16:13] <ubot2> Launchpad bug 1059722 in proftpd-dfsg (Ubuntu) "Oct 1 16:38:53 summerborn proftpd[8631]: mod_sftp/0.9.8: compiled using OpenSSL version 'OpenSSL 1.0.0e 6 Sep 2011' headers, but linked to OpenSSL version 'OpenSSL 1.0.1 14 Mar 2012' library" [Undecided,Confirmed]
[16:22] <rbasak> smola: so is it verified fixed in Trusty?
[16:34] <smola> rbasak: I have no access to a machine with Trusty, but that's probably unrelated: there's no need for a backport, just a re-build
[16:42] <smola> rbasak: these proftpd modules require a rebuild everything openssl is updated in the system, latest proftpd build on precise is 21 Nov 2011, since then openssl has been updated many times from 1.0.0e-1 (the one that proftpd was compiled against) up to 1.0.1-4ubuntu5.10
[16:42] <smola> everytime*
[16:43] <smola> so the warning messages are just about not being compiled against the current version (1.0.1-4ubuntu5.10)
[17:03] <rbasak> smola: I don't know what to do about triaging the bug since the main bug status is about the bug status in the current development version.
[17:04] <rbasak> smola: for the problem in Precise, is there an actual problem, or is it just a warning? Are you familiar with https://wiki.ubuntu.com/StableReleaseUpdates? For an update to Precise, there needs to be a test case and a consideration of regression risk.
[17:05] <TheLordOfTime> rbasak: oh good you're here, mind if I pick your brain?
[17:05] <rbasak> (for a rebuild we basically do a no-change update, which will trigger a rebuild)
[17:05] <rbasak> TheLordOfTime: go ahead
[17:05] <rbasak> TheLordOfTime: or maybe in #ubuntu-devel or #ubuntu-server as appropriate?
[17:05] <TheLordOfTime> rbasak: might be better if I pick your brain elsewhere, don't want to flood -bugs with security fix stuff, but meh
[17:05] <rbasak> Right :)
[17:06] <TheLordOfTime> rbasak: -server or -hardened might be more appropriate but either way :)
[17:06] <rbasak> I'm in both :)
[17:47] <smola> rbasak: right, it definitely does not met the criteria for an update
[17:47] <smola> it's just a warning about a possible source of troubles, but no actual problem surfaced so far
[17:56] <rbasak> smola: in that case we just need to verify that it's fixed in Trusty and then explain and mark Fix Released.
[18:32] <smola> rbasak: actually, it's probably better marked as WONTFIX; because openssl will always be updated in stable releases, leading to the same warning over and over
[18:34] <smola> or patched to show the warning only if x.x.x part of the version differs