cube
cube
PostsComments
UBUniversal Blue
Created by cube on 3/14/2025 in #🛟bazzite-help
Steam crashing constantly after loading (since 41.20250314)
Steam loads, then there is a black window, then it crashes (window closes), then I see the window again, then crash again, this repeats until I close steam from the sys tray.
45 replies
UBUniversal Blue
Created by cube on 3/14/2025 in #🛟bazzite-help
pcie errors (since version 41.20250314)
Haven't seen this before. Im not sure if I should report this upstream. kernel: 6.13.6-103.bazzite.fc41.x86_64 
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                  (First)
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                  (First)
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr    
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:06:52 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                  (First)
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:07:00 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                  (First)
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0: AER: Correctable error message received from 0000:00:1c.0
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0:   device [8086:a111] error status/mask=00000001/00002000
Mar 14 20:07:04 fedora kernel: pcieport 0000:00:1c.0:    [ 0] RxErr
5 replies
UBUniversal Blue
Created by cube on 2/26/2025 in #🛟bazzite-help
Hardware Acceleration on older Intel processors (pre Broadwell)
Right now on Bazzite, hardware acceleration does not work on older intel processors because it requires two packages: libva-intel-driver (for H264) and libva-intel-hybrid-driver (for VP8/9). They also require the LIBVA_DRIVER_NAME environment variable to be set to i965 (arch wiki). Can these packages be included by default in Bazzite? thanks!
3 replies
UBUniversal Blue
Created by cube on 2/20/2025 in #🛟bazzite-help
Waydroid starts in background (for no apparent reason)
Is there any way I can disable Waydroid? Recently I was getting really bad lag in a game when usually it runs fine. I looked at Mission Center and saw Waydroid was running in background. I killed it with pkill -9 waydroid. But then some hours later, I again got lag (while watching a movie), and saw it was running again. The weird thing is that running sudo waydroid container stop and sudo waydroid session stop doesn't stop it either. In fact sudo waydroid status shows Session: STOPPED but its running in the background. Also it seems to start close all installed apps continuously (as you can see in the screencast).
6 replies