Design Suite April 2018

design-devel@lists.fedoraproject.org

1 participants
14 discussions

[Bug 1384180] New: Cannot add movies to Blender
by Red Hat Bugzilla 03 Dec '18

03 Dec '18

https://bugzilla.redhat.com/show_bug.cgi?id=1384180 Bug ID: 1384180 Summary: Cannot add movies to Blender Product: Fedora Version: 24 Component: blender Assignee: luya_tfz(a)thefinalzone.net Reporter: yajo.sk8(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, jochen(a)herr-schmitt.de, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, promac(a)gmail.com Description of problem: Using its built-in Video Sequence Editor, I cannot input any video file. Version-Release number of selected component (if applicable): blender-2.77a-1.fc24.x86_64 How reproducible: Always Steps to Reproduce: 1. Open Blender. 2. Open its Video Sequence Editor. 3. Press Shift+A. 4. Choose "Video". 5. Choose a video file. Actual results: UI says: File /home/yajo/Vídeos/GOPR4948-20161012-194939.webm could not be loaded Console logs say: not an anim: /home/yajo/Vídeos/GOPR4948-20161012-194939.webm Expected results: File loaded. Additional info: I only tried with MP4 and webm files. This thread seems related: http://blender.stackexchange.com/questions/28839/cannot-load-movie-files-on… It suggests to add ffmpeg support at compile time. I hope that's possible. I have ffmpeg installed from RPMFusion, with no luck. -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1513797] New: Does not want to start
by bugzilla＠redhat.com 28 Nov '18

28 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1513797 Bug ID: 1513797 Summary: Does not want to start Product: Fedora Version: 27 Component: swatchbooker Assignee: luya_tfz(a)thefinalzone.net Reporter: harlequin78(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com Swatchbooker 0.8-0.3.20170131gitc5c8b02.fc27 вoes not want to start on fresh install: Traceback (most recent call last): File "/usr/share/swatchbooker/swatchbooker.pyw", line 25, in <module> from PIL import ImageQt ImportError: cannot import name ImageQt -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1435423] New: Need to fix wallpaper / background packaging situation
by bugzilla＠redhat.com 27 Nov '18

27 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1435423 Bug ID: 1435423 Summary: Need to fix wallpaper / background packaging situation Product: Fedora Version: rawhide Component: f26-backgrounds Severity: high Assignee: luya_tfz(a)thefinalzone.net Reporter: duffy(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, luya_tfz(a)thefinalzone.net Description of problem: The packaging bits for providing the default desktop background are overcomplicated and cause issues every release. On top of that, there is a new source package every release, so every release we need to do a new package review. Once the new package is in, we have to adjust stuff in comps/spin-kickstarts. Just using one package with subpackages could save a lot of pain. There is legitimate complexity here, but someone should sit down and think about how this works and come up with a better approach - it should be possible but it's never on anybody's priority list until we get into another situation with wallpapers blocking the release. Going to no alphas in favor of rawhide serving as alpha, we need to change how it works anyway. Roshi offered to write a script to autogenerate a placeholder wallpaper that could be used until draft artwork was ready. Idea from today's F26 alpha go/no-go meeting: 1) After branch you make that have the current release stuff and move the previous one to desktop-backgrounds-f25 subpackage 2) maybe just one source package is OK, it'd have a lot of subpackages but you could just keep them around for as long as you want and the subpackages should have virtual provides 3) when we get to final, we push it to N+1 and at that point it never is an issue again Another idea: 1) the real problem we have here is a) there's far too much unnecessary work to do each cycle to actually meet the requirements and b) no-one seems to have taken responsibility for making sure all that work gets done every cycle, even though it's completely predictable and plannable-for and it should be someone's job as soon as possible after branching to put in the 'real' wallpaper for the release 2) the placeholder wallpaper should just always be in rawhide 3) when we branch the package is updated to the new one 4) the neat thing about doing it that way is that as long as the real wallpaper gets in *some time* before release, we're good, because then all pre-release builds would kinda 'automatically' have different wallpaper from all final releases 5) the placeholder wallpaper can always stay the same or just be changed when someone gets bored of it. it doesn't really matter so long as it's never the same as any final release wallpaper Nirik has volunteered to look into this. CCing adamw, sgallagh, and nb based on their participation / interest. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1565659] New: Blender crash on start
by bugzilla＠redhat.com 16 Sep '18

16 Sep '18

https://bugzilla.redhat.com/show_bug.cgi?id=1565659 Bug ID: 1565659 Summary: Blender crash on start Product: Fedora Version: 28 Component: blender Assignee: luya_tfz(a)thefinalzone.net Reporter: mjuszkie(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com Description of problem: Blender crash on start. Version-Release number of selected component (if applicable): blender-1:2.79b-2.fc28.x86_64 How reproducible: always Steps to Reproduce: 1. dnf install blender 2. blender Actual results: 15:43 (0s) hrw@puchatek:~$ blender DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 : CommandLine Error: Option 'enable-value-profiling' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options 15:43 (1s) hrw@puchatek:~$ Expected results: Blender starts. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1571612] New: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution [epel-7]
by bugzilla＠redhat.com 28 Jun '18

