Bug 17811

Summary: lxterminal does not properly behave for Ctrl+Shift+<a_key>
Product: Mageia Reporter: Nicolas Salguero <nicolas.salguero>
Component: RPM PackagesAssignee: QA Team <qa-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: sysadmin-bugs, tarazed25
Version: 5Keywords: validated_update
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: advisory MGA5-32-OK MGA5-64-OK
Source RPM: lxterminal CVE:
Status comment:

Description Nicolas Salguero 2016-02-24 10:30:20 CET 
Hi,

The version 0.1.11 of lxterminal has a problem with Ctrl+Shift+<a_key>: the action defined by the accelerator is done but also the action defined by Ctrl+<the_same_key>.

For example, lxterminal also sends a break (Ctrl+C) when using (Ctrl+Shift+C) to copy.

Best regards,

Nico.
Comment 1 Nicolas Salguero 2016-02-24 10:44:12 CET 
Suggested advisory:
========================

The updated lxterminal package corrects the problem with Ctrl+Shift+C (used to copy the selection) which is also interpreted as Ctrl+C.
========================

Updated packages in core/updates_testing:
========================
i586:
lxterminal-0.1.11-5.1.mga5.i586.rpm

x86_64:
lxterminal-0.1.11-5.1.mga5.x86_64.rpm

Source RPMs:
lxterminal-0.1.11-5.1.mga5.src.rpm

Status: NEW => ASSIGNED
Assignee: bugsquad => qa-bugs

Comment 2 Len Lawrence 2016-02-24 21:00:38 CET 
mga5  i586 in virtualbox  Mate

Before updating:
[lcl@alkaid ~]$ ls | wc -l
11
[lcl@alkaid ~]$ gedit rootbashrc
^C
[lcl@alkaid ~]$ ls | wc -l
                                                
11
[lcl@alkaid ~]$ 

I launched the editor and then highlighted the first command and used
Ctrl Shift C to cut the selection.  A Ctrl C abort was issued immediately, killing gedit.  Ctrl Shift V then pasted the selection in the terminal and hit Return.  This demonstrates the fault.

Closed the lxterminal and installed the update and launched another lxterminal.  A similar sequence of commands did not exhibit the Ctrl C abort when an earlier command was highlighted.

[lcl@alkaid ~]$ ls | wc -l
11
[lcl@alkaid ~]$ gedit rootbashrc
ls | wc -l
[lcl@alkaid ~]$ ls | wc -l
11
[lcl@alkaid ~]$ 

The highlighted command was inserted after the gedit line using Ctrl Shift V but was not executed until the editor was closed.

Looks like it is fixed.

CC: (none) => tarazed25

Len Lawrence 2016-02-24 21:01:03 CET

Whiteboard: (none) => MGA5-32-OK

Comment 3 Len Lawrence 2016-02-24 21:04:52 CET 
The simple test from comment #2 was applied to the x86_64 update on real hardware.  The fault was there before the update and disappeared afterwards.

On the assumption that other accelerator key combinations also work after the update (?) I am inclined to validate this.  Holding off in case of objections.
Len Lawrence 2016-02-24 21:51:54 CET

Whiteboard: MGA5-32-OK => MGA5-32-OK MGA5-64-OK

Comment 4 claire robinson 2016-02-25 10:04:01 CET 
Looks OK Len, thanks. Validating. Advisory uploaded.

Please push to 5 updates

Thanks

Keywords: (none) => validated_update
Whiteboard: MGA5-32-OK MGA5-64-OK => advisory MGA5-32-OK MGA5-64-OK
CC: (none) => sysadmin-bugs

claire robinson 2016-02-25 12:06:20 CET

Source RPM: (none) => lxterminal

Comment 5 Mageia Robot 2016-02-26 22:46:31 CET 
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2016-0032.html

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