termdisc Posts - Answer Overflow

termdisc

•Created by termdisc on 8/12/2024 in #🛟bazzite-help

Solaar no longer running via Distrobox (Fedora, Arch or Ubuntu)

I have been using Solaar via a Fedora distrobox container forever, but it recently stopped working. I haven't changed anything about the containers as it exists solely to run Solaar. I have tried running it in Arch and Ubuntu containers, but it fails to run all the same with the same error. This is the terminal output from attempting to manually run it:

→  solaar
rules cannot access modifier keys in Wayland, accessing process only works on GNOME with Solaar Gnome extension installed
failed to set up dbus
solaar: error: Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/solaar/gtk.py", line 176, in main
    _dbus.watch_suspend_resume(lambda: _listener.ping_all(True))
  File "/usr/lib/python3.12/site-packages/solaar/dbus.py", line 59, in watch_suspend_resume
    bus.add_signal_receiver(_suspend_or_resume, "PrepareForSleep", dbus_interface=_LOGIND_INTERFACE, path=_LOGIND_PATH)
    ^^^
NameError: name 'bus' is not defined. Did you mean: 'dbus'?

→  solaar
rules cannot access modifier keys in Wayland, accessing process only works on GNOME with Solaar Gnome extension installed
failed to set up dbus
solaar: error: Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/solaar/gtk.py", line 176, in main
    _dbus.watch_suspend_resume(lambda: _listener.ping_all(True))
  File "/usr/lib/python3.12/site-packages/solaar/dbus.py", line 59, in watch_suspend_resume
    bus.add_signal_receiver(_suspend_or_resume, "PrepareForSleep", dbus_interface=_LOGIND_INTERFACE, path=_LOGIND_PATH)
    ^^^
NameError: name 'bus' is not defined. Did you mean: 'dbus'?

7 replies

UBUniversal Blue

•Created by termdisc on 5/31/2024 in #🛟bazzite-help

KDE Audio Device Selection

2 replies

UBUniversal Blue

•Created by termdisc on 5/14/2024 in #🛟bazzite-help

screen flickers in games after a desktop session puts the display to sleep

At least a few updates ago on stable and testing (notable only since Plasma 6), half of my display flickers white in games but only if the display has gone to sleep at some point. Restarting fixes it but only until I walk away from the PC for a period of time and the monitor turns off. This occurs on both DXVK and VKD3D and for games across different storefronts. GPU: AMD 7900xt DE: KDE, Wayland

46 replies

UBUniversal Blue

•Created by termdisc on 4/10/2024 in #🛟bazzite-help

Cannot launch Lutris or Steam games with 20240410 build - Mangohud issue

I just updated this morning and am coming up against an issue that I did not have last night. Both launching the Lutris app and launching Steam games throw the same error:

09:14:27 ~ →  lutris -d
INFO     2024-04-10 09:14:30,675 [application.do_command_line:479]:Starting Lutris 0.5.16
INFO     2024-04-10 09:14:30,676 [startup.get_drivers:67]:Running AMD Mesa driver 23.3.6 on AMD Radeon RX 7900 XT (radeonsi, navi31, LLVM 17.0.6, DRM 3.57, 6.8.4-202.fsync.fc39.x86_64) (0x744c)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU: 1002:744C 1EAE:7905 (amdgpu drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:1018] Failed to read presets file: '/home/outphase/.config/MangoHud/presets.conf'
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:145] Unrecognized key: '=Shift_L'
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:643] Unknown option 'engine'
terminate called after throwing an instance of 'std::out_of_range'
  what():  stoi
Aborted (core dumped)

09:14:27 ~ →  lutris -d
INFO     2024-04-10 09:14:30,675 [application.do_command_line:479]:Starting Lutris 0.5.16
INFO     2024-04-10 09:14:30,676 [startup.get_drivers:67]:Running AMD Mesa driver 23.3.6 on AMD Radeon RX 7900 XT (radeonsi, navi31, LLVM 17.0.6, DRM 3.57, 6.8.4-202.fsync.fc39.x86_64) (0x744c)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU: 1002:744C 1EAE:7905 (amdgpu drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
INFO     2024-04-10 09:14:30,677 [display.display_gpu_info:78]:GPU:   (evdi drivers)
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:1018] Failed to read presets file: '/home/outphase/.config/MangoHud/presets.conf'
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:145] Unrecognized key: '=Shift_L'
[2024-04-10 09:14:30.707] [MANGOHUD] [error] [overlay_params.cpp:643] Unknown option 'engine'
terminate called after throwing an instance of 'std::out_of_range'
  what():  stoi
