Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Galileo: Startup/Shudown interface does not work.
Galileo: Startup/Shudown interface does not work. [message #336871] Wed, 08 July 2009 13:18 Go to next message
Dan Thurman is currently offline Dan Thurman
Messages: 57
Registered: July 2009
Member
Galileo perhaps has a problem with the Startup/Shutdown
mechanism:

1) On startup, Galileo does not prompt user
for workspace selection and immediately
defaults to: $HOME/workspace.

Windows -> Preferences -> General -> Startup
and Shutdown -> 'Prompt for workspace on startup'
item is checked. Checking/Unchecking this item,
exiting/starting Eclipse does not restore startup
workspace prompting. This mechanism fails to work
and always defaults to $HOME/workspace.

2) Using: File -> Switch Workspace, and adding
user defined workspace does save the workspace
entries into: Windows -> Preferences -> General
-> Startup and Shutdown -> Workspaces and will
shutdown and restart Eclipse with the user-defined
workspace item selected. However, this user-selected
item is not "remembered", should the user manually
shutdown and restart Eclipse; the user is not
prompted for a workspace selection (in spite of
the 'Prompt for workspace on startup' item being
checked) and chooses the default workspace as:
$HOME/workspace.

I have removed the "$HOME/workspace" entry from
the list, leaving behind user-defined workspaces
and it seems that none of these user-defined
workspaces are chosen, only $HOME/workspace
is always chosen. The same is true if all items
are cleared from this list.

If I am missing something, please let me know.

Kind regards,
Dan
Re: Galileo: Startup/Shudown interface does not work. [message #336876 is a reply to message #336871] Wed, 08 July 2009 15:15 Go to previous messageGo to next message
Eclipse User
Originally posted by: eclipse-news.rizzoweb.com

Dan Thurman wrote:
> Galileo perhaps has a problem with the Startup/Shutdown
> mechanism:
>
> 1) On startup, Galileo does not prompt user
> for workspace selection and immediately
> defaults to: $HOME/workspace.
>
> Windows -> Preferences -> General -> Startup
> and Shutdown -> 'Prompt for workspace on startup'
> item is checked. Checking/Unchecking this item,
> exiting/starting Eclipse does not restore startup
> workspace prompting. This mechanism fails to work
> and always defaults to $HOME/workspace.
>
> 2) Using: File -> Switch Workspace, and adding
> user defined workspace does save the workspace
> entries into: Windows -> Preferences -> General
> -> Startup and Shutdown -> Workspaces and will
> shutdown and restart Eclipse with the user-defined
> workspace item selected. However, this user-selected
> item is not "remembered", should the user manually
> shutdown and restart Eclipse; the user is not
> prompted for a workspace selection (in spite of
> the 'Prompt for workspace on startup' item being
> checked) and chooses the default workspace as:
> $HOME/workspace.

Since it obviously works for most users (certainly Galileo would not
have released with such a drastic bug), all I can do is grasp at straws.
So here goes...

What, exactly, did you download and install? Which package? Have you
installed anything into that since first running it?
What happens if you get a new installation and try it; does it prompt
you for workspace selection on startup?

What does your eclipse.ini look like? Are you specifying a -data
argument there or on the command line (eg, in a Windows shortcut)?

