July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227420] New: openSUSE missing fi keymap
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227420 Bug ID: 1227420 Summary: openSUSE missing fi keymap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jarkko.torvinen(a)iki.fi QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Tumbleweed installer, when selecting keyboard "Finnish", it results in "fi-kotoistus" in /etc/vconsole.conf. Gnome is not aware of such layout, resulting in non-working keymap in Gnome desktop, gnome-settings listing input source as "fi+kotoistus", and you need to change it to "Finnish" or "Finnish (classic)" to have working keyboard. On Aeon, keyboard selection is done with gnome initial setup. It has options "Finnish" and "Finnish (classic)" (as above with TW gnome-settins). 1) "Finnish" results in "fi" in /etc/vconsole.conf, but fi.map.gz does not exist in openSUSE, resulting in failing unit systemd-vconsole-setup 2) "Finnish (classic)" results in "fi-classic" in /etc/vconsole.conf, and everything works fine So both TW and Aeon are broken if you simply select obvious choices "Finnish". TW in GNOME, Aeon in form of failing unit during boot. On TW, selecting "Finnish" does not alter /etc/vconsole.conf anymore, so it does not break it, only initial setup with Aeon. Other distros (Debian,Arch for example) ship with "fi" map, and works as should. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226021] New: VUL-0: CVE-2024-5171: chromium: libaom: heap buffer overflow in img_alloc_helper() caused by integer overflow
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1226021 Bug ID: 1226021 Summary: VUL-0: CVE-2024-5171: chromium: libaom: heap buffer overflow in img_alloc_helper() caused by integer overflow Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/408840/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: Andreas.Stieger(a)gmx.de Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: coldpool(a)suse.de, rfrohl(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Depends on: 1226020 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1226020 +++ Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_wrap() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-5171 https://www.cve.org/CVERecord?id=CVE-2024-5171 https://issues.chromium.org/issues/332382766 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228593] New: thinkpad x13s aarch64 continue reset during grub2 load kernel
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228593 Bug ID: 1228593 Summary: thinkpad x13s aarch64 continue reset during grub2 load kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: macromarship(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just bought a thinkpad x13s aarch64. Following HCL:suse I have successfully installed latest version. And I have copied the dtb file to system_drv partition as page requested. But after grub2 load kernel, the computer continues reset. About 7-8 times failed then 1 success. This makes I am afraid to reboot computer because next time will take more tries to come in. I notice the UEFI version is 1.60 or 1.70, which is a higher version than 1.58. Upgrade your UEFI firmware to the newer versions which can support LINUX boot v1.49 or later versions. The latest version tested: v1.58 I have read all the tickets on this website. Can any help guide how to resolve this? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1225932] New: Authentication failure for non-privileged user in "Software updates"
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225932 Bug ID: 1225932 Summary: Authentication failure for non-privileged user in "Software updates" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: robert.simai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875298 --> https://bugzilla.suse.com/attachment.cgi?id=875298&action=edit Cockpit message Logged into Cockpit (309) on Tumbleweed as non-privileged user "robert", clicked the "Software updates" and got the attached message on screen and the following in the journal: sudo[5258]: robert : 3 incorrect password attempts ; PWD=/ ; USER=root ; COMMAND=/usr/bin/cockpit-bridge --privileged Something similar happens when I click the "Check for updates" from the Software updates module, the journal message then is sudo[5856]: pam_unix(sudo:auth): authentication failure; logname=robert uid=1000 euid=0 tty= ruser=robert rhost= user=root sudo[5856]: robert : 3 incorrect password attempts ; PWD=/ ; USER=root ; COMMAND=/usr/bin/cockpit-bridge --privileged I'm not sure why refreshing the updates requires sudo as a regular user could successfully run "zypper lu" as well. But if it does, we could at least come up with a clearer message "switch to administrative access first" or such. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222815] New: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1222815 Bug ID: 1222815 Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just installing pcp and pmlogger leads to: # systemctl start pmlogger Failed to start pmlogger.service: Unit pmlogger_daily.timer not found. this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219884] New: Adapt package libzrtpcpp to build with OpenSSL 3
by bugzilla_noreply＠suse.com 30 Oct '24

30 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219884 Bug ID: 1219884 Summary: Adapt package libzrtpcpp to build with OpenSSL 3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Package libzrtpcpp requires openssl 1.0.0 that is EOL and we would like to remove it from Factory. > BuildRequires: libopenssl-1_0_0-devel Please check tracker bug 1219879 for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1224403] New: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage'
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224403 Bug ID: 1224403 Summary: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bpftrace fails to attach probe: # echo -e "\ninterval:s:5 { exit(); }" | cat /usr/share/bpftrace/tools/swapin.bt - | bpftrace - stdin:1-16: WARNING: swap_readpage is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail Attaching 3 probes... cannot attach kprobe, probe entry may not exist ERROR: Error attaching probe: 'kprobe:swap_readpage' # echo $? 255 It has been failing for some time (at least since 20240412, but probably much longer). -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1228355] New: Package rubygem-nokogiri does not build with gcc 14 because of new errors (that were previously warnings)
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228355 Bug ID: 1228355 Summary: Package rubygem-nokogiri does not build with gcc 14 because of new errors (that were previously warnings) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mrueckert(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Package rubygem-nokogiri fails to build with GCC 14 because of various C99 violations which previously just generated warning s but which cause errors with GCC 14 by default. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. BuildService failures are available online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… The build with GCC 14 can now be tried locally with: osc build --clean --alternative-project home:rguenther:nextgcc The (first) error that stops the build is: [ 17s] html4_document.c: In function ‘rb_html_document_s_read_io’: [ 17s] html4_document.c:49:52: error: passing argument 2 of ‘xmlSetStructuredErrorFunc’ from incompatible pointer type [-Wincompatible-pointer-types] [ 17s] 49 | xmlSetStructuredErrorFunc((void *)rb_error_list, Nokogiri_error_array_pusher); [ 17s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 17s] | | [ 17s] | void (*)(void *, xmlError *) {aka void (*)(void *, struct _xmlError *)} [ 17s] In file included from /usr/include/libxml/valid.h:15, [ 17s] from /usr/include/libxml/parser.h:19, [ 17s] from ./nokogiri.h:35, [ 17s] from html4_document.c:1: [ 17s] /usr/include/libxml/xmlerror.h:898:57: note: expected ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void *, const struct _xmlError *)’} but argument is of type ‘void (*)(void *, xmlError *)’ {aka ‘void (*)(void *, struct _xmlError *)’} [ 17s] 898 | xmlStructuredErrorFunc handler); [ 17s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~ [ 17s] html4_document.c: In function ‘rb_html_document_s_read_memory’: [ 17s] html4_document.c:109:52: error: passing argument 2 of ‘xmlSetStructuredErrorFunc’ from incompatible pointer type [-Wincompatible-pointer-types] [ 17s] 109 | xmlSetStructuredErrorFunc((void *)rb_error_list, Nokogiri_error_array_pusher); [ 17s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 17s] | | [ 17s] | void (*)(void *, xmlError *) {aka void (*)(void *, struct _xmlError *)} [ 17s] /usr/include/libxml/xmlerror.h:898:57: note: expected ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void *, const struct _xmlError *)’} but argument is of type ‘void (*)(void *, xmlError *)’ {aka ‘void (*)(void *, struct _xmlError *)’} [ 17s] 898 | xmlStructuredErrorFunc handler); [ 17s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219444] New: amdgpu critical error
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219444 Bug ID: 1219444 Summary: amdgpu critical error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: teuniz(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872372 --> https://bugzilla.suse.com/attachment.cgi?id=872372&action=edit Output of dmesg The kernel crashes approx every 5 minutes. I reverted back to kernel 5.14.21-150500.55.19-default because with that one it crashes approx once a day. Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.44-default (64-bit) Graphics Platform: X11 Processors: 32 × 13th Gen Intel Core i9-13900K Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon Pro W6600 Manufacturer: HP Product Name: HP Z2 Tower G9 Workstation Desktop PC dmesg | grep amdgpu [ 1.540640] [drm] amdgpu kernel modesetting enabled. [ 1.540703] amdgpu: CRAT table not found [ 1.540705] amdgpu: Virtual CRAT table created for CPU [ 1.540712] amdgpu: Topology: Add CPU node [ 1.542670] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT [ 1.542671] amdgpu: ATOM BIOS: 113-D5330400-100 [ 1.542770] amdgpu 0000:03:00.0: vgaarb: deactivate vga console [ 1.542771] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [ 1.542799] amdgpu 0000:03:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [ 1.542800] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 1.542801] amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 1.542845] [drm] amdgpu: 8176M of VRAM memory ready [ 1.542845] [drm] amdgpu: 15892M of GTT memory ready. [ 1.548699] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 1.548704] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 2.854516] amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries [ 2.895100] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware [ 3.094413] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 3.115717] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 3.115740] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2b00 (59.43.0) [ 3.115745] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 3.115777] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable [ 3.165133] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! [ 3.268063] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 3.268478] amdgpu: sdma_bitmap: ffff [ 3.302091] amdgpu: HMM registered 8176MB device memory [ 3.302135] amdgpu: SRAT table not found [ 3.302136] amdgpu: Virtual CRAT table created for GPU [ 3.302599] amdgpu: Topology: Add dGPU node [0x73e3:0x1002] [ 3.302601] kfd kfd: amdgpu: added device 1002:73e3 [ 3.302617] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 28 [ 3.302658] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.302664] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1 [ 3.303573] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0 [ 3.308709] fbcon: amdgpudrmfb (fb0) is primary device [ 3.505728] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 3.505731] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 3.505733] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 3.505733] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 3.505734] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 3.505736] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 3.524299] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 4.537456] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 5.416287] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 5.416312] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 5.416319] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [ 5.416324] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x0) [ 5.416329] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 5.416333] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 [ 5.416336] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 5.416340] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 5.416343] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 73.156519] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 73.156538] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 73.156546] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 73.156551] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 73.156562] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 73.156566] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 73.156570] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 73.156578] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 73.156582] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 uname -a 5.14.21-150500.55.44-default #1 SMP PREEMPT_DYNAMIC Mon Jan 15 10:03:40 UTC 2024 (cc7d8b6) x86_64 x86_64 x86_64 GNU/Linux lspci VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 WKS-XL [Radeon PRO W6600] -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1227575] New: Update nvidia driver to version 550.100
by bugzilla_noreply＠suse.com 28 Oct '24

28 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227575 Bug ID: 1227575 Summary: Update nvidia driver to version 550.100 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Update nvidia driver to version 550.100 ... Changes: - Fixed a bug that caused OpenGL triple buffering to behave like double buffering. -- You are receiving this mail because: You are on the CC list for the bug.

1 5