> Another thing: try to move your ~/.sage/ away
awesome, that worked -- thanks!
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegrou
Another thing: try to move your ~/.sage/ away and see if this allows you to
start Sage.
On Thursday, June 21, 2018 at 7:58:03 AM UTC+1, Christian Stump wrote:
>
> > Either you updated the system, or you updated the (shell) environment,
> or your disk/swap is almost full, or your hardware is dyi
$ printenv
CLUTTER_IM_MODULE=xim
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;
01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;
42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=
01;31:*.lha=01;31:*.lz4=01;31:*.lzh=0
> Either you updated the system, or you updated the (shell) environment, or
your disk/swap is almost full, or your hardware is dying, or worse...
It doesn't seem as if any of these apply -- any idea what I could check to
find the issue? Note that I can start python sage's python normally, see
a
Either you updated the system, or you updated the (shell) environment, or
your disk/swap is almost full, or your hardware is dying, or worse...
On Wednesday, June 20, 2018 at 7:34:22 PM UTC+1, Christian Stump wrote:
>
> Hi,
>
> since today, I cannot start sage anymore, not even on a freshly comp
> some interesting env var set?
not actively, looking through them doesn't show anything that seems sage
related.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
