[04:08] <dx> sup #ubuntu-bugs! the trusty/utopic versions of the 'bitlbee' package are very broken https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/1315550
[04:08] <dx> both were copied directly from debian testing while the debian testing version was broken
[04:09] <dx> and a fixed version was only uploaded in time for the jessie freeze, but not in time for the utopic freeze
[04:10] <dx> i'd like to do a SRU but the process looks scary
[07:57] <dx> aghh this is confusing
[07:57] <dx> >Check that the bug is fixed in the current development release, and that its bug task is "Fix Released". It is, in general, not appropriate to release bug fixes for stable systems without first testing them in the current development branch
[07:58] <dx> the SRU page says that, so i changed the status of the ticket to fix released (didn't know i could do that)... and apparently that counts as closing the ticket?
[07:58] <dx> it's fixed in vivid, not in trusty or utopic
[09:49] <mozzarella> guys help
[09:57] <dkessel> !ask | mozzarella
[09:58] <mozzarella> I found a bug and I'd like to fix it, however I need help, where should I ask?
[10:01] <dkessel> mozzarella: you need help in fixing the bug, or in getting the fix into ubuntu?
[10:06] <mozzarella> dkessel: fixing teh bug
[10:14] <brainwash> please mark bug 1386410 as critical
[10:14] <dkessel> mozzarella: you could contact the program's author and ask them for help
[10:17] <rbasak> brainwash: that's a security bug, and the CVE tracker is already showing it as assigned
[10:17] <rbasak> Marking every security bug as Critical doesn't help the security team
[10:17] <rbasak> Better to let them triage it.
[10:18] <brainwash> but it does not hurt either, does it?
[10:18] <mozzarella> dkessel: I don't know which package the bug is from
[10:18] <rbasak> Yes, it does, IMHO. It hides the really Critical bugs (from the POV of the security team) from them.
[10:20] <dkessel> mozzarella: do you know which program is affected by your bug?
[10:21] <mozzarella> dkessel: no
[10:21] <mozzarella> it's part of the desktop, not a program
[10:21] <mozzarella> well…
[10:21] <mozzarella> it's hard to say
[10:21] <dkessel> mozzarella: this may help you to understand the process of fixing a bug in ubuntu: http://packaging.ubuntu.com/html/fixing-a-bug.html
[10:22] <brainwash> rbasak: but this one is really really critical ;)
[10:46] <cristian_c> hello
[10:46] <cristian_c> about this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222763
[10:47] <cristian_c> What have I to do? What's the next step?
[11:11] <mozzarella> dkessel: I don't know if it's a bug inside the program or just a missing icon
[23:56] <somebody> Good night. I am getting an annoying crash while attempting to install 14.10 from a freshly made USB stick. According to Apport, the command on which it crashes is "noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity". I have reported it on Launchpad, but I am also looking for a way to cirumvent this bug and install the system. Any com
[23:56] <somebody> According to bug #1296410, this is specific to installs attempted from a USB dongle created with the help of a Startup USB Creator.
[23:56] <somebody> Can I bypass this problem by getting a live image of 14.10 onto a USB stick by a different program?
[23:58] <somebody> (This thing is marked as "Fix Released", yet my install aborts with a crash.)