[Bug 244894] x11-wm/xfce4-session: dumps core immediately after startup

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244894

Guido Falsi <madpilot at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |madpilot at FreeBSD.org
             Status|New                         |Open
              Flags|maintainer-feedback?(xfce at F |maintainer-feedback+
                   |reeBSD.org)                 |

--- Comment #1 from Guido Falsi <madpilot at FreeBSD.org> ---
This is not an easy thing to address. I have never seen this happen and there
are a bunch of possible causes.

You flagged this bug as "affects some people", do you have actual reports from
other people having the same issue?

One thing that could help is if you could rebuild the xfce4-session port with
debugging support. It can be done by setting
WITH_DEBUG_PORTS=x11-wm/xfce4-session in the relevant make.conf in poudriere or
the one in /etc for locally built ports.

With that you could extract a backtrace from the core dump which could shed
some light. Without a backtrace there's really no way of knowing why it has
crashed.

Are you using official binary packages? your own package set built using tools
like poudriere or building ports on the live system?

Are you using any custom options?

If you are building local ports, I'd ask you to try rebuilding at least
xfce4-sesion, but also others could be needed. The world has become much more
complex than years ago and building ports on a live system has become an
unreliable process causing strange local breakage. This sometimes can be
"fixed" by rebuilding the right part.

ANother thing that comes to my mind is you say you're using slim. slim is an
unmaintained software and has seen no development for years, in the while the
Xorg world has gone forward and things have really changed in the session
management world.

I'd ask you to test using a modern display manager light LightDM and see if the
issue happens with that too.

I hope these pointers can give you ideas on how to diagnose the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.