toast
4 June 2025 16:16
1
Every time I try to open up the search settings the whole settings app force closes instantly.
See the picture below. As soon as I click on that button the window vanishes.
Summary
System information below.
Hope someone can advise. Sorry I have not supplied specific error messages. I lack technical skill. I wanted to load gnome settings from a terminal so I could see the error messages generated, but thus far have not found what it’s name in the system is.
Generated on 2025-06-04 17:12:1749053555
#################### inxi -Fxzc0 ########################
System:
Kernel: 6.14.6-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
Desktop: GNOME v: 48.1 Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MPG X570S CARBON MAX WIFI (MS-7D52) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.80 date: 10/25/2023
CPU:
Info: 16-core model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ rev: 0 cache:
L1: 1024 KiB L2: 8 MiB L3: 64 MiB
Speed (MHz): avg: 1746 min/max: 550/5086 boost: enabled cores: 1: 1746 2: 1746 3: 1746 4: 1746
5: 1746 6: 1746 7: 1746 8: 1746 9: 1746 10: 1746 11: 1746 12: 1746 13: 1746 14: 1746 15: 1746
16: 1746 17: 1746 18: 1746 19: 1746 20: 1746 21: 1746 22: 1746 23: 1746 24: 1746 25: 1746
26: 1746 27: 1746 28: 1746 29: 1746 30: 1746 31: 1746 32: 1746 bogomips: 217592
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 2f:00.0
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: gnome-shell
driver: X: loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
resolution: no compositor data resolution: 3840x1080
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
active: gbm,wayland,x11,surfaceless,device inactive: N/A
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.5-arch1.1 glx-v: 1.4
direct-render: yes renderer: AMD Radeon RX 6800 XT (radeonsi navi21 LLVM 19.1.7 DRM 3.61
6.14.6-2-MANJARO)
Info: Tools: api: eglinfo,glxinfo de: kscreen-doctor x11: xprop
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio driver: snd_hda_intel
v: kernel bus-ID: 2f:00.1
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 31:00.4
Device-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-2:3
Device-4: XMOS EDIFIER S880DB driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 5-4:3
API: ALSA v: k6.14.6-2-MANJARO status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.2 status: active
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel port: f000
bus-ID: 27:00.0
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi v: kernel
bus-ID: 28:00.0
IF: wlo1 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 1-4:6
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 4.56 TiB used: 744.11 GiB (15.9%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G1X0E-00AFY0 size: 465.76 GiB
temp: 36.9 C
ID-2: /dev/nvme1n1 vendor: Seagate model: WDS200T1X0E-00AFY0 size: 1.82 TiB temp: 33.9 C
ID-3: /dev/sda vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB
ID-4: /dev/sdb vendor: Samsung model: SSD 850 PRO 512GB size: 476.94 GiB
Partition:
ID-1: / size: 452.8 GiB used: 18.36 GiB (4.1%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 4.65 GiB used: 320 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1
ID-3: /home size: 1.79 TiB used: 376.69 GiB (20.6%) fs: ext4 dev: /dev/nvme1n1p1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 43.2 C mobo: 35.6 C gpu: amdgpu temp: 46.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 128 GiB note: est. available: 125.71 GiB used: 6.36 GiB (5.1%)
Processes: 584 Uptime: 2h 10m Init: systemd
Packages: 1641 Compilers: gcc: 15.1.1 Client: gnome-shell v: 48.1 inxi: 3.3.38
<>
Just found out about the manjaro log helper.
I just rebooted, and provoked the error, then got the logs since last boot. The forum wont let me post it as pre-formatted text though - too many characters. So I’ve put it on pastebin. Link below.
https://pastebin.com/KW7nkFGu
It is:gnome-control-center
toast
4 June 2025 16:58
3
Thanks. Just ran it from terminal and provoked the error and this is the terminal output.
$ gnome-control-center
17:48:49.8240 Gtk[10926]: WARNING: Unknown key gtk-modules in /home/user/.config/gtk-4.0/settings.ini
Violación de segmento (`core' generado)
Sorry about the Spanish. Computer is set to Spanish and I don’t know to temporarily change terminal output to English. I saw a manjaro forum post about half an hour ago that showed the command, and now I cannot find it.
Violación de segmento is pretty obvious though. Segment violation.
I do not even have this file in my installation …
The template for what is in that directory by default is in:/etc/skel/.config/gtk-4.0
settings.ini is likely created by you or some configuration adjustment you made
Move the file or delete it would be my suggestion.
mv ~/.config/gtk-4.0/settings.ini ~/.config/gtk-4.0/settings.ini-backup
… prepend any command with:LC_ALL=C
toast
4 June 2025 17:27
5
Going by the terminal error I got I thought the problem could be something in the settings.ini file
Unknown key gtk-modules in /home/user/.config/gtk-4.0/settings.ini
So I renamed settings.ini to settings.ini.old and it certainly made a difference. The error still occurs but now the terminal output is just this.
$ gnome-control-center
Violación de segmento (`core' generado)
Segment violation. I have no idea what to do next about that.
Your system is up to date?
journalctl -r
will list the log in reverse order (newest first), so you will likely easily find it
toast
4 June 2025 19:39
7
Thanks for this.
I provoked the crash and immediately ran that command.
I’ve got a huge amount of information, and lots of repeats of the same I think. I see a lot of this, but not sure what it’s trying to tell me.
Jun 04 20:35:28 desktop systemd-coredump[17022]: Process 16964 (gnome-control-c) of user 1000 dumped core.
Stack trace of thread 16964:
#0 0x00007a6c00c12ff1 g_file_equal (libgio-2.0.so.0 + 0x4eff1)
#1 0x00007a6c00a56743 g_hash_table_lookup (libglib-2.0.so.0 + 0x49743)
#2 0x0000582f81116fb8 n/a (/usr/bin/gnome-control-center + 0xeffb8)
#3 0x0000582f81117d8f n/a (/usr/bin/gnome-control-center + 0xf0d8f)
#4 0x00007a6c00ba34f9 g_type_create_instance (libgobject-2.0.so.0 + 0x3e4f9)
#5 0x00007a6c00b88768 n/a (libgobject-2.0.so.0 + 0x23768)
#6 0x00007a6c00b89de7 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24de7)
#7 0x00007a6c00b8ae42 g_object_new (libgobject-2.0.so.0 + 0x25e42)
#8 0x0000582f8108fe0b n/a (/usr/bin/gnome-control-center + 0x68e0b)
#9 0x00007a6c00351426 gtk_widget_activate_action_variant (libgtk-4.so.1 + 0x551426)
#10 0x00007a6c00952661 n/a (libadwaita-1.so.0 + 0x152661)
#11 0x00007a6c0023fcdf n/a (libgtk-4.so.1 + 0x43fcdf)
#12 0x00007a6c0014f7d8 n/a (libgtk-4.so.1 + 0x34f7d8)
#13 0x00007a6c00b97e5c n/a (libgobject-2.0.so.0 + 0x32e5c)
#14 0x00007a6c00b97f72 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32f72)
#15 0x00007a6c00b98034 g_signal_emit (libgobject-2.0.so.0 + 0x33034)
#16 0x00007a6c002074e5 n/a (libgtk-4.so.1 + 0x4074e5)
#17 0x00007a6c00b7af36 g_cclosure_marshal_VOID__BOXEDv (libgobject-2.0.so.0 + 0x15f36)
#18 0x00007a6c00b97e5c n/a (libgobject-2.0.so.0 + 0x32e5c)
#19 0x00007a6c00b97f72 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32f72)
#20 0x00007a6c00b98034 g_signal_emit (libgobject-2.0.so.0 + 0x33034)
#21 0x00007a6c002039fe n/a (libgtk-4.so.1 + 0x4039fe)
#22 0x00007a6c002058ab n/a (libgtk-4.so.1 + 0x4058ab)
#23 0x00007a6c00208cdb n/a (libgtk-4.so.1 + 0x408cdb)
#24 0x00007a6c00345957 n/a (libgtk-4.so.1 + 0x545957)
#25 0x00007a6c0024ebf2 n/a (libgtk-4.so.1 + 0x44ebf2)
#26 0x00007a6c0024f823 n/a (libgtk-4.so.1 + 0x44f823)
#27 0x00007a6c004f29a8 n/a (libgtk-4.so.1 + 0x6f29a8)
#28 0x00007a6c0059332b n/a (libgtk-4.so.1 + 0x79332b)
#29 0x00007a6c00b97e5c n/a (libgobject-2.0.so.0 + 0x32e5c)
#30 0x00007a6c00b97f72 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32f72)
#31 0x00007a6c00b98034 g_signal_emit (libgobject-2.0.so.0 + 0x33034)
#32 0x00007a6c00595670 n/a (libgtk-4.so.1 + 0x795670)
#33 0x00007a6c004fe74c n/a (libgtk-4.so.1 + 0x6fe74c)
#34 0x00007a6c00a6b1e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#35 0x00007a6c00acee97 n/a (libglib-2.0.so.0 + 0xc1e97)
#36 0x00007a6c00a6a615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#37 0x00007a6c00ca37d6 g_application_run (libgio-2.0.so.0 + 0xdf7d6)
#38 0x0000582f8108e63a main (/usr/bin/gnome-control-center + 0x6763a)
#39 0x00007a6bfea5d6b5 n/a (libc.so.6 + 0x276b5)
#40 0x00007a6bfea5d769 __libc_start_main (libc.so.6 + 0x27769)
#41 0x0000582f8108e7f5 _start (/usr/bin/gnome-control-center + 0x677f5)
Stack trace of thread 16973:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac8024 n/a (libc.so.6 + 0x92024)
#3 0x00007a6bfeb425a6 ppoll (libc.so.6 + 0x10c5a6)
#4 0x00007a6c00acef67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5 0x00007a6c00a6a615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#6 0x00007a6bf7d412fe n/a (libdconfsettings.so + 0x62fe)
#7 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#8 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#9 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16969:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac8024 n/a (libc.so.6 + 0x92024)
#3 0x00007a6bfeb50c81 recvmsg (libc.so.6 + 0x11ac81)
#4 0x00007a6c00c5dbf1 n/a (libgio-2.0.so.0 + 0x99bf1)
#5 0x00007a6c00c5dfb7 g_socket_receive_message (libgio-2.0.so.0 + 0x99fb7)
#6 0x00007a6c00cdfb98 n/a (libgio-2.0.so.0 + 0x11bb98)
#7 0x00007a6c00cdfd3d n/a (libgio-2.0.so.0 + 0x11bd3d)
#8 0x00007a6c00cdfe4a n/a (libgio-2.0.so.0 + 0x11be4a)
#9 0x00007a6c00ce132e n/a (libgio-2.0.so.0 + 0x11d32e)
#10 0x00007a6c00c6dd6c n/a (libgio-2.0.so.0 + 0xa9d6c)
#11 0x00007a6c00c72055 n/a (libgio-2.0.so.0 + 0xae055)
#12 0x00007a6c00cdfbcd n/a (libgio-2.0.so.0 + 0x11bbcd)
#13 0x00007a6c00c57e94 n/a (libgio-2.0.so.0 + 0x93e94)
#14 0x00007a6c00a6b1e4 n/a (libglib-2.0.so.0 + 0x5e1e4)
#15 0x00007a6c00acee97 n/a (libglib-2.0.so.0 + 0xc1e97)
#16 0x00007a6c00a6bee7 g_main_loop_run (libglib-2.0.so.0 + 0x5eee7)
#17 0x00007a6c00cd8a84 n/a (libgio-2.0.so.0 + 0x114a84)
#18 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#19 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#20 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16981:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16982:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16972:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16986:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16988:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16970:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9d450 g_cond_wait (libglib-2.0.so.0 + 0x90450)
#2 0x00007a6c00a32dac n/a (libglib-2.0.so.0 + 0x25dac)
#3 0x00007a6c00a32e1d g_async_queue_pop (libglib-2.0.so.0 + 0x25e1d)
#4 0x00007a6bfe4aa92c n/a (libpangoft2-1.0.so.0 + 0xd92c)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17009:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17001:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac864c n/a (libc.so.6 + 0x9264c)
#3 0x00007a6bfeacad1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x00007a6bba4a142e n/a (libvulkan_radeon.so + 0x2a142e)
#5 0x00007a6bba46f6ed n/a (libvulkan_radeon.so + 0x26f6ed)
#6 0x00007a6bba4a138d n/a (libvulkan_radeon.so + 0x2a138d)
#7 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#8 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16983:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16968:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac8024 n/a (libc.so.6 + 0x92024)
#3 0x00007a6bfeb425a6 ppoll (libc.so.6 + 0x10c5a6)
#4 0x00007a6c00acef67 n/a (libglib-2.0.so.0 + 0xc1f67)
#5 0x00007a6c00a6a615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615)
#6 0x00007a6c00a6a672 n/a (libglib-2.0.so.0 + 0x5d672)
#7 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#8 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#9 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16967:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9d450 g_cond_wait (libglib-2.0.so.0 + 0x90450)
#2 0x00007a6c00a32dac n/a (libglib-2.0.so.0 + 0x25dac)
#3 0x00007a6c00aa3ad2 n/a (libglib-2.0.so.0 + 0x96ad2)
#4 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#5 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#6 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16987:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16985:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17007:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16984:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17004:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac864c n/a (libc.so.6 + 0x9264c)
#3 0x00007a6bfeacad1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x00007a6bba4a142e n/a (libvulkan_radeon.so + 0x2a142e)
#5 0x00007a6bba46f6ed n/a (libvulkan_radeon.so + 0x26f6ed)
#6 0x00007a6bba4a138d n/a (libvulkan_radeon.so + 0x2a138d)
#7 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#8 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17002:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac864c n/a (libc.so.6 + 0x9264c)
#3 0x00007a6bfeacad1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x00007a6bba4a142e n/a (libvulkan_radeon.so + 0x2a142e)
#5 0x00007a6bba46f6ed n/a (libvulkan_radeon.so + 0x26f6ed)
#6 0x00007a6bba4a138d n/a (libvulkan_radeon.so + 0x2a138d)
#7 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#8 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17003:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac864c n/a (libc.so.6 + 0x9264c)
#3 0x00007a6bfeacad1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x00007a6bba4a142e n/a (libvulkan_radeon.so + 0x2a142e)
#5 0x00007a6bba46f6ed n/a (libvulkan_radeon.so + 0x26f6ed)
#6 0x00007a6bba4a138d n/a (libvulkan_radeon.so + 0x2a138d)
#7 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#8 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17005:
#0 0x00007a6bfead3e22 n/a (libc.so.6 + 0x9de22)
#1 0x00007a6bfeac7fda n/a (libc.so.6 + 0x91fda)
#2 0x00007a6bfeac864c n/a (libc.so.6 + 0x9264c)
#3 0x00007a6bfeacad1e pthread_cond_wait (libc.so.6 + 0x94d1e)
#4 0x00007a6bba4a142e n/a (libvulkan_radeon.so + 0x2a142e)
#5 0x00007a6bba46f6ed n/a (libvulkan_radeon.so + 0x26f6ed)
#6 0x00007a6bba4a138d n/a (libvulkan_radeon.so + 0x2a138d)
#7 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#8 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 16989:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17006:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
Stack trace of thread 17008:
#0 0x00007a6bfeb4ceed syscall (libc.so.6 + 0x116eed)
#1 0x00007a6c00a9e167 g_cond_wait_until (libglib-2.0.so.0 + 0x91167)
#2 0x00007a6c00a32d75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007a6c00a32ee8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ee8)
#4 0x00007a6c00aa4410 n/a (libglib-2.0.so.0 + 0x97410)
#5 0x00007a6c00aa2b3e n/a (libglib-2.0.so.0 + 0x95b3e)
#6 0x00007a6bfeacb7eb n/a (libc.so.6 + 0x957eb)
#7 0x00007a6bfeb4f18c n/a (libc.so.6 + 0x11918c)
ELF object binary architecture: AMD x86-64
Jun 04 20:35:28 desktop systemd[1]: Started Process Core Dump (PID 17021/UID 0).
Jun 04 20:35:28 desktop systemd-coredump[17021]: Process 16964 (gnome-control-c) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jun 04 20:35:28 desktop kernel: Code: e5 41 57 41 56 41 55 49 89 f5 41 54 53 48 89 fb 48 83 ec 08 67 e8 0f f9 ff ff 48 85 db 74 6a 4c 8b 33 49 89 c4 4d 85 f6 74 05 <49> 39 06 74 10 4c 89 e6 48 89 df ff 15 fe d3 17 00 85 c0 74 4a 4d
Jun 04 20:35:28 desktop kernel: gnome-control-c[16964]: segfault at 582a18d9acc6 ip 00007a6c00c12ff1 sp 00007ffe6796ef20 error 4 in libgio-2.0.so.0.8400.1[4eff1,7a6c00bf6000+11c000] likely on CPU 2 (core 2, socket 0)
Jun 04 20:35:23 desktop gnome-control-c[16964]: Unknown key gtk-modules in /home/user/.config/gtk-4.0/settings.ini
Jun 04 20:35:23 desktop systemd[1917]: Started Application launched by gnome-shell.
Jun 04 20:35:07 desktop systemd[1]: systemd-coredump@1-16938-0.service: Consumed 422ms CPU time, 247.1M memory peak.
Jun 04 20:35:07 desktop systemd[1]: systemd-coredump@1-16938-0.service: Deactivated successfully.
Jun 04 20:35:07 desktop systemd-coredump[16939]: Process 16879 (gnome-control-c) of user 1000 dumped core.
toast
4 June 2025 20:20
8
Sorry I hadn’t replied until now. I only just noticed this post.
I’ve just come back to manjaro after a few months on mx kde so you are right. Those files are from a previous install.
I’m going to have a look in /etc/skel/ and compare it to the version I have in my home folder. I’ll let you know if I have any luck.
In this case there might lie the reason.
If it doesn’t, if everything is o.k., then I would suggest to reset your user account to defaults
… move the files instead of deleting them - in case you need some of the contents/etc/skel
toast
4 June 2025 21:02
10
That was a good idea. I did not think of creating a new user account.
I tried it and the problem does not occur in the test user account.
But I’m not keen to clear out my home folder. I had to do that in the past due to plasma settings causing a real mess in any new install I did. It was a bit of a big task.
Is there an easy way to reset your user account. When I did it previously I did it manually. Moved all my files elsewhere and then nuked all dotfiles in home.
This doesn’t seem occur in a VM I have. It’s local to your environment, I expect. See if it happens with another user account.
Prefixing commands with LC_ALL=C will generate output in English; for example:
LC_ALL=C sudo pacman -Syu
(this may not work for launching a GUI app from terminal)
Yes.
That is, while it is “easy”, still making things unnecessarily complicated.
You could just as well “nuke” the dotfiles and then replace them with the defaults in /etc/skel,
I’m sure you are aware that some “dotfiles” may be holding your browser settings and your complete e-mail account (not just the settings).~/.firefox and ~/.thunderbird are examples - and ~/.config/chromium and ~/.config/evolution as well. There are more …
Be also aware that this is best done when logged out of the graphical environment - as there is a process running which prevents you from truly deleting certain configuration files.TTY, with the graphical session NOT running.
Having a console file manager like mc will make the job much easier when you are not familiar with the command line.
Don’t forget to delete ~/.cache - sometimes this alone seems to help.
1 Like
toast
5 June 2025 18:19
13
Thanks for this. Appreciated.
I have all my important dotfiles in a well backed up dotfiles directory. I use stow to create the symlinks.
So I can afford to nuke the home folder, but the last time I did it it took me ages figuring out what to delete. I did it all pretty manually, and from a live usb so that I was out of the system and could delete things without problems. I think I did it a very clumsy way.
Before I go for clearing home of the junk, I’m going to try to learn at least something about debugging problems. I’ve not been using linux and nothing else for about 5 years. I jumped in 2020. I run a small business with linux, and I run two linode servers that I set up myself and have maintained for nearly 5 years. So I’m not totally new to linux anymore, but I know nothing about debugging. I see the knowledge you guys have on this forum and I always think, “How did they learn all that”. I’m going to need to learn at least something.
Someone in this thread gave me a journalctl command. I’ve heard of it but in truth did not know what it was for and have never used it. Last night I looked it up and got an inkling of what it’s for. Today when I was driving to work I listened to the audio from a few youtube videos on using journalctl to find problems. I now at least know that you can use the -f flag to get a live view of what’s happening, and you can use -t (is it -t) to limit it to a specific application (and I think gnome-control-center is what I need to target, so I’m going to have a shot and see if I get anywhere. I’ll provoke the crash with journalctl running and see if anything sticks out to me.
I can do everything I need to do on linux, apart from fix problems. I don’t have a clue. And when I’ve got spare time I invest it in language learning, not learning linux debugging.
I just remembered. The other flag I was searching for is -u (for Unit I believe).
If a program crashes (like gnome-control-center for you)
You can waste much time on it, but not get anywhere …
you know that a fresh user doesn’t have the problemthe logical conclusion is: something ain’t right in your current users configuration
move/remove the dotfiles/hidden directories - all of them
copy what is in /etc/skel into your $HOME - that is what a clean user account starts with
then you can copy back from your backup what you know you need, like e-mail and browser profile
Doing it from the outside, from a live system, is not unproblematic, as the permissions (owner and group) may be wrong as a result.
That doesn’t happen when you are logged in on TTY as that user on your real system.
toast
5 June 2025 18:55
15
You are right.
I just tried the journalctl experiment, and it was interesting. It worked. I provoked the error and the journal spat out a whole lot of stuff that I cannot decipher.
I’m going to follow your instructions about doing it from the tty, but there are a couple of things I’d like to ask if I can.
Do you use a command to wipe out everything in one go apart from your own data (docs, pictures, etc) in home? In the past I’ve gone folder by folder doing sudo rm -r .config .local and I’ve always felt I was doing it the baby way.
When coping from skel to home do I need any particular flags so as not to end up with root permissions in my home directory? Or is sudo cp -r /etc/skel/ ~/user/home enough?
Sorry. Basic questions I know.
Oh, by the way. I did not even know that the home directory is populated by a framework that comes from /etc/skel. I’ve been living under a rock it seems.
toast
5 June 2025 18:59
16
I’m pretty sure that’s exactly what happened to me when I did it from the live usb. I think I spent ages fighting with permissions afterwards. I can’t remember how I fixed it, but I know I had a hard time.
My basic answer and suggestion is, as I already said:
use a file manager like mc (midnight commander)
It saves you from having to use the command line - and me from assisting you by giving you specific command examples.
sudo pacman -Syu mc
Then start it to familiarize yourself with how it works.
2 Likes
toast
5 June 2025 19:02
18
You can run it in the tty or a terminal. I’m amazed. Superb. I’m going to install it now and have a mess about with it.
Many thanks for your time on this so far.
Installed now.
My god, how useful is this. I had no idea this existed.
I’ve used ncdu a lot which this reminds me of, but that was only for checking how much space I’ve used on the linodes over ssh. This thing is amazing.
1 Like
toast:
This thing is amazing.
it is
… I use it 99% of the time - the GUI file manager (Nautilus or Thunar or whatever) get very rarely used.
toast
5 June 2025 19:05
20
Es una maravilla. Es asombrosa. Me encanta. No estoy de broma.
1 Like
- perhaps looking at the system logs will give more clues - the coredump will be listed there.
