September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190210] nvidia: PCI ID Supplements no longer available on Tumbleweed
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190210 http://bugzilla.opensuse.org/show_bug.cgi?id=1190210#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Tried this --- my-find-supplements (revision 133) +++ my-find-supplements (working copy) @@ -16,6 +16,8 @@ if test -z "$krel"; then exit fi +echo "krel: $krel" +echo "pci_id_file: __ $PCI_ID_FILE __" # and create our own list of modalias supplements for id in $(cat ${PCI_ID_FILE} | cut -d " " -f 1|sed 's/0x//g'); do and both - $krel and $PCI_ID_FILE - are empty. Seems the script no longer gets the pci id file as paraemter although it's specified. in specfile. %define __kmp_supplements %_sourcedir/my-find-supplements %pci_id_file -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c5 --- Comment #5 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- (In reply to Pedro Monreal Gonzalez from comment #3) > (In reply to Michal Suchanek from comment #1) > > This is some tooling error. > > > > The man page comes correctly rendered in the upstream git, we alter the > > source, and then it comes mangled after it is regenerated from the XML > > > > Any idea what might have gone wrong with the xsltproc? > > > > /usr/bin/xsltproc \ > > -o modprobe.d.5 \ > > --nonet \ > > --stringparam man.output.quietly 1 \ > > --param funcsynopsis.style "'ansi'" \ > > /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl > > modprobe.d.xml > > Note: namesp. add : added namespace before processing modprobe.d > > Hi, @Michal. Looks like this recently accepted submissions is related: > https://build.opensuse.org/request/show/898998 > > I'm adding @Petr here in CC. Just for reference: * Upstream issue: https://gitlab.gnome.org/GNOME/libxslt/-/issues/31 * Upstream commit: https://gitlab.gnome.org/GNOME/libxslt/-/commit/f165525fe744e6fe3b377b480d6… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c4 Thomas Schraitle <thomas.schraitle(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(thomas.schraitle@ | |suse.com) | --- Comment #4 from Thomas Schraitle <thomas.schraitle(a)suse.com> --- Just to to let you know a few details which could be important. 1. Different DocBook versions Nowadays, DocBook has two major versions: 4 or 5. Among other changes, the most prevalent difference is a namespace in version 5. This looks like this: <refentry xmlns="http://docbook.org/ns/docbook" ...> If you don't have this namespace it is DocBook 4 which usually looks like this: <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> <refentry ...> 2. Different DocBook stylesheets Furthermore, the DocBook project publishes also the DocBook stylesheets. These are XSLT stylesheets which can transform the XML input into the most common output formats (HTML, FO, or--in your case--manpage). The tricky part is that these stylesheets comes in a non-ns and ns variant (ns stands for namespace). Although the non-ns variant is made for DocBook 4 and the ns variant for DocBook 5, it normally doesn't matter. However, I discovered some strange effects when using the ns variant with DocBook 4 sources (or vice versa). To make a long story short: check which DocBook version you have and use the right stylesheet for the job. For example, in case you still use DocBook 4, you want to try the non-ns variant. Replace this path: /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl with this: /usr/share/xml/docbook/stylesheet/nwalsh/current/manpages/docbook.xsl (without the "5" in nwalsh) Hope that helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190190] kmod: manpage of modprobe.d not correctly rendered
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190190 https://bugzilla.suse.com/show_bug.cgi?id=1190190#c3 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petr.vorel(a)suse.com Flags|needinfo?(pmonrealgonzalez@ | |suse.com) | --- Comment #3 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- (In reply to Michal Suchanek from comment #1) > This is some tooling error. > > The man page comes correctly rendered in the upstream git, we alter the > source, and then it comes mangled after it is regenerated from the XML > > Any idea what might have gone wrong with the xsltproc? > > /usr/bin/xsltproc \ > -o modprobe.d.5 \ > --nonet \ > --stringparam man.output.quietly 1 \ > --param funcsynopsis.style "'ansi'" \ > /usr/share/xml/docbook/stylesheet/nwalsh5/current/manpages/docbook.xsl > modprobe.d.xml > Note: namesp. add : added namespace before processing modprobe.d Hi, @Michal. Looks like this recently accepted submissions is related: https://build.opensuse.org/request/show/898998 I'm adding @Petr here in CC. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189922] config: enable CONFIG_USB_ISP1760_DUAL_ROLE
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189922 https://bugzilla.suse.com/show_bug.cgi?id=1189922#c3 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Matthias Brugger <mbrugger(a)suse.com> --- merged to tumbleweed and future Leap kernel -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190210] nvidia: PCI ID Supplements no longer available on Tumbleweed
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190210 http://bugzilla.opensuse.org/show_bug.cgi?id=1190210#c5 Hans-Peter Jansen <hpj(a)urpla.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hpj(a)urpla.net --- Comment #5 from Hans-Peter Jansen <hpj(a)urpla.net> --- The changes to my-find-supplements seems straight forward, but this will need another version dependent switch beforehand to separate the logic for the different rpm versions. On a second view, it's unclear, where the TW /usr/lib/rpm/find-supplements script gets the filename(s) from?!? Stefan, have you checked the output of this script already? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178830] hibernate: Disable when the kernel is locked down
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1178830 https://bugzilla.suse.com/show_bug.cgi?id=1178830#c1 Lukas Kucharczyk <lukas.kucharczyk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Lukas Kucharczyk <lukas.kucharczyk(a)suse.com> --- Done in https://github.com/openSUSE/release-notes-openSUSE/commit/5bf77079ddd305cc2… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190163] New: Adapt YaST Services Manager to recognize "maintenance" unit state
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190163 Bug ID: 1190163 Summary: Adapt YaST Services Manager to recognize "maintenance" unit state Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: YaST2 Assignee: mvidner(a)suse.com Reporter: mvidner(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- As our automated checker has noted[1], systemd units have a new unit state, "maintenance". We need to adapt yast2-services-manager to classify this state as basically-active or basically-inactive "maintenance" means that the unit will automatically return to be "active" after a while. (`systemctl clean` was invoked) See also https://bugzilla.suse.com/show_bug.cgi?id=884756 for a previous bug regarding new unit states. ("activating" was added there) [1]: https://github.com/yast/yast-services-manager/runs/3238884448?check_suite_f… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190143] 5.13.13 does not detect firmware framebuffer resolution (regression against 5.13.6)
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190143 https://bugzilla.suse.com/show_bug.cgi?id=1190143#c8 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(arvidjaar(a)gmail.c | |om) --- Comment #8 from Michael Chang <mchang(a)suse.com> --- (In reply to Andrei Borzenkov from comment #5) > (In reply to Takashi Iwai from comment #4) > > ... and I guess it's about bug 1189782, which could be a regression by bug > > 1189879. > > This is about wrong grub configuration due to file location change; in my > case grub configuration remains the same (gfxmode is set statically in > /etc/default/grub by YaST). Hi Andrei, This still looks to me a problem introduced by bsc#1189782. If the gfxpayload is missing, the gfxmode used by grub won't be set for linux kernel thus expected VESA VGA mode is not enabled. Would you please check if regenerating grub.cfg with restored kernel config in prior location could help to fix problem or not ? > ln -srf /usr/lib/modules/5.13.13-1-default/config /boot/config-5.13.13-1-default > grub2-mkconfig -o /boot/grub2/grub.cfg Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190182] New: new media backend - slow download
by bugzilla_noreply＠suse.com 06 Sep '21

06 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190182 Bug ID: 1190182 Summary: new media backend - slow download Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: bdamasceno(a)hotmail.com.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852294 --> http://bugzilla.opensuse.org/attachment.cgi?id=852294&action=edit new media backend - slow download - 20210901 Follow up from mailing list discussion: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message… ----------------------------- "regular" dup = zypper dup "super" dup = env ZYPP_SINGLE_RPMTRANS=1 ZYPP_MEDIANETWORK=1 zypper dup test: notebook: super dup to get snapshot 20210831. desktop: regular dup to get snapshot 20210831. The download with super dup was four times slower than the regular dup. The snapshot was fresh so the "additional mirror rating" from the new media backend must have made a poor choice due to the ongoing mirror syncing. ----------------------------- "...might be interesting to see your zypper log for the slow case to check if any timeouts were firing." Couldn't find timeouts on the log from the slow case (notebook). I tried to compare the mirrors used on both cases but the logs are different: while the old media backend logged the mirrors used the new media backend didn�t. libzypp-17.28.1-1.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 2