January 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1156797] Mangled she-bangs in ruby2.6 are broken
by bugzilla_noreply＠novell.com 05 Jan '20

05 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1156797 http://bugzilla.suse.com/show_bug.cgi?id=1156797#c1 Stefan Brüns <stefan.bruens(a)rwth-aachen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |mschnitzer(a)suse.com Flags| |needinfo?(mschnitzer(a)suse.c | |om) --- Comment #1 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- The bug has been open and assigned for 2 months. No reaction so far. There has been an open SR for 2 months: https://build.opensuse.org/request/show/744318 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1142670] LLADDR in bridge configuration ignored.
by bugzilla_noreply＠novell.com 05 Jan '20

05 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1142670 http://bugzilla.opensuse.org/show_bug.cgi?id=1142670#c21 Christian Wittmer <chris(a)computersalat.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |chris(a)computersalat.de --- Comment #21 from Christian Wittmer <chris(a)computersalat.de> --- with latest update e.g. on Leap 15.1 to wicked-0.6.60-lp151.2.3.1 now 'bridge' interface is not getting started, when LLADDR is defined in ifcfg-bridge sys-01:/etc/sysconfig/network # cat ifcfg-brint BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='' BRIDGE_STP='off' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.141.1/24' LLADDR='52:54:00:a8:8d:01' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' sys-01:~ # ifdown brint --- snip /var/log/messages --- 2020-01-05T14:56:12.278787+00:00 sys-01 named[2849]: no longer listening on 192.168.141.1#53 2020-01-05T14:56:12.525767+00:00 sys-01 dhcpd: receive_packet failed on brint: Network is down --- snip /var/log/messages --- sys-01:~ # ifup brint brint setup-in-progress --- snip /var/log/messages --- 2020-01-05T14:56:50.298370+00:00 sys-01 systemd-udevd[18160]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. 2020-01-05T14:56:50.298638+00:00 sys-01 systemd-udevd[18160]: Could not generate persistent MAC address for brint: No such file or directory 2020-01-05T14:56:50.314146+00:00 sys-01 kernel: [ 468.992201] IPv6: ADDRCONF(NETDEV_UP): brint: link is not ready --- snip /var/log/messages --- without LLADDR it works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159876] New: Pandoc regression when creating epubs
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159876 Bug ID: 1159876 Summary: Pandoc regression when creating epubs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cornelis(a)solcon.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See upstream bug: https://github.com/jgm/pandoc/issues/5986 It has been fixed upstream. This regression makes 2.9 in TW unusable for me. Would a patch be possible? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1159852] VUL-1: CVE-2019-19950: use-after-free in ThrowException and ThrowLoggedException of magick/error.c.
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1159852 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:11739:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1140018] New: inconsistent order of partitions
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1140018 Bug ID: 1140018 Summary: inconsistent order of partitions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The order of partitions is inconsistent between the Qt and ncurses user interface. In Qt the order is "sdc1, sdc10, sdc11, sdc2, ...", in ncurses it is by partition number (which I like more). -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1155674] New: Expert Partitioner: internal error, if encrypted btrfs shall be created
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1155674 Bug ID: 1155674 Summary: Expert Partitioner: internal error, if encrypted btrfs shall be created Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: maik.koehler(a)posteo.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 823065 --> http://bugzilla.opensuse.org/attachment.cgi?id=823065&action=edit Result of save_y2logs The Installer of the GNOME Live CD (Snapshot 20191030) produces an error during the creation of an encrypted btrfs subvolume, if the expert partitioner is used. My goal is to reuse the existing EFI partitioning of the Windows 10 install to dual boot - the guided partitioning scheme intends to create a new EFI partition. (not a deal breaker, but IMHO it should be possible to create an encrypted btrfs partition using the export route) Reproducible: always Steps to reproduce: 1. Boot GNOME Live CD (Snapshot 20191030) 2. Start Installation 3. During Partitioning choose "Expert" 4. Create a new partition 5. Choose format as btrfs, mount point /, enable subvolume creation 6. Choose to encrypt the partition 7. Click Next 8. Installer produces the following error message: Caller: /usr/share/YaST2/lib/y2partitioner/widgets/encrypt.rb:92:in `format' Details: key{Header} not found Expected result: Installer allows creation of custom partition with encrypted btrfs partition. Interestingly *not* choosing the expert partitioning and choosing to install with encryption works, if selected in the guided setup. (put does not produce the wanted custom partitioning scheme) I have attached a log produced by save_y2logs. I couldn't find an existing bug report and hope, that the information is useful. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1158297] New: FTBFS of boost:extra with Python 3.8
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1158297 Bug ID: 1158297 Summary: FTBFS of boost:extra with Python 3.8 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1158289 Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory:Staging:A/boost:ex… I am not sure what’s going on, but I would start at https://docs.python.org/dev/whatsnew/3.8.html#debug-build-uses-the-same-abi… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1160082] New: devel:languages:php:php73/php7: Bug
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1160082 Bug ID: 1160082 Summary: devel:languages:php:php73/php7: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pgajdos(a)suse.com Reporter: munix9(a)googlemail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- Files could not be expanded: service error: bad link: conflict in file php7.spec -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159900] update-smart-drivedb: ...: *** BAD signature ***
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1159900 http://bugzilla.suse.com/show_bug.cgi?id=1159900#c3 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Stanislav Brabec <sbrabec(a)suse.com> --- Thanks for the report. This problem affects smartmontools-6.6.tar.gz, e. g. Leap 15.*, SLE 15 * and SLE12 *. And yes, there are several upstream problems: - Bi-yearly replacement of signing keys completely invalidate the idea of trusted online updates. - And short key validity makes impossible to use the old signing keys as signing keys for old branches. I reported it to the upstream https://www.smartmontools.org/ticket/1278 Let's wait, how upstream will fix it. If they are able to sign 6.6 releases with 2018 key, then we don't need to do anything. If not, we need a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159152] New: Boot freeze on TPM (tpm_tis) line
by bugzilla_noreply＠novell.com 04 Jan '20

04 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159152 Bug ID: 1159152 Summary: Boot freeze on TPM (tpm_tis) line Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: mmrmartin(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 826083 --> http://bugzilla.opensuse.org/attachment.cgi?id=826083&action=edit Kernel log Hi, I just want to install openSUSE Tumbleweed NET x86_64 Snapshot 20191210 on Lenovo L490, but I got stuck 4 seconds after the start. I cannot even change CapsLock light so I expect a Kernel freeze occurred. I did some research and I found out an Arch forum <https://bbs.archlinux.org/viewtopic.php?id=250025> that says about two Kernel commits between 5.3.3 and 5.3.4 that could cause it: - 7f064c378e2c8c848c7acc3ebba7ec45df1c5492 - 5b359c7c43727e624eac3efc7ad21bd2defea161 The forum also provides a workaround using `tpm_tis.interrupts=0` boot parameter. That workaround also helped in my case... Ubuntu's Bugzilla maybe found a solution to this <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852586>... It seems to me they only reverted those commits <https://www.ubuntuupdates.org/package/canonical_kernel_team/eoan/main/base/…> - SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts" - SAUCE: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" Can the fix be ported to openSUSE too? It seems to me the bug also affects L580, E590 (at least according to forums). Related: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852586 (possible fix) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435 (more details) - https://bugzilla.kernel.org/show_bug.cgi?id=204121 (maybe related) - https://bbs.archlinux.org/viewtopic.php?id=250025 -- You are receiving this mail because: You are on the CC list for the bug.

1 5