Crash - help me isolate the issue with journalctl

apolo234 · 29 October 2024 22:16

Hi, today my computer started crashing several times and I can’t figure out what’s causing it. Here is the journal (journalctl -b -p err --no-pager ). Thanks a lot.

oct 29 16:54:41 arnaud-inspiron74052n1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20240322/dswload2-162)
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240322/psobject-220)
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: amdgpu 0000:03:00.0: amdgpu: Secure display: Generic Failure.
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: scsi 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: scsi 2:0:0:1: Failed to get diagnostic page 0x1
oct 29 16:54:41 arnaud-inspiron74052n1 kernel: scsi 2:0:0:1: Failed to bind enclosure -19
oct 29 16:54:41 arnaud-inspiron74052n1 systemd-udevd[449]: /usr/lib/udev/rules.d/51-trezor.rules:11 Unknown group 'trezord', ignoring.
oct 29 16:54:41 arnaud-inspiron74052n1 systemd-udevd[449]: /usr/lib/udev/rules.d/51-trezor.rules:12 Unknown group 'trezord', ignoring.
oct 29 16:54:41 arnaud-inspiron74052n1 systemd-udevd[449]: /usr/lib/udev/rules.d/51-trezor.rules:15 Unknown group 'trezord', ignoring.
oct 29 16:54:41 arnaud-inspiron74052n1 systemd-udevd[449]: /usr/lib/udev/rules.d/51-trezor.rules:16 Unknown group 'trezord', ignoring.
oct 29 16:54:41 arnaud-inspiron74052n1 systemd-udevd[449]: /usr/lib/udev/rules.d/51-trezor.rules:17 Unknown group 'trezord', ignoring.
oct 29 16:54:43 arnaud-inspiron74052n1 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
oct 29 16:54:43 arnaud-inspiron74052n1 bluetoothd[678]: Failed to set mode: Failed (0x03)
oct 29 16:54:49 arnaud-inspiron74052n1 dbus-broker-launch[803]: Ignoring duplicate name 'org.freedesktop.Akonadi.Control' in service file '/usr/share//dbus-1/services/org.freedesktop.Akonadi.Control.service'
oct 29 16:54:59 arnaud-inspiron74052n1 dbus-broker-launch[898]: Ignoring duplicate name 'org.freedesktop.Akonadi.Control' in service file '/usr/share//dbus-1/services/org.freedesktop.Akonadi.Control.service'
oct 29 16:55:03 arnaud-inspiron74052n1 bluetoothd[678]: Failed to set mode: Failed (0x03)
oct 29 16:55:04 arnaud-inspiron74052n1 bluetoothd[678]: Failed to set mode: Failed (0x03)
oct 29 16:55:11 arnaud-inspiron74052n1 kernel: pcie_mp2_amd 0000:03:00.7: amd_sfh_hid_client_init failed err -95
oct 29 16:55:11 arnaud-inspiron74052n1 kernel: MCE: Killing baloo_file_extr:1608 due to hardware memory corruption fault at 64ba80400378
oct 29 16:55:11 arnaud-inspiron74052n1 kernel: BUG: Bad page map in process baloo_file_extr  pte:b4fffe459f pmd:146963067
oct 29 16:55:11 arnaud-inspiron74052n1 kernel: addr:000064ba80401000 vm_flags:08100073 anon_vma:ffff9ccf07f12af8 mapping:0000000000000000 index:64ba80401
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: file:(null) fault:0x0 mmap:0x0 read_folio:0x0
oct 29 16:55:12 arnaud-inspiron74052n1 systemd-coredump[1995]: [🡕] Process 1608 (baloo_file_extr) of user 1000 dumped core.
                                                               
                                                               Stack trace of thread 1608:
                                                               #0  0x00007c40791e8d9c n/a (libKF6BalooEngine.so.6 + 0x1ed9c)
                                                               #1  0x00007c40791ea2b8 n/a (libKF6BalooEngine.so.6 + 0x202b8)
                                                               #2  0x00007c40791ea9e4 n/a (libKF6BalooEngine.so.6 + 0x209e4)
                                                               #3  0x00007c40791f084f _ZN5Baloo16WriteTransaction15replaceDocumentERKNS_8DocumentE6QFlagsINS_17DocumentOperationEE (libKF6BalooEngine.so.6 + 0x2684f)
                                                               #4  0x000064ba54eb0ea5 n/a (baloo_file_extractor + 0x12ea5)
                                                               #5  0x000064ba54eb1b1d n/a (baloo_file_extractor + 0x13b1d)
                                                               #6  0x00007c4077fa3397 n/a (libQt6Core.so.6 + 0x1a3397)
                                                               #7  0x00007c4077ecf654 n/a (libQt6Core.so.6 + 0xcf654)
                                                               #8  0x00007c4077f8d859 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18d859)
                                                               #9  0x00007c4077f45aa8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x145aa8)
                                                               #10 0x00007c40780c7658 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2c7658)
                                                               #11 0x00007c40781a9fd1 n/a (libQt6Core.so.6 + 0x3a9fd1)
                                                               #12 0x00007c407777d299 n/a (libglib-2.0.so.0 + 0x5d299)
                                                               #13 0x00007c40777dfec7 n/a (libglib-2.0.so.0 + 0xbfec7)
                                                               #14 0x00007c407777c795 g_main_context_iteration (libglib-2.0.so.0 + 0x5c795)
                                                               #15 0x00007c40781a82bd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a82bd)
                                                               #16 0x00007c4077f4ff66 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14ff66)
                                                               #17 0x00007c4077f4a11d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14a11d)
                                                               #18 0x000064ba54ea646d n/a (baloo_file_extractor + 0x846d)
                                                               #19 0x00007c4078e86e08 n/a (libc.so.6 + 0x25e08)
                                                               #20 0x00007c4078e86ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                                               #21 0x000064ba54ea6595 n/a (baloo_file_extractor + 0x8595)
                                                               
                                                               Stack trace of thread 1610:
                                                               #0  0x00007c4078f6c63d __poll (libc.so.6 + 0x10b63d)
                                                               #1  0x00007c4076ab220b n/a (libxcb.so.1 + 0xd20b)
                                                               #2  0x00007c4076ab3f3d xcb_wait_for_event (libxcb.so.1 + 0xef3d)
                                                               #3  0x00007c4073fadc99 n/a (libQt6XcbQpa.so.6 + 0x4ec99)
                                                               #4  0x00007c40780cd237 n/a (libQt6Core.so.6 + 0x2cd237)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1616:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1612:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1613:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1609:
                                                               #0  0x00007c4078f6c63d __poll (libc.so.6 + 0x10b63d)
                                                               #1  0x00007c40777dfe0d n/a (libglib-2.0.so.0 + 0xbfe0d)
                                                               #2  0x00007c407777c795 g_main_context_iteration (libglib-2.0.so.0 + 0x5c795)
                                                               #3  0x00007c40781a82bd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a82bd)
                                                               #4  0x00007c4077f4ff66 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14ff66)
                                                               #5  0x00007c407803d650 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23d650)
                                                               #6  0x00007c4078484f0e n/a (libQt6DBus.so.6 + 0x2df0e)
                                                               #7  0x00007c40780cd237 n/a (libQt6Core.so.6 + 0x2cd237)
                                                               #8  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #9  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1614:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1615:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               
                                                               Stack trace of thread 1611:
                                                               #0  0x00007c4078ef1a19 n/a (libc.so.6 + 0x90a19)
                                                               #1  0x00007c4078ef4479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                               #2  0x00007c40704cecae n/a (libgallium-24.2.4-arch1.0.1.so + 0xcecae)
                                                               #3  0x00007c40704ab6bc n/a (libgallium-24.2.4-arch1.0.1.so + 0xab6bc)
                                                               #4  0x00007c40704cebdd n/a (libgallium-24.2.4-arch1.0.1.so + 0xcebdd)
                                                               #5  0x00007c4078ef539d n/a (libc.so.6 + 0x9439d)
                                                               #6  0x00007c4078f7a49c n/a (libc.so.6 + 0x11949c)
                                                               ELF object binary architecture: AMD x86-64
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: get_swap_device: Bad swap offset entry 3ffffb5000011
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: BUG: Bad page map in process baloo_file:sh0  pte:b4fffe4347 pmd:146963067
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: addr:000064ba80401000 vm_flags:08100073 anon_vma:ffff9ccf07f12af8 mapping:0000000000000000 index:64ba80401
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: file:(null) fault:0x0 mmap:0x0 read_folio:0x0
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: BUG: Bad rss-counter state mm:000000006d58b492 type:MM_ANONPAGES val:2
oct 29 16:55:12 arnaud-inspiron74052n1 kernel: BUG: Bad rss-counter state mm:000000006d58b492 type:MM_SWAPENTS val:-1

