Ubuntu
gtk-vnc package

vinagre crashed with SIGSEGV in memcpy()

Bug #207205 reported by Jason Greene
74
Affects Status Importance Assigned to Milestone
gtk-vnc (Ubuntu)
Fix Released
Medium
Unassigned
Hardy
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: vinagre

I was just closing the application and go this error

ProblemType: Crash
Architecture: i386
Date: Wed Mar 26 11:22:27 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/vinagre
NonfreeKernelModules: nvidia
Package: vinagre 0.5.0-1
PackageArchitecture: i386
ProcCmdline: vinagre
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: vinagre
StacktraceTop:
 memcpy () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libgtk-vnc-1.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: vinagre crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Jason Greene (jason-the-greenes) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memcpy () from /lib/tls/i686/cmov/libc.so.6
gvnc_blt_fast (gvnc=0x8375800, src=0x8635c00 "\225��", pitch=5756, x=<value optimized out>,
gvnc_blt (gvnc=0x1, src=0xb38e1380 <Address 0xb38e1380 out of bounds>, pitch=1439, x=0,
gvnc_framebuffer_update (gvnc=0x8375800, etype=<value optimized out>, x=0, y=675,
gvnc_server_message (gvnc=0x8375800) at /build/buildd/gtk-vnc-0.3.4/./src/gvnc.c:2002

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in vinagre:
importance: Undecided → Medium
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Thanks for the report. Could you get a valgrind log of the crash? You can see how to use valgrind on https://wiki.ubuntu.com/Valgrind

Thanks

Changed in vinagre:
status: New → Incomplete
Revision history for this message
Jason Greene (jason-the-greenes) wrote : Re: [Bug 207205] Re: vinagre crashed with SIGSEGV in memcpy()

I tried running

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log vinagre

The app starts and and I can connect to a remote system but I never
get a usable screen
I have to kill the app so there is no log produced.

jason

On Wed, Mar 26, 2008 at 12:12 PM, Emilio Pozuelo Monfort
<email address hidden> wrote:
> Thanks for the report. Could you get a valgrind log of the crash? You
> can see how to use valgrind on https://wiki.ubuntu.com/Valgrind
>
> Thanks
>
> ** Visibility changed to: Public
>
> ** Changed in: vinagre (Ubuntu)
> Status: New => Incomplete
>
>
>
> --
> vinagre crashed with SIGSEGV in memcpy()
> https://bugs.launchpad.net/bugs/207205
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jason

Revision history for this message
Michael Adams (madams) wrote : Similar event happens after latest set of patches to Hardy

Running Hardy with Vinegre 0.5.0 & latest system updates: crash seems to occur after disconnecting with remote hosts.

Revision history for this message
Jonh Wendell (wendell) wrote :

This bug has been fixed in upstream:
http://gtk-vnc.codemonkey.ws/hg/outgoing.hg/rev/fb2b0584c87e

Changed in vinagre:
status: Incomplete → Fix Committed
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Please, see bug 218667 where I request an exception to get an update for gtk-vnc fixing this bug. There's a link to my ppa which has that patch, so please test it and comment on that bug.

Thanks

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

Would be nice to get the fix to the hardy updates

Changed in gtk-vnc:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

0.3.5 synced to Intrepid, the SRU for hardy is on its way (see bug 206227)

Changed in gtk-vnc:
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Changed in gtk-vnc:
status: Confirmed → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in gtk-vnc:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.