我的系统是ubuntu 7.04
今天上午看linux设备驱动程序 写了个程序 然后到控制台 运行 看了下输出
回来后 浏览网页的时候突然显示器黑屏 显示超出工作频率
然后我重启进入KDE 显示 您的会话只持续了不到10秒钟 请查看 .xsession-errors
但是可以进入GNOME桌面 我把.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" "eric"
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=zh_CN.
Start IM through /etc/X11/xinit/xinput.d/zh_CN linked to /etc/X11/xinit/xinput.d/scim.
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
SESSION_MANAGER=local/eric-desktop:/tmp/.ICE-unix/5333
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.4
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.4
Initializing gnome-mount extension
(gnome-panel:5441): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 26
evolution-alarm-notify-Message: Setting timeout for 49263 1197388800 1197339537
evolution-alarm-notify-Message: Wed Dec 12 00:00:00 2007
evolution-alarm-notify-Message: Tue Dec 11 10:18:57 2007
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 Wed Dec 12 00:00:00 2007
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/eric/.evolution/calendar/local/system
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/eric/.evolution/calendar/local/system - Calendar Open Async... 0x80bbed0
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:///
alarm-notify.c:456 (alarm_notify_add_calendar) contacts:/// - Calendar Open Async... 0x80d3b70
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/eric/.evolution/tasks/local/system
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/eric/.evolution/tasks/local/system - Calendar Open Async... 0x80d3cc0
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/eric/.evolution/memos/local/system
alarm-notify.c:456 (alarm_notify_add_calendar) file:///home/eric/.evolution/memos/local/system - Calendar Open Async... 0x80d7700
alarm-notify.c:393 (cal_opened_cb) file:///home/eric/.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) - 0x80dbf68: Received at thread b4536b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80bbed0
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:393 (cal_opened_cb) file:///home/eric/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-queue.c:560 (load_alarms_for_today) - From Tue Dec 11 10:19:03 2007
to Tue Dec 11 10:19:03 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80d6fe8: Received at thread b4536b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d3b70
alarm-notify.c:337 (alarm_msgport_replied) - 0x80dbf68: Replied to GUI thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Dec 11 10:19:03 2007
to Tue Dec 11 10:19:03 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:349 (alarm_msg_received) - 0x80d6ac0: Received at thread b4536b90
alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d3cc0
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d6fe8: Replied to GUI thread
alarm-queue.c:560 (load_alarms_for_today) - From Tue Dec 11 10:19:03 2007
to Tue Dec 11 10:19:03 2007
alarm-queue.c:497 (load_alarms)
alarm-queue.c:526 (load_alarms) - Setting Call backs
alarm-notify.c:337 (alarm_msgport_replied) - 0x80d6ac0: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) file:///home/eric/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80e83a0: Received** Message: <information> 您已连接到有线网络。
窗口管理器警告: 为 0x300027 (保留分�) 指定了无效的 WM_TRANSIENT_FOR 窗口 0x3000003。
进不了KDE 显示 您的会话只持续了不到10秒钟
-
- 帖子: 5
- 注册时间: 2007-04-05 14:25
-
- 帖子: 5
- 注册时间: 2007-04-05 14:25
-
- 帖子: 1
- 注册时间: 2008-09-17 12:51
我也遇见相同问题,不过已经解决了
我用root帐户登录,使用了chsh命令更改shell,把New shell的路径误输为“/bin/sh”,结果再用root登录时总提示:
“您的会话只持续了不到10秒钟。如果您没有注销,这就意味着安装可能出现了问题或者您的磁盘空间已耗尽,可以试试以某个failsafe会话登录以查看是否可以解决此问题”
使用failsafe会话登录根本没用,但我用另一普通用户登录正常,于是使用该普通帐户登录,在终端窗口使用su更换为root用户登录。然后再次使用chsh命令更改shell为“/bin/bash”,重启后再登录就好了。[/img]
“您的会话只持续了不到10秒钟。如果您没有注销,这就意味着安装可能出现了问题或者您的磁盘空间已耗尽,可以试试以某个failsafe会话登录以查看是否可以解决此问题”
使用failsafe会话登录根本没用,但我用另一普通用户登录正常,于是使用该普通帐户登录,在终端窗口使用su更换为root用户登录。然后再次使用chsh命令更改shell为“/bin/bash”,重启后再登录就好了。[/img]