empathy-accounts crashed with SIGSEGV in empathy_account_settings_get_account()

Bug #938696 reported by gogo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Expired
Medium
Unassigned

Bug Description

empathy-accounts crashed with SIGSEGV in empathy_account_settings_get_account()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Wed Feb 22 14:57:28 2012
ExecutablePath: /usr/bin/empathy-accounts
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120207)
ProcCmdline: empathy-accounts
ProcEnviron:
 PATH=(custom, no user)
 LANG=hr_HR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x457320 <empathy_account_settings_get_account>: mov 0x18(%rdi),%rax
 PC (0x00457320) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 empathy_account_settings_get_account ()
 ?? ()
 g_closure_invoke () 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
Title: empathy-accounts crashed with SIGSEGV in empathy_account_settings_get_account()
UpgradeStatus: Upgraded to precise on 2012-02-18 (3 days ago)
UserGroups: adm cdrom debian-tor dip disk lpadmin plugdev sambashare sudo

Revision history for this message
gogo (trebelnik-stefina) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 empathy_account_settings_get_account (settings=0x0) at empathy-account-settings.c:784
 account_dialow_show_edit_params_dialog (dialog=0x25ec040, button=<optimized out>) at empathy-accounts-dialog.c:663
 g_closure_invoke (closure=0x26d4d40, return_value=0x0, n_param_values=1, param_values=0x293a8e0, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.18/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x293a8e0) at /build/buildd/glib2.0-2.31.18/./gobject/gsignal.c:3302
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff25793968) at /build/buildd/glib2.0-2.31.18/./gobject/gsignal.c:3033

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible now ?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in empathy (Ubuntu):
status: New → Incomplete
Revision history for this message
Bilal Shahid (s9iper1) wrote :

attaching upstream bug

Revision history for this message
Bilal Shahid (s9iper1) wrote :

sorry for the last comment

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for empathy (Ubuntu) because there has been no activity for 60 days.]

Changed in empathy (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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