(In reply to comment #9)
> Symptoms still appearing using patched version. Any idea where a coredump might
> live so I can attach it?
Location and naming of core files on Linux can be set using the kernel params:
kernel.core_uses_pid
kernel.core_pattern
You may want to check with your distribution what's the best place to set these (usually /etc/sysctl.conf)
It is not clear if the program segfaults in your case or else if this is a bug in the new implementation of session management added by Nick and Stefan in 4.8, so that should be determined first.
Note that a core file won't be useful in this bug report because I am not using the same distribution as you, so unless the core file contains all the debugging symbols and the binary statically linked (which is definitely not the case), I won't be able to make any sense of such a core file.
Brian's put some instructions on how to help debugging here:
(In reply to comment #9)
> Symptoms still appearing using patched version. Any idea where a coredump might
> live so I can attach it?
Location and naming of core files on Linux can be set using the kernel params:
kernel. core_uses_ pid core_pattern
kernel.
You may want to check with your distribution what's the best place to set these (usually /etc/sysctl.conf)
It is not clear if the program segfaults in your case or else if this is a bug in the new implementation of session management added by Nick and Stefan in 4.8, so that should be determined first.
Note that a core file won't be useful in this bug report because I am not using the same distribution as you, so unless the core file contains all the debugging symbols and the binary statically linked (which is definitely not the case), I won't be able to make any sense of such a core file.
Brian's put some instructions on how to help debugging here:
http:// spurint. org/projects/ xfce4-debugging /