Eric
Re: Galileo: Startup/Shudown interface does not work. [message #336877 is a reply to message #336871] Wed, 08 July 2009 15:48 Go to previous messageGo to next message
Yves Schumann is currently offline Yves Schumann
Messages: 40
Registered: July 2009
Member
Hi Dan

Dan Thurman schrieb:
> Galileo perhaps has a problem with the Startup/Shutdown
> mechanism:

Works nice on a lot of installations here...

Just an idea: Is it possible that you have (some) write protected files
inside of your installation or inside of the workspace?

--
MfG
Yves

"Schlager sind Texte, die gesungen werden müssen, weil sie zu dumm sind,
um gesprochen zu werden." -- Gisela Uhlen
Re: Galileo: Startup/Shudown interface does not work. [message #336878 is a reply to message #336876] Wed, 08 July 2009 23:07 Go to previous messageGo to next message
Dan Thurman is currently offline Dan Thurman
Messages: 57
Registered: July 2009
Member
On Wed, 08 Jul 2009 15:15:28 -0400, Eric Rizzo wrote:

> Dan Thurman wrote:
>> Galileo perhaps has a problem with the Startup/Shutdown mechanism:
>>
>> 1) On startup, Galileo does not prompt user
>> for workspace selection and immediately defaults to:
>> $HOME/workspace.
>>
>> Windows -> Preferences -> General -> Startup and Shutdown -> 'Prompt
>> for workspace on startup' item is checked. Checking/Unchecking this
>> item, exiting/starting Eclipse does not restore startup workspace
>> prompting. This mechanism fails to work and always defaults to
>> $HOME/workspace.
>>
>> 2) Using: File -> Switch Workspace, and adding
>> user defined workspace does save the workspace entries into: Windows
>> -> Preferences -> General -> Startup and Shutdown -> Workspaces and
>> will shutdown and restart Eclipse with the user-defined workspace
>> item selected. However, this user-selected item is not
>> "remembered", should the user manually shutdown and restart Eclipse;
>> the user is not prompted for a workspace selection (in spite of the
>> 'Prompt for workspace on startup' item being checked) and chooses
>> the default workspace as: $HOME/workspace.
>
> Since it obviously works for most users (certainly Galileo would not
> have released with such a drastic bug), all I can do is grasp at straws.
> So here goes...
>

First off, I am running Eclipse on Fedora 9, not M$.

It did work, at first. But later on, when installing
most of the packages and default plugins I did not
seem to have any difficulties. Everything went along
just fine until I had problems fiddling with trying
to get the SVN, Subversion, Subclipse packages to
work and started using both Galileo and Ganymede
while testing why there was *many* problems with
SVN. Then somewhere along the line, Galileo's
Startup workspace prompt stopped working. Using
the same workspace with Ganymede and Galileo, only
Galileo's startup seems to be broken somewhere...

> What, exactly, did you download and install? Which package?

How can I easily get the entire list for you since
I don't want to type it all out by hand? ;)

I first downloaded JavaEE package for Fedora (linux)
and then from the Galileo update site, downloaded
nearly all items that were installable. Everything
that was available from Birt, C/C++ ... Perl, PHP...
plus some sources outside Galileo availability such
as Photran, Pydev, and SVN from polarion. I did not
install any plugins outside of what was already
available via Galileo.

> Have you installed anything into that since first
> running it? What happens if you get a new installation
> and try it; does it prompt you for workspace selection
> on startup?

Workspace prompts worked before updates. After updates,
it worked as well and I was running several JavaEE apps
and had my fun for awhile, until I noticed there was a
problem getting SVN commits to work, so I was fiddling
with SVN using both Ganymede & Galileo on the same workspace
(independently) and noticed that workspace prompts stopped
working. I was doing a LOT of work fiddling with SVN to
the point of completely uninstalling and installing SVN
so, somewhere in this step, workspace prompt stopped
working, perhaps. I just don't know when and what caused
workspace prompt to fail...

>
> What does your eclipse.ini look like? Are you specifying a -data
> argument there or on the command line (eg, in a Windows shortcut)?

Does Fedora use the eclipse.ini file? Do you want
me to dump the file here? Please let me know...

Also, if there is anything I can provide you let me know.
I am tempted to re-install Galileo again and see what gives
but I will leave the original Galileo if you want in order
to discover why it failed? Again, please let me know.

>
> Eric

