Description of problem: I was using Fedup to upgrade my F18 Laptop to F19 beta, the whole process went smoonthly, but after rebooting, and input my username and password, there is an error saying: Oh no! something has gone wrong. A problem has occured and the system can't recover. All extensions have been disabled as a precaution. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. fedup --network 19 2. after rebooting, input username and password 3. error occured Actual results: Error occurs Expected results: I should be able to login successfully. Additional info:
I think the problem is gnome-shell failed to start, I could not find gnome-shell process. After running gnome-shell in teminal manually, the error still occured. I can see another error: Bluetooth:ERROR:rfkill-glib.c:83:type_to_string: code should not be reached Aborted
I have his this issue as well, with the same flow and error message. Fedup.log fails during cleanup with this traceback: [ 0.188] (II) fedup:<module>() Exception: Traceback (most recent call last): File "/usr/bin/fedup-cli", line 181, in <module> main(args) File "/usr/bin/fedup-cli", line 82, in main do_cleanup(args) File "/usr/lib/python2.7/site-packages/fedup/commandline.py", line 183, in do_cleanup remove_cache() File "/usr/lib/python2.7/site-packages/fedup/sysprep.py", line 195, in remove_cache rm_rf(d) File "/usr/lib/python2.7/site-packages/fedup/util.py", line 51, in rm_rf rm_f(d, rm=rmtree) File "/usr/lib/python2.7/site-packages/fedup/util.py", line 48, in rm_f log.warn("failed to remove %s: %s", f, str(e)) NameError: global name 'log' is not defined [ 0.188] (II) fedup:<module>() /usr/bin/fedup-cli exiting at Wed Jun 5 12:38:49 2013 But I don't know if that's relevant. I suspect what Wei is reporting, that it's a gnome-shell issue, as I can login to a terminal fine.
Created attachment 757674 [details] fedup.log from f19 beta upgrade
This appears to be a gnome-bluetooth bug that has been fixed in git: https://git.gnome.org/browse/gnome-bluetooth/commit/lib/rfkill-glib.c?id=9932a6316be777d47b89323c9b8ae132c3676830
(In reply to Brian Hamrick from comment #2) > Fedup.log fails during cleanup with this traceback: > [...] > NameError: global name 'log' is not defined > [ 0.188] (II) fedup:<module>() /usr/bin/fedup-cli exiting at Wed Jun 5 > 12:38:49 2013 > > But I don't know if that's relevant. That's bug 958586, and yes, it's unrelated.
(In reply to Ray Strode [halfline] from comment #4) > This appears to be a gnome-bluetooth bug that has been fixed in git: > > https://git.gnome.org/browse/gnome-bluetooth/commit/lib/rfkill-glib. > c?id=9932a6316be777d47b89323c9b8ae132c3676830 I have disabled the bluetooth service, and login again, the same issue still happens
(In reply to Ray Strode [halfline] from comment #4) > This appears to be a gnome-bluetooth bug that has been fixed in git: > > https://git.gnome.org/browse/gnome-bluetooth/commit/lib/rfkill-glib. > c?id=9932a6316be777d47b89323c9b8ae132c3676830 Yes, you are right, this issue disappear after I updated gnome-bluetooth to 3.8.1-1