28 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1571612 Bug ID: 1571612 Summary: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution [epel-7] Product: Fedora EPEL Version: epel7 Component: blender Keywords: Security, SecurityTracking Severity: high Priority: high Assignee: luya_tfz(a)thefinalzone.net Reporter: amaris(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com 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-7. 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. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1571609] New: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution
by bugzilla＠redhat.com 28 Jun '18

28 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1571609 Bug ID: 1571609 Summary: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution Product: Security Response Component: vulnerability Keywords: Security Severity: high Priority: high Assignee: security-response-team(a)redhat.com Reporter: amaris(a)redhat.com CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com An exploitable integer overflow exists in the 'BKE_mesh_calc_normals_tessface' functionality of the Blender open-source 3d creation suite. A specially crafted .blend file can cause an integer overflow resulting in a buffer overflow which can allow for code execution under the context of the application. An attacker can convince a user to open a .blend file in order to trigger this vulnerability. External References: https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0438 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1571611] New: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution [fedora-all]
by bugzilla＠redhat.com 28 Jun '18

28 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1571611 Bug ID: 1571611 Summary: CVE-2017-12086 blender: Integer overflow in BKE_mesh_calc_normals_tessface potentially leading to code execution [fedora-all] Product: Fedora Version: 27 Component: blender Keywords: Security, SecurityTracking Severity: high Priority: high Assignee: luya_tfz(a)thefinalzone.net Reporter: amaris(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-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. 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.

1 4

[Bug 1435753] New: cant emerge blender in RHEL 7
by bugzilla＠redhat.com 27 Jun '18

27 Jun '18

https://bugzilla.redhat.com/show_bug.cgi?id=1435753 Bug ID: 1435753 Summary: cant emerge blender in RHEL 7 Product: Fedora EPEL Version: epel7 Component: blender Severity: medium Assignee: luya_tfz(a)thefinalzone.net Reporter: joroman(a)rand.org QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, jochen(a)herr-schmitt.de, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com Description of problem: rhel7 wont emerge blender without a dependency problem Version-Release number of selected component (if applicable): How reproducible: very Steps to Reproduce: 1.yum install blender 2. 3. Actual results: fails Expected results: Additional info: [root@redacted]# yum install blender Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager Resolving Dependencies --> Running transaction check ---> Package blender.x86_64 1:2.68a-6.el7 will be installed --> Processing Dependency: blender-fonts = 1:2.68a-6.el7 for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: google-droid-sans-fonts for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: /usr/bin/python3 for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libspnav.so.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libpython3.4m.so.1.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libopenal.so.1()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libjemalloc.so.1()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libjack.so.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libboost_regex-mt.so.1.53.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libboost_locale-mt.so.1.53.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libboost_filesystem-mt.so.1.53.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libboost_date_time-mt.so.1.53.0()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libOpenImageIO.so.1.5()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libOpenColorIO.so.1()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Processing Dependency: libGLEW.so.1.10()(64bit) for package: 1:blender-2.68a-6.el7.x86_64 --> Running transaction check ---> Package OpenColorIO.x86_64 0:1.0.9-4.el7 will be installed --> Processing Dependency: libyaml-cpp.so.0.3()(64bit) for package: OpenColorIO-1.0.9-4.el7.x86_64 --> Processing Dependency: libtinyxml.so.0()(64bit) for package: OpenColorIO-1.0.9-4.el7.x86_64 ---> Package OpenImageIO.x86_64 0:1.5.24-3.el7.1 will be installed --> Processing Dependency: libpugixml.so.1()(64bit) for package: OpenImageIO-1.5.24-3.el7.1.x86_64 --> Processing Dependency: libopencv_highgui.so.2.4()(64bit) for package: OpenImageIO-1.5.24-3.el7.1.x86_64 --> Processing Dependency: libopencv_core.so.2.4()(64bit) for package: OpenImageIO-1.5.24-3.el7.1.x86_64 ---> Package blender.x86_64 1:2.68a-6.el7 will be installed --> Processing Dependency: google-droid-sans-fonts for package: 1:blender-2.68a-6.el7.x86_64 ---> Package blender-fonts.noarch 1:2.68a-6.el7 will be installed ---> Package boost-date-time.x86_64 0:1.53.0-26.el7 will be installed ---> Package boost-filesystem.x86_64 0:1.53.0-26.el7 will be installed ---> Package boost-locale.x86_64 0:1.53.0-26.el7 will be installed --> Processing Dependency: boost-chrono(x86-64) = 1.53.0-26.el7 for package: boost-locale-1.53.0-26.el7.x86_64 --> Processing Dependency: libboost_chrono-mt.so.1.53.0()(64bit) for package: boost-locale-1.53.0-26.el7.x86_64 ---> Package boost-regex.x86_64 0:1.53.0-26.el7 will be installed ---> Package jack-audio-connection-kit.x86_64 0:1.9.9.5-6.el7 will be installed --> Processing Dependency: libffado.so.2()(64bit) for package: jack-audio-connection-kit-1.9.9.5-6.el7.x86_64 ---> Package jemalloc.x86_64 0:3.6.0-1.el7 will be installed ---> Package libGLEW.x86_64 0:1.10.0-5.el7 will be installed ---> Package libspnav.x86_64 0:0.2.3-1.el7 will be installed ---> Package openal-soft.x86_64 0:1.16.0-3.el7 will be installed ---> Package python34.x86_64 0:3.4.5-3.el7 will be installed ---> Package python34-libs.x86_64 0:3.4.5-3.el7 will be installed --> Running transaction check ---> Package blender.x86_64 1:2.68a-6.el7 will be installed --> Processing Dependency: google-droid-sans-fonts for package: 1:blender-2.68a-6.el7.x86_64 ---> Package boost-chrono.x86_64 0:1.53.0-26.el7 will be installed ---> Package libffado.x86_64 0:2.1.0-4.el7 will be installed --> Processing Dependency: libxml++-2.6.so.2()(64bit) for package: libffado-2.1.0-4.el7.x86_64 ---> Package opencv.x86_64 0:2.4.5-3.el7 will be installed ---> Package opencv-core.x86_64 0:2.4.5-3.el7 will be installed ---> Package pugixml.x86_64 0:1.8-1.el7 will be installed ---> Package tinyxml.x86_64 0:2.6.2-3.el7 will be installed ---> Package yaml-cpp03.x86_64 0:0.3.0-4.el7 will be installed --> Running transaction check ---> Package blender.x86_64 1:2.68a-6.el7 will be installed --> Processing Dependency: google-droid-sans-fonts for package: 1:blender-2.68a-6.el7.x86_64 ---> Package libxml++.x86_64 0:2.37.1-1.el7 will be installed --> Finished Dependency Resolution --> Finding unneeded leftover dependencies Found and removing 0 unneeded dependencies Error: Package: 1:blender-2.68a-6.el7.x86_64 (epel) Requires: google-droid-sans-fonts ********************************************************************** yum can be configured to try to resolve such errors by temporarily enabling disabled repos and searching for missing dependencies. To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf ********************************************************************** Error: Package: 1:blender-2.68a-6.el7.x86_64 (epel) Requires: google-droid-sans-fonts You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1478536] New: Blender warnings " X server found. dri2 connection failed!"
by bugzilla＠redhat.com 29 May '18

29 May '18

https://bugzilla.redhat.com/show_bug.cgi?id=1478536 Bug ID: 1478536 Summary: Blender warnings "X server found. dri2 connection failed!" Product: Fedora Version: 26 Component: blender Severity: medium Assignee: luya_tfz(a)thefinalzone.net Reporter: alex(a)malexmedia.net QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, jochen(a)herr-schmitt.de, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com Description of problem: When launching Blender, after switching the rendering engine to "Cycles Render", the terminal displays a large number of errors and warnings: ---- SNIP ---- X server found. dri2 connection failed! DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument Assuming 131072kB available aperture size. May lead to reduced performance or incorrect rendering. get chip id failed: -1 [22] param: 4, val: 0 ---- SNIP ---- Version-Release number of selected component (if applicable): blender-2.78c-4.fc26.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Launch /usr/bin/blender from within Terminal 2. Switch to "Cycles Render" in upper-right drop down. 3. Observe "dri2 connection failed" error messages repeated several times. Actual results: Blender complains over and over that it cannot connect to DRI. Expected results: Blender should be able to establish appropriate connections to DRI. Additional info: This issue is only reproducible within Wayland. Under Xorg, this issue is not present. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1549875] New: blender-2.79a is available
by bugzilla＠redhat.com 09 Apr '18

09 Apr '18

https://bugzilla.redhat.com/show_bug.cgi?id=1549875 Bug ID: 1549875 Summary: blender-2.79a is available Product: Fedora Version: rawhide Component: blender Keywords: FutureFeature, Triaged Assignee: luya_tfz(a)thefinalzone.net Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: design-devel(a)lists.fedoraproject.org, hobbes1069(a)gmail.com, kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net, negativo17(a)gmail.com, promac(a)gmail.com Latest upstream release: 2.79a Current version/release in rawhide: 2.79-6.fc28 URL: http://download.blender.org/source/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/201/ -- You are receiving this mail because: You are on the CC list for the bug.

1 12

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Design Suite April 2018