Bug 1045602

Summary: OSError: [Errno 3] Proces bestaat niet
Product: [Fedora] Fedora Reporter: Ben Lambrechts <benedictus>
Component: network-manager-appletAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dcbw, g.kaviyarasu, jklimes, jonathan, rvykydal, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:048d73b187bb0600b7e98a56ac7572dd14b26311bb7b95b262b458e00a8bd0c0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:40: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:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description Ben Lambrechts 2013-12-20 20:13:45 UTC
Version-Release number of selected component:
anaconda-20.25.15-1

The following was filed automatically by anaconda:
anaconda 20.25.15-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/subprocess.py", line 1527, in send_signal
    os.kill(self.pid, sig)
  File "/usr/lib64/python2.7/subprocess.py", line 1537, in kill
    self.send_signal(signal.SIGKILL)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 453, in kill_nmce
    self._running_nmce.kill()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 442, in on_edit_connection
    self.kill_nmce(msg="Configure button clicked")
OSError: [Errno 3] Proces bestaat niet

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.10-301.fc20.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        20

Comment 1 Ben Lambrechts 2013-12-20 20:13:49 UTC
Created attachment 839771 [details]
File: anaconda-tb

Comment 2 Ben Lambrechts 2013-12-20 20:13:52 UTC
Created attachment 839772 [details]
File: anaconda.log

Comment 3 Ben Lambrechts 2013-12-20 20:13:55 UTC
Created attachment 839773 [details]
File: environ

Comment 4 Ben Lambrechts 2013-12-20 20:13:57 UTC
Created attachment 839774 [details]
File: lsblk_output

Comment 5 Ben Lambrechts 2013-12-20 20:13:59 UTC
Created attachment 839775 [details]
File: nmcli_dev_list

Comment 6 Ben Lambrechts 2013-12-20 20:14:01 UTC
Created attachment 839776 [details]
File: os_info

Comment 7 Ben Lambrechts 2013-12-20 20:14:04 UTC
Created attachment 839777 [details]
File: program.log

Comment 8 Ben Lambrechts 2013-12-20 20:14:08 UTC
Created attachment 839778 [details]
File: storage.log

Comment 9 Ben Lambrechts 2013-12-20 20:14:12 UTC
Created attachment 839779 [details]
File: syslog

Comment 10 Ben Lambrechts 2013-12-20 20:14:14 UTC
Created attachment 839780 [details]
File: ifcfg.log

Comment 11 Ben Lambrechts 2013-12-20 20:14:20 UTC
Created attachment 839781 [details]
File: packaging.log

Comment 12 Radek Vykydal 2014-01-02 13:53:59 UTC
from syslog:

20:12:34,042 INFO kernel:[  241.956360] nm-connection-e[1190]: segfault at 4 ip 00007fabc4702f78 sp 00007fffa4aa7ce0 error 4 in libgtk-3.so.0.1000.4[7fabc4447000+509000]

The root cause is nm-connection-editor called by anaconda crashing for some reason. Anaconda is then trying to kill the (already crashed nm-c-e) on second [Configure] click, which results in exception and the traceback. Anaconda could handle the exception gracefully in this case, nevertheless we should also investigate why nm-c-e is crashing.

Ifcfg files content when invoking nm-c-e can be seen in comment #10.

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

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 20 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-06-29 13:40:33 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.