Logitech capture crashing11/24/2023 ![]() ![]() Xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves Topoext tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt Smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce Rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni skinit smap smca sme Perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 ![]() Npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb Mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl Volts: 1.2 V ext-clock: 100 MHz Core speeds (MHz): 1: 2193 2: 2194 3: 2195Ĥ: 2192 5: 2176 6: 2162 7: 2186 8: 2182 9: 2195 10: 2190 11: 2185 12: 2163įlags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1īmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb cpuidĬr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasidįma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca Info: 8-Core model: AMD Ryzen 7 2700X socket: AM4 bits: 64 type: MT MCPĪrch: Zen+ family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D cache: ![]() Total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/Aĭevice-2: DIMM_A2 size: 8 GiB speed: 3000 MT/s type: DDR4ĭevice-3: DIMM_B1 size: 8 GiB speed: 3000 MT/s type: DDR4ĭevice-4: DIMM_B2 size: 8 GiB speed: 3000 MT/s type: DDR4 RAM: total: 31.26 GiB used: 7.46 GiB (23.9%)Īrray-1: capacity: 128 GiB slots: 4 EC: None max-module-size: 32 GiBĭevice-1: DIMM_A1 size: 8 GiB speed: 3000 MT/s type: DDR4ĭetail: synchronous unbuffered (unregistered) bus-width: 64 bits Serial: UEFI: American Megatrends v: 5861 date: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-F GAMING v: Rev X.0x Parameters: root=UUID=0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 quiet apparmor=1 security=apparmor Here’s my inxi before the update: System: After that, qjackctl crashed and from then on I didn’t have any sound, in or out, even after restarting qjackctl. I usually have about 20 sets of inputs and outputs. I should have kept better notes on exactly what happened when, but as I tested -all- the inputs and outputs in the qjackctl graph disappeared. I started by opening my qjackctl graph to watch what happened when I opened Jitsi and Discord again and used the mic/sound tests that they both have. config and I reapplied the patches and played around a little more. This morning, I followed the instructions above to remove the pulse tdb and cookie files from. I didn’t have time to mess with it last night, so I reverted to a previous btrfs snapshot and all worked fine again. I use pipewire with jack2 and qjackctl, so I opened the qjacktl graph to see what was going on and it didn’t show the icon for my Quadcast capture outputs. When I quit and reopened Discord, Jitsi lost input from the mic. When I refreshed the Jitsi page, Discord lost input from my mic. I talked fine on Jitsi for over an hour, but as soon as I added a Discord conversation, Jitsi no longer got sound from my mic. Others on the bug report have now confirmed it too, and it seems even some wired USB devices (from other vendors) are also seeing the same problem.įor now, switching to Proton 6.3-8 or unplugging devices will get Unity games to work again on Linux and Steam Deck.I had sound issues after installing the last update, first noticed by my HyperX Quadcast USB mic appearing to be exclusive to one application at a time. Even if a game is fully loaded and working, simply plugging it in would cause an instant crash. I tested this repeatedly, and yup - simply having that plugged in caused the problem. Proton 6.3-8 would work but for some games, that had other issues that Proton 7 solved.Īfter some fiddling, I eventually found out that unplugging my Logitech Wireless Receiver suddenly made the games work. There was a bug report open from others also seeing a similar issue. Certain Unity games wouldn't load, and instead would present me with a Unity error screen with a loading bar and then just quit. Recently, while trying to capture footage from the Steam Deck for the GamingOnLinux YouTube channel I came up against a problem. This is the same across Linux desktop and Steam Deck, as it's a problem somewhere with Proton. Update: a fix for this is now available in Proton Experimental, so switch to that for now.Ĭuriously, it seems Proton 7 and Proton Experimental are having problems with Unity games recently but there's a possible temporary workaround for you. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |