May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223194] New: Empty battery reported after suspend
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 Bug ID: 1223194 Summary: Empty battery reported after suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following up on https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/… In between I have the impression that the battery status after a suspend is reported wrong from the system (so no drain ,as originally assumed). I had the laptop suspend and at the charger over night, in the morning it reported 8% charge left. Which is definitely wrong. Other than 'in earlier times' it does not get updated to the correct status. This is quite annoying as the laptop is my primary workhorse Let me know how I can debug/provide information on this. Thank you! Operating System: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: LENOVO Product Name: 20QWS0A8GE System Version: ThinkPad X1 Extreme 2nd -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225697] New: Problem video driver i915
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225697 Bug ID: 1225697 Summary: Problem video driver i915 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: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: sidewinderx(a)libero.it QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: I have a problem that is not clear to me I guess with the Intel G33 i915 video drivers. Upgrading from 15.4 to 15.5 opensuse leap I have freezes while navigating through the system menus and mainly I can’t launch graphics programs for pcb creation which didn’t happen in previous versions. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1212841] New: Lots of objtool warnings when building the nvidia driver
by bugzilla_noreply＠suse.com 15 Jun '24

15 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1212841 Bug ID: 1212841 Summary: Lots of objtool warnings when building the nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- # rpm -qv nvidia-driver-G06-kmp-default nvidia-driver-G06-kmp-default-535.54.03_k6.3.7_1-10.1.x86_64 # zgrep -c objtool zypper.log-20230627.xz 213230 extracts: [rpm> LD [M] /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000675kms+0x46: 'naked' return found in RETHUNK build [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-modeset.o: warning: objtool: _nv000676kms+0x46: 'naked' return found in RETHUNK build [cut] [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv040720rm+0xb9: return with modified stack frame [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv013581rm+0xd9: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-64 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv034058rm+0x83: stack state mismatch: reg1[5]=-1+0 reg2[5]=-2-56 [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv024689rm+0xb: missing int3 after ret [rpm> /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia.o: warning: objtool: _nv043791rm+0x4: missing int3 after ret [cut] then it finishes building and prints a couple last warnings such as: [rpm> Skipping BTF generation for /usr/src/kernel-modules/nvidia-535.54.03-default/nvidia-peermem.ko due to unavailability of vmlinux -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215984] New: virt-manager silently fails to connect
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215984 Bug ID: 1215984 Summary: virt-manager silently fails to connect Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- virt-manager fails to connect, no error is reported in the UI. Only debug output shows missing services. virt-manager --debug [Thu, 05 Oct 2023 22:27:55 virt-manager 17933] DEBUG (cli:205) Version 4.1.0 launched with command line: /usr/bin/virt-manager --debug [Thu, 05 Oct 2023 22:27:55 virt-manager 17933] DEBUG (virtmanager:167) virt-manager version: 4.1.0 [Thu, 05 Oct 2023 22:27:55 virt-manager 17933] DEBUG (virtmanager:168) virtManager import: /usr/share/virt-manager/virtManager [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (virtmanager:208) PyGObject version: 3.42.2 [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (virtmanager:212) GTK version: 3.24.34 [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (systray:72) Imported AppIndicator3=<IntrospectionModule 'AppIndicator3' from '/usr/lib64/girepository-1.0/AppIndicator3-0.1.typelib'> [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (systray:74) AppIndicator3 is available, but didn't find any dbus watcher. [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (systray:464) Showing systray: False [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (inspection:206) python guestfs is not installed [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (engine:114) Loading stored URIs: qemu:///system [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (engine:462) processing cli command uri= show_window=manager domain= [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (engine:464) No cli action requested, launching default window [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (manager:185) Showing manager [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (engine:316) window counter incremented to 1 [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (engine:211) Initial gtkapplication activated [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (connection:485) conn=qemu:///system changed to state=Connecting [Thu, 05 Oct 2023 22:27:56 virt-manager 17933] DEBUG (connection:906) Scheduling background open thread for qemu:///system [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:131) libvirt URI versions library=9.0.0 driver=9.0.0 hypervisor=7.1.0 [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:109) Fetched capabilities for qemu:///system: <capabilities> <host> <uuid>af7d05fd-06bf-ed11-a129-218475400338</uuid> <cpu> <arch>x86_64</arch> <model>Broadwell-noTSX-IBRS</model> <vendor>Intel</vendor> <microcode version='1068'/> <signature family='6' model='154' stepping='3'/> <counter name='tsc' frequency='2112000000' scaling='yes'/> <topology sockets='1' dies='1' cores='16' threads='1'/> <maxphysaddr mode='emulate' bits='39'/> <feature name='vme'/> <feature name='ds'/> <feature name='acpi'/> <feature name='ss'/> <feature name='ht'/> <feature name='tm'/> <feature name='pbe'/> <feature name='dtes64'/> <feature name='monitor'/> <feature name='ds_cpl'/> <feature name='vmx'/> <feature name='smx'/> <feature name='est'/> <feature name='tm2'/> <feature name='xtpr'/> <feature name='pdcm'/> <feature name='osxsave'/> <feature name='f16c'/> <feature name='rdrand'/> <feature name='arat'/> <feature name='tsc_adjust'/> <feature name='clflushopt'/> <feature name='clwb'/> <feature name='intel-pt'/> <feature name='sha-ni'/> <feature name='umip'/> <feature name='pku'/> <feature name='ospke'/> <feature name='waitpkg'/> <feature name='gfni'/> <feature name='vaes'/> <feature name='vpclmulqdq'/> <feature name='rdpid'/> <feature name='movdiri'/> <feature name='movdir64b'/> <feature name='pks'/> <feature name='fsrm'/> <feature name='md-clear'/> <feature name='serialize'/> <feature name='arch-lbr'/> <feature name='stibp'/> <feature name='arch-capabilities'/> <feature name='core-capability'/> <feature name='ssbd'/> <feature name='avx-vnni'/> <feature name='xsaveopt'/> <feature name='xsavec'/> <feature name='xgetbv1'/> <feature name='xsaves'/> <feature name='pdpe1gb'/> <feature name='abm'/> <feature name='invtsc'/> <feature name='rdctl-no'/> <feature name='ibrs-all'/> <feature name='skip-l1dfl-vmentry'/> <feature name='mds-no'/> <feature name='pschange-mc-no'/> <feature name='taa-no'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> <pages unit='KiB' size='1048576'/> </cpu> <power_management> <suspend_mem/> </power_management> <iommu support='yes'/> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> <uri_transport>rdma</uri_transport> </uri_transports> </migration_features> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>65537512</memory> <pages unit='KiB' size='4'>16384378</pages> <pages unit='KiB' size='2048'>0</pages> <pages unit='KiB' size='1048576'>0</pages> <distances> <sibling id='0' value='10'/> </distances> <cpus num='16'> <cpu id='0' socket_id='0' die_id='0' core_id='0' siblings='0-1'/> <cpu id='1' socket_id='0' die_id='0' core_id='0' siblings='0-1'/> <cpu id='2' socket_id='0' die_id='0' core_id='4' siblings='2-3'/> <cpu id='3' socket_id='0' die_id='0' core_id='4' siblings='2-3'/> <cpu id='4' socket_id='0' die_id='0' core_id='8' siblings='4-5'/> <cpu id='5' socket_id='0' die_id='0' core_id='8' siblings='4-5'/> <cpu id='6' socket_id='0' die_id='0' core_id='12' siblings='6-7'/> <cpu id='7' socket_id='0' die_id='0' core_id='12' siblings='6-7'/> <cpu id='8' socket_id='0' die_id='0' core_id='16' siblings='8'/> <cpu id='9' socket_id='0' die_id='0' core_id='17' siblings='9'/> <cpu id='10' socket_id='0' die_id='0' core_id='18' siblings='10'/> <cpu id='11' socket_id='0' die_id='0' core_id='19' siblings='11'/> <cpu id='12' socket_id='0' die_id='0' core_id='20' siblings='12'/> <cpu id='13' socket_id='0' die_id='0' core_id='21' siblings='13'/> <cpu id='14' socket_id='0' die_id='0' core_id='22' siblings='14'/> <cpu id='15' socket_id='0' die_id='0' core_id='23' siblings='15'/> </cpus> </cell> </cells> </topology> <cache> <bank id='0' level='3' type='both' size='12' unit='MiB' cpus='0-15'/> </cache> <secmodel> <model>apparmor</model> <doi>0</doi> </secmodel> <secmodel> <model>dac</model> <doi>0</doi> <baselabel type='kvm'>+107:+107</baselabel> <baselabel type='qemu'>+107:+107</baselabel> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-i386</emulator> <machine maxCpus='255'>pc-i440fx-7.1</machine> <machine canonical='pc-i440fx-7.1' maxCpus='255'>pc</machine> <machine maxCpus='288'>pc-q35-5.2</machine> <machine maxCpus='255'>pc-i440fx-2.12</machine> <machine maxCpus='255'>pc-i440fx-2.0</machine> <machine maxCpus='1'>xenpv</machine> <machine maxCpus='255'>pc-i440fx-6.2</machine> <machine maxCpus='288'>pc-q35-4.2</machine> <machine maxCpus='255'>pc-i440fx-2.5</machine> <machine maxCpus='255'>pc-i440fx-4.2</machine> <machine maxCpus='255'>pc-i440fx-5.2</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.5</machine> <machine maxCpus='255'>pc-q35-2.7</machine> <machine maxCpus='1024'>pc-q35-7.1</machine> <machine canonical='pc-q35-7.1' maxCpus='1024'>q35</machine> <machine maxCpus='255'>pc-i440fx-2.2</machine> <machine maxCpus='255'>pc-i440fx-2.7</machine> <machine maxCpus='288'>pc-q35-6.1</machine> <machine maxCpus='128'>xenfv-3.1</machine> <machine canonical='xenfv-3.1' maxCpus='128'>xenfv</machine> <machine maxCpus='255'>pc-q35-2.4</machine> <machine maxCpus='288'>pc-q35-2.10</machine> <machine maxCpus='288'>pc-q35-5.1</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.7</machine> <machine maxCpus='288'>pc-q35-2.9</machine> <machine maxCpus='255'>pc-i440fx-2.11</machine> <machine maxCpus='288'>pc-q35-3.1</machine> <machine maxCpus='255'>pc-i440fx-6.1</machine> <machine maxCpus='288'>pc-q35-4.1</machine> <machine maxCpus='255'>pc-i440fx-2.4</machine> <machine maxCpus='255'>pc-i440fx-4.1</machine> <machine maxCpus='255'>pc-i440fx-5.1</machine> <machine maxCpus='255'>pc-i440fx-2.9</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-q35-2.6</machine> <machine maxCpus='255'>pc-i440fx-3.1</machine> <machine maxCpus='288'>pc-q35-2.12</machine> <machine maxCpus='288'>pc-q35-7.0</machine> <machine maxCpus='255'>pc-i440fx-2.1</machine> <machine maxCpus='288'>pc-q35-6.0</machine> <machine maxCpus='255'>pc-i440fx-2.6</machine> <machine maxCpus='288'>pc-q35-4.0.1</machine> <machine maxCpus='255'>pc-i440fx-7.0</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.6</machine> <machine maxCpus='288'>pc-q35-5.0</machine> <machine maxCpus='288'>pc-q35-2.8</machine> <machine maxCpus='255'>pc-i440fx-2.10</machine> <machine maxCpus='288'>pc-q35-3.0</machine> <machine maxCpus='255'>pc-i440fx-6.0</machine> <machine maxCpus='288'>pc-q35-4.0</machine> <machine maxCpus='128'>xenfv-4.2</machine> <machine maxCpus='288'>microvm</machine> <machine maxCpus='255'>pc-i440fx-2.3</machine> <machine maxCpus='255'>pc-i440fx-4.0</machine> <machine maxCpus='255'>pc-i440fx-5.0</machine> <machine maxCpus='255'>pc-i440fx-2.8</machine> <machine maxCpus='288'>pc-q35-6.2</machine> <machine maxCpus='255'>pc-q35-2.5</machine> <machine maxCpus='255'>pc-i440fx-3.0</machine> <machine maxCpus='288'>pc-q35-2.11</machine> <domain type='qemu'/> <domain type='kvm'/> </arch> <features> <pae/> <nonpae/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='ppc'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-ppc</emulator> <machine maxCpus='1'>g3beige</machine> <machine maxCpus='1'>virtex-ml507</machine> <machine maxCpus='1'>mac99</machine> <machine maxCpus='32'>ppce500</machine> <machine maxCpus='1'>pegasos2</machine> <machine maxCpus='1'>sam460ex</machine> <machine maxCpus='1'>bamboo</machine> <machine maxCpus='1'>40p</machine> <machine maxCpus='1'>ref405ep</machine> <machine maxCpus='15'>mpc8544ds</machine> <machine maxCpus='1' deprecated='yes'>taihu</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='ppc64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-ppc64</emulator> <machine maxCpus='2147483647'>pseries-7.1</machine> <machine canonical='pseries-7.1' maxCpus='2147483647'>pseries</machine> <machine maxCpus='2048'>powernv9</machine> <machine canonical='powernv9' maxCpus='2048'>powernv</machine> <machine maxCpus='1' deprecated='yes'>taihu</machine> <machine maxCpus='2147483647'>pseries-4.1</machine> <machine maxCpus='15'>mpc8544ds</machine> <machine maxCpus='2147483647'>pseries-6.1</machine> <machine maxCpus='2147483647'>pseries-2.5</machine> <machine maxCpus='2048'>powernv10</machine> <machine maxCpus='2147483647'>pseries-4.2</machine> <machine maxCpus='2147483647'>pseries-6.2</machine> <machine maxCpus='2147483647'>pseries-2.6</machine> <machine maxCpus='32'>ppce500</machine> <machine maxCpus='2147483647'>pseries-2.7</machine> <machine maxCpus='2147483647'>pseries-3.0</machine> <machine maxCpus='2147483647'>pseries-5.0</machine> <machine maxCpus='1'>40p</machine> <machine maxCpus='2147483647'>pseries-2.8</machine> <machine maxCpus='1'>pegasos2</machine> <machine maxCpus='2147483647'>pseries-3.1</machine> <machine maxCpus='2147483647'>pseries-5.1</machine> <machine maxCpus='2147483647'>pseries-2.9</machine> <machine maxCpus='1'>bamboo</machine> <machine maxCpus='1'>g3beige</machine> <machine maxCpus='2147483647'>pseries-5.2</machine> <machine maxCpus='2147483647'>pseries-2.12-sxxm</machine> <machine maxCpus='2147483647'>pseries-2.10</machine> <machine maxCpus='2147483647'>pseries-7.0</machine> <machine maxCpus='1'>virtex-ml507</machine> <machine maxCpus='2147483647'>pseries-2.11</machine> <machine maxCpus='2147483647'>pseries-2.1</machine> <machine maxCpus='2147483647'>pseries-2.12</machine> <machine maxCpus='2147483647'>pseries-2.2</machine> <machine maxCpus='1'>mac99</machine> <machine maxCpus='1'>sam460ex</machine> <machine maxCpus='1'>ref405ep</machine> <machine maxCpus='2147483647'>pseries-2.3</machine> <machine maxCpus='2048'>powernv8</machine> <machine maxCpus='2147483647'>pseries-4.0</machine> <machine maxCpus='2147483647'>pseries-6.0</machine> <machine maxCpus='2147483647'>pseries-2.4</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='ppc64le'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-ppc64</emulator> <machine maxCpus='2147483647'>pseries-7.1</machine> <machine canonical='pseries-7.1' maxCpus='2147483647'>pseries</machine> <machine maxCpus='2048'>powernv9</machine> <machine canonical='powernv9' maxCpus='2048'>powernv</machine> <machine maxCpus='1' deprecated='yes'>taihu</machine> <machine maxCpus='2147483647'>pseries-4.1</machine> <machine maxCpus='15'>mpc8544ds</machine> <machine maxCpus='2147483647'>pseries-6.1</machine> <machine maxCpus='2147483647'>pseries-2.5</machine> <machine maxCpus='2048'>powernv10</machine> <machine maxCpus='2147483647'>pseries-4.2</machine> <machine maxCpus='2147483647'>pseries-6.2</machine> <machine maxCpus='2147483647'>pseries-2.6</machine> <machine maxCpus='32'>ppce500</machine> <machine maxCpus='2147483647'>pseries-2.7</machine> <machine maxCpus='2147483647'>pseries-3.0</machine> <machine maxCpus='2147483647'>pseries-5.0</machine> <machine maxCpus='1'>40p</machine> <machine maxCpus='2147483647'>pseries-2.8</machine> <machine maxCpus='1'>pegasos2</machine> <machine maxCpus='2147483647'>pseries-3.1</machine> <machine maxCpus='2147483647'>pseries-5.1</machine> <machine maxCpus='2147483647'>pseries-2.9</machine> <machine maxCpus='1'>bamboo</machine> <machine maxCpus='1'>g3beige</machine> <machine maxCpus='2147483647'>pseries-5.2</machine> <machine maxCpus='2147483647'>pseries-2.12-sxxm</machine> <machine maxCpus='2147483647'>pseries-2.10</machine> <machine maxCpus='2147483647'>pseries-7.0</machine> <machine maxCpus='1'>virtex-ml507</machine> <machine maxCpus='2147483647'>pseries-2.11</machine> <machine maxCpus='2147483647'>pseries-2.1</machine> <machine maxCpus='2147483647'>pseries-2.12</machine> <machine maxCpus='2147483647'>pseries-2.2</machine> <machine maxCpus='1'>mac99</machine> <machine maxCpus='1'>sam460ex</machine> <machine maxCpus='1'>ref405ep</machine> <machine maxCpus='2147483647'>pseries-2.3</machine> <machine maxCpus='2048'>powernv8</machine> <machine maxCpus='2147483647'>pseries-4.0</machine> <machine maxCpus='2147483647'>pseries-6.0</machine> <machine maxCpus='2147483647'>pseries-2.4</machine> <domain type='qemu'/> </arch> <features> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine maxCpus='255'>pc-i440fx-7.1</machine> <machine canonical='pc-i440fx-7.1' maxCpus='255'>pc</machine> <machine maxCpus='288'>pc-q35-5.2</machine> <machine maxCpus='255'>pc-i440fx-2.12</machine> <machine maxCpus='255'>pc-i440fx-2.0</machine> <machine maxCpus='1'>xenpv</machine> <machine maxCpus='255'>pc-i440fx-6.2</machine> <machine maxCpus='288'>pc-q35-4.2</machine> <machine maxCpus='255'>pc-i440fx-2.5</machine> <machine maxCpus='255'>pc-i440fx-4.2</machine> <machine maxCpus='255'>pc-i440fx-5.2</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.5</machine> <machine maxCpus='255'>pc-q35-2.7</machine> <machine maxCpus='1024'>pc-q35-7.1</machine> <machine canonical='pc-q35-7.1' maxCpus='1024'>q35</machine> <machine maxCpus='255'>pc-i440fx-2.2</machine> <machine maxCpus='255'>pc-i440fx-2.7</machine> <machine maxCpus='288'>pc-q35-6.1</machine> <machine maxCpus='128'>xenfv-3.1</machine> <machine canonical='xenfv-3.1' maxCpus='128'>xenfv</machine> <machine maxCpus='255'>pc-q35-2.4</machine> <machine maxCpus='288'>pc-q35-2.10</machine> <machine maxCpus='288'>pc-q35-5.1</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.7</machine> <machine maxCpus='288'>pc-q35-2.9</machine> <machine maxCpus='255'>pc-i440fx-2.11</machine> <machine maxCpus='288'>pc-q35-3.1</machine> <machine maxCpus='255'>pc-i440fx-6.1</machine> <machine maxCpus='288'>pc-q35-4.1</machine> <machine maxCpus='255'>pc-i440fx-2.4</machine> <machine maxCpus='255'>pc-i440fx-4.1</machine> <machine maxCpus='255'>pc-i440fx-5.1</machine> <machine maxCpus='255'>pc-i440fx-2.9</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-q35-2.6</machine> <machine maxCpus='255'>pc-i440fx-3.1</machine> <machine maxCpus='288'>pc-q35-2.12</machine> <machine maxCpus='288'>pc-q35-7.0</machine> <machine maxCpus='255'>pc-i440fx-2.1</machine> <machine maxCpus='255'>pc-i440fx-2.6</machine> <machine maxCpus='288'>pc-q35-6.0</machine> <machine maxCpus='288'>pc-q35-4.0.1</machine> <machine maxCpus='255'>pc-i440fx-7.0</machine> <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.6</machine> <machine maxCpus='288'>pc-q35-5.0</machine> <machine maxCpus='288'>pc-q35-2.8</machine> <machine maxCpus='255'>pc-i440fx-2.10</machine> <machine maxCpus='288'>pc-q35-3.0</machine> <machine maxCpus='255'>pc-i440fx-6.0</machine> <machine maxCpus='288'>pc-q35-4.0</machine> <machine maxCpus='128'>xenfv-4.2</machine> <machine maxCpus='288'>microvm</machine> <machine maxCpus='255'>pc-i440fx-2.3</machine> <machine maxCpus='255'>pc-i440fx-4.0</machine> <machine maxCpus='255'>pc-i440fx-5.0</machine> <machine maxCpus='255'>pc-i440fx-2.8</machine> <machine maxCpus='288'>pc-q35-6.2</machine> <machine maxCpus='255'>pc-q35-2.5</machine> <machine maxCpus='255'>pc-i440fx-3.0</machine> <machine maxCpus='288'>pc-q35-2.11</machine> <domain type='qemu'/> <domain type='kvm'/> </arch> <features> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> <cpuselection/> <deviceboot/> <disksnapshot default='on' toggle='no'/> </features> </guest> </capabilities> [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:741) Using domain events [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:783) Error registering network events: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:802) Error registering storage pool events: Failed to connect socket to '/var/run/libvirt/virtstoraged-sock': No such file or directory [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:827) Error registering node device events: Failed to connect socket to '/var/run/libvirt/virtnodedevd-sock': No such file or directory [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (pollhelpers:23) Unable to list all networks: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (engine:300) Error polling connection qemu:///system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 294, in _handle_tick_queue conn.tick_from_engine(**kwargs) File "/usr/share/virt-manager/virtManager/connection.py", line 1319, in tick_from_engine self._tick(*args, **kwargs) File "/usr/share/virt-manager/virtManager/connection.py", line 1207, in _tick initial_poll, pollvm, pollnet, pollpool, pollnodedev) File "/usr/share/virt-manager/virtManager/connection.py", line 1140, in _poll new_pools = _process_objects("pools") File "/usr/share/virt-manager/virtManager/connection.py", line 1126, in _process_objects gone, new, master = pollcb(self._backend, keymap, cb) File "/usr/share/virt-manager/virtinst/pollhelpers.py", line 57, in fetch_pools objs = backend.listAllStoragePools() File "/usr/lib64/python3.6/site-packages/libvirt.py", line 6223, in listAllStoragePools raise libvirtError("virConnectListAllStoragePools() failed") libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtstoraged-sock': No such file or directory [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:840) conn.close() uri=qemu:///system [Thu, 05 Oct 2023 22:27:57 virt-manager 17933] DEBUG (connection:485) conn=qemu:///system changed to state=Disconnected [Thu, 05 Oct 2023 22:28:01 virt-manager 17933] DEBUG (manager:196) Closing manager [Thu, 05 Oct 2023 22:28:01 virt-manager 17933] DEBUG (engine:323) window counter decremented to 0 [Thu, 05 Oct 2023 22:28:01 virt-manager 17933] DEBUG (engine:343) No windows found, requesting app exit [Thu, 05 Oct 2023 22:28:01 virt-manager 17933] DEBUG (engine:369) Exiting app normally. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1223461] New: Problem with upgrade: openSUSE-repos-Slowroll-NVIDIA-20240412.89bd714-2.1.x86_64
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223461 Bug ID: 1223461 Summary: Problem with upgrade: openSUSE-repos-Slowroll-NVIDIA-20240412.89bd714-2.1.x8 6_64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: lisbeth.gyl90(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I update through "Discover", and it returns an error, which it says: Dependency resolution failed:The openSUSE-repos-Slowroll-NVIDIA-20240412.89bd714-2.1.x86_64 element to be installed requires openSUSE-repos-Slowroll, but cannot be installed satisfy this requirement The openSUSE-repos-Tumbleweed-NVIDIA-20240412.89bd714-2.1.x86_64 element to be installed requires openSUSE-repos-Tumbleweed, but this requirement cannot be satisfied. After that, stops the upgrade. A message window appears of this error and suggest me to publish it to this channel. I'm using this OpenSuse Tumbleweed 20240425 with KDE Desktop in X11 WM. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

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

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220571 Bug ID: 1220571 Summary: [META] Packages failing because GCC 14+ treats some warnings as errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mjambor(a)suse.com Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- GCC 14 treats the following situations, which were only warnings before, as errors: -Werror=implicit-int -Werror=implicit-function-declaration -Werror=declaration-missing-parameter-type -Werror=return-mismatch -Werror=int-conversion -Werror=incompatible-pointer-types More details about all of these cases together with the most common ways of addressing them and some associated pitfalls is available at https://gcc.gnu.org/gcc-14/porting_to.html For the record, clang has taken a similar step since clang 16, see for example https://www.redhat.com/en/blog/new-warnings-and-errors-clang-16 The preferred method of dealing with these issues is of course fixing the code. Other distributions have shared patches from their porting efforts on relevant upstream mailing lists and bug trackers, Gentoo and RedHat are perhaps most active in this regard, so you can have a look at what they did for their packages at: - https://bugs.gentoo.org/showdependencytree.cgi?id=870412&hide_resolved=0 - https://gitlab.com/fweimer-rh/fedora-modernc/ In case there is for some reason not possible to fix the code, or at least to fix it in time for adoption of GCC 14, it is possible to turn these back to warnings by adding to the compiler options one of the following: -std=gnu89, -std=c89, or -fpermissive. (Especially if you use -fpermissive as a temporary workaround with intention to fix the underlying issues later, I'd suggest leaving the particular bug opened until it is done so.) -- You are receiving this mail because: You are on the CC list for the bug.

1 80

[Bug 1223783] New: Upgrade lapack to 3.12.0
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223783 Bug ID: 1223783 Summary: Upgrade lapack to 3.12.0 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: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Our lapack (at version 3.9.0) is pretty ancient at this point. We should consider bumping it straight to version 3.12.0 (released Nov 2023). Given the insane list of dependencies on lapack and its own rather insane list of patches used by Fedora [1], I thought of opening this tracking bug collecting the fallout that may or may not happen as a result of this upgrade (which I am starting work on, but seems more than a one-man job to be honest, so help welcome). The upcoming GCC14 breakage seems to be a good time to work on it since the latest version seems to fix this automatically. [1] https://src.fedoraproject.org/rpms/lapack/tree/rawhide -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1225296] New: Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225296 Bug ID: 1225296 Summary: Dual monitor not recognised after upgrade 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.schmidt(a)io-warnemuende.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Moin, moin, I am using openSUSE 15.5 on an old intel based x86 PC, equipped with a simple nvidia gforce and two monitors. The monitors are using a displayport connnection from the graphics card to the monitors via an Y-shaped cable. Both monitors are recognised correctly and can be configured to form a single graphical work space, when the system is up and running. After upgrading to openSUSE 15.6 this does not work any more. When booting, monitor 1 shows some firmware screen and the openSUSE boot screen, where the OS version (several subversions of 15.6 and frozen snapshots of 15.5) can be selected. Using the default option (15.6 from harddrive), the output of the boot process is moving to monitor 2, but monitor 1 is going to a "power saving sleep mode" and stays inactive frome here on. The boot process is finished correctly with monitor 2 as the only graphical device. Monitor 1 cannot be activated again. Switching off monitor 2 before booting, the system comes up without any valid output device. Monitor 1 goes to sleep after the system boot started. I did not check the system status with a remote ssh-connection yet. Switching off monitor 1 before booting, lets the system come up completely with monitor 2. Also the initial hardware screen is diplayerd there. In turn, booting from a read-only snapshot with openSUSE 15.5, both monitors are used as before. The nouveau-dri drivers are used, no propriatary nvidia driver is installed. Some upgrade history: - just to test, if the few graphic card cores could be used in a cuda environment, cuda was installed under 15.5. This failed and cuda was deinstalled. However, when upgrading later from 15.5 to 15.6 the cuda development environment was reinstalled automatically together with nvidia drivers. As a result the nvidia drivers allowed only for a single low resolution vga monitor. May be, this happened, since the nvidia repository was not deleted and there was some leftover from the cuda test. - with the ascii-yast the nvidia drivers (gforce003/004) and cuda could be removed and the nouveau-dri drivers where reinstalled - together with dependencies. This allows for a single monitor OS_15.6 system with high resolution, but the second monitor (monitor 1) is lost during the boot process as described above. Before I try to install from scratch just with the hope that the error goes away, I am reporting this strange behaviour here. May be, this helps to streamline the distribution. Any hints are very welcome - especially how to modify the bootloader options. Cheers, Martin Schmidt -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1224820] New: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224820 Bug ID: 1224820 Summary: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I recently assembled a computer based on the ASUS WRX90E Sage motherboard and a 32-core AMD Threadripper PRO CPU. In the BIOS, I enabled 64-bit PCIe remapping support to allow the OS to remap devices to 64-bit address space. For some odd reason, however, the system went into standby and could not recover. Pressing Control+Alt+F10 reported problems remapping the PCIe devices, and then there was a failure with BTRFS reading bad data, and the system hung. The NVME drive is an old Intel PCIe card I had lying around that only had light usage. I strongly suspect there are compatibility issues with the new motherboard chipset since it is pretty new. The WRX90 chipset is only used in two motherboards I am aware of, the ASUS board and an ASRock board. I could not capture the messages directly since the FS went read-only and it started spewing a ton of BTRFS errors before I could capture the screen. As for why it went into suspend mode to begin with, I have no idea. The reason I know it did is I sshed into the box remotely and got a broadcast message: Broadcast message from aaronw@localhost (Tue 2024-05-21 14:09:53 PDT): The system will suspend now! I will try disabling S4/S5 support in the BIOS and see if that helps and I can also try disabling the 64-bit PCIe remapping as well. System specs: ASUS Pro WRX90E Sage SE EEB motherboard with latest BIOS firmware AMD Threadripper Pro 7975WX CPU Gigabyte Ge-Force RTX4090 Windforce V2 24G graphics card Intel NVME drive Kingston Fury Renegade Pro 128GB ECC Registered DDR5 (PC5 48000) memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219494] New: libmfx no longer supported
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219494 Bug ID: 1219494 Summary: libmfx no longer supported Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- libmfx is no longer supported https://github.com/Intel-Media-SDK/MediaSDK DISCONTINUATION OF PROJECT. This project will no longer be maintained by Intel. This project has been identified as having known security escapes. Intel has ceased development and contributions including, but not limited to, maintenance, bug and security fixes, new releases, or updates, to this project. Intel no longer accepts patches to this project. If you have an ongoing need to use this project, are interested in independently developing it, or would like to maintain patches for the open source software community, please create your own fork of this project. [...] Let's get rid of it, i.e. remove the support from the following affected packages libavfilter7_110 libavutil56_70 libavcodec58_134 --> ffmpeg-4 vlc-noX --> vlc libavfilter8 libavutil57 libavcodec59 --> ffmpeg-5 gstreamer-plugins-bad --> gstreamer-plugins-bad Then drop libmfx package (includes libmfx-samples subpackage). -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Bug 1222754] New: Plasma Wayland: Keyboard layout is not applied to X11 applications
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222754 Bug ID: 1222754 Summary: Plasma Wayland: Keyboard layout is not applied to X11 applications Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kayboard layout configured at: System Settings > Input Devices > Keyboard > Layout is not applied to X11 applications. For example, when I add jp layout into the list, on Wayland applications, the layout become jp, but on X11 applications (e.g., xterm, vscode), the layout remains US. Here is output of xkb_keymap: ``` xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(evdev)" }; xkb_geometry { include "pc(pc105)" }; }; ``` Workaround: Run the following command $ setxkbmap jp * Plasma 5.27.11 * IBus 1.5.28 (which does not control key layouts on Wayland anymore) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218274] New: xfreerdp 2.4.0 Release 150400.3.23.1 fails with [ERROR][com.freerdp.core.fastpath]
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218274 Bug ID: 1218274 Summary: xfreerdp 2.4.0 Release 150400.3.23.1 fails with [ERROR][com.freerdp.core.fastpath] 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: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: haenig(a)cosifan.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: after updating freerdp to Release 150400.3.23.1 I am no longer able to connect to rdp Servers. After entering my password a window showing a fancy MS image as well as my logon name opens for a short time and then closes again on its own. the update has been done yesterday (2023-12-19) via 'zypper up' and therefore changed/updated other packages as well. Reproducible: Always Steps to Reproduce: 1. launch new rdp session (see details) 2. enter password Actual Results: # initiate session openconnect-leap:~> xfreerdp /kbd:0x00000407 /u:myusername /d:mydomain /v:myserverip [13:43:00:529] [6614:6615] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [13:43:00:843] [6614:6615] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [13:43:00:845] [6614:6615] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [13:43:00:845] [6614:6615] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [13:43:00:102] [6614:6615] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate (18)' at stack position 0 [13:43:00:103] [6614:6615] [WARN][com.freerdp.crypto] - CN = myservername.mydomain Password: [13:43:07:261] [6614:6615] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [13:43:07:262] [6614:6615] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [13:43:07:279] [6614:6615] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [13:43:07:287] [6614:6615] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - Fastpath update Bitmap [1] failed, status 0 [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data: fastpath_recv_update() - -1 [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data() fail [13:43:14:706] [6614:6615] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -3 [13:43:14:706] [6614:6615] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [13:43:14:706] [6614:6615] [INFO][com.freerdp.client.common] - Network disconnect! [13:43:14:706] [6614:6615] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor Expected Results: working rdesktop session with freerdp 2.4.0 Release 150400.3.20.1 everything was working O.K. Example: lverm@openvpn-leap:~> xfreerdp /kbd:0x00000407 /u:myusername /d:mydomain /v:myserverip [13:49:37:746] [3026:3027] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [13:49:37:066] [3026:3027] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [13:49:37:068] [3026:3027] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [13:49:37:068] [3026:3027] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [13:49:37:274] [3026:3027] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate (18)' at stack position 0 [13:49:37:274] [3026:3027] [WARN][com.freerdp.crypto] - CN = myservername.mydomain Password: [13:49:50:584] [3026:3027] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [13:49:50:584] [3026:3027] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [13:49:50:617] [3026:3027] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [13:49:50:637] [3026:3027] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd [13:49:55:507] [3026:3027] [INFO][com.freerdp.client.x11] - Logon Error Info SESSION_ID [LOGON_MSG_SESSION_CONTINUE] => here I have window open with a working rdp session -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1223533] New: cockpit: /nonexistent/libexec/cockpit-askpass
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223533 Bug ID: 1223533 Summary: cockpit: /nonexistent/libexec/cockpit-askpass Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874558 --> https://bugzilla.suse.com/attachment.cgi?id=874558&action=edit nonexistent/libexec/cockpit-askpass On freshly installed Leap 15.6 + cockpit If you login to localhost:9090 as a standard user and you try to enable the admin view by clicking on the cockpit homescreen button, then cockpit will raise following error Problem becoming administrator Sudo: unable to run /nonexistent/libexec/cockpit-askpass: No such file or directory sudo: no password was provided sudo: a password is required lkocman@localhost:~/Workspace/obs> sudo zypper in cockpit [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Retrieving repository 'packman' metadata .....................................................................................................................................................[done] Building repository 'packman' cache ..........................................................................................................................................................[done] Loading repository data... Warning: Repository 'update-non-oss (15.6)' metadata expired since 2023-09-21 14:47:58 CEST. Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manually refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. Reading installed packages... Resolving package dependencies... The following 2 recommended packages were automatically selected: cockpit-networkmanager cockpit-storaged The following package is recommended, but will not be installed due to conflicts or dependency issues: cockpit-packagekit The following 2 packages are suggested, but will not be installed: cockpit-pcp cockpit-selinux The following 8 NEW packages are going to be installed: cockpit cockpit-bridge cockpit-networkmanager cockpit-storaged cockpit-system cockpit-ws libpwquality-tools libudisks2-0_lvm2 8 new packages to install. Overall download size: 7.1 MiB. Already cached: 0 B. After the operation, additional 8.3 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: cockpit-bridge-309-bp156.1.2.x86_64 (repo-oss (15.6)) (1/8), 471.8 KiB Retrieving: cockpit-bridge-309-bp156.1.2.x86_64.rpm .............................................................................................................................[done (10.9 KiB/s)] Retrieving: cockpit-ws-309-bp156.1.2.x86_64 (repo-oss (15.6)) (2/8), 1.7 MiB Retrieving: cockpit-ws-309-bp156.1.2.x86_64.rpm ..................................................................................................................................[done (8.4 MiB/s)] Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64 (repo-oss (15.6)) (3/8), 19.4 KiB Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64.rpm ...................................................................................................................................[done] Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 (repo-oss (15.6)) (4/8), 57.0 KiB Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64.rpm .....................................................................................................................[done (93.5 KiB/s)] Retrieving: cockpit-system-309-bp156.1.2.noarch (repo-oss (15.6)) (5/8), 3.2 MiB Retrieving: cockpit-system-309-bp156.1.2.noarch.rpm ..............................................................................................................................[done (6.7 MiB/s)] Retrieving: cockpit-storaged-309-bp156.1.2.noarch (repo-oss (15.6)) (6/8), 850.0 KiB Retrieving: cockpit-storaged-309-bp156.1.2.noarch.rpm ............................................................................................................................[done (4.2 MiB/s)] Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch (repo-oss (15.6)) (7/8), 827.8 KiB Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch.rpm ......................................................................................................................[done (3.8 MiB/s)] Retrieving: cockpit-309-bp156.1.2.x86_64 (repo-oss (15.6)) (8/8), 45.5 KiB Retrieving: cockpit-309-bp156.1.2.x86_64.rpm .................................................................................................................................................[done] Checking for file conflicts: .................................................................................................................................................................[done] (1/8) Installing: cockpit-bridge-309-bp156.1.2.x86_64 ........................................................................................................................................[done] (2/8) Installing: cockpit-ws-309-bp156.1.2.x86_64 ............................................................................................................................................[done] (3/8) Installing: libpwquality-tools-1.4.5-150600.2.2.x86_64 .................................................................................................................................[done] (4/8) Installing: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 ................................................................................................................................[done] (5/8) Installing: cockpit-system-309-bp156.1.2.noarch ........................................................................................................................................[done] (6/8) Installing: cockpit-storaged-309-bp156.1.2.noarch ......................................................................................................................................[done] (7/8) Installing: cockpit-networkmanager-309-bp156.1.2.noarch ................................................................................................................................[done] (8/8) Installing: cockpit-309-bp156.1.2.x86_64 ...............................................................................................................................................[done] lkocman@localhost:~/Workspace/obs> sudo systemctl enable --now cockpit.socket Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket. lkocman@localhost:~/Workspace/obs> -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225174] New: conflicto actualizacion
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225174 Bug ID: 1225174 Summary: conflicto actualizacion Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: allanvejar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- <html>Ha fallado la resolución de dependencias:<br/><br/>el elemento tlp-1.6.1-2.1.noarch que se va a instalar tiene un conflicto con tuned, que proporciona el elemento tuned-2.22.1.2+git.86ac977-3.1.noarch instalado</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1223967] New: %suse_build_hwcaps_libs fails to generate -x86_64-v3 packages when shared library is an update-alternatives link
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223967 Bug ID: 1223967 Summary: %suse_build_hwcaps_libs fails to generate -x86_64-v3 packages when shared library is an update-alternatives link Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ## Originally reported on GitHub: https://github.com/openSUSE/obs-build/issues/1001 This came up when trying to enable -v3 hwcaps enhanced libs for `lapack`. As it turns out, `lapack` uses update-alternatives to create a symlink `/usr/lib64/libblas.so.3` pointing to the real library `/usr/lib64/blas/libblas.so.3` via `update-alternatives` called during `post`. The file `/usr/lib64/libblas.so.3` does not exist a build-time, but created by update-alternatives during `post` install. It is also marked as `%ghost` in the package. Apparently `%{?suse_build_hwcaps_libs}` cannot handle this. It tries to copy the non-existent — at build time — `/usr/lib64/libblas.so.3` and fails catastrophically _after_ actually generating the hwaps libs. This is what I see in the log. Note the error: `mv: cannot stat '.cfiles/usr/lib64/liblapack.so.3': No such file or directory` which suggests it is trying to move a non-existent file which will be created during `post` install: > [ 218s] RPMLINT report: > [ 218s] =============== > [ 220s] ============================ rpmlint session starts ============================ > [ 220s] rpmlint: 2.5.0 > [ 220s] configuration: > [ 220s] /opt/testing/lib64/python3.11/rpmlint/configdefaults.toml > [ 220s] /opt/testing/share/rpmlint/cron-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/dbus-services.toml > [ 220s] /opt/testing/share/rpmlint/device-files-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/licenses.toml > [ 220s] /opt/testing/share/rpmlint/opensuse.toml > [ 220s] /opt/testing/share/rpmlint/pam-modules.toml > [ 220s] /opt/testing/share/rpmlint/permissions-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/pie-executables.toml > [ 220s] /opt/testing/share/rpmlint/polkit-rules-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/scoring.toml > [ 220s] /opt/testing/share/rpmlint/security.toml > [ 220s] /opt/testing/share/rpmlint/sudoers-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/sysctl-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/systemd-tmpfiles.toml > [ 220s] /opt/testing/share/rpmlint/users-groups.toml > [ 220s] /opt/testing/share/rpmlint/world-writable-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/zypper-plugins.toml > [ 220s] rpmlintrc: > [ 220s] /home/abuild/rpmbuild/SOURCES/lapack.rpmlintrc > [ 220s] checks: 41, packages: 21 > [ 220s] > [ 220s] libblas3.x86_64: I: package-supports-update-alternatives > [ 220s] libcblas3.x86_64: I: package-supports-update-alternatives > [ 220s] liblapack3.x86_64: I: package-supports-update-alternatives > [ 220s] liblapacke3.x86_64: I: package-supports-update-alternatives > [ 220s] libblas3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] libcblas3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] liblapack3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] liblapacke3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] Check time report (>1% & >0.1s): > [ 220s] Check Duration (in s) Fraction (in %) Checked files > [ 220s] ExtractRpm 0.3 30.3 > [ 220s] SignatureCheck 0.2 19.6 > [ 220s] BinariesCheck 0.2 19.2 > [ 220s] SharedLibraryPolicyCheck 0.2 16.2 > [ 220s] TOTAL 1.0 100.0 > [ 220s] > [ 220s] 21 packages and 0 specfiles checked; 0 errors, 0 warnings, 131 filtered, 0 badness; has taken 1.1 s > [ 220s] > [ 220s] ... cleaning ccache > [ 220s] setting SOURCE_DATE_EPOCH_MTIME to 1714856125 > [ 220s] 1 > [ 220s] ... saving ccache archive > [ 220s] ... creating baselibs > [ 220s] setting SOURCE_DATE_EPOCH_MTIME to 1714856125 > [ 220s] no targets for arch x86_64, skipping lapack-devel > [ 220s] no targets for arch x86_64, skipping liblapack3 > [ 220s] no targets for arch x86_64, skipping lapacke-devel > [ 220s] no targets for arch x86_64, skipping libblas3 > [ 220s] no targets for arch x86_64, skipping liblapacke3 > [ 220s] no targets for arch x86_64, skipping libcblas3 > [ 220s] no targets for arch x86_64, skipping cblas-devel > [ 220s] no targets for arch x86_64, skipping blas-devel > [ 220s] liblapack3(x86_64:x86-64-v3): writing specfile... > [ 220s] liblapack3(x86_64:x86-64-v3): running build... > [ 220s] rpmbuild failed: 256 > [ 220s] re-running in verbose mode: > [ 220s] using SOURCE_DATE_EPOCH with value 1714856124 as build time > [ 220s] Executing(%prep): /usr/bin/bash -e /var/tmp/rpm-tmp.r51odx > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + RPM_EC=0 > [ 220s] ++ jobs -p > [ 220s] + exit 0 > [ 220s] Executing(%build): /usr/bin/bash -e /var/tmp/rpm-tmp.dHOH58 > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT > [ 220s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + RPM_EC=0 > [ 220s] ++ jobs -p > [ 220s] + exit 0 > [ 220s] Executing(%install): /usr/bin/bash -e /var/tmp/rpm-tmp.Aiq5Zt > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT > [ 220s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + cd /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + mkdir -p .cfiles > [ 220s] + pushd .cfiles > [ 220s] ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/.cfiles ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + cat > [ 220s] + rpm2cpio //home/abuild/rpmbuild/RPMS/x86_64_v3/liblapack3-3.12.0-94.1.x86_64_v3.rpm > [ 220s] + cpio -i -d -v -E .filelist > [ 220s] ./usr/lib64/lapack/liblapack.so.3 > [ 221s] ./usr/lib64/lapack/liblapack.so.3.12.0 > [ 221s] 15311 blocks > [ 221s] + popd > [ 221s] ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack > [ 221s] + mv .cfiles/usr/lib64/lapack/liblapack.so.3 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack/liblapack.so.3 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack > [ 221s] + mv .cfiles/usr/lib64/lapack/liblapack.so.3.12.0 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack/liblapack.so.3.12.0 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3 > [ 221s] + mv .cfiles/usr/lib64/liblapack.so.3 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/liblapack.so.3 > [ 221s] mv: cannot stat '.cfiles/usr/lib64/liblapack.so.3': No such file or directory > [ 221s] error: Bad exit status from /var/tmp/rpm-tmp.Aiq5Zt (%install) > [ 221s] > [ 221s] RPM build errors: > [ 221s] Bad exit status from /var/tmp/rpm-tmp.Aiq5Zt (%install) > [ 221s] ### VM INTERACTION START ### > [ 221s] [ 217.139930][ T1] sysrq: Power Off > [ 221s] [ 217.141087][ T10] reboot: Power down > [ 221s] ### VM INTERACTION END ### > [ 221s] > [ 221s] i01-ch1d failed "build lapack.spec" at Mon May 6 11:51:16 UTC 2024. > [ 221s] FWIW, here is the baselibs.conf: > ... > > liblapack3 > -/usr/lib(64)?/liblapack.so.3 > requires "update-alternatives" > postin "ln -sf /etc/alternatives/liblapack.so.3_<targettype> /usr/%_lib/liblapack.so.3" > postin "/usr/sbin/update-alternatives --force --install /usr/%_lib/liblapack.so.3 liblapack.so.3_<targettype> /usr/%_lib/lapack/liblapack.so.3 50" > postun "/usr/sbin/update-alternatives --remove liblapack.so.3_<targettype> /usr/%_lib/lapack/liblapack.so.3" > > ... And attached is the full build log if it helps (from https://build.opensuse.org/package/show/home:badshah400:lapackv3/lapack). -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1223615] New: Nextcloud-desktop can't add multiple accounts
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223615 Bug ID: 1223615 Summary: Nextcloud-desktop can't add multiple accounts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: karlggest(a)yahoo.es QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Seems since some Nextcloud-desktop versions app can't show add account option in the menu. Steps: 1. Start Nextcloud-desktop 2. Click on the app on system tray, main window appears. 3. Click on dropdown menu. Add accounts appears. 4. Add the first account. Complain all details and finish. 5. Go to steps 2, 3 and 4 again. Add accounts option does not appear I try app from standard repo and flatpak package. Both fails. Appimage from https://nextcloud.com/install/#install-clients works as expected. Extra: Another packages even in another distros fails in the same way: https://help.nextcloud.com/t/nextcloud-desktop-client-with-support-for-mult… https://help.nextcloud.com/t/desktop-clients-number-of-multiple-accounts/10… Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215646] New: Fontconfig file oversight on Noto Sans CJK fonts
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215646 Bug ID: 1215646 Summary: Fontconfig file oversight on Noto Sans CJK fonts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mn230199(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On /etc/fonts/conf.d/60-family-prefer.conf the Noto Sans CJK fonts don't have the 'CJK' part in their names (instead of "Noto Sans CJK JP" it appears as "Noto Sans JP"), making the fonts not get used for CJK text. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223366] New: network:im:signal/signal-desktop: Segmentation fault with 7.5.1-1.2 and 7.5.1-1.3
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223366 Bug ID: 1223366 Summary: network:im:signal/signal-desktop: Segmentation fault with 7.5.1-1.2 and 7.5.1-1.3 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: brunopitrus(a)hotmail.com Reporter: john-susecom(a)pelago.org.uk QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Signal Desktop is segmentation faulting for me, since version 7.5.1-1.2. Log: Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' } NODE_ENV production NODE_CONFIG_DIR /usr/libexec/signal-desktop/config NODE_CONFIG {} ALLOW_CONFIG_MUTATIONS undefined HOSTNAME hp450g4 NODE_APP_INSTANCE undefined SUPPRESS_NO_CONFIG_WARNING undefined SIGNAL_ENABLE_HTTP undefined userData: /home/john/.config/Signal config/get: Successfully read user config file config/get: Successfully read ephemeral config file getLogger: Logger not yet initialized! crashReporter: enabled making app single instance {"level":30,"time":"2024-04-24T16:17:06.386Z","msg":"crashReporter: enabled"} {"level":30,"time":"2024-04-24T16:17:06.395Z","msg":"got fast localeOverride setting null"} {"level":30,"time":"2024-04-24T16:17:06.395Z","msg":"app.ready: hour cycle preference: UnknownPreference"} {"level":30,"time":"2024-04-24T16:17:06.395Z","msg":"app.ready: preferred system locales: en-GB, en"} {"level":30,"time":"2024-04-24T16:17:06.396Z","msg":"locale: Supported locales: af-ZA, ar, az-AZ, bg-BG, bn-BD, bs-BA, ca, cs, da, de, el, en, es, et-EE, eu, fa-IR, fi, fr, ga-IE, gl-ES, gu-IN, he, hi-IN, hr-HR, hu, id, it, ja, ka-GE, kk-KZ, km-KH, kn-IN, ko, ky-KG, lt-LT, lv-LV, mk-MK, ml-IN, mr-IN, ms, my, nb, nl, pa-IN, pl, pt-BR, pt-PT, ro-RO, ru, sk-SK, sl-SI, sq-AL, sr, sv, sw, ta-IN, te-IN, th, tl-PH, tr, ug, uk-UA, ur, vi, yue, zh-CN, zh-HK, zh-Hant"} {"level":30,"time":"2024-04-24T16:17:06.396Z","msg":"locale: Preferred locales: en-GB, en"} {"level":30,"time":"2024-04-24T16:17:06.400Z","msg":"locale: Locale Override: null"} {"level":30,"time":"2024-04-24T16:17:06.404Z","msg":"locale: Matched locale: en"} {"level":40,"time":"2024-04-24T16:17:06.485Z","msg":"intl.onWarn [@formatjs/intl] \"defaultRichTextElements\" was specified but \"message\" was not pre-compiled. \nPlease consider using \"@formatjs/cli\" to pre-compile your messages for performance.\nFor more details see https://formatjs.io/docs/getting-started/message-distribution"} {"level":30,"time":"2024-04-24T16:17:06.486Z","msg":"locale: Text info direction for en: ltr"} {"level":30,"time":"2024-04-24T16:17:06.486Z","msg":"getSystemTraySetting got value MinimizeToAndStartInSystemTray"} {"level":30,"time":"2024-04-24T16:17:06.486Z","msg":"getSystemTraySetting returning MinimizeToAndStartInSystemTray"} {"level":30,"time":"2024-04-24T16:17:06.488Z","msg":"app ready"} {"level":30,"time":"2024-04-24T16:17:06.488Z","msg":"starting version 7.5.1"} {"level":30,"time":"2024-04-24T16:17:06.488Z","msg":"media access status [object Undefined] [object Undefined]"} {"level":30,"time":"2024-04-24T16:17:06.491Z","msg":"got fast theme-setting value dark"} {"level":30,"time":"2024-04-24T16:17:06.493Z","msg":"got fast theme-setting value dark"} {"level":30,"time":"2024-04-24T16:17:06.493Z","msg":"got fast spellcheck setting true"} {"level":30,"time":"2024-04-24T16:17:06.494Z","msg":"Initializing BrowserWindow config: {\"show\":false,\"width\":683,\"height\":696,\"minWidth\":300,\"minHeight\":200,\"autoHideMenuBar\":false,\"titleBarStyle\":\"default\",\"backgroundColor\":\"#121212\",\"webPreferences\":{\"devTools\":false,\"spellcheck\":true,\"enableBlinkFeatures\":\"CSSPseudoDir,CSSLogical\",\"enablePreferredSizeMode\":true,\"nodeIntegration\":false,\"nodeIntegrationInWorker\":false,\"sandbox\":false,\"contextIsolation\":true,\"preload\":\"[REDACTED]/preload.bundle.js\",\"backgroundThrottling\":true,\"disableBlinkFeatures\":\"Accelerated2dCanvas,AcceleratedSmallCanvases\"},\"icon\":\"[REDACTED]/images/signal-logo-desktop-linux.png\",\"x\":3,\"y\":28}"} {"level":30,"time":"2024-04-24T16:17:06.594Z","msg":"spellcheck: user locales: [\"en-GB\",\"en\"]"} {"level":30,"time":"2024-04-24T16:17:06.594Z","msg":"spellcheck: available spellchecker languages: [\"af\",\"bg\",\"ca\",\"cs\",\"cy\",\"da\",\"de\",\"de-DE\",\"el\",\"en\",\"en-AU\",\"en-CA\",\"en-GB\",\"en-GB-oxendict\",\"en-US\",\"es\",\"es-419\",\"es-AR\",\"es-ES\",\"es-MX\",\"es-US\",\"et\",\"fa\",\"fo\",\"fr\",\"fr-FR\",\"he\",\"hi\",\"hr\",\"hu\",\"hy\",\"id\",\"it\",\"it-IT\",\"ko\",\"lt\",\"lv\",\"nb\",\"nl\",\"pl\",\"pt\",\"pt-BR\",\"pt-PT\",\"ro\",\"ru\",\"sh\",\"sk\",\"sl\",\"sq\",\"sr\",\"sv\",\"ta\",\"tg\",\"tr\",\"uk\",\"vi\"]"} {"level":30,"time":"2024-04-24T16:17:06.594Z","msg":"spellcheck: setting languages to: [\"en-GB\",\"en\"]"} {"level":40,"time":"2024-04-24T16:17:06.595Z","msg":"MainSQL: Database log code=283: recovered 580 frames from WAL file [REDACTED]/sql/db.sqlite-wal"} {"level":30,"time":"2024-04-24T16:17:06.595Z","msg":"MainSQL: updateSchema:\n Current user_version: 1010;\n Most recent db schema: 1010;\n SQLite version: 3.42.0;\n SQLCipher version: 4.5.5 community;\n (deprecated) schema_version: 409;\n"} {"level":30,"time":"2024-04-24T16:17:07.167Z","msg":"got fast theme-setting value dark"} {"level":30,"time":"2024-04-24T16:17:08.023Z","msg":"got fast spellcheck setting true"} {"level":30,"time":"2024-04-24T16:17:08.033Z","msg":"System tray service: created"} {"level":30,"time":"2024-04-24T16:17:08.034Z","msg":"System tray service: updating main window. Previously, there was not a window, and now there is"} {"level":30,"time":"2024-04-24T16:17:08.034Z","msg":"System tray service: rendering no tray"} {"level":30,"time":"2024-04-24T16:17:08.034Z","msg":"System tray service: enabling"} {"level":30,"time":"2024-04-24T16:17:08.034Z","msg":"System tray service: rendering the tray"} {"level":30,"time":"2024-04-24T16:17:08.034Z","msg":"System tray service: creating the tray"} {"level":30,"time":"2024-04-24T16:17:08.036Z","msg":"Begin ensuring permissions"} {"level":30,"time":"2024-04-24T16:17:08.038Z","msg":"main window is ready-to-show"} {"level":30,"time":"2024-04-24T16:17:08.039Z","msg":"Ensuring file permissions for 4 files"} {"level":30,"time":"2024-04-24T16:17:08.041Z","msg":"Finish ensuring permissions in 5ms"} {"level":30,"time":"2024-04-24T16:17:08.699Z","msg":"MainSQL: slow query getAllStories duration=561ms"} {"level":30,"time":"2024-04-24T16:17:08.829Z","msg":"Prevent display sleep service: allowing display sleep"} {"level":30,"time":"2024-04-24T16:17:08.829Z","msg":"Background throttling enabled because no call is active"} {"level":30,"time":"2024-04-24T16:17:09.164Z","msg":"updater/start: Updates disabled - not starting new version checks"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"App loaded - time: 2678"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"SQL init - time: 202"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"Preload - time: 822"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"WebSocket connect - time: 588"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"Processed count: 12"} {"level":30,"time":"2024-04-24T16:17:09.165Z","msg":"Messages per second: 9.46372239747634"} {"level":40,"time":"2024-04-24T16:17:09.212Z","msg":"crashReports: 10 pending dumps found"} {"level":30,"time":"2024-04-24T16:17:13.853Z","msg":"System tray service: rendering the tray"} Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224059] New: Bumblebee freezes laptop at boot
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224059 Bug ID: 1224059 Summary: Bumblebee freezes laptop at boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aleksey.rukhlenko(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I found two ways to reproduce this bug. 1. Only suse-prime and bbswitch are installed. In this case, you need to switch to nvidia drivers, logout, login, then switch to intel, logout, and then the system freezes. After forced switch off and on, the booting process freezes at the starting of X server. 2. bbswitch, bumblebee and primusrun are installed, bumblebee daemon is configured to start on boot, the user is added to bumblebee and video groups. In this case, system freezes on boot during starting X server. In addition, the very presence of bbswitch and suse-prime installed screws up the laptop sound, even if intel drivers are chosen and system does not freeze. Hardware: Dell XPS 17 9700 OS: Fresh install of OpenSUSE 15.6 64-bit. Nvidia drivers: nvidia-G06 Kind regards, Oleksii -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213879] New: Could not allocate memory for RTAS
by bugzilla_noreply＠suse.com 13 Jun '24

13 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 Bug ID: 1213879 Summary: Could not allocate memory for RTAS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: PowerPC OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dmitriy.markov(a)mezame.ru QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: Good afternoon. While booting from iso for further installation of the system, I encountered the error "Could not allocate memory for RTAS". The problem is only present in the openSUSE Leap 15.5 ppc64le distribution. OpenSUSE Leap 15.4 ppc64le does not have this problem. Of course, on the Internet there was a solution from the equipment manufacturer. (https://www.ibm.com/support/pages/could-not-allocate-memory-rtas-grub-or-ya…) But it does not help and the error remains. My opinion is that this is a bug in the distribution, if it is not, please let me know about it. Reproducible: Always Steps to Reproduce: 1.Booting LPAR from CD/DVD openSUSE-Leap-15.5-DVD-ppc64le-Media.iso 2.In the bootloader, select "install operating system" 3.We get an error Actual Results: We get an error Welcome to GRUB! search prep from disk `ieee1275//vdevice/v-s csi@3000000b/disk@8100000000000000' error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. earlycfg: root=memdisk prefix=(memdisk)/ bdev=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000 bpart=,1 bpath=/boot/ppc64le/grub2-ieee1275 Reading vars from (ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000) error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. ENV_HINT= ENV_GRUB_DIR= ENV_FS_UUID= searching for /boot/ppc64le/grub2-ieee1275/grub.cfg /boot/ppc64le/grub2-ieee1275/grub.cfg is on ieee1275//vdevice/v-scsi@3000000b/disk@81000 00000000000,1 prefix=(ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1)/boot/ppc64le /grub2-ieee1275 root=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1 Loading kernel ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 5.14.21-150500.53-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binut ils; SUSE Linux Enterprise 15) 2.39.0.20220810-150100.7.40) #1 SMP Wed May 10 07:56:26 UTC 2023 (b630043) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/boot/ppc64le/linux Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 000000001fef0000 alloc_top : 0000000020000000 alloc_top_hi : 0000000020000000 rmo_top : 0000000020000000 ram_top : 0000000020000000 Could not allocate memory for RTAS EXIT called ok 0 > Expected Results: The system installer is loading iso SHA-256 checksum - pass My HW - IBM Power E880 SLES 12SP5 - also not affected by this error. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1222151] New: XCURSOR_THEME is missing from the environment variables
by bugzilla_noreply＠suse.com 12 Jun '24

12 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222151 Bug ID: 1222151 Summary: XCURSOR_THEME is missing from the environment variables Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: 95kreaninw95(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- XCURSOR_THEME should be specified in the environment variables. Otherwise, some apps, Blender for example, would run with a super tiny mouse in Wayland session. And from missing XCURSOR_THEME, specifying XCURSOR_SIZE wouldn't work. See Blender issue: https://projects.blender.org/blender/blender/issues/105895 It seems XCURSOR_THEME used to be specified in openSUSE. But due to issue #1157617 (https://bugzilla.suse.com/show_bug.cgi?id=1157617), XCURSOR_THEME was removed altogether. From my understanding, the issue #1157617 happened because of the incorrect XCURSOR_THEME value that was specified by the system script. The fix didn't correct the XCURSOR_THEME value, but removed XCURSOR_THEME altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215701] New: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag
by bugzilla_noreply＠suse.com 12 Jun '24

12 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215701 Bug ID: 1215701 Summary: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/379815/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: rfrohl(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- yt-dlp is a youtube-dl fork with additional features and fixes. yt-dlp allows the user to provide shell command lines to be executed at various stages in its download steps through the `--exec` flag. This flag allows output template expansion in its argument, so that metadata values may be used in the shell commands. The metadata fields can be combined with the `%q` conversion, which is intended to quote/escape these values so they can be safely passed to the shell. However, the escaping used for `cmd` (the shell used by Python's `subprocess` on Windows) does not properly escape special characters, which can allow for remote code execution if `--exec` is used directly with maliciously crafted remote data. This vulnerability only impacts `yt-dlp` on Windows, and the vulnerability is present regardless of whether `yt-dlp` is run from `cmd` or from `PowerShell`. Support for output template expansion in `--exec`, along with this vulnerable behavior, was added to `yt-dlp` in version 2021.04.11. yt-dlp version 2023.09.24 fixes this issue by properly escaping each special character. `\n` will be replaced by `\r` as no way of escaping it has been found. It is recommended to upgrade yt-dlp to version 2023.09.24 as soon as possible. Also, always be careful when using --exec, because while this specific vulnerability has been patched, using unvalidated input in shell commands is inherently dangerous. For Windows users who are not able to upgrade: 1. Avoid using any output template expansion in --exec other than {} (filepath). 2. If expansion in --exec is needed, verify the fields you are using do not contain ", | or &. 3. Instead of using --exec, write the info json and load the fields from it instead. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40581 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222343] New: protobuf linking issue
by bugzilla_noreply＠suse.com 12 Jun '24

12 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222343 Bug ID: 1222343 Summary: protobuf linking issue 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: Development Assignee: screening-team-bugs(a)suse.de Reporter: jonaski(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, I'm getting several linking errors while building strawberry on leap. Full log can be seen on https://build.opensuse.org/package/show/multimedia:apps/strawberry This happened a few weeks ago, and it seem to be the same issue on both Leap 15.5 and 15.6, it is not an issue on Tumbleweed or any other linux distribution (Fedora, Debian and Ubuntu builds fine). I suspect an issue with the protobuf library on Leap. From the build log: [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: CMakeFiles/strawberry-tagreader.dir/tagreaderworker.cpp.o: in function `google::protobuf::internal::ArenaStringPtr::SetBytes(void const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:495:(.text+0x44e): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadertaglib.cpp.o): in function `google::protobuf::internal::ArenaStringPtr::Set(char const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:470:(.text+0x9935): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: /usr/include/google/protobuf/arenastring.h:470:(.text+0x9976): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::SongMetadata::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2565:(.text+0x1886): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2769:(.text+0x18a6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3007:(.text+0x18c6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3211:(.text+0x18e6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3463:(.text+0x1906): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o):/home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3939: more undefined references to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' follow [ 76s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1222971] New: Add `zypper pa --TBD` to show @System packages
by bugzilla_noreply＠suse.com 12 Jun '24

12 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222971 Bug ID: 1222971 Summary: Add `zypper pa --TBD` to show @System packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installed packages (-i) divide into those - available in an active repo - not available in an active repo (@System) @System is not the same as --orphaned, because orphaned implies that also no update candidate for the package is available (different version or renamed). An option to query them is desired. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225432] New: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text
by bugzilla_noreply＠suse.com 12 Jun '24

12 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225432 Bug ID: 1225432 Summary: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: locilka(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875149 --> https://bugzilla.suse.com/attachment.cgi?id=875149&action=edit Snippet of the log When iSCSI Targets are being discovered in Agama, the iSCSI library logs all the details. Sadly, also including passwords. How to reproduce? Easily -> Start Agama Installer -> Go to Storage details -> Click Prepare devices by configuring advanced storage technologies -> Choose iSCSI -> Click Discover iSCSI targets -> Fill-up some users/passwords -> Click Confirm This will be most probably the same in YaST as well because it uses the same library. BTW, there are two entries for user/password, but you can see only the first one in the log. That's most probably because the second one would be used later, if the first one succeeds (not my case). Additionally, even the save_y2logs script does not remove the passwords. maybe because the string in the log this: {"name"=>"discovery.sendtargets.auth.password", "value"=>"and their password", "kind"=>"value", "type"=>1, "comment"=>""} -- You are receiving this mail because: You are on the CC list for the bug.

1 11