[Solved] xfce4-settings crash since upgrading to 4.14

stanna · 2019-08-13 02:09:20

hey all,

i was hoping someone could shed some light on the below crashing whenever i try to open the display settings in xfce4 since upgrading to 4.14. sadly i cant use this at all anymore even downgrading xfce4-settings to the previous version has had no effect so it may be a different package thats caused it?

Aug 13 12:07:08 motion.local audit[1799]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=5 pid=1799 comm="xfce4-display-s" exe="/usr/bin/xfce4-display-settings" sig=11 res=1
Aug 13 12:07:08 motion.local kernel: xfce4-display-s[1799]: segfault at 29 ip 00007f0a09872c90 sp 00007ffe169c5780 error 4 in libc-2.29.so[7f0a09810000+14a000]
Aug 13 12:07:08 motion.local kernel: Code: 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 83 ec 18 48 8b 05 79 42 13 00 48 8b 00 48 85 c0 0f 85 7d 00 00 00 48 85 ff 74 70 <48> 8b 47 f8 48 8d 77 f0 a8 02 75 34 48 8b 15 d5 40 13 00 64 48 83
Aug 13 12:07:08 motion.local kernel: audit: type=1701 audit(1565662028.432:190): auid=1000 uid=1000 gid=1000 ses=5 pid=1799 comm="xfce4-display-s" exe="/usr/bin/xfce4-display-settings" sig=11 res=1
Aug 13 12:07:08 motion.local systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Aug 13 12:07:08 motion.local systemd[1]: Started Process Core Dump (PID 1802/UID 0).
Aug 13 12:07:08 motion.local audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1802-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 13 12:07:08 motion.local kernel: audit: type=1130 audit(1565662028.439:191): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1802-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 13 12:07:08 motion.local systemd-coredump[1803]: Process 1799 (xfce4-display-s) of user 1000 dumped core.
                                                     
                                                     Stack trace of thread 1799:
                                                     #0  0x00007f0a09872c90 __libc_free (libc.so.6)
                                                     #1  0x000055a540bf1975 n/a (xfce4-display-settings)
                                                     #2  0x000055a540be9ad5 n/a (xfce4-display-settings)
                                                     #3  0x000055a540bec896 n/a (xfce4-display-settings)
                                                     #4  0x000055a540be7201 n/a (xfce4-display-settings)
                                                     #5  0x00007f0a09811ee3 __libc_start_main (libc.so.6)
                                                     #6  0x000055a540be7d0e n/a (xfce4-display-settings)
                                                     
                                                     Stack trace of thread 1800:
                                                     #0  0x00007f0a098dc667 __poll (libc.so.6)
                                                     #1  0x00007f0a09a18a80 n/a (libglib-2.0.so.0)
                                                     #2  0x00007f0a09a18b51 g_main_context_iteration (libglib-2.0.so.0)
                                                     #3  0x00007f0a09a18ba2 n/a (libglib-2.0.so.0)
                                                     #4  0x00007f0a099f5a31 n/a (libglib-2.0.so.0)
                                                     #5  0x00007f0a08d9857f start_thread (libpthread.so.0)
                                                     #6  0x00007f0a098e70e3 __clone (libc.so.6)
                                                     
                                                     Stack trace of thread 1801:
                                                     #0  0x00007f0a098dc667 __poll (libc.so.6)
                                                     #1  0x00007f0a09a18a80 n/a (libglib-2.0.so.0)
                                                     #2  0x00007f0a09a19a63 g_main_loop_run (libglib-2.0.so.0)
                                                     #3  0x00007f0a09b85a38 n/a (libgio-2.0.so.0)
                                                     #4  0x00007f0a099f5a31 n/a (libglib-2.0.so.0)
                                                     #5  0x00007f0a08d9857f start_thread (libpthread.so.0)
                                                     #6  0x00007f0a098e70e3 __clone (libc.so.6)
