Bug 18412 - 6sta1 GNOME terminal does not respond to resizing from its own menu
Summary: 6sta1 GNOME terminal does not respond to resizing from its own menu
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2016-05-08 19:13 CEST by Len Lawrence
Modified: 2016-11-14 21:37 CET (History)
2 users (show)

See Also:
Source RPM: gnome-terminal-3.20.1-1.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Len Lawrence 2016-05-08 19:13:13 CEST 
Description of problem:
Clicking on the Terminal option shows a menu of sizes like 80x24 to 132x43.  The terminal does not honour any of them.  The resize request is also ignored when the terminal has been resized by dragging a corner. 

Version-Release number of selected component (if applicable):
gnome-terminal-3.20.1-1.mga6

How reproducible:
Always

Steps to Reproduce:
1. Click on terminal in menu-bar
2. Select e.g. 80x43
3. Observe that nothing changes from the default 80x24
Comment 1 Marja Van Waes 2016-05-12 15:09:28 CEST 
Assigning to all packagers collectively, since there is no maintainer for this package

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs
Source RPM: (none) => gnome-terminal-3.20.1-1.mga6

Comment 2 Len Lawrence 2016-08-16 00:46:30 CEST 
This bug is apparent in mga6 RC classic GNOME.  Probable upstream bug.
Comment 3 Len Lawrence 2016-08-16 00:48:56 CEST 
Not important and the workaround is manual resizing.

Keywords: (none) => UPSTREAM

Comment 4 Marja Van Waes 2016-09-07 11:47:03 CEST 
re-assigning to the Gnome maintainers group.

Assignee: pkg-bugs => gnome

Comment 5 Len Lawrence 2016-11-14 21:37:42 CET 
This bug seems to have been solved.  Checked it on a Mageia5.1 GNOME Live install.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.