On Thu, May 10, 2012 at 10:33 AM, Amit Saha <amitksaha(a)fedoraproject.org> wrote:
On Thu, May 10, 2012 at 9:58 AM, Adam Williamson
<awilliam(a)redhat.com> wrote:
> On Thu, 2012-05-10 at 09:46 +0530, Amit Saha wrote:
>> On Tue, May 8, 2012 at 8:44 PM, Adam Williamson <awilliam(a)redhat.com>
wrote:
>> > On Tue, 2012-05-08 at 13:54 +0530, Amit Saha wrote:
>> >> On Tue, May 8, 2012 at 11:35 AM, Adam Williamson
<awilliam(a)redhat.com> wrote:
>> >> > On Tue, 2012-05-08 at 07:48 +0530, Amit Saha wrote:
>> >> >
>> >> >> Here is the screenshot of the screen [1]. I was hoping to work
around
>> >> >> it to do a fresh install by clicking on "Continue
Install", but from
>> >> >> what I remember now, the Installer crashed, and I attempted to
save
>> >> >> the logs, for which it attempted to connect to the Network, but
which
>> >> >> never succeeded. I shall attempt to try this again and retrieve
more
>> >> >> information.
>> >> >>
>> >> >>
>> >> >> [1]
https://twitter.com/#!/echorand/status/199682569703407616/photo/1/large
>> >> >
>> >> > Ah. 'product mismatch' there means you had a 32-bit system
installed and
>> >> > booted the 64-bit installer, or vice versa, I believe. The
installer
>> >> > crash may well not have been related, but if you couldn't save
logs,
>> >> > it's difficult to tell. :/ It would be interesting to know if
you can
>> >> > recreate the failure by doing the same thing again.
>> >>
>> >> Please find a screenshot of the exception/bug [1] when I click on the
>> >> "Continue" button after the previous error dialog box. Sorry,
but once
>> >> again I tried to save the log and the network configuration step
>> >> didn't quite work. (That's probably another investigation
required).
>> >> It seems like a Dbus exception.
>> >
>> > You should be able to get a copy of the traceback and logs from /tmp if
>> > you go to the ctrl-alt-f2 console when you hit the error. You can just
>> > copy them to a manually-mounted USB stick, or bring up the network
>> > manually and fpaste them out, I guess.
>>
>> Thanks. Here is the anaconda.log [1]. I have the other logs saved as
>> well. Please let me know if you would like to take a look at any other
>> file.
>>
>> [1]
https://gist.github.com/2650996
>>
>> Hope it helps you in tracking the problem.
>
> Can you file a bug against anaconda, and attach all the logs? Thanks!
Done [1].
was closed citing
that dbus may not have been installed correctly or is not running.
Any idea how I can find that out? I built a boot.iso again and the
installer crashes with the same exception.
Also, I see towards building the boot.iso:
<code>
..
rebuilding boot/initramfs-3.3.4-4.fc17.i686.img
E: Dracut module "anaconda" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "anaconda" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "nfs" cannot be found.
rebuilding boot/initramfs-3.3.4-4.fc17.i686.PAE.img
E: Dracut module "anaconda" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "anaconda" cannot be found.
E: Dracut module "nfs" cannot be found.
E: Dracut module "nfs" cannot be found.
..
</code>
Is this ignnorable or should I be checking something?
Thanks a lot.
-Amit
--