https://bugzilla.redhat.com/show_bug.cgi?id=2249261
Bug ID: 2249261
Summary: Blender + HIP + mesa crashing on Radeon RX 6650
(RDNA2)
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: blender
Keywords: Desktop
Severity: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: lucas.kurdziel(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: code(a)musicinmybrain.net,
design-devel(a)lists.fedoraproject.org,
epel-packagers-sig(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com
Target Milestone: ---
Classification: Fedora
Hello,
I've been trying to run Blender rendering on GPU. I tried couple of weeks ago
on Fedora 38 and today after fresh upgrade to Fedora 39. I've installed Blender
from repositories. After intalling `rocm-hip` package the GPU becomes listed as
available in Blender GPU rendering properties. It. Crashes. Every. Single.
Time.
Now, the interesting part is: If I run Blender via `distrobox` (installed in an
Arch Linux container) it all works beautifully! Here's the link to a
hack/workaround:
https://www.reddit.com/r/Fedora/comments/11qh9j3/getting_bender_hip_to_work/
Is `rocm-hip` in Fedora not the equivalent of `hip-runtime-amd` from Arch? Is
there a way of getting GPU rendering in Blender on Fedora with Mesa drivers and
HIP? Because as proved - it does work on this hardware + mesa + blender
Blender from F39 repo: 3.6.4
Blender in Arch container: 3.6.5
I've tried also installing Blender 3.6.5 from Rawhide but same exact thing
happens - Blender crashing
Reproducible: Always
Steps to Reproduce:
1. dnf install blender rocm-hip
2. Open up Blender, go to Edit -> Preferences -> System -> Cycles rendering
devices -> HIP, Radeon RDNA2 GPU ticked
3. Close it. Go to Render properties on the right bottom pane, select Render
engine: Cycles, Feature set: Supported, Device: GPU Compute, press F12
4. Press F12 and Blender will crash right away. If you're unlucky it'll crash
at step 2
Actual Results:
Blender crash
Expected Results:
Blender doesn't crash
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2249261
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2280786
Bug ID: 2280786
Summary: CVE-2024-4067 yarnpkg: micromatch: vulnerable to
Regular Expression Denial of Service [fedora-all]
Product: Fedora
Version: 40
Status: NEW
Component: yarnpkg
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: zsvetlik(a)redhat.com
Reporter: rkeshri(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
manisandro(a)gmail.com, ngompa13(a)gmail.com,
zsvetlik(a)redhat.com
Target Milestone: ---
Classification: Fedora
More information about this security flaw is available in the following bug:
http://bugzilla.redhat.com/show_bug.cgi?id=2280601
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2280786
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2283798
Bug ID: 2283798
Summary: Location of unix socket is hardcoded in
/etc/sysconfig/valkey
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: valkey
Severity: high
Assignee: jonathan(a)almalinux.org
Reporter: fedora(a)joshuanoeske.de
CC: epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, jonathan(a)almalinux.org,
nathans(a)redhat.com, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
Changing the location of the unixsocket in /etc/valkey/valkey.conf does not
actually change its location as it is hardcoded in /etc/sysconfig/valkey. It
took me quite some time to figure out why the location of my socket was not
changing although I changed it. Either inform users about that or remove the
hardcoded location of the socket, please
Reproducible: Always
Steps to Reproduce:
1. Change location of unix socket in /etc/valkey/valkey.conf
2. Restart valkey
Actual Results:
Unix socket still at /var/run/valkey/valkey.conf
Expected Results:
Change the location of the unixsocket.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2283798
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2269669
Bug ID: 2269669
Summary: Fastboot crashes with std::out_of_range on
android-tools 34.0.4-4.fc39
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: android-tools
Keywords: External
Severity: medium
Assignee: ivan.afonichev(a)gmail.com
Reporter: patryk.ryczko(a)protonmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
go-sig(a)lists.fedoraproject.org,
ivan.afonichev(a)gmail.com, jeroen(a)tietema.net
Target Milestone: ---
Classification: Fedora
I was flashing FaiprhoneOS when this crash happened:
Sending 'dtbo_b' (24576 KB) OKAY [ 0.843s]
Writing 'dtbo_b' OKAY [ 0.103s]
Finished. Total time: 0.957s
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::compare: __pos (which is 917456) > this->size() (which
is 0)
./flash_fp5_factory.sh: line 205: 20588 Aborted (core dumped) (
"${FASTBOOT_BIN}" -s "${ANDROID_SERIAL}" flash "${partition}" "${image_file}" )
ERROR: Could not flash the super partition on device 49ba2508.
ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)
ERROR: Aborting now (press Enter to terminate).
Reproducible always, after rebooting the same error is appearing again.
After I've deleted android-tools and used ones from google it worked perfectly,
no issues.
There seems to be problem with this version on upstream, more details here:
https://gitlab.archlinux.org/archlinux/packaging/packages/android-tools/-/i…
Reproducible: Always
Steps to Reproduce:
1. Try flashing android image with fastboot from android-tools provided by
Fedora 39
2. After some time this error will appear.
Actual Results:
terminate called after throwing an instance of 'std::out_of_range' appears,
image not flashed.
Expected Results:
Image flashed successfully.
Stable Fedora 39, latest android-tools provided by Fedora.
Here is the link to Fairphone Community forum, just in case:
https://forum.fairphone.com/t/flashing-fp5-with-fastboot-error-could-not-fl….
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2269669
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2281506
Bug ID: 2281506
Summary: CVE-2024-34083 python-aiosmtpd: aiosmtpd: servers
based on aiosmtpd accept extra unencrypted commands
[epel-7]
Product: Fedora EPEL
Version: epel7
Status: NEW
Component: python-aiosmtpd
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: epel-packagers-sig(a)lists.fedoraproject.org
Reporter: ybuenos(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, psimovec(a)redhat.com
Target Milestone: ---
Classification: Fedora
More information about this security flaw is available in the following bug:
http://bugzilla.redhat.com/show_bug.cgi?id=2281505
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2281506
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2269312
Bug ID: 2269312
Summary: CVE-2024-27305 python-aiosmtpd: aio-libs/aiosmtpd:
SMTP smuggling [epel-7]
Product: Fedora EPEL
Version: epel7
Status: NEW
Component: python-aiosmtpd
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: epel-packagers-sig(a)lists.fedoraproject.org
Reporter: trathi(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: aurelien(a)bompard.org,
epel-packagers-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, psimovec(a)redhat.com
Target Milestone: ---
Classification: Fedora
More information about this security flaw is available in the following bug:
http://bugzilla.redhat.com/show_bug.cgi?id=2269311
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2269312
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…