Dear Maintainer,
* What led up to the situation?
The problems started immediately after upgrading to Trixie. There was no errors
or anything while upgrading, but the problems started immediately after that. I
can run the system normally for around day, but when the problems start, almost
all the applications become usable. Gaming, screen casting and similar video-
related tasks seems to many times cause the crash, or it at least happens when
I'm doing things like that.
In logs I see errors related to gnome-shell, wayland, pipewire, gpu, etc. So
the problem affects systemwide and only after reboot things work normally
again. None of the internet browsers, video players or almost anything starts
at all, after few hours, when the packages start crashing. MPV player haven't
worked at all, since the upgrade.
Here are some examples of the errors in logs:
pw.mem: 0x55834d330890: cannot import invalid fd:-1
Aug 16 23:48:50 86465435-PC pipewire[220908]: pw.port: 0x55834d22ee30: mix use
buffers failed: -22 (Invalid argument)
Aug 16 23:48:50 86465435-PC com.obsproject.Studio.desktop[276650]: info:
[pipewire] Stream 0x5582389753e0 state: "error" (error: error use input
buffers: -22 (Invalid argument))
Aug 16 23:48:50 86465435-PC com.obsproject.Studio.desktop[276650]: error:
[pipewire] Error id:2 seq:64 res:-32 (Broken pipe): error use input buffers:
-22 (Invalid argument)
Aug 16 23:48:50 86465435-PC pipewire[220908]: pw.link: (105.0.0 -> 123.0.0)
allocating -> error (error use input buffers: -22 (Invalid argument)) (paused-
paused)
Aug 16 23:48:50 86465435-PC gnome-shell[3698]: pipewire remote error: id:2
error use input buffers: -22 (Invalid argument)
Aug 16 22:47:42 86465435-PC gnome-shell[3698]: WL: error marshalling arguments
for format_table: dup failed: Too many open files
Aug 16 22:47:42 86465435-PC gnome-shell[3698]: WL: error in client
communication (pid 3698)
Aug 16 22:47:42 86465435-PC gnome-shell[248546]: (EE) failed to read Wayland
events: Broken pipe
Aug 16 22:47:42 86465435-PC gnome-shell[3698]: Connection to xwayland lost
Aug 16 22:47:42 86465435-PC gnome-shell[3698]: X Wayland crashed; attempting to
recover
Aug 16 21:46:50 86465435-PC gnome-shell[3698]: Failed to remove DRM timeline
syncobj
Aug 16 21:46:50 86465435-PC gnome-shell[3698]: Failed to remove DRM timeline
syncobj
Aug 16 21:46:50 86465435-PC pipewire[3538]: pw.mem: 0x56149351e880: cannot
import invalid fd:-1
Aug 16 21:46:50 86465435-PC pipewire[3538]: pw.port: 0x561493b87080: mix use
buffers failed: -22 (Invalid argument)
Aug 16 21:46:50 86465435-PC pipewire[3538]: pw.link: (99.0.0 -> 98.0.0)
allocating -> error (error use input buffers: -22 (Invalid argument)) (paused-
paused)
Aug 16 17:08:37 86465435-PC gnome-shell[3698]: Error blitting to screencast
framebuffer: cogl_framebuffer_blit premult mismatch.
Aug 16 17:08:37 86465435-PC gnome-shell[3698]: Could not destroy EGLImage
attached to GBM BO: One or more argument values are invalid.
Aug 16 17:08:37 86465435-PC gnome-shell[3698]: Error blitting to screencast
framebuffer: cogl_framebuffer_blit premult mismatch.
Aug 16 17:08:37 86465435-PC gnome-shell[3698]: Could not destroy EGLImage
attached to GBM BO: One or more argument values are invalid.
dmesg gives [drm] Fence fallback timer expired on ring sdma0
Also, during the boot phase, I started receiving 'your CPUs had inconsistent
variable MTRR settings', that didn't happen before the upgrade either.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have tried to find solution on my own, but so far I haven't found anything
helpful.