May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225378] New: [Agama][Milestone8+] Installation progress does not report libzypp errors, e.g., if the package fails to install
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225378 Bug ID: 1225378 Summary: [Agama][Milestone8+] Installation progress does not report libzypp errors, e.g., if the package fails to install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major 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 875135 --> https://bugzilla.suse.com/attachment.cgi?id=875135&action=edit YaST logs I have created a system with too small /usr and /var, both 500 MiB encrypted XFS. While that might sound like a useful size, there is basically almost no free space left for data already after formatting. See bug #1225364 and bug #1225371. During the actual installation of RPMs, the space run out and libzypp started to report these errors, example: [zypp::exec] abstractspawnengine.cc(checkStatus):182 Pid 10413 exited with status 1 [zypp-core] Exception.cc(log):202 RpmDb.cc(doInstallPackage):1846 THROW: Subprocess failed. Error: RPM failed: Command exited with status 1. [zypp-core] Exception.cc(log):202 History: [zypp-core] Exception.cc(log):202 - installing package xfce4-power-manager-lang-4.18.3-1.3.noarch needs 2MB more space on the /usr filesystem [zypp-core] Exception.cc(log):202 [zypp-core] PathInfo.cc(unlink):711 unlink /mnt/var/cache/zypp/packages/https-download.opensuse.org-425fd75b/noarch/xfce4-power-manager-lang-4.18.3-1.3.noarch.rpm So libzypp failed to install the package, but there was no error in the UI. At the end, Agama congratulated me to a successful installation and told me to reboot. Many have obviously failed, the system would not boot. It's good that libstorage failures are reported, but failures from libzypp don't seem to be. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225371] New: [Agama][Milestone8+] Software needs to check the available space
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225371 Bug ID: 1225371 Summary: [Agama][Milestone8+] Software needs to check the available space 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 875134 --> https://bugzilla.suse.com/attachment.cgi?id=875134&action=edit YaST logs I've tuned the Storage proposal to contain two encrypted XFS file systems for /var and /usr: - partition: size: 500 MiB start: 405466 MiB (395.96 GiB) name: "/dev/nvme0n1p8" type: primary id: linux file_system: xfs mount_point: "/var" encryption: type: luks name: "/dev/mapper/cr_var" password: "***" - partition: size: 500 MiB start: 405966 MiB (396.45 GiB) name: "/dev/nvme0n1p9" type: primary id: linux file_system: xfs mount_point: "/usr" encryption: type: luks name: "/dev/mapper/cr_usr" password: "***" These partitions really have 500 MiB, but XFS takes the first 300 MiB just for metadata/log (see bug #1220728) and before this, the encryption itself also takes something. The result is that these partitions have just a tiny free space for real data. The information (and counting) about free space probably belongs to Storage/libstorage-ng, but Software should use it and check if the list of selected packages really fits. Or at least guess that and report back a warnig (?) if the doesn't. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225364] New: [Agama][Milestone8+] Storage needs to have better min sizes for file systems
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225364 Bug ID: 1225364 Summary: [Agama][Milestone8+] Storage needs to have better min sizes for file systems 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 875133 --> https://bugzilla.suse.com/attachment.cgi?id=875133&action=edit YaST logs In bug #1220728 the minimal size of an XFS file system has been raised from 40 to 300 MB. Libstorage has been changed by https://github.com/openSUSE/libstorage-ng/pull/990 As it shows now, it's not just simple like that. Creating a 300 MiB partition with XFS is possible, but if that partition is encrypted, there is only 284 MiB left for the file system. And then mkfs.xfs still complains. And even if it was slightly bigger, it would not have enough space basically for anything. These minimal sizes are not visible to the user or the Installer (?). I will report another bug for the Installer (Agama) to use mounted file systems for checking the free space - if the system actually fits, but it will need to report the real free space - i.e., size without metadata/log/... I've used 500 MiB partitions. They run out of space pretty quickly. I'm afraid we might need have some better checks closer to the reality. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222715] New: segmentation fault with vdr-plugin-xineliboutput and libvdpau
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222715 Bug ID: 1222715 Summary: segmentation fault with vdr-plugin-xineliboutput and libvdpau 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: Other Assignee: screening-team-bugs(a)suse.de Reporter: pmlists(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, With a fresh new installation of Leap-15.5 I get a segmentation fault when trying to run vdr with xineliboutput and vdpau video driver. Steps to reproduce: - new installation of Leap-15.5 (basic graphical interface) - zypper ar https://download.opensuse.org/repositories/vdr/15.5/vdr.repo - zypper in vdr-plugin-xineliboutput - vdr -P"xineliboutput -Vvdpau" Last lines on the terminal: video_decoder: first_frame_flag = 2. load_plugins: plugin dxr3-mpeg2 failed to instantiate itself. video_out_vdpau: video surface #9 (1920 x 1080) aligned to (1920 x 1088). video_out: vo_open (0x7f414c541640) load_plugins: plugin vdpau_mpeg12 will be used for video streamtype 00. video_out_vdpau: video surface #10 (704 x 576). Segmentation fault Last line of journal: vdr[4629]: [4639] [xine..put] cXinelibLocal::Action - fe config OK vdr[4629]: [4646] [demux_vdr] video fifo flush and decoder reset after still image vdr[4629]: [4646] [demux_vdr] H.264 scanner: Possible MPEG2 start code (0xb3) kernel: Local decoder/d[4643]: segfault at 48 ip 00007f4157688e25 sp 00007f413e9fe460 error 4 in libvdpau_r600.so.1.0.0[7f4157200000+b71000] likely on CPU 1 (core 1, socket 0) kernel: Code: 45 00 01 f0 83 2e 01 0f 84 c0 01 00 00 0f 1f 84 00 00 00 00 00 48 8b 83 d8 00 00 00 48 89 ab e8 00 00 00 66 0f ef c0 49 89 e4 <48> 8b 68 48 0f b7 45 44 0f b7 55 40 0f 29 04 24 48 89 ee c6 43 3f Kind regards, Peter -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1218424] New: go1.22 release tracking
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218424 Bug ID: 1218424 Summary: go1.22 release tracking 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: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.22 (expected February 2024) is a major release of Go. Minor releases of go1.22.x will be provided through February 2025. This issue tracks go1.22.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225497] New: bcc-tools's bashreadline fails to run due to missing dependency
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225497 Bug ID: 1225497 Summary: bcc-tools's bashreadline fails to run due to missing dependency 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: shung-hsi.yu(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Running bashreadline fails with the following stack trace > $ /usr/share/bcc/tools/bashreadline > Traceback (most recent call last): > File "/usr/share/bcc/tools/bashreadline", line 20, in <module> > from elftools.elf.elffile import ELFFile The line was added in v0.30.0 with commit 706ec4fe ("Fix bashreadline (#4903)") The solution is to add python3-pyelftools as runtime dependency. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217029] New: [Build 20231109] openQA test fails in networkd_dhcp
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1217029 Bug ID: 1217029 Summary: [Build 20231109] openQA test fails in networkd_dhcp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3714912/modules/netw orkd_dhcp/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation The test spawns two containers that are then supposed to interact. Calling networkctl against node1 seems to 'time out' since recently command 'systemd-run -tM node1 /bin/bash -c "networkctl"' timed out Please help investigating what is going on here openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-systemd-networkd@64bit fails in [networkd_dhcp](https://openqa.opensuse.org/tests/3714912/modules/networkd_d… ## Test suite description Maintainer: dheidler(a)suse.de Test for systemd-networkd. These tests run on a single testmachine and spawn systemd-nspawn containers. ## Reproducible Fails since (at least) Build [20231109](https://openqa.opensuse.org/tests/3713820) ## Expected result Last good: [20231108](https://openqa.opensuse.org/tests/3711613) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220574] New: [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now errors)
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220574 Bug ID: 1220574 Summary: [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now 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: --- Meta issue that will track all packages that fail with gcc14 package except for those that are tracked in bug#1220571 - i.e. those that cannot be worked around by turning new errors back to warnings. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1225213] New: no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 Bug ID: 1225213 Summary: no sound on speakers, headphones work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- after yesterdays upgrade sound does not play on speakers, but works on headphones. tried to change volum on all devices but no luck. Plasma indicator shows sound playing but nothing is hearable. polrus  ~  inxi -A Audio: Device-1: Intel Comet Lake PCH cAVS driver: sof-audio-pci-intel-cnl API: ALSA v: k6.9.1-1-default status: kernel-api Server-1: PipeWire v: 1.0.6 status: active polrus  ~  dmesg |grep snd_hda [ 6.260721] [ T773] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 6.579988] [ T1408] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat snd_soc_rt715 snd_soc_rt1308_sdw snd_soc_rt711 snd_hda_codec_hdmi regmap_sdw snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm(+) snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_avs snd_soc_hda_codec mac80211 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi libarc4 snd_soc_core snd_compress snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core intel_uncore_frequency spi_nor intel_uncore_frequency_common snd_hwdep hid_sensor_als iTCO_wdt iwlwifi intel_tcc_cooling mtd intel_pmc_bxt hid_sensor_trigger snd_pcm processor_thermal_device_pci_legacy iTCO_vendor_support dell_laptop hid_sensor_iio_common x86_pkg_temp_thermal ee1004 processor_thermal_device industrialio_triggered_buffer intel_powerclamp -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219663] New: Error running 'nvme list'
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219663 Bug ID: 1219663 Summary: Error running 'nvme list' Classification: openSUSE Product: openSUSE Leap Micro Version: 5.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: hare(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Running the command 'nvme list' on Leap Micro 5.5 results in: # nvme list nvme: error while loading shared libraries: libhugetlbfs.so: cannot enable executable stack as shared object requires: Permission denied Huh? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1224404] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224404 Bug ID: 1224404 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1219180 Target Milestone: --- Found By: openQA Blocker: --- +++ This bug was initially created as a clone of Bug #1219180 +++ Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. The original bug report has some more details, but the summary is that efifb or other builtin drivers don't work with virtio-gpu-pci. To get any display output at all, the virtio-gpu module is needed. From a dracut PoV, the crypt module should probably pull in drm if virtio-gpu is detected? ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1220403] New: VUL-0: CVE-2024-23837: libhtp: excessive processing time of HTTP headers can lead to denial of service
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220403 Bug ID: 1220403 Summary: VUL-0: CVE-2024-23837: libhtp: excessive processing time of HTTP headers can lead to denial of service Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/395171/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: otto.hollmann(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- LibHTP is a security-aware parser for the HTTP protocol. Crafted traffic can cause excessive processing time of HTTP headers, leading to denial of service. This issue is addressed in 0.5.46. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23837 https://www.cve.org/CVERecord?id=CVE-2024-23837 https://github.com/OISF/libhtp/commit/20ac301d801cdf01b3f021cca08a22a87f477… https://github.com/OISF/libhtp/security/advisories/GHSA-f9wf-rrjj-qx8m https://redmine.openinfosecfoundation.org/issues/6444 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223587] New: windows:mingw:win{32|64}: not present email address hib@hiberis.nl in bug tracker
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223587 Bug ID: 1223587 Summary: windows:mingw:win{32|64}: not present email address hib(a)hiberis.nl in bug tracker Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- When opening new bugs for the mingw32|64 project, the mentioned email address is entered in the CC field. Submitting the bug then fails with the error message that this email address does not exist. This email address should be removed from the ticket system. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1221715] New: GCC 14: liblogging package fails
by bugzilla_noreply＠suse.com 04 Jun '24

04 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221715 Bug ID: 1221715 Summary: GCC 14: liblogging package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: thomas.blume(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building liblogging with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: beepframe.c:170:1: error: return type defaults to ‘int’ [-Wimplicit-int] 170 | sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beeplisten.c: In function ‘sbLstnInit’: beeplisten.c:1055:28: error: implicit declaration of function ‘sbSock_InitUXDOMSOCK’ [-Wimplicit-function-declaration] 1055 | if((iRet = sbSock_InitUXDOMSOCK(&(pThis->pSockUXDOMSOCKListening), pActualSockName, /*SOCK_DGRAM*/ SOCK_STREAM)) != SR_RET_OK) | ^~~~~~~~~~~~~~~~~~~~ Builds with: Index: liblogging-1.0.6/rfc3195/src/beepframe.c =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/beepframe.c +++ liblogging-1.0.6/rfc3195/src/beepframe.c @@ -167,6 +167,7 @@ srRetVal sbFramActualRecvFramCommonHdr(s * The channel object is updated, e.g. with a * new seqno. */ +int sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) { unsigned iToRcv; Index: liblogging-1.0.6/rfc3195/src/sockets.h =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/sockets.h +++ liblogging-1.0.6/rfc3195/src/sockets.h @@ -340,4 +340,8 @@ srRetVal sbSockRecvFrom(sbSockObj *pThis # define SOCKET_ERROR -1 #endif +#if FEATURE_UNIX_DOMAIN_SOCKETS == 1 +srRetVal sbSock_InitUXDOMSOCK(sbSockObj **ppThis, char *pszSockName, int iSockType); +#endif + #endif See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225689] New: Error message received from tik with mount system call failed.
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225689 Bug ID: 1225689 Summary: Error message received from tik with mount system call failed. Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: tony.neely(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: [tik][20240531-02:01:04][LOG] [START] /usr/bin/tik [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:04][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [zenity][0][] --info --ok-label=Install Now --no-wrap --width=300 --height=300 --icon=distributor-logo-Aeon-symbolic --title= --text=<big>Welcome to openSUSE Aeon</big>\n\nPlease press <b>Install Now</b> to continue [/usr/lib/tik/modules/pre/10-welcome][20240531-02:01:24][LOG] [STOP] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/10-welcome [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:24][LOG] [START] /usr/lib/tik/modules/pre//usr/lib/tik/modules/pre/20-mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:32][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [zenity][0][nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V] --list --column=Disk --column=Size --width=1000 --height=340 --title=Select A Disk --text=Select the disk to install the operating system to. <b>Make sure any important documents and files have been backed up.</b>\n ata-Samsung_SSD_860_EVO_1TB_S3Z8NY0M767057P 931.5G nvme-Samsung_SSD_970_EVO_Plus_250GB_S4P3NF0M605653V 232.9G [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mkdir -p /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [pkexec][0] /usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] [probe_partitions] /dev/disk/by-id/nvme-eui.0025385691b29275-part2 found [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:43][LOG] Legacy Aeon Install FOUND [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/umount /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/rmdir /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][0] /usr/bin/mkdir /var/lib/tik/mig/mnt mount: /var/lib/tik/mig/mnt: mount system call failed: No such file or directory. dmesg(1) may have more information after failed mount system call. [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][LOG] [pkexec][32] /usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:48][ERROR] Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [zenity][0][] --error --text Command <tt>/usr/bin/mount -o compress=zstd:1,subvol=/@/home /dev/disk/by-id/nvme-eui.0025385691b29275-part2 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-02:01:54][LOG] [STOP][1] /usr/bin/tik Reproducible: Always Actual Results: System notified me of error and shut down. I have an existing Aeon install, with a separate drive (BTRFS formatted) for my /home. Easy enough to setup with old installer. Chose system drive (not /home drive) for the install. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1223405] New: Bluetooth disabled at each login since upgrade to Plasma 6
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223405 Bug ID: 1223405 Summary: Bluetooth disabled at each login since upgrade to Plasma 6 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: epp(a)mcom.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the upgrade to Plasma 6, Bluetooth becomes disabled at each login. Must manually re-enable it each time. Once enabled, it should remain enabled between sessions. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224215] New: Krunner randomly forces you to backspace-remove text to clear out text
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224215 Bug ID: 1224215 Summary: Krunner randomly forces you to backspace-remove text to clear out text Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: jlopez777+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Krunner randomly forces you to backspace-remove text to clear out text Submitted here too: https://bugs.kde.org/show_bug.cgi?id=485375 SUMMARY I have to manually hit backspace to remove text from krunner. expected behavior: it should just clear out text or have it highlighted to allow for "write over" so that the new text I enter wipes out old text. Hard to reproduce, not sure what triggers it because it doesn't happen all the time...but I think its when I highlight text. 1. Highlight some random text from web browser 2. Call krunner 3. Observe behavior 4. esc and call krunner again, and NOW it highlights all the text for overwrite....which should be intended behavior initially. DEMO of the problem: Hard to explain, so here is a vid: https://youtu.be/0WtkuhZGlEs -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216083] New: cockpit-ws: theme QA
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216083 Bug ID: 1216083 Summary: cockpit-ws: theme QA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Cockpit-bugs(a)suse.de, qa-bugs(a)suse.de Depends on: 1216082 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1216082 +++ We should add openQA test for basic theme and login -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216082] New: cockpit-ws: theme missing
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216082 Bug ID: 1216082 Summary: cockpit-ws: theme missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The theme seems to not be loaded correcly. It looks very dark, like the default theme. See MicroOS 5.1 for correct theme. TW, 5.5 need fixes. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220476] New: GCC 14: freeipmi package fails
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220476 Bug ID: 1220476 Summary: GCC 14: freeipmi package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kkaempf(a)suse.com, mjambor(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building freeipmi with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: sel/ipmi-sel-string-supermicro-x10dimm-common.c: In function ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’: sel/ipmi-sel-string-supermicro-x10dimm-common.c:87:14: error: implicit declaration of function ‘sel_string_output_supermicro_dimm_event_data2_event_data3’; did you mean ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’? [-Wimplicit-function-declaration] 87 | if ((ret = sel_string_output_supermicro_dimm_event_data2_event_data3 (ctx, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | sel_string_output_supermicro_x10dimm_event_data2_event_data3 ipmi-sensors-oem-intel.c: In function ‘ipmi_sensors_oem_intel_output_oem_record’: ipmi-sensors-oem-intel.c:98:18: error: implicit declaration of function ‘ipmi_sensors_oem_intel_s2600wp_output_oem_record’; did you mean ‘ipmi_sensors_oem_intel_s2600jf_output_oem_record’? [-Wimplicit-function-declaration] 98 | if ((ret = ipmi_sensors_oem_intel_s2600wp_output_oem_record (state_data, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ipmi_sensors_oem_intel_s2600jf_output_oem_record Builds with: Index: freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h +++ freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h @@ -38,5 +38,14 @@ int sel_string_output_supermicro_overhea unsigned int flags, unsigned int *wlen, struct ipmi_sel_system_event_record_data *system_event_record_data); +int sel_string_output_supermicro_dimm_event_data2_event_data3 (ipmi_sel_ctx_t ctx, + struct ipmi_sel_entry *sel_entry, + uint8_t sel_record_type, + char *buf, + unsigned int buflen, + unsigned int flags, + unsigned int *wlen, + struct ipmi_sel_system_event_record_data *system_event_record_data, + int *oem_rv); #endif /* IPMI_SEL_STRING_SUPERMICRO_COMMON_H */ Index: freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c +++ freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c @@ -34,6 +34,7 @@ #include "ipmi-sensors-oem-intel.h" #include "ipmi-sensors-oem-intel-s5500wb.h" #include "ipmi-sensors-oem-intel-s2600jf.h" +#include "ipmi-sensors-oem-intel-s2600wp.h" #include "ipmi-sensors-oem-intel-quanta-qssc-s4r.h" #include "ipmi-sensors-oem-intel-node-manager.h" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221340] New: qemu: fails to build with osc
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221340 Bug ID: 1221340 Summary: qemu: fails to build with osc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, dfaggioli(a)suse.com Target Milestone: --- Found By: Development Blocker: --- Steps to reproduce: osc co openSUSE:Factory/qemu && cd $_ osc build --noservice --clean standard Actual results: using SOURCE_DATE_EPOCH with value 1709510400 as build time error: Failed build dependencies: canokey-qemu-devel is needed by qemu-8.2.1-0.x86_64 libxdp-devel is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-protocol) >= 0.12.3 is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-server) >= 0.12.5 is needed by qemu-8.2.1-0.x86_64 xen-devel >= 4.2 is needed by qemu-8.2.1-0.x86_64 Powering off. [ 94.494179][ T3445] reboot: Power down This likely has to do with these macros %if 0%{with canokey} BuildRequires: canokey-qemu-devel %endif that are not properly parsed to provide the BuildRequires # rpm -q osc build osc-1.6.1-150500.403.1.noarch build-20240221-150500.444.1.noarch (both from openSUSE:Tools / 15.5) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225574] New: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225574 Bug ID: 1225574 Summary: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- apache2-mod_mono, by default, creates a socket `/tmp/mod_mono_server_global`, allowing unprivileged users to break the module by creating an identically named file in that location. However a) this behavior is documented b) it is mitigated by a systemd hardening in the apache2 package: > [Unit] > Description=The Apache Webserver > After=network.target nss-lookup.target time-sync.target remote-fs.target > Before=getty(a)tty1.service plymouth-quit.service xdm.service > PartOf=apache2.target > [Service] > Type=notify > PrivateTmp=true -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225522] New: sharing a folder in nautilus gives a usershare failed error
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225522 Bug ID: 1225522 Summary: sharing a folder in nautilus gives a usershare failed error Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: hotel-brot.0z(a)icloud.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: sharing a folder in nautilus gives a usershare failed error: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Reproducible: Always Steps to Reproduce: 1.create any folder for testing 2.right click on folder in nautilus -> Sharing Options -> Share this folder -> Create Share Actual Results: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Expected Results: successful sharing of a folder journalctl does not show more than the same error given above -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225690] New: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225690 Bug ID: 1225690 Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.mattiazzo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Stable channel has been updated to 125.0.6422.141/.142 for Windows, Mac and 125.0.6422.141 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 11 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. - CVE-2024-5493: Heap buffer overflow in WebRTC. - CVE-2024-5494: Use after free in Dawn. - CVE-2024-5495: Use after free in Dawn. - CVE-2024-5496: Use after free in Media Session. - CVE-2024-5497: Out of bounds memory access in Keyboard Inputs. - CVE-2024-5498: Use after free in Presentation API. - CVE-2024-5499: Out of bounds write in Streams API. As usual, our ongoing internal security work was responsible for a wide range of fixes: [343518382] Various fixes from internal audits, fuzzing and other initiatives Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. [0] https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-des… -- You are receiving this mail because: You are on the CC list for the bug.

1 5