Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
reopen 612504 thanks On dim., 2011-02-20 at 19:41 -0500, Brandon Simmons wrote: I wanted to add more to this as this bug has re-appeared. I haven't figured out when and why it shows up, but now after several reboots it's still here. As mentioned earlier. the problem first shows itself when I attempt to suspend from the xfce4-session GUI box and it asks me for a password. After clicking cancel and checking my ~/.xsession-errors, I see: -- SNIP -- ** (x-session-manager:2178): WARNING **: xfsm-shutdown-helper.c:157: Failed to contact HAL: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** Message: xfsm-shutdown-helper.c:274: HAL not available or does not permit to shutdown/reboot the computer, trying sudo fallback instead. -- SNIP -- Is hal still installed? I think it may be related to PolicyKit and perhaps the fact that I use 'slim' as my login manager. I think it is also related to this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525909 Consolekit is basically broken in sid if you don't use gdm/gdm3 or startx, iirc, and that might be related. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597937 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601003 There was a patch to slim which might help though: http://developer.berlios.de/bugs/?func=detailbugbug_id=17757group_id=2663 I'm sorry I can't offer the solution yet. It'd help to have a backtrace, and you can try with another login manager (I think plain startx with “startxfce4” in your .xsession would work). Check that ck-list-session returns something like: corsac@hidalgo: ck-list-sessions Session9: unix-user = '1000' realname = 'Yves-Alexis Perez' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2011-02-19T22:19:19.773649Z' login-session-id = '4294967295' especially the active = TRUE and is-local = TRUE Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
On Wed, Feb 9, 2011 at 1:11 AM, Yves-Alexis Perez cor...@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: http://wiki.debian.org/HowToGetABacktrace 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 frozen. 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. Brandon http://blog.cryptomilk.org/2010/12/23/gdb-backtrace-to-file/ but the resulting file contained only no stack and no registers. That might work but, again, the one to debug is xfce4-session. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
On mer., 2011-02-09 at 10:54 -0500, Brandon Simmons wrote: On Wed, Feb 9, 2011 at 1:11 AM, Yves-Alexis Perez cor...@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: http://wiki.debian.org/HowToGetABacktrace 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 frozen. 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. I'd say this is because it was stuck in gdb on tty1. 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). As xfce4-session had segfaulted but not yet quitted (stuck in gdb) its children weren't killed and in particular the suspend order was correctly processed. At least that's how I see it. 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. Do you mean that it now works even without any gdb debugging? 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. That looks like a Consolekit/Policykit issue. Anyway thanks for the help in trying to resolve this. So what's the status right now? Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
On Wed, Feb 9, 2011 at 11:19 AM, Yves-Alexis Perez cor...@debian.org wrote: On mer., 2011-02-09 at 10:54 -0500, Brandon Simmons wrote: On Wed, Feb 9, 2011 at 1:11 AM, Yves-Alexis Perez cor...@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: http://wiki.debian.org/HowToGetABacktrace 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 frozen. 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. I'd say this is because it was stuck in gdb on tty1. 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). As xfce4-session had segfaulted but not yet quitted (stuck in gdb) its children weren't killed and in particular the suspend order was correctly processed. At least that's how I see it. 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. Do you mean that it now works even without any gdb debugging? Yes. Sorry to be unclear. 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. That looks like a Consolekit/Policykit issue. Anyway thanks for the help in trying to resolve this. So what's the status right now? Seems to be working. I did a restart yesterday, and I assume it had been working since then, but I hadn't tested it again until trying to do the debugging today. Brandon Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
On mar., 2011-02-08 at 15:50 -0500, Brandon Simmons wrote: After upgrading to wheezy, the suspend functionality from the logout menu no longer works. Instead it seems I am logged out of my session and presented with the 'slim' login screen. In /var/log/messages I see the following line: Feb 8 13:06:29 jberryman kernel: [70830.865667] x-session-manag[2055]: segfault at 0 ip 0805b05d sp bf9b23d0 error 4 in xfce4-session[8048000+1c000] I would be happy to help resolve this issue and grateful for any ideas on work-arounds. Is your wheezy fully up to date? Could you try to get a backtrace? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
On Tue, Feb 8, 2011 at 4:21 PM, Yves-Alexis Perez cor...@debian.org wrote: On mar., 2011-02-08 at 15:50 -0500, Brandon Simmons wrote: After upgrading to wheezy, the suspend functionality from the logout menu no longer works. Instead it seems I am logged out of my session and presented with the 'slim' login screen. In /var/log/messages I see the following line: Feb 8 13:06:29 jberryman kernel: [70830.865667] x-session-manag[2055]: segfault at 0 ip 0805b05d sp bf9b23d0 error 4 in xfce4-session[8048000+1c000] I would be happy to help resolve this issue and grateful for any ideas on work-arounds. Is your wheezy fully up to date? Could you try to get a backtrace? It is up to date. Here is my sources.list in case there is anything wrong here: deb http://ftp.us.debian.org/debian/ wheezy main deb-src http://ftp.us.debian.org/debian/ wheezy main deb http://ftp.us.debian.org/debian/ wheezy non-free contrib deb-src http://ftp.us.debian.org/debian/ wheezy non-free contrib deb http://security.debian.org/ wheezy/updates main deb-src http://security.debian.org/ wheezy/updates main # For skype: deb http://download.skype.com/linux/repos/debian/ stable non-free 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: http://wiki.debian.org/HowToGetABacktrace but I was instantly logged out of my session. I also tried to dump a backtrace to a file using this trick: http://blog.cryptomilk.org/2010/12/23/gdb-backtrace-to-file/ but the resulting file contained only no stack and no registers. Brandon Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612504: [Pkg-xfce-devel] Bug#612504: xfce4-session: Attempted suspend causes logout and segfault
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: http://wiki.debian.org/HowToGetABacktrace 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 frozen. http://blog.cryptomilk.org/2010/12/23/gdb-backtrace-to-file/ but the resulting file contained only no stack and no registers. That might work but, again, the one to debug is xfce4-session. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
