Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 170403 - texmacs does not work with the Fedora extras maxima package
texmacs does not work with the Fedora extras maxima package
Product: Fedora
Classification: Fedora
Component: TeXmacs (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Gérard Milmeister
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2005-10-11 08:09 EDT by Luis
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: 2005-10-11 15:57:12 EDT
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 Luis 2005-10-11 08:09:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7

Description of problem:
The script /usr/share/TeXmacs/bin/tm_maxima used by TeXmacs to use itself as a graphical interface to maxima does not recognize the current maxima package.

Maxima presents itself as maxima- (current version). But the above script only recognizes the following versions
So it cannot identify maxima properly and Texmacs hangs

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.open TaXmacs
2.Insert --> Session --> Maxima (maxima installed)

Actual Results:  texmacs hangs

Expected Results:  3 

Additional info:

The following patch on /usr/libexec/TeXmacs/bin/tm_maxima works fine on my system

<* | 5.9.2*) exec maxima -u $1 -l $2 -p "$TEXMACS_MAXIMA_PATH/texmacs-maxima-5.9.2.lisp";;
> 5.9.1.* | 5.9.2*) exec maxima -u $1 -l $2 -p "$TEXMACS_MAXIMA_PATH/texmacs-maxima-5.9.2.lisp";;
Comment 1 Gérard Milmeister 2005-10-11 15:57:12 EDT
Thanks for notifying.

I will submit a new build ASAP.

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