August 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1175779] New: Symlink /etc/systemd/system/tmp.mount cripples system
by bugzilla_noreply＠suse.com 21 Sep '22

21 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175779 Bug ID: 1175779 Summary: Symlink /etc/systemd/system/tmp.mount cripples system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: suseacc(a)johnzone.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the dist-upgrade to 20200823, my system did not log in to the graphical environment (plasma). After reboot, it was worse. The root fs was mounted read only and some services did not start because of this. After some poking, I decided to roll back. The system came up and I dist-upgraded again. As Robert Munteanu hinted, there was a symlink from /etc/systemd/system/tmp.mount to /usr/share/systemd/tmp.mount which I deleted. The system rebooted normally this time. I checked the snapshots and did not find this symlink in the rw snapshot after the rollback, but in all previous until the one after the first upgrade to 20200823. I did comment out the /tmp entry in /etc/fstab as described in the wiki to migrate /tmp to tmpfs (https://en.opensuse.org/openSUSE:Tmp_on_tmpfs) and i wrote a service to create a symlink from /tmp/dumps to /dev/null to prevent steam from dumping gigabytes of logfiles there, effectively filling /tmp. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1154582] New: [Build 20191018] openQA test fails in shutdown: at-spi2 hangs
by bugzilla_noreply＠novell.com 19 Sep '22

19 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154582 Bug ID: 1154582 Summary: [Build 20191018] openQA test fails in shutdown: at-spi2 hangs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1061840/modules/shut down/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_mate@64bit fails in [shutdown](https://openqa.opensuse.org/tests/1061840/modules/shutdown/steps/… ## Test suite description ## Reproducible Fails since (at least) Build [20191017](https://openqa.opensuse.org/tests/1059937) ## Expected result Last good: [20191016](https://openqa.opensuse.org/tests/1058657) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1154753] New: screen stays dark on boot unless I specify nouveau.modeset=0
by bugzilla_noreply＠novell.com 17 Sep '22

17 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154753 Bug ID: 1154753 Summary: screen stays dark on boot unless I specify nouveau.modeset=0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: estellnb(a)elstel.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel modesetting does not seem to work with 4.12.14-lp151.28.20-default. My screens (integrated+external) stay dark without nouveau.modeset=0. I have a dual boot option with Debian 9, kernel 4.20.0-rc4 and there it works well with nouveau.hdmimhz=225. Strange. I remember that always having worked without any additional parameter (4K only with hdmimhz). Would you believe it to be possible that this is caused by openSUSE kernel extensions? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1174239] New: KDE Software Updater Applet: "Reboot needed / reboot now?" notification before Kernel update is installed
by bugzilla_noreply＠suse.com 17 Sep '22

17 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174239 Bug ID: 1174239 Summary: KDE Software Updater Applet: "Reboot needed / reboot now?" notification before Kernel update is installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: thomas-formella(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If a kernel update is available, the "KDE Software Updater Applet" notifies a "reboot needed / reboot now?" BEFORE the delta-rpm is downloaded and installed. It worked already as intended in a previous release before 15.0 (download kernel delta-rpm -> install -> notification "reboot needed / reboot now?"). Currently, the notification may confuse new users or desktop users, who don't use YaST or zypper to install updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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