screen crashed with SIGABRT

[Anders Kaseorg]

screen crashed with SIGABRT

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: screen 4.3.0-2
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jun 19 14:15:38 2015
ExecutablePath: /usr/bin/screen
InstallationDate: Installed on 2015-06-02 (17 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: SCREEN -S upgrade-servers-8496 -- /home/anders/bin/rupgrade --in-screen all
Signal: 6
SourcePackage: screen
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: screen crashed with SIGABRT
UpgradeStatus: Upgraded to wily on 2015-06-17 (1 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 SetCanvasWindow (cv=cv@entry=0x231d530, wi=0x23f2ff0) at canvas.c:336
 KillWindow (wi=wi@entry=0x2864090) at process.c:5440
 WindowDied (p=p@entry=0x2864090, wstat=<optimized out>, wstat@entry=0, wstat_valid=<optimized out>, wstat_valid@entry=0) at screen.c:1583
 win_readev_fn (ev=<optimized out>, data=0x2864090 "P\324s\002") at window.c:1904
 sched () at sched.c:237

[Axel Beckert (xtaran)]

Hi Anders,

this crash seems to happen regularily at yours, but so far only at yours. At least this bug report doesn't seem to contain the information from the screen-dbg package and the two duplicates don't contain any stacktrace at all. Any chance to get a stacktrace with the debug package installed.

It would be also nice to know what you did, when it happened so I can maybe reproduce it.

Does any of these sound familiar? https://savannah.gnu.org/search/?Search=Suchen&words=crash+seg&type_of_search=bugs&only_group_id=4235&exact=0#options

[Anders Kaseorg (andersk)]

This seems to match https://savannah.gnu.org/bugs/?func=detailitem&item_id=46507.

[Christian Ehrhardt  (paelzer)]

The referred fix is in 4.3.1 that version (or later) is in >=17.04.
Somebody tagged it artful, but did someone really try this with newer releases?

[Anders Kaseorg (andersk)]

Um, there’s no “referred fix”. I gave up on reporting duplicates of this a while ago, but the last one I reported (bug 1708927) was with screen 4.6.1-1 in artful. I’m pretty sure I’ve seen this in bionic, so I’ll be sure to send another report next time.

[Christian Ehrhardt  (paelzer)]

I meant the savanah.gnu.org link, that is listed as 4.3.1 - I didn't go into detail there.
Thanks for the feedback that this still affects newer versions.

[Anders Kaseorg (andersk)]

The savannah.gnu.org link is to an open bug report, there is no fix there.

[Christian Ehrhardt  (paelzer)]

Now I needed to read it in more detail.
I beg your pardon, reading it again obviously they list "release" and "fixed release" separately - and I misread the former for the latter.
I'm with you now, sorry for the (confused) noise

[Sergio Durigan Junior (sergiodj)]

Thanks for the bug report and sorry for the delay; this apparently fell through the cracks.

The upstream bug you pointed as being a possible match still hasn't received any replies in all these years. Can you confirm whether you're still experiencing this bug, and if yes, could you provide steps to reproduce it?

I understand that it's been a while since you first reported this problem, and I also noticed that the latest apport-generated tag was for the Cosmic distro, which may indicate that the bug has been fixed since then. However, I'd like to confirm if this is still an issue that's affecting you.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for screen (Ubuntu) because there has been no activity for 60 days.]