Desktop settings and latte dock resets after reboot(after system crash while gaming)

Hi everyone.
I have a problem when sometimes my game is freezes so much, that my system does it too and then I shut it down with a power button.
It’s okay, I guess(although would’ve been nice to avoid those situations somehow), but the problem is that after that some desktop settings can reset.

Either non, or all these at once:
Screen Edges(I have them all non-active, but default one turns on)
Task Switcher(but only it’s type, custom shortcut will still be there)
Latte Dock keeps my custom profile, but it becomes empty(dock and panel dissapear from the profile and I need to create and configure new ones)
“Raise maximum volume” for output disables itself
There was something else related to default settings, but I can’t remember(cause it’s less annoying) and you got the idea anyway.

And my full specs just in case:

System:
  Kernel: 5.15.59-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.15-x86_64
    root=UUID=3b24eaa3-20f4-4163-8828-353ccc9dba82 rw rootflags=subvol=@
    quiet udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.6 tk: Qt v: 5.15.5 info: latte-dock
    wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: Acer product: Swift SF314-43 v: V1.04
    serial: <superuser required>
  Mobo: LN model: Sake_CA v: V1.04 serial: <superuser required>
    UEFI: Insyde v: 1.04 date: 07/28/2021
Battery:
  ID-1: BAT1 charge: 41.9 Wh (79.5%) condition: 52.7/53.2 Wh (99.0%)
    volts: 12.4 min: 11.6 model: COSMX AP20CBL type: Li-ion serial: <filter>
    status: N/A
CPU:
  Info: model: AMD Ryzen 5 5500U with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 2 gen: 3 built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x68 (104) stepping: 1 microcode: 0x8608102
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 2952 high: 3470 min/max: 1400/4056 boost: enabled
    scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 3072 2: 2700
    3: 1992 4: 2046 5: 3241 6: 3175 7: 3188 8: 3237 9: 3015 10: 2968 11: 3470
    12: 3326 bogomips: 50321
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Lucienne vendor: Acer Incorporated ALI driver: amdgpu
    v: kernel arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm) built: 2018-21
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s
    ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0
    chip-ID: 1002:164c class-ID: 0300
  Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-3:2
    chip-ID: 0408:a094 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x683d built: 2019
    res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85")
    diag: 355mm (14") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  OpenGL: renderer: RENOIR (renoir LLVM 14.0.6 DRM 3.42 5.15.59-1-MANJARO)
    v: 4.6 Mesa 22.2.0-devel (git-a4a15f500c) direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Acer Incorporated
    ALI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Acer Incorporated
    ALI driver: snd_rn_pci_acp3x v: kernel
    alternate: snd_pci_acp3x,snd_pci_acp5x pcie: gen: 3 speed: 8 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Acer Incorporated ALI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  Sound Server-1: ALSA v: k5.15.59-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.56 running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: Lite-On driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 01:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IF-ID-1: tap-easytether state: down mac: <filter>
Bluetooth:
  Device-1: Lite-On Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 1-4:3 chip-ID: 04ca:3802 class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 208.98 GiB (43.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PDP3512B-AA1
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B
    speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: EDFK0S03
    temp: 46.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 208.98 GiB
    (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 608 KiB
    (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 208.98
    GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%) used: 208.98
    GiB (43.8%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A gpu: amdgpu temp: 46.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 376 Uptime: 10h 37m wakeups: 7544 Memory: 14.98 GiB used: 7.31
  GiB (48.8%) Init: systemd v: 251 default: graphical tool: systemctl
  Compilers: gcc: 12.1.1 clang: 14.0.6 Packages: apk: 0 pacman: 1364 lib: 413
  Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: yakuake inxi: 3.3.20

That’s a very bad thing to do.

This is perfectly normal. If you hard-reset the computer, then the operating system cannot properly close any open files, which leaves your filesystem in disarray. Upon rebooting, the system will fsck the filesystem and will attempt to repair damaged files by rolling back the journal.

However, this is just like playing dice, and it may be that the damaged files cannot be repaired, especially if it’s not just the files that were damaged, but the filesystem itself. And given that there was a freeze before you reset the machine, the chances to filesystem damage are quite substantial.

The bottom line is that if your desktop’s configuration files are damaged or unrecoverable, then Plasma will start up with a clean slate, i.e. with the default configuration as it ships from — in this case — the Manjaro developers, and the Manjaro customizations to Plasma are only mildly divergent from the upstream configuration of KDE itself.

1 Like

Try and figure that out instead of just living with it. To try to start troubleshooting, run the following:

journalctl --boot=-1 --priority=3

on the first successful boot immediately after hanging and rebooting it that way.

In addition, because:

…see

Hope you manage!

3 Likes

OK, I’m confused here. This wasn’t an answer to your question in any way. So I removed the mark.

Well, you added a link to a guide with an instruction on what to do when laptop freezes so I could avoid situation in the first place, so it’s a solution.

Very informative, thanks :slight_smile:

No, it doesn’t solve the crash, does it?