Description of problem:
Selected Software Development
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.19 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 193, in execWithRedirect
: raise RuntimeError, errstr
: File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1300, in execute
: File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 58, in doConfiguration
: ksdata.services.execute(storage, ksdata, instClass)
: 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 91, in run
: threading.Thread.run(self, *args, **kwargs)
:RuntimeError: Error running systemctl: No such file or directory
Created attachment 632379 [details]
Created attachment 632380 [details]
Created attachment 632381 [details]
Created attachment 632382 [details]
Created attachment 632383 [details]
Created attachment 632384 [details]
Created attachment 632385 [details]
Created attachment 632386 [details]
Created attachment 632387 [details]
Created attachment 632388 [details]
Created attachment 632389 [details]
Created attachment 632390 [details]
Created attachment 632391 [details]
Development and Creative Workstation
Obviously systemd was not installed with the Development and Creative Workstation environment.
I'm almost positive this is an anaconda problem.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
Still hitting this bug.
Any time you reopen a bug, you need to attach the traceback.
It wont let me do that through ABRT since it says it's a duplicate of this bug. Any tips on an easy way to do that?
dan: you have to do it manually unfortunately. the traceback will be in /tmp with the filename anaconda-tb-randomstring . just grab it and attach it (either usb stick or fpaste it out).
no ppc specific problem, I'll put it on the F18Blocker list
karsten: do you have a traceback for us?
I tested with F18 Beta DVD i386, selected components according to comment 14. No problem at all, everything worked fine.
Discussed at 2012-11-29 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-11-29/f18final-blocker-review-1.1.2012-11-29-17.01.log.txt . We agreed we need re-testing to clarify whether this is really a current issue before deciding on blocker status.
From c#30, it sounds like this might be fixed. Dan, if you're still hitting this, could you attach the tracebacks that Chris asked for?
(In reply to comment #27)
> dan: you have to do it manually unfortunately. the traceback will be in /tmp
> with the filename anaconda-tb-randomstring . just grab it and attach it
> (either usb stick or fpaste it out).
Here is the file you request (which was too large for fpaste) and hit on my current compose of the DVD.(In reply to comment #32)
> From c#30, it sounds like this might be fixed. Dan, if you're still hitting
> this, could you attach the tracebacks that Chris asked for?
Using Anaconda 18.37.4
Created attachment 668355 [details]
Dan: your install had massive dependency problems and almost the entire package set was nerfed by skipbroken. Only 36 packages got installed. Just search the log for SKIPBROKEN and see the carnage. Since you're using a DVD you built yourself, that looks like your problem, unless you can reproduce it with an official build. And almost certainly not the same problem as the original reporter hit.
Discussed at 2013-01-02 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2013-01-02/f18final-blocker-review-8.2013-01-02-17.03.log.txt . Rejected as a blocker per comment #35 - this looks like it was specific to Dan's own build / comps setup. As Dan re-opened this 'fixed' bug for his case, I am going to re-close the bug. Dan, if you think there's a valid bug lurking here, please pin it down more specifically - or if it's in your MATE comps stuff, just fix it yourself - and file it separately. Thanks. It is clearly not really this bug.