Login Screen Does Not Load [SOLVED]
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
neopaul
Login Screen Does Not Load [SOLVED]
After Installing Some Required Pieces Of Software, I Think The Last One I Installed Was Cairo-1.10.0 and then the terminal wouldn't load so i rebooted. once the computer rebooted everything seemed to be alright up until where the login screen normally appears, it makes the sound like its done loading, but i can only access my computer if i use the life cd, i can also access my harddrive while on the live cd, but i cant get to my desktop, i was trying to install the requirements for GTK+ and when i felt like i was almost done...terminal stopped loading on me...
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
neopaul
Re: Login Screen Does Not Load
Never Mind, Im Just Going To Do A Reinstall >.> I Didn't Want To Do This But I Don't Have All Day Either, I Need It Up And Running Before The End Of The Day...So Ima Just Do A Reinstall
-
SimonTS
Re: Login Screen Does Not Load
Missed this post first time round. Unfortunately, none of on here are paid for helping - we all have other things to do as well and I was out.
When the system appears to have finished loading, can you press <CTRL>+<ALT>+<F1> to see if you get a terminal login? Also, when you get the GRUB boot menu, select to edit to boot command and modify the 'quiet splash' to 'noquiet nosplash'. That should allow you to see the messages as it boots up.
When the system appears to have finished loading, can you press <CTRL>+<ALT>+<F1> to see if you get a terminal login? Also, when you get the GRUB boot menu, select to edit to boot command and modify the 'quiet splash' to 'noquiet nosplash'. That should allow you to see the messages as it boots up.
-
neopaul
Re: Login Screen Does Not Load
alright ill give that a try, didnt think i'd get a reply... =p i cant do a fresh install, even though i can access my hd via when i load the os it wont let me copy my important files off the laptop >.< i.e. non-replaceable pictures, data i have been working on for years...i orginally had it on my flash drive but...i needed something to transfer some movies to my laptop and b4 i had the chance to put them back onto my flash drive i couldnt get the laptop to even login...but ill give that a shot
-
neopaul
Re: Login Screen Does Not Load
<CRL><ALT>F1 Doesnt Do Anything But I Wrote Some Stuff Down But It Was Going Too Fast To Get All Of It
I Accidently Did <CRL><ALT>ESC And It Changed And Showed A Warning Message, Kept Doing It Adventually It Will Do A Bunch Of Loading Errors
That First Message Was Something Like..
Warning 125: GLIB "Something" GETPWID_R "Something"
Not Sure The Message Doesn't Stay Long, I'd Take Like 20-50 Reboots To Get All Of It...And I Don't Think Thats Neccarry Cause Of This Lil Bit Of Info Should Be Enough...
The Second Bunches Of Lines Is Nearly Impossible To Catch Anything...
Goes Way Too Fast Then Loads The Background, Then Makes The Normal Beep Sound, But Sometimes I Can't Move The Mouse...
But Somewhere In All Those Error Messages...it Says vDev or something similiar
EDIT: Tried Doing A Search For GLIB GETPWID_R And I Found Something That Looks Almost The Same..
(process 239): GLIb-WARNING **: getpwid_r(): failed due to unknown user id (0)
https://bugs.launchpad.net/ubuntu/+sour ... bug/532984
But Doesn't Fix My Problem Just Gives You More INFO On What Might Be The Problem
I Accidently Did <CRL><ALT>ESC And It Changed And Showed A Warning Message, Kept Doing It Adventually It Will Do A Bunch Of Loading Errors
That First Message Was Something Like..
Warning 125: GLIB "Something" GETPWID_R "Something"
Not Sure The Message Doesn't Stay Long, I'd Take Like 20-50 Reboots To Get All Of It...And I Don't Think Thats Neccarry Cause Of This Lil Bit Of Info Should Be Enough...
The Second Bunches Of Lines Is Nearly Impossible To Catch Anything...
Goes Way Too Fast Then Loads The Background, Then Makes The Normal Beep Sound, But Sometimes I Can't Move The Mouse...
But Somewhere In All Those Error Messages...it Says vDev or something similiar
EDIT: Tried Doing A Search For GLIB GETPWID_R And I Found Something That Looks Almost The Same..
(process 239): GLIb-WARNING **: getpwid_r(): failed due to unknown user id (0)
https://bugs.launchpad.net/ubuntu/+sour ... bug/532984
But Doesn't Fix My Problem Just Gives You More INFO On What Might Be The Problem
-
SimonTS
Re: Login Screen Does Not Load
The 'GLIB-WARNING' message that you found on your search is something different and it's not important - everybody gets that due to an error in the boot-up.
Did you manage to edit the boot parameters like I suggested? The other thing to try is, once the system freezes on the graphical boot screen, try pressing the right arrow button and see if it brings up messages - may show you the last set of things it was doing. If there's too much to write down then take a photo with a digital cam and post it here.
Did you manage to edit the boot parameters like I suggested? The other thing to try is, once the system freezes on the graphical boot screen, try pressing the right arrow button and see if it brings up messages - may show you the last set of things it was doing. If there's too much to write down then take a photo with a digital cam and post it here.
-
neopaul
Re: Login Screen Does Not Load
i cant get into the terminal without booting from the live cd, i did try to change the boot parameters that way (live cd, when it first starts i pressed tab then changed them that way..) but i dont know how to boot into recovery mode to make changes like that, i tried pressing f6 on boot
-
neopaul
Re: Login Screen Does Not Load
i tried to press the right arrow key where it stoped loading and nothing happened
-
neopaul
Re: Login Screen Does Not Load
if i reinstall i lose all my data thats not replaceable...any way i can access my files, to by-pass the lock preventing me from taking certain files?
you see on the live cd i've figured out how to login as root,
# sudo passwd root
then
# su
ive tried to...
# mv /media/c3*/home/neo/Desktop/untitled* /media/AB*
And Even As Root It Pops Up Permission Denied...
you see on the live cd i've figured out how to login as root,
# sudo passwd root
then
# su
ive tried to...
# mv /media/c3*/home/neo/Desktop/untitled* /media/AB*
And Even As Root It Pops Up Permission Denied...
Last edited by neopaul on Thu Apr 07, 2011 3:15 pm, edited 1 time in total.
-
SimonTS
Re: Login Screen Does Not Load
If you can boot off the LiveCD then you should be able to copy any data you need off the hard-drive. If there's any that don't want to copy, then try launching Nautilus from the command line as a root user;-
$ gksudo nautilus
$ gksudo nautilus
-
neopaul
Re: Login Screen Does Not Load
# gksudo nautilus
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(gksudo:4753): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:4754): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf warning: failure listing pairs in `/apps/nautilus/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:4754): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
(nautilus:4754): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:4754): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
I Assume This Means I Cannot Do It..
I'm Running On Linux Mint 9, 64 Bit Os
EDIT: I Don't Want To Lose All My Important Data, So Reinstall Will Not Be Possible Until I'm Able To Back Up My Data From My HD, But If I Can Fix This Problem Without Reinstalling, That Is More Preferred But The Faster I Get This Fixed The Better, So If I Can Only Do A Reinstall I'm Sure Theres A Method Of Recovering The Data From The HD, Just How To Do It Is A Real Problem, If I Come Up With A Solution I'll Post The Results
EDIT: I'm Fairly New To Linux, I Have Been Using It For About 6 Months Now, Google Is My Best Friend = ) I Can Install From Source Without Much Problems Now, But While On Live CD, That Much Isn't That Useful Because You Can't Update Or Install Software Onto The HD Or Disc, Unless Theres A Way To Uninstall What I Did And Backtrack Until The Problem Is Fixed, But The Commands For Uninstall I'm Not Familiar With, Nor Do I Know The Commands To Install/Uninstall From The HD As A Mounted Filesystem Rather Than A Primary Filesystem...
For Me To Access My HD I Have To Go To /media/c3* (c3595d12-5faa-4072-9de7-75b0d0a65683) It Also Apears As A Mounted HD
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(gksudo:4753): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:4754): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf warning: failure listing pairs in `/apps/nautilus/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:4754): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:4754): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
(nautilus:4754): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:4754): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
I Assume This Means I Cannot Do It..
I'm Running On Linux Mint 9, 64 Bit Os
EDIT: I Don't Want To Lose All My Important Data, So Reinstall Will Not Be Possible Until I'm Able To Back Up My Data From My HD, But If I Can Fix This Problem Without Reinstalling, That Is More Preferred But The Faster I Get This Fixed The Better, So If I Can Only Do A Reinstall I'm Sure Theres A Method Of Recovering The Data From The HD, Just How To Do It Is A Real Problem, If I Come Up With A Solution I'll Post The Results
EDIT: I'm Fairly New To Linux, I Have Been Using It For About 6 Months Now, Google Is My Best Friend = ) I Can Install From Source Without Much Problems Now, But While On Live CD, That Much Isn't That Useful Because You Can't Update Or Install Software Onto The HD Or Disc, Unless Theres A Way To Uninstall What I Did And Backtrack Until The Problem Is Fixed, But The Commands For Uninstall I'm Not Familiar With, Nor Do I Know The Commands To Install/Uninstall From The HD As A Mounted Filesystem Rather Than A Primary Filesystem...
For Me To Access My HD I Have To Go To /media/c3* (c3595d12-5faa-4072-9de7-75b0d0a65683) It Also Apears As A Mounted HD
-
neopaul
Re: Login Screen Does Not Load
ok i tried something, hopefully it works, but ill edit this post to prevent mass msgs, alright the site i used is.. http://community.linuxmint.com/tutorial/view/245
EDIT: No Success With That >.<
I'm Going To Try Something Else, Previously I Tried To Move The Files, With
# mv
command But This Time I'll Look For A Copy Command, Maybe Ill Have More Success That Way..
EDIT: Alright I Have An Update, I Managed To Successfully Get My Files Backed Up, I'm Not 100% On What I Did But A Few Commands I Did Check Was..
# chmod 777
# chmod 000
(Which Did Really Nothing lol)
# sudo passwd root
(Lets You Reset The Root Password / Sets A Root Password)
For Those On Live CD With The Same Problem This Helps = )
# cp
(Copy) Didn't Really Do Much For Me >.<
I Went To The Folder That Had The X In The Top-Right Corner Of Each File/Folder And Right Clicked, "Open As Admin" Then Went Up A Folder, And Went To It's Properties.. And Set Them "Read And Write" To All People = ) Then I Just Copied Them Over, Seemed To Work Pretty Good = )
Now Since It's All Backed Up, I'm Going To Do A Reinstall,
Thanks For Your Help = )
EDIT: No Success With That >.<
I'm Going To Try Something Else, Previously I Tried To Move The Files, With
# mv
command But This Time I'll Look For A Copy Command, Maybe Ill Have More Success That Way..
EDIT: Alright I Have An Update, I Managed To Successfully Get My Files Backed Up, I'm Not 100% On What I Did But A Few Commands I Did Check Was..
# chmod 777
# chmod 000
(Which Did Really Nothing lol)
# sudo passwd root
(Lets You Reset The Root Password / Sets A Root Password)
For Those On Live CD With The Same Problem This Helps = )
# cp
(Copy) Didn't Really Do Much For Me >.<
I Went To The Folder That Had The X In The Top-Right Corner Of Each File/Folder And Right Clicked, "Open As Admin" Then Went Up A Folder, And Went To It's Properties.. And Set Them "Read And Write" To All People = ) Then I Just Copied Them Over, Seemed To Work Pretty Good = )
Now Since It's All Backed Up, I'm Going To Do A Reinstall,
Thanks For Your Help = )