December 2024 - openSUSE Bugs - openSUSE Mailing Lists

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

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233451 https://bugzilla.suse.com/show_bug.cgi?id=1233451#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(marco(a)growy.nl) --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- OK, then it doesn't smell like a regression in the kernel code. You can try older or newer kernels from my other OBS reops, e.g. home:tiwai:kernel:6.7, too, just to be sure. Once after confirming others don't work, either, you can check the older iwlwifi firmware files. Get from the linux-firmware git tree and just copy to /usr/lib/firmware/ without compression. Then this uncompressed file will be picked up instead of the system default one. Or, you can create /usr/lib/firmware/updates directory and put the test firmware there, instead, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220088] Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 https://bugzilla.suse.com/show_bug.cgi?id=1220088#c36 --- Comment #36 from Takashi Iwai <tiwai(a)suse.com> --- Another thing we can try is to test the direct hibernation without systemd. e.g. run the following as root: echo -n disk > /sys/power/state This will trigger the hibernation. You can combine with the different /sys/power/disk and /sys/kernel/reboot/type as previously tested, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223434] New: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223434 Bug ID: 1223434 Summary: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: gerald_chen(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874523 --> https://bugzilla.suse.com/attachment.cgi?id=874523&action=edit With 21.conf vs without 21.conf I've noticed that emoji look weird in Firefox, as shown in the upper side of the attachment (look at those spooky triangle eyes!). After deleting /etc/fonts/conf.d/21-emoji-rendering.conf, emoji got rendered properly, as shown in the lower side of the attachment. Other applications, such as Konsole and Chromium, don't have this problem. /etc/fonts/conf.d/21-emoji-rendering.conf says that emoji fonts don't need hinting. It seems not to be the case. My fontconfig file in home directory hasn't specified hinting or hintstyle. System info: Operating System: openSUSE Tumbleweed 20240423 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Other files in /etc/fonts/conf.d: 09-autohint-if-no-hinting.conf 10-hinting-slight.conf 10-rendering-options.conf 10-scale-bitmap-fonts.conf 10-sub-pixel-none.conf 10-yes-antialias.conf 11-base-rendering.conf 11-lcdfilter-default.conf 12-tt-monospace-rendering.conf 13-selective-rendering.conf 13-selective-rendering-ipa.conf 20-unhint-small-vera.conf 22-noto-cjk-rendering.conf 30-metric-aliases.conf 31-metric-aliases-bw.conf 32-emoji-reject.conf 32-symbol-substitution.conf 40-nonlatin.conf 45-generic.conf 45-latin.conf 48-spacing.conf 49-family-default.conf 49-family-default-emoji.conf 49-sansserif.conf 55-local.conf 56-user.conf 58-family-prefer-local.conf 59-family-prefer-lang-specific-cjk.conf 59-family-prefer-lang-specific.conf 59-family-prefer-lang-specific-noto.conf 60-family-prefer.conf 60-generic.conf 61-latin.conf 61-stix.conf 61-wine-aliases.conf 65-fonts-persian.conf 65-nonlatin.conf 69-unifont.conf 70-reject.conf 80-delicious.conf 90-synthetic.conf README -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1234026] preempt=full causes frequent freezing
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234026 https://bugzilla.suse.com/show_bug.cgi?id=1234026#c2 --- Comment #2 from Lassi Väätämöinen <lassi.vaatamoinen(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > As TW is already moving to 6.12.x, could you verify whether the issue is > reproducible with the kernel in OBS Kernel:stable repo? I'll try to find some time. By the looks of it, the issue is far less frequent on my home AMD Rzyen desktop, on the Lenovo P15 it's a daily phenomenon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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