May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1168447] New: Please build Blender 2.8x with OptiX support
by bugzilla_noreply＠novell.com 16 Sep '22

16 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1168447 Bug ID: 1168447 Summary: Please build Blender 2.8x with OptiX support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: cfeck(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Blender has improved support for RTX cards since version 2.81. The official Blender download supports these Cycles engines: CPU, CUDA, OptiX, and OpenCL. In the Tumbleweed build of Blender, only CPU, CUDA, and OpenCL are selectable. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1121578] New: python-aiohttp Factory version unable to build on Leap
by bugzilla_noreply＠novell.com 15 Sep '22

15 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1121578 Bug ID: 1121578 Summary: python-aiohttp Factory version unable to build on Leap Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In order to fix python-aiohttp build failure in Leap 15.1, python-aiohttp's Factory version has submitted to Leap, however this version unable to build on Leap due to missing deps, https://build.opensuse.org/package/show/openSUSE:Leap:15.1:Staging:adi:21/p… Note that, a problem is, python-Cython is one of the dep does not have greater enough version in Leap, and python-Cython is from SLE. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1146856] New: security/fail2ban: Bug - failtoban breaks restarting firewalld
by bugzilla_noreply＠novell.com 14 Sep '22

14 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1146856 Bug ID: 1146856 Summary: security/fail2ban: Bug - failtoban breaks restarting firewalld Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: meissner(a)suse.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- on a system with fail2ban installed and activated it is impossible to use systemctl restart to restart firewalld: nextcloud:~ # systemctl restart firewalld Failed to restart firewalld.service: Transaction contains conflicting jobs 'restart' and 'stop' for fail2ban.service. Probably contradicting requirement dependencies configured. See system logs and 'systemctl status firewalld.service' for details. the sequence "systemctl stop fail2ban; systemctl restart firewalld; systemctl start fail2ban" works as exected. the same used to happen when I still used SuSEfirewall2 instead of firewalld, so I'm pretty sure the issue is with fail2ban and not with either of the two firewalls... for more info: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871993 https://bugzilla.redhat.com/show_bug.cgi?id=1379141 https://lists.freedesktop.org/archives/systemd-devel/2016-March/036011.html -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1057976] New: Patch for gtk3 (openSUSE-2017-1032) requires vietnamese, inuktitut, thai, and amharic
by bugzilla_noreply＠novell.com 12 Sep '22

12 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1057976 Bug ID: 1057976 Summary: Patch for gtk3 (openSUSE-2017-1032) requires vietnamese, inuktitut, thai, and amharic Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 740114 --> http://bugzilla.opensuse.org/attachment.cgi?id=740114&action=edit Screen shot showing Yast's suggestions When online updating the gtk3-3.20.10-5.3.1 to gtk3-3.20.10-5.6.1, Yast2 insists to add additional language modules like gtk3-immodule-{ietnamese,inuktitut,thai,amharic} which I don't need. See attachment. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 966042] New: yast command-line usage emits "unable to close filehandle properly" warning at exit
by bugzilla_noreply＠novell.com 09 Sep '22

