Acak dan tiba-tiba keluar dari sesi pengguna saya

17

Saya punya masalah dengan ubuntu 14.10 dan 15.04. Saya keluar dari sesi pengguna saya secara acak dan tiba-tiba.

Berikut ini beberapa informasi log:

kern.log

logout pertama:

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

logout kedua:

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

logout pertama:

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....

logout kedua:

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....

Adakah ide untuk memperbaikinya?

Salam

logout Aliot
sumber
Ketik Ctrl-Alt-F1 dan login ke sesi terminal. sudo grep metacity /var/spool/log/*
waltinator
@ Alliot Kesalahan apa pun dalam log Xorg juga dapat membantu pemecahan masalah. sudo grep EE /var/log/Xorg.0.log
kargo
apakah Anda mencoba dpkg-mengkonfigurasi ulang metacity? (tidak pernah melakukan mysef, tetapi jika gagal, mungkin masalahnya adalah metacity atau konfigurasi server X)
feligiotti
ini persis seperti apa yang dihadapi teman saya. dan dia memperhatikan bahwa sesinya selalu tiba-tiba logout jika dia menjalankan Chrome. apakah Anda mengalami ini saat menjalankan program tertentu? ini memang bug. dalam kasus Anda tampaknya 'kegigihan'. coba gunakan program windows manager lain.
adadion
dapatkah kita memiliki beberapa informasi spesifik perangkat keras silakan buka terminal dan ketik lspci kemudian kirimkan output. Apakah Anda sudah menginstal tema atau memodifikasi GUI?
Komputer A1

Jawaban:

1

Ini adalah bug yang belum terselesaikan, tetapi relatif jarang, jika Anda menggunakan sesi gnome-flashback. Sebagian karena sebagian besar semuanya menggunakan UI default. Lihat detail lebih lanjut dan berlangganan untuk melihat apakah masalah teratasi di sini: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916

Perbaikan sementara - jangan gunakan sesi gnome-flashback.

ulcha
sumber