telepathy-haze segfault
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-
Jul 17 11:01:53 user gdm-simple-
Jul 17 11:01:54 user kernel: [ 890.390803] __ratelimit: 9 callbacks suppressed
Jul 17 11:01:54 user kernel: [ 890.390810] telepathy-
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
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-
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-
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-
Jul 17 11:01:58 user bonobo-
Jul 17 11:02:08 user init: tty2 main process ended, respawning
description: | updated |
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.