telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()

Bug #918744 reported by Pavol Klačanský
528
This bug affects 69 people
Affects Status Importance Assigned to Milestone
telepathy-idle (Ubuntu)
Confirmed
High
Unassigned

Bug Description

woke up laptop and got error

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: bab5d08f3dbd30d3050bc5105fc7267d
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
CrashCounter: 1
Date: Thu Jan 19 15:31:16 2012
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
SegvAnalysis:
 Segfault happened at: 0x7ffb6d126064 <g_io_stream_get_output_stream+4>: mov (%rdi),%rax
 PC (0x7ffb6d126064) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
 g_io_stream_get_output_stream () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 idle_server_connection_send_async ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()
UpgradeStatus: Upgraded to precise on 2012-01-18 (1 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare

Revision history for this message
Pavol Klačanský (pavolzetor-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_io_stream_get_output_stream (stream=0x0) at /build/buildd/glib2.0-2.31.10/./gio/giostream.c:247
 idle_server_connection_send_async (conn=0x1892920, cmd=0x7fff649daed0 "USER pk 8 * :Pavol Klacansky\r\n", cancellable=0x0, callback=0x40a520 <_msg_queue_timeout_ready>, user_data=0x17ad100) at idle-server-connection.c:452
 msg_queue_timeout_cb (user_data=<optimized out>) at idle-connection.c:904
 g_timeout_dispatch (source=0x18b1de0, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.31.10/./glib/gmain.c:3857
 g_main_dispatch (context=0x17a03d0) at /build/buildd/glib2.0-2.31.10/./glib/gmain.c:2513

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 telepathy-idle (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 telepathy-idle (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
visibility: public → private
Changed in telepathy-idle (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
importance: Medium → High
visibility: private → public
Revision history for this message
Ken VanDine (ken-vandine) wrote :
Revision history for this message
Mengxuan Xia (xiamx) wrote :
Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :

The bug still occurs on Quantal Quetzal, with version 0.1.11-2 of telepathy-idle.
It is triggered whenever a connection isn't available - like at the moment of a redial, all 24 hours to my provider. A try ... except ConnectionError: could set them an end.

Revision history for this message
Rafael García (rgo) wrote :

You can reproduce it powering off the router

Revision history for this message
Arthur (iegik) wrote :

$ gnome-shell --replace&
(gnome-shell:1127): folks-WARNING **: postal-address-details.vala:283: Empty postal address passed to PostalAddressFieldDetails.
...

Changed in telepathy-idle (Ubuntu):
assignee: Ken VanDine (ken-vandine) → nobody
To post a comment you must log in.