-
-
Notifications
You must be signed in to change notification settings - Fork 47
SageMath Console not displaying the "sage:" prompt #58
Comments
update: I've waited for an hour and it's still not showing the prompt :( |
@Weierstrash Some antivirus programs interfere with Sage. Do you have any running? |
thanks for the reply. I had avast running but I disabled it. The issue still persists. Should I completely uninstall the antivirus? |
update: I've completely uninstalled the antivirus and restarted my laptop; the issue still persists. |
@Weierstrash You don't need to fully remove or even disable your antivirus. Avast has been a problem in the past with quarantining false positives from Sage. You can read these instructions on how to add a directory to be excluded from Avast's scans, and should apply it to the directory where Sage is installed (typically something like Chances are it deleted/quarantined some files, so the best thing to do is add an exclusion, then re-install Sage. |
This is what I did: I completely uninstalled the antivirus, then re-installed sage. Unfortunately, the issue still persists. |
That is bizarre. Did you have a previous Sage version that you were already using previously? If you run the "Sage Shell" shortcut does the shell prompt come up? If so, what happens if you run |
I'm installing sage for the first time on my laptop. When I run the "Sage Shell", the prompt doesn't show up. The same happens when I try to open "Sage Notebook Server". I just hope I don't have to reinstall windows to fix this :( |
Well, no, don't do that. But that the shell prompt doesn't even come up suggests the problem is with something beyond sage. If you just install plain cygwin by itself, are you able to launch the cygwin shell? (Sage for Windows is really just a distribution of Cygwin with Sage included). |
I don't think so--that's normal as far as I can tell. |
@guraltsev Thank you for the insight. That's very strange. I'm not sure why ccache would be running at all. It would have to be because something is calling gcc (to which ccache is linked), but I'm not sure why anything would be doing that during startup. If you run the "SageMath Shell" shortcut (I think it's called) which just opens a bash shell, can you see if there's a ccache directory in your home directory?
And if so, try deleting that and see if helps anything:
|
Also, some other things about my Windows 10 installation: I do not have cygwin installed (though I think I did some time ago and it worked). I have msys2 installed and it works perfectly. I tried disabling Windows defender (antivirus) and nothing changes. |
I just tried the same thing on a different windows machine and the problem is the same. To be fair, though, the configurations of the two machines are similar (not identical). |
@guraltsev Ah, your sleuthing at least reveals why the heck gcc is being run at all, which was confusing me. It happens during setup of the Sage shell environment, in a line that runs That does not explain why gcc is freezing, especially on such a trivial command. What happens if, after launching the shell, you hit Ctrl-C a couple times? Do you get a shell prompt? If so, what happens when you run |
Ctrl-C just closes the window. |
@guraltsev What if you run mintty directly? |
So, I launched the mintty sage by running the same command as in the sage shortcut:
This gives me a tty prompt When running
it gives the output
Now, if I enable |
I think the problem definitely seems related to ccache for some reason. What if you set the environment variable:
and then run
? |
It works! So, now what? Edit: I realize that the original might have come off as rude. I wanted to say that with your suggestion of
(for e.g. the sage notebook). Please let me know if I can further debug and provide information about my system to troubleshoot the issue |
I recently downloaded version 9.2 SageMath for my windows 10 laptop. However, when I try to open the SageMath console, it doesn't display the "sage:" prompt and is stuck on the following screen:
Can someone tell me what's going on?
The text was updated successfully, but these errors were encountered: