December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205401] [Build 20221113] Error: Cannot update the dynamic configuration policy - no /sbin/netconfig
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205401 https://bugzilla.suse.com/show_bug.cgi?id=1205401#c15 Thomas Schmidt <tschmidt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tschmidt(a)suse.com --- Comment #15 from Thomas Schmidt <tschmidt(a)suse.com> --- In OBS, suseconnect-ng just succeeded to build on ppc64le: https://build.opensuse.org/package/live_build_log/systemsmanagement:SCC/sus… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c4 --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- That backtrace is trivial to fix: diff --git a/src/modules/Security.rb b/src/modules/Security.rb index 865addc..c58ca4b 100644 --- a/src/modules/Security.rb +++ b/src/modules/Security.rb @@ -687,7 +687,7 @@ module Yast # Security read dialog caption caption = _("Saving Security Configuration") - steps = 4 + steps = 5 Progress.New( caption, -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- That backtrace goes back until SLE-15-SP4 (no such backtrace with SLE-15-SP3). It does write the values to /etc/login.defs.d/70-yast.defs, though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205303] New: AppArmor prevents winbind from starting /usr/sbin/samba-gpupdate
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205303 Bug ID: 1205303 Summary: AppArmor prevents winbind from starting /usr/sbin/samba-gpupdate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Winbind needs to be able to execute /usr/sbin/samba-gpupdate in order to apply group policy, but it's being blocked by apparmor: [2022/11/09 11:02:36.004585, 0] ../../lib/util/util_runcmd.c:355(samba_runcmd_io_handler) /usr/sbin/samba-gpupdate: Failed to exec child - Permission denied [2022/11/09 11:02:36.006258, 3] ../../lib/util/util_runcmd.c:319(samba_runcmd_io_handler) samba_runcmd_io_handler: Child /usr/sbin/samba-gpupdate exited 255 [2022/11/09 11:02:36.006294, 0] ../../source3/winbindd/winbindd_gpupdate.c:182(gpupdate_cmd_done) gpupdate_cmd_done: gpupdate failed with exit status 255 type=AVC msg=audit(1668022211.285:471): apparmor="DENIED" operation="exec" profile="winbindd" name="/usr/sbin/samba-gpupdate" pid=9638 comm=74666F726B20776169746572 requested_mask="x" denied_mask="x" fsuid=0 ouid=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205863] Qt private API issue
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205863 https://bugzilla.suse.com/show_bug.cgi?id=1205863#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- How was this bug hit? What's the wanted effect of adding this patch? I'm asking because this bug does effectively not affect packages built for openSUSE and packages not built for openSUSE won't work even if this patch is applied. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205787] New: kernel-default-devel = 5.3.18-57 missing in repo meta data of Leap 15.3 (was: nvidia update 470.129.06 => 470.141.03 fails)
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205787 Bug ID: 1205787 Summary: kernel-default-devel = 5.3.18-57 missing in repo meta data of Leap 15.3 (was: nvidia update 470.129.06 => 470.141.03 fails) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: jsrain(a)suse.com CC: arvidjaar(a)gmail.com, joerg.kuehne(a)gmx.de, lubos.kocman(a)suse.com, ma(a)suse.com, mlin(a)suse.com, paul.pgp-7(a)gmx.com, stvdo(a)posteo.net Depends on: 1202116 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202116 +++ On openSUSE Leap 15.3 nvidia update (from https://download.nvidia.com/opensuse/leap/15.3) 470.129.06-lp153.57.1 => 470.141.03-lp153.53.1 fails due to: "nothing provides 'kernel-default-devel = 5.3.18-57'" The 15.3 kernel is currently at 5.3.18-150300.59.87.1 Full conflict log: #### YaST2 conflicts list - generated 2022-08-03 16:58:10 #### nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies [ ] do not install x11-video-nvidiaG05-470.141.03-lp153.53.1.x86_64 nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-glG05-470.141.03-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-computeG05-470.141.03-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies #### YaST2 conflicts list END ### -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1205915] New: GNOME fails to start
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205915 Bug ID: 1205915 Summary: GNOME fails to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: rjschwei(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- AFter upgrade from 15.3 to 15.4 GNOME fails to start. /var/log/messages contains the following information: gnome-session[3731]: gnome-session-binary[3731]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed gnome-session[3731]: gnome-session-binary[3731]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed gnome-session-binary[3731]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed gnome-session-binary[3731]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed [ 224.047413][ T3750] traps: gnome-shell[3750] trap int3 ip:7fca77260911 sp:7ffde4477c80 error:0 in libglib-2.0.so.0.7000.4[7fca77205000+131000] Unrecoverable failure in required component org.gnome.Shell.desktop dbus-daemon[3730]: [session uid=462 pid=3730] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 ailed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c2 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> --- I get the same backtrace on that same "Login Settings" dialog even on my workstation with the YaST:Head repository active, so it's easy to reproduce. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205918] [Build 20221130] yast2 security crashes
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205918 https://bugzilla.suse.com/show_bug.cgi?id=1205918#c1 --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- I see this backtrace in both calls to "yast2 security": 2022-12-01 02:45:17 <3> susetest(9049) [Ruby] modules/Progress.rb(UpdateProgressBar):606 Progress bar has only 4 steps, not 5. ------------- Backtrace begin ------------- .../modules/Progress.rb:606:in `UpdateProgressBar' .../modules/Progress.rb:661:in `NextStep' .../modules/Progress.rb:671:in `NextStage' .../modules/Security.rb:764:in `Write' .../include/security/complex.rb:50:in `WriteDialog' .../include/security/wizards.rb:133:in `block in SecuritySequence' .../vendor_ruby/3.1.0/yast/builtins.rb:546:in `eval' .../modules/Sequencer.rb:247:in `WS_run' .../modules/Sequencer.rb:318:in `block in Run' .../modules/Sequencer.rb:310:in `loop' .../modules/Sequencer.rb:310:in `Run' .../include/security/wizards.rb:148:in `SecuritySequence' .../vendor_ruby/3.1.0/yast/fun_ref.rb:33:in `call' .../vendor_ruby/3.1.0/yast/fun_ref.rb:33:in `call' .../modules/CommandLine.rb:1569:in `Run' .../clients/security.rb:153:in `main' .../clients/security.rb:264:in `<top (required)>' .../vendor_ruby/3.1.0/yast/wfm.rb:345:in `eval' .../vendor_ruby/3.1.0/yast/wfm.rb:345:in `run_client' .../vendor_ruby/3.1.0/yast/wfm.rb:206:in `call_builtin' .../vendor_ruby/3.1.0/yast/wfm.rb:206:in `call_builtin_wrapper' .../vendor_ruby/3.1.0/yast/wfm.rb:195:in `CallFunction' .../bin/y2start:68:in `<main>' ------------- Backtrace end --------------- -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204952] System crashes when booting first time after kernel update
by bugzilla_noreply＠suse.com 01 Dec '22

01 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1204952 https://bugzilla.suse.com/show_bug.cgi?id=1204952#c5 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #5 from Franck Bui <fbui(a)suse.com> --- (In reply to Ulrich Windl from comment #3) > OK, for today's kernel update I added a "panic=45" kernel parameter, but > then realized that the reboot is *not* caused by a kernel panic, but by some > systemd action! May I ask how you figured this out ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0