Project

General

Profile

Bug #5031

Fail to switch to other suite from module manager of Kepler-2.0-RC3

Added by Lei Dou about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
core
Target version:
Start date:
05/27/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5031

Description

In the newly installed Kepler-2.0-RC3 on windows vista, I want to switch to comad-exp-1.0.0 suite from the default kepler suite.

The steps are:
1. open the module manager
2. choose the comad-exp-1.0.0 from the availabel suites and click the right arrow. The comad-exp-1.0.0 appears in the "Selected Modules".
3. click the button of "Apply and Restart".

The expected result is: The original opened Kepler window is closed and a new window is started.

The current situation is: The button of "Apply and Restart" is disabled. Then the system hangs on here. Nothing happens any more.

I tried it on linux(CentOS) and Mac(OS X 10.5.8) and there's no such problem.


Related issues

Blocked by Kepler - Bug #4943: RC5 Installer Tracking BugResolved04/19/2010

History

#1 Updated by David Welker about 10 years ago

This is an important bug that should block the release.

#2 Updated by David Welker about 10 years ago

We will look more at this bug after release candidate 4.

#3 Updated by Derik Barseghian about 10 years ago

David, I went to test this on RC4 w/ Vista but the only suite listed at the moment under Available Suites: is kepler-2.0.0 (as expected, I don't think others are published at the moment). I was able to select kepler-2.0.0 and Apply and Restart, and Kepler restarted as one would hope.

#4 Updated by David Welker about 10 years ago

It looks like this is working in RC4 on Lei's machine under Windows Vista too. The origins of this problem remain unknown. Closing this bug.

#5 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 5031

Also available in: Atom PDF