[Bug 2031495] New: Blender not working properly with wayland with
nvidia
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2031495
Bug ID: 2031495
Summary: Blender not working properly with wayland with nvidia
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: blender
Severity: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: paul.woegerer(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When running Blender on Fedora 35 with Wayland with nvidia drivers from RPM
Fusion the dropdown windows are not showing up reliably. This makes Blender
unusable.
Switching back to X11 fixes the problem and Blender works as expected.
To be able to have Wayland with NVIDIA drivers enabled per default for Fedora
36 this needs to be fixed.
Name : blender
Epoch : 1
Version : 3.0.0
Release : 2.fc35
Architecture : x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2031495
1 year, 4 months
[Bug 2014331] New: [abrt] blender: std::__replacement_assert():
blender killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2014331
Bug ID: 2014331
Summary: [abrt] blender: std::__replacement_assert(): blender
killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:5b4070982b11941697ee4c232ddee022084e0b93;VAR
IANT_ID=workstation;
Component: blender
Assignee: luya_tfz(a)thefinalzone.net
Reporter: MikeDawg(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Just attempting to launch blender
Version-Release number of selected component:
blender-1:2.93.4-1.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-blender-249284.scope
cmdline: blender
crash_function: std::__replacement_assert
executable: /usr/bin/blender
journald_cursor:
s=ddbc815615424ba889b26a0bcf96f8f3;i=29c973;b=8d64d080c9144fbcbd3560dd4a6e4bc8;m=19fe18b0be;t=5ce57a68c3316;x=77c180641e9cf2e3
kernel: 5.14.10-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Potential duplicate: bug 1938324
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2014331
1 year, 4 months
[Bug 1738968] New: gimp-layer-via-copy-cut depends on Python 2
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1738968
Bug ID: 1738968
Summary: gimp-layer-via-copy-cut depends on Python 2
Product: Fedora
Version: rawhide
Status: NEW
Component: gimp-layer-via-copy-cut
Assignee: luya_tfz(a)thefinalzone.net
Reporter: lbalhar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
luya_tfz(a)thefinalzone.net
Blocks: 1698500 (F31_PY2REMOVAL)
Target Milestone: ---
Classification: Fedora
Python 2.7 will reach end-of-life in January 2020, over 9 years after it was
released. This falls within the Fedora 31 lifetime.
Packages that depend on Python 2 are being switched to Python 3 or removed from
Fedora:
https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#...
Python 2 will be retired in Fedora 32:
https://fedoraproject.org/wiki/Changes/RetirePython2
To help planning, we'd like to know the plans for gimp-layer-via-copy-cut's
future. Specifically:
- What is the reason for the Python2 dependency? (Is it software written in
Python, or does it just provide Python bindings, or use Python in the build
system or test runner?)
- What are the upstream/community plans/timelines regarding Python 3?
- What is the guidance for porting to Python 3? (Assuming that there is someone
who generally knows how to port to Python 3, but doesn't know anything about
the particular package, what are the next steps to take?)
This bug is filed semi-automatically, and might not have all the context
specific to gimp-layer-via-copy-cut.
If you need anything from us, or something is unclear, please mention it here.
Thank you.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1698500
[Bug 1698500] F31 Mass Python 2 Package Removal
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 10 months
[Bug 1964069] New: blender 2.92.0 crash fails when trying to run
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1964069
Bug ID: 1964069
Summary: blender 2.92.0 crash fails when trying to run
Product: Fedora
Version: 34
Status: NEW
Component: blender
Assignee: luya_tfz(a)thefinalzone.net
Reporter: christianbueno.1(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1786567
--> https://bugzilla.redhat.com/attachment.cgi?id=1786567&action=edit
blender fails
Description of problem:
when trying to run blender, it fails, crash.
Version-Release number of selected component (if applicable):
fedora 34
blender 2.92.0 rpm fedora reository
How reproducible:
always
Steps to Reproduce:
1.install blender by,
sudo dnf install blender
2.trying to run blender by terminal
> blender
3.blender fails, crash
Actual results:
blender fails
Expected results:
we can run blender and use the software
Additional info:
terminal error,
[chris@f34 ~]$ blender
/usr/include/c++/11/bits/stl_deque.h:1328: std::deque<_Tp, _Alloc>::reference
std::deque<_Tp, _Alloc>::operator[](std::deque<_Tp, _Alloc>::size_type) [with
_Tp = nv50_ir::ValueRef; _Alloc = std::allocator<nv50_ir::ValueRef>;
std::deque<_Tp, _Alloc>::reference = nv50_ir::ValueRef&; std::deque<_Tp,
_Alloc>::size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)
[chris@f34 ~]$
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year, 10 months
[Bug 2007657] New: Blender color management options not available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2007657
Bug ID: 2007657
Summary: Blender color management options not available
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: blender
Severity: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: ebudan(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Using the Fedora 34 package (blender-2.93.4-1.fc34.src.rpm), all 'Color
Management' options under the 'Render Properties' are missing. Using the
blender.org download all options are found as expected.
A possinle cause:
Upon starting the executable in a shell, error messages about color management
and OpenColorIO are produced. An RPM ChangeLog entry states:
* Wed Sep 01 2021 Richard Shaw <hobbes1069(a)gmail.com> 1:2.93.3-9
- Rebuild for OpenColorIO 2.1.
Fedora 34, however, seems to provide OpenColorIO 1.1.1.
Version-Release number of selected component (if applicable):
2.93.4-1.fc34
How reproducible:
Steps to Reproduce:
1. Start package provided Blender
2. Navigate to Render Options (by default right-side lower section, 2nd tab
from top), scroll to end of tab, expand Color Management
3. Click on View Transform, note multiple missing options (e.g. Filmic)
4. Click on Look, not multiple missing options
5. Build a scene and attempt to modify Exposure, Gamma; note lack of change
(use viewport shading: rendered)
Actual results:
Multiple missing options and functionality under Color Management.
Expected results:
View Transform dropdown should contain False Color, Raw, Filmic, Filmic Log,
Standard. Look dropdown should contain multiple contrast options. Exposure,
Gamma sliders should affect (rendered shading) lighting.
Additional info:
Suspected culprit: package compiled against OCIO 2, F34 supplies OCIO 1.
(Separately, Blender has previously encountered problems with paths containing
more exotic UTF-8 characters, leading to similar problems when required data
files are not found, but this presumably is not the issue here.)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2007657
2 years