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

Bug #960649 reported by Jimmy Angelakos
212
This bug affects 24 people
Affects Status Importance Assigned to Milestone
vino
New
Critical
vino (Ubuntu)
Triaged
High
Unassigned
Precise
Won't Fix
High
Unassigned

Bug Description

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

Revision history for this message
Jimmy Angelakos (vyruss) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in vino (Ubuntu):
importance: Undecided → Medium
summary: - vino-server crashed with SIGABRT in raise()
+ vino-server crashed with SIGABRT in __libc_message()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: vino-server crashed with SIGABRT in __libc_message()

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

Changed in vino (Ubuntu):
status: New → Confirmed
visibility: private → public
tags: added: qa-manual-testing
Changed in vino (Ubuntu):
importance: Medium → High
Revision history for this message
Sepero (cowpie2000) wrote :

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

Why does the server not automatically restart?

Revision history for this message
joe4379 (joe4379-n) wrote :

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

Revision history for this message
Lem (lem-jjr) wrote :

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.

tags: added: quantal running-unity
summary: - vino-server crashed with SIGABRT in __libc_message()
+ vino-server SIGABRT, "buffer overflow detected"
summary: - vino-server SIGABRT, "buffer overflow detected"
+ vino-server SIGABRT, "buffer overflow detected" in clipboard handling
+ code
Changed in vino (Ubuntu Precise):
milestone: none → ubuntu-12.04.1
tags: added: bugpattern-needed
Revision history for this message
Sepero (cowpie2000) wrote :

Vino should restart after a crash.

Changed in vino (Ubuntu):
status: Confirmed → Triaged
Changed in vino (Ubuntu Precise):
status: Confirmed → Triaged
Changed in vino (Ubuntu Precise):
milestone: ubuntu-12.04.1 → ubuntu-12.04.2
Para Siva (psivaa)
tags: added: rls-q-incoming
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

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.

tags: added: rls-q-notfixing
removed: rls-q-incoming
Revision history for this message
Samuel Coleman (sjcoleman) wrote :

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.

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

tags: added: raring
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

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

Revision history for this message
Sasa Paporovic (melchiaros) wrote :
tags: added: patch
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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.]

Changed in vino:
importance: Unknown → Critical
status: Unknown → New
Colin Watson (cjwatson)
Changed in vino (Ubuntu Precise):
milestone: ubuntu-12.04.2 → ubuntu-12.04.3
Revision history for this message
Steve Langasek (vorlon) wrote :

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

Changed in vino (Ubuntu Precise):
status: Triaged → Won't Fix
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.