Aug 13 12:07:08 motion.local systemd[1]: systemd-coredump@0-1802-0.service: Succeeded.

Last edited by stanna (2019-08-20 01:05:57)

demolitions · 2019-08-13 06:12:21

I also have the same problem.
I'd like to add that if I launch the program multiple times in quick succession, it somehow manages to run, but segfaults as soon as I try to apply any screen configuration.

I'm inclined to believe that's not a driver issue, since xrandr (by itself or with ARandR) correctly changes the screen configuration, without errors.

May well be unrelated, but after the same upgrade, I had to recompile xfdashboard because it would not find libxfconf-0.so.2

I believe that we have simply to reinstall/recompile a package to get everything working again, the problem is figuring out which one.

stanna · 2019-08-13 06:26:12

i just did a fresh install on another laptop and am getting the exact same issue.

filed a bug report :: https://bugs.archlinux.org/task/63449

real show stopper for me. need to dock laptop at work and use without dock at home and was really looking forward to this new feature.

Last edited by stanna (2019-08-13 07:06:13)

demolitions · 2019-08-13 07:00:08

I also have problems with the color theme (both xfce4-panel and xfce4-settings keep changing from dark to light seemingly at random every login), and it won't recognize my keyboard shortcuts (I use around 4-5 almost constantly).

Downgrading all xfce4 packages to the previously installed version (list included) solves all those issues for now.

libxfce4util 4.13.5-1
xfconf 4.12.1-7
libxfce4ui 4.13.7-1
xfce4-appfinder 4.12.0-5
xfce4-panel 4.12.2-1
xfce4-clipman-plugin 1.4.3-1
xfce4-datetime-plugin 0.7.1-1
xfce4-dev-tools 4.13.0-1
xfce4-genmon-plugin 4.0.1-1
xfce4-notes-plugin 1.8.1-3
xfce4-notifyd 0.4.4-1
xfce4-power-manager 1.6.4-1
xfce4-pulseaudio-plugin 0.4.1-1
xfce4-session 4.12.1-11
xfce4-settings 4.12.4-2
xfce4-terminal 0.8.8-1
xfce4-xkb-plugin 0.8.1-1
xfdesktop 4.13.6-1
xfwm4 4.12.5-1

I downgraded them all at once using this command:

sudo downgrade $(cat /var/log/pacman.log | grep -a '2019-08-12' | grep -a 'xf' | grep -av 'video-intel' | awk '{print $5}')

Of course you'll want to substitute '2019-08-12' with the date you applied the upgrade.

Where should we go from here? Is this bug to be reported upstream? Does any other distribution use Xfce 4.14 so we could check if they have the same issues?

Last edited by demolitions (2019-08-13 07:02:17)

toz · 2019-08-13 10:42:20

Can you try running xfsettingsd in debug mode:

XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon

and then opening display settings to see if anything useful is output?

Ropid · 2019-08-13 11:19:23

Things seem to run fine here for me, there's nothing crashing. I can visit the Display settings tool and use it fine.

Maybe one thing to try would be removing the saved config for the "Display" settings. You can do that with the "Settings Editor" tool: the Display tool saves its stuff under the name "displays" on the left pane of the settings editor. You can right-click on that "displays" entry there on the left pane, then choose the "reset" menu entry. The "displays" entry from the left pane should then disappear. The entry will get recreated the next time you visit the "Display" settings tool.

demolitions · 2019-08-13 11:45:20

Ropid wrote:

[...] removing the saved config for the "Display" settings.

stanna wrote:

i just did a fresh install on another laptop and am getting the exact same issue.

The issue is present also on a newly installed machine, so I don't believe that forcing xfsettingsd to recreate the configuration will solve anything.

toz wrote:

Can you try running xfsettingsd in debug mode:
XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
and then opening display settings to see if anything useful is output?

I'm currently reinstalling the "broken" packages, will try afterwards and report back, thanks.

