Config breaks after system crash

Issues & Assistance Newbies
#1

Hello all.

When I reboot Garuda sometimes my system freezes right after I login. It mostly seems to happen at random. Sometimes after a system crash, after I update, or just when I boot up. After the system freezes and I hard reboot, on the linux boot screen I get a Wating for dynamic link cache for about 2 seconds, boot up nomally, then login again. After loging in again applications like Pamac and Brave have the Breeze Dark theme (instead of the Sweetified Plasma theme), The compositor goes starts using OpenGL 2.0 (instead of 3.1), and there's a blue button in the top left corner of every Titlebar (the same one you see if you go to System Settings -> Appearance -> Window Decorations -> Sweet-Dark/Sweet-Dark-transparent. I've gone to Garuda Assistant and reset every config one by one, but only after reseting "All" configs does it fix the issue.

Is there a way to fix this without having to reset all configs?

System:
Kernel: 5.15.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f4e7b0e7-de23-4a85-9052-1ef321250ac6 rw [email protected]
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=UUID=203739ae-5fe8-4720-bf53-35f074b31819 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: MAXIMUS VII FORMULA v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 3503
date: 04/18/2018
CPU:
Info: model: Intel Core i7-4790K bits: 64 type: MT MCP arch: Haswell
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 4038 high: 4352 min/max: 800/4400 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3998 2: 3998 3: 3998
4: 3998 5: 4003 6: 3998 7: 3966 8: 4352 bogomips: 63961
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: nvidia
v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1b81
class-ID: 0300
Device-2: NVIDIA GM204 [GeForce GTX 970] vendor: eVga.com. driver: nvidia
v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 02:00.0 chip-ID: 10de:13c2
class-ID: 0300
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 101 s-size: 966x272mm (38.0x10.7")
s-diag: 1004mm (39.5")
Monitor-1: DP-1 res: 1920x1080 hz: 60 dpi: 102
size: 477x268mm (18.8x10.6") diag: 547mm (21.5")
Monitor-2: DP-3 res: 1920x1080 hz: 60 dpi: 102
size: 477x268mm (18.8x10.6") diag: 547mm (21.5")
OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
class-ID: 0403
Device-2: NVIDIA GP104 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:10f0
class-ID: 0403
Device-3: NVIDIA GM204 High Definition Audio vendor: eVga.com.
driver: snd_hda_intel v: kernel bus-ID: 02:00.1 chip-ID: 10de:0fbb
class-ID: 0403
Sound Server-1: ALSA v: k5.15.12-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: JACK v: 1.9.19 running: no
Sound Server-4: PulseAudio v: 15.0 running: no
Sound Server-5: PipeWire v: 0.3.42 running: yes
Network:
Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: kernel
port: f040 bus-ID: 00:19.0 chip-ID: 8086:15a1 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 06:00.0
chip-ID: 8086:24f3 class-ID: 0280
IF: wlp6s0 state: down mac: <filter>
Device-3: TP-Link RTL8812AU Archer T4U 802.11ac type: USB driver: N/A
bus-ID: 7-1.4:4 chip-ID: 2357:0101 class-ID: 0000 serial: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
bus-ID: 3-5.1:4 chip-ID: 8087:0a2b class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 2.29 TiB used: 59.07 GiB (2.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Dogfish Technology model: SSD 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1A0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZEX-21M2NA0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 1A01 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 860 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-4: /dev/sdi maj-min: 8:128 type: USB vendor: Seagate
model: ST9500325AS size: 465.76 GiB block-size: physical: 512 B
logical: 512 B type: HDD rpm: 5400 serial: <filter> rev: 214 scheme: GPT
Partition:
ID-1: / raw-size: 431.05 GiB size: 431.05 GiB (100.00%)
used: 59.07 GiB (13.7%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 431.05 GiB size: 431.05 GiB (100.00%)
used: 59.07 GiB (13.7%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 431.05 GiB size: 431.05 GiB (100.00%)
used: 59.07 GiB (13.7%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 431.05 GiB size: 431.05 GiB (100.00%)
used: 59.07 GiB (13.7%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 34.42 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdc3 maj-min: 8:35
ID-2: swap-2 type: zram size: 31.29 GiB used: 2.2 MiB (0.0%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 48 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 13%
Info:
Processes: 379 Uptime: 2h 24m wakeups: 0 Memory: 31.29 GiB
used: 9.21 GiB (29.4%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 2178 lib: 587 flatpak: 0
Shell: fish v: 3.3.1 running-in: konsole inxi: 3.3.11
#2

Did it happen on your previous boot? If so - the output of journalctl -b -1 would be very helpful.

#3

No, it mostly happens at random. Is there anything specific I should be looking for in jourrnalctl -b -1?

#4

The reset config button copies the config files from /etc/skel back into your home folder. I'm not sure which config file would be relevant here, but you would have to copy said config file(s?) from /etc/skel to your own home folder manually, which would fix the issue. If you do find out, I could add it to Garuda Assistant :wink:

2 Likes
#5

Crashes and errors. The next time it happens randomly - reboot and post that log (it shows the log of your previous boot) and likely a tthe end, it will show errors and crashes.

1 Like
#6

Ok, I'll make sure to do that. Thanks for the help!

#8

After having another crash I realized that the logs I posed form journalctl -b -1 is just what gets logged everytime I boot, sorry about that. I couldn't get the log from my last crash either because it was flooded with another by some other logs.

#9

I found that gtk-3.0 folder fixes the theme and kwinrc file fixes the titlebar and compositor. For some reason after I crash the files get overwriten. The gtk-3.0's settings.ini files changes from the default to

[Settings]
gtk-application-prefer-dark-theme=true
gtk-button-images=true
gtk-cursor-theme-name=Sweet-cursors
gtk-cursor-theme-size=24
gtk-decoration-layout=icon:minimize,maximize,close
gtk-enable-animations=true
gtk-font-name=Fira Sans,  10
gtk-icon-theme-name=BeautyLine
gtk-menu-images=true
gtk-modules=colorreload-gtk-module:appmenu-gtk-module
gtk-primary-button-warps-slider=false
gtk-shell-shows-menubar=1
gtk-toolbar-style=3

while the kwinrc file only changes to

[Compositing]
OpenGLIsUnsafe=false

[Desktops]
Id_1=c8398d2f-3cc6-43ad-ac87-565c643d7230
Number=1
Rows=1

[Windows]
BorderlessMaximizedWindows=true

and I have no idea why this happens.

#10

Hi i just got the same problem but for me it also killed Latte, and my internet connection. I have the jounalctl but its to long to upload as plain text and i cant upload the file. is there another way to share it with you?
Edit: @filo I think thats what might have happpend yesterday to just in a weaker form

#11

It looks like journalctl is just a log of everything that's happened from boot till shutdown. So you only need to share anything towards the end that looks like it's related to an error. It's never broken the internet for me, but for latte the way I got it back is just typing latte on the desktop and clicking latte.

#12

If Latte is crashing on startup, this can be corrected by adding a 3 second delay (sleep 3) before Latte starts up. Search the forum if you need help doing that as this has been covered in a fair number of posts in the past.

3 Likes