December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179708] drbd fails to build with the upcoming kernel 5.10
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179708 https://bugzilla.suse.com/show_bug.cgi?id=1179708#c5 nick wang <nwang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from nick wang <nwang(a)suse.com> --- Change to resolved/fixed, since the sr to openSUSE:Factory is merged. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177395] gnome-software defunct/hangs after resume from suspend (affects checking for updates)
by bugzilla_noreply＠suse.com 11 Dec '20

11 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1177395 https://bugzilla.suse.com/show_bug.cgi?id=1177395#c18 --- Comment #18 from Jonathan Kang <songchuan.kang(a)suse.com> --- (In reply to Chris Schaller from comment #17) > Created attachment 843610 [details] > Output of journalctl, pkmon, gnome-software in one single file > > Here's how the log got created: > .......................................... > #!/bin/sh > > LOG=log > > killall gnome-software > > echo "### Log started at `date`" > $LOG > > echo "### Capturing output of journalctl --utc -f" >> $LOG > journalctl --utc -f >> $LOG 2>&1 & > > echo "### Capturing output of pkmon" >> $LOG > pkmon >> $LOG 2>&1 & > > echo "### Starting and capturing gnome-software --verbose" >> $LOG > gnome-software --verbose >> $LOG 2>&1 & > > echo "READY. Type in comments" > sed -u 's/^/### /' < /dev/stdin >> $LOG > .......................................... This is very useful! The logs show that GNOME Software somehow created a transaction and then does nothing with it. And PackageKit was processing that transaction. But as the transaction asked to do nothing, PK was doing nothing. However, what's not very clear is how GNOME Software created a "empty" transaction. So if you can add dbus logging which shows which methods are called on "org.freedesktop.PackageKit" interface, that'll help a lot on further debuging it. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179866] Remove deprecated package yast2-fonts from Tumbleweed
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179866 Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez(a)suse.com Assignee|yast2-maintainers(a)suse.de |jlopez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179528] VUL-0: CVE-2020-27818: pngcheck: global buffer overflow was discovered in check_chunk_name function via crafted pngfile
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179528 https://bugzilla.suse.com/show_bug.cgi?id=1179528#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:2227-1: An update that fixes one vulnerability is now available. Category: security (moderate) Bug References: 1179528 CVE References: CVE-2020-27818 JIRA References: Sources used: openSUSE Backports SLE-15-SP1 (src): pngcheck-2.3.0-bp151.4.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179447] VUL-0: CVE-2020-28926: minidlna: before versions 1.3.0 allows remote code execution
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179447 https://bugzilla.suse.com/show_bug.cgi?id=1179447#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:2226-1: An update that fixes two vulnerabilities is now available. Category: security (moderate) Bug References: 1179447 CVE References: CVE-2020-12695,CVE-2020-28926 JIRA References: Sources used: openSUSE Backports SLE-15-SP1 (src): minidlna-1.3.0-bp151.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179840] New: GitHub CLI: version is 'DEV'
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179840 Bug ID: 1179840 Summary: GitHub CLI: version is 'DEV' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed gh from the factory repo ( not yet in a TW snapshot ). I noticed that the version command prints 'DEV' instead of the actual release version. $ rpm -q gh gh-1.3.1-1.1.x86_64 $ gh version gh version DEV https://github.com/cli/cli/releases/latest It would be great if this could point to the actual tagged version. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1179913] VUL-1: CVE-2020-20739: vips: uninitialized variable in im_vips2dz function may leak remote server path or stack address
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179913 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179914] VUL-0: CVE-2020-29367: blosc: heap-based buffer overflow when there is a lack of space to write compressed data
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179914 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178275] New: usb3 device generates lots of command errors
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178275 Bug ID: 1178275 Summary: usb3 device generates lots of command errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jimoe(a)sohnen-moe.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- tumbleweed 20201022 I am using a 2TB Seagate external drive (2r1apl-500) as a backup device; backintime is the backup app. It is formatted with XFS. The system journal contains lots of the errors shown below; there are 5 groups of such errors each time a backup starts. After it gets through the errors sets, the backup proceeds normally. Backup sets are normal. I had an earlier Seagate disk drive (1.5 TB) for backup, formatted with BTRFS. It showed none of these difficulties. Further I have included some errors from startup. The OS seems to have a hard time with the disk drive from the beginning. The difficulty continues after boot is complete; eventually the device is considered functional, mostly. I cannot tell if this is a hardware problem (USB interface, disk drive), or an XFS filesystem issue. What other information is needed? ----[ usb3 disk access errors ]---- 2020-10-29T06:00:02-0700 sma-station14l python3[29320]: backintime (jmoe/1): INFO: Call rsync to take the snapshot 2020-10-29T06:03:35-0700 sma-station14l kernel: sd 7:0:0:0: [sde] tag#29 uas_eh_abort_handler 0 uas-tag 29 inflight: CMD OUT 2020-10-29T06:03:35-0700 sma-station14l kernel: sd 7:0:0:0: [sde] tag#29 CDB: Write(10) 2a 00 04 2c d6 20 00 04 00 00 2020-10-29T06:03:36-0700 sma-station14l kernel: sd 7:0:0:0: [sde] tag#28 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT ... blah blah blah ... 2020-10-29T06:03:38-0700 sma-station14l kernel: sd 7:0:0:0: [sde] tag#0 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT 2020-10-29T06:03:38-0700 sma-station14l kernel: sd 7:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 04 2c ca 28 00 03 fa 00 2020-10-29T06:03:38-0700 sma-station14l kernel: scsi host7: uas_eh_device_reset_handler start 2020-10-29T06:03:38-0700 sma-station14l kernel: usb 3-4: reset SuperSpeed Gen 1 USB device number 14 using xhci_hcd 2020-10-29T06:03:38-0700 sma-station14l kernel: scsi host7: uas_eh_device_reset_handler success 2020-10-29T06:04:00-0700 sma-station14l python3[29320]: backintime (jmoe/1): INFO: Save config file 2020-10-29T06:04:00-0700 sma-station14l python3[29320]: backintime (jmoe/1): INFO: Save permissions 2020-10-29T06:04:06-0700 sma-station14l python3[29320]: backintime (jmoe/1): INFO: Create info file 2020-10-29T06:04:07-0700 sma-station14l python3[29320]: backintime (jmoe/1): INFO: [smart remove] remove snapshots: [20201022-060002-585] ----[ end ]---- ----[ from dmesg (system boot) ]---- [ 19.788644] XFS (sde1): Mounting V5 Filesystem [ 19.840770] EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: data=ordered [ 19.862152] EXT4-fs (sdf1): mounted filesystem with ordered data mode. Opts: data=ordered [ 20.493479] XFS (sde1): Ending clean mount [ 442.856937] usb usb3-port2: Cannot enable. Maybe the USB cable is bad? [ 448.672230] usb 3-2: Device not responding to setup address. [ 448.934389] usb 3-2: Device not responding to setup address. [ 449.140637] usb 3-2: device not accepting address 43, error -71 [ 449.336706] usb 3-2: Device not responding to setup address. [ 449.544732] usb 3-2: Device not responding to setup address. [ 449.752681] usb 3-2: device not accepting address 44, error -71 [ 449.752823] usb usb3-port2: attempt power cycle [ 450.264711] usb 3-2: Device not responding to setup address. [ 450.472717] usb 3-2: Device not responding to setup address. [ 450.680667] usb 3-2: device not accepting address 45, error -71 [ 450.876704] usb 3-2: Device not responding to setup address. [ 451.084705] usb 3-2: Device not responding to setup address. [ 451.131079] XFS (sde1): Unmounting Filesystem [ 451.292664] usb 3-2: device not accepting address 46, error -71 [ 451.292812] usb usb3-port2: unable to enumerate USB device [ 471.718753] usb 3-2: Device not responding to setup address. [ 471.926647] usb 3-2: Device not responding to setup address. [ 472.134552] usb 3-2: device not accepting address 47, error -71 [ 472.334520] usb 3-2: Device not responding to setup address. [ 472.542435] usb 3-2: Device not responding to setup address. [ 472.750369] usb 3-2: device not accepting address 48, error -71 [ 472.750521] usb usb3-port2: attempt power cycle [ 473.266237] usb 3-2: Device not responding to setup address. [ 473.474149] usb 3-2: Device not responding to setup address. [ 473.682014] usb 3-2: device not accepting address 49, error -71 [ 474.709684] usb 3-2: Device not responding to setup address. [ 474.917636] usb 3-2: Device not responding to setup address. [ 475.125480] usb 3-2: device not accepting address 50, error -71 [ 475.125551] usb usb3-port2: unable to enumerate USB device [ 475.581560] usb 3-2: new SuperSpeed Gen 1 USB device number 51 using xhci_hcd ----[ end ]---- -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1179914] New: VUL-0: CVE-2020-29367: blosc: heap-based buffer overflow when there is a lack of space to write compressed data
by bugzilla_noreply＠suse.com 10 Dec '20

10 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179914 Bug ID: 1179914 Summary: VUL-0: CVE-2020-29367: blosc: heap-based buffer overflow when there is a lack of space to write compressed data Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/272427/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-29367 blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data. References: https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30c… https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442 https://bugzilla.redhat.com/show_bug.cgi?id=1903232 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29367 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29367 -- You are receiving this mail because: You are on the CC list for the bug.

1 1