Version-Release number of selected component: anaconda-18.6.1-1.fc18.x86_64 Additional info: libreport version: 2.0.13 cmdline: initrd=initrd0.img root=live:CDLABEL=fedora-livec-x86_64-201208271518 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 kernel: 3.6.0-0.rc2.git2.1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.6.1 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 51, in setup : super(LiveImagePayload, self).setup() : File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 645, in payloadInitialize : payload.setup(storage) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 87, in run : threading.Thread.run(self, *args, **kwargs) :TypeError: setup() takes exactly 2 arguments (1 given)
Created attachment 607394 [details] File: ifcfg.log
Created attachment 607395 [details] File: anaconda-tb
Created attachment 607396 [details] File: environ
Created attachment 607397 [details] File: type
Created attachment 607398 [details] File: storage.log
Created attachment 607399 [details] File: other involved packages
Created attachment 607400 [details] File: program.log
Created attachment 607401 [details] File: product
Created attachment 607402 [details] File: anaconda.log
Created attachment 607403 [details] File: hashmarkername
Created attachment 607404 [details] File: version
Created attachment 607405 [details] File: release
Created attachment 607406 [details] File: messages
This was experienced using the latest anaconda live cd build here: http://dl.fedoraproject.org/pub/alt/anaconda/livecd-fedora-livecd-desktop-201208271518.iso
I believe this is related to SELinux. I am attaching a screenshot.
Created attachment 607407 [details] selinux alerts when running anaconda
It's got nothign to do with selinux.
I just noticed those SELinux alerts at the same time.
Not experiencing this issue anymore.