Try 'gnome-wm' and it works.  Border comes back.  But terminal shows
this (term1.png)

Below is .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" 
"clem"
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to 
/etc/X11/xinit/xinput.d/default.
SESSION_MANAGER=local/CrownBox:/tmp/.ICE-unix/5007
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
evolution-alarm-notify-Message: Setting timeout for 12476 1177516800 1177504324
evolution-alarm-notify-Message:  Thu Apr 26 00:00:00 2007

evolution-alarm-notify-Message:  Wed Apr 25 20:32:04 2007

Initializing gnome-mount extension
DCOPClient::attachInternal. Attach failed Could not open network socket
modinfo: could not find module fglrx
modinfo: could not find module ipw3945
modinfo: could not find module nvidia_legacy
modinfo: could not find module nvidia_new
modinfo: could not find module nvidia
alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New 
 alarm-notify.c:304 (alarm_channel_setup) - Channel Setup
 alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1875 (alarm_queue_init)
alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Thu Apr 26 00:00:00 2007
 
alarm-notify.c:220 (load_calendars) - Loading Calendar 
file:///home/clem/.evolution/calendar/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) 
file:///home/clem/.evolution/calendar/local/system - Calendar Open Async... 
0x1007e050
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// 
alarm-notify.c:456 (alarm_notify_add_calendar) contacts:/// - Calendar Open 
Async... 0x10096670
alarm-notify.c:220 (load_calendars) - Loading Calendar 
file:///home/clem/.evolution/tasks/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) 
file:///home/clem/.evolution/tasks/local/system - Calendar Open Async... 
0x10098fa0
alarm-notify.c:220 (load_calendars) - Loading Calendar 
file:///home/clem/.evolution/memos/local/system 
alarm-notify.c:456 (alarm_notify_add_calendar) 
file:///home/clem/.evolution/memos/local/system - Calendar Open Async... 
0x1009b820
alarm-notify.c:393 (cal_opened_cb) 
file:///home/clem/.evolution/calendar/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x100af2e8: Received at thread 
3399e4c0
alarm-queue.c:2008 (alarm_queue_add_async) - 0x1007e050
alarm-queue.c:560 (load_alarms_for_today) - From Thu Apr 26 00:00:00 2007
 to Thu Apr 26 00:00:00 2007

alarm-queue.c:497 (load_alarms) 
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x100af2e8: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) 
file:///home/clem/.evolution/tasks/local/system - Calendar Status 0

** Attachment added: "term1.png"
   http://librarian.launchpad.net/7405589/term1.png

-- 
Ubuntu Feisty Desktop
https://bugs.launchpad.net/bugs/109675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to