Bug 1045044 - Sagemath crashes after reinstallation
Summary: Sagemath crashes after reinstallation
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: sagemath
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Paulo Andrade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 14:15 UTC by maldun.finsterschreck
Modified: 2013-12-19 21:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-19 16:49:06 UTC
Type: Bug


Attachments (Terms of Use)
Crash report of sage (12.59 KB, text/plain)
2013-12-19 14:15 UTC, maldun.finsterschreck
no flags Details

Description maldun.finsterschreck 2013-12-19 14:15:03 UTC
Created attachment 839000 [details]
Crash report of sage

Description of problem:

Sage fails after deinstallation and reinstallation

Version-Release number of selected component (if applicable):
5.9-9.fc19

How reproducible:
Install sage with yum, deinstall and reinstall it

Steps to Reproduce:
1. yum install sagemath
2. yum remove sagemath
3. yum install sagemath
4. sage

Actual results:

[reiteres@localhost:~/.config/ipython]$ sage
/usr/bin/sage: line 14: module: command not found
/usr/bin/sage: line 15: module: command not found
----------------------------------------------------------------------
| Sage Version 5.9, Release Date: 2013-04-30                         |
| Type "notebook()" for the browser-based notebook interface.        |
| Type "help()" for help.                                            |
----------------------------------------------------------------------

**********************************************************************

Oops, Sage crashed. We do our best to make it stable, but...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current Sage configuration.

It was left in the file named:
        '/home/reiteres/.config/ipython/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will help
them in understanding and correcting the problem.

You can mail it to: sage-support at sage-support
with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-support < /home/reiteres/.config/ipython/Sage_crash_report.txt

To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org/sage_trac

Hit <Enter> to quit (your terminal may close):

Expected results:

----------------------------------------------------------------------
| Sage Version 5.9, Release Date: 2013-04-30                         |
| Type "notebook()" for the browser-based notebook interface.        |
| Type "help()" for help.                                            |
----------------------------------------------------------------------
sage:

Additional info:

Crash report attached

Comment 1 Paulo Andrade 2013-12-19 16:49:06 UTC
The lines

/usr/bin/sage: line 14: module: command not found
/usr/bin/sage: line 15: module: command not found

are very suspicious. It appears some packages (at
least environment-modules) were removed with --nodeps
what caused the "toplevel" only rpm dependencies to
be reinstalled.

I just did the procedures, install, remove, install
again, in a f19 computer and it works.

It is possible that you have some wrong files or
symlinks from very earlier sagemath packages that
had a bug with upgrades. To ensure it is not older
files around, remove sagemath, and then remove
anything under

/usr/share/sagemath

and

/usr/lib64/sagemath # for x86_64
/usr/lib/sagemath # for i586

and install sagemath again.

Comment 2 maldun.finsterschreck 2013-12-19 17:12:28 UTC
Indeed I use --nodeps for a problem with the nvidia drivers, but I do not know ho this is related to sage.

I now removed all files you suggested, but the problem still persists.

Thank you nevertheless

Comment 3 Paulo Andrade 2013-12-19 21:29:33 UTC
You can try something like

rpm -V `rpm -qa`

http://www.rpm.org/max-rpm/ch-rpm-verify.html


Note You need to log in before you can comment on or make changes to this bug.