October 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177618] External monitor connected via HDMI only works with 640x480 resolution
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177618 https://bugzilla.suse.com/show_bug.cgi?id=1177618#c3 --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- Date: Tue, 13 Oct 2020 17:29:06 +0200 From: Teo Tei <teo8976(a)gmail.com> To: sndirsch(a)suse.com Subject: Re: [Bug 1177618] External monitor connected via HDMI only works with 640x480 resolution Hello, The bugtracker is down so I'm forced to reply directly via email (or to know who knows how long and keep checking): > Ah. It's a laptop, probably with an internal 1080p display Yes, exactly > but it's strange that this does not occur in xrandr output at all. Sorry, my bad, I only copied the part of xandr output about the display that doesn't work, and what is worse is I didn't specify that. > Could you please provide /var/log/Xorg.0.log and output when running "dmesg" command in a terminal? Right now I can't connect the monitor because I left my HDMI cable elsewhere. Will the file and the dmesg output be useful if I retrieve them now or should I do that when I have the monitor connected? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177568] VUL-0: CVE-2020-26945: mybatis: mishandles deserialization of object streams which could result in remote code execution
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177568 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|pmonrealgonzalez(a)suse.com |security-team(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177568] VUL-0: CVE-2020-26945: mybatis: mishandles deserialization of object streams which could result in remote code execution
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177568 https://bugzilla.suse.com/show_bug.cgi?id=1177568#c1 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmonrealgonzalez(a)suse.com --- Comment #1 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- Update to 3.5.6 submitted to Factory: https://build.opensuse.org/request/show/841573 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177629] -mbranch-protection=standard (PAuth + BTI) breaks find-debuginfo.sh
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177629 https://bugzilla.suse.com/show_bug.cgi?id=1177629#c5 Martin Liška <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet(a)arm.com Flags| |needinfo?(guillaume.gardet@ | |arm.com) --- Comment #5 from Martin Liška <martin.liska(a)suse.com> --- Btw. do we have another smaller package where you can see the same failure? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177430] dwz fails on testsuite for aarch64
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177430 https://bugzilla.suse.com/show_bug.cgi?id=1177430#c3 Michael Matz <matz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|christian.voegl(a)suse.com |tdevries(a)suse.com --- Comment #3 from Michael Matz <matz(a)suse.com> --- Luckily Tom maintains dwz upstream :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177629] -mbranch-protection=standard (PAuth + BTI) breaks find-debuginfo.sh
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177629 https://bugzilla.suse.com/show_bug.cgi?id=1177629#c4 Martin Liška <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.liska(a)suse.com Assignee|screening-team-bugs(a)suse.de |martin.liska(a)suse.com --- Comment #4 from Martin Liška <martin.liska(a)suse.com> --- Working on that right now.. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177273] Updating wicked 0.6.63 to 0.6.64 breaks tap0
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177273 Malcolm Lewis <malcolmlewis(a)cableone.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wicked-maintainer | |s(a)suse.de) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177273] Updating wicked 0.6.63 to 0.6.64 breaks tap0
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177273 https://bugzilla.suse.com/show_bug.cgi?id=1177273#c5 Malcolm Lewis <malcolmlewis(a)cableone.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Malcolm Lewis <malcolmlewis(a)cableone.net> --- (In reply to Rubén Torrero Marijnissen from comment #4) > Thanks for the logs Malcom, > > the configuration you are using does not configure tap0 as bridge port using > BRIDGE_PORTS='eth0 tap0' and thus wicked 0.6.64 correctly unenslaves it from > it's wrong master while 0.6.63 contained a bug not doing it. > > There are two possible solutions: > 1) use BRIDGE_PORTS='eth0 tap0' > 2) rm ifcfg-tap0 and create inside your qemu scripts (like libvirt is doing > it). Hi Rubén Many thanks for the pointer and fixes, I went for option 1 at this point, will move to option 2 later. Consider this bug report resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177629] -mbranch-protection=standard (PAuth + BTI) breaks find-debuginfo.sh
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177629 https://bugzilla.suse.com/show_bug.cgi?id=1177629#c3 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tdevries(a)suse.com --- Comment #3 from Richard Biener <rguenther(a)suse.com> --- Hmm, eventually commit acdf733634745548c0167c40bad80e6140ac2eeb Author: Szabolcs Nagy <szabolcs.nagy(a)arm.com> Date: Mon Apr 27 09:07:15 2020 +0100 aarch64: Fix .cfi_window_save with pac-ret [PR94515] On aarch64 -mbranch-protection=pac-ret reuses the dwarf opcode for window_save to mean "toggle the return address mangle state", but in the dwarf2cfi internal logic the state was not updated when an opcode was emitted, the currently present update logic is only valid for the original sparc use of window_save so a separate bool is used on aarch64 to track the state. This bug can cause the unwinder not to authenticate return addresses that were signed (or vice versa) which means a runtime crash on a pauth enabled system. gives a hint and consumers (DWZ / libdwarf) possibly need updating. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177531] xen project hypervisor + drbd -> cannot create "drbd" VBD type vm -reason-> rpm package 'drbd-utils' => /usr/lib/xen/scripts/block-common.sh broken migration to new directory '/usr/lib/xen/scripts/block-drbd'
by bugzilla_noreply＠suse.com 13 Oct '20

13 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177531 https://bugzilla.suse.com/show_bug.cgi?id=1177531#c4 --- Comment #4 from James Fehlig <jfehlig(a)suse.com> --- (In reply to nick wang from comment #3) > So either align with other packages to move all xen script to > "/usr/lib/xen/scripts/xxx" or move back the block drbd script to > "/etc/xen/scripts/". The problem is not many packages have moved content out of /etc. IMO there needs to be a concerted effort to do it in a coordinated fashion, otherwise you get bugs like this one. Any non-trivial package likely has relationships with other packages that are affected by such changes. Not to mention apparmor profiles and selinux policies that must also be adapted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0