Empathy don't save the salon's history after a wifi's cut

Bug #954275 reported by Mozaic
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telepathy Indicator
New
Undecided
Unassigned
telepathy-idle
New
Undecided
auto-bugsquad-fr
telepathy-idle (Ubuntu)
New
Undecided
Unassigned

Bug Description

Step:
1) Go to a salon with XMPP's account
2) Cut the wifi
3) Restart wifi
4) Empathy create a multi discussion: if there are three people who write before the wifi cut empathy create three discussion alone, but the salon's history is empty

goal:
After a cut of a connection, empathy restart the salon with all the discussion in the salon.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 13 18:46:02 2012
ExecutablePath: /usr/lib/telepathy/telepathy-idle
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/telepathy/telepathy-idle
SegvAnalysis:
 Segfault happened at: 0x7fdff9e35f84 <g_io_stream_get_output_stream+4>: mov (%rdi),%rax
 PC (0x7fdff9e35f84) 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-03-12 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Mozaic (mozaic) wrote :
visibility: private → public
summary: - telepathy-idle crashed with SIGSEGV in g_io_stream_get_output_stream()
+ telepathy don't save the salon's history after a wifi's cut
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #918744, 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.

tags: removed: need-amd64-retrace
Mozaic (mozaic)
summary: - telepathy don't save the salon's history after a wifi's cut
+ Empathy don't save the salon's history after a wifi's cut
Revision history for this message
Mozaic (mozaic) wrote :

It's look like different, now. I have got a crash and it's generate a rapport but, i see nothing in notification

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

  • auto-bugsquad-fr Edit

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