Hide Forgot
Created attachment 533952 [details] /var/log/gdm/:0-greeter.log Description of problem: After upgrading to Fedora 16, I get the "Oh no! Something has gone wrong" with "A problem haas occured and the system can't recover. Please contact a system administrator". This message is displayed by the new gdm from GNOME 3.2. I also had another problem with the upgrade. The upgrade was performed from Fedora 15 using Preupgrade on a MacBook 3,2. It has x86_64 hardware with a x32 EFI implementation. I used instructions at <http://fedora64.org/Members/jmontleon/installing-fedora-16-on-macbooks-using-grub2-efi> to boot the new Fedora. Reading the logs (see attached file), gdm can't find Caribou typelib. But I can find it in the filesystem just file. The file /usr/lib/girepository-1.0/Caribou-1.0.typelib exists just fine. I performed an upgrade on the commandline, and restarted gdm using "systemctl restart prefdm.service" and I get no improvements. Version-Release number of selected component (if applicable): caribou-0.4.1-1.fc16.i686 gdm-3.2.1.1-8.fc16.x86_64 How reproducible: always Steps to Reproduce: boot on a broken system Actual results: Oh no screen Expected results: login screen Additional info: This prevents graphical log in on the system
For some reason, the package "caribou" was install for i686, but I am using a x86_64 system. I just erased caribou.i686 (strangely, it didn't prompt me to remove any other dependency). I just installed right after caribou.x86_64. This problem also affected gnome-shell. And the same solution applied. I don't understand how this dependency could slip though.
Just a "me too". The upgrade process is clearly broken - after upgrade F15->F16 I was getting the "oh no" screen. "rpm -e caribou.i686; yum -y install caribou" fixed this (thanks, Mildred!). In addition to that, after upgrading two of my computers to F16 they both ended up with empty /boot/grub/grub2.cfg, and I had to figure out what kernel parameters should I add (especially interesting with encrypted volumes). I have to look it up in bugzilla and probably file a new report.
Digging into this further, I think the problem is not (only) in the caribou.i686 package. I have just upgrade a virtual machine from F15 to F16 (the display manager is OK, as well as logging into the GNOME session. I have removed the installed caribou.x86_64 package, and then installed caribou-0.4.1-1.fc16.i686. Gdm still works, even after reboot. So the problem has to be more complicated (other "Oh no" reports - such as this one: http://blog.kosmokaryote.org/2011/11/fedora-16-oh-no-failure-at-log-in.html mention SELinux). [off-topic: the grub problem mentioned in comment #2 is now reported as bug #755232)
Note: I was using SELinux in permissive mode.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.