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


** Visibility changed to: Public

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

Title:
  empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid()

Status in “empathy” package in Ubuntu:
  New

Bug description:
  Unable to open chat window since last Empathy updates.
  It seems to crash every time.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.5.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
  Uname: Linux 3.5.0-5-generic x86_64
  ApportVersion: 2.4-0ubuntu3
  Architecture: amd64
  Date: Fri Jul 20 00:18:55 2012
  ExecutablePath: /usr/lib/empathy/empathy-chat
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  ProcCmdline: /usr/lib/empathy/empathy-chat
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=nl:en_AU:en
   LANG=nl_BE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x4605ca <empathy_adium_path_is_valid+26>:     cmpb   
$0x2f,(%rdi)
   PC (0x004605ca) ok
   source "$0x2f" ok
   destination "(%rdi)" (0x00000000) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: empathy
  StacktraceTop:
   empathy_adium_path_is_valid ()
   empathy_adium_info_new ()
   empathy_adium_data_new ()
   ?? ()
   ?? ()
  Title: empathy-chat crashed with SIGSEGV in empathy_adium_path_is_valid()
  UpgradeStatus: Upgraded to quantal on 2012-06-19 (29 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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