June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225544] New: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225544 Bug ID: 1225544 Summary: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop 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: sm(a)eisoft.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I start a new Aeon installation with my laptop unplugged and running on battery power, the installer correctly tells me that I need to be plugged into power before proceeding. However, even after plugging my laptop into a power source the aforementioned message cannot be dismissed. Software: openSUSE Aeon RC2 Hardware: Lenovo Thinkpad X1 Carbon 6th Intel Core i7 16GB Memory 1.0TB HD Steps to Reproduce: Start a fresh installation of Aeon via bootable USB while laptop is not connected to power. A message will appear saying that the installation cannot continue while on battery power. Plug laptop into power. Message will not be dismissed and clicking "ok" will result in message reappearing over and over again. Workaround: Make sure laptop is plugged in before starting an Aeon installation. ¯\_(ツ)_/¯ -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225709] New: tik mounts the wrong path onto usb sticks installations
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225709 Bug ID: 1225709 Summary: tik mounts the wrong path onto usb sticks installations 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: 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: tik tries to mount ‘/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0’ but the correct path to mount would be ‘/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0\:0’ it seems as if tik just stops indicating the path at \ Reproducible: Always Steps to Reproduce: try to install aeon onto a usb stick Actual Results: mount: /var/lib/tik/mig/mnt: special device /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 does not exist. dmesg(1) may have more information after failed mount system call. [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:17][LOG] [pkexec][32] /usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:17][ERROR] Command <tt>/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:20][LOG] [zenity][0][] --error --text Command <tt>/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:20][LOG] [STOP][1] /usr/bin/tik Expected Results: Successful mounting -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1226418] yast2-audit-laf rules are not preserved across reboots
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226418 https://bugzilla.suse.com/show_bug.cgi?id=1226418#c3 --- Comment #3 from Henryk Hecht <nvbugs(a)hhecht.e4ward.com> --- If the code is that old, it dates from audit-1.x, which is before augenrules and the inclusion of 10-no-audit.rules -> audit.rules as the baseline configuration. So its behavior makes sense with contemporary versions of audit. I am unsurprised that the module is unpopular: there are probably very few people actively and directly using audit in the first place, and the yast module isn't required/recommended by anything, so it's hard to know that it's there. But the rule editing probably hasn't worked properly since at least 2015, so if this is the first bug report of that, it seems really no one at all is using it, and dropping it may be reasonable. If not, the other three tabs still seem to work, so maybe it could be salvaged by either making it edit /etc/audit/rules.d/audit.rules instead of /etc/audit/audit.rules, or else just scrapping the rules editing portion. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226453] New: Kernel 6.9.4 not being booted after update because of syntax error in grub script
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226453 Bug ID: 1226453 Summary: Kernel 6.9.4 not being booted after update because of syntax error in grub script 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: rx2l5t+4zshakz4lenfc(a)sharklasers.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When upgrading the kernel, after it installs and dracut finishes, the grub script outputs: + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt /etc/grub.d/10_linux: 154: Syntax error: "(" unexpected (expecting "}") CA enrolled. Skip /etc/uefi/certs/1F673297.crt warning: %post(kernel-default-6.9.4-1.1.x86_64) scriptlet failed, exit status 2 Line 154: files=($(for bls in ${blsdir}/*.conf; do -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219494 https://bugzilla.suse.com/show_bug.cgi?id=1219494#c60 --- Comment #60 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-RU-2024:0165-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1219494,1223909 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): vlc-3.0.21-bp155.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226445] Leap 15.6: Rusticl OpenCL driver from package Mesa-libRusticlOpenCL from repo X11:XOrg - version 24.0.3 in repository, expected v. 24.1.1
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226445 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226445] Leap 15.6: Rusticl OpenCL driver from package Mesa-libRusticlOpenCL from repo X11:XOrg - version 24.0.3 in repository, expected v. 24.1.1
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226445 https://bugzilla.suse.com/show_bug.cgi?id=1226445#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- As usual Mesa was still building against Leap 15.5/15.6, but -drivers not. I've now wiped all Mesa RPMs from the 15.5/`5.6 repositories. You need to go back to 15.6 Mesa/Mesa-drivers packages. Sorry. I should really give up on trying to get packages in X11:XOrg building against Leap. It's just not doable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226450] New: disable compinit
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226450 Bug ID: 1226450 Summary: disable compinit Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: spam.catcher(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Ubuntu offers in # /etc/zsh/zshrc (lines 106-108) # If you don't want compinit called here, place the line # skip_global_compinit=1 # in your $ZDOTDIR/.zshenv whereas Opensuse # /etc/zshrc (lines 66-71) # The default way is the usage of the zsh built-in completer # Comment the two below lines out, if you are on a slow machine, and # comment the above compctl lines in. autoload -U compinit compinit However, not all users are admins of their (Open)Suse installation and can edit system files which are overriden by packages updates anyway. Therefore, how about allowing the user to disable the compinit as well? (One benefit being a many times faster startup time on some systems). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226442] New: hangs and delays after upgrade from Leap 15.5 to 15.6
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226442 Bug ID: 1226442 Summary: hangs and delays after upgrade from Leap 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: batpul(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday I upgraded from Leap 15.5 to 15.6 using zypper dup as explained on a opensuse site. The 15.5 had been very stable. Since the upgrade the X11 session hung twice. The first was yesterday when a youtube video was playing in Chrome and the sound just continued forever as if nothing happened while the screen was totally frozen. Ctrl+Backspace and Ctrl+Alt+F1 didn't work and a hard reset was the only way out. Today the screen again froze totally, except for the mouse. The mouse pointer was movable over the screen and this time Ctrl+Backspace did work and gave me the GDM login screen. Couldn't find anything in dmesg or in Xorg.0.log. Needless to say, this is very disturbing to me. This is a previous Xorg bug from me for details: https://bugzilla.opensuse.org/show_bug.cgi?id=1214448. There is now another problem. I run icewm as a window manager and GNOME applications like gnome-calculator and evince take 40 seconds to appear. strace shows they block on a futex a couple of times, but unclear what they are waiting for. This is very annoying too. If I want to read PDFs it now takes ages. There is also this in my environment which I don't know how to influence as there seems no documentation about, hence I can't figure out how to tweak it: GTK_IM_MODULE=cedilla GTK_MODULES=canberra-gtk-module:canberra-gtk-module Can I unset this, or are these needed for the GNOME applications, or what can I do with them? Thanks for your time and attention. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219545] New: sound hangs after zypper update; unable to play any sound
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219545 Bug ID: 1219545 Summary: sound hangs after zypper update; unable to play any sound 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: Sound Assignee: tiwai(a)suse.com Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Sound used to work fine until yesterday Feb 3 zypper update. Today after boot the sound configuration was non-existent. After yast2 sound Quick configuration the test sound produces no output. Set all volume controls to max. No improvement. Reboot doesn't help. Repeatedly deleting and recreating the sound configuration with yast2 in various ways doesn't help. When an application like aplay, audacious tries to play a sound it hangs. yast2 sound configuration info. 100 Series/C230 Series Chipset Family HD Audio Controller Configured as sound card number 0 Driver snd-hda-intel PulseAudio is enabled. aplay just hangs until it timeouts: $ ll /usr/share/sounds/purple/alert.wav -rw-r--r-- 1 root root 23314 May 9 2022 /usr/share/sounds/purple/alert.wav $ aplay /usr/share/sounds/purple/alert.wav Playing WAVE '/usr/share/sounds/purple/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono ALSA lib pcm_pulse.c:758:(pulse_prepare) PulseAudio: Unable to create stream: Timeout aplay: set_params:1416: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 16 CHANNELS: 1 RATE: 22050 PERIOD_TIME: 125000 PERIOD_SIZE: (2756 2757) PERIOD_BYTES: (5512 5513) PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 11025 BUFFER_BYTES: 22050 TICK_TIME: [0 0] -- You are receiving this mail because: You are on the CC list for the bug.

1 2