Design Suite November 2018

design-devel@lists.fedoraproject.org

1 participants
5 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 27 Nov '18

27 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 1631922] New: No text in Blender UI
by bugzilla＠redhat.com 04 Nov '18

04 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1631922 Bug ID: 1631922 Summary: No text in Blender UI Product: Fedora Version: 29 Component: blender Severity: high Assignee: luya_tfz(a)thefinalzone.net Reporter: ego.cordatus(a)gmail.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 Created attachment 1485834 --> https://bugzilla.redhat.com/attachment.cgi?id=1485834&action=edit Blender no text Description of problem: No text in UI. Version-Release number of selected component (if applicable): 2.79b-7 How reproducible: Run Blender. Actual results: No text and other UI elements. Blender unusable. Expected results: As before. Additional info: Blender from Steam and from official Blender site run ok. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1638592] New: Blender UI broken on Fedora 29, RNA_string_set: OperatorProperties.mode not found.
by bugzilla＠redhat.com 02 Nov '18

02 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1638592 Bug ID: 1638592 Summary: Blender UI broken on Fedora 29, RNA_string_set: OperatorProperties.mode not found. Product: Fedora Version: 29 Component: blender Assignee: luya_tfz(a)thefinalzone.net Reporter: ifoolb(a)gmail.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 Created attachment 1493103 --> https://bugzilla.redhat.com/attachment.cgi?id=1493103&action=edit abnormal blender screenshot Description of problem: Many of Blender's UI elements are missing. Errors can be seen when launching Blender from the command line. Version-Release number of selected component (if applicable): 2.79b How reproducible: open Blender Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Design Suite November 2018