October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 20 Oct '24

20 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed: [...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1231812] New: Installation of Packages Failed
by bugzilla_noreply＠suse.com 20 Oct '24

20 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231812 Bug ID: 1231812 Summary: Installation of Packages Failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: senexstyxnyx(a)protonmail.ch QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- <html>Dependency resolution failed: problem with the installed libavcodec60-32bit-6.1.1-11.1.x86_64 problem with the installed libavutil58-32bit-6.1.1-11.1.x86_64 problem with the installed libswresample4-32bit-6.1.1-11.1.x86_64</html> I was just trying to update my system -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231814] New: rtw89_8852ce 0000:02:00.0: firmware failed to ack for leaving ps mode
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231814 Bug ID: 1231814 Summary: rtw89_8852ce 0000:02:00.0: firmware failed to ack for leaving ps mode 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [14391.684532] [ T869] rtw89_8852ce 0000:02:00.0: FW status = 0x2f001100 [14391.684558] [ T869] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [14391.684564] [ T869] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [14391.684569] [ T869] rtw89_8852ce 0000:02:00.0: FW MISC = 0x0 [14391.684574] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1000 [14391.684579] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0x1000000 [14391.684588] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011bf14 [14391.684617] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a030 [14391.684646] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a044 [14391.684662] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a038 [14391.684690] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a026 [14391.684710] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a03e [14391.684739] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f72 [14391.684757] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a038 [14391.684777] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a030 [14391.684806] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f86 [14391.684826] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f7c [14391.684855] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9e [14391.684877] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f7a [14391.684906] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f8c [14391.684926] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f70 [14391.684940] [ T869] rtw89_8852ce 0000:02:00.0: ---> err=0x1000 [14391.684954] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO =0x01000000 [14391.684959] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO =0x01000000 [14391.684964] [ T869] rtw89_8852ce 0000:02:00.0: DBG Counter 1 (R_AX_DRV_FW_HSK_4)=0x00060006 [14391.684970] [ T869] rtw89_8852ce 0000:02:00.0: DBG Counter 2 (R_AX_DRV_FW_HSK_5)=0x00820082 [14391.684977] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_DMAC_ERR_ISR=0x00000040 [14391.685014] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_DMAC_ERR_IMR=0x00000000 [14391.685019] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERR_FLAG_CFG=0x00000000 [14391.685024] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERR_FLAG_CFG=0x80190000 [14391.685029] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERRFLAG_MSG=0xc0801741 [14391.685033] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERRFLAG_MSG=0x00000000 [14391.685038] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_DBGERR_LOCKEN=0x00000000 [14391.685043] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_DBGERR_STS=0x00000000 [14391.685047] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERR_IMR=0xffffffff [14391.685052] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WDE_ERR_ISR=0x00000000 [14391.685056] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERR_IMR=0xffffffff [14391.685060] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PLE_ERR_FLAG_ISR=0x02000080 [14391.685065] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WD_CPUQ_OP_0=0x00000000 [14391.685069] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WD_CPUQ_OP_1=0x00000000 [14391.685073] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WD_CPUQ_OP_2=0x00000000 [14391.685077] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PL_CPUQ_OP_0=0x00000000 [14391.685082] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PL_CPUQ_OP_1=0x00000000 [14391.685086] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PL_CPUQ_OP_2=0x00000000 [14391.685090] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_WD_CPUQ_OP_STATUS=0x00000000 [14391.685094] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_PL_CPUQ_OP_STATUS=0x00000000 [14391.685099] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_RX_CTRL0=0x0a050000 [14391.685103] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_RX_CTRL1=0x00000004 [14391.685108] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_RX_CTRL2=0x00004201 [14391.685117] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_ERR_ISR [0]=0x00000000 [14391.685124] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_FUNC_EN [0]=0xf000803f [14391.685129] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_CK_EN [0]=0xffffffff [14391.685135] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_CMAC_ERR_IMR [0]=0x00000000 [14391.685140] [ T869] rtw89_8852ce 0000:02:00.0: [CMAC] : CMAC1 not enabled [14391.685145] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_DBG_ERR_FLAG=0x00000000 [14391.685149] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_LBC_WATCHDOG=0x0030d800 [14391.685151] [ T869] rtw89_8852ce 0000:02:00.0: <--- [14391.685153] [ T869] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1000 [14391.733928] [ T84877] rtw89_8852ce 0000:02:00.0: firmware failed to ack for leaving ps mode [14391.784574] [ T84877] rtw89_8852ce 0000:02:00.0: rtw89: failed to leave lps state [14391.787284] [ T869] rtw89_8852ce 0000:02:00.0: FW status = 0x2f001100 [14391.787386] [ T869] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [14391.787395] [ T869] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [14391.787401] [ T869] rtw89_8852ce 0000:02:00.0: FW MISC = 0x0 [14391.787408] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1001 [14391.787414] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0x1000000 [14391.787425] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f98 [14391.787533] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f72 [14391.787634] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f98 [14391.787744] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a026 [14391.787854] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a012 [14391.787952] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f9c [14391.788060] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a016 [14391.788169] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a042 [14391.788267] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a030 [14391.788404] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a034 [14391.788504] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f96 [14391.788603] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f96 [14391.788710] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20119f98 [14391.788817] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a03a [14391.788915] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2011a012 [14391.788931] [ T869] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1001 [14391.789275] [ T869] rtw89_8852ce 0000:02:00.0: FW status = 0x2f008100 [14391.789382] [ T869] rtw89_8852ce 0000:02:00.0: FW BADADDR = 0x0 [14391.789390] [ T869] rtw89_8852ce 0000:02:00.0: FW EPC/RA = 0x0 [14391.789396] [ T869] rtw89_8852ce 0000:02:00.0: FW MISC = 0x20117bd4 [14391.789402] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_HALT_C2H = 0x1002 [14391.789407] [ T869] rtw89_8852ce 0000:02:00.0: R_AX_SER_DBG_INFO = 0xf1000000 [14391.789417] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013fbbc [14391.789529] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013ae72 [14391.789636] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2000c1d2 [14391.789734] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c944 [14391.789841] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2002e94e [14391.789948] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c94e [14391.790044] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2000c1d2 [14391.790153] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2002d950 [14391.790260] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013ae74 [14391.790358] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2003c9aa [14391.790465] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013ae7e [14391.790572] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2013b2ec [14391.790649] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x20025bfe [14391.790759] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2000c1d2 [14391.790857] [ T869] rtw89_8852ce 0000:02:00.0: [ERR]fw PC = 0x2000c1d2 [14391.790871] [ T869] rtw89_8852ce 0000:02:00.0: SER catches error: 0x1002 [14391.943973] [ T84877] rtw89_8852ce 0000:02:00.0: c2h class 1 func 3 not support -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1231813] New: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231813 Bug ID: 1231813 Summary: [riscv64][Unmatched][regression] Hard lockup on reboot/poweroff with 6.11 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddavis(a)suse.com, jeffm(a)suse.com, schwab(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Reboot or poweroff on HiFive Unmatched board is no longer working at 20241016/17 (was working with 20240828; its 6.10.5 kernel with 20241017 does not help) and runs into a hard CPU lockup kernel panic: [ 56.329837][ T1379] sifive-serial 10010000.serial: BREAK detection not supported [ 57.664396][ T1] reboot: Power down [ 72.030230][ C3] watchdog: Watchdog detected hard LOCKUP on cpu 0 [ 96.026864][ C2] watchdog: Watchdog detected hard LOCKUP on cpu 3 [ 96.026873][ C2] Modules linked in: af_packet rfkill nf_tables libcrc32c snd_hda_codec_hdmi snd_hda_intel mscc snd_intel_dspcfg macsec snd_hda_codec nls_iso8859_1 nls_cp437 snd_hda_core vfat macb fat snd_hwdep phylink snd_pcm ofpart of_mdio snd_timer fixed_phy fwnode_mdio libphy snd spi_nor ptp at24 soundcore da9063_onkey pps_core mtd uio_pdrv_genirq uio fuse dm_mod nvme_fabrics nvme_keyring loop efi_pstore configfs nfnetlink dmi_sysfs ip_tables x_tables ext4 mbcache jbd2 xe hid_apple hid_generic usbhid apple_mfi_fastcharge xhci_pci mmc_block xhci_pci_renesas xhci_hcd drm_ttm_helper ttm i2c_algo_bit gpu_sched drm_buddy video drm_suballoc_helper drm_gpuvm mmc_spi crc_itu_t crc7 drm_exec of_mmc_spi usbcore drm_display_helper mmc_core rtc_da9063 da9063_regulator nvme cec lm90 da9063 mfd_core regmap_i2c rc_core nvme_core usb_common nvme_auth i2c_ocores pwm_sifive spi_sifive efivarfs [ 96.027165][ C2] Kernel panic - not syncing: Hard LOCKUP [ 96.027178][ C2] CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Tainted: G U 6.11.3-1-default #1 openSUSE Tumbleweed 1400000003000000474e55005c3864d57907faa4 [ 96.027195][ C2] Tainted: [U]=USER [ 96.027198][ C2] Hardware name: sifive SiFive HiFive Unmatched A00/SiFive HiFive Unmatched A00, BIOS 2024.10 10/01/2024 [ 96.027204][ C2] Call Trace: [ 96.027211][ C2] [<ffffffff80006b4a>] dump_backtrace+0x1c/0x24 [ 96.027236][ C2] [<ffffffff80a00178>] show_stack+0x2c/0x38 [ 96.027251][ C2] [<ffffffff80a0cd7c>] dump_stack_lvl+0x50/0x72 [ 96.027270][ C2] [<ffffffff80a0cdb2>] dump_stack+0x14/0x1c [ 96.027279][ C2] [<ffffffff80a00410>] panic+0x106/0x312 [ 96.027288][ C2] [<ffffffff80022c0a>] add_taint+0x0/0x8c [ 96.027302][ C2] [<ffffffff80123204>] watchdog_hardlockup_check+0x170/0x1b4 [ 96.027322][ C2] [<ffffffff80123ca8>] watchdog_buddy_check_hardlockup+0x4c/0x5c [ 96.027334][ C2] [<ffffffff80122e98>] watchdog_timer_fn+0x70/0x238 [ 96.027344][ C2] [<ffffffff800d0540>] __hrtimer_run_queues+0xfe/0x240 [ 96.027364][ C2] [<ffffffff800d133a>] hrtimer_interrupt+0xca/0x1d6 [ 96.027374][ C2] [<ffffffff807b5e58>] riscv_timer_interrupt+0x3a/0x52 [ 96.027387][ C2] [<ffffffff800a1e0a>] handle_percpu_devid_irq+0x8a/0x1c0 [ 96.027403][ C2] [<ffffffff8009c6b0>] generic_handle_domain_irq+0x1c/0x2a [ 96.027423][ C2] [<ffffffff8055d908>] riscv_intc_irq+0x26/0x60 [ 96.027441][ C2] [<ffffffff80a0ce20>] handle_riscv_irq+0x4c/0x76 [ 96.027451][ C2] [<ffffffff80a1b106>] call_on_irq_stack+0x32/0x40 [ 96.788253][ C2] SMP: failed to stop secondary CPUs 0,2-3 [ 96.788264][ C2] Kernel Offset: 0x0 from 0xffffffff80000000 After some minutes it then reboots (also for poweroff). I've manually updated the two U-Boot partitions to latest Factory 2024.10, to no improvement. The taint is from xe.force_probe (bug #1231756); happens without as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1196835] [riscv64][Unmatched] CPU#0 stuck forever while trying to reboot the board.
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1196835 Andreas Färber <afaerber(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1231813 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217774] New: qt6-webengine qtpdf.index reproducible builds
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217774 Bug ID: 1217774 Summary: qt6-webengine qtpdf.index reproducible builds 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 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our qt6-webengine / qt6-webengine-docs-html subpackage varied between builds in /usr/share/doc/qt6/qtpdf/qtpdf.index See diff at https://rb.zq1.de/compare.factory-20230830/diffs/qt6-webengine-compare.out You probably need to build with osc build -M docs -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1231811] New: Dependency resolution failed rstudio-2024.09.0+375-1.x86_64
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231811 Bug ID: 1231811 Summary: Dependency resolution failed rstudio-2024.09.0+375-1.x86_64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: yoshiki3x(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878106 --> https://bugzilla.suse.com/attachment.cgi?id=878106&action=edit Picture with error <html>Dependency resolution failed: problem with the installed rstudio-2024.09.0+375-1.x86_64</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230118] New: [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230118 Bug ID: 1230118 Summary: [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: cathy.hu(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just pasting the email to factory as reference: RFC: SELinux as default MAC system on new Tumbleweed installations SELinux is being adopted more and more as the main Mandatory Access Control (MAC) system in openSUSE distributions and SUSE products. The SUSE SELinux working group would like to announce the plan to switch new Tumbleweed installations to SELinux as default MAC system *by the end of this year*. Currently, new Tumbleweed installations select AppArmor in the installer as default MAC system. After this change, new Tumbleweed installations will select SELinux in enforcing mode as default MAC system. Users will still be able to select AppArmor as MAC system in the installer. Existing installations will *not* be affected. If you would like to migrate your existing system from AppArmor to SELinux, we have a guide on what to consider and how to do that here [0]. *What does it mean for users?* Our SELinux policy contains many policy modules, which confine most well-known services. Switching to SELinux means more services are confined by default, which means enhanced security. On the other hand, more confinement also means that in the early phase of the adoption there could be more bugs caused by SELinux denying legitimate accesses. We perform both manual and automated tests via openQA, to ensure that our policy works seamlessly. We also rely on you, the community, to create bugreports so that we can adapt the policy to any scenarios that we did not foresee. We have a page on how to report bugs here: https://en.opensuse.org/openSUSE:Bugreport_SELinux To learn more about SELinux, we also have a Portal in the openSUSE wiki: https://en.opensuse.org/Portal:SELinux Please feel free to reply to this email in case you have any questions or concerns. We plan to do the change earliest in September 2024, and latest by the end of the year. Separate announcements will follow just before and after the change. TL;DR: - The Tumbleweed installer will select SELinux in enforcing mode as default on new installations - When: by the end of 2024, earliest in September, we will do separate announcements before and after - AppArmor can still be selected in the installer as an alternative - Existing installations will *not* change - Leap 15.x is not affected in any way [0] https://en.opensuse.org/Portal:SELinux/Setup#Setup_SELinux_on_existing_tumb… -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1229019] KVM:Starting KVM error "ensure all devices within the iommu_group are bound to their vfio bus driver" after kernel update
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229019 https://bugzilla.suse.com/show_bug.cgi?id=1229019#c63 --- Comment #63 from Jim Niko <jniko19aban(a)gmail.com> --- (In reply to Jiri Slaby from comment #60) > We need to find proper fix, not a work around (a revert). Hi Jiri, I think Vassilis solution might be a way for resolving this issue and not revert it. When need a test for a new solution about this issue, please let me know because I have the proper hardware available. Best regards, Jim -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1081430] TW 20180214 NetworkManager segv Segmentation fault. #0 0x0000555cae32f7a3 in nm_connection_clear_secrets (connection=connection@entry=0x6c00000001) at libnm-core/nm-connection.c:1662
by bugzilla_noreply＠suse.com 19 Oct '24

19 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1081430 tom kosvic <tcklinux(a)ix.netcom.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tcklinux(a)ix.netcom.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0