January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1178859] apparmor startup produce warning Cache: failed to add read only location '/usr/share/apparmor/cache'
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1178859 http://bugzilla.opensuse.org/show_bug.cgi?id=1178859#c4 Goldwyn Rodrigues <rgoldwyn(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Goldwyn Rodrigues <rgoldwyn(a)suse.com> --- Closing as RESOLVED-UPSTREAM since it does not happen anymore. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180592] Qt plug-in could not be loaded.
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180592 https://bugzilla.suse.com/show_bug.cgi?id=1180592#c4 Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez(a)suse.com, | |Markus.Elfring(a)web.de Flags| |needinfo?(Markus.Elfring@we | |b.de) --- Comment #4 from Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> --- Markus, could you please attach the YaST logs [1]? Maybe this issue is related to this other report [2]. Thanks! [1] https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_…. [2] https://bugzilla.suse.com/show_bug.cgi?id=1179862 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1082027] New: gcc7 can not build clisp even with --enable-portability (no memory/stack changes)
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1082027 Bug ID: 1082027 Summary: gcc7 can not build clisp even with --enable-portability (no memory/stack changes) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since gcc7 it is not possible anymore to build clisp even with disabling assembler as well stack and memory layout with the configure option --enable-portability ... note that this is the only architecture which does not build. Hence upstream has the opinion that our gcc7 is somehow broken as on Debian s390x with an older gcc the clisp-2.49.92 does build. Is there any older gcc available for Factory/Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1180610] perf does not load symbols from libantlr4
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180610 http://bugzilla.opensuse.org/show_bug.cgi?id=1180610#c12 --- Comment #12 from Richard Biener <rguenther(a)suse.com> --- (In reply to Martin Li��ka from comment #11) > (In reply to Richard Biener from comment #10) > > So to clarify - when strip strips a section from ELF it also needs to remove > > any symbols pointing to it since else they might end up pointing into wrong > > sections or to sections that do not exist (out of bound section index) or to > > places outside of the (invalid) section. > > > > eu_strip gets this "right" (with limited testing of a simple exec compiled > > with -flto and stripped with eu-strip --strip-debug), strip --strip-debug > > as well (binutils 2.35.1). > > How do you create the separate debug info ELF file? Note that the > problematic symbol is in the separate binary: > > $ gcc foo.c -O2 -g -flto -shared -o libfoo.so > $ objcopy --only-keep-debug libfoo.so debug.so > $ readelf -s --wide debug.so | grep foo.c > 60: 0000000000000067 0 NOTYPE LOCAL DEFAULT 25 foo.c.cf7807ca I don't - I checked that strip --strip-debug does the correct thing. So there must be code to handle symbols refering to the debug. Because objcopy --only-keep-debug keeps the source intact. You need an additional step to strip libfoo.so from its debug info and that's where things go wrong it seems. > > > > So sth is bogus in the course of events performing the stripping? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1045901] strongswan 5.3.5: No connection possible!
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1045901 https://bugzilla.suse.com/show_bug.cgi?id=1045901#c10 Manuel Buil <mbuil(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Manuel Buil <mbuil(a)suse.com> --- (In reply to Michael Hirmke from comment #9) > (In reply to Manuel Buil from comment #8) > > Hey, I have inherited strongswan as Madhu left the company. I see that this > > bug did not have any activity for years and it refers to an old version of > > strongswan, can we close it? Thanks > > Thx for asking, but for me the problem has been solved. Then, we can close it :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180610] perf does not load symbols from libantlr4
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180610 http://bugzilla.opensuse.org/show_bug.cgi?id=1180610#c11 --- Comment #11 from Martin Li��ka <martin.liska(a)suse.com> --- (In reply to Richard Biener from comment #10) > So to clarify - when strip strips a section from ELF it also needs to remove > any symbols pointing to it since else they might end up pointing into wrong > sections or to sections that do not exist (out of bound section index) or to > places outside of the (invalid) section. > > eu_strip gets this "right" (with limited testing of a simple exec compiled > with -flto and stripped with eu-strip --strip-debug), strip --strip-debug > as well (binutils 2.35.1). How do you create the separate debug info ELF file? Note that the problematic symbol is in the separate binary: $ gcc foo.c -O2 -g -flto -shared -o libfoo.so $ objcopy --only-keep-debug libfoo.so debug.so $ readelf -s --wide debug.so | grep foo.c 60: 0000000000000067 0 NOTYPE LOCAL DEFAULT 25 foo.c.cf7807ca > > So sth is bogus in the course of events performing the stripping? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180537] [Build 20210103] [s390x] Can't find YCP client component wrapper_storage
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180537 https://bugzilla.suse.com/show_bug.cgi?id=1180537#c7 --- Comment #7 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #6) > > That was done based on a version of the code that didn't contain the > adaptations I forgot the link to prove that: https://github.com/yast/yast-packager/commit/6a6b1764feabec3c102f7df1f05ae2… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180610] perf does not load symbols from libantlr4
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180610 http://bugzilla.opensuse.org/show_bug.cgi?id=1180610#c10 --- Comment #10 from Richard Biener <rguenther(a)suse.com> --- So to clarify - when strip strips a section from ELF it also needs to remove any symbols pointing to it since else they might end up pointing into wrong sections or to sections that do not exist (out of bound section index) or to places outside of the (invalid) section. eu_strip gets this "right" (with limited testing of a simple exec compiled with -flto and stripped with eu-strip --strip-debug), strip --strip-debug as well (binutils 2.35.1). So sth is bogus in the course of events performing the stripping? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c31 --- Comment #31 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #30) > (In reply to Fabian Vogt from comment #29) > > > > I did another try with also patching out the product features condition and > > then resume= appeared in the cmdline. > > > > Using /dev/disk/by-uuid/, so this bug is confirmed fixed! > > But, are you sure is using the correct UUID? Because we suspect that > (although YaST itself seems to be doing its part) this is in fact broken > because libstorage-ng is not honoring the UUID set by YaST. See bug#1180560. I didn't actually run the installation so far, just checked the grub settings in the overview. I just completed one and the UUID of the swap partition matches the one in /etc/fstab as well as resume= in /proc/cmdline. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180537] [Build 20210103] [s390x] Can't find YCP client component wrapper_storage
by bugzilla_noreply＠suse.com 07 Jan '21

07 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180537 https://bugzilla.suse.com/show_bug.cgi?id=1180537#c6 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com --- Comment #6 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- That path of code was removed a long, long time ago, when it still was located in clients/software_proposal.rb. https://github.com/yast/yast-packager/pull/261/commits/3344dfcd281e963b37fa… But it looks like around the same time, the code was moved from that initial location to lib/packager/clients/software_proposal.rb That was done based on a version of the code that didn't contain the adaptations, so the code path was in practice not really deleted (or it was restored, depends on how you look at it). It's weird that such error had remained unnoticed for so long. -- You are receiving this mail because: You are on the CC list for the bug.

1 0