03.05.2019 Sync Report
Nacho_Trebuchet
Does TF2 crash for you after playing for some time, or instantly? Because I just gave TF2 a quick check and it's working fine on my system (GNOME edition, Nvidia 418.52.05 drivers).
Junglist My situation is this (sorry if this is too long winded):
I was able to run TF2 before the 5.0 kernel release, I think. (I don't play that much to know the exact timing). But I do know I just bought Dying Light which I can play for no more than 5 minutes before my computer crashes (complete power off). I can play for 5 to 10 minutes before TF2 crashes the system. I have high frame rates for both. I think there is a heating issue (bad sensor, kernel change, or DE update). I have not had issues in the past with Tomb Raider, LFD2, HalfLife, Portal, BioShock Infinite, Borderlands, etc.
I run a mild overclock, which MSI calls Game Boost, at 4.05GHz (base is 3.6GHz and max overclock is 4.2GHz). Game Boost defaults the CPU fan to max. I've had no previous issues with this setup for the past year. I run Solus Budgie, Ryzen 5 2600x on a MSI B450, Sapphire Nitro+ RX580, 16GB RAM, two 140mm intake fans, two 120mm exhaust fans, and the stock Wraith CPU fan.
After this issue started last week, I installed Radeon Profile to run the GPU fans at a higher fixed RPM thinking it may be the GPU overheating. Sensors seem to indicate the GPU is fine. I have not experienced any heating issues previously with the stock air cooler running at max. I see one sensor with a small range which is the one I believe is exceeding its threshold. Do you know what the k10temp-pci-00c3 sensor is? Once I start gaming, it quickly jumps to over 55 deg C then crashes soon after (assuming it exceeded 70 deg C). Other temps seem to stay within range, including the CPU (CPUTIN) and GPU (amdgpu-pci-1c00). I could be misinterpreting these sensors below, so I am not positive this is a heating issue or some other issue with the DE.
SENSORS AT IDLE:
fan1: 0 RPM (min = 0 RPM)
fan2: 2523 RPM (min = 0 RPM)
fan3: 1247 RPM (min = 0 RPM)
fan4: 1288 RPM (min = 0 RPM)
fan5: 1212 RPM (min = 0 RPM)
fan6: 1229 RPM (min = 0 RPM)
SYSTIN: +39.0°C sensor = CPU diode
CPUTIN: +36.0°C (high = +127.0°C, hyst = +105.0°C) sensor = thermistor
AUXTIN0: +38.0°C (high = +127.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN1: -128.0°C sensor = thermistor
AUXTIN2: +39.0°C sensor = thermistor
AUXTIN3: -1.0°C sensor = thermistor
SMBUSMASTER 0: +40.0°C (high = +127.0°C, hyst = +105.0°C)
PCH_CHIP_CPU_MAX_TEMP: +0.0°C
PCH_CHIP_TEMP: +0.0°C
PCH_CPU_TEMP: +0.0°C
intrusion0: ALARM
intrusion1: ALARM
beep_enable: disabled
amdgpu-pci-1c00
Adapter: PCI adapter
vddgfx: +0.72 V
fan1: 838 RPM (min = 0 RPM, max = 3200 RPM)
temp1: +32.0°C (crit = +94.0°C, hyst = -273.1°C)
power1: 34.16 W (cap = 175.00 W)
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +40.0°C (high = +70.0°C)
Tctl: +40.0°C
Nacho_Trebuchet I only did this: sudo eopkg install https://packages.getsol.us/unstable/g/gnome-shell/gnome-shell-3.32.1-41-1-x86_64.eopkg
and reboot. This solved the 100% cpu peak problem for me. But this package as already on stable repositories.
mariojuniorjp
Got it. Unfortunately that fix won't work for me. I'm on Budgie. I wasn't sure if your solution was DE specific and it looks to be. Glad that worked for you. Thanks!
Nacho_Trebuchet but this solves the problem for me on budgie. ;P
Also, maybe this is another problem with your system. Good luck!
- Edited
mariojuniorjp Ahhhh. I should be patient, follow the link and read. I saw Gnome-shell in the URL and assumed. Shame on me. Thanks for pointing that out.
Hi, I have the icons problem but the suggested fix didn't fixed it. Any ideas?
anthonydouwes Are you using Vivaldi? Because I have the same issue with vivaldi-stable which wasn't updated on friday.
I'm on Budgie as well.
Screen dims and turns off with fullscreen video or non-fullscreen video running in active tab, neither of which happened before last sync. When I turn off screen dimming and blank screen after x minutes, it just suspends after the specified time in automatic suspend. In Firefox everything works as expected.
Just wanted to report an issue that I managed to fix on my own.
I am running Solus Gnome. After the update last weekend when I rebooted it went into a blank screen. I used the Solus 4 ISO to run a LiveCD and get back into the internet and troubleshoot.
I rebooted, hit CTRL+ALT+F2
and logged in through TTY
.
Then, I ran
sudo usysconf run -f
sudo eopkg rbd
sudo eopkg up
The usysconf
showed that one of my Icon sets, Numix-Circle was broken.
I logged back in through the Solus 4 ISO LiveCD and deleted the Numix-Circle folders in /usr/share/icons and when I rebooted everything worked fine.
Everything works properly now thanks to some of the posts on this forum.
Hey quick question:
It seems like Budgie does not have GNOME's org.gnome.settings-daemon.plugins.power
percentage-low percentage-critical percentage-action and use-time-for-policy keys. Is this intentional?
I do need to adjust those controls, so if they don't exist on dconf/gsettings intentionally.. Is there a config file I should refer to to adjust them?
Um, my Firefox has no sound, it had it yesterday, and no updates were done.
catfishsushi That isn't relevant to this sync report. I'd check that you don't have tabs accidentally muted, double check via Sound settings, etc.