> Can you try either or both of those from git and confirm whether it's fixed > or it's a separate issue?
> You can force one or the other to be built: > ./AppRun --compile --enable-gtk3 > or > ./AppRun --compile --disable-gtk3 > Without any arguments AppRun runs roxterm. Ok, first building with "./AppRun --compile --disable-gtk3", and running with "./AppRun", there is no more "extra window" and the session state seems to be restored properly, except that there is no login shell. When roxterm is first started, before the session-restore, there is a proper login shell. Second, building with "./AppRun --compile --enable-gtk3", and again running with "./AppRun", the session is restored properly, except, again, no login shell. And again, when first started, there is a proper login shell. Also, when first starting, the opened window is "maximized", even though "Appearance/Maximise" is not selected. However, the restored session windows are in the correct state. Also, I am noticing that if I select "File/New Window", instead of "File/New Window with Profile", I still get a window with the Profile configuration, at least with respect to getting a window with multiple tabs, instead of only one tab or no tabs. Or, does a "New Window" with no Profile mean "with the Default Profile"? Also, "File/Close Window" fails to obey the "Options/Warn when closing a window with multiple tabs" selection and no "Only warn if tasks are still running". However, using the window decoration "X" to close the window, the "Confirm Close" window pops-up as would be expected. But then, selecting "Option/Only warn if tasks are still running", the behaviour is the same, which, I suppose that all the running shells would be considered running tasks here - but I'm not sure what would be the point of an open tab with no shell - or, how is that suppose to work? If then "Options/No warnings when closing windows/tabs" is selected, there is no popup window, as expected. These other problems do not seem dependent upon whether this is a first session or a restored session. All these new problems are extent for both gtk2 and gtk3 versions. So, two fixed, and four new, and the issues seem to be common to both gtk2 and gtk3. > I think that's going to turn out to have a different cause if it isn't > fixed in this git version, so let's use 663739 for the login option > problem, and 663736 for the original problems. Both fixed, but then these new issues. I'll let you decide. Do you need new bug reports? Or, take a look first, and see if these others are inter-related? James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
