empathy crashed with SIGABRT in raise()

Bug #746603 reported by Will Olbrys
104
This bug affects 23 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: empathy

i think this happened because the empathy window tried to start on a monitor that wasn't available at the time.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.33.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: vmblock
Architecture: amd64
Date: Thu Mar 31 13:48:31 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: empathy
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: empathy crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:1600): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
 (nautilus:1600): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
 (nautilus:1600): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
 (nautilus:1600): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
 (nautilus:1600): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Will Olbrys (willolbrys) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=0x7fdc749e2d50 "settings_backend_path_changed", message=0x1095990 "assertion failed: (settings->priv->backend == backend)") at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1358
 g_assertion_message_expr (domain=0x7fdc749ca401 "GLib-GIO", file=0x7fdc749e2f78 "/build/buildd/glib2.0-2.28.4/./gio/gsettings.c", line=338, func=0x7fdc749e2d50 "settings_backend_path_changed", expr=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1369
 settings_backend_path_changed (target=0x1054990, backend=<value optimized out>, path=<value optimized out>, origin_tag=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./gio/gsettings.c:338

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
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Evan Huus (eapache) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are very sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

---
Evan Huus
Ubuntu Bug Squad Volunteer
https://wiki.ubuntu.com/BugSquad

Changed in empathy (Ubuntu):
status: New → Incomplete
Revision history for this message
Ian Nicholson (imnichol) wrote :

I just experienced this after the upgrade from 11.04 to 11.10

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
Revision history for this message
Ian Nicholson (imnichol) wrote :

When I first click on the messaging icon and then on "chat" after starting my computer, te empathy icon appears for a split second on my dock before disappearing. I believe this behavior is caused by this bug. How can I test it now that apport is no longer enabled?

Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :

Empathy crashed on startup of Unity 2D in Ubuntu 12.04 LTS Beta 1 (nightly build).

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

the people who are having this crash one of you mark it confirm and than one of you can upstream it and answer the developer there,, and share the upstream link here .

Changed in empathy (Ubuntu):
status: New → Confirmed
Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :

1) Ubuntu 12.04 LTS - just after a fresh installation and with all the newest updates

2) empathy: Installiert: 3.3.92-0ubuntu3
unity-2d: Installiert: 5.8.0-0ubuntu1

3) You just start a new Unity 2D session.

4) Within two minutes after the start, you have this bugreport coming up.

How to get this bug
Before this bug is triggered, you have first to logout from a Unity 2D session - and then start a new one from LightDM. Now within 2 minutes, you normally should get this bug and send here.
Condition: In the old session, you had empathy running, while in the new session you yet didn't start it. Sounds weird but is a fact.
The bug does not occure, if the Unity 2D session is the first one after a cold start of the computer.

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

any body upstream it please and attach the link with the bug and also subscribe with the bug in upstream

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.