This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Problems while rendering ChoiceComponent in console mode installation
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 31, 2007
01:50 AM
Problems while rendering ChoiceComponent in console mode installation
I have a InstallShield Multiplatform project moved from 4.5.3 to 11.5. This is working fine for GUI and silent mode installations but i have a few problems in console mode installation.
From the Installation type screen ( Typical/Custom ) where a ChoiceComponent() is used to input the value, it just quits the installer once a value is selected. When I tried to run the installer in debug mode it failed with the following Exception.
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.awt.GraphicsEnvironment.checkHeadless(Unknown Source)
at java.awt.Choice.(Unknown Source)
at com.installshield.wizardx.ui.ChoiceComponent.(Unknown Source)
at com.installshield.wizardx.ui.ChoiceComponent.(Unknown Source)
at com.installshield.wizardx.ui.ChoiceComponent.(Unknown Source)
at com.installshield.wizardx.ui.ChoiceComponent.(Unknown Source)
at com.installshield.wizardx.ui.ChoiceComponent.(Unknown Source)
at com.installshield.wizardx.panels.ConfigureASAPUnixVariables.initialize(ConfigureASAPUnixVariables.java:191)
at com.installshield.wizardx.panels.ExtendedWizardPanel.consoleInitialize(Unknown Source)
at com.installshield.wizardx.panels.ConfigureASAPUnixVariables.consoleInitialize(ConfigureASAPUnixVariables.java:74)
at com.installshield.wizardx.panels.ExtendedWizardPanelConsoleImpl.initialize(Unknown Source)
at com.installshield.wizard.console.ConsoleWizardUI.currentBeanChanged(Unknown Source)
at com.installshield.wizard.StandardWizardListener.currentBeanChanged(Unknown Source)
at com.installshield.wizard.Wizard$RunThread.run(Unknown Source)
(May 31, 2007 2:40:32 AM), Setup.product.install, com.installshield.wizard.console.ConsoleWizardUI, err, could not display error message panel -- exiting wizard
Wizard.getExitCode(): called after WizardServices is shutdown.
Wizard.getExitCode(): called after WizardServices is shutdown.
SolarisSystemUtilServiceImpl: deleteFilesAfterExit()
SO I tried to set the DISPLAY variable and run the installer and it proceeds fine. But it doesn't makes sense to run a console mode installation setting the DISPLAY variable.
I gave this another try by removing the ChoiceComponent from the particular screen, rebuild the installer and run it in console mode. This time without setting the DISPLAY variable it works fine but fails in another screen where a ChoiceComponent is used.
Could any one of you shed some light and help me out resolving this issue.
Regards,
Balaji .C
From the Installation type screen ( Typical/Custom ) where a ChoiceComponent() is used to input the value, it just quits the installer once a value is selected. When I tried to run the installer in debug mode it failed with the following Exception.
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.awt.GraphicsEnvironment.checkHeadless(Unknown Source)
at java.awt.Choice.
at com.installshield.wizardx.ui.ChoiceComponent.
at com.installshield.wizardx.ui.ChoiceComponent.
at com.installshield.wizardx.ui.ChoiceComponent.
at com.installshield.wizardx.ui.ChoiceComponent.
at com.installshield.wizardx.ui.ChoiceComponent.
at com.installshield.wizardx.panels.ConfigureASAPUnixVariables.initialize(ConfigureASAPUnixVariables.java:191)
at com.installshield.wizardx.panels.ExtendedWizardPanel.consoleInitialize(Unknown Source)
at com.installshield.wizardx.panels.ConfigureASAPUnixVariables.consoleInitialize(ConfigureASAPUnixVariables.java:74)
at com.installshield.wizardx.panels.ExtendedWizardPanelConsoleImpl.initialize(Unknown Source)
at com.installshield.wizard.console.ConsoleWizardUI.currentBeanChanged(Unknown Source)
at com.installshield.wizard.StandardWizardListener.currentBeanChanged(Unknown Source)
at com.installshield.wizard.Wizard$RunThread.run(Unknown Source)
(May 31, 2007 2:40:32 AM), Setup.product.install, com.installshield.wizard.console.ConsoleWizardUI, err, could not display error message panel -- exiting wizard
Wizard.getExitCode(): called after WizardServices is shutdown.
Wizard.getExitCode(): called after WizardServices is shutdown.
SolarisSystemUtilServiceImpl: deleteFilesAfterExit()
SO I tried to set the DISPLAY variable and run the installer and it proceeds fine. But it doesn't makes sense to run a console mode installation setting the DISPLAY variable.
I gave this another try by removing the ChoiceComponent from the particular screen, rebuild the installer and run it in console mode. This time without setting the DISPLAY variable it works fine but fails in another screen where a ChoiceComponent is used.
Could any one of you shed some light and help me out resolving this issue.
Regards,
Balaji .C
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2007
09:02 AM
Maybe you could post some of the code that seems to be causing the issue
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 18, 2007
12:51 AM
Hi Jeremy,
Thanks for the interest that you have shown in investigating the issue.
Recently, I had managed to find a way to overcome the issue and its working fine now.
With Regards,
Balaji .C
Thanks for the interest that you have shown in investigating the issue.
Recently, I had managed to find a way to overcome the issue and its working fine now.
With Regards,
Balaji .C