O Ubuntu 16.04 ocasionalmente trava com a tela desligada depois de trocar de TTYs ou desligar a tela por inatividade

1

Às vezes, quando eu alterno TTYs (também durante a alternância entre usuários conectados) ou depois que a tela escurece e desliga, minha tela fica / permanece no modo de espera e não é mais ativada. Na verdade, todo o sistema trava então porque ele não reage mais a nada (pressionar, por exemplo, Shift ou NUM-Lock não alterna os LEDs,).

A única coisa que ainda funciona são os comandos mágicos Alt + SysRq que eu uso para reiniciar a máquina ("R-E-I-S-U-B").

Eu suspeito de um problema com minha antiga placa de vídeo AMD. Ele também está desligando e ligando a tela rapidamente, como se fosse alterar a resolução em várias ocasiões, como abrir a janela Configurações do Sistema, etc. Talvez o suporte a hardware desse modelo tenha sido removido (acidentalmente) desde 16.04, porque antes da atualização em 15.10 sem essas falhas. As falsas mudanças de resolução estavam presentes naquela época também. Usando o desktop Unity do Ubuntu 16.04 de 64 bits agora.

Meus gráficos:

$ inxi -G
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV535 [Radeon X1650 PRO]
           Display Server: X.Org 1.18.3 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: [email protected]
           GLX Renderer: Gallium 0.4 on ATI RV530 GLX Version: 2.1 Mesa 11.2.0

Trecho de syslog em torno do último travamento (causado por TTS alternando entre dois usuários conectados) e antes de reinicializar o sistema com o REISUB:

