Maxima does not start

[Ángela]

Binary package hint: maxima

user@host:~$ maxima

Maxima 5.17.1 http://maxima.sourceforge.net
Using Lisp GNU Common Lisp (GCL) GCL 2.6.7 (aka GCL)
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1)
Maxima encountered a Lisp error:

 Error in PROGN [or a callee]: Couldn't protect

Automatically continuing.
To reenable the Lisp debugger set *debugger-hook* to nil.
(%i1) xmalloc: out of virtual memory
user@host:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
user@host:~$ apt-cache policy maxima
maxima:
  Instalados: 5.17.1-1ubuntu1
  Candidato: 5.17.1-1ubuntu1
  Tabla de versión:
 *** 5.17.1-1ubuntu1 0
        500 http://es.archive.ubuntu.com karmic/universe Packages
        500 http://de.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status
user@host:~$

ProblemType: Bug
Architecture: amd64
Date: Wed Mar 3 16:46:57 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: maxima 5.17.1-1ubuntu1
ProcEnviron:
 LANGUAGE=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: maxima
Uname: Linux 2.6.31-20-generic x86_64
XsessionErrors:
 (npviewer.bin:2240): Gdk-WARNING **: XID collision, trouble ahead
 (npviewer.bin:2240): Gdk-WARNING **: XID collision, trouble ahead
 (npviewer.bin:2240): Gdk-WARNING **: XID collision, trouble ahead

[Tyler Tinkler (tyler-g-tinkler)]

Installing maxima-share on 8.10 fixed this problem for me.

[themusicgod1 (themusicgod1)]

Like #261056 the upstream bug at debian (linked, now), Camm Maguire mentions what the cause of this is and requests more information on how it was triggered - ie the particulars of the kernel and the settings for why memory pages are not writeable. That was 7 years ago and many versions ago, though. If you can reproduce this on trusty+ it might be worth investigating what kernel/security settings are triggering this, otherwise marking as incomplete.