Ubuntu

Login broken

Asked by John Cottier

Kubuntu Feisty has been running fine for a few weeks. But today after boot up, kdm login fails. After accepting my password, the display flickers and returns to the login screen. There are no error messages. The behaviour is the same with gdm as I also have ubuntu-desktop. If I go to console login and try startx this fails. The only thing that works is starting in recovery mode, and then startx works with a default gnome desktop, but all configurations (e-mail etc) are lost (Kontact cannot 'see' my existing mail folders etc). I have tried checking hard drive space and I have bucket loads. I have tried removing the nvidia driver and returning to the nv driver and tried dpkg reconfigure xserver-xorg but none makes any difference, except to the looks of the gdm screen. I cant use even use vmware as the license cant be found in this mode. This is my work PC and I am really stuck! Please help!! Regards John Cottier.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Cesare Tirabassi
Solved:
Last query:
Last reply:
Revision history for this message
Cesare Tirabassi (norsetto) said : 		#1

After attempting to enter your session, try to login in a safe-mode terminal.
If you succeed, have a look at ~/.xsession-errors and /var/log/user.log for any error message.
Have a look also to daemon.log:

if you use gnome:

cat /var/log/daemon | grep gdm

If you use kdm:

cat /var/log/daemon | grep kdm

Revision history for this message
John Cottier (j-cottier) said : 		#2

Hello Cesare, Thanks for your reply. .Xsession-errors seems to have a few permission refused errors. I cant see any problems in the user.log but I will attach both files. var/log/daemon folder does not exist.

I have tried reconfiguring kdm, removing and re-installing kubuntu desktop, and have now removed kdm. Behaviour is still the same, but gdm does at least give an error message "mkdtemp: private socket dir: permission denied".

I can startx if I goto to console, remove the x lock file and do sudo startx. But this still creates a root x session.

Revision history for this message
John Cottier (j-cottier) said : 		#3

Sorry, I cant find a way to attach a file. Here are the file dumps:-

.Xsession-errors:

/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "john"
/etc/gdm/Xsession: Beginning session setup...
mkdtemp: private socket dir: Permission denied
Xsession: X session started for root at Tue Jul 17 14:22:22 BST 2007
SESSION_MANAGER=local/john-ubuntu:/tmp/.ICE-unix/6347

** (update-notifier:6422): WARNING **: not starting because user is not in admin group

evolution-alarm-notify-Message: Setting timeout for 38252 1184716800 1184678548
evolution-alarm-notify-Message: Wed Jul 18 01:00:00 2007

evolution-alarm-notify-Message: Tue Jul 17 14:22:28 2007

