Bug 963177

Summary: [abrt] telepathy-haze-0.6.0-3.fc18: sipe_backend_media_set_cname: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Louis van Dyk <louis>
Component: telepathy-hazeAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fc09bd05f9bc2511eeb3585ff5aec139ee257dd4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:22:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Louis van Dyk 2013-05-15 10:43:24 UTC
Description of problem:
After suspending the laptop, when switching on again, haze crashes.

Version-Release number of selected component:
telepathy-haze-0.6.0-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/telepathy-haze
crash_function: sipe_backend_media_set_cname
executable:     /usr/libexec/telepathy-haze
kernel:         3.8.8-202.fc18.x86_64
uid:            1000
ureports_counter: 8

Truncated backtrace:
Thread no. 1 (6 frames)
 #1 sipe_backend_media_set_cname at purple-media.c:295
 #2 sipe_media_call_new at sipe-media.c:689
 #3 process_incoming_invite_call at sipe-media.c:893
 #4 sip_transport_input at sip-transport.c:1643
 #5 purple_glib_io_invoke at main.c:89
 #10 tp_run_connection_manager at run.c:285

Potential duplicate: bug 851759

Comment 1 Louis van Dyk 2013-05-15 10:43:30 UTC
Created attachment 748185 [details]
File: backtrace

Comment 2 Louis van Dyk 2013-05-15 10:43:36 UTC
Created attachment 748186 [details]
File: cgroup

Comment 3 Louis van Dyk 2013-05-15 10:43:41 UTC
Created attachment 748187 [details]
File: core_backtrace

Comment 4 Louis van Dyk 2013-05-15 10:43:46 UTC
Created attachment 748188 [details]
File: dso_list

Comment 5 Louis van Dyk 2013-05-15 10:43:53 UTC
Created attachment 748189 [details]
File: environ

Comment 6 Louis van Dyk 2013-05-15 10:43:57 UTC
Created attachment 748190 [details]
File: limits

Comment 7 Louis van Dyk 2013-05-15 10:44:05 UTC
Created attachment 748191 [details]
File: maps

Comment 8 Louis van Dyk 2013-05-15 10:44:11 UTC
Created attachment 748192 [details]
File: open_fds

Comment 9 Louis van Dyk 2013-05-15 10:44:16 UTC
Created attachment 748193 [details]
File: proc_pid_status

Comment 10 Louis van Dyk 2013-05-15 10:44:21 UTC
Created attachment 748194 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-12-21 13:32:47 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2014-02-05 21:22:41 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.