April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210334] New: wants to install gnome
by bugzilla_noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210334 Bug ID: 1210334 Summary: wants to install gnome Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: f4tmike(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866265 --> http://bugzilla.opensuse.org/attachment.cgi?id=866265&action=edit latest zypper dup Running hyprland on tumbleweed. Sometimes when I 'zypper dup' it wants to install the gnome stack! After booting I end up in gnome. I'm not using any display manager. Booting in hyprland directly (~/.config/fish/conf.d/hyprland.fish): set TTY1 (tty) [ "$TTY1" = "/dev/tty1" ] && exec Hyprland Attached is the latest zypper dup (I didn't execute). Got the same issue on my pc at home as well as on my pc at work. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1210329] New: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210329 Bug ID: 1210329 Summary: use after free bug in da9150_charger_remove due to race condition Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: hackerzheng666(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In da9150_charger_probe, &charger->otg_work is bound with da9150_charger_otg_work. da9150_charger_otg_ncb may be called to start the work. If we remove the module which will call da9150_charger_remove to make cleanup, there may be a unfinished work. The possible sequence is as follows: Fix it by canceling the work before cleanup in the da9150_charger_remove CPU0 CPUc1 |da9150_charger_otg_work da9150_charger_remove | power_supply_unregister | device_unregister | power_supply_dev_release | kfree(psy) | | | power_supply_changed(charger->usb); | //use There's no kernel log. Here is the patch link of [1] Linux-v6.3 and [2]patchwork [1] https://lore.kernel.org/all/CAHk-=whcaHLNpb7Mu_QX7ABwPgyRyfW-V8=v4Mv0S22fpj… [2] https://lore.kernel.org/all/20230328142620.323334485@linuxfoundation.org/ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1210140] New: [SELinux] can't install cockpit
by bugzilla_noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210140 Bug ID: 1210140 Summary: [SELinux] can't install cockpit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: filippo.bonazzi(a)suse.com QA Contact: security-team(a)suse.de Found By: --- Blocker: --- Created attachment 866127 --> http://bugzilla.opensuse.org/attachment.cgi?id=866127&action=edit SELinux AVCs Operating System: openSUSE MicroOS SELinux status, mode and policy name: enabled, enforcing, targeted SELinux policy version and repository: Repository : openSUSE-Tumbleweed-Oss Name : selinux-policy-targeted Version : 20230321-1.1 Arch : noarch Vendor : openSUSE Installed Size : 24.0 MiB Installed : Yes (automatically) Status : up-to-date The software (incl. version) that is affected by the SELinux issue and the error message: cockpit SELinux Audit log: attached Any other important details: This is a fresh MicroOS VM from the qcow2 image [0]. I just created the VM, started it and added the root user. I installed cockpit following the instructions from [1]: $ transactional-update pkg install -t pattern microos-cockpit This completed and I rebooted the system. The instructions are evidently not enough, as many cockpit packages including cockpit are not installed by this, and of course the cockpit socket is not present and cockpit cannot be started. Therefore, I launched another transactional update to install cockpit: $ transactional-update pkg install cockpit This now breaks with this error: ``` (4/5) Installing: cockpit-ws-276.1-4.2.x86_64 [... SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.33: Permission denied /usr/sbin/load_policy: Can't load policy: Permission denied grep: /etc/pam.d/cockpit: No such file or directory done] ``` There are several AVCs (attached), I'm not sure if they are related. [0] https://download.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64… [1] https://documentation.suse.com/sle-micro/5.3/html/SLE-Micro-all/article-coc… -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1209985] Secure boot violation
by bugzilla_noreply＠suse.com 12 Apr '23

12 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209985 Joey Lee <jlee(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jlee(a)suse.com |dennis.tseng(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210066] New: Logspam: SELinux is preventing systemd-journal from read access on the directory dbus.service.
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210066 Bug ID: 1210066 Summary: Logspam: SELinux is preventing systemd-journal from read access on the directory dbus.service. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: khanich.opensource(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- OS: openSUSE microOS Raspberry Pi 4 systemd-journald tries to access /sys/fs/cgroup/system.slice/dbus.service. This gets blocked by SELinux by default. Here is one of the log entries which I got via sealert: -------------------------------------------------------------------------------- SELinux is preventing systemd-journal from read access on the directory dbus.service. ***** Plugin catchall_boolean (89.3 confidence) suggests ****************** If you want to allow logging to syslogd list non security dirs Then you must tell SELinux about this by enabling the 'logging_syslogd_list_non_security_dirs' boolean. Do setsebool -P logging_syslogd_list_non_security_dirs 1 ***** Plugin catchall (11.6 confidence) suggests ************************** If you believe that systemd-journal should be allowed read access on the dbus.service directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'systemd-journal' --raw | audit2allow -M my-systemdjournal # semodule -X 300 -i my-systemdjournal.pp Additional Information: Source Context system_u:system_r:syslogd_t:s0 Target Context system_u:object_r:cgroup_t:s0 Target Objects dbus.service [ dir ] Source systemd-journal Source Path systemd-journal Port <Unknown> Host backupserver Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-20221019-9.1.noarch Local Policy RPM selinux-policy-targeted-20221019-9.1.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name backupserver Platform Linux backupserver 6.2.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Mar 13 10:57:27 UTC 2023 (fa1a4c6) aarch64 aarch64 Alert Count 293 First Seen 2023-04-03 16:34:04 UTC Last Seen 2023-04-03 16:44:06 UTC Local ID faab6787-1eb1-499b-a834-61d1174f2239 Raw Audit Messages type=AVC msg=audit(1680540246.709:2998): avc: denied { read } for pid=952 comm="systemd-journal" name="dbus.service" dev="cgroup2" ino=1985 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:cgroup_t:s0 tclass=dir permissive=0 Hash: systemd-journal,syslogd_t,cgroup_t,dir,read -------------------------------------------------------------------------------- While if it would only be one entry, this wouldn't be too bad (although I would very much go and research why it wants to access that), journald tries to access this every 2 seconds and as such I get a log entry every 2 seconds. At that point it's just spam because it drowns out every other log message. Considering that besides me installing some SELinux tools to debug this better, I didn't change anything about the configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1210176] New: LLVM16 breaks Thunderbird 102 build
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210176 Bug ID: 1210176 Summary: LLVM16 breaks Thunderbird 102 build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: wolfgang(a)rosenauer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since LLVM16 landed on Tumbleweed Thunderbird fails to build. https://build.opensuse.org/package/live_build_log/mozilla:Factory/MozillaTh… As long as we don't find a solution to make TB compile again (which we might not be able to w/o upstream) there are no TB updates possible anymore in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1210267] New: Trouble with newest package amavisd-new
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210267 Bug ID: 1210267 Summary: Trouble with newest package amavisd-new Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The new version of /etc/amavisd.conf in package amvisd-new, which came in 20230407, changes the working directory for amavis.service from /var/spool/ amavis into /var/amavis. However this change is not reflected in creating the necessary folders in /var/amavis like /var/amavis/{tmp,db} with the owner/group vscan:vscan. Also the working directory in /usr/lib/systemd/system/amavis.service needs to be changed in the same way. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1207772] New: mozilla-openh264 doesn't work with Fish default shell
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207772 Bug ID: 1207772 Summary: mozilla-openh264 doesn't work with Fish default shell Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running mozilla-openh264-2.3.1-2.sle150400.1.x86_64 from http://codecs.opensuse.org/openh264/openSUSE_Leap I see that /etc/profile.d/gmpopenh264.sh is not triggered for me, since my default shell is Fish -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1210168] New: [Build 20230404] firefox no longer existing on i586
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210168 Bug ID: 1210168 Summary: [Build 20230404] firefox no longer existing on i586 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i586 URL: https://openqa.opensuse.org/tests/3210979/modules/fire fox/steps/16 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation The latest submission for MozillaFirefox has set ExcludeArch %ix86, which means FF is no longer built. openQA test in scenario opensuse-Tumbleweed-LegacyX86-DVD-i586-gnome@32bit fails in [firefox](https://openqa.opensuse.org/tests/3210979/modules/firefox/steps/16) ## Test suite description Revert schedule to working settings - dleuenberger, 20211117 ## Reproducible Fails since (at least) Build [20230404](https://openqa.opensuse.org/tests/3210979) (current job) ## Expected result Last good: [20230403](https://openqa.opensuse.org/tests/3208208) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=i586&distri=opensuse&… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1199210] New: Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 incompatibility
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199210 Bug ID: 1199210 Summary: Firefox 99 no longer plays video content due to Tumbleweed FFMPEG / openh264 incompatibility Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: jphands(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- About 21 days ago, I reported a bug ( https://bugzilla.mozilla.org/show_bug.cgi?id=1764436 ) to the FireFox team, after a Tumbleweed update caused FireFox to stop playing some video content. Other browsers like Brave or Opera worked just fine, leading me to suspect Firefox. I worked with the FF team to run various tests and their eventual resolution is "wontfix" because the problem actually seems to be some packaging issue with FFMPEG and OPeH264...perhaps a version mismatch. One of the FF developers said "To fix the problem, you need to install the exact same version of https://software.opensuse.org/package/libopenh264-6 that was used to build OpenSuse's ffmpeg-5." The mozilla bug link above gives the full story. I have been unable to get Firefox to play video content, no matter what combination of FFMPEG and Openh264 I've tried, but this area isn't my strength. The FF people recommended that I open a bug with Tumbleweed, and perhaps together, the bug can be resolved. I'm available for any testing or experiments...just let me know. ==========================MACHINE INFO========================================== Operating System: openSUSE Tumbleweed 20220503 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 24 � AMD Ryzen 9 3900X 12-Core Processor Memory: 47.0 GiB of RAM Graphics Processor: AMD DIMGREY_CAVEFISH -- You are receiving this mail because: You are on the CC list for the bug.

1 4