Aborted (core dumped)

10 replies

UBUniversal Blue

•Created by termdisc on 2/12/2024 in #🛟bazzite-help

XR Gaming driver unable to run

This issue has been cross-posted with the LinuXR server. I recently picked up the Viture One XR glasses and attempted to use the XR Gaming Decky plugin. It initially says "No device connected" despite actually being connected. Attempting to restart the service results in this error:

08:46:13 ~ →  sudo systemctl status xreal-air-driver
[sudo] password for termdisc: 
× xreal-air-driver.service - XREAL Air user-space driver
     Loaded: loaded (/etc/systemd/system/xreal-air-driver.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2024-02-12 08:44:53 CST; 1min 30s ago
   Duration: 14ms
    Process: 7671 ExecStart=/home/termdisc/bin/xrealAirLinuxDriver (code=exited, status=1/FAILURE)
   Main PID: 7671 (code=exited, status=1/FAILURE)
        CPU: 11ms

Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Scheduled restart job, restart counter is at 6.
Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Start request repeated too quickly.
Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Failed with result 'exit-code'.
Feb 12 08:44:53 bazzil systemd[1]: Failed to start xreal-air-driver.service - XREAL Air user-space driver.

08:46:13 ~ →  sudo systemctl status xreal-air-driver
[sudo] password for termdisc: 
× xreal-air-driver.service - XREAL Air user-space driver
     Loaded: loaded (/etc/systemd/system/xreal-air-driver.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2024-02-12 08:44:53 CST; 1min 30s ago
   Duration: 14ms
    Process: 7671 ExecStart=/home/termdisc/bin/xrealAirLinuxDriver (code=exited, status=1/FAILURE)
   Main PID: 7671 (code=exited, status=1/FAILURE)
        CPU: 11ms

Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Scheduled restart job, restart counter is at 6.
Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Start request repeated too quickly.
Feb 12 08:44:53 bazzil systemd[1]: xreal-air-driver.service: Failed with result 'exit-code'.
Feb 12 08:44:53 bazzil systemd[1]: Failed to start xreal-air-driver.service - XREAL Air user-space driver.

Attempting to run the driver manually results in this error:

08:46:24 ~ →  ./bin/xrealAirLinuxDriver 
./bin/xrealAirLinuxDriver: /lib64/libcurl.so.4: no version information available (required by ./bin/xrealAirLinuxDriver)

08:46:24 ~ →  ./bin/xrealAirLinuxDriver 
./bin/xrealAirLinuxDriver: /lib64/libcurl.so.4: no version information available (required by ./bin/xrealAirLinuxDriver)

This error is confusing because libcurl.so.4 is provided by libcurl and is already available. Another user on the LinuXR server is facing the same error on Fedora although I don't know what spin/flavor. Does anyone have experience with XR glasses to overcome the driver and plugin errors?

7 replies

UBUniversal Blue

•Created by termdisc on 12/31/2023 in #🛟bazzite-help

SDDM not appearing after rebasing

Just changed from Gnome to KDE on my desktop. On boot, I just get a black screen with no interactivity. I can access tty terminals, so something is working. How do I push forward to gain access to the DE?

14 replies

UBUniversal Blue

•Created by termdisc on 12/26/2023 in #🛟bazzite-help

night mode requires enabling force composite per-game

The Steam UI and individual games must have force composite enabled again to have night mode applied. A game’s setting is retained between launches.

7 replies

UBUniversal Blue

•Created by termdisc on 11/7/2023 in #🛟bazzite-help

Dependency problem when trying to layer libOSMesa

I'm trying to reinstall a layered package libOSMesa, and I'm getting these dependency errors. Is there anything I can do about this right now, or do I just have to wait for packages to normalize after the fc39 update?

17 replies

UBUniversal Blue

•Created by termdisc on 9/7/2023 in #🛟bazzite-help

rebasing from gnome to kde - black screen on boot to ode

I just rebased from gnome to kde but ended up with a black screen as if SDDM isn’t firing off. I can access tty to reset or remove any potentially messed up configs that may have carried over from old backups. Any suggestions on what to remove?

4 replies

Gaming

Programming