[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 2052019] New: blender: Out-of-bounds memory access due to
malformed DDS image file [epel-all]
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2052019
Bug ID: 2052019
Summary: blender: Out-of-bounds memory access due to malformed
DDS image file [epel-all]
Product: Fedora EPEL
Version: epel7
Status: NEW
Component: blender
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: negativo17(a)gmail.com
Reporter: mcascell(a)redhat.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
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2052019
1 year, 11 months
[Bug 2052013] New: blender: Out-of-bounds memory access in
IMB_flipy() due to large image dimensions [epel-all]
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2052013
Bug ID: 2052013
Summary: blender: Out-of-bounds memory access in IMB_flipy()
due to large image dimensions [epel-all]
Product: Fedora EPEL
Version: epel7
Status: NEW
Component: blender
Keywords: Security, SecurityTracking
Severity: high
Priority: high
Assignee: negativo17(a)gmail.com
Reporter: mcascell(a)redhat.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
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora EPEL. While
only one tracking bug has been filed, please correct all affected versions
at the same time. If you need to fix the versions independent of each
other, you may clone this bug as appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2052013
1 year, 11 months