Bug 859667

Summary: [abrt] emerillon-0.1.90-8.fc17: position_changed_cb: Process /usr/bin/emerillon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Twing Slice <twing>
Component: emerillonAssignee: Peter Robinson <pbrobinson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:96c69ff7b4c7abe73a942601d3f72de4ce3b1fd7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:27:42 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description Twing Slice 2012-09-23 02:33:37 UTC
Version-Release number of selected component:
emerillon-0.1.90-8.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        emerillon
crash_function: position_changed_cb
kernel:         3.5.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (5 frames)
: #0 position_changed_cb at window.c
: #5 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c
: #10 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c
: #11 dbus_g_proxy_manager_filter at dbus-gproxy.c
: #19 gtk_main at gtkmain.c

Comment 1 Twing Slice 2012-09-23 02:33:40 UTC
Created attachment 615960 [details]
File: core_backtrace

Comment 2 Twing Slice 2012-09-23 02:33:42 UTC
Created attachment 615961 [details]
File: environ

Comment 3 Twing Slice 2012-09-23 02:33:45 UTC
Created attachment 615962 [details]
File: backtrace

Comment 4 Twing Slice 2012-09-23 02:33:47 UTC
Created attachment 615963 [details]
File: limits

Comment 5 Twing Slice 2012-09-23 02:33:49 UTC
Created attachment 615964 [details]
File: cgroup

Comment 6 Twing Slice 2012-09-23 02:33:52 UTC
Created attachment 615965 [details]
File: maps

Comment 7 Twing Slice 2012-09-23 02:33:54 UTC
Created attachment 615966 [details]
File: dso_list

Comment 8 Twing Slice 2012-09-23 02:33:56 UTC
Created attachment 615967 [details]
File: var_log_messages

Comment 9 Twing Slice 2012-09-23 02:33:58 UTC
Created attachment 615968 [details]
File: open_fds

Comment 10 Fedora End Of Life 2013-07-04 02:29:06 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 11 Fedora End Of Life 2013-08-01 08:27:46 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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