demolitions · 2019-08-13 12:12:35

$ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
xfce4-settings(xsettings): _XSETTINGS_S0 registered on screen 0
xfce4-settings(xsettings): 29 settings changed (serial=0, len=1164)
xfce4-settings(xsettings): resource manager (xft) changed (len=117)
xfce4-settings(displays): Detected CRTC 63.
xfce4-settings(displays): Detected CRTC 64.
xfce4-settings(displays): Detected CRTC 65.
xfce4-settings(displays): Detected output 66 eDP-1.
xfce4-settings(displays): Detected output 67 HDMI-1.
xfce4-settings(displays): Detected output 68 DP-1.
[1]    2484 segmentation fault (core dumped)  XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon

This is what I get upon launching xfsettingsd, it won't even open the settings window.

toz · 2019-08-13 12:25:56

Does using coredumpctl and generating a backtrace provide some information?

Also, you seem to have 3 display devices. Maybe start by having only one connected to see if it works and then adding them one at a time to see which one generates the core dump.

demolitions · 2019-08-13 12:48:11

You are on to something.

I have a laptop, so one display cannot be disconnected, but following your advice I found out that xfsettingsd segfaults as soon as it detects 3 screens.

It's not one or the other, I can keep it working perfectly with the HDMI one(eDP-1 + HDMI-1), or with the VGA one (eDP-1 + DP-1), but as soon as I connect the third, it segfaults.

And xfsettingsd crashing is the reason of my other issues, as they disappear if I keep only one external monitor connected and xfsettingsd keeps running.

output of coredumpctl:
https://pastebin.com/raw/0h0S4biu

output of XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon:
https://pastebin.com/raw/4yJNvGhi

I'll add that I have an nvidia optimus video card, but it should be activated via bumblebee, Xorg correctly reports using the Intel driver.

Last edited by demolitions (2019-08-13 12:50:26)

andyboeh · 2019-08-13 15:28:40

I do have the same problem with xfce4-display-settings crashing, but xfsettingsd does not crash for me. I've got three screens as well (Laptop + two screens) and crashes (of xfce4-display-settings) start as soon as the second screen is connected.

toz · 2019-08-13 15:59:25

andyboeh wrote:

I do have the same problem with xfce4-display-settings crashing, but xfsettingsd does not crash for me. I've got three screens as well (Laptop + two screens) and crashes (of xfce4-display-settings) start as soon as the second screen is connected.

Can you post the output of:

XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon

...initially without the second screen connected and then when the output pauses, connect the second screen?

toz · 2019-08-13 16:09:48

demolitions wrote:

output of coredumpctl:
https://pastebin.com/raw/0h0S4biu

Unfortunately there is not enough information there to identify the code section at fault. Is there any chance you can manually build xfce4-settings with debug enabled (--enable-debug) to be able to get the full trace to the crash? It would help the developers with tracking down the problem.

Someone recently created an upstream bug report for this issue. Appending this information to that report would probably be the best way to move forward.

stanna · 2019-08-13 22:45:48

i am happy to provide as much information as possible that might help resolve the issue if someone would be kind enough to provide a list of what is required and how to obtain it.

demolitions · 2019-08-14 07:42:51

I added my (somewhat scarce) info to the upstream bug report, if someone could walk me through recompiling the whole daemon, I could extract a debug trace.

Will it suffice to grab xfce4-settings-devel PKGBUILD and change it (change version and configure flags)?

EDIT: perhaps not, since after having done this, the core dump is not different in the slightest.

Last edited by demolitions (2019-08-14 08:01:30)

V1del · 2019-08-14 08:10:05

You will at least also want to disable stripping and explicitly add debug symbols in the PKGBUILD config: https://wiki.archlinux.org/index.php/De … ing_Traces

demolitions · 2019-08-14 08:29:13

V1del wrote:

