[Pkg-xfce-devel] Bug#612504: Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
brandon.m.simmons at gmail.com
Wed Feb 9 15:54:25 UTC 2011
On Wed, Feb 9, 2011 at 1:11 AM, Yves-Alexis Perez <corsac at debian.org> wrote:
> On mar., 2011-02-08 at 18:56 -0500, Brandon Simmons wrote:
>> As for the backtrace, I'll need some hints on how to do that. I
>> re-built the 'xfce4-session' package with debugging symbols and
>> attempted to get a backtrace of "xfce4-session-logout --suspend" per
>> these instructions:
>> but I was instantly logged out of my session. I also tried to dump a
>> backtrace to a file using this trick:
> xfce4-session-logout doesn't segfaults, it's xfce4-session. Try to
> attach it using gdb -p $(pid xfce4-session). You should do it from a
> console or from ssh since when it'll be killed the session might be
I had gdb running in a separate TTY with:
$ gdb x-session-manager $(pidof x-session-manager)
And when I ran in TTY 7
$ xfce4-session-logout --suspend
I got the message "Failed to receive a reply from the session
manager". However, after quitting gdb the system immediately suspended
successfully (and when it came back up it went into suspend again,
presumably because I had tried the suspend command above twice).
At this point suspend seems to be working normally for whatever
reason. I'm sure it is unrelated to the debugging I just did, but I
thought I would mention the process I went through, since I haven't
done anything else with it in the meantime.
One final thing to mention: when suspend stopped working, I was asked
for my password when I tried to suspend from the GUI logout screen;
this never happened before. After entering it I was logged out.
Anyway thanks for the help in trying to resolve this.
>> but the resulting file contained only "no stack" and "no registers".
> That might work but, again, the one to debug is xfce4-session.
More information about the Pkg-xfce-devel