From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:184.108.40.206) Gecko/20070530 Fedora/220.127.116.11-1.fc6 Firefox/18.104.22.168
Description of problem:
On first starup, Quantum GIS is looking for plugins at the following path:
This path is non-existent on my system. The plugins are actually located in the following directory:
If I change the Plugin Directory to this path in the Plugin Manager dialog box, all the installed plugins are displayed. If I click the 'OK' button and re-open the dialog box, however, I receive a warning message that there are No Plugins (see attached file: no_plugins.png) because the Plugin Manager is again looking in:
for the plugins.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start Quantun GIS
2.Select Plugins->Plugin Manager...
3.Change the Plugin Directory path
4.Click the 'OK' button
5.Select Plugins->Plugin Manager...
The Plugin Directory changed back to the default.
The new Plugin Directory should have been persisted.
If after changing the Plugin Directory, all of the installed plugins are selected. new menu entries appear under the Plugins top level menu. While the Plugin Directory is forgotten the next time the Plugin Manager is opened, Quantum GIS remembers which plugins have been selected. However, this information is forgotten if Quantum GIS is re-started.
Created attachment 158815 [details]
No Plugins found warning message
I confirm this.
I've submitted the bug upstream:
I believe this is mostly a problem due to bug#247549 which I believe to be
fixed with the next release (due out soon).
I confirm this bug was fixed on my machine by updating to the version 0.9.0-1
release in Fedora Extras.
qgis-0.9.0-2.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update qgis'
qgis-0.9.0-2.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.