Zsh5 crashes when resizing window after startup

Bug #1587622 reported by Paul Munday
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zsh (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Steps to reproduce:
1. Open terminal window
2. Resize by grabbing corner etc, before typing commands

Notes:
1. It only happens *before* you type anything at the prompt (though commands have been run in zsh through zshrc (I have it use toilet/figlet to print stuff on startup (before the prompt appears)
2. Once you typed have something it doesn't seem to occur, its happens consistently if you haven't though.
3. This happens across multiple terminals: gnome-terminal, terminator, xterm, uxterm
4. I saw a similar crash starting guake as well. On startup if I hit F12 to open it crashed. I have to do this multiple times before it stays open.

This is on a fresh install of 14.04. I have a lot of customization in my .zshrc. I haven't seen this on other machines with the same dot-files, or the same machine prior to a fresh hard drive/install.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: zsh 5.0.2-3ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 31 12:09:31 2016
InstallationDate: Installed on 2016-05-20 (10 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: zsh
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Paul Munday (paulm-4) wrote :
Revision history for this message
Axel Beckert (xtaran) wrote :

I'm sorry, but I can't reproduce this issue. Tried with uxterm on trusty and my own .zshrc (which is based on the Grml zshrc). No crash at all.

Revision history for this message
Paul Munday (paulm-4) wrote :

tracked down the issue to elsewhere (even if tis just as confusing)

Changed in zsh (Ubuntu):
status: New → Invalid
Revision history for this message
Paul Munday (paulm-4) wrote :

Specifically the segfualt is caused by referencing $WIDGET in TRAPWINCH before any user interaction. I've reported this upstream.

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.