January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206957] lua-lmod Permission denied in init/bash
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206957 https://bugzilla.suse.com/show_bug.cgi?id=1206957#c6 --- Comment #6 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Ludwig Nussel from comment #5) > No it's not a duplicate. Ah OK. My bad then, yes. > lmod is doing nasty things here and pollutes the > shell environment via /etc/profile.d/lmod.sh. This seems to be true. But there is a regressions somewhere in lmod, lesscode or apparmor, as this was not there until the last update. > My strong advice would be not > do that. Instead there could be eg. only something like an "lmod-activate" > or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on > demand* rather than for each and every shell of each and every user. No idea here, but seems to be a core feature of lmod to enable / disable module without user interaction, nor logout / login routine. I guess that you get dragged here because one change in the apparmor spec that seems unrelated (usermerge). The other package the changed was lmod. Less did no change recently. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206957] lua-lmod Permission denied in init/bash
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206957 https://bugzilla.suse.com/show_bug.cgi?id=1206957#c5 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |lnussel(a)suse.com Resolution|DUPLICATE |--- --- Comment #5 from Ludwig Nussel <lnussel(a)suse.com> --- No it's not a duplicate. lmod is doing nasty things here and pollutes the shell environment via /etc/profile.d/lmod.sh. My strong advice would be not do that. Instead there could be eg. only something like an "lmod-activate" or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on demand* rather than for each and every shell of each and every user. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206367] systemd-status-mail does not send mail....
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206367 https://bugzilla.suse.com/show_bug.cgi?id=1206367#c8 --- Comment #8 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Axel Braun from comment #7) > (In reply to Thorsten Kukuk from comment #6) > > It's a configuration problem, not code problem. > > Sorry to reopen, but if you say 'you have to modify the script' comment#5 it > is not just config. So what script is expected to be modified? > I tried to add the parameter to /etc/mailx.rc, but that did not help either What you want is support to setup a complex null client mail system. Sorry, but this is not doable here. Your choices are: - setup a working, local mail system with postfix or sendmail yourself or - try MAILX_OPTIONS (https://manpages.opensuse.org/Tumbleweed/systemd-status-mail/systemd-status…) Your mail setup is not a problem of systemd-status-mail, this tool expects a working mail setup (like e.g. cron does, too) and is no replacement for it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206965] New: Cockpit: No login possible with modern browser due to bug in outdated cockpit version.
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206965 Bug ID: 1206965 Summary: Cockpit: No login possible with modern browser due to bug in outdated cockpit version. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: nwslttr(a)cwld.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest available version ist 276. Witch ist outdated and buggy. therefore it is not possible to login with modern browsers. See also: https://cockpit-project.org/blog/login-issues.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206757] AUDIT-WHITELIST: NetworkManager-libreswan: move dbus system.d file to /usr
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206757 http://bugzilla.opensuse.org/show_bug.cgi?id=1206757#c4 --- Comment #4 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1206757) was mentioned in https://build.opensuse.org/request/show/1057042 Factory / NetworkManager-libreswan -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1167780] New: MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1167780 Bug ID: 1167780 Summary: MicroOS images don't update grub if booted without EFI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- The .qcow2 images are meant to work fine on systems with EFI (optionally secure boot) and without, so they have both i386-pc and x86_64-efi targets of grub2 installed by kiwi during image building. Kiwi sets LOADER_TYPE="grub2-efi" for this. When booting the image without EFI though, this is not changed by anything and so update-bootloader only manages the x86_64-efi target of grub2. As the grub.cfg file is in the same location, there aren't any immediate issues, but it means that grub is never updated in those deployments. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1190256] New: Keyboard not working on ASUS Zenbook 14 UM425UA
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190256 Bug ID: 1190256 Summary: Keyboard not working on ASUS Zenbook 14 UM425UA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mkrapp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new ASUS Zenbook 14 UM524UA. Unfortunately keyboard is not at all working in latest Tumbleweed with kernel 5.14.0-1-default. I: Bus=0018 Vendor=04f3 Product=3134 Version=0100 N: Name="ASUE140A:00 04F3:3134 Keyboard" P: Phys=i2c-ASUE140A:00 S: Sysfs=/devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input8 U: Uniq= H: Handlers=sysrq kbd leds event5 B: PROP=0 B: EV=120013 B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe B: MSC=10 B: LED=1f It's recognized during boot: > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input3 > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input4 > Aug 31 20:00:01 localhost kernel: input: ASUE140A:00 04F3:3134 Keyboard as /devices/platform/AMDI0010:03/i2c-0/i2c-ASUE140A:00/0018:04F3:3134.0001/input/input5 > Aug 31 20:00:01 localhost kernel: hid-generic 0018:04F3:3134.0001: input,hidraw0: I2C HID v1.00 Mouse [ASUE140A:00 04F3:3134] on i2c-ASUE140A:00 but not working at all. no events created when pressing/releasing keys. The touchpad works fine, albeit I didn't try to get the extra function working (numpad on touchpad) yet. I'll attach hwinfo and journal in a minute. Any idea how I can get the keyboard working? -- You are receiving this mail because: You are on the CC list for the bug.

1 65

[Bug 1206367] systemd-status-mail does not send mail....
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206367 https://bugzilla.suse.com/show_bug.cgi?id=1206367#c7 --- Comment #7 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Thorsten Kukuk from comment #6) > It's a configuration problem, not code problem. Sorry to reopen, but if you say 'you have to modify the script' comment#5 it is not just config. So what script is expected to be modified? I tried to add the parameter to /etc/mailx.rc, but that did not help either Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206869] azure-cli-core requires python3-packaging < 22.0
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206869 https://bugzilla.suse.com/show_bug.cgi?id=1206869#c2 --- Comment #2 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Thank you Adrian! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206927] New: yupdate and the D-Installer
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206927 Bug ID: 1206927 Summary: yupdate and the D-Installer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The yupdate script cannot update the D-Installer, it would be nice to update it to support also this use case. -- You are receiving this mail because: You are on the CC list for the bug.

1 2