Thanks, DLD. I did try clearing the cache, but it made no difference. It is probably something like that, anyway. Something that did happen when I had notebooks running in chrome is that error messages would pop up saying that it could not auto-save the notebook. (Obviously I do have write permission in the directory from which I am running sage --notebook).
But anyway, firefox works fine, and I may bother to look up how to get sage to use it instead of chrome on my laptop (unless some kind person who knows tells me first...) John On Mon, 31 Mar 2025 at 16:15, David Lowry-Duda <da...@lowryduda.com> wrote: > > On 14:24 Mon 31 Mar 2025, John Cremona wrote: > >This is only with chrome, firefox is fine. And it did work (in > >chrome) last Friday after I fixed the permissions of /usr/local/share, > >which is mysterious! > > I wonder if this is a funny Chrome cache issue. Perhaps Chrome checks > localstorage for some outdated token? Does Chrome work if you try to access > the url from an incognito window? If so, then clearing the cache might work. > > - DLD > > -- > You received this message because you are subscribed to a topic in the Google > Groups "sage-support" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sage-support/ec1H4p4SIGY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > sage-support+unsubscr...@googlegroups.com. > To view this discussion visit > https://groups.google.com/d/msgid/sage-support/Z-qxieMC4EPsSdZs%40icerm-dld. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-support/CAD0p0K7mL2ZBXfss_TdCT5epY-7MeQ-ZeLU9sb%2BZk2CMdgi5%3DA%40mail.gmail.com.
