<div dir="ltr"><div class="gmail_extra"><div>On Mon, Feb 15, 2016 at 5:52 PM, Takashi Sakamoto <span dir="ltr"><<a href="mailto:o-takashi@sakamocchi.jp" target="_blank">o-takashi@sakamocchi.jp</a>></span> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Why did you add additional comments to the fixed-released bug? It's not within my intension to mention about the bug. I think your behaviour is unwelcome to developers. You should have used button of 'This bug affects you' or something similar...<br></blockquote><div><br></div><div>I'm not sure what the point of your lecture was/is. But thank you for initially pointing me to the bug-report where my "inappropriate" comments got this bug correctly resolved. Furthermore, hopefully this means people updating to 16.04LTS in the near future will still have use of their Envy24 sound cards. The end result is that the problem was acknowledged, a new build was done, and the issue was resolved. </div><div><br></div><div>See <a href="https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/16">https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/16</a></div><div><a href="https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/17">https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/17</a><br></div><div><a href="https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/18">https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/18</a><br></div><div><a href="https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/19">https://bugs.launchpad.net/ubuntu/xenial/+source/mudita24/+bug/1534647/comments/19</a><br></div><div><br></div><div>Specifically, I can now confirm working ICE1712 cards, and associated mudita24(1) application, on</div>4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC (*).<br><br>Working Audio:<br>card 0: DMX6Fire [TerraTec DMX6Fire], device 0: ICE1712 multi [ICE1712 multi]<br> Subdevices: 1/1<br> Subdevice #0: subdevice #0</div><div class="gmail_quote"><div class="gmail_quote">card 3: M66 [M Audio Delta 66], device 0: ICE1712 multi [ICE1712 multi]</div><div class="gmail_quote"> Subdevices: 1/1</div><div class="gmail_quote"> Subdevice #0: subdevice #0</div><div>Working Midi:<br></div></div><div class="gmail_quote"> 16:0 TerraTec DMX6Fire MIDI-Front DMX6fire 0<br> 16:32 TerraTec DMX6Fire Wavetable DMX6fire 0<br><br>(*): 4.4.0-6.21 kernel retrieved and manually installed onto Ubuntu 14.04LTS Skylake-based system:<br><a href="https://launchpad.net/ubuntu/xenial/amd64/linux-headers-4.4.0-6/4.4.0-6.21">https://launchpad.net/ubuntu/xenial/amd64/linux-headers-4.4.0-6/4.4.0-6.21</a><br><a href="https://launchpad.net/ubuntu/xenial/amd64/linux-headers-4.4.0-6-generic/4.4.0-6.21">https://launchpad.net/ubuntu/xenial/amd64/linux-headers-4.4.0-6-generic/4.4.0-6.21</a><br><a href="https://launchpad.net/ubuntu/xenial/amd64/linux-image-4.4.0-6-generic/4.4.0-6.21">https://launchpad.net/ubuntu/xenial/amd64/linux-image-4.4.0-6-generic/4.4.0-6.21</a><br><a href="https://launchpad.net/ubuntu/xenial/amd64/linux-image-extra-4.4.0-6-generic/4.4.0-6.21">https://launchpad.net/ubuntu/xenial/amd64/linux-image-extra-4.4.0-6-generic/4.4.0-6.21</a><br><div> </div><div>........</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Well, if you improve something you use, it's better to follow each rules of development.<br>
<br>
In your case, at first, you should watch release schedule of Ubuntu 16.04.<br>
<a href="https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule</a><br>
<br>
You can see date of KernelFreeze is Apr. 7th 2016. In my opinion, till then, what you're expected is:<br>
- Read wiki page about Ubuntu kernel development cycle and understand it<br>
- <a href="https://wiki.ubuntu.com/Kernel" rel="noreferrer" target="_blank">https://wiki.ubuntu.com/Kernel</a><br>
- Test with daily build image<br>
- <a href="http://cdimages.ubuntu.com/daily-live/current/" rel="noreferrer" target="_blank">http://cdimages.ubuntu.com/daily-live/current/</a><br>
- When you still find your bug, seek it in <a href="http://launchpad.net" rel="noreferrer" target="_blank">launchpad.net</a><br>
- <a href="https://launchpad.net/bugs" rel="noreferrer" target="_blank">https://launchpad.net/bugs</a><br>
- When you find similar bug, watch it by subscibing or something like it.<br>
- When you cannot find similar bugs, register it as new one.<br>
- but you should keep more days to investigate duplicated bug<br>
<br>
At least, additional comments without enough consideration seems not to be helpful to yourself, against your expectation. And you should not test with packages in PPA. PPA is just Private Package Archive. The packages in PPA do not always go for official release.<br>
<br>
Although I said some lectures, I wish this bug will be fixed in Ubuntu 16.04 release.<br></blockquote><div><br></div><div>Instead of wishing, I'd rather make things happen and get things fixed.</div><div><br></div><div>--Niels.</div><div><a href="http://www.nielsmayer.com">http://www.nielsmayer.com</a></div></div></div></div>