Bug 223313 - sci-visualization/qtiplot-0.9.6.2 working issues
Bug#: 223313 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: RESOLVED Severity: normal Priority: P2
Resolution: INVALID Assigned To: cryos@gentoo.org Reported By: urcindalo@gmail.com
Component: Applications
URL: 
Summary: sci-visualization/qtiplot-0.9.6.2 working issues
Keywords:  
Status Whiteboard: 
Opened: 2008-05-23 08:36 0000
Description:   Opened: 2008-05-23 08:36 0000
First af all, I don't really know where to file these bugs, so I apologize if
this is not the best way. Additionally, I don't know if they affect all version
of qtiplot, since I have only stumbled upon them in 0.9.6.2. They are:

1) I had to upgrade sci-libs/gsl from 1.9 to 1.11 and then re-emerge
pygsl-0.9.0 and qtiplot-0.9.6.2 in order to eliminate the pyhton errors
appearing in qtiplot's console upon launching. (I use python 2.5.2-r4).

2) Qtiplot's config files are installed in /urs/local/qtiplot. However, if this
directory is own by root:root and its permissions are drwxr-xr-x, qtiplot can't
create the files qtiplotrc.pyc and qtiUtil.pyc inside it for a regular user at
launch time. I had to manually modify the permissions to drwxrwxrwx for qtiplot
to work correctly.

3) Unless qtiplot is launched from a terminal inside the /usr/local/qtiplot
directory, qtiUtil.py is NOT correctly loaded. You get this error in qtiplot's
console: "Failed to import qtiUtil file!". But, if the command "qtiplot" is
invoked from within /usr/local/qtiplot, then the file is loaded: "qtiUtil file
successfully imported!"

And that's pretty much it. These issues don't prevent a user from a basic usage
of this program. But if you want to create your own python functions and add
them to the 'Set column values' function pop-up menu through qtiUtil.py, for
instance, they are of capital importance.

Thanks for reading this.

Reproducible: Always

------- Comment #1 From Jeroen Roovers 2008-05-24 16:02:16 0000 -------
It would have been better to file one bug report for each bug.

------- Comment #2 From urcindalo 2008-05-26 10:54:47 0000 -------
OK. I'm gonna do that :)

------- Comment #3 From Andrey Grozin 2008-05-27 21:21:55 0000 -------
This bug has been replaced by the bugs #223671, #223673, #223665