Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash after very specific reinstallation steps #6123

Closed
PeterParker opened this issue May 4, 2012 · 3 comments
Closed

Crash after very specific reinstallation steps #6123

PeterParker opened this issue May 4, 2012 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@PeterParker
Copy link
Contributor

This issue was originally TRAC 5277

Owen - Nick suggested that you may be uniquely suited to look into this one due to your work with the installers, so assigning to you for now if that's ok.

Originally reported under http://trac.mantidproject.org/mantid/ticket/5198, but that has morphed into a ticket covering a different issue, so raising again here.

Observed on Windows 7, with 64-bit installer. To reproduce:

  • To make sure we start with a clean slate, uninstall Mantid and then delete (or rename) the MantidInstall directory, then reinstall it.
  • Uninstall Mantid again, but this time only delete the ''contents'' of the MantidInstall directory.
  • Now reinstall Mantid, and then try to change the facility / instrument via the preferences dialog. An unexpected exception occurs.

Marked as minor since you have to jump through several hoops to get to this point.

@PeterParker
Copy link
Contributor Author

@NickDraper (2012-08-10T12:45:15):
http://www.mantidproject.org/Release_Notes_2_2_Full_List


@NickDraper (2012-10-28T11:42:54):
Moved to release 2.4


@NickDraper (2013-01-28T09:23:34):
Moved at the code freeze for release 2.4


@NickDraper (2013-04-29T09:50:08):
Moved to r2.6 at the end of r2.5


@NickDraper (2013-07-26T13:59:11):
Moved to the Backlog after the code freeze for R2.6


@NickDraper (2014-02-14T11:07:57):
bulk move to assigned at the into of the triage step

@PeterParker PeterParker added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

2 participants