suspend/hibernate support in xfce4-session

Brian J. Tarricone bjt23 at
Sat Nov 1 23:31:03 CET 2008

On Sat, 1 Nov 2008 22:10:44 +0000 Olivier Fourdan wrote:

> Humm, not so fast, xfce4-session cores at startup now (back in
> gnome...)
> (gdb) bt
> #0  0x000000342d426323 in g_type_check_is_value_type ()
>    from /lib64/
 #1  0x000000342d42cb9a in g_value_init ()
> from /lib64/ #2  0x00000035ff20f480 in
> dbus_g_proxy_call () from /usr/lib64/
> #3  0x0000000000a8c8d9 in xfconf_channel_get_internal
> (channel=0x1f726a0, property=0x417319 "/splash/Engine",
> value=0x7fffdfa49de0) at xfconf-dbus-bindings.h:57
> #4  0x0000000000a8fbc3 in IA__xfconf_channel_get_string
> (channel=0x1f726a0, property=0x417319 "/splash/Engine",
> default_value=0x417314 "mice") at xfconf-channel.c:808
> #5  0x000000000040a72c in main (argc=1, argv=0x7fffdfa49f78) at
> main.c:142

Shit.  What happens when you run

xfconf-query -c xfce4-session -p /splash/Engine

from the commandline?

The only thing I can think of is that it has to do with the new
sub-channel code in libxfconf, but I just looked at it, and I don't see
how it could be a problem.  Any chance you can run it through valgrind
and get a log of any errors?  Something like this should work:

which Xephyr && Xephyr :1 -ac || Xnest :1 -ac &
export DISPLAY=:1
eval `dbus-launch --exit-with-session`
valgrind --leak-check=no --num-callers=50
         --log-file=xfce4-session-log xfce4-session

(Might want to temporarily disable most of your autostart items before
doing this tho.)


More information about the Xfce4-dev mailing list