Custom Application Launcher with Application in Terminal enabled should use user-specified terminal emulator
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brisk-menu (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
classicmenu-indicator (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
glib2.0 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
mate-desktop-environment (Ubuntu) |
Fix Released
|
Medium
|
Martin Wimpress | ||
mate-menu (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mate-menus (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mate-panel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mate-settings-daemon (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ubuntu-mate-settings (Ubuntu) |
Fix Released
|
Medium
|
Martin Wimpress | ||
vala-panel-appmenu (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. Install Ubuntu MATE 20.04 LTS
2. Install non-default terminal - Tilix, by `sudo apt-get install tilix`
3. Install terminal-based application - Midnight Commander, by `sudo apt-get install mc`
3. Set Tilix as default terminal in `mate-default-
gsettings set org.mate.
4. Set Tilix as alternative for x-terminal-emulator by update-
update-
sudo update-alternatives --set x-terminal-emulator /usr/bin/
5. Reboot
6. Add Custom Application Launcher to the MATE Panel:
Type: Application in Terminal
Name: mc
Command: mc
7. Click the icon of just created Custom Application Launcher
Expected results:
* Midnight Commander is opened in the user-defined terminal - in Tilix
Actual results:
* Midnight Commander is default terminal - in MATE Terminal
Notes:
* This also happens with desktop-files installed by Midnight Commander, it opens in MATE Terminal when called from Brisk menu, Classic menu, Compact Menu, Dock, <Alt>+<F1> menu, Advanced Mate Menu (`mate-menu` package)
* What is interesting, the <Alt>+<F2> respects user preferences and uses Tilix
* Also <Ctrl>+<Alt>+<T> opens Tilix as expected.
---
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mate-panel 1.24.0-2
ProcVersionSign
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: MATE
Date: Mon Apr 20 10:48:51 2020
InstallationDate: Installed on 2020-04-19 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200419)
SourcePackage: mate-panel
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
description: | updated |
description: | updated |
tags: | added: xenial |
tags: | added: bionic eoan |
tags: | removed: eoan |
tags: | added: hirsute |
tags: |
added: impish jammy removed: xenial |
Changed in mate-desktop: | |
status: | Unknown → New |
no longer affects: | ubuntu-mate |
Changed in brisk-menu (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in classicmenu-indicator (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mate-menu (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mate-menus (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mate-panel (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in vala-panel-appmenu (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mate-settings-daemon (Ubuntu): | |
status: | Confirmed → Invalid |
no longer affects: | mate-desktop |
Changed in glib2.0 (Ubuntu): | |
status: | New → Confirmed |
Changed in mate-desktop-environment (Ubuntu): | |
status: | New → Confirmed |
Changed in ubuntu-mate-settings (Ubuntu): | |
status: | New → Confirmed |
Changed in ubuntu-mate-settings (Ubuntu): | |
status: | Triaged → In Progress |
Changed in mate-desktop-environment (Ubuntu): | |
status: | Triaged → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Martin Wimpress (flexiondotorg) |
Changed in ubuntu-mate-settings (Ubuntu): | |
assignee: | nobody → Martin Wimpress (flexiondotorg) |
importance: | Undecided → Medium |
Changed in mate-desktop-environment (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-mate-settings (Ubuntu): | |
status: | In Progress → Fix Committed |
Status changed to 'Confirmed' because the bug affects multiple users.