Empathy don't save the salon's history after a wifi's cut
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Telepathy Indicator |
New
|
Undecided
|
Unassigned | ||
telepathy-idle |
New
|
Undecided
|
|||
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
ProcVersionSign
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/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fdff9e35f84 <g_io_stream_
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_
idle_server_
?? ()
?? () from /lib/x86_
g_main_
Title: telepathy-idle crashed with SIGSEGV in g_io_stream_
UpgradeStatus: Upgraded to precise on 2012-03-12 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 |
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.