vino-server assert failure: *** glibc detected *** /usr/lib/vino/vino-server: malloc(): memory corruption: 0x000000000249b710 ***

[José Alburquerque]

Happens when I log in.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: vino 3.1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
AssertionMessage: *** glibc detected *** /usr/lib/vino/vino-server: malloc(): memory corruption: 0x000000000249b710 ***
CrashCounter: 1
Date: Tue Sep 20 16:45:40 2011
ExecutablePath: /usr/lib/vino/vino-server
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/vino/vino-server --sm-disable
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: vino
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7fd7d19d40d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7fd7d19d1167 "malloc(): memory corruption", ptr=<optimized out>) at malloc.c:6283
 _int_malloc (av=0x7fd7d1c0f1c0, bytes=79) at malloc.c:4396
 __GI___libc_malloc (bytes=79) at malloc.c:3660
 GetUPNPUrls () from /usr/lib/libminiupnpc.so.5
Title: vino-server assert failure: *** glibc detected *** /usr/lib/vino/vino-server: malloc(): memory corruption: 0x000000000249b710 ***
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare src
XsessionErrors: (vino-server:30183): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #841384, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.