TheMCNerd2018
UBUniversal Blue
•Created by TheMCNerd2018 on 10/19/2024 in #🛟bazzite-help
KDE desktop environment crashes and session ends when moving the mouse right as the device locks
Very strange issue I came across yesterday that happened when I moved my mouse while the device was attempting to transition to the lockscreen. The screen showed my desktop for a split second before the screen went blank, only showing the mouse cursor which I could still move around. Upon closing the lid and reopening it (thinking that the lockscreen was just bugged and that putting the device to sleep and waking it would fix it) I was back at the blank screen but with no mouse pointer this time. After a minute of waiting I started trying to switch to a tty to see if the system was still functional, and after a couple seconds I was brought to a tty. All of the ttys were accessible except for tty1 which was just a blinking cursor. Upon signing in through the tty I noticed that I was automatically signed out of the previous session.
I've attached output of rpm-ostree status and a journalctl log of when the issue occured. I think this might be a KDE bug but I'm not entirely sure.
Device specifications:
CPU: Intel i9-13950HX
GPU 1: Intel Raptor Lake-S UHD Graphics
GPU 2: NVIDIA RTX 5000 Ada Generation Laptop GPU
RAM: 128 GB DDR5 5600 Mhz ECC
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
1 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 10/16/2024 in #🛟bazzite-help
Various KDE and system issues in 40.20241013 and 40.20241014 while device is in Power Saver mode
I'm encountering several strange issues that only seem to manifest after the device has been on for a few hours. These issues only started happenening after updating to version 40.20241014. Basically various parts of the desktop start to lock up like the taskbar and notifications. Soon after the screen stops updating for up to several minutes (the only thing updating being the mouse pointer). Additionally putting the device into sleep mode by closing the lid while this is happening puts the device into an state where the system time, USB devices and various other things start to act inconsistent. Putting the device into sleep mode can also trigger these issues to happen too (usually starting with an unresponsive lock screen).
I do not know what exactly triggers these issues, they happen randomly and even happen when nothing else is open on the device. Usually I have to reboot to fix the issues but rarely they will go away by themselves.
EDIT: I found out that having my device on Power Saver causes these issues to manifest, on both 40.20241013 and 40.20241014 after around an hour of use or randomly when putting the device in sleep mode. However the device hanging on shutdown due to either systemd-journal-flush or ostree-finalize-staged still comes up even if I keep my device on Performance.
I've attached a journalctl from a few minutes before the issues started happening up until I saved the log and rebooted along with an output of rpm-ostree status.
Device specifications:
CPU: Intel i9-13950HX
GPU 1: Intel Raptor Lake-S UHD Graphics
GPU 2: NVIDIA RTX 5000 Ada Generation Laptop GPU
RAM: 128 GB DDR5 5600 Mhz ECC
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
89 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 9/12/2024 in #🛟bazzite-help
Baldi's Basics Plus native Linux build graphics corruption with an Nvidia GPU
4 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 9/4/2024 in #🛟bazzite-help
Kernel oops followed by full system lockup when attempting to put laptop in sleep mode
When attempting to put my laptop in sleep mode from the Application Launcher, nothing happened and the button stayed "pressed". Pressing it again caused Application Launcher and the taskbar to lock up, though I could still interact with open windows. Shortly after everything froze. When closing the lid for a minute and reopening it, I could interact with the system again, but could not close certain applications or open any new applications at all. Attempting to unmount external drives also would not work (pressing the button in Dolphin and Disks & Devices would do nothing. Attempting to switch to any of the TTYs would not work, even though the keyboard was fully functional and I could type text in open applications. I also could not lock the device or bring up the shutdown menu.
Shortly after, multiple error notifications about applications failing to launch showed up with this as the reason: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
A few minutes later I force-shutdown my laptop (though for some reason I had to hold the power button for much longer than usual) and turn it back on. I grabbed the journal of the last boot, which shows multiple kernel oops along with other errors at the time I attempted to put the laptop into sleep mode (the errors start at 20:39:35 in the log).
I've uploaded the rpm-ostree status along with the journalctl log that I captured.
I'm unsure what caused this issue as everyting was working normally before I attempted to put the laptop into sleep mode.
Specifications of the Laptop:
-Model: Lenovo Thinkpad P16 Gen 2
-CPU: Intel i9-13950HX
-GPU 1: Intel Raptor Lake-S UHD Graphics
-GPU 2: Nvidia RTX 5000 Ada Laptop GPU
-RAM: 128 GB DDR5 5600 MHz ECC
1 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 9/2/2024 in #🛟bazzite-help
How to make Blender Flatpak always use the dedicated Nvidia GPU?
For some odd reason that I can't figure out, the Blender Flatpak that I installed from KDE Discover only ever uses the Intel Integrated GPU on my laptop instead of the Nvidia GPU. The only way I have gotten it to use the Nvidia GPU is with switcherooctl, but that requires me to execute the command in a terminal every time I want to use Blender. Is there any way I can make the Blender Flatpak always use the dedicated Nvidia GPU in my laptop regardless of how I open it?
1 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 8/25/2024 in #🛟bazzite-help
Virtualization randomly stopped working and libvirt stuff vanished after an update
Very strange issue that has come up after a system update installed a few days ago. I can no longer start Virtual Machine manager with an error stating "Unable to connect to libvirt qemu:///system. Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory". Attempting to navigate to that directory fails is it is no longer present there. Additionally attempting to run ujust setup-virtualization and selecting enable virtualization exits after printing a warning about updates taking longer. Additionally the libvirt user group is missing too.
Does anyone know what caused this to happen? Right now I'm re-running the ujust comand but selected to disable virtualization instead so that after I reboot I can re-enable it through the ujust command to see if that fixes the issue.
7 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 8/22/2024 in #🛟bazzite-help
Display freezes randomly on a Thinkpad P16 Gen 2
Ever since I have installed Bazzite on my Thinkpad P16 Gen 2, a rare issue comes up randomly where the screen just freezes while mostly everything else continues to function (sounds will play, programs will run, the system will respond to keyboard inputs, etc). Additionally connecting a monitor via the HDMI port on the laptop while this happens results in the monitor simply displaying a blank screen (not a "No Signal" screen). The only things that don't function in this state is plugging in new USB devices and some keyboard shortcuts like for the volume and brightness. After force-shutting down the laptop and powering it back up, most programs that were opened when the issue occurred had their window resized to 640x480.
Looking at the journal of the last boot shows a bunch of "Pageflip timed out!" errors after the issue started occurring (which was at 21:28:44 in the journal as it happened right after exiting fullscreen of a running game). Sadly kernel messages were lost as they vanished from the journal while I was viewing it in the KDE journal viewer (most likely due to another Nvidia bug where the driver spams errors to dmesg when any chromium-based application is open).
Is there any fix to this issue?
Specifications of the Thinkpad:
CPU: Intel i9-13950HX vPro
GPU: Nvidia RTX 5000 Ada Laptop GPU
RAM: 128 GB DDR5 5600 MHz ECC
5 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 7/23/2024 in #🛟bazzite-help
Fwupd firmware updates no longer work; states "shim isn't installed to EFI/bazzite/shimx64.efi"
Every time I attempt to apply firmware updates with fwupd, I get an error stating that "Secure boot is enabled, but shim isn't installed to EFI/bazzite/shimx64.efi" and firmware update fails. This happen in both the KDE Discover application and when invoking fwupdmgr through a terminal. This did not happen the last time I've applied firmware updates through fwupd which was around a month ago. On my system all EFI boot files for bazzite are present in a "fedora" folder in the EFI partition, though for some reason a "bazzite" folder was recently created in the EFI partition which only contains a "fw" folder which contains a CAP file within.
Has a recent Bazzite change caused this issue to occur?
4 replies
UBUniversal Blue
•Created by TheMCNerd2018 on 4/24/2024 in #🛟bazzite-help
Odd issues after updating to Bazzite 3 on a Thinkpad P16 Gen 2
After updating to Bazzite 3.0 on my Thinkpad P16 Gen 2, I'm encountering very strange issues when the system boots up or shuts down. On bootup, SDDM very often fails to load correctly, getting stuck on a blank screen with or without a mouse pointer. After a few minutes on the black screen SDDM finally appears, but it's completely unresponsive. This happens regardless of whether I last used the X11 or Wayland session.
After I managed to sign in via one of the TTYs, attempting to start plasma with X11 results in the system locking up for a few minutes (no keyboard inputs work during this so I can't change to another TTY) before the desktop finally loads. If I start plasma with Wayland instead, it loads within a few seconds without any issues. Doing either of these results in the SDDM becoming functional.
When I'm logged in at the desktop, I no longer have a GPU switcher icon in the tray, though the system still sees both the Nvidia GPU and the Intel UHD Graphics and seems to switch between the Intel UHD Graphics and Nvidia GPU as I can run games properly. Virtualization also works correctly.
When I attempt to shut down the system, it takes around 3 minutes to do so now. If I remove quiet from the kernel arguments (allowing me to see kernel messages) it complains about a watchdog timer a bit before shutting down.
None of these issues occur when I boot from the Bazzite 39 image, they only started happening after the Bazzite 40 image was installed. Additionally the only packages that are layered on the system are the ones that ujust installed when enabling virtualization. I've also collected a dmesg log, a systemd-blame log, a journalctl log and the rpm-ostree status, though I'm not sure if they will help in finding out what is causing these issues.
6 replies