Bug 20521

Summary: no "terminal" window when invoking terminal from Mageia Welcome
Product: Mageia Reporter: Ben McMonagle <westel>
Component: RPM PackagesAssignee: Daniel Napora <napcok>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: mageia, pkg-bugs, yvesbrungard
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: report.bug.xz mate i586 install

Description Ben McMonagle 2017-03-19 06:10:58 CET
Description of problem: attempting to invoke a terminal from Mageia welcome (Mate i586 single DE install from i586 build date : Mar 14 22:4:58 CET 2017) results in no terminal window presented.

invoking Mageia welcome from terminal and then invoking "terminal"from mageia welcome advises:

$ mageiawelcome
>>> "run xvt"
['xvt']
no terminal emulator detected



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.install Mate only DE from .iso dated : Mar 14 22:4:58 CET 2017. reboot.
2.invoke "terminal" from pg4 of Mageia welcome - nothing happens
3.invoke Mageia welcome from  "mate terminal"
4.invoke "terminal" from pg4 of Mageia welcome - mate terminal advises "no terminal emulator detected"
Comment 1 Ben McMonagle 2017-03-19 06:12:38 CET
Created attachment 9118 [details]
report.bug.xz mate i586 install
Ben McMonagle 2017-03-19 06:13:16 CET

Summary: no "terminal" when invoking terminal from Mageia Welcome => no "terminal" window when invoking terminal from Mageia Welcome

Rémi Verschelde 2017-03-19 10:04:40 CET

CC: (none) => pkg-bugs, yves.brungard_mageia
Assignee: bugsquad => napcok

Comment 2 Martin Whitaker 2017-03-20 22:02:53 CET
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) => mageia

Comment 3 Rémi Verschelde 2017-03-21 11:18:12 CET
Thanks for the explanations Martin; I think it's the same bug as bug 20522 so let's just keep one. This should be fixed in desktop-common-data.

*** This bug has been marked as a duplicate of bug 20522 ***

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