Bug 1589669

Summary: [abrt] redshift-gtk: _child_cb(): statusicon.py:148:_child_signal:ProcessLookupError: [Errno 3] No such process
Product: [Fedora] Fedora Reporter: Patrick Laxton <patrick.laxton>
Component: redshiftAssignee: Miloš Komarčević <kmilos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: fry.futurateam, kmilos, oliver
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7928e7124ba8f2b1c5cf02edf36a3cc2a1f0e2d3
Whiteboard: abrt_hash:468794dcebf78f262906334e8d9daf8b87bf15cb;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 21:51: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: backtrace
none
File: cgroup
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Patrick Laxton 2018-06-11 06:42:02 UTC
Description of problem:
redshift seems to be unable to get my position

Version-Release number of selected component:
redshift-gtk-1.11-8.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        /usr/bin/python3 /usr/bin/redshift-gtk
crash_function: _child_cb
exception_type: GLib.GError
executable:     /usr/bin/redshift-gtk
interpreter:    python3-3.6.5-1.fc28.x86_64
kernel:         4.16.14-300.fc28.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: Le processus fils s’est terminé avec le 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 400, in toggle_cb
    self._controller.set_inhibit(not self._controller.inhibited)
  File "/usr/lib/python3.6/site-packages/redshift_gtk/statusicon.py", line 144, in set_inhibit
    self._child_toggle_inhibit()
  File "/usr/lib/python3.6/site-packages/redshift_gtk/statusicon.py", line 152, in _child_toggle_inhibit
    self._child_signal(signal.SIGUSR1)
  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.SIGUSR1: 10>
self: <statusicon.RedshiftController object at 0x7f418ffb07e0 (redshift_gtk+statusicon+RedshiftController at 0x55780ebefda0)>

Potential duplicate: bug 1483086

Comment 1 Patrick Laxton 2018-06-11 06:42:06 UTC
Created attachment 1449901 [details]
File: backtrace

Comment 2 Patrick Laxton 2018-06-11 06:42:07 UTC
Created attachment 1449902 [details]
File: cgroup

Comment 3 Patrick Laxton 2018-06-11 06:42:08 UTC
Created attachment 1449903 [details]
File: cpuinfo

Comment 4 Patrick Laxton 2018-06-11 06:42:10 UTC
Created attachment 1449904 [details]
File: environ

Comment 5 Patrick Laxton 2018-06-11 06:42:11 UTC
Created attachment 1449905 [details]
File: mountinfo

Comment 6 Patrick Laxton 2018-06-11 06:42:12 UTC
Created attachment 1449906 [details]
File: namespaces

Comment 7 Patrick Laxton 2018-06-11 06:42:13 UTC
Created attachment 1449907 [details]
File: open_fds

Comment 8 Ben Cotton 2019-05-02 19:23:17 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 Ben Cotton 2019-05-02 21:18:47 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 10 Ben Cotton 2019-05-28 21:51:42 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.