Bug 1373029

Summary: [abrt] redshift-gtk: statusicon.py:148:_child_signal:ProcessLookupError: [Errno 3] No such process
Product: [Fedora] Fedora Reporter: fiendishx
Component: redshiftAssignee: Miloš Komarčević <kmilos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: kmilos, oliver
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9ac2ae6bd417cd14dcdf1815aa970e932b0050b3
Whiteboard: abrt_hash:468794dcebf78f262906334e8d9daf8b87bf15cb;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:01:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description fiendishx 2016-09-04 23:01:27 UTC
Version-Release number of selected component:
redshift-gtk-1.11-2.fc24

Additional info:
reporter:       libreport-2.7.2
cmdline:        python3 /usr/bin/redshift-gtk
executable:     /usr/bin/redshift-gtk
kernel:         4.6.7-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
statusicon.py:148:_child_signal:ProcessLookupError: [Errno 3] No such process

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/redshift_gtk/statusicon.py", line 169, in _child_cb
    GLib.spawn_check_exit_status(status)
GLib.GError: g-exec-error-quark: Child process killed by signal 10 (19)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/redshift_gtk/statusicon.py", line 400, in toggle_cb
    self._controller.set_inhibit(not self._controller.inhibited)
  File "/usr/lib/python3.5/site-packages/redshift_gtk/statusicon.py", line 144, in set_inhibit
    self._child_toggle_inhibit()
  File "/usr/lib/python3.5/site-packages/redshift_gtk/statusicon.py", line 152, in _child_toggle_inhibit
    self._child_signal(signal.SIGUSR1)
  File "/usr/lib/python3.5/site-packages/redshift_gtk/statusicon.py", line 148, in _child_signal
    os.kill(self._process[0], sg)
ProcessLookupError: [Errno 3] No such process

Local variables in innermost frame:
sg: <Signals.SIGUSR1: 10>
self: <statusicon.RedshiftController object at 0x7f8e047a6e58 (redshift_gtk+statusicon+RedshiftController at 0x559889c33c00)>

Comment 1 fiendishx 2016-09-04 23:01:32 UTC
Created attachment 1197714 [details]
File: backtrace

Comment 2 fiendishx 2016-09-04 23:01:33 UTC
Created attachment 1197715 [details]
File: environ

Comment 3 Fedora End Of Life 2017-07-25 22:50:05 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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 24 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 4 Fedora End Of Life 2017-08-08 17:01:09 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.