qubes-issues
qubes-issues copied to clipboard
Include qubes (or their "Settings" entries) with no app shortcuts in app menu search results
Qubes OS release
4.2
Steps to reproduce
- Move out any application from app menu for your template
- Go to Qubes application menu
- Search for the name of the template
Expected behavior
Do not hide or remove the template entirely, but make it appear as if you are opening the Qubes app menu and manually navigating to a template without any added applications (displaying the template name and settings).
Actual behavior
No template will show up:
The search is about applications specifically, not any objects., so it works as intended. But this sounds like a useful feature request. Alternatively, similar "fix" would be to considering "settings" entry in the search results too.
I just came across this issue. When having lots of qubes, search is often the only practical way look a qube up. And if we want open a qube's settings we can't go through search.
@marmarta they may be worth adding to the menu revision project.
When having lots of qubes, search is often the only practical way look a qube up. And if we want open a qube's settings we can't go through search.
You can search in the Qube Manager rather than the app menu, and that does allow you to easily open the settings of any qube returned in the search results.
You can search in the Qube Manager rather than the app menu, and that does allow you to easily open the settings of any qube returned in the search results.
That's true, but at the same time she settings are needed to access relatively frequently. And my impression is that the Qube Manager is only for more powerful / bulk actions. At least that's how I use (I rarely open it).
Maybe that's just my usage. Feel free to close if the impression is that this is a niche need (which I don't think it is).
One way to tackle this could be to keep the same right-side panel structure (with the settings and network state).
This way, the first result (Any Qube) would have normal results (without the settings), but once the user hovered over the specific qube they'd see the settings.
That's true, but at the same time she settings are needed to access relatively frequently.
Well, that's a matter of personal habits. I wouldn't be surprised if many users don't have to access qube settings frequently once they initially set things up the way they need.
And my impression is that the Qube Manager is only for more powerful / bulk actions. At least that's how I use (I rarely open it).
That's also a matter of personal habits. Personally, I always have it open, like a dashboard.
Personally, I would rather see the feature requested in this issue be an option that can be turned on or off, maybe something like [x] Show qubes without shortcuts in the app menu. I would hate for my menu to be cluttered up with every qube in the system with no way to opt out. In general, there really need to be ways not to have to see every single qube in the system all the time in every interface. Many qubes exist only as part of the internal machinery required to make the system work. Always having them mixed in with the user's own qubes makes it frustrating to find and organize one's own apps and data (related: https://github.com/QubesOS/qubes-issues/issues/8663).
So, my current idea is to add life cycle buttons and settings to search, but, to avoid inconsistencies and weird keyboard nav behavior, to move settings to the bottom of the app list (both in search and in normal view), to be grouped with lifecycle buttons.
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.3 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing bookworm-testing (or appropriate equivalent for your template version), then use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.3 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing trixie-testing (or appropriate equivalent for your template version), then use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.3 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.3 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.2 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing bookworm-testing (or appropriate equivalent for your template version), then use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.2 testing repository for the Debian template.
To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing trixie-testing (or appropriate equivalent for your template version), then use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 testing repository for the Fedora template.
To test this update, please install it with the following command:
sudo dnf update --enablerepo=qubes-vm-r4.2-current-testing
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The package desktop-linux-menu has been pushed to the r4.2 stable repository for the Debian template.
To install this update, please use the standard update command:
sudo apt-get update && sudo apt-get dist-upgrade
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:
sudo dnf update
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:
sudo dnf update
Automated announcement from builder-github
The component desktop-linux-menu (including package desktop-linux-menu) has been pushed to the r4.2 stable repository for the Fedora template.
To install this update, please use the standard update command:
sudo dnf update