vino-server crashed with SIGSEGV in tp_connection_get_contacts_by_handle()

Bug #979186 reported by Jonathon Fernyhough
40
This bug affects 4 people
Affects Status Importance Assigned to Milestone
telepathy-glib (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Apport report. Tried to share desktop with jabber contact.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: vino 3.4.0-0ubuntu3
Uname: Linux 3.3.0-1.dmz.1-liquorix-amd64 x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Wed Apr 11 19:02:56 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/vino/vino-server
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
ProcCmdline: /usr/lib/vino/vino-server --sm-disable
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f6e9cde6a5d <tp_connection_get_contacts_by_handle+29>: mov 0x48(%rdi),%rax
 PC (0x7f6e9cde6a5d) ok
 source "0x48(%rdi)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vino
StacktraceTop:
 tp_connection_get_contacts_by_handle () from /usr/lib/libtelepathy-glib.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: vino-server crashed with SIGSEGV in tp_connection_get_contacts_by_handle()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Jonathon Fernyhough (jfernyhough) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tp_connection_get_contacts_by_handle (self=0x0, n_handles=1, handles=0x7ffff8b07a3c, n_features=2, features=0x7ffff8b07a30, callback=0x42d310 <vino_tube_server_factory_handle_cb>, user_data=0x20f8d60, destroy=0, weak_object=0x0) at contact.c:4152
 vino_tube_server_share_with_tube (server=0x20f8d60, error=0x0) at server/vino-tube-server.c:480
 handle_channels_cb (handler=<optimized out>, account=<optimized out>, connection=<optimized out>, channels=<optimized out>, requests_satisfied=<optimized out>, user_action_time=<optimized out>, context=0x20f8aa0, user_data=0x2051600) at server/vino-tube-servers-manager.c:227
 handle_channels (client=0x2060050, account=0x20684d0, connection=0x20e8390, channels=0x206a0e0, requests_satisfied=<optimized out>, user_action_time=<optimized out>, context=0x20f8aa0) at simple-handler.c:223
 handle_channels_context_prepare_cb (source=<optimized out>, result=<optimized out>, user_data=0x2060050) at base-client.c:2224

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
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in vino (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Ken, could you check with upstream if that's a known issue, something that we should try to get fixed in a SRU?

visibility: private → public
affects: vino (Ubuntu) → telepathy-glib (Ubuntu)
Changed in telepathy-glib (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Changed in telepathy-glib (Ubuntu):
assignee: Ken VanDine (ken-vandine) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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