Can't open Manjaro settings manager

Aelkatraz · 30 August 2021 21:59

I just updated to 5.13 after having my PC not in use for a few months.

Prior to updating my settings would not open (I figured since I was on 5.10 and it was no longer supported). However even after the update this problem is persisting. Not only in my setting manager not opening (unless I use terminal), but KDE connect is also refusing to open.

I am unsure if the problem are related or separate.

I should note that I had to run version 5.4 (LTS) in order to update to 5.13 since while in 5.10 it would always fail to update.

Thanks

papajoke · 30 August 2021 22:25

can you run manjaro-settings-manager in terminal for view error (if exists…)

never good… some .pacnew to merge ?

Aelkatraz · 30 August 2021 23:03

Yea I was away for a bit so PC stayed dormant.

> [alek@OldReliable ~]$ sudo manjaro-settings-manager
> [sudo] password for alek: 
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'

this is what I get, and the app opens no problem

papajoke · 30 August 2021 23:20

is good this sudo ? but we not use sudo for load this app so output without is best
without sudo, this app use polkit … (you not have .pacnew with polkit package ?)

 LANG=C pacman -Qii $(pacman -Qsq polkit) | grep MODIFIED

Aelkatraz · 30 August 2021 23:23

if I do not use sudo I get this

> [alek@OldReliable ~]$ manjaro-settings-manager
> Segmentation fault (core dumped)
> [alek@OldReliable ~]$

I use Pacman for all my apps

I get this:

> [alek@OldReliable ~]$ LANG=C pacman -Qii $(pacman -Qsq polkit) | grep MODIFIED
> UNMODIFIED	/etc/pam.d/polkit-1
> [alek@OldReliable ~]$

scachemaille · 31 August 2021 11:10

Is your system actually up to date…
Or it’s just the kernel.
Your post is not clear about that.

Aelkatraz · 31 August 2021 18:56

All my apps are updated, and I tried Sudo pacman Syyu and tells me there is nothing to do.
I even tried resetting my xfce4 back to default and that did not work.

Aelkatraz · 31 August 2021 21:35

There seems to have a bigger problem behind this, since it’s not only my settings manager not working.
But I tried to install Virtualbox and that will not open either, so I tried to do the same on my laptop (running same kernel) and it worked right away.

So I am thinking I have something else broken but not sure where to start looking.
Any help would be much appreciated

System info:

> [alek@OldReliable ~]$ neofetch
> ██████████████████  ████████   alek@OldReliable 
> ██████████████████  ████████   ---------------- 
> ██████████████████  ████████   OS: Manjaro Linux x86_64 
> ██████████████████  ████████   Kernel: 5.13.12-1-MANJARO 
> ████████            ████████   Uptime: 21 mins 
> ████████  ████████  ████████   Packages: 1365 (pacman) 
> ████████  ████████  ████████   Shell: bash 5.1.8 
> ████████  ████████  ████████   Resolution: 1920x1080 
> ████████  ████████  ████████   DE: Xfce 4.16 
> ████████  ████████  ████████   WM: Xfwm4 
> ████████  ████████  ████████   WM Theme: Matcha-sea 
> ████████  ████████  ████████   Theme: Matcha-sea [GTK2], Adwaita [GTK3] 
> ████████  ████████  ████████   Icons: Papirus-Maia [GTK2], Adwaita [GTK3] 
> ████████  ████████  ████████   Terminal: xfce4-terminal 
>                                Terminal Font: Monospace 12 
>                                CPU: Intel i7-3820 (8) @ 5.700GHz 
>                                GPU: NVIDIA GeForce GTX 980 
>                                Memory: 2674MiB / 32084MiB

Apps with known issues:

> [alek@OldReliable ~]$ kdeconnect-app
> Segmentation fault (core dumped)
> [alek@OldReliable ~]$ manjaro-settings-manager
> Segmentation fault (core dumped)
> [alek@OldReliable ~]$ virtualbox
> WARNING: The vboxdrv kernel module is not loaded. Either there is no module
>          available for the current kernel (5.13.12-1-MANJARO) or it failed to
>          load. Please recompile the kernel module and install it by
> 
>            sudo /sbin/vboxconfig
> 
>          You will not be able to start VMs until this problem is fixed.
> Segmentation fault (core dumped)
> [alek@OldReliable ~]$ sudo /sbin/vboxconfig
> [sudo] password for alek: 
> sudo: /sbin/vboxconfig: command not found

Current kernels on machine:

> [alek@OldReliable ~]$ mhwd-kernel -li
> Currently running: 5.13.12-1-MANJARO (linux513)
> The following kernels are installed in your system:
>    * linux513
>    * linux54

El_Brujo · 1 September 2021 04:09

I’d try to reproduce the issues opening up your applications again.
Once you have done that, I’d look up for errors in the journal on a terminal as per below and please share the output with us:

sudo journalctl -b 0 -p err

Aelkatraz · 1 September 2021 04:12

Here is what I got,

> [alek@OldReliable ~]$ sudo journalctl -b 0 -p err
> [sudo] password for alek: 
> -- Journal begins at Tue 2021-02-09 08:42:23 MST, ends at Tue 2021-08-31 22:16:>
> Aug 31 15:54:12 OldReliable kernel: usb 1-1.6: device descriptor read/64, error>
> Aug 31 15:54:12 OldReliable kernel: 
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:13 OldReliable systemd-udevd[315]: could not read from '/sys/modul>
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device wit>
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel >
> lines 1-23...skipping...
> -- Journal begins at Tue 2021-02-09 08:42:23 MST, ends at Tue 2021-08-31 22:16:29 MDT. --
> Aug 31 15:54:12 OldReliable kernel: usb 1-1.6: device descriptor read/64, error -32
> Aug 31 15:54:12 OldReliable kernel: 
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:12 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable systemd-udevd[315]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Couldn't find mci handler
> Aug 31 15:54:13 OldReliable kernel: EDAC sbridge: Failed to register device with error -19.
> Aug 31 15:54:22 OldReliable lightdm[1356]: gkr-pam: unable to locate daemon control file
> Aug 31 15:54:24 OldReliable wpa_supplicant[776]: bgscan simple: Failed to enable signal strength monitoring
> Aug 31 15:54:25 OldReliable systemd-coredump[1623]: [🡕] Process 1528 (msm_notifier) of user 1000 dumped core.
>                                                     
>                                                     Stack trace of thread 1528:
>                                                     #0  0x00007fdc1330c928 __tzstring (libc.so.6 + 0xbc928)
>                                                     #1  0x00007fdc1330dfe9 __tzfile_compute (libc.so.6 + 0xbdfe9)
>                                                     #2  0x00007fdc1330ce66 __tz_convert (libc.so.6 + 0xbce66)
>                                                     #3  0x00007fdc1330b341 ranged_convert (libc.so.6 + 0xbb341)
>                                                     #4  0x00007fdc1330b691 __mktime_internal (libc.so.6 + 0xbb691)
>                                                     #5  0x00007fdc136f6889 _Z7qMkTimeP2tm (libQt5Core.so.5 + 0xc2889)
>                                                     #6  0x00007fdc137d0a1b n/a (libQt5Core.so.5 + 0x19ca1b)
>                                                     #7  0x00007fdc137d1058 n/a (libQt5Core.so.5 + 0x19d058)
>                                                     #8  0x00007fdc137d1160 n/a (libQt5Core.so.5 + 0x19d160)
>                                                     #9  0x00007fdc137d1650 n/a (libQt5Core.so.5 + 0x19d650)
>                                                     #10 0x00007fdc137d3996 _ZN9QDateTime18setMSecsSinceEpochEx (libQt5Core.so.5 + 0x19f996)
>                                                     #11 0x00007fdc137d5ce5 _ZN9QDateTime19fromMSecsSinceEpochExN2Qt8TimeSpecEi (libQt5Core.so.5 + 0x1a1ce5)
>                                                     #12 0x00007fdc137d6437 _ZN9QDateTime19fromMSecsSinceEpochEx (libQt5Core.so.5 + 0x1a2437)
>                                                     #13 0x00007fdc1381caf4 _ZNK9QFileInfo8fileTimeEN11QFileDevice8FileTimeE (libQt5Core.so.5 + 0x1e8af4)
>                                                     #14 0x00007fdc1381ccc8 _ZNK9QFileInfo12lastModifiedEv (libQt5Core.so.5 + 0x1e8cc8)
>                                                     #15 0x00007fdc13877ad2 n/a (libQt5Core.so.5 + 0x243ad2)
>                                                     #16 0x00007fdc13877c5c n/a (libQt5Core.so.5 + 0x243c5c)