soundofthunder · 30 October 2024 02:31

You might try the following commands to see if that helps. Please report any errors from these commands.

balooctl disable
balooctl purge
balooctl enable

Otherwise, this seems likely to be related to a confirmed KDE bug:

See KDE bug report #487628 and Note 959092

Though, if I’m reading it correctly, that should have already been addressed: Merge request #200

How long is it since you performed an update?
Are you using a BTRFS file system?
Are you multi-booting with Windows?
(If so, please check that Fast Startup has not been re-enabled by a recent Windows Update).

Please provide some system information in case there might be other contributing factors:

inxi --admin --verbosity=8 --filter --no-host --width

The following might be a consequence of that bug, or another issue entirely; I’m afraid all I can do is guess:

BG405 · 30 October 2024 03:16

I guess you are using a swap file and the starting block has been moved.

Maybe this will help with a resolution:

There is a recent post on here detailing how to find the offset value; I’m currently looking for it.

apolo234 · 30 October 2024 10:06

Hi, thanks a lot for your answer.
My system was up to date yesterday, this morning I checked again and there were a few updates related to xorg and then the system asked to restart which I did. Then it took forever to restart, it was stuck on the computer brand logo for a while and then switch to a black screen with some lines of text, about the swap file (baloo file). I did not take a screenshot unfortunately. Finally, it allowed me to entered my encryption password and the normal screen to enter my normal password.
When I try to enter balooctl disable, it tries to correct me into balooctl6 disable? Is it correct?
I don’t multiboot with Windows, I only have Manjaro.
I don’t think I’m using a BTFRS file system but I’m using Veracrypt to encrypt my drive.
The issue happened after I hit by mistake the hibernate button yesterday morning (which I never use), so it may have something to do with it. I’m using a swap file for putting my computer to sleep. (since Dell following Microsoft orders got rid of the full sleep mode).
Here is the result for inxi:

