gnome-terminal crashes on resize

Bug #1627697 reported by Alan Griffiths
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MirAL
Fix Released
High
Unassigned
Ubuntu
Fix Released
High
Unassigned

Bug Description

Yakkety, Mir-0.24, lp:miral

Run gnome-terminal on a touchscreen laptop and resizing by three-finger pinch...

$ miral-run gnome-terminal
$
(gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: Unsupported GDK backend
...
(gnome-terminal-server:4817): Gdk-WARNING **: unknown property gtk-fontconfig-timestamp

(gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir event 11

(gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
*** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or corruption (out): 0x00007f2e70258010 ***

(Can't reproduce with Mir-0.1, but that may be because resize was too broken.)

Tags: gtk-mir

Related branches

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Actually, breaks just as easily with pointer based resize. (But I need an external mouse to get that to work.)

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

The problem seems specific to Yakkety: Can not reproduce on Xenial and Vivid+Overlay.

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

This appears to be racy code in the gtk-mir client: if I hack the server to only send one in five resize requests everything *appears* to work.

(Investigating to see if I can come up with a clean workaround based on this finding.)

Changed in miral:
importance: Undecided → High
Changed in miral:
assignee: nobody → Alan Griffiths (alan-griffiths)
status: New → In Progress
no longer affects: miral
no longer affects: gtk+3.0 (Ubuntu)
Changed in miral:
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
affects: gtk → gtk+3.0 (Ubuntu)
Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
Changed in miral:
importance: Undecided → High
Changed in gtk+3.0 (Ubuntu):
importance: Undecided → High
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

gtk seems to be fixed on 17.04

Changed in miral:
status: Fix Committed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yeah seems to work on zesty. Although only as a regular user (not sudo) and with a mountain of GTK warnings.

affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.