Description: Guidance is a collection of system administration tools for Linux/KDE systems that is designed to be:
* Update to date
* High quality, designed with user friendlyness as high priority. That is to say that the tools should get the job done quickly, accurately and with as little effort as possible.
* Aimed at the Linux "desktop".
* Built on KDE.
* Maintainable.
* Free Software.
Development version.Last changelog:
* Displayconfig working and almost feature complete.
* xf86config C module has been removed and replaced with pure Python.
* Numerous little bugs fixed in the userconfig, mountconfig and serviceconfig.
I get follow error trace from displayconfig from guidance 0.6.4:
[root@hagar ~]# displayconfig
kbuildsycoca running...
Traceback (most recent call last):
File "/usr/bin/displayconfig", line 1699, in ?
displayapp = DisplayApp()
File "/usr/bin/displayconfig", line 443, in __init__
self.xsetup = XSetup(self.xconfigpath)
File "/usr/share/apps/guidance/displayconfigabstraction.py", line 363, in __init__
self._finalizeInit()
File "/usr/share/apps/guidance/displayconfigabstraction.py", line 368, in _finalizeInit
gfxcard._finalizeInit()
File "/usr/share/apps/guidance/displayconfigabstraction.py", line 971, in _finalizeInit
self.gfxcard_model = GetGfxCardModelDB().getGfxCardModelByName(self.x_device[0].boardname)
File "/usr/share/apps/guidance/displayconfigabstraction.py", line 2321, in getGfxCardModelByName
return self.db[name]
KeyError: u'nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro]'
PyKDE version is 3.11.4-0.3 with extensions version 0.4.0 running under Fedora 5.
Can you email the author directly (simon@simonzone.com) with this error message and also say what distro you are using and which version libtool you have. (in the shell run "libtool --version" to find out what version it is).
then we start working out what is going on and what the solution is.
thanks,
--
Simon
KDE needs more possibilities to configure the system.
At the moment you are forced to use distribution-own tools.
And the structure of the system-services is much better than the structure of ksysv!
Keep at it :)
There are too many things that need to be added/compiled to make this work. It would be best if you can make this work without requiring the extras. Having to compile 3 different apps is bad. The odds of a failure of a compile increase significantly. Yes, it increased to the point that I failed on the compile. This is not a good thing. Then to have the third package require me to post errors to a mailing list is stupidity at its greatest.
It makes me exposed to a group of individuals I don't want to be exposed to and it shows that the author of the programs don't want to assume responsibility for their work. Take ownership and make it work, make it work right and make it work the first time.
Hi catmandu, BorqQueen,
First, thank you for taking the time to test guidance.
As to your problems, we'd love to get more detailed feedback on them, that is: At what point did compilation fail? What distro are you using, which versions of software guidance needs do you have installed on your system? What tools did were you going to compile 'by hand'? (For most distros there are packages for SIP, PyQt, PyKDE). libpythonize is needed if you want to run the applications from withing kcontrol, so that might be a candidate. (There's work going on to get that prepackaged also.)
As you might have noticed, we're still working on it, guidance is currently pre-beta, so it's no more than natural that there are issues around. We did this release in order to get aware of these issues still left and be able to fix them.
As to the dependencies you're complaining about: guidance is meant to get included in distros, so the packaging and installation / compilation of the dependencies will be nothing the end user ever will have to care about, compiling system administration tools is clearly developer's work, and you're testing beta software ...
Quite frankly, I'm wondering why it's stupidity to ask you to post feedback with errors to a mailinglist? It gives you the opportunity to get feedback from the people responsible for the errors you're getting. PyKDE is a good place to go with this kind of problems, the list is very responsive and there are people that are familiar with more and less common issues, and not at least we as the developers are around there also. You shouldn't be afraid that you're bothering people who don't want to have anything to do with it, they'll just ignore your posting.
KDE is a community based project, we're doing nothing but offering software, putting our free time in it, and I might add that guidance is working quite good for me. Without testers like you, we'd probably not be able to deliver a quality product.
Again, thanks for your feedback, and a little patience and more productive feedback would certainly be helpful. :-)
Lemme tell you guys that I am quite disappointed to see such comments. Sebas could well be quite upset and disgusted by your attitude, Catmandu and BorgQueen.
*Your comment* is stupidity as its greatest, Catmandu. Who are you to tell people what they should do? Sebas wrote a software. He didn't have to. So YOU have to abide by HIS rule. Period. If you're not happy, go buy Microsoft products, so you can be ignored by their hotline.
I'm impressed Sebas manages to respond calmly and kindly to such silly posts.
While compiling I'm getting errors starting from:
serviceconfig/kcm_serviceconfig.cpp:11:23: pythonize.h: No such file or directory
I'm using Debian unstable. There is no package providing that file on the official mirror. Google returns merely 10 hits for word pythonize, most of them are about errors too:)
So, my question is where can I find the relevant library and include files?
man you're God :D
debian seriously lacks things like this, and I whould love to see more administration tools. especially the system services tool is cool!
keep up the good work!
Ratings & Comments
15 Comments
I get follow error trace from displayconfig from guidance 0.6.4: [root@hagar ~]# displayconfig kbuildsycoca running... Traceback (most recent call last): File "/usr/bin/displayconfig", line 1699, in ? displayapp = DisplayApp() File "/usr/bin/displayconfig", line 443, in __init__ self.xsetup = XSetup(self.xconfigpath) File "/usr/share/apps/guidance/displayconfigabstraction.py", line 363, in __init__ self._finalizeInit() File "/usr/share/apps/guidance/displayconfigabstraction.py", line 368, in _finalizeInit gfxcard._finalizeInit() File "/usr/share/apps/guidance/displayconfigabstraction.py", line 971, in _finalizeInit self.gfxcard_model = GetGfxCardModelDB().getGfxCardModelByName(self.x_device[0].boardname) File "/usr/share/apps/guidance/displayconfigabstraction.py", line 2321, in getGfxCardModelByName return self.db[name] KeyError: u'nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro]' PyKDE version is 3.11.4-0.3 with extensions version 0.4.0 running under Fedora 5.
New version, same error: libtool --mode=compile c++ -pthread -c -g -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/usr/include -I/usr/include -I/usr/include/python2.4 -I/usr/include/python2.4 -I/usr/include -I/usr/lib/qt-3.3/include -I. serviceconfig/kcm_serviceconfig.cpp -o serviceconfig/serviceconfig.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' error: command 'libtool' failed with exit status 1
Can you email the author directly (simon@simonzone.com) with this error message and also say what distro you are using and which version libtool you have. (in the shell run "libtool --version" to find out what version it is). then we start working out what is going on and what the solution is. thanks, -- Simon
Have you installed pythonize.h? I was installed them and this error disapear.
KDE needs more possibilities to configure the system. At the moment you are forced to use distribution-own tools. And the structure of the system-services is much better than the structure of ksysv! Keep at it :)
There are too many things that need to be added/compiled to make this work. It would be best if you can make this work without requiring the extras. Having to compile 3 different apps is bad. The odds of a failure of a compile increase significantly. Yes, it increased to the point that I failed on the compile. This is not a good thing. Then to have the third package require me to post errors to a mailing list is stupidity at its greatest. It makes me exposed to a group of individuals I don't want to be exposed to and it shows that the author of the programs don't want to assume responsibility for their work. Take ownership and make it work, make it work right and make it work the first time.
Agreed
Hi catmandu, BorqQueen, First, thank you for taking the time to test guidance. As to your problems, we'd love to get more detailed feedback on them, that is: At what point did compilation fail? What distro are you using, which versions of software guidance needs do you have installed on your system? What tools did were you going to compile 'by hand'? (For most distros there are packages for SIP, PyQt, PyKDE). libpythonize is needed if you want to run the applications from withing kcontrol, so that might be a candidate. (There's work going on to get that prepackaged also.) As you might have noticed, we're still working on it, guidance is currently pre-beta, so it's no more than natural that there are issues around. We did this release in order to get aware of these issues still left and be able to fix them. As to the dependencies you're complaining about: guidance is meant to get included in distros, so the packaging and installation / compilation of the dependencies will be nothing the end user ever will have to care about, compiling system administration tools is clearly developer's work, and you're testing beta software ... Quite frankly, I'm wondering why it's stupidity to ask you to post feedback with errors to a mailinglist? It gives you the opportunity to get feedback from the people responsible for the errors you're getting. PyKDE is a good place to go with this kind of problems, the list is very responsive and there are people that are familiar with more and less common issues, and not at least we as the developers are around there also. You shouldn't be afraid that you're bothering people who don't want to have anything to do with it, they'll just ignore your posting. KDE is a community based project, we're doing nothing but offering software, putting our free time in it, and I might add that guidance is working quite good for me. Without testers like you, we'd probably not be able to deliver a quality product. Again, thanks for your feedback, and a little patience and more productive feedback would certainly be helpful. :-)
Lemme tell you guys that I am quite disappointed to see such comments. Sebas could well be quite upset and disgusted by your attitude, Catmandu and BorgQueen. *Your comment* is stupidity as its greatest, Catmandu. Who are you to tell people what they should do? Sebas wrote a software. He didn't have to. So YOU have to abide by HIS rule. Period. If you're not happy, go buy Microsoft products, so you can be ignored by their hotline. I'm impressed Sebas manages to respond calmly and kindly to such silly posts.
Same too!
i get the same libtool error as above
While compiling I'm getting errors starting from: serviceconfig/kcm_serviceconfig.cpp:11:23: pythonize.h: No such file or directory I'm using Debian unstable. There is no package providing that file on the official mirror. Google returns merely 10 hits for word pythonize, most of them are about errors too:) So, my question is where can I find the relevant library and include files?
Info and help: http://www.simonzone.com/software/guidance/ -- Simon
KDE still lacks common linux config tools
man you're God :D debian seriously lacks things like this, and I whould love to see more administration tools. especially the system services tool is cool! keep up the good work!