Bug 31557 - telepathy-sofiasip-0.6.4: raise: Process /usr/libexec/telepathy-sofiasip was killed by signal 6
Summary: telepathy-sofiasip-0.6.4: raise: Process /usr/libexec/telepathy-sofiasip was ...
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: rakia (show other bugs)
Version: 0.10
Hardware: Other All
: low normal
Assignee: Mikhail Zabaluev
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-11 13:21 UTC by Brian Pepple
Modified: 2019-12-03 19:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Backtrace (7.57 KB, text/plain)
2010-11-11 13:21 UTC, Brian Pepple 		Details
View All

Description Brian Pepple 2010-11-11 13:21:48 UTC 
Created attachment 40213 [details]
Backtrace

abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-sofiasip
component: telepathy-sofiasip
crash_function: raise
executable: /usr/libexec/telepathy-sofiasip
kernel: 2.6.35.6-48.fc14.i686
package: telepathy-sofiasip-0.6.4-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-sofiasip was killed by signal 6
(SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289492748
uid: 500

Original bug: https://bugzilla.redhat.com/show_bug.cgi?id=652421
Comment 1 Mikhail Zabaluev 2011-01-17 00:52:21 UTC 
This seems to occur during shutdown. As we have no state to save and all Telepathy objects should be finalized by this point (kick me if they aren't), this is a low priority issue.
Comment 2 GitLab Migration User 2019-12-03 19:37:04 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-rakia/issues/14.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.