vino-server SIGABRT, "buffer overflow detected" in clipboard handling code

[Jimmy Angelakos]

vino crashed in the background while I was doing unrelated tasks in the foreground.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: vino 3.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 20 23:49:49 2012
ExecutablePath: /usr/lib/vino/vino-server
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120315)
ProcCmdline: /usr/lib/vino/vino-server --sm-disable
Signal: 6
SourcePackage: vino
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
Title: vino-server crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7fe2bffb271c "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 __GI___fortify_fail (msg=0x7fe2bffb26b3 "buffer overflow detected") at fortify_fail.c:32
 __GI___chk_fail () at chk_fail.c:29
 __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
 rfbCloseClient (cl=0x25180c0) at server/libvncserver/sockets.c:353

[Launchpad Janitor (janitor)]

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

[Sepero (cowpie2000)]

When it crashed, I was on a skype call while saving a file in gedit.

Why does the server not automatically restart?

[joe4379 (joe4379-n)]

crashed on nx client after nx server was forcibly closed (reboot)

[Lem (lem-jjr)]

I seem to trigger this bug occasionally when using copy/paste via right click menu. Happens in XChat, Pidgin and Firefox. I don't think it's specific to those applications though.

[Sepero (cowpie2000)]

Vino should restart after a crash.

[Didier Roche-Tolomelli (didrocks)]

We are other important bugs in quantal and didn't get the time to fix them. In addition, we already live with that issue on precise. I think we should focus on the other bugs first and get back to this one later.

[Samuel Coleman (sjcoleman)]

Can later be now, now? On a multiuser system I run, it's extremely frustrating to have Vino constantly dying, not to mention unsettling for my users to have a big, scary dialog pop up with “something something error something” on it.

[Sebastien Bacher (seb128)]

@Samuel: do you have steps that allow to reproduce the issue easily? that would help to debug it...

[Sasa Paporovic (melchiaros)]

David King from GNOME was fast and keen on the upstream report. He has already created a patch and asking for testing.

I attach the patch file here

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "vino-check-socket-fd-before-deref.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release