"Oh no! Something has gone wrong. A problem has ocurred and the system can't recover.

[Andreu]

Hi

I have a problem when upgrading to Fedora 16, I've tried several times and always get the same result.
F15 to F16 upgrade with preupgrade, all right, I updated the whole system and when it finishes and reboots the system does not arrive to load gnome, I started well but when I get to gnome for me and I get a screen that says to me: "Oh no! Something have gone wrong.A problem ocurred and the system can't recover. Please contact the system administrator. "
I searched on Google and find no solution.
No longer do I have updated several times and always the same, I return to restore the image backup of F15, I look for info, update and same thing, so I take three days.
Can you help?
You know why can this happen?

thank you very much

Andreu

[WarrenJ]

Hi Andreu,

I had this exact problem too. Looking around the forums, a lot of people are suggesting that it's an SELinux conflict with the nVidia drivers, or some such. This was not the case for me. After many fruitless hours, I solved it myself. I booted into multi-user mode (run level 3) successfully. Then I ran "startx" as root, and redirected the errors to a log file. This revealed that the Gnome Desktop Manager was crashing because of an unmet dependency on something called "Caribou", which i understand might be a touch-screen driver. Although I already had Caribou installed, it turns out that I had the 32 bit version; I run a 64-bit Fedora system so actually I needed the 64-bit version to match. My first attempt at installation failed because the 32- and 64-bit versions cannot coexist. So I used yum to first uninstall the 32-bit version of Caribou and then install the correct 64-bit version. Et voila! I now have a fully working Fedora 16 desktop, and have not had to revert to Fedora 15. Nothing to do with SELinux or using the nouveau vs nvidia drivers; it was entirely down to this one issue. It's a bug in the preupgrade process, I guess.

Hope this helps.

Warren

[Andreu]

Hi Warren:

Thank you very much, this was my problem.
Now I have upgraded to F16 perfect!
Thank you very much, problem solved.

Best regards

Andreu

[griff]

Warren,
THANK YOU, I owe you a beer, you saved me a lot of time.
For those of you with the same problem an alternate version of what Warren did:

I actually had already fired up another consol (CRTL-ALT-F2) logged in as root
Get rid of the offending version:
# rpm -e caribou-0.4.1-1.fc16.i686
Network manager had not started up the network, so:
# ifup eth0
Then install the correct version of caribou
# yum install caribou


Thanks again,
-roger

[sysadmn]

Thanks! This was my problem exactly.

[ajgunn]

You guys are lifesavers. Thanks a ton for posting this info.

[JuhaniJaakola]

I have the same symptoms, but I have a 32-bit system and I have caribou installed.

Where did you find the GDM error message - startx gives a lot of output? Did startx fail or did it start successfully for you?

I tried the following:
- execute "init 3" as root to kill the failing GDM
- execute "startx" as a normal user. This started Gnome for me. There are a lot of warnings and failures in the startx output, which of them are related to the GDM problem?

By the way, my system worked well before I updated today to latest packages (including kernel 3.1.1-1 and kmod-nvidia-290.06-1 and other packages).

[AdamW]

I wish I could figure out why the upgrade is installing the wrong arch of caribou. Sigh.

[WarrenJ]

Hi Andreu, Roger,

No worries, you're welcome. I didn't want others to have to waste the hours that it took me to figure it out, if I could help it.

re JuhaniJaakola's post,

My startx log contains only 123 lines: I just redirected the errors using "startx 2> startx.log", so there may have been other stuff on stdout, but it's only the errors that are relevant here. I had booted into runlevel 3 by editing the grub command at boot time. Anyway, in startx.log I got a lot of stuff like this:

JS ERROR: !!! Exception was: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found
JS ERROR: !!! lineNumber = '0'
JS ERROR: !!! fileName = '"gjs_throw"'
JS ERROR: !!! stack = '"("Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found")@gjs_throw:0

This was repeated several times, followed by this:

Window manager warning: Log level 32: Execution of main.js threw exception: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found

So it wasn't exactly hard to diagnose by this point. However, if you're running a 32-bit system anyway, you likely have an unrelated problem. Unfortunately the unhelpful catch-all error message has made the symptoms indistinguishable. Still, your own X log is a good place to start - good luck!

Cheers,

Warren

[jff]

I still have this issue too. "Oh! No! Something has gone wrong." is raised due to gnome-shell-extensions. If they are disabled, then no issues, but assume gnome-shell-extensions should still work in F16.

[justFlow]

Many many thanks Warren!!!! Same Problem here and solved now. I´m happy

[jff]

Found that only gnome-shell-extension-alternative-status-menu cause "Oh! No! Something has gone wrong." message for me, so it's broken.

[rojo2000r]

i do yum install caribou and it says: Error: no such table: packages

why it can't install caribou?

[davidd]

I still have this issue too. "Oh! No! Something has gone wrong." is raised due to gnome-shell-extensions. If they are disabled, then no issues, but assume gnome-shell-extensions should still work in F16.

Yep, me too. I have a clean install of KDE, added Gnome (groupinstall "Gnome Desktop Environment." Added the tweak tool and some extensions. I've checked, and the 64-bit Caribou is installed. The only extension I can have running is the clock extension. The alternate-menu extension gets a crash on login. I turn off the menu extension from the crash screen, logout, and can login successfully.

[jff]

There's bug logged for this alternative-status-menu issue.
Workaround available