Some features returns non-zero exit after using Desktop

[ghost]

I am using Customizer latest commit 94a5558 from master branch. I experienced this issue for both GUI and CLI instances (while testing for documentation purpose). Tested using Xubuntu 12.04 and 14.04 32-bit ISO images on Xubuntu 12.04 and 14.04 32-bit host systems respectively.

The issue is, some features will return "non-zero exit" when trying to run the affected features after using Desktop feature. This issue will persists as long as current GUI is running.

The affected core features in GUI are: Edit sources, Terminal in Main tab and Browse FileSystem, Browse ISO in Extra tab.

Steps to reproduce this issue in Customizer GUI:

1. Select ISO of any official image (must contain Desktop Environment)
2. After extracted by Customizer, click on Desktop button to run live session
3. Do nothing, just select "log off" from live session to exit Xephyr.
4. Click on either Edit sources / Terminal (in Main tab) or Browse FileSystem / Browse ISO (in Extra tab) and you will see similar "non-zero exit" error dialog will appear.

Similarly, the affected features in CLI are: -c | --chroot and -x | --xnest arguments. However, I have witnessed the "non-zero exit" error only once and failed to reproduce this on CLI counterpart.

Above all, this issue is not critical. Because this can be resolved by itself when I exit and rerun GUI again. As long as I don't use the Desktop feature first, the previously affected features will remain functional.

So, if I ever use Desktop feature while remastering in current GUI, I just need to exit and rerun GUI again. Not a big deal, but may be troublesome for other users.

Another thing I noticed is, this issue only affects the recent commits and doesn't affect the first release of 4.1.0 (commit b75e06a) as I have tested its GUI on the same host system.

[ghost]

Example screenshots showing the "non-zero exit" on Xubuntu 14.04 32-bit host system.

Trying to run Edit sources feature after running Desktop feature:

Exit current GUI, rerun GUI from Terminal and rerun Edit sources feature--now working again:

The host system is fresh installed and no additional packages been upgraded. Only dependencies for Customizer 4.1.0 have been installed and updated.

[fluxer]

Make sue you really are using the latest version, the issue should've been fixed with a2eb05f (do not mind the XDG menus part, it broke again. it's some env. vars issue).

[ghost]

@fluxer
Yes, I am sure.

In fact, I purged existing install, redownload then reinstall again (now this is the "default" method I had updated in the first guide page).

In short, I used wget https://github.com/clearkimura/Customizer/archive/master.tar.gz to download the latest release from master branch.

I am getting the same result as reported above. Additionally, I have experienced the Desktop feature cannot be run again for second time, unless I close and rerun GUI.

When using GUI, after running Desktop and closing it for first time using "log off" menu, then trying to run Desktop for second time gives me this:

When using CLI, running Desktop and closing Live session using "log off" menu gives me this:

Don't mind about hanging cursor--I press Return key and it will show username@hostname~$ line as usual again.

In contrast, when using CLI, running Desktop and but this time closing Live session using "X" button on Window Manager gives me this:

The difference between the two interface is, even CLI shows similar error, CLI doesn't prevent me from running Desktop or the -x | --xnest argument as many times as I want.

CLI always works regardless of error messages. So I suppose this is GUI issue?

[ghost]

This is another follow up, to confirm that this issue also affects Customizer installed on Linux Mint host system. Screenshots as below.

When using GUI, run Desktop feature at first and select "Log off" in Live session to exit Xephyr, then run Edit sources and Terminal features in turns and each failed.

When exit GUI and rerun again, running Terminal feature first, it run normal OK.

Another screenshot showing CLI counterpart is unaffected, as below.

From above screenshot, the CLI has no problem running Desktop or the -x | --xnest argument followed by running Terminal or the -c | --chroot argument.

So to clarify again, this issue only persists on GUI counterpart.

Tested latest Customizer 4.1.0 on Linux Mint 17 32-bit host system, using official Xubuntu 14.04 32-bit ISO image on virtual machine.