Ubuntu
linux package

  1. Vivid (15.04)
  2. Bug #1338706
  3. Comment #26

Comment 26 for bug 1338706

Revision history for this message
LPNow (lpnow) wrote :

It would really be great if Canonical, or the developers could contact Samsung, if anyone knows how?

I wonder if Samsung is even aware of this situation, or if they really care. I'd hate to think we're going to have to sit around and wait on this, because this has been going in their SSDs already over a year, what's to say this is ever going to get fixed, unless we get some Developmental Clout out there sending them word?

PLEASE Canonical I IMPLORE you KINDLY to reach out to Samsung over this?

It would also be great if someone can reply to this post here and let us know too?

THANK YOU! :)