March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209924] New: /usr/lib/os-release contains BUG_REPORT_URL="https:/bugs.opensuse.org" which redirects to en.opensuse.org instead of bugzilla.opensuse.org
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209924 Bug ID: 1209924 Summary: /usr/lib/os-release contains BUG_REPORT_URL="https:/bugs.opensuse.org" which redirects to en.opensuse.org instead of bugzilla.opensuse.org Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: NetWare 6.5 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Original Summary: /usr/lib/os-release contains BUG_REPORT_URL="https:/bugs.opensuse.org" which redirects to en.opensuse.org instead of bugzilla.opensuse.org Actual line item in /etc/os-release: BUG_REPORT_URL="https://bugs.opensuse.org/" causes redirect to https://en.opensuse.org/openSUSE:Submitting_bug_reports Expected line item in /etc/os-release: BUG_REPORT_URL="https://bugzilla.opensuse.org/" which goes directly to the bug tracker itself If the intent of the string is to provide instructions for filing bug reports rather than going directly to the official bug tracker, then BUG_REPORT_URL= should be replaced with some alternative string that confers an intent to provide bug reporting instructions. https://web.archive.org/web/20230314225146/www.linux.org/docs/man5/os-relea… [quote] SUPPORT_URL= should refer to the main support page for the operating system, if there is any. This is primarily intended for operating systems which vendors provide support for. BUG_REPORT_URL= should refer to the main bug reporting page for the operating system, if there is any. This is primarily intended for operating systems that rely on community QA. [/quote] SUPPORT_URL= does not exist in current os-release. Maybe it should contain: https://en.opensuse.org/openSUSE:Submitting_bug_reports so that BUG_REPORT_URL= can mean what it says and direct to: https://bugzilla.opensuse.org/ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1209963] New: AUDIT-0: wtmpdb: New pam_wtmpdb module replacing wtmp and parts of pam_lastlog
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209963 Bug ID: 1209963 Summary: AUDIT-0: wtmpdb: New pam_wtmpdb module replacing wtmp and parts of pam_lastlog 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- wtmpdb is a Y2038 safe implementation of "wtmp". wtmp entries are written by login applications and mainly used (read) by: last, last, last, ..., lslogin Collecting the data is done by a PAM module which needs to be whitelisted. https://build.opensuse.org/package/show/Linux-PAM/wtmpdb https://github.com/thkukuk/wtmpdb -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1155207] New: systemctl command line completion is very slow
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1155207 Bug ID: 1155207 Summary: systemctl command line completion is very slow Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- systemctl command line completion is very slow Suppose I type: systemctl status smart[tab][tab] and I get nothing. One second, two seconds... so I insist and hit tab several times, and after several seconds I get (one line per second): Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart smartcard.target smartd.service smartd_generate_opts.path smartd_generate_opts.service Isengard:~ # systemctl status smart and then I can type "d" and enter. Why is it that slow? It is an M2 disk. ie, SSD technology. It responds instantly when completing a normal command: Isengard:~ # smart smart_agetty smartctl smartd Isengard:~ # smart And that system is not busy at all, load 0.20. I can replicate the issue on other machines, and has been so probably for a year or so. Google "systemctl completion slow" finds reports on other distributions and several media. <https://bugzilla.redhat.com/show_bug.cgi?id=1491668> <https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1471723> and: <https://github.com/systemd/systemd/issues/7185> -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1207419] New: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207419 Bug ID: 1207419 Summary: jeos-firsboot dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: fvogt(a)suse.com Reporter: aherzig(a)suse.com QA Contact: jsrain(a)suse.com CC: vmoutoussamy(a)suse.com Found By: Development Blocker: --- The dependency on network was removed from main package (which supported both NM and W), but left on -rpiwifi sub-package, to be addressed. spec file requires wicked and needs adaptation to also work with networkmanager if it is installed (and not wicked), configurable or detected on run-time -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1159528] New: keybase client package is extremely outdated, plus lacks all gui elements
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1159528 Bug ID: 1159528 Summary: keybase client package is extremely outdated, plus lacks all gui elements 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: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the keybase package that comes packaged in openSUSE Leap 15.1 is outdated... to the ponit of being a prehistoric artefact: bundled comes version 2.11 - current from keybase.io is 5.1.1.... also, it lacks all gui elements - probably because it is such an old version. please update to the latest version. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1126900] New: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system.
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1126900 Bug ID: 1126900 Summary: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From a health-checker run: Clearing GRUB flag + grub2-editenv - set health_checker_flag=0 grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Starting health check -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1194160] New: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic"
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194160 Bug ID: 1194160 Summary: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Upgrading from Leap 15.2 to 15.3 via "zypper dup" showed this error message: (4328/5706) Installing: texlive-tex-gyre-fonts-2017.134.2.004svn18651-5.18.noarch .....[done] Additional rpm output: Unknown Type 1 weight "BoldItalic" Couldn't determine weight for qcsbi.pfb -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1204746] New: texlive-scheme-medium missing english documentation for fancyhdr
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204746 Bug ID: 1204746 Summary: texlive-scheme-medium missing english documentation for fancyhdr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lukasstraub2(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing texlive-scheme-medium, it includes documentation, but for example for fancyhdr only the italian docs are included, not the english ones. i.e. only texlive-fancyhdr-it is installed, not texlive-fancyhdr-doc. I suspect this is not the only package that has this problem. I expect at least english documentation to be installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1208289] New: [distrobox] cannot enter a container
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208289 Bug ID: 1208289 Summary: [distrobox] cannot enter a container Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just run (distrobox is 1.4.2.1 from TW): $ distrobox create paperino $ distrobox enter paperino and in the podman logs I found this piece of wisdom: Resolving package dependencies... Problem: the to be installed util-linux-systemd-2.38.1-6.1.x86_64 requires 'which', but this requirement cannot be provided not installable providers: which-2.21-5.7.i586[repo-oss] which-2.21-5.7.x86_64[repo-oss] Solution 1: deinstallation of busybox-which-1.36.0-26.1.noarch Solution 2: do not install util-linux-systemd-2.38.1-6.1.x86_64 Solution 3: break util-linux-systemd-2.38.1-6.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Error: An error occurred Obviously entering errored in ��Installing basic packages��. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1208396] New: Seamonkey starts coredump after opening link in new tab
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208396 Bug ID: 1208396 Summary: Seamonkey starts coredump after opening link in new tab Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: madmax(a)teenspirit.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed Seamonkey 2.53.15-1.8-x86_64 today. When I open links in a new tab and click on this tab, Seamonkey crashes and in the journal I sea a coredump started. What happens? Open youtube. Open youtube link in new tab Click on tab. Seamonkey freezes. Seamonkey disappears. Looking at journalctl coredump ends with these lines feb 16 17:11:58 monch systemd[1]: systemd-coredump(a)7-585-0.service: Deactivated successfully. feb 16 17:11:58 monch systemd[1]: systemd-coredump(a)7-585-0.service: Consumed 5.590s CPU time. feb 16 17:11:58 monch plasmashell[32696]: /usr/bin/seamonkey: regel 140: 32701 Segmentation fault (geheugendump gemaakt) $MOZ_PROGRAM "$@" feb 16 17:12: -- You are receiving this mail because: You are on the CC list for the bug.

1 7