LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices

Reply
 
Search this Thread
Old 11-12-2012, 11:18 AM   #16
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176

I am not familiar with GNOME but netsearching suggests that the per-user session autostart directory is ~/.config/autostart. You could try renaming it so GNOME does not find it.

At this point in the investigation we are guessing which files under the home directory are causing the problem. If we are lucky we will find them quickly but it may take a long time.
 
1 members found this post helpful.
Old 11-12-2012, 02:38 PM   #17
\/4A
Member
 
Registered: Aug 2012
Posts: 112

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by catkin View Post
I am not familiar with GNOME but netsearching suggests that the per-user session autostart directory is ~/.config/autostart. You could try renaming it so GNOME does not find it.
Thanks Catkin,

I renamed the directory called autostart which is under the ~/.config/ in V4A, then rebooted my PC but no luck. V4A still refuses to successfully load the desktop.

I was then just looking through the files in the ~/home/v4a/ folder to see which new files have come today during the last (unsuccessful) login and came across a file called .xsession-errors
Just in case it may have some info, here's the contents:
Code:
Running X session wrapper
Loading profile from /etc/profile
Loading profile from /home/v4a/.profile
Loading resource: /etc/X11/Xresources/x11-common
Loading X session script /etc/X11/Xsession.d/20x11-common_process-args
Loading X session script /etc/X11/Xsession.d/30x11-common_xresources
Loading X session script /etc/X11/Xsession.d/40x11-common_xsessionrc
Loading X session script /etc/X11/Xsession.d/50_check_unity_support
Loading X session script /etc/X11/Xsession.d/50x11-common_determine-startup
Loading X session script /etc/X11/Xsession.d/52libcanberra-gtk3-module_add-to-gtk-modules
Loading X session script /etc/X11/Xsession.d/52libcanberra-gtk-module_add-to-gtk-modules
Loading X session script /etc/X11/Xsession.d/55gnome-session_gnomerc
Loading X session script /etc/X11/Xsession.d/60x11-common_localhost
Loading X session script /etc/X11/Xsession.d/60x11-common_xdg_path
Loading X session script /etc/X11/Xsession.d/60xdg-user-dirs-update
Loading X session script /etc/X11/Xsession.d/65compiz_profile-on-session
Loading X session script /etc/X11/Xsession.d/70gconfd_path-on-session
Loading X session script /etc/X11/Xsession.d/75dbus_dbus-launch
Loading X session script /etc/X11/Xsession.d/80im-switch
Setting IM through im-switch for locale=en_CA.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
Loading X session script /etc/X11/Xsession.d/90consolekit
Loading X session script /etc/X11/Xsession.d/90x11-common_ssh-agent
Loading X session script /etc/X11/Xsession.d/98vboxadd-xclient
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Failed to connect to the VirtualBox kernel service
Loading X session script /etc/X11/Xsession.d/99x11-common_start
GNOME_KEYRING_CONTROL=/tmp/keyring-mXYTBd
GNOME_KEYRING_CONTROL=/tmp/keyring-mXYTBd
GPG_AGENT_INFO=/tmp/keyring-mXYTBd/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-mXYTBd/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-mXYTBd
GPG_AGENT_INFO=/tmp/keyring-mXYTBd/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-mXYTBd/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-mXYTBd
GPG_AGENT_INFO=/tmp/keyring-mXYTBd/gpg:0:1
gnome-session[1756]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Failed to play sound: File or data not found
** Message: Initializing gksu extension...
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area
Segmentation fault

(nm-applet:1871): libnotify-WARNING **: Failed to connect to proxy
(nm-applet:1871): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
gnome-session[1756]: WARNING: Application 'gnome-shell.desktop' killed by signal
gnome-session[1756]: WARNING: Application 'gnome-shell.desktop' killed by signal
gnome-session[1756]: WARNING: App 'gnome-shell.desktop' respawning too quickly
gnome-session[1756]: CRITICAL: We failed, but the fail whale is dead. Sorry....

** (gnome-screensaver:1937): WARNING **: Screensaver already running in this session
** (deja-dup-monitor:1989): DEBUG: monitor.vala:221: Automatic backups disabled.  Not scheduling a backup.
gnome-session[1756]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(gdu-notification-daemon:1945): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.


(gnome-settings-daemon:1881): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
** (process:1948): DEBUG: zeitgeist-datahub.vala:58: Zeitgeist-daemon disappeared from the bus, exitting...

** (process:1948): WARNING **: zeitgeist-datahub.vala:218: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
 
Old 11-12-2012, 05:32 PM   #18
JaseP
Senior Member
 
