May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225217] New: OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 Bug ID: 1225217 Summary: OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: charafweb(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My specs: CPU i7 6700HQ, Nvidia Geforce 960M, 4k Screen, 16GB RAM, 512GB SSD, and 2TB HDD (ASUS Laptop N552V). OpenSUSE TW won’t boot without the “dis_ucode_ldr” kernel boot parameter. I removed the “quiet” boot kernel parameter to get error output, but unfortunately, nothing shows up; the boot process stops very early. Even on a fresh install with default open-source drivers, I’m facing the same issue. So, it doesn’t seem to be related to the Nvidia drivers. In fact, openSUSE boots without any issues the first time because the Intel microcode isn’t installed. But once it’s installed, the boot process hangs. I’ve tried several rolling distros that use version 6 kernels, they all present the same problem. Only kernel 6.1.x seems to work with Intel-ucode (tested in Manjaro). OpenSUSE Leap (kernel v. 5.x) works fine even when installing ucode. So, I thought the issue might be with the ucode for TW. I tried copying the microcode file (06-5e-03) from Leap and replacing the one in TW, following successfully all the necessary steps to install it manually, but the boot process continues to hang with no output. Microcode code for i7 6700HQ is not updated anymore, the latest version is microcode-20220510. It’s possible that something broke with kernel versions above 6.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220043] amdgpu DRM/radeonsi Mesa: X dies when using Prism Launcher, sometimes disabling user input entirely.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220043 https://bugzilla.suse.com/show_bug.cgi?id=1220043#c4 --- Comment #4 from roke beedell <rokejulianlockhart+1674683091(a)outlook.com> --- (In reply to Stefan Dirsch from comment #3) > Could this be retested with latest TW please? I'm using https://download.fedoraproject.org/pub/fedora/linux/releases/40/Spins/x86_6… currently, so I can't - I don't have the space for second OS. Unless someone else who was able to reproduce this can do so, it'll have to wait until I next use OSTW on this HW configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217299] zypp:plugins/zypper-changelog-plugin: Bug repodata is now using zstd compression
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217299 https://bugzilla.suse.com/show_bug.cgi?id=1217299#c2 Zoltan Balogh <zbalogh(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Zoltan Balogh <zbalogh(a)suse.com> --- Sorry Ian for the extremely late response. I have totally missed both this bug and the patch. Thank you for reporting this problem. I am integrating your patch to the upstream project first and then I request a submission to the Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224212] JeOS firstboot select America/New York as default timezone
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224212 https://bugzilla.suse.com/show_bug.cgi?id=1224212#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Previously it was UTC because of a bug: The previous data set has US/Eastern as default TZ for en_US, but that's only an alias which is not part of the timezone dialog options. So it used the first option (UTC) as default. As using UTC makes sense in this case I made that behaviour explicit: https://build.opensuse.org/request/show/1176741 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225213] no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 https://bugzilla.suse.com/show_bug.cgi?id=1225213#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Alfredo Cubitos from comment #8) > (In reply to Takashi Iwai from comment #7) > > (In reply to Alfredo Cubitos from comment #6) > > > Comment on attachment 875068 [details] > > > alsainfo > > > > > > same issue here. > > > Headset works, bluetooth works, speakers not > > > > This is still with 6.9.1 kernel. Can you test with the previous 6.8.x > > kernel? > > it doesn't work either :-( > same issue with kernel 6.8.9-1, headset works, speaker not. Could you give alsa-info.sh output again from there, too? Just to be sure. > But it still worked a few days before. Any idea where to look? Check your zypper history log. Usually it's either the update of kernel, firmware or sound backend such as pipewire / wireplumber. Also, please take alsa-info.sh output at both testing the speaker output and the headphone output for comparison. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224462] New: RC2 Tik installer / first boot doesn't prompt for hostname
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224462 Bug ID: 1224462 Summary: RC2 Tik installer / first boot doesn't prompt for hostname Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: solutionroute(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Build Identifier: Aeon is a turnkey solution and a hostname - blank if expected to be set via a corp or home DHCP, manually set if not - should be part of the install (preferable) or first boot. Reproducible: Always Steps to Reproduce: 1.Install Actual Results: No hostname is gathered during the install or first boot and therefore not set. Expected Results: Provide opportunity for user to enter a hostname and set /etc/hostname, optionally leaving blank for DHCP situations. It's a small thing that most with-it users will know how to address, but would make the system more finished at first boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225213] no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 https://bugzilla.suse.com/show_bug.cgi?id=1225213#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Alfredo Cubitos from comment #6) > Comment on attachment 875068 [details] > alsainfo > > same issue here. > Headset works, bluetooth works, speakers not This is still with 6.9.1 kernel. Can you test with the previous 6.8.x kernel? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225213] no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 https://bugzilla.suse.com/show_bug.cgi?id=1225213#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- There is no obvious error through a quick glance. Could you try to boot with the previous 6.8.x kernel, and verify whether the problem persists? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225213] no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 https://bugzilla.suse.com/show_bug.cgi?id=1225213#c3 --- Comment #3 from Sebastian Turzański <dpbasti(a)wp.pl> --- Created attachment 875069 --> https://bugzilla.suse.com/attachment.cgi?id=875069&action=edit alsa-info -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202796] Zypper can't stop PackageKit
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1202796 https://bugzilla.suse.com/show_bug.cgi?id=1202796#c18 --- Comment #18 from ell1e <el(a)horse64.org> --- For what it's worth I have slow internet, and a repository refresh takes multiple minutes as a minimum. So if that for example isn't canceled, and packagekitd maybe even does that often (which in my opinion maybe it shouldn't but other comments suggested it currently does) that would explain why it never quits. However, KDE Discover also seems to aggressively restart packagekitd from how it looks like to me, that seems like part of the problem. My apologies if I observed any of these things incorrectly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0