升级14.10后,启动出了点小问题,求助!

荆棘谷-部落-我要么 发布于 2014/10/26 07:45
阅读 7K+
收藏 2
以下是 dmesg 的信息,其中: 
systemd-logind 好像有点问题,对吧?
gdm 被杀死?
nmbd 进程无法启动?我把 samba 给删了的。。。
各位,还能从这里看出什么问题不能?

谢谢了。

代码:
[   31.662523] init: gdm main process (2613) killed by TERM signal
[   35.843633] init: Failed to spawn nmbd main process: unable to execute: No such file or directory
[   35.990697] init: plymouth-upstart-bridge main process ended, respawning
[   36.325536] systemd-logind[2062]: Failed to start unit  user@111.service : Unknown unit:  user@111.service
[   36.325543] systemd-logind[2062]: Failed to start user service: Unknown unit:  user@111.service
[   36.328918] systemd-logind[2062]: New session c1 of user lightdm.
[   36.328935] systemd-logind[2062]: Linked /tmp/.X11-unix/X0 to /run/user/111/X11-display.
[   43.344674] systemd-logind[2062]: Failed to start unit  user@1000.service : Unknown unit:  user@1000.service
[   43.344681] systemd-logind[2062]: Failed to start user service: Unknown unit:  user@1000.service
[   43.349577] systemd-logind[2062]: New session c2 of user wyn.
[   43.349593] systemd-logind[2062]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
[   55.057878] audit: type=1400 audit(1414195175.782:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=3634 comm="apparmor_parser"
[   55.057887] audit: type=1400 audit(1414195175.782:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=3634 comm="apparmor_parser"
[   55.070040] audit: type=1400 audit(1414195175.798:43): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="third_party" pid=3634 comm="apparmor_parser"
[   96.318683] systemd-timedated[3855]: /etc/localtime should be a symbolic link to a timezone data file in /usr/share/zoneinfo/.
[  234.252004] chrome[3998]: segfault at 1f8 ip 00007f3a8912163f sp 00007fffb6a9c0e0 error 4 in i965_dri.so[7f3a88dce000+51c000]
[  234.655106] chrome[4095]: segfault at 1f8 ip 00007fb70e93363f sp 00007fff0b20e0f0 error 4 in i965_dri.so[7fb70e5e0000+51c000]
[  234.697923] chrome[4103]: segfault at 1f8 ip 00007f1dc283363f sp 00007fffe30bc5d0 error 4 in i965_dri.so[7f1dc24e0000+51c000]
[ 6327.911360] systemd-logind[2062]: Power key pressed.

[ 6329.057202] compiz[3319]: segfault at 75 ip 00007fd6524491c0 sp 00007fff219e6938 error 4 in libnux-core-4.0.so.0.7.0[7fd652406000+4e000]

另,启动时,好像有提示: failed 

加载中
0
eechen
eechen
Ubuntu14.10引入了systemd这个新的服务管理器,而原来的版本比如14.04有些服务用的是upstart,因此可能会造成一些问题。14.04是LTS版,支持期长达5年,不建议从LTS版升级到普通版本,默认情况下系统也不支持这样升级,因为这会让LTS显得没有意义。安心使用5年LTS版,以后再重新安装1个最新的LTS新版本,这是我推荐的做法。
荆棘谷-部落-我要么
荆棘谷-部落-我要么
已经升过级了,看来是改不回来了。。。
0
love4taylor
love4taylor

me too

[  107.954693] systemd-logind[828]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
[  107.954702] systemd-logind[828]: Failed to start user service: Unknown unit: user@1000.service
[  107.960521] systemd-logind[828]: New session c2 of user love4taylor.
[  107.960548] systemd-logind[828]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.

0
hippieZhou
hippieZhou
有可能是内核出错了吧,我以前也升级过一次,就是因为内核升级失败导致系统崩溃!
0
流光月舞
流光月舞
你可以試試從舊的內核啟動'看看能不能正常進入。我早就升級到14.10,正常使用中
0
f
freebird666

sudo apt-get purege systemd

sudo apt-get remove systemd

OSCHINA
登录后可查看更多优质内容
返回顶部
顶部