Bug 10868

Summary:	codeblocks can't launch console apps by default, should suggest xterm
Product:	Mageia	Reporter:	Patrick Hibbs <codebase7>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	minor
Priority:	Normal	CC:	cvargas
Version:	3	Keywords:	Junior_job
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	codeblocks	CVE:
Status comment:

Description Patrick Hibbs 2013-07-28 09:17:44 CEST

Description of problem:
codeblocks launches console apps using xterm by default. As the rpm does not suggest xterm, it's possible for it to not be installed when codeblocks is. In this case codeblocks will attempt to launch the console app and silently fail leaving the user confused as to why the console app did not start.

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

How reproducible:
Install codeblocks.

Steps to Reproduce:
1.urpmi codeblocks.
2.Load a console app project.
3.Attempt to launch console app.

Really all that is needed is a "Suggests: xterm" in the rpm spec.

This is debatable however as the user can change the used terminal emulator for running console apps. It's just that codeblocks by default uses xterm. For a user who wants it to "just work" this could be useful. The alternitive would be to set the default to a different terminal emulator that is installed, or just warn the user.

Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2013-07-29 20:19:12 CEST

Summary: codeblocks can't launch console apps by default. => codeblocks can't launch console apps by default

Manuel Hiebel 2013-07-29 20:20:09 CEST

Keywords: (none) => Junior_job
CC: (none) => cvargas
Summary: codeblocks can't launch console apps by default => codeblocks can't launch console apps by default, should suggest xterm

Comment 1 Manuel Hiebel 2013-07-29 20:20:22 CEST

(sorry)

Comment 2 Marja Van Waes 2015-03-31 16:03:23 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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