On Sat, 2013-06-15 at 22:37 +0300, moshe nahmias wrote: > I can re-try but would prefer to know what I need to do before hand, > so I won't need to do it again afterwards or at least lower the > chances of doing so again. > > > what should I do when the bug hit again? I don't care to try multiple > times as long as it's done one after the other to find something and > not for every question here. > > > I do need this computer but can do it for now, hopefully the debugging > will be short enough so we will be able to find the culprit before I > will have to stop. All we really need to do is get the backtrace out. You could try the reporting tool again, or when it crashes, you can hit ctrl-alt-f2 which should get you a console, and you should find an anaconda-tb-(something) file in /tmp - you can fpaste it out if you have a network connection, or plug in a USB stick, mount it and copy to that. Oh, and also get /tmp/program.log. Thanks! > BTW, if it's possible to do dual boot, one install with bios and the > other with EFI That's very unlikely to work on a single disk. It might work in theory with two+ disks if you only have one type of install per disk, but it's entirely possible that some firmwares would be buggy with this setup. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
