Bug 1012869

Summary: [abrt] gtk-redshift-1.7-5.fc19: PyErr_Occurred: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: daramas444
Component: redshiftAssignee: Miloš Komarčević <kmilos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: kmilos, valent.turkovic
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:50e572e753e4f16045ec15b2e31ea681bcb18ec7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:22:33 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description daramas444 2013-09-27 09:44:45 UTC
Description of problem:
gtk-redshift is launched
right clic on the icon in the toolbar, quit
get this crash

repetable every single time

Version-Release number of selected component:
gtk-redshift-1.7-5.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        python /usr/bin/gtk-redshift
crash_function: PyErr_Occurred
executable:     /usr/bin/python2.7
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 PyErr_Occurred at /usr/src/debug/Python-2.7.5/Python/errors.c:80
 #1 collect at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:1097
 #2 PyGC_Collect at /usr/src/debug/Python-2.7.5/Modules/gcmodule.c:1514
 #3 Py_Finalize at /usr/src/debug/Python-2.7.5/Python/pythonrun.c:444
 #4 Py_Main at /usr/src/debug/Python-2.7.5/Modules/main.c:665
 #5 __libc_start_main at libc-start.c:274
 #6 _start

Comment 1 daramas444 2013-09-27 09:44:59 UTC
Created attachment 803841 [details]
File: backtrace

Comment 2 daramas444 2013-09-27 09:45:15 UTC
Created attachment 803842 [details]
File: cgroup

Comment 3 daramas444 2013-09-27 09:45:19 UTC
Created attachment 803843 [details]
File: core_backtrace

Comment 4 daramas444 2013-09-27 09:45:22 UTC
Created attachment 803844 [details]
File: dso_list

Comment 5 daramas444 2013-09-27 09:45:25 UTC
Created attachment 803845 [details]
File: environ

Comment 6 daramas444 2013-09-27 09:45:30 UTC
Created attachment 803846 [details]
File: exploitable

Comment 7 daramas444 2013-09-27 09:45:34 UTC
Created attachment 803847 [details]
File: limits

Comment 8 daramas444 2013-09-27 09:45:39 UTC
Created attachment 803848 [details]
File: maps

Comment 9 daramas444 2013-09-27 09:45:53 UTC
Created attachment 803849 [details]
File: open_fds

Comment 10 daramas444 2013-09-27 09:45:58 UTC
Created attachment 803850 [details]
File: proc_pid_status

Comment 11 daramas444 2013-09-27 09:46:03 UTC
Created attachment 803851 [details]
File: var_log_messages

Comment 12 Valent Turkovic 2013-10-16 13:13:24 UTC
Hi guys,
I just saw this issue on Ubuntu bugtracker:
https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/868904

Issue is with missing geoclue-hostip as dependency...

Could this also be issue in Fedora?

Comment 13 Fedora End Of Life 2015-01-09 20:00:16 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 14 Fedora End Of Life 2015-02-17 17:22:33 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.