Thanks!
Dan
Re: Galileo: Startup/Shudown interface does not work. [message #336879 is a reply to message #336877] Wed, 08 July 2009 23:08 Go to previous messageGo to next message
Dan Thurman is currently offline Dan Thurman
Messages: 57
Registered: July 2009
Member
On Wed, 08 Jul 2009 21:48:32 +0200, Yves Schumann wrote:

> Hi Dan
>
> Dan Thurman schrieb:
>> Galileo perhaps has a problem with the Startup/Shutdown mechanism:
>
> Works nice on a lot of installations here...
>
> Just an idea: Is it possible that you have (some) write protected files
> inside of your installation or inside of the workspace?

No write protect problems AFAIK since I use both
Ganymede and Galileo on the same test workspace,
one at a time of course... ;)

Dan
Re: Galileo: Startup/Shudown interface does not work. [message #336892 is a reply to message #336878] Fri, 10 July 2009 06:00 Go to previous messageGo to next message
Achim Loerke is currently offline Achim Loerke
Messages: 314
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

On Thu, 9 Jul 2009 03:07:31 +0000 (UTC), Dan Thurman <dant@cdkkt.com>
wrote:

Comments below

>First off, I am running Eclipse on Fedora 9, not M$.
>

To remove obvious problems: are you sure that you're not using gcj
(the "native" java runtime) of Fedora? This is normally linked to
/usr/bin/java and will be used by Eclipse if you don't specify another
JVM. gcj is not supported and causes all kinds of strange behaviour.

>
>>
>> What does your eclipse.ini look like? Are you specifying a -data
>> argument there or on the command line (eg, in a Windows shortcut)?
>
>Does Fedora use the eclipse.ini file? Do you want
>me to dump the file here? Please let me know...
>

Since the JVM is specified in the eclipse.ini it would be helpful to
see its contents.


Achim
--
Achim Lörke

Eclipse-Stammtisch in the Braunschweig, Germany area:
http://www.bredex.de/de/news/events.html


Achim Lörke

Jubula Funtional Testing Tool:http://www.eclipse.org/proposals/jubula
Eclipse-Stammtisch Braunschweig: http://www.bredex.de/de/news/eclipse.html
Re: Galileo: Startup/Shudown interface does not work. [message #336895 is a reply to message #336892] Fri, 10 July 2009 10:24 Go to previous messageGo to next message
Dan Thurman is currently offline Dan Thurman
Messages: 57
Registered: July 2009
Member
On Fri, 10 Jul 2009 12:00:12 +0200, Achim Lörke wrote:

> On Thu, 9 Jul 2009 03:07:31 +0000 (UTC), Dan Thurman <dant@cdkkt.com>
> wrote:
>
> Comments below
>
>>First off, I am running Eclipse on Fedora 9, not M$.
>>
>>
> To remove obvious problems: are you sure that you're not using gcj (the
> "native" java runtime) of Fedora? This is normally linked to
> /usr/bin/java and will be used by Eclipse if you don't specify another
> JVM. gcj is not supported and causes all kinds of strange behaviour.
>

# java -version
java version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b09)
OpenJDK Server VM (build 1.6.0-b09, mixed mode)


And, here is eclipse.ini:

Ganymede:
===============================================
# cat eclipse.ini
-showsplash
org.eclipse.platform
-framework
plugins/org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
===============================================

Galileo:
===============================================
# cat eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v 20090520
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=256m
-Xms40m
===============================================