Jul  4 18:52:18 wolf-pack gnome-session[2706]: gnome-session-binary[2706]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul  4 18:52:18 wolf-pack gnome-session[2706]: message repeated 4 times: [ gnome-session-binary[2706]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed]
Jul  4 18:52:18 wolf-pack gnome-session-binary[2706]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul  4 18:52:18 wolf-pack gnome-session-binary[2706]: message repeated 4 times: [ GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed]
Jul  4 18:52:18 wolf-pack gnome-session[2706]: gnome-session-binary[2706]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul  4 18:52:18 wolf-pack gnome-session-binary[2706]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (deja-dup-monitor:5126): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack org.gnome.zeitgeist.SimpleIndexer[2570]: (zeitgeist-fts:3365): GLib-GIO-WARNING **: Error releasing name org.gnome.zeitgeist.SimpleIndexer: The connection is closed
Jul  4 18:52:20 wolf-pack org.gnome.zeitgeist.SimpleIndexer[2570]: ** (zeitgeist-fts:3365): WARNING **: zeitgeist-fts.vala:252: The connection is closed
Jul  4 18:52:20 wolf-pack org.gnome.zeitgeist.Engine[2570]: (zeitgeist-daemon:3358): GLib-GIO-WARNING **: Error releasing name org.gnome.zeitgeist.Engine: The connection is closed
Jul  4 18:52:20 wolf-pack org.gnome.zeitgeist.Engine[2570]: #033[31m[16:52:20.036353 WARNING]#033[0m zeitgeist-daemon.vala:449: The connection is closed
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (unity-fallback-mount-helper:2853): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (deja-dup-monitor:5126): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (deja-dup-monitor:5126): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (deja-dup-monitor:5126): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack gnome-session[2706]: (deja-dup-monitor:5126): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jul  4 18:52:20 wolf-pack gnome-session[2706]: ** (zeitgeist-datahub:3347): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Jul  4 18:52:24 wolf-pack systemd[1]: Created slice User Slice of lightdm.
Jul  4 18:52:24 wolf-pack systemd[1]: Starting User Manager for UID 119...
Jul  4 18:52:24 wolf-pack systemd[1]: Started Session c5 of user lightdm.
Jul  4 18:52:24 wolf-pack systemd[16791]: Reached target Paths.
Jul  4 18:52:24 wolf-pack systemd[16791]: Reached target Timers.
Jul  4 18:52:24 wolf-pack systemd[16791]: Reached target Sockets.
Jul  4 18:52:24 wolf-pack systemd[16791]: Reached target Basic System.
Jul  4 18:52:24 wolf-pack systemd[16791]: Reached target Default.
Jul  4 18:52:24 wolf-pack systemd[16791]: Startup finished in 127ms.
Jul  4 18:52:24 wolf-pack systemd[1]: Started User Manager for UID 119.
Jul  4 18:52:25 wolf-pack org.a11y.atspi.Registry[16813]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul  4 18:52:27 wolf-pack dbus[689]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Jul  4 18:52:28 wolf-pack rtkit-daemon[1829]: Successfully made thread 16859 of process 16859 (n/a) owned by '119' high priority at nice level -11.
Jul  4 18:52:28 wolf-pack rtkit-daemon[1829]: Supervising 7 threads of 3 processes of 3 users.
Jul  4 18:52:29 wolf-pack rtkit-daemon[1829]: Successfully made thread 16926 of process 16926 (n/a) owned by '119' high priority at nice level -11.
Jul  4 18:52:29 wolf-pack rtkit-daemon[1829]: Supervising 8 threads of 4 processes of 3 users.
Jul  4 18:52:29 wolf-pack pulseaudio[16926]: [pulseaudio] pid.c: Daemon already running.
Jul  4 18:52:42 wolf-pack systemd[1]: Stopping User Manager for UID 1000...
Jul  4 18:52:42 wolf-pack systemd[1923]: Reached target Shutdown.
Jul  4 18:52:42 wolf-pack systemd[1923]: Starting Exit the Session...
Jul  4 18:52:42 wolf-pack systemd[1923]: Stopped target Default.
Jul  4 18:52:42 wolf-pack systemd[1923]: Stopped target Basic System.
Jul  4 18:52:42 wolf-pack systemd[1923]: Stopped target Timers.
Jul  4 18:52:42 wolf-pack systemd[1923]: Stopped target Sockets.
Jul  4 18:52:42 wolf-pack systemd[1923]: Stopped target Paths.
Jul  4 18:52:42 wolf-pack systemd[1923]: Received SIGRTMIN+24 from PID 17186 (kill).
Jul  4 18:52:42 wolf-pack systemd[1]: Stopped User Manager for UID 1000.
Jul  4 18:52:42 wolf-pack systemd[1]: Removed slice User Slice of alphawolf.
Jul  4 18:52:52 wolf-pack pulseaudio[16859]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
Jul  4 18:52:58 wolf-pack kernel: [ 2853.412116] sysrq: SysRq : This sysrq operation is disabled.
Jul  4 18:52:59 wolf-pack kernel: [ 2854.461708] sysrq: SysRq : This sysrq operation is disabled.
Jul  4 18:53:01 wolf-pack kernel: [ 2855.916207] sysrq: SysRq : This sysrq operation is disabled.
Jul  4 18:53:03 wolf-pack kernel: [ 2858.442002] sysrq: SysRq : Emergency Sync
Jul  4 18:53:03 wolf-pack kernel: [ 2858.457544] Emergency Sync complete
Jul  4 18:53:07 wolf-pack kernel: [ 2862.284760] sysrq: SysRq : Emergency Remount R/O
Jul  4 18:54:05 wolf-pack rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="750" x-info="http://www.rsyslog.com"] start

Por favor, me diga quais informações adicionais e registros você precisa.

Qual é a causa dessas falhas e como posso evitá-las?

Já desabilitei a desativação da tela após inatividade, mas não posso deixar de trocar os TTYs de vez em quando.

    
por Byte Commander 05.07.2016 / 10:03

1 resposta

0

Eu entrei neste site para ver se conseguia encontrar uma resposta para um problema muito semelhante. Eu não encontrei uma resposta exata, no entanto, o seu post e outros me fizeram mudar minha placa de vídeo. Drivers foi (com a mudança de hardware) de um ATI r5480 (com o problema) para NV43 (para problema resolvido).

Estou executando o desktop 16.04.1 LTS

    
por Simon 04.10.2016 / 20:38