You will at least also want to disable stripping and explicitly add debug symbols in the PKGBUILD config: https://wiki.archlinux.org/index.php/De … ing_Traces

Thanks, this actually produced some symbols in the trace.

coredumpctl info

gdb trace from core dump

Do you think that I should also recompile libgio-2 and libc?
libgio-2 should be available in eschwartz repo, but I'm a bit worried that recompiling libc will take a long time.

toz · 2019-08-14 11:09:36

demolitions wrote:

Thanks, this actually produced some symbols in the trace.
coredumpctl info
gdb trace from core dump

This will be useful info for the developer. Looks like it's crashing because of something with new display profiles that was added to 4.14. Specfically in: https://git.xfce.org/xfce/xfce4-setting … iles.c#n74. And somehow tied to the fact that it is 3 monitors (or 3 different types of display connections).

stanna · 2019-08-14 23:58:56

a solution for those who can apply and test it.

https://bugzilla.xfce.org/show_bug.cgi?id=15816#c8

I have no idea how but keen to know if anyone else can and confirm it works

demolitions · 2019-08-16 06:59:56

I tried the patch, and for me it does not change a thing.

Can someone confirm that I'm doing it correctly, with this PKGBUILD ?

toz · 2019-08-16 13:27:46

demolitions wrote:

I tried the patch, and for me it does not change a thing.
Can someone confirm that I'm doing it correctly, with this PKGBUILD ?

==> Validating source files with sha256sums...
xfce4-settings-4.14.0.tar.bz2 ... Skipped
3screens.patch ... Skipped
==> Extracting sources...
-> Extracting xfce4-settings-4.14.0.tar.bz2 with bsdtar
==> Starting build()...
patching file common/display-profiles.c

Yes, it looks like the patch is being applied.

Is xfsettingsd still crashing? What does your coredumpctl info look like now?

demolitions · 2019-08-16 13:57:38

toz wrote:

Is xfsettingsd still crashing? What does your coredumpctl info look like now?

exactly the same as before.

I tried rebooting, and the coredump is the same.

I checked /bin/xfsettingsd last change time, to be sure it was being reinstalled, and it was.

toz · 2019-08-16 15:08:38

Probably best to post your findings to the upstream bug report.

demolitions · 2019-08-18 13:46:20

There is a new patch on the upstream bug report, I don't have access to the 3-screen setup until tomorrow, if anyone has the same problem could try it out.

demolitions · 2019-08-19 07:41:42

Ok, both the last two patches solve the problem on my system.

Would an AUR package be useful (since I already have a PKGBUILD, I can quickly fix it (add the checksum, remove debug options) and upload it), or should we simply wait for the upstream release?

Arch Linux

#1 2019-08-13 02:09:20

[Solved] xfce4-settings crash since upgrading to 4.14

#2 2019-08-13 06:12:21

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#3 2019-08-13 06:26:12

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#4 2019-08-13 07:00:08

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#5 2019-08-13 10:42:20

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#6 2019-08-13 11:19:23

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#7 2019-08-13 11:45:20

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#8 2019-08-13 12:12:35

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#9 2019-08-13 12:25:56

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#10 2019-08-13 12:48:11

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#11 2019-08-13 15:28:40

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#12 2019-08-13 15:59:25

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#13 2019-08-13 16:09:48

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#14 2019-08-13 22:45:48

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#15 2019-08-14 07:42:51

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#16 2019-08-14 08:10:05

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#17 2019-08-14 08:29:13

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#18 2019-08-14 11:09:36

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#19 2019-08-14 23:58:56

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#20 2019-08-16 06:59:56

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#21 2019-08-16 13:27:46

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#22 2019-08-16 13:57:38

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#23 2019-08-16 15:08:38

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#24 2019-08-18 13:46:20

Re: [Solved] xfce4-settings crash since upgrading to 4.14

#25 2019-08-19 07:41:42

Re: [Solved] xfce4-settings crash since upgrading to 4.14

Board footer