Bug 1483086

Summary: [abrt] redshift-gtk: _child_cb(): statusicon.py:148:_child_signal:ProcessLookupError: [Errno 3] No such process
Product: [Fedora] Fedora Reporter: Miroslav Avramov <apexengine>
Component: redshiftAssignee: Miloš Komarčević <kmilos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: bitchecker, kmilos, oliver
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7928e7124ba8f2b1c5cf02edf36a3cc2a1f0e2d3
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: 2018-05-29 11:38:11 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: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Miroslav Avramov 2017-08-18 17:51:02 UTC
Version-Release number of selected component:
redshift-gtk-1.11-5.fc26

Additional info:
reporter:       libreport-2.9.1
cmdline:        python3 /usr/bin/redshift-gtk
crash_function: _child_cb
exception_type: GLib.GError
executable:     /usr/bin/redshift-gtk
kernel:         4.12.5-300.fc26.x86_64
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.6/site-packages/redshift_gtk/statusicon.py", line 169, in _child_cb
    GLib.spawn_check_exit_status(status)
GLib.GError: g-spawn-exit-error-quark: Child process exited with code 1 (1)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/redshift_gtk/statusicon.py", line 510, in terminate_child
    c.terminate_child()
  File "/usr/lib/python3.6/site-packages/redshift_gtk/statusicon.py", line 235, in terminate_child
    self._child_signal(signal.SIGINT)
  File "/usr/lib/python3.6/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.SIGINT: 2>
self: <statusicon.RedshiftController object at 0x7f9758421ca8 (redshift_gtk+statusicon+RedshiftController at 0x7f97500019a0)>

Potential duplicate: bug 1373029

Comment 1 Miroslav Avramov 2017-08-18 17:51:08 UTC
Created attachment 1315341 [details]
File: backtrace

Comment 2 Miroslav Avramov 2017-08-18 17:51:09 UTC
Created attachment 1315342 [details]
File: cgroup

Comment 3 Miroslav Avramov 2017-08-18 17:51:11 UTC
Created attachment 1315343 [details]
File: cpuinfo

Comment 4 Miroslav Avramov 2017-08-18 17:51:12 UTC
Created attachment 1315344 [details]
File: environ

Comment 5 Miroslav Avramov 2017-08-18 17:51:14 UTC
Created attachment 1315345 [details]
File: mountinfo

Comment 6 Miroslav Avramov 2017-08-18 17:51:15 UTC
Created attachment 1315346 [details]
File: namespaces

Comment 7 Miroslav Avramov 2017-08-18 17:51:17 UTC
Created attachment 1315347 [details]
File: open_fds

Comment 8 Fedora End Of Life 2018-05-03 08:13:56 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 9 Fedora End Of Life 2018-05-29 11:38:11 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.