(gnome-panel:6409): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
Initializing gnome-mount extension
You should really not run firefox through sudo WITHOUT the -H option.
Anyway, I'll do as if you did use the -H option.
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: The desktop entry file /usr/share/applications/DefaultPlugins.desktop has Type=Link instead of "Application" or "Service"
kio (KService*): WARNING: Invalid Service : /usr/share/applications/DefaultPlugins.desktop
kio (KSycoca): ERROR: No database available!
kdecore (KProcess): WARNING: _attachPty() 11
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
kbuildsycoca running...
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x3400007 (Session Ch).
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x3400007 (Session Ch).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x2801733 (file:///ho).
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x3400097 (Binary Fil).
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Launched ok, pid = 7296
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kdecore (KProcess): WARNING: _attachPty() 11
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x3000007 (Session Ch).

user.log:

erver is not in use, shutting down.
Jul 16 09:47:55 john-ubuntu gconfd (john-6919): Exiting
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): starting (version 2.18.0.1), pid 7635 user 'john'
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 09:49:49 john-ubuntu gconfd (john-7635): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 09:50:19 john-ubuntu gconfd (john-7635): GConf server is not in use, shutting down.
Jul 16 09:50:19 john-ubuntu gconfd (john-7635): Exiting
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): starting (version 2.18.0.1), pid 7863 user 'john'
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 09:53:13 john-ubuntu gconfd (john-7863): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 11:53:52 john-ubuntu cupsd: Unable to open log file "/var/log/cups/access_log" - Permission denied
Jul 16 11:53:52 john-ubuntu cupsd: Unable to open log file "/var/log/cups/access_log" - Permission denied
Jul 16 13:48:13 john-ubuntu gconfd (john-7863): GConf server is not in use, shutting down.
Jul 16 13:48:13 john-ubuntu gconfd (john-7863): Exiting
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): starting (version 2.18.0.1), pid 17064 user 'john'
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 13:49:13 john-ubuntu gconfd (john-17064): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 13:50:13 john-ubuntu gconfd (john-17064): GConf server is not in use, shutting down.
Jul 16 13:50:13 john-ubuntu gconfd (john-17064): Exiting
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): starting (version 2.18.0.1), pid 20766 user 'john'
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 15:27:01 john-ubuntu gconfd (john-20766): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 15:28:01 john-ubuntu gconfd (john-20766): GConf server is not in use, shutting down.
Jul 16 15:28:01 john-ubuntu gconfd (john-20766): Exiting
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): starting (version 2.18.0.1), pid 21331 user 'john'
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 15:41:04 john-ubuntu gconfd (john-21331): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 15:42:34 john-ubuntu gconfd (john-21331): GConf server is not in use, shutting down.
Jul 16 15:42:34 john-ubuntu gconfd (john-21331): Exiting
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): starting (version 2.18.0.1), pid 23072 user 'john'
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 16:27:38 john-ubuntu gconfd (john-23072): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 16:28:08 john-ubuntu gconfd (john-23072): GConf server is not in use, shutting down.
Jul 16 16:28:08 john-ubuntu gconfd (john-23072): Exiting
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): starting (version 2.18.0.1), pid 23352 user 'john'
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 16:34:07 john-ubuntu gconfd (john-23352): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 16:40:07 john-ubuntu gconfd (john-23352): GConf server is not in use, shutting down.
Jul 16 16:40:07 john-ubuntu gconfd (john-23352): Exiting
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): starting (version 2.18.0.1), pid 24075 user 'john'
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 16:46:16 john-ubuntu gconfd (john-24075): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 17:03:16 john-ubuntu gconfd (john-24075): GConf server is not in use, shutting down.
Jul 16 17:03:16 john-ubuntu gconfd (john-24075): Exiting
Jul 16 17:03:53 john-ubuntu cupsd: Unable to open log file "/var/log/cups/access_log" - Permission denied
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): starting (version 2.18.0.1), pid 25012 user 'john'
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): Resolved address "xml:readwrite:/home/john/.gconf" to a writable configuration source at position 1
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 16 17:09:03 john-ubuntu gconfd (john-25012): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 16 17:15:03 john-ubuntu gconfd (john-25012): GConf server is not in use, shutting down.
Jul 16 17:15:03 john-ubuntu gconfd (john-25012): Exiting
Jul 16 17:15:55 john-ubuntu cupsd: Unable to open log file "/var/log/cups/access_log" - Permission denied
Jul 17 08:39:29 john-ubuntu dhcdbd: Started up.
Jul 17 08:39:30 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:39:30 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:39:30 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 08:39:33 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 08:39:33 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 08:39:33 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 08:42:21 john-ubuntu dhcdbd: Started up.
Jul 17 08:42:22 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:42:22 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:42:22 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 08:42:28 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 08:42:28 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 08:42:28 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 08:49:52 john-ubuntu dhcdbd: Started up.
Jul 17 08:49:53 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:49:53 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 08:49:53 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 08:49:56 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 08:49:56 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 08:49:56 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 09:31:39 john-ubuntu dhcdbd: Started up.
Jul 17 09:31:40 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:31:40 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:31:40 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 09:31:46 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 09:31:46 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 09:31:46 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 09:36:08 john-ubuntu dhcdbd: Started up.
Jul 17 09:36:09 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:36:09 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:36:09 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 09:36:11 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 09:36:11 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 09:36:11 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 09:58:37 john-ubuntu dhcdbd: Started up.
Jul 17 09:58:38 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:58:38 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 09:58:38 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 09:58:42 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 09:58:42 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 09:58:42 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 10:00:25 john-ubuntu dhcdbd: Started up.
Jul 17 10:00:26 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 10:00:26 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 10:00:26 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 10:00:29 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 10:00:29 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 10:00:29 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 10:54:31 john-ubuntu dhcdbd: Started up.
Jul 17 10:54:32 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 10:54:32 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 10:54:32 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 10:54:37 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 10:54:37 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 10:54:37 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 11:13:44 john-ubuntu dhcdbd: Started up.
Jul 17 11:13:45 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 11:13:45 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 11:13:45 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 11:13:47 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 11:13:47 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 11:13:47 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 12:12:47 john-ubuntu dhcdbd: Started up.
Jul 17 12:12:48 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 12:12:48 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 12:12:48 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 12:12:53 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 12:12:53 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 12:12:53 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 12:17:56 john-ubuntu cupsd: Unable to open log file "/var/log/cups/error_log" - Permission denied
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): starting (version 2.18.0.1), pid 6113 user 'root'
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 17 12:18:09 john-ubuntu gconfd (root-6113): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 17 12:18:16 john-ubuntu gconfd (root-6113): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 0
Jul 17 12:34:17 john-ubuntu gconfd (root-6113): Exiting
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): starting (version 2.18.0.1), pid 7933 user 'root'
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 17 12:49:19 john-ubuntu gconfd (root-7933): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 17 12:49:20 john-ubuntu gconfd (root-7933): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 0
Jul 17 13:02:49 john-ubuntu gconfd (root-7933): Failed to send buffer
Jul 17 14:03:10 john-ubuntu gconfd (root-7933): Exiting
Jul 17 14:06:07 john-ubuntu dhcdbd: Started up.
Jul 17 14:06:07 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:06:07 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:06:08 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 14:06:13 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 14:06:13 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 14:06:13 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 14:12:44 john-ubuntu dhcdbd: Started up.
Jul 17 14:12:44 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:12:44 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:12:48 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 14:12:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 14:12:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 14:12:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 14:14:48 john-ubuntu dhcdbd: Started up.
Jul 17 14:14:49 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:14:49 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:14:49 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 14:14:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 14:14:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 14:14:51 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 14:18:59 john-ubuntu dhcdbd: Started up.
Jul 17 14:18:59 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:18:59 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 17 14:18:59 john-ubuntu hpiod: 1.7.3 accepting connections at 2208...
Jul 17 14:19:02 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jul 17 14:19:02 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jul 17 14:19:02 john-ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): starting (version 2.18.0.1), pid 6389 user 'root'
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jul 17 14:22:22 john-ubuntu gconfd (root-6389): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jul 17 14:22:25 john-ubuntu gconfd (root-6389): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 0