System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=5b0aa847-5522-407a-8c14-ff29320ec66d rw quiet
    cryptdevice=UUID=2ac977df-d71b-4806-8688-f922a992e8dc:luks-2ac977df-d71b-4806-8688-f922a992e8dc
    root=/dev/mapper/luks-2ac977df-d71b-4806-8688-f922a992e8dc splash
    resume=/dev/mapper/luks-4f0f459d-133e-41bc-8898-2957e9e6e715
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Convertible System: Dell product: Inspiron 7405 2n1 v: 1.4.0
    serial: <superuser required> Chassis: type: 31 v: 1.4.0
    serial: <superuser required>
  Mobo: Dell model: 0NNDRC v: A00 serial: <superuser required> part-nu: 09E3
    uuid: <superuser required> UEFI: Dell v: 1.4.0 date: 10/26/2020
Battery:
  ID-1: BAT0 charge: 37.0 Wh (100.0%) condition: 37.0/53.0 Wh (69.9%)
    volts: 16.2 min: 15.0 model: SMP-ATL3.56 DELL 9077G0C type: Li-poly
    serial: <filter> status: full
  Device-1: hid-0018:04F3:2A82.0006-battery model: 04F31234:00 04F3:2A82
    serial: N/A charge: N/A status: N/A
Memory:
  System RAM: total: 16 GiB available: 15 GiB used: 4.65 GiB (31.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 1 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-B DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 3200 MT/s volts: note: check curr: 1
    min: 1 max: 1 width (bits): data: 64 total: 64 manufacturer: 802C0000802C
    part-no: 8ATF2G64HZ-3G2E2 firmware: 8ATF2G64HZ-3G2E2 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP
    arch: Zen 2 gen: 2 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x8600104
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 smt: <unsupported> cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 1459 min/max: 1400/2000 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1459 2: 1459 3: 1459
    4: 1459 5: 1459 6: 1459 7: 1459 8: 1459 bogomips: 31948
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibrs ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sha_ni skinit smap smca smep ssbd sse sse2 sse4_1
    sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext tsc
    tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall
    wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow mitigation: SMT disabled
  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: Retpolines; IBPB: conditional; STIBP:
    disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir [Radeon Vega Series /
    Radeon Mobile Series] vendor: Dell driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: HDMI-A-1,eDP-1 empty: DP-1 bus-ID: 03:00.0
    chip-ID: 1002:1636 class-ID: 0300 temp: 71.0 C
  Device-2: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2.1.2:5
    chip-ID: 046d:085c class-ID: 0102 serial: <filter>
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2:2 chip-ID: 0c45:671b
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
    s-diag: 1245mm (49.01") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: Gigabyte G27Q serial: <filter> built: 2023
    res: 2560x1440 dpi: 108 gamma: 1.2 chroma: red: x: 0.678 y: 0.314 green:
    x: 0.278 y: 0.667 blue: x: 0.137 y: 0.039 white: x: 0.314 y: 0.329
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
    modes: 2560x1440, 2560x1080, 1920x1200, 1920x1080, 1600x1200, 1680x1050,
    1400x1050, 1280x1024, 1440x900, 1280x960, 1280x800, 1152x864, 1280x720,
    1440x576, 1024x768, 832x624, 800x600, 720x576, 720x480, 640x480, 720x400
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 96 2: parse_edid:
    unhandled CEA mode 97 3: parse_edid: unhandled CEA mode 89
  Monitor-2: eDP-1 model: ChiMei InnoLux 0x14d4 built: 2017 res: 1920x1080
    dpi: 158 gamma: 1.2 chroma: red: x: 0.592 y: 0.349 green: x: 0.329 y: 0.557
    blue: x: 0.153 y: 0.118 white: x: 0.314 y: 0.329
    size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9
    modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x800, 1280x720,
    1024x768, 800x600, 640x480
  EDID-Warnings: 1: parse_edid: unknown flag 0
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir
    LLVM 18.1.8 DRM 3.57 6.10.13-3-MANJARO) device-ID: 1002:1636
    memory: 500 MiB unified: no
  API: Vulkan v: 1.3.295 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 24.2.4-arch1.0.1
    device-ID: 1002:1636 surfaces: xcb,xlib
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition
    Audio vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor
    vendor: Dell driver: snd_rn_pci_acp3x v: kernel alternate: snd_pci_acp3x,
    snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: Logitech Logitech H570e Stereo
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-2.1.1:4 chip-ID: 046d:0a56 class-ID: 0300
    serial: <filter>
  Device-5: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2.1.2:5
    chip-ID: 046d:085c class-ID: 0102 serial: <filter>
  API: ALSA v: k6.10.13-3-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.5 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:3 chip-ID: 8087:0029
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: luks-2ac977df-d71b-4806-8688-f922a992e8dc maj-min: 254:0
    type: LUKS dm: dm-0 size: 460.14 GiB
  Components:
  p-1: nvme0n1p2 maj-min: 259:2 size: 460.15 GiB
  Device-2: luks-4f0f459d-133e-41bc-8898-2957e9e6e715 maj-min: 254:1
    type: LUKS dm: dm-1 size: 16.49 GiB
  Components:
  p-1: nvme0n1p3 maj-min: 259:3 size: 16.5 GiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 5.01 TiB used: 406.17 GiB (7.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: BC511 NVMe 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 11004101 temp: 61.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD50NDZW-11A8JS1
    size: 4.55 TiB block-size: physical: 4096 B logical: 512 B type: USB rev: 3.1
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 4008 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 460.14 GiB size: 451.85 GiB (98.20%)
    used: 402.33 GiB (89.0%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2ac977df-d71b-4806-8688-f922a992e8dc label: N/A
    uuid: 5b0aa847-5522-407a-8c14-ff29320ec66d
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 460 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 77A0-411F
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 16.49 GiB used: 3.83 GiB (23.2%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-4f0f459d-133e-41bc-8898-2957e9e6e715 label: swap
    uuid: 56e8b51c-8e26-498e-a2b4-21464ab8e9d9
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 4.55 TiB fs: <superuser required>
    label: N/A uuid: N/A
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-2:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Hub-3: 1-2.1:3 info: Realtek RTS5411 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 1-2.1.1:4 info: Logitech Logitech H570e Stereo type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 046d:0a56 class-ID: 0300 serial: <filter>
  Device-2: 1-2.1.2:5 info: Logitech C922 Pro Stream Webcam type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 046d:085c class-ID: 0102 serial: <filter>
  Device-3: 1-2.1.3:6 info: Maxxter Telink Wireless Receiver
    type: mouse,keyboard driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 50mA
    chip-ID: 248a:8367 class-ID: 0301
  Device-4: 1-2.1.4:7 info: Maxxter Wireless Receiver type: mouse,keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 50mA chip-ID: 248a:8327 class-ID: 0301
  Hub-4: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 2-2:2 info: Realtek Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-6: 2-2.1:3 info: Realtek Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 0bda:0411
    class-ID: 0900
  Hub-7: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-2:2 info: Microdia Integrated_Webcam_HD type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 500mA chip-ID: 0c45:671b class-ID: 0e02
  Device-2: 3-3:3 info: Intel AX200 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0029 class-ID: e001
  Device-3: 3-4:4 info: Shenzhen Goodix FingerPrint type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 27c6:538d class-ID: ff00
  Hub-8: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 4-1:2 info: Western Digital My Passport 2627 type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.1 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 896mA chip-ID: 1058:2627 class-ID: 0806
    serial: <filter>
Sensors:
  System Temperatures: cpu: 66.0 C mobo: 49.0 C gpu: amdgpu temp: 72.0 C
  Fan Speeds (rpm): cpu: 3777
Repos:
  Packages: 1663 pm: pacman pkgs: 1636 libs: 407 tools: pamac pm: flatpak
    pkgs: 27
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    4: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    5: http://manjaro.grena.ge/stable/$repo/$arch
    6: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 332
  1: cpu: 40.1% command: baloo_file_extractor pid: 1618 mem: 253.8 MiB (1.6%)
  2: cpu: 23.2% command: vivaldi-bin pid: 1838 mem: 352.5 MiB (2.2%)
  3: cpu: 16.4% command: vivaldi-bin pid: 1709 mem: 286.4 MiB (1.8%)
  4: cpu: 9.2% command: konsole pid: 2661 mem: 231.4 MiB (1.5%)
  5: cpu: 6.5% command: vivaldi-bin pid: 1899 mem: 288.0 MiB (1.8%)
  Memory top: 5 of 332
  1: mem: 452.5 MiB (2.9%) command: vivaldi-bin pid: 1646 cpu: 5.9%
  2: mem: 421.8 MiB (2.7%) command: plasmashell pid: 1086 cpu: 0.5%
  3: mem: 356.1 MiB (2.3%) command: vivaldi-bin pid: 2087 cpu: 1.9%
  4: mem: 352.5 MiB (2.2%) command: vivaldi-bin pid: 1838 cpu: 23.2%
  5: mem: 305.8 MiB (1.9%) command: vivaldi-bin pid: 2055 cpu: 1.7%
Info:
  Processes: 332 Power: uptime: 15m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 5.98 GiB services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 256 default: graphical tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.36

cscs · 30 October 2024 10:16

Its there;

[HowTo] Configure hibernation with a swap file

Find $DEVICE UUID and swap file offset

Instructions

The most reliable address for a device is the UUID.
To find the UUID of your devices/partitions you may use a command such as blkid.
When setting resume=$DEVICE using a UUID the option should appear as resume=UUID=$UUID.
And when using a swap file the UUID of the device or partition containing the swap file should be used.

Find UUID

Here we will assume it is on the same root / device.

Execute:
findmnt / -o UUID
Find offset

For btrfs:
sudo btrfs inspect-internal map-swapfile -r /swapfile
For all other filesystems:
Execute:
sudo filefrag -v /swapfile | awk '$1=="0:" {print substr($4, 1, length($4)-2)}'

Nachlese · 30 October 2024 11:04

He has got a swap partition - just as the root partition within the encrypted container.
Not a swap file.
No need for resume_offset=

I’m not capable right now to solve the puzzle with the drives UUID’s vs the mapped UUID’s due to the encryption.

Probably not needed - either hardware (memory) or baloo.

I’d boot from USB and do a file system check anyway.

Not sure about the differences in opening the container in order to do the fsck because:

@apolo234
if you did use the Calamares installer, the disk is unlikely to be encrypted using Veracrypt
and everything else says: Luks

soundofthunder · 30 October 2024 13:41

So, it looks like the first problem resulted from the update. Did you check Known Issues and Solutions in the Stable Update Announcement?

Just a reminder that kernel 6.10.x has reached EOL; nothing to be concerned with right now though.

That is unfortunate;
the messages might have given additional hints.

I’m not familiar with using encryption on Manjaro;
If the issue is in any way related to an encrypted filesystem, I’ll have to defer to others who might be more able to offer advice.

Yes, that should be fine (the 6 denotes the Qt6 version for Plasma6).

Yes, from the timing I dare say it’s a foregone conclusion; this on top of a possible issue during update.

It’s also possible you have damaged RAM. If you search the forum you should find instructions on how to run a memtest.

Did your system recover properly from hibernation, or did you do a hard reset? If indeed you have never used the hibernate button; are you certain it worked properly before; have you ever hibernated?

If you have not, then it’s possible your swap was already mis-configured and this lead to the initial crash; when the damage was done.

According to your system information you are using zswap together with a swap partition within a luks container.

Again, I’m unable to offer advice here; only making observations.

I notice also / (root) hasn’t much free space; this may have also contributed to the issue you’re now facing.

None of this will likely lead to a solution, but may be food for thought. And another thought; if the problem isn’t hardware, a full reinstallation might be the fastest way back to a stable Manjaro system.

But first, wait and see what others may have to add.

I can only wish you luck.

I don’t think @BG405 had the benefit of system information when he posted.

BG405 · 30 October 2024 16:58

Thanks, I was getting a bit too tired to look properly!

apolo234 · 31 October 2024 00:07

Thanks a lot for all the help. It’s really useful. I have not had any issues today so I think maybe after the last reboot, the system was reconfigured automatically and the issue got fixed.
I never used the hibernate function before and the system froze so I had to do a hard reset, that probably messed up the swap file.
Concerning the balootctl6 disable, I got no error. However, for balooctl6 purge, I got an error saying ‘failed to stop’. And obviously, for blooctl6 enable, I got a message saying ‘file indexer already running’.
Should I be worried for the stability of my system? Thanks a lot.

soundofthunder · 31 October 2024 01:13

You should switch kernels soon. As 6.10 has reached EOL, it will likely disappear from the repo’s without much ceremony. Again, I suggest 6.6 (LTS) or 6.12 (LTS) [when it’s released].

Updates can fail to complete for many reasons;

If you look at the Update Announcement thread (before performing an update) you will see a list near the top of what is to be updated.

A rule of thumb is that if you see anything major will be updated; like, anything related to your DE, the X server (X11) or Wayland, for example; always perform that update from outside of the GUI;

Reboot; and once you’re at the SDDM login screen, open a TTY and perform the update there, without loading the GUI. This can help avoid many potential issues. In fact, it’s a safer method to use, generally.

A handy tutorial if an update fails to complete due to your computer crashing:

Recovering from an Interrupted Update/Upgrade

Please see my comments my post (below) concerning Baloo.

Regarding stability, I’d suggest paying particular attention to system maintenance generally; perhaps the Manjaro Wiki might help fill in a few gaps in knowledge if needed.

We can’t monitor your system for you, but if you have other issues you can always start a new support thread.

Cheers.

Takakage · 31 October 2024 01:48

Citation needed? My understanding is that kde-baloo.service runs as a user unit, and that all relevant files are under ~/.local/share/baloo/, so I wouldn’t think that sudo would be necessary or desired.

soundofthunder · 31 October 2024 01:50

Observation, more than anything.

The purge fails (to stop) without it; which the OP likely discovered.

Unless this is a bug; I don’t know that this behaviour would be by design.

I’ve given this some further thought;

The balooctl6 purge command should clear the Baloo index and stop monitoring. Yet, having issued the balooctl6 disable command the indexing service is disabled, and any background processes are already terminated; including the Baloo daemon itself.

So, if one runs balooctl6 disable before balooctl6 purge then the purge process; the part that stops monitoring; subsequently fails because monitoring has already been stopped. This must then generate a warning rather than the error it might seem to be; presumedly after a timeout.

Regarding the use of sudo with the balooctl6 purge command;

While sudo is technically not needed, it did allow the purge to complete without a warning. The main complication seems a result of having run balooctl6 disable beforehand; though I have noticed disabling Baloo first being recommended in past threads.

As I understand it, running sudo balooctl6 purge should have no detrimental affect. The purge process removes the index database files and metadata in ~/.local/share/baloo/, but no configuration files are impacted; no files are created or written to; associated caches and logs are deleted; and no directories are created until indexing is again enabled.

To the point;

If balooctl6 disable is not issued prior to balooctl6 purge then the purge process completes as expected (without resorting to sudo). Using balooctl6 suspend instead looks to be a viable alternative, though I am uncertain of the fundamental difference. One presumes that processes are terminated and the service is left in situ.

Amending my previous advice, the better approach might be;

balooctl6 suspend
balooctl6 purge
balooctl6 enable

…or…

balooctl6 purge

…followed by a reboot.

The Baloo indexing service will commence immediately after a reboot if not enabled manually (performance may be sluggish for a little while).

Note:- There is a KDE bug #437176 that causes warnings to be printed to screen; I’m uncertain whether this has been addressed or applicable for Qt6.

apolo234 · 31 October 2024 10:22

sorry I completely forgot to use ‘sudo’. Thanks for the reminder.

soundofthunder · 31 October 2024 10:28

If you reread, you should see that quite the opposite was inferred.

Do not use sudo for the balooctl6 purge command;

Instead, this is better:

balooctl6 suspend
balooctl6 purge

and then reboot when the purge finishes and indexing will again be enabled.

Cheers.

apolo234 · 13 November 2024 20:01

Hi, I did not have time to look into it, and I should have, because yesterday, my computer completely crashed and displayed the following. I reinstalled Manjaro (and I struggled, the installation would freeze regularly and the installer would not even start). Finally I was able to reinstall manjaro KDE plasma. But a few hours after the same message reappeared. I think the drive might be damaged.

I complied with the instructions and ran fsck (see 2nd image),

which got me back in the system, but later on the system froze again and I got the initial message again. What should I do? Thanks a lot.

soundofthunder · 13 November 2024 20:45

How old is the Manjaro Installer ISO that you are using?
The latest available is usually preferable.

Possibly reinstall again, only first, install gparted to the Live environment. Create a new GPT partition table (assuming you are booting as UEFI) and manually create the partitions you need.

Shutdown (cleanly) for a few minutes, and then boot to the Manjaro Installer and install Manjaro KDE; use the manual partitioning method and re-use the new partitions created in gparted; naturally, configure them to your preference.

Note 1:- Disconnect any unnecessary disks temporarily.
Note 2:- Consider not choosing encryption during install (You can configure it manually later when the machine is working as expected)

I don’t know if this will solve anything for you, especially if the disk happens to be damaged, but on the chance that it is only filesystem damage, starting with a fresh slate (the new partition table) might improve things. If not, 1TB SSD’s are generally affordable and faster, so perhaps that might be a consideration.

Regards.

apolo234 · 13 November 2024 23:14

I’m using the latest Manjaro Installer ISO. I did reinstall without the encryption to see if it helped. It did help avoiding the installer to stop midway and complete the installer but unfortunately it did not help with the stability of the system.
I will try the manual partitioning and see what happens. I might indeed in the end upgrade my SSD to 1TB to solve the issue. Thanks a lot for the pointers.

apolo234 · 14 November 2024 23:39

So I ran memtest to check the memory and it came back perfectly fine. I also ran nvme smart-log as well as the smart status in KDE partition manager and both came back totally fine. (I tried smartctl but for some reason, the smart info were missing).
Regarding your previous recommendation, how should I choose to partition the drive? I never did it before so I’m a bit at a loss.
Also, I can never cleanly shut down the computer, I get a black screen with the mouse pointer but it does not shut down (even shutting down with the Manjaro installer ISO).
Thanks a lot

soundofthunder · 15 November 2024 06:58

I don’t recommend anything. Any suggestions given are only thoughts that might help discover a possible workaround.

That being the case, please ignore my previous suggestion to use gparted and the manual partitioning method. Use whichever partitioning method you’re most comfortable with.

The suggestion was mainly to workaround possible issues (and bugs) with the KDE partitioner that I’ve seen mentioned in recent times.

Is this only since reinstalling, of have you experienced this even before the crashes mentioned?

apolo234 · 15 November 2024 10:01

Thanks. The issue with shutting down the computer appeared since the crash and the different reinstall. I tried to contact Dell support and it’s pretty much non existent where I live (in South America)