December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234053] Podman cannot create container in network
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234053 https://bugzilla.suse.com/show_bug.cgi?id=1234053#c1 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rbobro(a)gmail.com) CC| |alexandre.vicenzi(a)suse.com, | |rbobro(a)gmail.com --- Comment #1 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- Please, provide the output of: > podman info > podman version > iptables -V We recently switched to nftables as a backend for Podman instead of iptables, that might be the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213879] Could not allocate memory for RTAS (When booting from CD ISO image)
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|msuchanek(a)suse.com |snwint(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213879] Could not allocate memory for RTAS (When booting from CD ISO image)
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 https://bugzilla.suse.com/show_bug.cgi?id=1213879#c35 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878744|0 |1 is obsolete| | --- Comment #35 from Michal Suchanek <msuchanek(a)suse.com> --- Created attachment 878826 --> https://bugzilla.suse.com/attachment.cgi?id=878826&action=edit drops WiFi and video drivers This patch removed WiFi and GPU drivers from the ramdisk. While there is theoretical possibility that somebody might want to use them it is very unlikely. It would be fine for Tumbeweed ppc64le but other platforms rely on this kind of hardware during installation. I do not see any platform-specific way to remove modules. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234036] New: filezilla missing RPM dependencies: libpugixml1, glib2/libglib
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234036 Bug ID: 1234036 Summary: filezilla missing RPM dependencies: libpugixml1, glib2/libglib Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rjwilmsi(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- filezilla missing RPM dependencies: libpugixml1, glib2/libglib I upgraded filezilla to filezilla-3.68.0-1.1.x86_64 from a 3.5x version. RPMs at that point: rpm -qa | grep -E '(filezilla|libglib|glib2)' libglib-2_0-0-2.68.3-3.1.x86_64 glib2-lang-2.68.3-3.1.noarch glib2-tools-2.68.3-3.1.x86_64 libglib-2_0-0-32bit-2.68.3-3.1.x86_64 libfilezilla46-0.49.0-1.1.x86_64 libpackagekit-glib2-18-1.2.2-12.1.x86_64 filezilla-3.68.0-1.1.x86_64 filezilla-lang-3.68.0-1.1.noarch glib2-devel-2.68.3-472.1.x86_64 Filezilla failed to open with error "filezilla: symbol lookup error: /lib64/libwx_gtk3u_core-suse.so.12.0.0: undefined symbol: g_string_free_and_steal" I upgrade glib2/libglib-2, RPMs at that point: rpm -qa | grep -E '(filezilla|libglib|glib2)' glib2-lang-2.82.2-2.1.noarch glib2-devel-2.82.2-2.1.x86_64 libglib-2_0-0-32bit-2.82.2-2.1.x86_64 libglib-2_0-0-2.82.2-2.1.x86_64 libfilezilla46-0.49.0-1.1.x86_64 libpackagekit-glib2-18-1.2.2-12.1.x86_64 filezilla-3.68.0-1.1.x86_64 filezilla-lang-3.68.0-1.1.noarch glib2-tools-2.82.2-2.1.x86_64 Filezilla now failed to open with error "filezilla: symbol lookup error: /lib64/libfzclient-commonui-private-3.68.0.so: undefined symbol: _ZN4pugi10xml_writerD2Ev" I upgraded libpugixml1 from libpugixml1-1.11.4-1.5.x86_64 to libpugixml1-1.14-1.3.x86_64. Filezilla then opened without error. There must be incorrect RPM dependencies in filezilla against libpugixml1 and at least one of the glib2/libglib packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1233690] Docker containers are not reachable from network after OS update from 20241114 to 20241115
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 https://bugzilla.suse.com/show_bug.cgi?id=1233690#c15 --- Comment #15 from JDA <jda82(a)vicious-gaming.de> --- Can confirm that removing iptables-backend-nft fixes my issue. Thank you very much for the amazingly fast fix and workaround :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233690] New: Docker containers are not reachable from network
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233690 Bug ID: 1233690 Summary: Docker containers are not reachable from network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: seifert(a)alesak.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After regular OS update from 20241114 to 20241115 or later makes containers unreachable. Containers seams to be normally bind to correct interfaces. As it is on production server I was not able to investigate for very long time, reverting to previous OS snapshot resolved the problem. Installed current version of "openSUSE-MicroOS.x86_64-ContainerHost-kvm-and-xen.qcow2" into VM but unable to reproduce the issue, everything seams to work normally. The only symptom in journal is high occurrence of similar lines: Nov 24 02:23:46 backup1 dockerd[1340]: time="2024-11-24T02:23:46.068350205Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.20.0.66:42800" dns-server="udp:213.186.33.99:53" error="read udp 172.20.0.66:42800->213.186.33.99:53: i/o timeout" question=";certbot.\tIN\t AAAA" spanID=850c3ffdfcec0675 traceID=e1693dcfdf213f90555090b6285ac906 Also there is a difference in IPTABLES: NOT working: Chain FORWARD (policy DROP) target prot opt source destination DOCKER-USER all -- anywhere anywhere DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere working: Chain FORWARD (policy DROP) target prot opt source destination DOCKER-USER all -- anywhere anywhere DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225862] Package metamail does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225862 https://bugzilla.suse.com/show_bug.cgi?id=1225862#c3 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcepl(a)suse.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Matej Cepl <mcepl(a)suse.com> --- https://build.opensuse.org/request/show/1181483 has been accepted -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220571] [META] Packages failing because GCC 14+ treats some warnings as errors
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220571 Bug 1220571 depends on bug 1225862, which changed state. Bug 1225862 Summary: Package metamail does not build with gcc14 because of new errors https://bugzilla.suse.com/show_bug.cgi?id=1225862 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233451] iwlwifi does not work with AX210
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233451 https://bugzilla.suse.com/show_bug.cgi?id=1233451#c8 --- Comment #8 from Marco Louter <marco(a)growy.nl> --- Created attachment 878824 --> https://bugzilla.suse.com/attachment.cgi?id=878824&action=edit dmesg output 6.8.9 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1233451] iwlwifi does not work with AX210
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233451 https://bugzilla.suse.com/show_bug.cgi?id=1233451#c7 --- Comment #7 from Marco Louter <marco(a)growy.nl> --- (In reply to Takashi Iwai from comment #6) > Meanwhile, there are old kernel packages in my OBS repos, e.g. > home:tiwai:kernel:6.8 > https://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.8/ARM/ > > Could you check with this kernel and see whether the problem persists or not? > If the old kernel is confirmed to work, you can report it as a regression. I have downgraded the kernel-default package to the version from your repository. In the dmesg output I see that the driver tries to load firmware version 86 instead of 89. Other than that the output looks the same. -- You are receiving this mail because: You are on the CC list for the bug.

1 0