>
>>
>>> What does your eclipse.ini look like? Are you specifying a -data
>>> argument there or on the command line (eg, in a Windows shortcut)?
>>
>>Does Fedora use the eclipse.ini file? Do you want me to dump the file
>>here? Please let me know...
>>
>>
> Since the JVM is specified in the eclipse.ini it would be helpful to see
> its contents.
>
>
> Achim
Re: Galileo: Startup/Shudown interface does not work. [message #336915 is a reply to message #336895] Mon, 13 July 2009 09:49 Go to previous messageGo to next message
Eclipse User
Originally posted by: eclipse-news.rizzoweb.com

Dan Thurman wrote:
> On Fri, 10 Jul 2009 12:00:12 +0200, Achim Lörke wrote:
>
>> On Thu, 9 Jul 2009 03:07:31 +0000 (UTC), Dan Thurman <dant@cdkkt.com>
>> wrote:
>>
>> Comments below
>>
>>> First off, I am running Eclipse on Fedora 9, not M$.
>>>
>>>
>> To remove obvious problems: are you sure that you're not using gcj (the
>> "native" java runtime) of Fedora? This is normally linked to
>> /usr/bin/java and will be used by Eclipse if you don't specify another
>> JVM. gcj is not supported and causes all kinds of strange behaviour.
>>
>
> # java -version
> java version "1.6.0"
> OpenJDK Runtime Environment (build 1.6.0-b09)
> OpenJDK Server VM (build 1.6.0-b09, mixed mode)

The first thing I suggest is using the Sun "official" JDK instead of
OpenJDK. I don't think Eclipse is tested against OpenJDK and there could
be incompatibilities. And make sure to specify the JVM in eclipse.ini,
as described here: http://wiki.eclipse.org/Eclipse.ini

I would rule that out before going any further.

Eric


>
>
> And, here is eclipse.ini:
>
> Ganymede:
> ===============================================
> # cat eclipse.ini
> -showsplash
> org.eclipse.platform
> -framework
> plugins/org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Xms40m
> -Xmx512m
> -XX:MaxPermSize=256m
> ===============================================
>
> Galileo:
> ===============================================
> # cat eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v 20090520
> -product
> org.eclipse.epp.package.jee.product
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -XX:MaxPermSize=256m
> -Xms40m
> ===============================================
>
>>>> What does your eclipse.ini look like? Are you specifying a -data
>>>> argument there or on the command line (eg, in a Windows shortcut)?
>>> Does Fedora use the eclipse.ini file? Do you want me to dump the file
>>> here? Please let me know...
>>>
>>>
>> Since the JVM is specified in the eclipse.ini it would be helpful to see
>> its contents.
>>
>>
>> Achim
Re: Galileo: Startup/Shudown interface does not work. [message #336977 is a reply to message #336871] Fri, 17 July 2009 17:20 Go to previous message
Stephan Herrmann is currently offline Stephan Herrmann
Messages: 927
Registered: July 2009
Senior Member
> 1) On startup, Galileo does not prompt user
> for workspace selection and immediately
> defaults to: $HOME/workspace.
there is a bug whereby this result can in fact happen quasi
non-deterministically:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204829
In short: org.eclipse.core.resources and org.eclipse.ui.ide.application each
have their strategy for initializing the "instance location" (the path of
your workspace). core.resources always uses $HOME/workspace whereas
ide.application prompts with a dialog. Which strategy is used is purely
based on initialization order of these plugins.

If for some reason any plugin accesses core.resources before ide.application
had a chance to put up the dialog $HOME/workspace will be used and
ide.application considers this just as if -data somedir would have been
passed on the command line (which you could use as a workaround, no?)

To find out whether this might explain the behavior you're seeing,
would should probably activate some tracing to see the order of bundle
loading/activation. I could imagine the following lines in an .options
file could do the job:

org.eclipse.osgi/debug=true
org.eclipse.osgi/trace/activation=true

see also "Turning on debug tracing" at
http://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_ tracing_facility%3F

In the output I'd expect "->started org.eclipse.ui.ide" to come BEFORE
"->started org.eclipse.core.resources" for normal behavior. Otherwise you
might indeed see bug 204829.


best,
Stephan
Previous Topic:ctrl+c/v/x in Eclipse 3.5
Next Topic:ClassCircularityError on IConfigurationElement.createExecutableExtension in Eclipse 3.5
Goto Forum:
  


Current Time: Mon Apr 21 03:15:09 EDT 2014

Powered by FUDForum. Page generated in 0.06460 seconds