GNOME守护进程什么时候才会出错??

为当前最终发行版之前的所有版本提供支持
回复
newwoods
帖子: 6
注册时间: 2007-07-14 9:37
送出感谢: 0
接收感谢: 0

GNOME守护进程什么时候才会出错??

#1

帖子 newwoods » 2007-07-14 15:49

启动 GNOME 设置守护进程时出错。

主题、声音或者背景设置等可能不会正常工作。

最后的错误信息是:

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.

GNOME 在您下次登录时仍将试图重启动设置守护进程。



我ubuntu每次启动时,输入用户和密码后,都会傻等5分钟左右,报上面的错误,然后才出现桌面,哪个高手指点一下??
newwoods
帖子: 6
注册时间: 2007-07-14 9:37
送出感谢: 0
接收感谢: 0

#2

帖子 newwoods » 2007-07-16 22:59

怎么没有人指点呀:(

讲一下历史吧:我的cpu是amd的,装ubuntu时,说要,取消掉apic,我就disable了,
装好ubuntu后,也试着把boot/grub/menu.list修改,在kernel中增加了noapic,
发现重启不行,于是就又把去掉了noapic,
结果机器就成这样了,每次输入name和password后,等5分钟,后报错如下

启动 GNOME 设置守护进程时出错。

主题、声音或者背景设置等可能不会正常工作。

最后的错误信息是:

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.

GNOME 在您下次登录时仍将试图重启动设置守护进程。


谁能指点一下,不胜感激
头像
eexpress
帖子: 58428
注册时间: 2005-08-14 21:55
来自: 长沙
送出感谢: 4 次
接收感谢: 256 次

#3

帖子 eexpress » 2007-07-16 23:15

这种情况,少有出现,一般是自己修改了什么设置引起某些deamon失效引起的。也无定论。需要多查看自己的log。/var/log和~/.xsession-error。自己先提取错误提示出来。
● 鸣学
newwoods
帖子: 6
注册时间: 2007-07-14 9:37
送出感谢: 0
接收感谢: 0

#4

帖子 newwoods » 2007-07-19 23:07

~/..xsession-error中最近的内容,看不懂问题

55 alarm-queue.c:497 (load_alarms)
56 alarm-queue.c:526 (load_alarms) - Setting Call backs
57 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d0768: Replied to GUI thread
58 alarm-notify.c:393 (cal_opened_cb) file:///home/why/.evolution/memos/local/system - Calendar Status 0
59 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
60 alarm-notify.c:349 (alarm_msg_received) - 0x80d6c48: Received at thread b55f5b90
61 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d1880
62 alarm-queue.c:560 (load_alarms_for_today) - From Thu Jul 19 22:47:08 2007
63 to Thu Jul 19 22:47:08 2007
64
65 alarm-queue.c:497 (load_alarms)
66 alarm-queue.c:526 (load_alarms) - Setting Call backs
67 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d6c48: Replied to GUI thread
68 alarm-notify.c:393 (cal_opened_cb) file:///home/why/.evolution/tasks/local/system - Calendar Status 0
69 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
70 alarm-notify.c:349 (alarm_msg_received) - 0x80d1670: Received at thread b55f5b90
71 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80cdd30
72 alarm-queue.c:560 (load_alarms_for_today) - From Thu Jul 19 22:47:08 2007
73 to Thu Jul 19 22:47:08 2007
74
75 alarm-queue.c:497 (load_alarms)
76 alarm-queue.c:526 (load_alarms) - Setting Call backs
77 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d1670: Replied to GUI thread
78 alarm-notify.c:393 (cal_opened_cb) file:///home/why/.evolution/calendar/local/system - Calendar Status 0
79 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
80 alarm-notify.c:349 (alarm_msg_received) - 0x80cef10: Received at threa
回复

回到 “老旧版本支持”