QGIS
QGIS copied to clipboard
No Vector toolbar
What is the bug or the crash?
There's no Vector menu in QGIS 3.22.5 on MacOS 10.15.7. I've tried re-installing the program twice, but the menu continues to just randomly disappear.
Steps to reproduce the issue
Literally just install QGIS and the Vector menu isn't there in the top toolbar.
Versions
QGIS version | 3.22.5-Białowieża | QGIS code revision | 2a0a86f142 |
---|---|---|---|
Qt version | 5.14.2 | ||
Python version | 3.8.7 | ||
GDAL/OGR version | 3.2.1 | ||
PROJ version | 6.3.2 | ||
EPSG Registry database version | v9.8.6 (2020-01-22) | ||
GEOS version | 3.9.1-CAPI-1.14.2 | ||
SQLite version | 3.31.1 | ||
PostgreSQL client version | 12.3 | ||
SpatiaLite version | 4.3.0a | ||
QWT version | 6.1.4 | ||
QScintilla2 version | 2.11.4 | ||
OS version | macOS 10.15 | ||
Active Python plugins | |||
sagaprovider | 2.12.99 | ||
db_manager | 0.1.20 | ||
MetaSearch | 0.3.5 |
Active Python plugins sagaprovider 2.12.99 db_manager 0.1.20 MetaSearch 0.3.5
Supported QGIS version
- [x] I'm running a supported QGIS version according to the roadmap.
New profile
- [x] I tried with a new QGIS profile
Additional context
I tried Settings > Profiles > New Profile and QGIS immediately crashed.
The current LTR version in 3.22.7, can you try with that?
Can you open the processing toolbox?
Probably Processing not being activated on the installation. Try enabling (in Plugins menu).
I reinstalled it (for a third time) and it now seems to be working fine in 3.22.8. I think in a previous run something from the Vector toolbar had caused QGIS to crashed, so it disabled (and deleted) the toolbar. Still, I shouldn't have to reinstall QGIS every time it crashes from an unexpectedly heavy operation.
On Mon, Jun 20, 2022 at 1:08 AM Harrissou Sant-anna < @.***> wrote:
Probably Processing not being activated on the installation. Try enabling (in Plugins menu).
— Reply to this email directly, view it on GitHub https://github.com/qgis/QGIS/issues/49070#issuecomment-1160113811, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM7PU2XUVCVDRHSI4NTAJYDVQARJDANCNFSM5ZHJEEBA . You are receiving this because you authored the thread.Message ID: @.***>
Is this still an issue?
No, it seems to have gone away after the reinstall.
On Mon, Jun 5, 2023 at 5:43 AM Alexander Bruy @.***> wrote:
Is this still an issue?
— Reply to this email directly, view it on GitHub https://github.com/qgis/QGIS/issues/49070#issuecomment-1576723563, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM7PU2UTFKGI7MBWFT7PAH3XJXIATANCNFSM5ZHJEEBA . You are receiving this because you authored the thread.Message ID: @.***>
Still, I shouldn't have to reinstall QGIS every time it crashes from an unexpectedly heavy operation
Many people still do/advise that but they shouldn't have to; starting with a new user profile most of the times cleans up the mess.
Is this still an issue?
@alexbruy Could there be a situation during a reinstall where Processing could get deactivated (and reactivating would fail), leading to missing vector and Processing menus upon restarting? I'm asking because I had that feeling (#52623, #50478, #51662, #49956) although reading again their reports it is unclear if installation was a trigger or an attempt to fix it. Or people deactivate Processing without noticing?
@DelazJ, maybe ensuring that, even when the Processing core plugin is disabled, the "Vector" (and "Raster") menu is present and contains an item like "Activate the Processing plugin" which activates the Processing plugin or opens the Plugins manager, would help the user to fix the issue.
It could be an option indeed, @agiudiceandrea
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.
Let's close this, as the original issue is solved, and open a feature request as per @agiudiceandrea suggestion.