Revision history for this message
Cesare Tirabassi (norsetto) said : 		#4

My mistake, it is daemon.log
Try again to see if it contains some hints.
I assume you are running gdm from the recovery session?
As you already spotted this is indeed not normal:

mkdtemp: private socket dir: Permission denied

Have you run other sessions before as root? This could change the ownership of some files in your home directory and cause such a problem.
Can you check the permissions of files and directories in your home dir? Make particular attention to hidden ones.
Check also what is in your .dmrc file.

Revision history for this message
John Cottier (j-cottier) said : 		#5

Hello Cesare,

I found that the error "mkdtemp: private socket dir: Permission denied" was
due to incorrect permissions on /tmp folder. I changed this using chmod
a+w /tmp (found on ubuntu forum) and I can now login to kde.
However something is still pear shaped with the login/out.

If I try to logout, I just get a brief view of the down splash then the screen
goes black with a flashing text cursor. However if I use Ctrl+Alt+Bkspace
this takes me back to login ok.

Also, if I try to login to the ubuntu desktop, I just get a white screen and a
mouse cursor. Any ideas?

I have only run sessions as root with the recovery mode, and with normal
terminal session using sudo because graphical login failed. Never before. I
suspect an errant program simple-backup was responsible for changing
permissions as this requires root permissions to launch, and it was after a
test backup/restore that Kubuntu failed. But I am not going to test my
theory!!

Regards

John Cottier.

On Tuesday 17 July 2007 17:50:36 Cesare Tirabassi wrote:
> Your question #9899 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/9899
>
> Status: Open => Answered
>
> Cesare Tirabassi proposed the following answer:
> My mistake, it is daemon.log
> Try again to see if it contains some hints.
> I assume you are running gdm from the recovery session?
> As you already spotted this is indeed not normal:
>
> mkdtemp: private socket dir: Permission denied
>
> Have you run other sessions before as root? This could change the ownership
> of some files in your home directory and cause such a problem. Can you
> check the permissions of files and directories in your home dir? Make
> particular attention to hidden ones. Check also what is in your .dmrc file.

Scanned by MailDefender - managed email security from intY - www.maildefender.net

Revision history for this message
Cesare Tirabassi (norsetto) said : 		#6

John,

if you want to debug gdm, it is advisable to enable its debug mode.
You may want to follow the advice of this page:

http://www.gnome.org/projects/gdm/docs/2.14/troubleshooting.html

There is also a good tip about relaxing permissions.

Revision history for this message
Best Cesare Tirabassi (norsetto) said : 		#7

Sorry, that was the wrong version. Its about the same text:

http://www.gnome.org/projects/gdm/docs/2.18/troubleshooting.html

You may want to read a bit through the manual as well.

Revision history for this message
John Cottier (j-cottier) said : 		#8

Hello Casare, Thanks I seem to have resolved it now, but I will keep that info for reference.
I took an inspired guess and replaced the restricted nvidia driver that I had installed before this problem.
I did this by manually launching gnome-control-centre since Kcontrol does not allow this operation for some reason (its greyed out in administrator mode).
When I re-started the xserver (Ctrl+Alt+BkSpace) it all worked properly again. Logout is normal, and login to gnome or kde works fine. I will check for any other errors but I cant see anything serious.

I think what happened is that simple backup changed the permissions of /tmp initially, and then not knowing how or what had fallen over, tried removing the restricted driver which did not complete cleanly due to lack of proper permissions in /tmp. Thats my theory anyway.

Regards John Cottier.