vino-server crashed with SIGSEGV in free()

StacktraceTop:
 _int_free (av=0x7ff8b20a51c0, p=0x10fb710) at malloc.c:4964
 __GI___libc_free (mem=<optimized out>) at malloc.c:3738
 UPNP_GetValidIGD () from /tmp/tmpt4Y8Ml/usr/lib/libminiupnpc.so.5
 update_upnp_status (upnp=0x10e8650) at server/vino-upnp.c:97
 update_upnp_status (upnp=0x10e8650) at server/vino-upnp.c:79

pedro, could you upstream this one?

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=658550

Any news or progress on this one? Since Gnome said that it is Debian/Ubuntu miniupnp specific, no one over here seems to care?!

Vino-server worked well on my AMD E350 system as I first upgraded to Oneiric about one month ago. But after some updates, it does not want to start anymore. Since it was running on Natty, but did not redraw the screen, it would be really nice to have it up and running in Oneiric.

Kind regards
Phil

Of got a problem with vino-server not starting anymore as well.

Laurence Jeloudev
<email address hidden>

On 24/09/2011, at 19:05, Philipp Michalschik <email address hidden> wrote:

> Any news or progress on this one? Since Gnome said that it is
> Debian/Ubuntu miniupnp specific, no one over here seems to care?!
>
> Vino-server worked well on my AMD E350 system as I first upgraded to
> Oneiric about one month ago. But after some updates, it does not want to
> start anymore. Since it was running on Natty, but did not redraw the
> screen, it would be really nice to have it up and running in Oneiric.
>
> Kind regards
> Phil
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/840696
>
> Title:
> vino-server crashed with SIGSEGV in free()
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/vino/+bug/840696/+subscriptions

Sorry, it is just me or the bug on https://bugzilla.gnome.org/show_bug.cgi?id=658550 is never going to be resolved?

The bug on bugzilla site says INVALID and status marked as RESOLVED. Is this a stuck-in-limbo case?

no that is completely wrong Vino Server still doesn't work on my ubuntu....
its not resolved hopefully someone smart enough will fix it.. I just report bugs where things have gone wrong..
if some one could post an explanation of how to upload logs to find the cause of the problem.. I can assist in providing a log.

btw i don't have a gnome bug report account on launchpad if some who has a gnome account can change the status for it.. as Vino Server does not work on Ubuntu 11.10. using the unity 3d interface.

This bug is really frustrating. It is impossible to control the desktop externally which is a must for me when I'm traveling, etc. Is there any way this bug can be really looked at. This has been broken for too long, it feels.

Maybe the bug that the upstream developer refers to should be watched in place of the original bug report filed upstream?

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

I was just able to execute vino-server manually, but as a user, i.e. not as root. Specifically, at a shell prompt, I typed

/usr/lib/vino/vino-server

A vnc client can now access the desktop. However, it segfaults after a few seconds when the "Automatically configure UPnP router to open and forward ports" is enabled. When this is disabled, it seems to work ok.

I can confirm that a vnc client can access the desktop now, but I'm still unable to control it. Although the mouse pointer moves, no keyboard input or mouse clicks seem to be sent/received.

I got this crash when I enabled 'Automatically configure UPnP router to open and forward ports' in Desktop Sharing Preferences.

vino version is 3.2.0-0ubuntu1

I can see and control my HTPC again! Thanks a lot.

WORKAROUND

Apparently this is a timing problem, cart before the horse so to speak. As seen above the suggestions about starting/stopping/enabling/disabling networks and/or desktop sharing, I figured the problem was probably due to the fact that the desktop sharing was enabling BEFORE the network was actually ready, thereby killing the process when the network then became ready. This may or not be but creating a simple script that fires up the vino-server after waiting for 10 seconds after login solves the problem. I created this and added it to my startup applicaitions.

#!/bin/bash
sleep 10
/usr/lib/vino/vino-server

Now all is well. This was on Linux Mint 12 using the MATE desktop.

Does this happen only on GNOME login? Because for me it happens during session as well. I'll report another bug and let others decide.
Reported as Bug #922126.

This bug was fixed in the package vino - 3.3.3-0ubuntu2

---------------
vino (3.3.3-0ubuntu2) precise; urgency=low

  * debian/patches/05_use-system-miniupnpc.patch:
    - update to the current libminiupnpc abi, the previous version was still
      using the source .h copies and the functions prototypes and code were
      different from the runtime (lp: #840696, #841384, #854512, #903879).
 -- Sebastien Bacher <email address hidden> Thu, 26 Jan 2012 16:26:41 +0100

This bug is still not fixed for me (running Ubuntu Oneric, fully updated). I've been reading that there are possible fixes. I Haven't tried them, but I would guess that the relevant packages should be updated with a fix if there is one.

Ah, now I see that there has been a fix released. Will wait for the fix then.

the fixes just got uploaded, the precise package still needs to build and the oneiric sru to be approved by a mir team member before building

Hello Mike, or anyone else affected,

Accepted vino into oneiric-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I can confirm that the fixes in the proposed packages (vino and miniupnpc) allow the desktop to be viewed/controlled through VNC as before.

I hope vino remote desktop all works as well for the upgrade to 12.04.
When it is released in April. I can confirm vino now works on my machine as
well after the updates.

On Tuesday, 31 January 2012, José Alburquerque <email address hidden>
wrote:
> I can confirm that the fixes in the proposed packages (vino and
> miniupnpc) allow the desktop to be viewed/controlled through VNC as
> before.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/840696
>
> Title:
> vino-server crashed with SIGSEGV in free()
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/miniupnpc/+bug/840696/+subscriptions
>

--
Laurence Jeloudev
Do us a favour and get gmail (http://www.gmail.com), so you don't loose
your emails and then print them off!

I can confirm as well, that the fixes in the proposed packages, from #25, made the desktop sharing work fine via VNC, but I still hope that in 12.04, it could work easily like previous versions. Thanks, Chris Rogers!

This bug was fixed in the package vino - 3.2.0-0ubuntu1.1

---------------
vino (3.2.0-0ubuntu1.1) oneiric-proposed; urgency=low

  * debian/patches/05_use-system-miniupnpc.patch:
    - update to the current libminiupnpc abi, the previous version was still
      using the source .h copies and the functions prototypes and code were
      different from the runtime (lp: #840696)
 -- Sebastien Bacher <email address hidden> Thu, 26 Jan 2012 16:11:41 +0100

Now working fine here, after a system update!! Thank you!!

I still get a segfault: Connecting to the vino server via vinaigre works exactly one time, but after that the server crashes.