Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21684 - [grass] can not start in wxpython gui

Attached to Project: Community Packages
Opened by Huub Munstege (HuMu) - Saturday, 13 November 2010, 08:57 GMT
Last edited by Thomas Dziedzic (tomd123) - Saturday, 13 November 2010, 18:24 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Grass 6.4.0-4 can not start in wxpython gui. Probably is related with the python 3.0 upgrade.

Additional info:
* package version: 6.4.0-4

Steps to reproduce:
start grass64 in terminal gives this error:

grass64
"Cleaning up temporary files ...
Starting GRASS ...
File "/opt/grass-6.4.0/etc/wxpython/gis_set.py", line 474
except StandardError, e:
^
SyntaxError: invalid syntax
Error in GUI startup. If necessary, please
report this error to the GRASS developers.
Switching to text mode now.
Hit RETURN to continue..."
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Saturday, 13 November 2010, 18:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  6.4.0-5
Comment by Ionut Biru (wonder) - Saturday, 13 November 2010, 10:08 GMT
that is a python issue and i think that file doesn't have a python2 shebang
Comment by Thomas Dziedzic (tomd123) - Saturday, 13 November 2010, 13:56 GMT
Can you check if adding a "#!/usr/bin/env python2" string at the very top of that file fixes it?
Comment by Huub Munstege (HuMu) - Saturday, 13 November 2010, 14:57 GMT
Sorry that doesn't work : same error message
Comment by Thomas Dziedzic (tomd123) - Saturday, 13 November 2010, 15:01 GMT
ok, I think I fixed it in 6.4.0-5, it worked for me, can you try? (wait for it to get synced to the mirrors)

Loading...