*** This bug is a duplicate of bug 1065674 ***
    https://bugs.launchpad.net/bugs/1065674

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 #1065674, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421807/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421809/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421810/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421811/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421812/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421813/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1074381/+attachment/3421814/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1065674

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-indicator in Ubuntu.
https://bugs.launchpad.net/bugs/1074381

Title:
  telepathy-indicator crashed with SIGSEGV in
  g_cclosure_marshal_VOID__STRINGv()

Status in “telepathy-indicator” package in Ubuntu:
  New

Bug description:
  I had an open chat window, and someone sent me a message. Then, I
  noticed that the notification indicator was on, so I went to the mail
  icon on the bar, and clicked the new notification in the menu for the
  same person I was already chatting with. Then it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: telepathy-indicator 0.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov  2 09:23:13 2012
  ExecutablePath: /usr/bin/telepathy-indicator
  InstallationDate: Installed on 2012-07-17 (107 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  MarkForUpload: True
  ProcCmdline: telepathy-indicator
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x404205:      mov    0x8(%rax),%r8
   PC (0x00404205) ok
   source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%r8" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-indicator
  StacktraceTop:
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: telepathy-indicator crashed with SIGSEGV in 
g_cclosure_marshal_VOID__STRINGv()
  UpgradeStatus: Upgraded to quantal on 2012-10-05 (28 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-indicator/+bug/1074381/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to