On Thu, Apr 24, 2014 at 01:30:12AM +0200, Alf Gaida wrote: > Source: xfce4-session > Version: 4.10.1-5 > Severity: important > > Dear Maintainer, > > with current build options legacy commands are saved in session cache - this > leads to several misbehaviors when > reloading a session (commands are eventually executed twice, legacy commands > are executed without options and so on) > According to the manual, xfce4-session should be build without legacy-sm > > Command Explanations > --disable-legacy-sm: This switch disables legacy session management which > isn't necessary on modern system.
So, there's an xfce4-session built with --disable-legacy-sm. It seems to cause #751725 but I'm a bit unsure what really happens there. I have to admit session management doesn't really appear to work really fine here with or without legacy-sm enabled (chromium for example seems to never be part of a session…). It might help to be a little bit more specific about what exactly is broken with the legacy-sm enabled, because if that actually breaks some useful behavior for some people and it's actually a no-op for me, I'm not sure I'll keep it like that. Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pkg-xfce-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xfce-devel
