April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 foo4bar.dev <foo4bar(a)foo4bar.dev> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |foo4bar(a)foo4bar.dev -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222188] lazarus crashes, when debugging with gdb is enabled
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222188 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|matz(a)suse.com |tdevries(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221183] Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 https://bugzilla.suse.com/show_bug.cgi?id=1221183#c3 --- Comment #3 from Richard Biener <rguenther(a)suse.com> --- The change for llvm15 seems to be just adding to clang_binfiles? The alternatives stuff there is obfuscated by macros. IMO the even older llvm might be better dropped on update? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c25 --- Comment #25 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Togan Muftuoglu from comment #23) > (In reply to Stefan Dirsch from comment #19) > > To confirm that radeonsi DRI modules is still loaded you could run. strace > > needs to be installed though. > > > > strace -f -e trace=file glxinfo -B 2>&1 | grep radeonsi_dri > > Here is the output > > openat(AT_FDCWD, "/usr/lib64/dri/tls/radeonsi_dri.so", O_RDONLY|O_CLOEXEC) = > -1 ENOENT (No such file or directory) > openat(AT_FDCWD, "/usr/lib64/dri/radeonsi_dri.so", O_RDONLY|O_CLOEXEC) = 5 Thanks! This confirms my assumption. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c24 --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- If it's a kernel regression, please clarify which kernel still worked and which one started showing the problem. You can find some older packages in TW history repo http://download.opensuse.org/history/ and install the older kernel packages with zypper install --oldpackage option. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221183] Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 https://bugzilla.suse.com/show_bug.cgi?id=1221183#c2 --- Comment #2 from Richard Biener <rguenther(a)suse.com> --- That's then required in all clang7, clang11, clang13 and clang15? In the SP2 codestream we also seem to have llvm9 and I can't see llvm13 so that's possibly only via the OBS sle-backports repository? I'll note I had issues with the Factory python3-clang conflicts/provides switching from %python3_sitearch to something else so I reverted that (but only for llvm17). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c21 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com --- Comment #21 from Stefan Dirsch <sndirsch(a)suse.com> --- Adding our kernel guys. @Patrik @Thomas @Takashi Which information is needed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c20 --- Comment #20 from Stefan Dirsch <sndirsch(a)suse.com> --- Could anyone try to boot with an older kernel to see if the regression is in the kernel? Unfortunately I don't know which kernel this would be. :-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c19 --- Comment #19 from Stefan Dirsch <sndirsch(a)suse.com> --- To confirm that radeonsi DRI modules is still loaded you could run. strace needs to be installed though. strace -f -e trace=file glxinfo -B 2>&1 | grep radeonsi_dri -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c18 --- Comment #18 from Stefan Dirsch <sndirsch(a)suse.com> --- @Togan You're using radeon.si_support=0 amdgpu.si_support=1 right? I believe with that radeon kernel module is still being loaded but doesn't initialize anything. So just amdgpu is active in that case. Usage of radeonsi DRI driver for 2D acceleration in Xserver is hardcoded. So this stays. radeonsi also stays for Mesa, because that's the radeon driver for current AMD Radeon cards and r300 and r600 is only for older cards. So could be that latest radeonsi Mesa driver triggers a bug in latest radeon kernel module. -- You are receiving this mail because: You are on the CC list for the bug.

1 0