Oh no! Something has gone wrong. A problem has ocurred and the system can't recover.
来源:互联网 发布:大数据报表展示平台 编辑:程序博客网 时间:2024/04/30 08:56
"Oh no! Something has gone wrong. A problem has ocurred and the system can't recover.
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
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
#2
13th November 2011, 06:50 PM
Registered User
Join Date: Nov 2011
Location: Reading, United Kingdom
Posts: 2
Re: "Oh no! Something has gone wrong. A problem has ocurred and the system can't reco
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
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
Last edited by WarrenJ; 13th November 2011 at 07:42 PM.
#3
13th November 2011, 09:05 PM
Registered User
Join Date: Sep 2011
Posts: 7
Re: "Oh no! Something has gone wrong. A problem has ocurred and the system can't reco
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
Thank you very much, this was my problem.
Now I have upgraded to F16 perfect!
Thank you very much, problem solved.
Best regards
Andreu
#4
14th November 2011, 05:58 PM
Registered User
Join Date: Feb 2008
Location: 127.0.0.1
Posts: 9
Re: "Oh no! Something has gone wrong. A problem has ocurred and the system can't reco
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
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
这个上面说的是fedora升级到fedora 16就解决问题了,可是我装的是fedora 18也有这个问题。???
- Oh no! Something has gone wrong. A problem has ocurred and the system can't recover.
- VNC远程连接服务器出现 A problem has occurred and the system can't recover. 错误
- oh no, something has gone wrong: startx failed
- Oh no! Something has gone wrong.Logout!解决方法
- On no!Something has gone wrong!
- GNOME3启动时出错:Oh no! Something has gone wrong.Logout!
- 记一次装B失败:Oh no! Something has gone wrong.
- CentOS Ghome桌面 Something has gone wrong 的解决办法
- The connection to adb is down, and a severe error has ocurred
- Wrong orientation? No orientation specified, and the default is horizontal, yet this layout has mult
- Wrong orientation? No orientation specified, and the default is horizontal, yet this layout has mult
- Wrong orientation? No orientation specified, and the default is horizontal, yet this layout has mult
- The ancient sprite has gone
- Where has the caret gone?
- Can't sendRedirect() after data has committed to the client.
- WMS has encountered a problem and needs to close. We are sorry for the inconvenience.
- it has a DefiningQuery and no <InsertFunction> element exists in the <ModificationFunctionMapping>
- Android: couldn't save which view has focus because the focused view ### has no id
- android中如何解析没有Key的Json数据
- iOS开发之多媒体播放
- 人生励志博文系列收集
- 百炼 1833:排列
- 图片添加高清版本的办法
- Oh no! Something has gone wrong. A problem has ocurred and the system can't recover.
- 海盗分宝石[智力测试题]---印象非常深刻
- 2ccc.com的去45秒等待油猴脚本
- 重复数据删除技术
- 您正试图运行的函数包含有宏或需要宏语言支持的内容。而在安装此软件时,您(或您的管理员)选择了不安装
- iOS通过iTunes search检测版本更新,并提示用户更新!
- 友元函数和友元类
- 背景建模之单高斯实现
- 在论坛上面发外链还可以起到作用吗