June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095749] Error message 'repository managed by service "' when managing repos via YaST
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095749 http://bugzilla.suse.com/show_bug.cgi?id=1095749#c3 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang(a)rosenauer.org Flags| |needinfo?(wolfgang@rosenaue | |r.org) --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- So the message per se is probably valid (well, is it? Is that repo indeed managed by a service?), but the placeholder for the service is empty which is a real bug, albeit probabably a minor one. Wolfgang, please describe what you did (doesn't need to be in great detail, just a rough idea). Is it plausible that this repo is managed by a service? Or what kind of repo is it? What does "zypper lr" say about that repo? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095749] Error message 'repository managed by service "' when managing repos via YaST
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095749 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|strange error message when |Error message 'repository |managing repos via YaST |managed by service "' when | |managing repos via YaST -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095749] strange error message when managing repos via YaST
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095749 http://bugzilla.suse.com/show_bug.cgi?id=1095749#c2 --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- This looks like the code location throwing that message: https://github.com/yast/yast-packager/blob/master/src/lib/packager/clients/… "git blame" says it's introduced by this commit: https://github.com/yast/yast-packager/commit/18383b497d914f0a7388b0c3f60e14… which belongs to this pull request: https://github.com/yast/yast-packager/pull/346 which was the fix for bug #1078323. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092543] New: GCC 8: xen build fails
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1092543 Bug ID: 1092543 Summary: GCC 8: xen build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1092539] WSL LEAP image contains packages from home repos
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1092539 http://bugzilla.suse.com/show_bug.cgi?id=1092539#c9 --- Comment #9 from Cristian Rodríguez <crrodriguez(a)opensuse.org> --- (In reply to Cédric Bosdonnat from comment #6) > This is a backport of a patch for aaa_base to avoid messing with the PATH > set by WSL. Hi Cedric..yes.. I figured that out.. the point is .. images or releases said to be provided by SUSE or the openSUSE project must only contain packages signed by either official keys. I know you are not malicious party, but no such trust can be given or extended to to any home repository at all, thus this is in violation of the established security model of releases. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095749] strange error message when managing repos via YaST
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095749 http://bugzilla.suse.com/show_bug.cgi?id=1095749#c1 --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- Translation: Repository 'mozilla-beta' is managed by service ". Your manual changes might be reset by the next service update! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092309] leap 15/tw isos have an incorrect el-torito (uefi) boot entry
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1092309 http://bugzilla.opensuse.org/show_bug.cgi?id=1092309#c12 Adrian Schröter <adrian(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #12 from Adrian Schröter <adrian(a)suse.com> --- the efi boot sort file was only created as side effect of promo code. fixed that in request 613992 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1091968] New: Migrated/upgraded systems have SuSEFirewall2 enabled which is not supported anymore
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1091968 Bug ID: 1091968 Summary: Migrated/upgraded systems have SuSEFirewall2 enabled which is not supported anymore Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/667584/modules/firew all_enabled/steps/1 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: jsrain(a)suse.com CC: jeriveramoya(a)suse.com, riafarov(a)suse.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1091649 +++ ## Observation When migrating older products which had SuSEFirewall2 as default to a current product version which have firewalld by default then the SuSEFirewall2 is preserved which is not supported anymore. See for example scenario opensuse-15.0-DVD-x86_64-update_Leap_42.3_gnome@64bit-2G in [firewall_enabled](https://openqa.opensuse.org/tests/667584/modules/firewall… showing that SuSEFirewall2 is still active. ## Reproducible * Upgrade pre-15 distributions (or corresponding TW version) with enabled SuSEFirewall2 to corresponding 15-based version * `SuSEfirewall2 status` reports that the firewall is still running ## Expected result * **E1:** An unsupported firewall should not continue to run silently in the background. Some error message or information to the user should be shown. ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=15.0&distri=opensu… https://openqa.suse.de/tests/1657059#step/firewall_enabled/1 shows the corresponding SuSEFirewall2 for SLE15 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1095670] Problem with suid pgms on Leap-15.0
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1095670 http://bugzilla.opensuse.org/show_bug.cgi?id=1095670#c11 --- Comment #11 from L. A. Walsh <suse(a)tlinx.org> --- I don't understand how " POS36-C: "Consequently, it is recommended that a program relinquish > supplementary group IDs immediately before relinquishing root privileges." would affect the original submitter. The problem was the loss of supplementary group ID's upon becoming root, where as the POS36C section that was quoted says to relinquish such ID's before relinquishing root privs. As an aside -- since it was an SUID program it would relinquish it's root privs upon exit, so it seems pointless to relinquish any groups as the process goes away. Maybe in some other circumstance that wouldn't be the case, but the 1st point still stands -- the POS36c statement above doesn't say to relinquish groups upon becoming root, but on transitioning away from root. Ideally, the groups active at the beginning of a root session would be those retained when transitioning away from root. I.e this would put things back exactly the way before the UID change. No doubt it is a fear of people not getting it right and having additional groups added as root that propagate to a user. However, reiterating: the above POS36 **recommendation** (not requirement), only would seem to apply when transitioning away from root -- so the original submitter should not have encountered a problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1094085] Cannot install nvidia drivers. ksym(default:vfree)
by bugzilla_noreply＠novell.com 04 Jun '18

04 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1094085 http://bugzilla.suse.com/show_bug.cgi?id=1094085#c3 --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- Marti, still available and interested? -- You are receiving this mail because: You are on the CC list for the bug.

1 0