Fabby · 1 September 2021 11:21

Does this also happen when:

you log in to a TTY
create a new user there (E.G. aelkatraz2)
log into that user?

Aelkatraz · 1 September 2021 15:43

I created a new user, but I am unable to login the new user.
I have a none admin user from prior and it also has the same issue.

Fabby · 1 September 2021 15:46

Something else is wrong with your system so

Please read this:
[HowTo] Provide System Information
and press the three dots … below your post and press the to give us more information so we can see what’s really going on.
Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

P.S. If you want to notify me that you did provide this information, please this message and I’ll come back and have another look.

Aelkatraz · 1 September 2021 16:04

Here is the inxi output

> [alek@OldReliable ~]$ inxi --admin --verbosity=7 --filter --no-host --width
> System:
>   Kernel: 5.13.12-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
>   parameters: BOOT_IMAGE=/boot/vmlinuz-5.13-x86_64 
>   root=UUID=8aec7e29-1a4c-45ff-983f-e12ead7f6d83 rw quiet apparmor=1 
>   security=apparmor resume=UUID=4c0eb61c-ef43-4e03-b2ee-106257b99d73 
>   udev.log_priority=3 
>   Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
>   dm: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux 
> Machine:
>   Type: Desktop Mobo: ASUSTeK model: RAMPAGE IV EXTREME v: Rev 1.xx 
>   serial: <filter> BIOS: American Megatrends v: 0604 date: 10/28/2011 
> Battery:
>   Message: No system battery data found. Is one present? 
> Memory:
>   RAM: total: 31.33 GiB used: 2.88 GiB (9.2%) 
>   RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
> CPU:
>   Info: Quad Core model: Intel Core i7-3820 bits: 64 type: MT MCP 
>   arch: Sandy Bridge family: 6 model-id: 2D (45) stepping: 7 microcode: 71A 
>   cache: L2: 10 MiB bogomips: 57483 
>   Speed: 1198 MHz min/max: 1200/5700 MHz Core speeds (MHz): 1: 1198 2: 1233 
>   3: 1197 4: 2413 5: 2867 6: 2107 7: 1198 8: 2093 
>   Flags: acpi aes aperfmperf apic arat arch_perfmon avx bts clflush cmov 
>   constant_tsc cpuid cx16 cx8 dca de ds_cpl dtes64 dtherm dts epb ept est 
>   flexpriority flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce md_clear 
>   mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm 
>   pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdtscp rep_good sep ss 
>   ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc 
>   tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr 
>   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 and seccomp 
>   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 status: Not affected 
>   Type: tsx_async_abort status: Not affected 
> Graphics:
>   Device-1: NVIDIA GM204 [GeForce GTX 980] vendor: ASUSTeK driver: nvidia 
>   v: 470.63.01 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 
>   chip-ID: 10de:13c0 class-ID: 0300 
>   Display: x11 server: X.Org 1.20.13 compositor: xfwm4 v: 4.16.1 driver: 
>   loaded: nvidia display-ID: :0.0 screens: 1 
>   Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.9x11.9") 
>   s-diag: 610mm (24") 
>   Monitor-1: DP-0 res: 1920x1080 dpi: 92 size: 531x299mm (20.9x11.8") 
>   diag: 609mm (24") 
>   OpenGL: renderer: NVIDIA GeForce GTX 980/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01 
>   direct render: Yes 
> Audio:
>   Device-1: Intel C600/X79 series High Definition Audio vendor: ASUSTeK 
>   driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1d20 
>   class-ID: 0403 
>   Device-2: NVIDIA GM204 High Definition Audio vendor: ASUSTeK 
>   driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:0fbb 
>   class-ID: 0403 
>   Device-3: Corsair VOID Wireless Gaming Dongle type: USB 
>   driver: hid-generic,snd-usb-audio,usbhid bus-ID: 9-2:2 chip-ID: 1b1c:1b27 
>   class-ID: 0300 
>   Sound Server-1: ALSA v: k5.13.12-1-MANJARO running: yes 
>   Sound Server-2: JACK v: 1.9.19 running: no 
>   Sound Server-3: PulseAudio v: 15.0 running: yes 
>   Sound Server-4: PipeWire v: 0.3.33 running: no 
> Network:
>   Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe 
>   driver: e1000e v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1503 
>   class-ID: 0200 
>   IF: eno1 state: down mac: <filter> 
>   Device-2: Broadcom BCM4352 802.11ac Wireless Network Adapter vendor: ASUSTeK 
>   driver: wl v: kernel modules: bcma port: e000 bus-ID: 05:00.0 
>   chip-ID: 14e4:43b1 class-ID: 0280 
>   IF: wlp5s0 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 
>   WAN IP: <filter> 
> Bluetooth:
>   Device-1: ASUSTek Bluetooth Adapter type: USB driver: btusb v: 0.8 
>   bus-ID: 1-1.6:3 chip-ID: 0b05:179c class-ID: e001 
>   Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running 
>   rfk-block: hardware: no software: yes address: see --recommends 
> Logical:
>   Message: No logical block device data found. 
> RAID:
>   Message: No RAID data found. 
> Drives:
>   Local Storage: total: 2.5 TiB used: 158.64 GiB (6.2%) 
>   SMART Message: Required tool smartctl not installed. Check --recommends 
>   ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HDT725050VLA360 
>   size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
>   type: N/A serial: <filter> rev: A7BA scheme: GPT 
>   ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital 
>   model: WDS250G2B0A-00SM50 size: 232.89 GiB block-size: physical: 512 B 
>   logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 20WD 
>   scheme: MBR 
>   ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD20EZAZ-00GGJB0 
>   size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
>   type: HDD rpm: 5400 serial: <filter> rev: 0A80 
>   Message: No optical or floppy data found. 
> Partition:
>   ID-1: / raw-size: 224.08 GiB size: 219.57 GiB (97.98%) 
>   used: 33.97 GiB (15.5%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: N/A 
>   uuid: 8aec7e29-1a4c-45ff-983f-e12ead7f6d83 
>   ID-2: /run/media/Steam raw-size: 1.82 TiB size: 1.79 TiB (98.37%) 
>   used: 124.68 GiB (6.8%) fs: ext4 dev: /dev/sdc maj-min: 8:32 
>   label: Game Drive uuid: dc9e34ab-e9f3-4aa9-b52e-aab40b45d433 
> Swap:
>   Kernel: swappiness: 60 (default) cache-pressure: 100 (default) 
>   ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2 
>   dev: /dev/sdb2 maj-min: 8:18 label: N/A 
>   uuid: 4c0eb61c-ef43-4e03-b2ee-106257b99d73 
> Unmounted:
>   ID-1: /dev/sda1 maj-min: 8:1 size: 74.51 GiB fs: ext4 label: Timeshift 
>   uuid: f6c4527d-1a44-4699-8df0-65f3e7e0f4dc 
> USB:
>   Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
>   Device-1: 1-1.6:3 info: ASUSTek Bluetooth Adapter type: Bluetooth 
>   driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA 
>   chip-ID: 0b05:179c class-ID: e001 
>   Hub-3: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
>   Device-1: 2-1.1:3 info: Corsair Gaming M65 Pro RGB Mouse type: Mouse,HID 
>   driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s 
>   power: 300mA chip-ID: 1b1c:1b2e class-ID: 0300 serial: <filter> 
>   Device-2: 2-1.2:4 info: Logitech G710 Gaming Keyboard type: Keyboard,HID 
>   driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s 
>   power: 400mA chip-ID: 046d:c24d class-ID: 0300 
>   Hub-5: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Hub-6: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s 
>   chip-ID: 1d6b:0003 class-ID: 0900 
>   Hub-7: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Hub-8: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s 
>   chip-ID: 1d6b:0003 class-ID: 0900 
>   Hub-9: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Hub-10: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s 
>   chip-ID: 1d6b:0003 class-ID: 0900 
>   Hub-11: 9-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
>   speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
>   Device-1: 9-2:2 info: Corsair VOID Wireless Gaming Dongle type: Audio,HID 
>   driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 
>   speed: 12 Mb/s power: 100mA chip-ID: 1b1c:1b27 class-ID: 0300 
>   Hub-12: 10-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 
>   speed: 5 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 
> Sensors:
>   System Temperatures: cpu: 29.0 C mobo: N/A gpu: nvidia temp: 46 C 
>   Fan Speeds (RPM): N/A gpu: nvidia fan: 3% 
> Info:
>   Processes: 280 Uptime: 3m wakeups: 0 Init: systemd v: 248 tool: systemctl 
>   Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1374 lib: 422 
>   flatpak: 0 Shell: Bash v: 5.1.8 running-in: xfce4-terminal inxi: 3.3.06

Do you require any other logs?

Fabby · 1 September 2021 17:02

That all looks good.

Can you:

reboot
Log on

execute:

mv ~/.config/manjaro/manjaro-settings-manager.conf ~/.config/manjaro/manjaro-settings-manager.conf_bak

Execute:
```
manjaro-settings-manager
```

What does that do?

Aelkatraz · 1 September 2021 17:10

first attempt

> [alek@OldReliable ~]$ mv ~/.config/manjaro/manjaro-settings-manager.conf ~/.config/manjaro/manjaro-settings-manager.conf _bak
> mv: target '_bak' is not a directory

this I tried with removing the space in front of _bak

> [alek@OldReliable ~]$ mv ~/.config/manjaro/manjaro-settings-manager.conf ~/.config/manjaro/manjaro-settings-manager.conf_bak
> mv: cannot stat '/home/alek/.config/manjaro/manjaro-settings-manager.conf': No such file or directory
> [alek@OldReliable ~]$

and I still get the Segmentation fault (core dumped) error if I try to execute manjaro-settings-manager

I also attempted the commands in the 5.4 kernel I have with the same errors earlier today.

Fabby · 1 September 2021 17:21

Sorry! Typo!

Also: I’m all out of fresh ideas as I’m on KDE, so that’s where my knowledge ends…

Aelkatraz · 1 September 2021 18:13

Is there a way to find the log or route cause of these Segmentation fault (core dumped) in order to fix them.

or

Is there a way to reinstall the kernel(s) or GRUB to patch the errors without losing my data?

El_Brujo · 1 September 2021 18:53

In my opinion, the core dumps might be caused by a few reasons, among them:

Faulty hardware.
Corrupted software (e.g. libraries, kernel modules, etc.).

I’d say, rule out your hardware first. Some things that come up in my mind right now:

Check your memory. You may have a faulty memory module or just the ECC settings disabled on your BIOS, according to the journal output provided. Look up on how to do a memtest for this. There are other threads around discussing that.
Check your system storage. Boot from Live media and make sure your system partitions are unmounted. Then run a filesystem check on them. For more information on how to do this, on a terminal check out the manual pages for lsblk and fsck :

man lsblk
man fsck

Hope that helps!

alven · 2 September 2021 05:28

May be to try to re-install all packages also?