Registered: Jun 2002
Location: Eastern PA, USA
Distribution: K/Ubuntu 10.04/12.04, Scientific Linux 6.3, Android-x86, Maemo
Posts: 1,658

Rep: Reputation: 138Reputation: 138
Is there a lockfile in the user directory?!?! They are hidden files (start with a . ).
 
Old 11-12-2012, 09:05 PM   #19
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
.xsession-errors normally has many error messages so it's hard to know if any of those are significant.

It is likely that the file system filled while V4A was logged on and, when V4A logged off, it was unable to write some files resulting in a mess which is preventing desktop logon.

It might be worth creating an /etc/forcefsck file and rebooting. That will check the file system. If /etc/forcefsck exists after booting, remove it.

We now know that the problem is caused by something under /home/V4A. One way to identify what would be to move half the files-and-directories somewhere else and test again. If desktop logon works you know the problem lies in the files-and-directories moved so you can move half of the moved files back and retest. If desktop logon does not work you know the problem lies with the unmoved files-and-directories so you can move half of them to the same somewhere else.
 
1 members found this post helpful.
Old 11-14-2012, 08:40 AM   #20
\/4A
Member
 
Registered: Aug 2012
Posts: 112

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by catkin View Post
It might be worth creating an /etc/forcefsck file and rebooting. That will check the file system. If /etc/forcefsck exists after booting, remove it.
Should I just make a new blank file (let'say in gedit) and call itforcefsck and place it in /etc/

Quote:
Originally Posted by catkin View Post
We now know that the problem is caused by something under /home/V4A. One way to identify what would be to move half the files-and-directories somewhere else and test again. If desktop logon works you know the problem lies in the files-and-directories moved so you can move half of the moved files back and retest. If desktop logon does not work you know the problem lies with the unmoved files-and-directories so you can move half of them to the same somewhere else.
Would you be referring to any particular files/directories here? Would you also be referring to hidden ones?
 
Old 11-14-2012, 09:27 AM   #21
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by \/4A View Post
Should I just make a new blank file (let'say in gedit) and call itforcefsck and place it in /etc/

Would you be referring to any particular files/directories here? Would you also be referring to hidden ones?
That would work but the easiest way would be touch /etc/forfsck

No particular files/directories. After trying with autostart and that not working there are no particular files that come to mind. Yes, the hidden ones too.
 
1 members found this post helpful.
Old 11-14-2012, 10:38 AM   #22
\/4A
Member
 
Registered: Aug 2012
Posts: 112

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by catkin View Post
No particular files/directories. After trying with autostart and that not working there are no particular files that come to mind. Yes, the hidden ones too.
autostart?
 
Old 11-14-2012, 10:54 AM   #23
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
~/.config/autostart
 
1 members found this post helpful.
Old 11-14-2012, 11:19 AM   #24
\/4A
Member
 
Registered: Aug 2012
Posts: 112

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by catkin View Post
~/.config/autostart
My aplogies, Catkin, I forgot the autostart you had earlier mentioned.
 
Old 11-16-2012, 03:47 AM   #25
\/4A
Member
 
Registered: Aug 2012
Posts: 112

Original Poster
Rep: Reputation: Disabled
Isn't there a way I could import all programs, settings, user files, etc..... into the new V4A user a/c we made? or, isn't there a way to 'repair' the desktop of V4A user (how about if I upgraded to Linux Mint 13)?
 
Old 11-16-2012, 09:14 AM   #26
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Servers: Debian Squeeze and Wheezy. Desktop: Slackware64 14.0. Netbook: Slackware 13.37
Posts: 8,541
Blog Entries: 28

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by \/4A View Post
Isn't there a way I could import all programs, settings, user files, etc..... into the new V4A user a/c we made? or, isn't there a way to 'repair' the desktop of V4A user (how about if I upgraded to Linux Mint 13)?
Yes -- but it would almost certainly result in the V4A user having the same problem. Hence the suggestion to move half the files/directories back; if the problem recurs move half out again and, if doesn't move half the remaining ones back out and so on until you identify the one(s) that trigger the problem.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"Display is not set" ; boots to login, then frozen grey/white screen w. globes wiliamvw Slackware 6 05-10-2010 05:30 PM
Lucid x64 boots to login screen, at times.... salmanal Ubuntu 3 05-03-2010 11:19 AM
system boots but no login screen grindelwald Linux - Desktop 3 03-03-2008 12:58 PM
SUSE 10 on thinkpad doesn't give login screen, it just boots right up LordFett Linux - Laptop and Netbook 4 01-16-2006 11:13 PM
System no longer boots to graphical login will103 Debian 3 01-08-2005 03:56 PM


All times are GMT -5. The time now is 07:26 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration