May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 967560] Tumbeweed snapshot 2016.02.12 install failure
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=967560 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dutch.glory@yahoo | |.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222978] [SELinux] gnome-control-center (users) unable to set AutoLogin
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222978 https://bugzilla.suse.com/show_bug.cgi?id=1222978#c6 --- Comment #6 from Filippo Bonazzi <filippo.bonazzi(a)suse.com> --- I think so. If you can build a GDM rpm with this change, we can test it and see what we need to change for SELinux. -- 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 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224212 https://bugzilla.suse.com/show_bug.cgi?id=1224212#c2 --- Comment #2 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Thank you Fabian! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222978] [SELinux] gnome-control-center (users) unable to set AutoLogin
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222978 https://bugzilla.suse.com/show_bug.cgi?id=1222978#c5 xiaoguang wang <xiaoguang.wang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(xiaoguang.wang@su | |se.com) | --- Comment #5 from xiaoguang wang <xiaoguang.wang(a)suse.com> --- (In reply to Filippo Bonazzi from comment #4) > Hi @xiaoguang.wang, instead of writing the temp file to > /etc/sysconfig/displaymanager.new.<somenumber>, could you write it to > <some_private_temp_folder>/displaymanager.new? Writing the temp file to /tmp/gdm.xxxxxx/displaymanager.new, xxxxxx is the random number. Does it work for SELinux context? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c14 --- Comment #14 from llyyr <llyyr.public(a)gmail.com> --- Gave 6.10-rc1 a shot, got a freeze within minutes. The patch still workarounds the issue though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225297] New: yast2 systemd bootloader error
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225297 Bug ID: 1225297 Summary: yast2 systemd bootloader error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: xjoelx(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have two drives in my system, NVME with Tumbleweed and an SSD with Windows. Grub2 is having errors on its own with this setup but I wanted to try systemd boot. I used yast2 to swap over, error occured. Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/share/YaST2/lib/bootloader/systemdboot.rb:204:in `initialize' Details: No such file or directory @ rb_sysopen - /etc/kernel/cmdline" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225296] Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225296 https://bugzilla.suse.com/show_bug.cgi?id=1225296#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.schmidt@io-warnemuen | |de.de Status|NEW |IN_PROGRESS Flags| |needinfo?(martin.schmidt@io | |-warnemuende.de) --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. This looks like a regression in nouveau kernel driver in kernel 6.4 of Leap 15.6. Unfortunately we can't support nouveau driver. I suggest to install proprietary driver instead. If you already have a modern card (Turing+ from 2018+), you could even install the new open source kernel driver from NVIDIA. Output of hwinfo --gfxcard xrandr -q would be useful. And /var/log/Xorg.*.log or ~/.local/share/xorg/Xorg.*.log. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224459] WARNING at apply_retpolines when using NVIDIA proprietary driver - 470 series
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224459 https://bugzilla.suse.com/show_bug.cgi?id=1224459#c3 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|sndirsch(a)suse.com |qa-bugs(a)suse.de Component|X11 3rd Party Driver |Kernel --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So this is a regression caused by updating to kernel 6.9.0+. Mabye our kernel guys have a clue about this. (In reply to Ionut Nechita from comment #2) > Is not related to boo#1212841, it would be a problem related to the > proprietary driver. > After the new video driver from NVIDIA will be integrated, this ticket > should be taken as a reference for the internal tests in openQA. I find this comment confusing and not helpful at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(llyyr.public@gmai | |l.com) | --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to llyyr from comment #12) > (In reply to Takashi Iwai from comment #11) > > OK, then please update the upstream bugtracker info accordingly. It's > > useful to know that the very latest code still suffers from the same problem. > > > 6.10-rc1 should be tagged later today, I'll give that a spin then update > upstream. Might also be worth trying out the > https://gitlab.freedesktop.org/agd5f/linux/-/tree/amd-staging-drm-next > branch? Sure, worth to try out. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 https://bugzilla.suse.com/show_bug.cgi?id=1224457#c41 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(andrwlms(a)gmail.co | |m) | --- Comment #41 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. Now the parameter is passed properly, and the driver tries forcibly probing a codec at each given slot, but all failed. It means that the codec is disabled by some reason; either a full power-off that doesn't react to the normal codec probe procedure, or disabled in BIOS somehow. An abnormal situation, in anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 0