December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1133295] LTO: xterm build fails
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1133295 https://bugzilla.suse.com/show_bug.cgi?id=1133295#c4 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Li��ka <martin.liska(a)suse.com> --- It's using LTO now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1138836] LTO: sanlock build fails
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1138836 https://bugzilla.suse.com/show_bug.cgi?id=1138836#c1 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Li��ka <martin.liska(a)suse.com> --- It's using LTO now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133084] [META] GCC + LTO package failures
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1133084 Bug 1133084 depends on bug 1138836, which changed state. Bug 1138836 Summary: LTO: sanlock build fails https://bugzilla.suse.com/show_bug.cgi?id=1138836 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135211] LTO: inkscape build fails
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1135211 https://bugzilla.suse.com/show_bug.cgi?id=1135211#c1 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Martin Li��ka <martin.liska(a)suse.com> --- Fixed now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133084] [META] GCC + LTO package failures
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1133084 Bug 1133084 depends on bug 1135211, which changed state. Bug 1135211 Summary: LTO: inkscape build fails https://bugzilla.suse.com/show_bug.cgi?id=1135211 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180051] New: security:tls/gnutls: Bug
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180051 Bug ID: 1180051 Summary: security:tls/gnutls: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: vcizek(a)suse.com Reporter: jcnengel(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: pmonrealgonzalez(a)suse.com Found By: --- Blocker: --- With the recent change #43 a default priority "@SYSTEM" was introduced, however no configuration file defining this priority set is delivered with the package. This leads to a situation where applications using libgnutls fail upon setting default priorities. We should include for example this as /etc/crypto-policies/back-ends/gnutls.config: [priorities] SYSTEM = SECURE192:+SECURE128:-VERS-ALL:+VERS-TLS1.2:+VERS-TLS1.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1177527] New: hplip upgrade message points to bugzilla.novell.com
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1177527 Bug ID: 1177527 Summary: hplip upgrade message points to bugzilla.novell.com Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: msvec(a)suse.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- Just noticed this message in the log: /hp-upgrade[1365]: hp-upgrade[1365]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.novell.com/show_bug.cgi?id=853405 - if you like to upgrade HPLIP, use an openSUSE software package manager like YaST or zypper. It should point to bugzilla.suse.com Plus, it would be nice to make the message a bit clearer, e.g. by saying "HPLIP built-in automatic upgrade functionality is disabled..." -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1144527] Virtualization/libvirt: Bug Call to virDomainCreateWithFlags failed: internal error: Process exited prior to exec: libvirt: error : Failed to bind /dev/null on to /var/run/libvirt/qemu/496-tests_testing-15.0-a.dev/null: Permission denied
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1144527 https://bugzilla.suse.com/show_bug.cgi?id=1144527#c9 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dcermak(a)suse.com) | --- Comment #9 from Dan ��erm��k <dcermak(a)suse.com> --- (In reply to James Fehlig from comment #8) > (In reply to Dan ��erm��k from comment #7) > > type=AVC msg=audit(1607005863.720:1043): apparmor="DENIED" operation="mount" > > info="failed mntpnt match" error=-13 profile="libvirtd" > > name="/run/libvirt/qemu/3-tests_15.2-arm.dev/null" pid=23462 comm="libvirtd" > > srcname="/dev/null" flags="rw, bind" > > I'm not an apparmor expert, but a rough translation: the libvirtd apparmor > profile denied 'mount -o rw,bind ...' > > > So do libvirt's apparmor rules need updating? > > Probably. If I understand the mount rule stuff in apparmor.d man page, > allowing the bind option should help. E.g. can you see if the following > change in /etc/apparmor.d/usr.sbin.libvirtd helps (reload the profile with > 'apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd' after making the > change) > > --- usr.sbin.libvirtd.orig 2020-12-07 16:50:43.027846340 -0700 > +++ usr.sbin.libvirtd 2020-12-07 16:51:53.093047089 -0700 > @@ -30,7 +30,7 @@ > capability sys_resource, > > mount options=(rw,rslave) -> /, > - mount options=(rw, nosuid) -> /{var/,}run/libvirt/qemu/*.dev/, > + mount options=(rw, nosuid, bind) -> /{var/,}run/libvirt/qemu/*.dev/, > umount /{var/,}run/libvirt/qemu/*.dev/, > > # libvirt provides any mounts under /dev to qemu namespaces I have applied your patch and after a reboot the issue no longer appears, however I also have not found any mention of mount in /var/log/audit.log. I am not sure if that means that libvirt has not tried a bind mount? I wonder what would make it trigger that. Should we forward this to the libvirt and/or apparmor maintainers? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133084] [META] GCC + LTO package failures
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1133084 Bug 1133084 depends on bug 1144032, which changed state. Bug 1144032 Summary: LTO: Segmentation fault when trying to link gmsh https://bugzilla.suse.com/show_bug.cgi?id=1144032 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144032] LTO: Segmentation fault when trying to link gmsh
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1144032 https://bugzilla.suse.com/show_bug.cgi?id=1144032#c7 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #7 from Martin Li��ka <martin.liska(a)suse.com> --- Should be fixed now and the package uses -flto now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0