Process 3659 (xfsettingsd) of user 1000 dumped core

Support Xfce
1

seeing this after boot in journalctl -p 3 -xb

Aug 22 14:54:06 radu-lenovo systemd-coredump[7230]: Process 3659 (xfsettingsd) of user 1000 dumped core.

                                                Stack trace of thread 3659:
                                                #0  0x0000000000000000 n/a (n/a + 0x0)

– Subject: Process 3659 (xfsettingsd) dumped core
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance
– Documentation: man:core(5)

– Process 3659 (xfsettingsd) crashed and dumped core.

– This usually indicates a programming error in the crashing program and
– should be reported to its vendor as a bug.

2

Hello and welcome,

To make sure your system is updated and the xfce4-settings package is not corrupted, run this command from terminal:
sudo pacman-mirrors -f && sudo pacman -Syyu xfce4-settings

Reboot the system after that:
systemctl reboot

3

same, here is full output, I also see lightdm complains but maybe are not related

[radu@radu-lenovo ~]$ journalctl -p 3 -xb

– Logs begin at Thu 2020-06-25 23:17:48 +07, end at Sat 2020-08-22 16:50:12 +07. –
Aug 22 16:31:43 radu-lenovo lightdm[1137]: gkr-pam: unable to locate daemon control file
Aug 22 16:33:09 radu-lenovo systemd-coredump[2719]: Process 2418 (xfsettingsd) of user 1000 dumped core.

                                                Stack trace of thread 2418:
                                                #0  0x0000000100000000 n/a (n/a + 0x0)

– Subject: Process 2418 (xfsettingsd) dumped core
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance
– Documentation: man:core(5)

– Process 2418 (xfsettingsd) crashed and dumped core.

– This usually indicates a programming error in the crashing program and
– should be reported to its vendor as a bug.
Aug 22 16:33:19 radu-lenovo systemd-coredump[2727]: Process 2664 (xfsettingsd) of user 1000 dumped core.

                                                Stack trace of thread 2664:
                                                #0  0x00000000000000c0 n/a (n/a + 0x0)

– Subject: Process 2664 (xfsettingsd) dumped core
– Defined-By: systemd
– Support: https://forum.manjaro.org/c/technical-issues-and-assistance
– Documentation: man:core(5)

– Process 2664 (xfsettingsd) crashed and dumped core.

– This usually indicates a programming error in the crashing program and
– should be reported to its vendor as a bug.

4

See if doing this will help:

Will have to check on a XFCE install too. I might be able to do that later.
Also, i can’t tell what kernel you are using right now, but have you tried a different one?

5

Using this kernel 5.8.0-2. As I remember was same with prev version.

Noticed that right after boot I see only this:

[radu@radu-lenovo ~]$ journalctl -p 3 -xb
– Logs begin at Thu 2020-06-25 23:17:48 +07, end at Sat 2020-08-22 21:45:31 +07. –
Aug 22 21:44:47 radu-lenovo lightdm[1153]: gkr-pam: unable to locate daemon control file

And only after about 1m I see also the line related to xfsettingsd.

In all this time the defined Applications Shortcuts in Keyboard in settings are not working.
So I assume is because is keep trying to start xfsettingsd and only after it starts or next process in chain activates shortcuts.

6

I guess I found the issue for that specific crash. Seems in startup in xfce4-settings I had some XFCE-Panel Workaround
which executed:

#/bin/sh
sleep 5
xfsettingsd --replace &
sleep 15
xfsettingsd --replace &
sleep 25
xfsettingsd --replace &

I don’t remember adding this.

After removing this I don’t see the crash.

I still see this though, but maybe I should not worry for now as I don’t see anything not working for now.

– Logs begin at Fri 2020-06-26 09:04:44 +07, end at Sat 2020-08-22 22:09:02 +07. –
Aug 22 22:08:16 radu-lenovo lightdm[1145]: gkr-pam: unable to locate daemon control file

I still have some delay about 10-15 seconds until Application Shortcuts become active but will read more about that. As I assume it should not take so long right?

Thanks for the help.

1 Like