Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#994392: blender: Color management settings missing
106 views
Skip to first unread message
Mikko Rasa
Sep 15, 2021, 8:50:03 AM9/15/21
to
Package: blender
Version: 2.93.4+dfsg-1
Severity: normal
Blender 2.93.4 is missing most options in color management settings. I only
have "sRGB" for display device, "Standard" for view transform, "None" for look
and "sRGB" and "Linear" for sequencer. A build downloaded from blender.org
shows all of the options, so it seems Debian's build is incorrectly configured
somehow.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.11.10-k8 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages blender depends on:
ii blender-data 2.93.4+dfsg-1
ii fonts-dejavu 2.37-2
ii libavcodec58 7:4.4-5+b1
ii libavdevice58 7:4.4-5+b1
ii libavformat58 7:4.4-5+b1
ii libavutil56 7:4.4-5+b1
ii libboost-locale1.74.0 1.74.0-9
ii libc6 2.32-2
ii libembree3-3 3.13.1+dfsg-1
ii libfftw3-double3 3.3.8-2
ii libfreetype6 2.10.4+dfsg-1
ii libgcc-s1 11.2.0-4
ii libgl1 1.3.2-1
ii libglew2.1 2.1.0-4+b1
ii libgomp1 11.2.0-4
ii libilmbase25 2.5.7-1
ii libjack-jackd2-0 [libjack-0.125] 1.9.19~dfsg-2
ii libjemalloc2 5.2.1-3
ii libjpeg62-turbo 1:2.0.6-4
ii libopenal1 1:1.19.1-2
ii libopenexr25 2.5.7-1
ii libopenimageio2.2 2.2.17.0+dfsg-2
ii libopenjp2-7 2.4.0-3
ii libopenvdb8.1 8.1.0-1
ii libosdcpu3.4.4 3.4.4-2
ii libpcre3 2:8.39-13
ii libpng16-16 1.6.37-3
ii libpugixml1v5 1.11.4-1
ii libpulse0 15.0+dfsg1-2
ii libpython3.9 3.9.7-2
ii libsdl2-2.0-0 2.0.16+dfsg1-4
ii libsndfile1 1.0.31-2
ii libspnav0 0.2.3-1+b2
ii libstdc++6 11.2.0-4
ii libswscale5 7:4.4-5+b1
ii libtbb2 2020.3-1
ii libtiff5 4.3.0-2
ii libx11-6 2:1.7.2-1
ii libxfixes3 1:5.0.3-2
ii libxi6 2:1.7.10-1
ii libxml2 2.9.12+dfsg-3
ii libxrender1 1:0.9.10-1
ii libxxf86vm1 1:1.1.4-1+b2
ii zlib1g 1:1.2.11.dfsg-2
blender recommends no packages.
blender suggests no packages.
-- no debconf information
Version: 2.93.4+dfsg-1
Severity: normal
Blender 2.93.4 is missing most options in color management settings. I only
have "sRGB" for display device, "Standard" for view transform, "None" for look
and "sRGB" and "Linear" for sequencer. A build downloaded from blender.org
shows all of the options, so it seems Debian's build is incorrectly configured
somehow.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.11.10-k8 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages blender depends on:
ii blender-data 2.93.4+dfsg-1
ii fonts-dejavu 2.37-2
ii libavcodec58 7:4.4-5+b1
ii libavdevice58 7:4.4-5+b1
ii libavformat58 7:4.4-5+b1
ii libavutil56 7:4.4-5+b1
ii libboost-locale1.74.0 1.74.0-9
ii libc6 2.32-2
ii libembree3-3 3.13.1+dfsg-1
ii libfftw3-double3 3.3.8-2
ii libfreetype6 2.10.4+dfsg-1
ii libgcc-s1 11.2.0-4
ii libgl1 1.3.2-1
ii libglew2.1 2.1.0-4+b1
ii libgomp1 11.2.0-4
ii libilmbase25 2.5.7-1
ii libjack-jackd2-0 [libjack-0.125] 1.9.19~dfsg-2
ii libjemalloc2 5.2.1-3
ii libjpeg62-turbo 1:2.0.6-4
ii libopenal1 1:1.19.1-2
ii libopenexr25 2.5.7-1
ii libopenimageio2.2 2.2.17.0+dfsg-2
ii libopenjp2-7 2.4.0-3
ii libopenvdb8.1 8.1.0-1
ii libosdcpu3.4.4 3.4.4-2
ii libpcre3 2:8.39-13
ii libpng16-16 1.6.37-3
ii libpugixml1v5 1.11.4-1
ii libpulse0 15.0+dfsg1-2
ii libpython3.9 3.9.7-2
ii libsdl2-2.0-0 2.0.16+dfsg1-4
ii libsndfile1 1.0.31-2
ii libspnav0 0.2.3-1+b2
ii libstdc++6 11.2.0-4
ii libswscale5 7:4.4-5+b1
ii libtbb2 2020.3-1
ii libtiff5 4.3.0-2
ii libx11-6 2:1.7.2-1
ii libxfixes3 1:5.0.3-2
ii libxi6 2:1.7.10-1
ii libxml2 2.9.12+dfsg-3
ii libxrender1 1:0.9.10-1
ii libxxf86vm1 1:1.1.4-1+b2
ii zlib1g 1:1.2.11.dfsg-2
blender recommends no packages.
blender suggests no packages.
-- no debconf information
Matteo F. Vescovi
Sep 15, 2021, 5:30:03 PM9/15/21
to
Hi Mikko!
On 2021-09-15 at 15:24 (+03), Mikko Rasa wrote:
> Blender 2.93.4 is missing most options in color management settings.
> I only have "sRGB" for display device, "Standard" for view transform,
> "None" for look and "sRGB" and "Linear" for sequencer.
> A build downloaded from blender.org shows all of the options, so it
> seems Debian's build is incorrectly configured somehow.
Digging in the build logs[1] you'll find something like:
= = = = >8 = = = =
-- Could NOT find OpenColorIO: Found unsuitable version "1.1.1", but
-- required is at least "2.0.0"
-- (found /usr/lib/libOpenColorIO.so;/usr/lib/x86_64-linux-gnu/libexpat.so)
-- OpenColorIO not found
= = = = >8 = = = =
OpenColorIO is still at 1.1.1 in Debian, in fact. And OCIO library is
responsible for color management in Blender, as you can see at [2].
Now, even if I've tried to spend some time on packaging the 2.x.y version
actually I'm still failing badly due to external requests (that is, more
libraries or tools not packaged in Debian yet) for the package to build.
Hope this helps to understand the problem.
Cheers.
mfv
[1] https://buildd.debian.org/status/fetch.php?pkg=blender&arch=amd64&ver=2.93.4%2Bdfsg-1&stamp=1630968330&raw=0
[2] https://docs.blender.org/manual/en/latest/render/color_management.html
--
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
On 2021-09-15 at 15:24 (+03), Mikko Rasa wrote:
> Blender 2.93.4 is missing most options in color management settings.
> I only have "sRGB" for display device, "Standard" for view transform,
> "None" for look and "sRGB" and "Linear" for sequencer.
> A build downloaded from blender.org shows all of the options, so it
> seems Debian's build is incorrectly configured somehow.
= = = = >8 = = = =
-- Could NOT find OpenColorIO: Found unsuitable version "1.1.1", but
-- required is at least "2.0.0"
-- (found /usr/lib/libOpenColorIO.so;/usr/lib/x86_64-linux-gnu/libexpat.so)
-- OpenColorIO not found
= = = = >8 = = = =
OpenColorIO is still at 1.1.1 in Debian, in fact. And OCIO library is
responsible for color management in Blender, as you can see at [2].
Now, even if I've tried to spend some time on packaging the 2.x.y version
actually I'm still failing badly due to external requests (that is, more
libraries or tools not packaged in Debian yet) for the package to build.
Hope this helps to understand the problem.
Cheers.
mfv
[1] https://buildd.debian.org/status/fetch.php?pkg=blender&arch=amd64&ver=2.93.4%2Bdfsg-1&stamp=1630968330&raw=0
[2] https://docs.blender.org/manual/en/latest/render/color_management.html
--
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
Marios Sioutis
Sep 20, 2021, 10:10:02 PM9/20/21
to
Hi,
I'm using blender for a scientific simulation project and I'm affected
by this bug too.
As a workaround, I'll try alternative install methods in the meantime.
Looking forward to a quick resolution!
On Wed, 15 Sep 2021 23:19:59 +0200 "Matteo F. Vescovi" <m...@debian.org>
wrote:
I'm using blender for a scientific simulation project and I'm affected
by this bug too.
As a workaround, I'll try alternative install methods in the meantime.
Looking forward to a quick resolution!
On Wed, 15 Sep 2021 23:19:59 +0200 "Matteo F. Vescovi" <m...@debian.org>
wrote:
Andrius Merkys
Oct 6, 2021, 8:10:02 AM10/6/21
to
Hi Matteo,
On 2021-09-16 00:19, Matteo F. Vescovi wrote:
> On 2021-09-15 at 15:24 (+03), Mikko Rasa wrote:
>> Blender 2.93.4 is missing most options in color management settings.
>> I only have "sRGB" for display device, "Standard" for view transform,
>> "None" for look and "sRGB" and "Linear" for sequencer.
>> A build downloaded from blender.org shows all of the options, so it
>> seems Debian's build is incorrectly configured somehow.
> Digging in the build logs[1] you'll find something like:
>
> = = = = >8 = = = =
> -- Could NOT find OpenColorIO: Found unsuitable version "1.1.1", but
> -- required is at least "2.0.0"
> -- (found /usr/lib/libOpenColorIO.so;/usr/lib/x86_64-linux-gnu/libexpat.so)
> -- OpenColorIO not found
> = = = = >8 = = = =
>
> OpenColorIO is still at 1.1.1 in Debian, in fact. And OCIO library is
> responsible for color management in Blender, as you can see at [2].
>
> Now, even if I've tried to spend some time on packaging the 2.x.y version
> actually I'm still failing badly due to external requests (that is, more
> libraries or tools not packaged in Debian yet) for the package to build.
Maybe you could share hare the list of missing dependencies? This way
people could help speeding up the fix.
Best,
Andrius
On 2021-09-16 00:19, Matteo F. Vescovi wrote:
> On 2021-09-15 at 15:24 (+03), Mikko Rasa wrote:
>> Blender 2.93.4 is missing most options in color management settings.
>> I only have "sRGB" for display device, "Standard" for view transform,
>> "None" for look and "sRGB" and "Linear" for sequencer.
>> A build downloaded from blender.org shows all of the options, so it
>> seems Debian's build is incorrectly configured somehow.
> Digging in the build logs[1] you'll find something like:
>
> = = = = >8 = = = =
> -- Could NOT find OpenColorIO: Found unsuitable version "1.1.1", but
> -- required is at least "2.0.0"
> -- (found /usr/lib/libOpenColorIO.so;/usr/lib/x86_64-linux-gnu/libexpat.so)
> -- OpenColorIO not found
> = = = = >8 = = = =
>
> OpenColorIO is still at 1.1.1 in Debian, in fact. And OCIO library is
> responsible for color management in Blender, as you can see at [2].
>
> Now, even if I've tried to spend some time on packaging the 2.x.y version
> actually I'm still failing badly due to external requests (that is, more
> libraries or tools not packaged in Debian yet) for the package to build.
people could help speeding up the fix.
Best,
Andrius
Matteo F. Vescovi
Oct 6, 2021, 3:00:02 PM10/6/21
to
Hi Andrius!
On 2021-10-06 at 14:56 (+03), Andrius Merkys wrote:
> Maybe you could share hare the list of missing dependencies? This way
> people could help speeding up the fix.
Good idea!
I've already worked on pystring (#992013) that is waiting in the NEW
queue at the moment.
More over, press-sphinx-theme is needed and I filed an RFP bug report
for it (#992016).
That's all, for now. But I haven't investigated further, I must admit.
Hope this helps.
Cheers.
On 2021-10-06 at 14:56 (+03), Andrius Merkys wrote:
> Maybe you could share hare the list of missing dependencies? This way
> people could help speeding up the fix.
I've already worked on pystring (#992013) that is waiting in the NEW
queue at the moment.
More over, press-sphinx-theme is needed and I filed an RFP bug report
for it (#992016).
That's all, for now. But I haven't investigated further, I must admit.
Hope this helps.
Cheers.
Andrius Merkys
Oct 7, 2021, 10:50:02 AM10/7/21
to
Hi Matteo,
On 2021-10-06 21:50, Matteo F. Vescovi wrote:
> I've already worked on pystring (#992013) that is waiting in the NEW
> queue at the moment.
> More over, press-sphinx-theme is needed and I filed an RFP bug report
> for it (#992016).
Thanks for sharing your situation. I tried building opencolorio from
salsa and ran into an issue with expat.cmake:
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
The imported target "expat::expat" references the file
"/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
but this file does not exist.
Have you solved it? To me it seems like a bug in expat package.
By the way, building pystring failed for me too until I dropped its
debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
has pystring_1.1.3.orig.tar.gz.
Best,
Andrius
On 2021-10-06 21:50, Matteo F. Vescovi wrote:
> I've already worked on pystring (#992013) that is waiting in the NEW
> queue at the moment.
> More over, press-sphinx-theme is needed and I filed an RFP bug report
> for it (#992016).
salsa and ran into an issue with expat.cmake:
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
The imported target "expat::expat" references the file
"/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
but this file does not exist.
Have you solved it? To me it seems like a bug in expat package.
By the way, building pystring failed for me too until I dropped its
debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
has pystring_1.1.3.orig.tar.gz.
Best,
Andrius
Matteo F. Vescovi
Oct 7, 2021, 5:50:03 PM10/7/21
to
Hi Andrius!
On 2021-10-07 at 17:44 (+03), Andrius Merkys wrote:
[...]
> Thanks for sharing your situation. I tried building opencolorio from
> salsa and ran into an issue with expat.cmake:
>
> CMake Error at
> /usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
> The imported target "expat::expat" references the file
>
> "/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
>
> but this file does not exist.
>
> Have you solved it? To me it seems like a bug in expat package.
Oh. Last time I build-tested OCIO 2.x that error didn't show up.
Something must have changed lately. As you said, there's probably a
problem with expat package. Gotta check.
> By the way, building pystring failed for me too until I dropped its
> debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
> look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
> has pystring_1.1.3.orig.tar.gz.
Right. Fixed with a new commit on salsa. Feel free to pull it.
On 2021-10-07 at 17:44 (+03), Andrius Merkys wrote:
[...]
> Thanks for sharing your situation. I tried building opencolorio from
> salsa and ran into an issue with expat.cmake:
>
> CMake Error at
> /usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
> The imported target "expat::expat" references the file
>
> "/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
>
> but this file does not exist.
>
> Have you solved it? To me it seems like a bug in expat package.
Something must have changed lately. As you said, there's probably a
problem with expat package. Gotta check.
> By the way, building pystring failed for me too until I dropped its
> debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
> look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
> has pystring_1.1.3.orig.tar.gz.
Andrius Merkys
Oct 8, 2021, 2:10:03 AM10/8/21
to
Hi Matteo!
Please note I have submitted bug #995905 to specifically track the
progress of opencolorio v2.* packaging. I suggest continuing our
conversation there - I have set new bug's email address in Reply-To
header for this message.
On 2021-10-08 00:39, Matteo F. Vescovi wrote:
> On 2021-10-07 at 17:44 (+03), Andrius Merkys wrote:
>> Thanks for sharing your situation. I tried building opencolorio from
>> salsa and ran into an issue with expat.cmake:
>>
>> CMake Error at
>> /usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
>> The imported target "expat::expat" references the file
>>
>> "/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
>>
>> but this file does not exist.
>>
>> Have you solved it? To me it seems like a bug in expat package.
>
> Oh. Last time I build-tested OCIO 2.x that error didn't show up.
> Something must have changed lately. As you said, there's probably a
> problem with expat package. Gotta check.
I have submitted #995907 on libexpat1-dev. I managed to get around this
issue by patching
/usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat-noconfig.cmake, but
this has to be fixed in the appropriate package.
>> By the way, building pystring failed for me too until I dropped its
>> debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
>> look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
>> has pystring_1.1.3.orig.tar.gz.
>
> Right. Fixed with a new commit on salsa. Feel free to pull it.
Thanks!
Best wishes,
Andrius
Please note I have submitted bug #995905 to specifically track the
progress of opencolorio v2.* packaging. I suggest continuing our
conversation there - I have set new bug's email address in Reply-To
header for this message.
On 2021-10-08 00:39, Matteo F. Vescovi wrote:
> On 2021-10-07 at 17:44 (+03), Andrius Merkys wrote:
>> Thanks for sharing your situation. I tried building opencolorio from
>> salsa and ran into an issue with expat.cmake:
>>
>> CMake Error at
>> /usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat.cmake:74 (message):
>> The imported target "expat::expat" references the file
>>
>> "/usr/lib/x86_64-linux-gnu/libexpat.so.1.8.1"
>>
>> but this file does not exist.
>>
>> Have you solved it? To me it seems like a bug in expat package.
>
> Oh. Last time I build-tested OCIO 2.x that error didn't show up.
> Something must have changed lately. As you said, there's probably a
> problem with expat package. Gotta check.
issue by patching
/usr/lib/x86_64-linux-gnu/cmake/expat-2.4.1/expat-noconfig.cmake, but
this has to be fixed in the appropriate package.
>> By the way, building pystring failed for me too until I dropped its
>> debian/gbp.conf. It seems that line 'compression = xz' forces gbp to
>> look for pystring_1.1.3.orig.tar.xz in pristine-tar branch, whereas it
>> has pystring_1.1.3.orig.tar.gz.
>
> Right. Fixed with a new commit on salsa. Feel free to pull it.
Best wishes,
Andrius
0 new messages