Date: Wed, 22 Feb 2012 18:31:12 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Rainer Hurling <rhurlin@gwdg.de> Cc: wmaker-dev@lists.windowmaker.info, freebsd-ports@freebsd.org Subject: Re: x11-wm/windowmaker: saving session not possible any more Message-ID: <4F45A4F0.2090802@FreeBSD.org> In-Reply-To: <4F453843.3030805@gwdg.de> References: <4F3F94C5.5020005@gwdg.de> <4F4021CF.9030503@FreeBSD.org> <4F409850.2010404@gwdg.de> <4F453843.3030805@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------020700010206070508010403 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Rainer, I'm cc'ing the wmaker-dev list, please follow up there rather than freebsd-ports till we get this resolved. On 02/22/2012 10:47, Rainer Hurling wrote: > it seems I found a workaround for getting the session restored after > restarting windowmaker. I took a look at this and got some very odd results. First, using stock windowmaker, I started, did a 'clear session', made sure everything was closed, then exited with the save session box checked. Then I started a few apps, exited with save session checked, and when I restarted it brought the session back. Then I used the attached patch to see the values of those variables you mentioned ... both were "(null)" as expected, and restoring the session continued to work. At this point I got creative and started playing with various combinations of 'clear session' and saving or not saving my session, and managed to get windomaker into a state where it would fail when started and bring up the dialog that gave the option to restart, start another wm, or dump a core file. Still not sure what was happening there, and the core wasn't particularly useful. Now that I think about it, I suspect that if I had tried 'wmaker -norestore' it would have worked ... What I suggest you do is add the attached to windowmaker/files (rename to patch-debug) and build it without your change. Then run startx and check the terminal. Try doing what I did above (clear session, exit w/save, startx, run some stuff, exit w/save, startx) and see if it works. If it doesn't, check the values of those 2 knobs in the printout on the terminal and let us know what's going on. hth, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ --------------020700010206070508010403 Content-Type: text/plain; name="nopatch-debug" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nopatch-debug" --- src/startup.c.orig 2012-02-22 16:25:30.000000000 -0800 +++ src/startup.c 2012-02-22 16:16:47.000000000 -0800 @@ -760,6 +760,8 @@ /* restore saved menus */ wMenuRestoreState(wScreen[j]); +wmessage("restarting: %s, norestore: %s\n", wPreferences.flags.restarting, wPreferences.flags.norestore); + /* If we're not restarting, restore session */ if (wPreferences.flags.restarting == 0 && !wPreferences.flags.norestore) wSessionRestoreState(wScreen[j]); --------------020700010206070508010403--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F45A4F0.2090802>