February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208221] Remove NIS support from sendmail
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208221 http://bugzilla.opensuse.org/show_bug.cgi?id=1208221#c1 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com Flags| |needinfo?(kukuk(a)suse.com) --- Comment #1 from Dr. Werner Fink <werner(a)suse.com> --- What is about NISPLUS? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207949] Nautilus: the toggle to set file executable permissions is missing (via NFS)
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207949 https://bugzilla.suse.com/show_bug.cgi?id=1207949#c3 --- Comment #3 from Alynx Zhou <alynx.zhou(a)suse.com> --- So I think its actually a feature that they now only show the toggle on some mime types: <https://gitlab.gnome.org/GNOME/nautilus/-/blob/master/src/nautilus-properti…>. However, if you still have questions please tell me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207949] Nautilus: the toggle to set file executable permissions is missing (via NFS)
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207949 https://bugzilla.suse.com/show_bug.cgi?id=1207949#c2 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou(a)suse.com --- Comment #2 from Alynx Zhou <alynx.zhou(a)suse.com> --- Hi, could you please tell me which kind of files does not have this toggle? It seems that only some kinds of files (like `.py`, `.txt`) have this toggle on my machine, if you got the same result, I could confirm we get the same problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206774] saa7146 driver is not present in 6.1 kernel
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206774 https://bugzilla.suse.com/show_bug.cgi?id=1206774#c11 --- Comment #11 from Jiri Slaby <jslaby(a)suse.com> --- And now also the budget modules +CONFIG_DVB_BUDGET_CORE=m +CONFIG_DVB_BUDGET=m +CONFIG_DVB_BUDGET_CI=m -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205169] New: With sudo the XDG variables point to SUDO_UID aka calling user instead of 0 aka root
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205169 Bug ID: 1205169 Summary: With sudo the XDG variables point to SUDO_UID aka calling user instead of 0 aka root Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: zimtsui(a)gmail.com Depends on: 1205109 Found By: --- Blocker: --- Note that the description below is not fully correct: /suse/werner> sudo printenv | grep XDG XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session11 XDG_MENU_PREFIX=fvwm- XDG_CONFIG_HOME=/suse/werner/.config XDG_SEAT=seat0 XDG_SESSION_DESKTOP= XDG_SESSION_TYPE=x11 XDG_CURRENT_DESKTOP=FVWM XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XDG_CACHE_HOME=/suse/werner/.cache/noether:0 XDG_SESSION_CLASS=user XDG_DESKTOP_DIR=/suse/werner/Desktop XDG_SESSION_COOKIE=noether XDG_VTNR=7 XDG_SESSION_ID=733 XDG_RUNTIME_DIR=/run/user/223 XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg that is sudo does *not* remove the XDG variables from the ennvirnment nor does the pam_systemd module set the correct XDG variables. +++ This bug was initially created as a clone of Bug #1205109 +++ # Description Emacs checks whether environment variable `XDG_RUNTIME_DIR` exists to determine where a certain socket file should be placed. If `XDG_RUNTIME_DIR` doesn't exist, emacs will fallback to some other location. See <https://git.savannah.gnu.org/cgit/emacs.git/tree/lib-src/emacsclient.c?h=em…> `sudo` defaults to unset all environment variables and set some certain ones. So any program run by `sudo` should miss `XDG_RUNTIME_DIR` in its environment. If I run `sudo emacs-nox`, everything goes expectedly. But if I run `sudo emacs`, emacs prompts `Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/0" not available: No such file or directory`. # Possible reason The binary `/usr/bin/emacs` is not built from emacs source, but made by the SUSE package maintainer. The binary checks whether it's run in terminal or X to determine whether it should exec `emacs-nox` or `emacs-x11`. The `/usr/bin/emacs` binary defines an environment variable `XDG_RUNTIME_DIR` as `/run/user/<USER_ID>` arbitrarily. But `/run/user/0` doesn't exist because it should be created by `/etc/profile` in a login shell. And `sudo` doesn't spawn a new login shell. # Reproduction 1. Install `emacs` and `emcas-nox` from zypper, and don't install `emacs-x11`. 1. Restart your computer and don't login as root in any tty, but login as a regular user. 1. `sudo emacs` 1. Quit emacs. 1. You will see the prompt. # Versions openSUSE Leap 15.4 Emacs 27.2 Sudo 1.9.9 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208173] Can't boot devel:RISCV:Factory:Contrib:StarFive:VisionFive2/JeOS-starfivevisionfive2, "sbi_trap_error: hart0: trap handler failed (error -2)"
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208173 https://bugzilla.suse.com/show_bug.cgi?id=1208173#c1 --- Comment #1 from Chester Lin <chester.lin(a)suse.com> --- (In reply to Aaron Puchert from comment #0) > This is not technically Tumbleweed, so I open with lower severity. > > This is on a VisionFive 2 V1.3B, with u-boot-spl.bin.normal.out and > visionfive2_fw_payload.img from [1], and JeOS-starfivevisionfive2 on an SD > card. The initial boot produces the error mentioned in the Wiki [2]: > > Loading Linux 6.2.0-rc7-12-default ... > Loading initial ramdisk ... > EFI stub: Booting Linux Kernel... > Unhandled exception: Store/AMO access fault > EPC: 00000000fff47a98 RA: 00000000fff8684a TVAL: 0000000040000000 > EPC: 0000000040201a98 RA: 000000004024084a reloc adjusted > > [...] > UEFI image [0x00000000fe460000:0x00000000fe716fff] > '/efi\boot\bootriscv64.efi' > UEFI image [0x00000000cb23a000:0x00000000ccf42fff] > > Ok, let's mark that region as reserved as the Wiki says: > > StarFive # fdt addr ${fdtcontroladdr}; fdt rsvmem add 0x40000000 0x00001000 > StarFive # boot > ## Warning: defaulting to text format > ## Error: "boot2" not defined > switch to partitions #0, OK > mmc1 is current device > Scanning mmc 1:1... > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Card did not respond to voltage select! : -110 > ** Unable to read file ubootefi.var ** > Failed to load EFI variables > Found EFI removable media binary efi/boot/bootriscv64.efi > 2846720 bytes read in 122 ms (22.3 MiB/s) > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > Welcome to GRUB! > [...] > Loading Linux 6.2.0-rc7-12-default ... > Loading initial ramdisk ... > EFI stub: Booting Linux Kernel... > EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path > EFI stub: Using DTB from configuration table > EFI stub: Exiting boot services... > clk u5_dw_i2c_clk_core already disabled > clk u5_dw_i2c_clk_apb already disabled > sbi_trap_error: hart0: trap handler failed (error -2) > sbi_trap_error: hart0: mcause=0x0000000000000005 mtval=0x0000000040047060 > sbi_trap_error: hart0: mepc=0x0000000040004cac mstatus=0x0000000200001800 > sbi_trap_error: hart0: ra=0x0000000040009ee2 sp=0x0000000040046f10 > sbi_trap_error: hart0: gp=0x0000000000000000 tp=0x0000000040047000 > sbi_trap_error: hart0: s0=0x0000000040046f20 s1=0x0000000040047000 > sbi_trap_error: hart0: a0=0x0000000040047060 a1=0x0000000000000002 > sbi_trap_error: hart0: a2=0x0000000000000000 a3=0x0000000000000019 > sbi_trap_error: hart0: a4=0x0000000000000001 a5=0x0000000040047060 > sbi_trap_error: hart0: a6=0x00000000400470a8 a7=0x0000000000000004 > sbi_trap_error: hart0: s2=0x00000000400241a8 s3=0x0000000000000000 > sbi_trap_error: hart0: s4=0x0000000000000000 s5=0x0000000040028000 > sbi_trap_error: hart0: s6=0x0000000040028020 s7=0x0000000000000000 > sbi_trap_error: hart0: s8=0x000000000000001c s9=0x0000000040034ab0 > sbi_trap_error: hart0: s10=0x0000000000000000 s11=0x0000000000000000 > sbi_trap_error: hart0: t0=0x0000000000000000 t1=0x0000000000000000 > sbi_trap_error: hart0: t2=0x0000000000000000 t3=0x0000000000002000 > sbi_trap_error: hart0: t4=0x0000000000000000 t5=0x0000000000000000 > sbi_trap_error: hart0: t6=0x0000000000000000 > Hi, Could you add 'earlycon=sbi' and then remove the 'loglevel' limit from the kernel command line in grub2? It could help us to check what happened since the earlycon is disabled by default. Thanks. > and then it hangs. Now OpenSBI tells me this: > > Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I) > Domain0 Region01 : 0x0000000040000000-0x000000004007ffff () > Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X) > > so maybe the region wasn't big enough? But a size of 0x80000 doesn't do it > either, and the error is a different one. > > Booting the SDK kernel (e.g. image.fit from [1]) with the instructions given > in the repository README (i.e. via tftpboot) works fine. > > Out of curiosity, I tried to switch roles: put the SDK kernel on the SD > card, and tried tftpboot with the openSUSE kernel. The SDK kernel on the SD > card produces pretty much the same sbi_trap_error, whereas the openSUSE > kernel via tftp can at least start itself and some services. It's then > missing things, because it expects a disk around, but that's expected: > > StarFive # setenv bootfile vmlinuz; setenv fileaddr a0000000; setenv > fdtcontroladdr 0xffffffffffffffff > StarFive # setenv kernel_comp_addr_r 0xb0000000; setenv kernel_comp_size > 0x10000000; > StarFive # tftpboot ${fdt_addr_r} jh7110-starfive-visionfive-2-vb.dtb > [...] > StarFive # tftpboot ${kernel_addr_r} Image-6.2.0-rc7-12-default > [...] > StarFive # tftpboot ${ramdisk_addr_r} initrd-6.2.0-rc7-12-default > [...] > StarFive # run chipa_set_linux > StarFive # booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} > ## Flattened Device Tree blob at 46000000 > Booting using the fdt blob at 0x46000000 > Using Device Tree in place at 0000000046000000, end 0000000046008140 > > Starting kernel ... > > [ 0.000000][ T0] Linux version 6.2.0-rc7-12-default (geeko@buildhost) > (gcc (SUSE Linux) 12.2.1 20230124 [revision > 193f7e62815b4089dfaed4c2bd34fd4f10209e27], GNU ld (GNU Binutils; openS) > [ 0.000000][ T0] OF: fdt: Ignoring memory range 0x40000000 - 0x40200000 > [ 0.000000][ T0] Machine model: StarFive VisionFive 2 VB > [...] > [ 0.000000][ T0] CPU with hartid=0 is not available > [ 0.000000][ T0] CPU with hartid=0 is not available > [ 0.000000][ T0] CPU with hartid=0 is not available > [...] > [ 19.230279][ T711] dracut: FATAL: No root device found > [ 19.235549][ T711] dracut: Refusing to continue > > But that's expected. So I don't think there is anything wrong with the > kernel. It seems to be an issue either with the firmware or with the > bootloader. For what it's worth, I see that > devel:RISCV:Factory:Contrib:StarFive:VisionFive2 has some kind of u-boot, > but I can't find a pendant for visionfive2_fw_payload.img. > > Likely I'm just doing something wrong though and maybe the documentation > could be improved a bit. > > [1] https://github.com/starfive-tech/VisionFive2/releases/tag/VF2_v2.8.0 > [2] https://en.opensuse.org/HCL:VisionFive2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200544] New: xbell no longer working
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200544 Bug ID: 1200544 Summary: xbell no longer working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: agesen(a)cs.stanford.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I updated from 15.3 to 15.4 and all is well, well :-) mostly. Sound works when playing video in firefox, when playing musing with mplayer, etc. But xbell is no longer to be heard. I miss "vi" baking a beep when I hit escape at the wrong time. I miss xbiff making a sound when an email arrives (there is no sound but it still changes the icon to flag-up). How may we go about debugging missing "system sound" (or whatever it is? Just to clarify, I have checked pavucontrol and tried fiddling with all the sliders. No difference. Please let me know if I can upload log files that may help. Thanks, Ole Dell Inspiron from 2011ish. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1208204] nvidia G04 drivers: Broken behaviour with glibc 2.37 update
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208204 https://bugzilla.suse.com/show_bug.cgi?id=1208204#c16 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |DUPLICATE Flags|needinfo?(paka(a)opensuse.org | |) | --- Comment #16 from Stefan Dirsch <sndirsch(a)suse.com> --- Let's close as duplicate. *** This bug has been marked as a duplicate of bug 1208198 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208204] nvidia G04 drivers: Broken behaviour with glibc 2.37 update
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208204 https://bugzilla.suse.com/show_bug.cgi?id=1208204#c15 --- Comment #15 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks for finding this. So does this fix the issue for you? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208204] nvidia G04 drivers: Broken behaviour with glibc 2.37 update
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208204 https://bugzilla.suse.com/show_bug.cgi?id=1208204#c14 --- Comment #14 from Stefan Dirsch <sndirsch(a)suse.com> --- Nevertheless I assume you suffer from the same issues Marcus does in boo#1208198 (which I could easily reproduce with G04 and glibc 2.37 on Tumbleweed). -- You are receiving this mail because: You are on the CC list for the bug.

1 0