November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204720] wget dies writing too long filename
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204720 https://bugzilla.suse.com/show_bug.cgi?id=1204720#c6 Valentin Lefebvre <valentin.lefebvre(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Valentin Lefebvre <valentin.lefebvre(a)suse.com> --- Indeed, the patch noted in comment#1, did not take the use case when option "dirstruct" is not set. I will update this one to fix this use case and submit it to SLE-15:Update in first step, and it will be available ASAP to Leap15.4 :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189172] USB CDC-ACM device keeps disconnecting and reconnecting
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1189172 https://bugzilla.suse.com/show_bug.cgi?id=1189172#c9 --- Comment #9 from Marc Balmer <marc(a)msys.ch> --- It seem somehow to be related to the USB controller in use. On an IBM SurePOS 300 with UHCI, I have not issues. On EHCI and XHCI controllers it seems not to work. Also there are two hardware versions of the 1472g base station that use different CPUs. So there is quite some variations to check... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204762] New: glibc error "Cannot stat: No such file or directory" during build of git
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204762 Bug ID: 1204762 Summary: glibc error "Cannot stat: No such file or directory" during build of git Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- git can not build with glibc 2.36 on openSUSE Tumbleweed for s390x. We are receiving following error messages: [ 1989s] cpio: glibc-2.36/bits/sockaddr.h: Cannot stat: No such file or directory [ 1989s] cpio: glibc-2.36/bits/stdint-intn.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/bits/stdint-uintn.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/abi-note.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/init.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/elf/elf.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/include/dso_handle.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/include/stdlib.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/inet/netinet/in.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/posix/bits/types.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/stdlib/: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/stdlib/atexit.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/crti.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/crtn.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/start.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/unix/sysv/linux/bits/socket.h: Cannot stat: No such file or directory It seems, that default libraries can not be found. Link to the build log: [ 1989s] cpio: glibc-2.36/bits/sockaddr.h: Cannot stat: No such file or directory [ 1989s] cpio: glibc-2.36/bits/stdint-intn.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/bits/stdint-uintn.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/abi-note.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/csu/init.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/elf/elf.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/include/dso_handle.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/include/stdlib.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/inet/netinet/in.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/posix/bits/types.h: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/stdlib/: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/stdlib/atexit.c: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/crti.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/crtn.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/s390/s390-64/start.S: Cannot stat: No such file or directory [ 1990s] cpio: glibc-2.36/sysdeps/unix/sysv/linux/bits/socket.h: Cannot stat: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1201015] [SELinux] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c12 Zdenek Kubala <zkubala(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #12 from Zdenek Kubala <zkubala(a)suse.com> --- Thanks for testing Issue resolved. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205177] New: Mutt: Some characters in mail headers kill the XTerm mutt is running in
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205177 Bug ID: 1205177 Summary: Mutt: Some characters in mail headers kill the XTerm mutt is running in Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: P.Suetterlin(a)royac.iac.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A really strange one, happened to me the second time now: I read my mail via mutt, running in an XTerm. I access my mailbox via IMAPS. If there are emails with strange characters in the Subject: line, when printing that on screen XTerm dies with a segmentation fault. It is specific to XTerm, if I run mutt in Konsole (or a virtual console outside X11) it does work, If I look at the "bad" file with less, I can see Subject: =?utf-8?B?MjAlIHJhYmF0dCBww6UgcmFtYXIg8J+SpQ==?= console/Konsole do display an empty square at the end of the line, so I suspect that one is to blame? I am running TW 20221025 with X11 as server, mutt is 2.2.7-2.1, xterm 373-1.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1204762] glibc error "Cannot stat: No such file or directory" during build of git
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204762 Ihno Krumreich <ihno(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198618] systemd-boot: openSUSE branding
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198618 https://bugzilla.suse.com/show_bug.cgi?id=1198618#c5 --- Comment #5 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Franck Bui from comment #3) > (In reply to Ludwig Nussel from comment #1) > > the subdirectory on the ESP is also "systemd", should be opensuse probably > > It should be possible with "--entry-token=" (available since v251). > > Actually I just did the test with v252 and couldn't find "systemd". By > default $machine-id is created. machine id is used for the location where kernels are stored. systemd-boot installs itself as EFI/systemd/systemd-bootx64.efi -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198618] systemd-boot: openSUSE branding
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1198618 https://bugzilla.suse.com/show_bug.cgi?id=1198618#c4 --- Comment #4 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Franck Bui from comment #2) > (In reply to Ludwig Nussel from comment #0) > > systemd-boot calls itself "Linux Boot Manager". Maybe it should brand itself > > according to /etc/os-release. Upstream issue: > > https://github.com/systemd/systemd/issues/17044 > > This seems to have been addressed by the introduction of the new option > "--efi-boot-option-description=", which should be available when v252 will > be released (hopefully soon). That helps if you call it manually maybe. I assume the distro will call bootctl install unattended somehow. Eg after package installation to update the bootloader. So it somehow has to remember what to pass. Therefore either a config file is needed or a different value has to be built in. > Note that according to the man page, there is usually no need to change the > description "Linux Boot Manager" though. Well, upstream thinks there's only one instance of sd-boot. In practice it's installed by a specific distribution so in the end different distros will again compete about that entry. So IMO we should still label that with openSUSE. > Ludwig are you OK to close this report ? I'd like to keep this open to track the missing feature. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205185] New: Current image in MS Store has no repositories and yast-firstboot wizzard exits with an error
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205185 Bug ID: 1205185 Summary: Current image in MS Store has no repositories and yast-firstboot wizzard exits with an error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: WSL Assignee: sle-ms(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-c(a)suse.de Found By: --- Blocker: --- Raised by Fabian on #opensuse-factory : We need to reupload the current TW image to the MS Store, that seem to have currently defined repos, and yast-firstboot seem to pass. Thx -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1205185] Current image in MS Store is outdated and unusable
by bugzilla_noreply＠suse.com 08 Nov '22

08 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205185 https://bugzilla.suse.com/show_bug.cgi?id=1205185#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- Turns out in parallel to the MS Store version there was still an older indistinguishable "openSUSE Tumbleweed" app installed which was launched instead. I unregistered the WSL distro, uninstalled both and installed the MS store version to make sure and now I have 20220907, which is much better. So this was a false alarm, apologies for that. I did notice that the installation for some reason waited for a keypress without asking for one, it silently did not launch YaST. -- You are receiving this mail because: You are on the CC list for the bug.

1 0