Bug 20522 - mate fails to try several terminal when clicing on "Vim" icon in application menu (bad handling of "Terminal=True")
Summary: mate fails to try several terminal when clicing on "Vim" icon in application ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Atilla ÖNTAŞ
QA Contact:
URL:
Whiteboard:
Keywords: 6sta2
: 20521 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-19 06:44 CET by Ben McMonagle
Modified: 2017-03-23 08:07 CET (History)
3 users (show)

See Also:
Source RPM: desktop-common-data
CVE:
Status comment:


Attachments
report.bug.xz mate i586 install (181.84 KB, application/x-xz)
2017-03-19 06:45 CET, Ben McMonagle
Details

Description Ben McMonagle 2017-03-19 06:44:35 CET
Description of problem: Mate DE : when "Vim" is invoked from application menu pop up advises: Error; could not launch "Vim"
failed to execute child process "xterm" (no such file or directory)

how-ever, if invoked from "mate terminal","vim" introduction  appears


Version-Release number of selected component (if applicable):
i586.iso build date : Mar 14 22:4:58 CET 2017

How reproducible:every time


Steps to Reproduce:
1.install Mate DE only from iso dated : Mar 14 22:4:58 CET 2017. reboot
2.invoke "Vim" from menu application launcher
3.note popup
4. invoke "vim" from mate terminal
Comment 1 Ben McMonagle 2017-03-19 06:45:24 CET
Created attachment 9119 [details]
report.bug.xz mate i586 install
Ben McMonagle 2017-03-19 06:45:36 CET

Keywords: (none) => 6sta2

Rémi Verschelde 2017-03-19 10:05:33 CET

Assignee: bugsquad => thierry.vignaud

Comment 2 Thierry Vignaud 2017-03-21 10:46:37 CET
That's hardly a vim bug:
Vim is _not_ supposed to start the emulator.

Like if one adds an icon for bash, bash wouldn't be responsible for opening the terminal emulator :-)
Nor would be cat/grep/sed/cut/perl/python...

That's the job for the DE (here: MATE).
That's why there's "Terminal=true" in /usr/share/applications/vim.desktop (unlike /usr/share/applications/gvim.desktop)

Here mate obviously has some logic to do so but it fails to fallback on it's own terminal if xterm isn't installed (actually it should try mate-terminal first IMHO...).

Assignee: thierry.vignaud => bugsquad
Source RPM: (none) => mate-panel

Thierry Vignaud 2017-03-21 10:47:25 CET

CC: (none) => tarakbumba, thierry.vignaud
Summary: when "Vim" is invoked from application menu it fails to open terminal window => mate fails to try several terminal when clicing on "Vim" icon in application menu (bad handling of "Terminal=True")

Comment 3 Rémi Verschelde 2017-03-21 11:17:38 CET
Probably the same issue as bug 20521 then. I haven't checked the logic but I guess mate-panel tries to load xvt which itself lacks logic for mate-terminal.

(In reply to Martin Whitaker from comment #2)
> This was caused by the cleanups to rpmsrate, which should now have been
> reverted. But xvt should really be updated to know about and use
> mate-terminal. It only worked before because Eterm was getting installed.

CC: (none) => mageiatools
Assignee: bugsquad => tarakbumba
Source RPM: mate-panel => desktop-common-data

Comment 4 Rémi Verschelde 2017-03-21 11:18:12 CET
*** Bug 20521 has been marked as a duplicate of this bug. ***
Comment 5 Thierry Vignaud 2017-03-21 11:26:38 CET
(In reply to Rémi Verschelde from comment #3)

You should be able to use the "bug #XYZ comment #ZYX" syntax in order to have proper links to other bugs' comments:
See Martin's comment in bug #20521 comment #2
Comment 6 Atilla ÖNTAŞ 2017-03-22 22:58:22 CET
I can't reproduce this on fresh install sta2 on VM. Vim launches as intended. Here is my screenshot link: http://i1316.photobucket.com/albums/t604/tarakbumba/VirtualBox_Mageia6_23_03_2017_00_05_28_zpsrffvbdh8.png
Comment 7 Rémi Verschelde 2017-03-23 08:07:30 CET
It was fixed with desktop-common-data 6.9:
http://svnweb.mageia.org/packages?view=revision&revision=1093929.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.