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

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 #1194079, 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/1220402/+attachment/3801367/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1194079
   evolution-calendar-factory crashed with SIGSEGV in g_type_check_instance()

** Information type changed from Private Security to Public Security

** Tags removed: need-amd64-retrace

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in
  g_type_check_instance()

Status in “evolution-data-server” package in Ubuntu:
  New

Bug description:
  no mas que decir que ayudenme por favor a solucionar estos errores

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep  2 03:19:51 2013
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  ExecutableTimestamp: 1374779878
  InstallationDate: Installed on 2013-05-30 (94 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  ProcCwd: /home/ariel
  SegvAnalysis:
   Segfault happened at: 0x7ff73c8a6719 <g_type_check_instance+25>:     mov    
(%rax),%rdi
   PC (0x7ff73c8a6719) ok
   source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_type_check_instance () 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
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: evolution-calendar-factory crashed with SIGSEGV in 
g_type_check_instance()
  UpgradeStatus: Upgraded to saucy on 2013-06-03 (90 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1220402/+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