我在Ubuntu 14.10和15.04上遇到问题。我随机突然退出了用户会话。
以下是一些日志信息：
内核日志
首次登出：
May 3 16:34:59 rm-work kernel: [28558.808129] traps: metacity[7712] trap int3 ip:7fe10cb50d00 sp:7ffdb4f06a00 error:0
May 3 16:34:59 rm-work gnome-session[7637]: Unrecoverable failure in required component metacity.desktop
May 3 16:35:12 rm-work gnome-session[30100]: Entering running state
第二次登出：
May 4 00:50:24 rm-work kernel: [54634.236474] traps: metacity[30179] trap int3 ip:7f68e3eddd00 sp:7ffc5e2b9d30 error:0
May 4 00:50:24 rm-work gnome-session[30100]: Unrecoverable failure in required component metacity.desktop
May 4 00:50:42 rm-work gnome-session[27957]: Entering running state
syslog.log
第一次注销：
May 3 16:34:59 rm-work gnome-session[7637]: Avertissement du gestionnaire de fenêtres : Log level 6: The program 'metacity' received an X Window System error.
May 3 16:34:59 rm-work gnome-session[7637]: This probably reflects a bug in the program.
May 3 16:34:59 rm-work gnome-session[7637]: The error was 'BadRegion (invalid Region parameter)'.
May 3 16:34:59 rm-work gnome-session[7637]: (Details: serial 63596288 error_code 140 request_code 138 (XFIXES) minor_code 12)
May 3 16:34:59 rm-work gnome-session[7637]: (Note to programmers: normally, X errors are reported asynchronously;
May 3 16:34:59 rm-work gnome-session[7637]: that is, you will receive the error a while after causing it.
May 3 16:34:59 rm-work gnome-session[7637]: To debug your program, run it with the GDK_SYNCHRONIZE environment
May 3 16:34:59 rm-work gnome-session[7637]: variable to change this behavior. You can then get a meaningful
May 3 16:34:59 rm-work gnome-session[7637]: backtrace from your debugger if you break on the gdk_x_error() function.)
May 3 16:34:59 rm-work kernel: [28558.808129] traps: metacity[7712] trap int3 ip:7fe10cb50d00 sp:7ffdb4f06a00 error:0
May 3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: Child process 7712 was already dead.
May 3 16:34:59 rm-work gnome-session[7637]: WARNING: Child process 7712 was already dead.
May 3 16:34:59 rm-work gnome-session[7637]: WARNING: Application 'metacity.desktop' killed by signal 5
May 3 16:34:59 rm-work gnome-session[7637]: WARNING: App 'metacity.desktop' respawning too quickly
May 3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: Application 'metacity.desktop' killed by signal 5
May 3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: WARNING: App 'metacity.desktop' respawning too quickly
May 3 16:34:59 rm-work gnome-session[7637]: Unrecoverable failure in required component metacity.desktop
May 3 16:34:59 rm-work gnome-session[7637]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May 3 16:34:59 rm-work gnome-session[7637]: gnome-session[7637]: CRITICAL: We failed, but the fail whale is dead. Sorry....
第二次登出：
May 4 00:50:24 rm-work gnome-session[30100]: Avertissement du gestionnaire de fenêtres : Log level 6: The program 'metacity' received an X Window System error.
May 4 00:50:24 rm-work gnome-session[30100]: This probably reflects a bug in the program.
May 4 00:50:24 rm-work gnome-session[30100]: The error was 'BadRegion (invalid Region parameter)'.
May 4 00:50:24 rm-work gnome-session[30100]: (Details: serial 170024023 error_code 140 request_code 138 (XFIXES) minor_code 12)
May 4 00:50:24 rm-work gnome-session[30100]: (Note to programmers: normally, X errors are reported asynchronously;
May 4 00:50:24 rm-work gnome-session[30100]: that is, you will receive the error a while after causing it.
May 4 00:50:24 rm-work gnome-session[30100]: To debug your program, run it with the GDK_SYNCHRONIZE environment
May 4 00:50:24 rm-work gnome-session[30100]: variable to change this behavior. You can then get a meaningful
May 4 00:50:24 rm-work gnome-session[30100]: backtrace from your debugger if you break on the gdk_x_error() function.)
May 4 00:50:24 rm-work kernel: [54634.236474] traps: metacity[30179] trap int3 ip:7f68e3eddd00 sp:7ffc5e2b9d30 error:0
May 4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: Child process 30179 was already dead.
May 4 00:50:24 rm-work gnome-session[30100]: WARNING: Child process 30179 was already dead.
May 4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: Application 'metacity.desktop' killed by signal 5
May 4 00:50:24 rm-work gnome-session[30100]: WARNING: Application 'metacity.desktop' killed by signal 5
May 4 00:50:24 rm-work gnome-session[30100]: WARNING: App 'metacity.desktop' respawning too quickly
May 4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: WARNING: App 'metacity.desktop' respawning too quickly
May 4 00:50:24 rm-work gnome-session[30100]: Unrecoverable failure in required component metacity.desktop
May 4 00:50:24 rm-work gnome-session[30100]: CRITICAL: We failed, but the fail whale is dead. Sorry....
May 4 00:50:24 rm-work gnome-session[30100]: gnome-session[30100]: CRITICAL: We failed, but the fail whale is dead. Sorry....
有解决的办法吗？
问候
@Aliot Xorg日志中的任何错误也可能有助于解决问题。
—
货运
sudo grep EE /var/log/Xorg.0.log
您是否尝试过dpkg-reconfigure metacity？（从来没有做过mysef，但如果失败，则可能是由于metacity或服务器X配置）
—
feligiotti 2015年
这就像我朋友面对的一样。并且他注意到，如果他运行的是Chrome浏览器，会话总是突然退出。您在运行特定程序时是否遇到了这种情况？这确实是一个错误。就您而言，这似乎是“变态”。尝试使用其他Windows管理器程序。
—
adadion 2015年
我们可以提供一些特定于硬件的信息吗，请打开一个终端并输入lspci，然后发布输出。您是否还安装了任何主题或修改了GUI？
—
A1电脑
sudo grep metacity /var/spool/log/*