09 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966042 Bug ID: 966042 Summary: yast command-line usage emits "unable to close filehandle properly" warning at exit Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bk(a)ancilla.ca QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Specifically, it says: Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line 21 during global destruction (#1) (S io) An error occurred when Perl implicitly closed a filehandle. This usually indicates your file system ran out of disk space. This happens with (as far as I can tell, I haven't tested exhaustively) all command-line yast invokations that involve a module. So, e.g., "yast users help" or "yast sysconfig help" will produce this message. "yast help" on its own, however, won't. It does not appear to affect yast's exit code, or it's ability to do its job; if I run "yast sysconfig set LOADER_TYPE=none", it does the right thing and then produces that message while exiting. Despite the hint that it may be space-related, this happens on multiple computers, all of them with plenty of space available on all filesystems. These systems are all running recent (~2 weeks) versions of Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 997317] New: grub2-branding lacks posttrans
by bugzilla_noreply＠novell.com 07 Sep '22

07 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=997317 Bug ID: 997317 Summary: grub2-branding lacks posttrans Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: ohering(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- grub2-branding creates a grub2.cfg in its %post. this is a very expensive operation, in combination with os-prober. there is nothing in that pkg which requires immediate action. cumulate the required steps and do it once in a single %posttrans. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1047852] New: knotify_libjack audio kcrash on pthread_key_create() at ../common/JackError.cpp:88
by bugzilla_noreply＠novell.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047852 Bug ID: 1047852 Summary: knotify_libjack audio kcrash on pthread_key_create() at ../common/JackError.cpp:88 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 Assignee: anixx(a)opensuse.org Reporter: drankinatty(a)suddenlinkmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 731684 --> http://bugzilla.opensuse.org/attachment.cgi?id=731684&action=edit knotify_libjack wdebug kcrash file (the 6 is just the 6th one I saved) A knotify/libjack.so.0 crash will regularly occur once during a session. It may take a day or two for the bug to appear, but on access to sound theme sound (no one in particular, e.g. dialog-open, minimize, etc.) a kcrash report appears and the desktop sounds no longer play until you restart the desktop. This time it took 2 days 5:29 minutes under heavy use to occur. It is strangely random when it happens, but very consistent that it *will* happen. This is not new and has been around at least since 13.1 (it may go back to 11.4). I have experiences this on two separate laptops with 13.1 and Leap 42.2. (I really think it was there in 11.4, but I'm far too old to remember) I have attached a wdebug.kcrash that details the error. -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 952799] New: bogofilter-{db,sqlite3} insists on using wordlist.tc
by bugzilla_noreply＠novell.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=952799 Bug ID: 952799 Summary: bogofilter-{db,sqlite3} insists on using wordlist.tc Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gour(a)atmarama.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the past, when using other Linux distros I was mostly using bogofilter with sqlite3 back-end, but after switching to openSUSE I've decided to convert to 'default' (Berkeley) DB backend. Unfortunately, after bogofilter package was updated in openSUSE, it looks it does insist on using $HOME/.bogofilter/wordlist.tc for the database name even if one uses Berkeley DB or Sqlite3 back-ends? When I try to use my old wordlist.db, Bogofilter plugin (Claws & Evolution) starts from the scratch and creates wordlist.tc. I wonder about this line in *.spec: %if 0%{?suse_version} > 1320 iow. whether the new Bogofilter package is ready to use existing setup with appropriate back-end (not equal to TokyoCabinet)? -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1107615] New: sysconfig requires ifup
by bugzilla_noreply＠novell.com 06 Sep '22

06 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=1107615 Bug ID: 1107615 Summary: sysconfig requires ifup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mt(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- sysconfig requires ifup and that pulls in wicked. For a basic container chroot that is not needed actually. Can we drop requiring ifup? Alternatively or in addition is it safe to not install sysconfig at all? netconfig which is needed for /etc/resolv.conf is separate anyways so sysconfig basically just provides some skeletons for ppp/ip-up and config files. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1169783] New: Passphase prompt for full disk encryption dissappear after TW upgrade from 20200411-0 to 20200414-0
by bugzilla_noreply＠novell.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1169783 Bug ID: 1169783 Summary: Passphase prompt for full disk encryption dissappear after TW upgrade from 20200411-0 to 20200414-0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 836048 --> http://bugzilla.opensuse.org/attachment.cgi?id=836048&action=edit Cannot boot to desktop, stuck here. With the latest TW update, I could not boot to the desktop. Normally, my PC will ask for my password for encrypted drive on Btrfs that I have setup according to https://en.opensuse.org/SDB:Encrypted_root_file_system which also avoid typing password twice. Everything have been working well until the latest upgrade from 20200411-0 to 20200414-0. The latest update did not ask me for the password, it seems to just skip it and would get stuck as the image shown. I roll back with snapper rollback and try to upgrade again but fail the same way. Any suggestion to how to get more info on this issue? System info (not broken) Operating System: openSUSE Tumbleweed 20200411 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.6.2-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are on the CC list for the bug.

2 103