CentOS 6 does not show any desktop icons or anything in the panel
up vote
0
down vote
favorite
I was using CentOS 6 in VirtualBox fine for a couple of days. Now, when I login via the GUI user prompt, all I get is the background screen, no icons, no menubar, nothing. I am not terribly familiar with UNIX, but have used it in the past. That being said, if you need me to locate error messages to help diagnose this, please be specific as to where to locate files or specific commands that you would like me to execute, if possible. I have gotten to the GRUB prompt, but don't know what to do from there.
I am reposting this question as the one for CentOS 5 had no visible answers.
linux virtualbox centos
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
add a comment |
up vote
0
down vote
favorite
I was using CentOS 6 in VirtualBox fine for a couple of days. Now, when I login via the GUI user prompt, all I get is the background screen, no icons, no menubar, nothing. I am not terribly familiar with UNIX, but have used it in the past. That being said, if you need me to locate error messages to help diagnose this, please be specific as to where to locate files or specific commands that you would like me to execute, if possible. I have gotten to the GRUB prompt, but don't know what to do from there.
I am reposting this question as the one for CentOS 5 had no visible answers.
linux virtualbox centos
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
1
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was using CentOS 6 in VirtualBox fine for a couple of days. Now, when I login via the GUI user prompt, all I get is the background screen, no icons, no menubar, nothing. I am not terribly familiar with UNIX, but have used it in the past. That being said, if you need me to locate error messages to help diagnose this, please be specific as to where to locate files or specific commands that you would like me to execute, if possible. I have gotten to the GRUB prompt, but don't know what to do from there.
I am reposting this question as the one for CentOS 5 had no visible answers.
linux virtualbox centos
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
I was using CentOS 6 in VirtualBox fine for a couple of days. Now, when I login via the GUI user prompt, all I get is the background screen, no icons, no menubar, nothing. I am not terribly familiar with UNIX, but have used it in the past. That being said, if you need me to locate error messages to help diagnose this, please be specific as to where to locate files or specific commands that you would like me to execute, if possible. I have gotten to the GRUB prompt, but don't know what to do from there.
I am reposting this question as the one for CentOS 5 had no visible answers.
linux virtualbox centos
linux virtualbox centos
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
asked May 8 '13 at 14:19
JustWantToWorkAgain
111
111
1
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47
add a comment |
1
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47
1
1
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
At the screen with nothing on it, hit Alt+F1 (Or possibly Ctrl+Alt+F1), which should take you to a login console. Login with your credentials, then run 'sudo dmesg > dmesg.out'. Look through dmesg.out for errors related to gnome and post any you find here...
edited Apr 23 '17 at 7:31
phuclv
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
At the screen with nothing on it, hit Alt+F1 (Or possibly Ctrl+Alt+F1), which should take you to a login console. Login with your credentials, then run 'sudo dmesg > dmesg.out'. Look through dmesg.out for errors related to gnome and post any you find here...
edited Apr 23 '17 at 7:31
phuclv
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
add a comment |
up vote
0
down vote
At the screen with nothing on it, hit Alt+F1 (Or possibly Ctrl+Alt+F1), which should take you to a login console. Login with your credentials, then run 'sudo dmesg > dmesg.out'. Look through dmesg.out for errors related to gnome and post any you find here...
edited Apr 23 '17 at 7:31
phuclv
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
add a comment |
up vote
0
down vote
up vote
0
down vote
At the screen with nothing on it, hit Alt+F1 (Or possibly Ctrl+Alt+F1), which should take you to a login console. Login with your credentials, then run 'sudo dmesg > dmesg.out'. Look through dmesg.out for errors related to gnome and post any you find here...
edited Apr 23 '17 at 7:31
phuclv
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
At the screen with nothing on it, hit Alt+F1 (Or possibly Ctrl+Alt+F1), which should take you to a login console. Login with your credentials, then run 'sudo dmesg > dmesg.out'. Look through dmesg.out for errors related to gnome and post any you find here...
edited Apr 23 '17 at 7:31
phuclv
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
edited Apr 23 '17 at 7:31
phuclv
8,79563688
edited Apr 23 '17 at 7:31
phuclv
8,79563688
edited Apr 23 '17 at 7:31
phuclv
8,79563688
8,79563688
answered May 8 '13 at 14:41
tdk2fe
1092
answered May 8 '13 at 14:41
tdk2fe
1092
answered May 8 '13 at 14:41
tdk2fe
1092
1092
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
add a comment |
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
Thanks for the response. I have edited my question with the solution I found, since I am disallowed from answering my own question for 8 hours.
– JustWantToWorkAgain
May 8 '13 at 14:48
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f593093%2fcentos-6-does-not-show-any-desktop-icons-or-anything-in-the-panel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I realized that I could login as root from the GUI prompt. When I did, everything worked as expected. This let me know that there was a problem with the user account. So, as root, I disabled the scripts in the user .cshrc. Once the scripts were disabled, I logged into the user account. Everything came up as expected. Now, I just need to debug the scripts that were being run via the .cshrc.
– JustWantToWorkAgain
May 8 '13 at 14:47