[SRU] screen server process can be crashed by byobu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
screen |
Unknown
|
Unknown
|
|||
byobu (Debian) |
Fix Released
|
Unknown
|
|||
byobu (Ubuntu) |
Fix Released
|
Critical
|
Dustin Kirkland | ||
Trusty |
Fix Released
|
Critical
|
Dustin Kirkland | ||
Utopic |
Fix Released
|
Critical
|
Dustin Kirkland | ||
screen (Debian) |
Confirmed
|
Unknown
|
|||
screen (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Trusty |
Won't Fix
|
Medium
|
Unassigned | ||
Utopic |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
screen crashed with SIGSEGV
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: screen 4.1.0~20120320g
ProcVersionSign
Uname: Linux 3.13.0-5-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jan 29 23:59:55 2014
ExecutablePath: /usr/bin/screen
InstallationDate: Installed on 2010-12-05 (1152 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: SCREEN
SegvAnalysis:
Segfault happened at: 0x7f4f000a1f15 <__GI_tcsetattr
PC (0x7f4f000a1f15) ok
source "(%r8)" (0x00001430) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: screen
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: screen crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2013-10-31 (91 days ago)
UserGroups:
[Impact]
* Byobu users of the byobu-screen backend will find their screen process crashed, if they hit ctrl-a (screen's default escape sequence). This is a critical breakage for byobu-screen users.
[Test Case]
* From a new or fresh Trusty installation (desktop or server), drop to a command line, and run 'byobu-screen'. You'll be interactively prompted to choose whether ctrl-a should be handled like screen or emacs. Choose (1) for screen. Your screen session is now crashed.
* Upgrade to the package in trusty-proposed, launch a new byobu-screen session, and press ctrl-a-c to create a new window, and then ctrl-a-n and ctrl-a-p and that should all work perfectly well now.
[Regression Potential]
* This fix does revert the change that was intended to fix a far more minor Bug: #814172. I have reopened that bug, will fix it separately, and upload another SRU later.
* Otherwise, regression potential should be minimal. Once that recent commit was reverted, the code looks very much like it's looked for a very long, stable time.
[Other Info]
* None
information type: | Private → Public |
summary: |
- screen crashed with SIGSEGV + screen server process can be crashed by byobu |
Changed in byobu (Ubuntu): | |
status: | Confirmed → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Dustin Kirkland (kirkland) |
Changed in byobu (Ubuntu Trusty): | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Dustin Kirkland (kirkland) |
milestone: | none → trusty-updates |
Changed in byobu (Ubuntu Utopic): | |
status: | In Progress → Fix Committed |
summary: |
- screen server process can be crashed by byobu + [SRU] screen server process can be crashed by byobu |
description: | updated |
Changed in screen (Debian): | |
status: | Unknown → Confirmed |
Changed in byobu (Debian): | |
status: | Unknown → Confirmed |
tags: |
added: verification-failed removed: verification-needed |
Changed in byobu (Ubuntu Trusty): | |
status: | Fix Committed → In Progress |
tags: |
added: verification-done removed: verification-needed |
Changed in screen (Ubuntu Trusty): | |
importance: | Undecided → Medium |
Changed in screen (Ubuntu Utopic): | |
status: | Confirmed → Won't Fix |
Changed in byobu (Debian): | |
status: | Confirmed → Fix Released |
Any hint about what you were doing when it crashed?