Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 216884 - gcl: xmaxima can't open socket
gcl: xmaxima can't open socket
Product: Fedora
Classification: Fedora
Component: gcl (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Gérard Milmeister
Fedora Extras Quality Assurance
Depends On:
Blocks: 216539
  Show dependency treegraph
Reported: 2006-11-22 10:05 EST by Rex Dieter
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-28 13:34:19 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rex Dieter 2006-11-22 10:05:53 EST
+++ This bug was initially created as a clone of Bug #216539 +++

Description of problem:

I can use maxima in the console, but if i start xmaxima i get this error message:

Maxima 5.10.0 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.
This is a development version of Maxima. The function bug_report()
provides bug reporting information.
(%i1) jfa: starting server on port 4008
couldn't open socket:

Installed packages:
maxima 5.10.0-8.fc6.i386
maxima-gui 5.10.0-8.fc6.i386
maxima-runtime-gcl 5.10.0-8.fc6.i386

-- Additional comment from rdieter@math.unl.edu on 2006-11-22 09:59 EST --
Looks like we're not alone, Ubuntu has the same problem:

Their recommendations were to use a different maxima-runtime (one of
maxima-runtime-clisp, maxima-runtime-cmucl, maxima-runtime-sbcl).

-- Additional comment from rdieter@math.unl.edu on 2006-11-22 10:04 EST --
Upon closer inspection of ubuntu's report, they claim it to be a gcl bug, see
Comment 1 Rex Dieter 2006-11-28 13:34:19 EST
closing this (for now), as the bug that prompted it seems to be not reproducible.

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