Bug 1204883

Summary: RuntimeError: Unable to register enum 'PyNetworkManagerState'
Product: [Fedora] Fedora Reporter: Ivan Pacheco <kinokoio>
Component: pygobject3Assignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, awilliam, bochecha, g.kaviyarasu, icq, john.j5live, jonathan, rvykydal, satellitgo, vanmeeuwen+fedora, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:218cd95cd6768535eaeaef4965d440090bc7de1feb25262d7726819f599e56b0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:10:12 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: anaconda-tb
none
File: anaconda.log
none
File: environ
none
File: journalctl
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: ifcfg.log
none
patch suggested by bochecha none

Description Ivan Pacheco 2015-03-23 16:57:45 UTC
Description of problem:
Just entered the installer.

F22 Beta TC4 Workstation Live

Version-Release number of selected component:
anaconda-core-22.20.6-1.fc22.i686

The following was filed automatically by anaconda:
anaconda 22.20.6-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/gi/module.py", line 155, in __getattr__
    wrapper = enum_register_new_gtype_and_add(info)
  File "/usr/lib/python2.7/site-packages/pyanaconda/nm.py", line 153, in nm_is_connected
    return nm_state() in (NetworkManager.State.CONNECTED_GLOBAL,
  File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 1258, in _wait_for_connecting_NM
    if nm.nm_is_connected():
  File "/usr/lib/python2.7/site-packages/pyanaconda/network.py", line 1292, in wait_for_connecting_NM_thread
    connected = _wait_for_connecting_NM()
  File "/usr/lib/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 238, in run
    threading.Thread.run(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 112, in wait
    self.raise_if_error(name)
  File "/usr/lib/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 1216, in _runThread
    threadMgr.wait(THREAD_WAIT_FOR_CONNECTING_NM)
  File "/usr/lib/python2.7/threading.py", line 766, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 238, in run
    threading.Thread.run(self, *args, **kwargs)
RuntimeError: Unable to register enum 'PyNetworkManagerState'

Additional info:
cmdline:        /usr/bin/python2  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base
cmdline_file:   BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-22_B-T4 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.0.0-0.rc3.git0.1.fc22.i686
other involved packages: pygobject3-base-3.15.91-1.fc22.i686, python-libs-2.7.9-5.fc22.i686
product:        Fedora"
release:        Fedora release 22 (Twenty Two)
type:           anaconda
version:        Fedora

Comment 1 Ivan Pacheco 2015-03-23 16:57:48 UTC
Created attachment 1005492 [details]
File: anaconda-tb

Comment 2 Ivan Pacheco 2015-03-23 16:57:49 UTC
Created attachment 1005493 [details]
File: anaconda.log

Comment 3 Ivan Pacheco 2015-03-23 16:57:50 UTC
Created attachment 1005494 [details]
File: environ

Comment 4 Ivan Pacheco 2015-03-23 16:57:52 UTC
Created attachment 1005495 [details]
File: journalctl

Comment 5 Ivan Pacheco 2015-03-23 16:57:52 UTC
Created attachment 1005496 [details]
File: lsblk_output

Comment 6 Ivan Pacheco 2015-03-23 16:57:53 UTC
Created attachment 1005497 [details]
File: nmcli_dev_list

Comment 7 Ivan Pacheco 2015-03-23 16:57:54 UTC
Created attachment 1005498 [details]
File: os_info

Comment 8 Ivan Pacheco 2015-03-23 16:57:55 UTC
Created attachment 1005499 [details]
File: program.log

Comment 9 Ivan Pacheco 2015-03-23 16:57:56 UTC
Created attachment 1005500 [details]
File: storage.log

Comment 10 Ivan Pacheco 2015-03-23 16:57:57 UTC
Created attachment 1005501 [details]
File: ifcfg.log

Comment 11 Adam Williamson 2015-03-23 18:03:26 UTC
I can't reproduce this just by booting the i686 F22 Beta TC4 Workstation live in a VM and running the installer, FWIW, must be somehow sporadic or system specific.

The error comes from pygobject, but it's possible there's a problem in how anaconda uses it. In addition to the traceback I see a warning:

12:52:37,085 WARN anaconda: /usr/lib/python2.7/site-packages/gi/module.py:155: Warning: cannot register existing type 'PyNetworkManagerState'
  wrapper = enum_register_new_gtype_and_add(info)

Comment 12 Adam Williamson 2015-03-23 18:40:00 UTC
clumens and I both rather suspect this is a pygobject issue - the error is raised from pygobject code, and the anaconda code really doesn't seem to take any responsibility for the init stuff that's failing here, it's just leaving it to pygobject.

I am generally suspicious of this commit:

https://git.gnome.org/browse/pygobject/commit/?id=149c31beced944c72fba6ca6e096c81c1100ea2b

which seems to have touched the affected code fairly recently in a pretty extensive overhaul, but I can't point to anything specific.

The anaconda code here is:

https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/nm.py#L87-L156

Comment 13 Adam Williamson 2015-03-27 19:26:54 UTC
I just hit this one time booting the Beta TC5 Server x86_64 netinst with 'debug' on the cmdline, but then booted again and didn't hit it, so it seems to just be one of those things that only goes wrong occasionally, somehow timing-related.

Someone in #fedora-desktop had a suggestion for a change in anaconda's way of dealing with NM here, but I don't think I have it handy - I'll have to dig it out of my IRC logs in a bit.

Comment 14 Adam Williamson 2015-03-27 19:36:19 UTC
Created attachment 1007453 [details]
patch suggested by bochecha

bochecha suggested that anaconda's interface with NM could be changed here. The patch he pasted for me is attached; I don't know enough to know if it's a good idea or not.

Comment 15 David Shea 2015-07-23 19:27:39 UTC
*** Bug 1220953 has been marked as a duplicate of this bug. ***

Comment 16 Fedora Admin XMLRPC Client 2016-01-27 17:42:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 17 Fedora Admin XMLRPC Client 2016-01-27 17:58:44 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 18 Fedora Admin XMLRPC Client 2016-01-27 17:59:45 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 19 David Shea 2016-01-27 18:03:51 UTC
(In reply to Fedora Admin XMLRPC Client from comment #17)
> This package has changed ownership in the Fedora Package Database. 
> Reassigning to the new owner of this component.

Sorry about that, I'm bad at computers. Why is this package orphaned, though?

Comment 20 Fedora Admin XMLRPC Client 2016-01-27 18:11:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 21 Fedora End Of Life 2016-07-19 13:10:12 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.