telepathy-haze segfault

Bug #606609 reported by Mr. Blonde
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-haze (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: telepathy-haze

___________________

Ubuntu Lucid
telepathy-haze 0.3.4-1
___________________

This segfault somehow caused me to be logged out of the session. I was writing a message when it occured.

Jul 17 11:01:53 user console-kit-daemon[781]: WARNING: Couldn't read /proc/1427/environ: Failed to open file '/proc/1427/environ': No such file or directory
Jul 17 11:01:53 user gdm-simple-slave[2401]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
Jul 17 11:01:54 user kernel: [ 890.390803] __ratelimit: 9 callbacks suppressed
Jul 17 11:01:54 user kernel: [ 890.390810] telepathy-haze[2059]: segfault at f8 ip 00be1aa7 sp bfd169f0 error 4 in liboscar.so.0.0.0[ba9000+42000]
Jul 17 11:01:54 user acpid: client 916[0:0] has disconnected
Jul 17 11:01:54 user acpid: client 916[0:0] has disconnected
Jul 17 11:01:54 user acpid: client connected from 2404[0:0]
Jul 17 11:01:54 user acpid: 1 client rule loaded
Jul 17 11:01:54 user pulseaudio[2397]: pid.c: Stale PID file, overwriting.
Jul 17 11:01:54 user pulseaudio[2397]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-bpGQ0ZFQ8I: Connection refused
Jul 17 11:01:54 user pulseaudio[2409]: pid.c: Daemon already running.
Jul 17 11:01:54 user acpid: client connected from 2404[0:0]
Jul 17 11:01:54 user acpid: 1 client rule loaded
Jul 17 11:01:55 user gdm-session-worker[2444]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
Jul 17 11:01:55 user rtkit-daemon[1229]: Sucessfully made thread 2448 of process 2448 (n/a) owned by '114' high priority at nice level -11.
Jul 17 11:01:55 user rtkit-daemon[1229]: Supervising 1 threads of 1 processes of 2 users.
Jul 17 11:01:56 user gdm-simple-greeter[2442]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.1/gtk/gtkwidget.c:5636: widget not within a GtkWindow
Jul 17 11:01:56 user rtkit-daemon[1229]: Sucessfully made thread 2457 of process 2448 (n/a) owned by '114' RT at priority 5.
Jul 17 11:01:56 user rtkit-daemon[1229]: Supervising 2 threads of 1 processes of 2 users.
Jul 17 11:01:56 user rtkit-daemon[1229]: Sucessfully made thread 2458 of process 2448 (n/a) owned by '114' RT at priority 5.
Jul 17 11:01:56 user rtkit-daemon[1229]: Supervising 3 threads of 1 processes of 2 users.
Jul 17 11:01:58 user gdm-session-worker[2444]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Jul 17 11:01:58 user bonobo-activation-server (odin-2462): could not associate with desktop session: Failed to connect to socket /tmp/dbus-bpGQ0ZFQ8I: Connection refused
Jul 17 11:02:08 user init: tty2 main process ended, respawning

Mr. Blonde (mr.blonde)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in telepathy-haze (Ubuntu):
importance: Undecided → Low
status: New → Invalid
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.