March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

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

1 0

[Bug 1209499] New: System is freezing with current openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209499 Bug ID: 1209499 Summary: System is freezing with current openSUSE Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: adrian.schroeter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I updated today to current tumbleweed and noticed that I get a freezing system (sometimes just the GUI and sometimes entire network loss). Not sure when this started, because downgrading to last februar snapshot has the same issue now. I made sure that any trace of virtualbox and nvidia drivers got removed, but I can still triggering it by opening a web browser with many tabs. Last words in dmesg are: [ 209.486479] nouveau 0000:02:00.0: fifo: fault 01 [WRITE] at 0000000000048000 engine 03 [PEEPHOLE] client 08 [HUB/BAR_WRITE] reason 02 [PAGE_NOT_PRESENT] on channel 2 [001fcd0000 Xorg.bin[1343]] [ 209.486502] nouveau 0000:02:00.0: fifo:000000:0002:[Xorg.bin[1343]] rc scheduled [ 209.486509] nouveau 0000:02:00.0: fifo:000000: rc scheduled [ 209.486518] nouveau 0000:02:00.0: fifo: INTR 08000000 [ 209.486541] nouveau 0000:02:00.0: fifo:000000:0002:0002:[Xorg.bin[1343]] errored - disabling channel [ 209.486549] nouveau 0000:02:00.0: Xorg.bin[1343]: channel 2 killed! [ 209.503310] nouveau 0000:02:00.0: fifo: fault 01 [WRITE] at 0000000000048000 engine 03 [PEEPHOLE] client 08 [HUB/BAR_WRITE] reason 02 [PAGE_NOT_PRESENT] on channel 2 [001fcd0000 Xorg.bin[1343]] The last line is repeating in an endless loop afterwards, until the system is freezing entirely a few minutes later. The GFX card is a "NVIDIA Corporation GF119 [NVS 310] (rev a1)" running with two displays. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c16 --- Comment #16 from Franck Bui <fbui(a)suse.com> --- (In reply to Fabian Vogt from comment #14) > The graphical session itself is split over multiple services, so unless you > want applications started by keyboard shortcuts (kglobalaccel) have a > different keyring than applications started by the start menu (plasmashell) > or the command launcher (krunner), this is needed. I see that makes sense for a group of user services that belong to the same component. BTW how does it work currently ? do these KDE applications rely on the kernel key management infra currently ? if so do they fallback to the user session keyring ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c15 --- Comment #15 from Franck Bui <fbui(a)suse.com> --- (In reply to Joe S from comment #6) > In my testing I think that the reason is because pam_cifscreds is somehow > now storing the cached credentials in the _ses keyring instead of the > _uid_ses.1000 keyring. Again wrong keyring used, this sounds like cifscreds should have used the user keyring. > From your second link it says: > > IIRC the usual advice by Lennart is to use the user-wide @u keyring > instead > of session keyrings. (Programs searching in @s should automatically find > credentials added to @u, as pam_keyinit creates the link by default.) > > A few years ago I have asked one affected kernel subsystem (cifs) to allow > using @u. They had no interest in doing so. I have since then decided to > just give up on being able to use cifs -o multiuser. (See also: GitHub > issue regarding AFS PAGs.) > > It seems to me like, if cifs used @u and pam_keyinit_so and pam_cifscreds > all used @u then all of these problems would go away. I agree. I don't know cifscreds at all so it might have good reasons to work like it does currently. If you want to get to the bottom of it I would suggest you to contact the cifscreds developers and ask them how this is supposed to work. According to the excerpt you showed, the problem is common to all distros. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207730] vncserver requires dbus-1-x11
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207730 https://bugzilla.suse.com/show_bug.cgi?id=1207730#c3 --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- @Chris Still available? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1140581] Raspberry pi touchscreen unusable
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1140581 https://bugzilla.suse.com/show_bug.cgi?id=1140581#c65 --- Comment #65 from Stefan Dirsch <sndirsch(a)suse.com> --- @Chaoyang Still available? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c14 --- Comment #14 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Franck Bui from comment #12) > That said I agree that user manager instances should have their own session > keyring > properly hooked up even though it doesn't sound that useful for user > services to share keys at a first glance. The graphical session itself is split over multiple services, so unless you want applications started by keyboard shortcuts (kglobalaccel) have a different keyring than applications started by the start menu (plasmashell) or the command launcher (krunner), this is needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208711] New: Artifacts in the terminal
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208711 Bug ID: 1208711 Summary: Artifacts in the terminal Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: msvec(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Since I switched to a new notebook (Dell Latitude 7430) I have artifacts in Konsole. I've tried more recent kernels incl. kernel-default-5.14.21-150500.75.1.ged939b6.x86_64 or 6.1.12 but the artifacts persist. All the other apps seem to work fine, only Konsole seems to be affected. The artifacts are only user-visible, the contents is not affected, it's only display-related. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c13 --- Comment #13 from Franck Bui <fbui(a)suse.com> --- (In reply to Fabian Vogt from comment #11) > pam_cifscreds' design won't work anymore unless pam_systemd can somehow > transfer the session keyring to systemd --user, which is currently just not > possible. The design of kernel keyrings does not allow it. That suggests (again) that cifscreds is using the wrong keyring. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193135] Key stuck after resume from S3
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1193135 https://bugzilla.suse.com/show_bug.cgi?id=1193135#c13 --- Comment #13 from Stefan Dirsch <sndirsch(a)suse.com> --- Hello @Maximilian! Still available? -- You are receiving this mail because: You are on the CC list for the bug.

1 0