Mam problem z Ubuntu 14.10 i 15.04. Wylogowano mnie z sesji użytkownika losowo i nagle.
Oto niektóre informacje dziennika:
kern.log
pierwsze wylogowanie:
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
drugie wylogowanie:
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
pierwsze wylogowanie:
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....
drugie wylogowanie:
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....
Masz pomysł, aby to naprawić?
pozdrowienia
@Aliot Wszelkie błędy w dziennikach Xorg mogą również pomóc w rozwiązywaniu problemów.
—
ładunek
sudo grep EE /var/log/Xorg.0.log
próbowałeś dpkg-rekonfigurować metacity? (nigdy nie robiłem mysef, ale jeśli się nie powiedzie, być może problemem jest metacity lub konfiguracja serwera X)
—
feligiotti
dokładnie tak stało się z moim przyjacielem. i zauważa, że jego sesja zawsze nagle się wylogowuje, jeśli używa Chrome. Czy doświadczyłeś tego podczas uruchamiania określonego programu? to jest rzeczywiście błąd. w twoim przypadku wydaje się to „metacity”. spróbuj użyć innego programu zarządzającego Windows.
—
adadion
czy możemy uzyskać jakieś informacje dotyczące sprzętu, otwórz terminal i wpisz lspci, a następnie wyślij wyjście. Czy zainstalowałeś też jakieś motywy lub zmodyfikowałeś GUI?
—
A1 Computers
sudo grep metacity /var/spool/log/*