← Back to team overview

ubuntustudio-bugs team mailing list archive

[Bug 1826180] Reminder of SRU verification policy change

 

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to blender in Ubuntu.
Matching subscriptions: ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/1826180

Title:
  [SRU] blender: erases photoshop files

Status in blender package in Ubuntu:
  Fix Released
Status in blender source package in Bionic:
  Fix Committed
Status in blender source package in Cosmic:
  Fix Released
Status in blender source package in Disco:
  Fix Released
Status in blender source package in Eoan:
  Fix Released

Bug description:
  [Warning]
  * Since this bug is about a data loss, BE CAREFUL in your testing!
  [Impact]

  When simply accessing a folder that contains a Photoshop file, at
  least in thumbnail mode, as well as trying to open the file for
  viewing or using it as a texture, Blender turn the file in a ZERO kB
  file, essentially deleting it.  This can affect directly users who
  haven't been keeping their original file on the working folder with
  the catastrophic scenario where they'll lose the original file.

  The proposed fix should be backported to Ubuntu 18.04, 18.10 and 19.04
  as all of them are affected by this dangerous issue.

  This bug is caused by a Debian-specific patch.

  [Test Case]

   * Open Blender
   * Go to file browser (maybe change it to thumbnails)
   * Access a folder that contains a photoshop file
   * All photoshop files on that folder will be zeroed out and
     it's unrecoverable, nor there is any message.

  [Regression Potential]

  No regression should manifest as a result for this change.

  [Other Info]
  https://developer.blender.org/T63045
  I posted this on the main ubuntu bug tracker but I have an impression they will tell me it's ubuntu mate's problem... so here is a copy of the bug at https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1822196

  This was posted on Blender bug https://developer.blender.org/T63045
  It was determined that it doesn't happen with the official downloadable release, only with the one installed through the Ubuntu. Here is the report as filed:

  System Information
  Operating system: Ubuntu mate, both 18.10 and 18.04.2 64 bits, Ryzen 7 2700x
  Graphics card: Radeon fury nano

  Blender Version: 2.79.b+dfsg0-1 from distro

  Short description of error
  When I simply access a folder that contains a photoshop file in thumbnail mode, as well as trying to open the file for viewing or using it as a texture, Blender turn the file in a ZERO kb file, essentially deleting it. Luckily I haven't been keeping my original file on the working folder but at one point this will be catastrophic and I'll lose an original file.

  Exact steps for others to reproduce the error
  Simply open Blender, go to file browser, change it to thumbnails, and access a folder on systems like mine that contains a photoshop file. This doesn't seem to happen on windows. All photoshop files on that folder will be zeroed out and it's unrecoverable, nor there is any message.

  I have tested this on many photoshop files (not intentionally, I
  always just forget that there's this huge bug and to make sure any
  folder I'm viewing doesn't have a photoshop file). All of them became
  zero kb and I had to find the source to recover.

  I'm not sure why I haven't seen people complaining about it but this
  is pretty major.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1826180/+subscriptions


References