有时当我切换 TTY（也包括切换登录用户时）或屏幕变暗并关闭后，我的屏幕会进入/保持待机模式并且不再唤醒。实际上整个系统会崩溃，因为它不再对任何内容做出反应（例如按Shift或NUM-Lock不会切换 LED）。
唯一仍然有效的是魔法Alt+SysRq命令，然后我使用它来重新启动机器（“REISUB”）。
我怀疑我的 AMD 显卡有问题。它还会定期短暂地关闭和打开屏幕，好像它会在多个场合更改分辨率，例如打开“系统设置”窗口等。也许自 16.04 以来（意外地？）删除了对此型号的硬件支持，因为在升级之前它在 15.10 上运行没有这些崩溃。不过，当时也存在虚假的分辨率更改。现在使用 Ubuntu 16.04，64 位，Unity 桌面。
我的图形：
$ 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
摘自syslog上次崩溃（由 TTS 在两个登录用户之间切换引起）并在使用 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
请告诉我您需要哪些附加信息和日志。
这些崩溃的原因是什么？我该如何防止它们发生？
我已经禁用了不活动后关闭屏幕的功能，但我无法放弃时不时切换 TTY。
答案1
我访问此网站是为了查看是否能找到一个非常相似的问题的答案。我没有找到确切的答案，但是，您的帖子和其他人的帖子让我更换了显卡。驱动程序（随着硬件的变化）从 ATI r5480（有问题）换成了 NV43（问题解决了）。
我正在运行桌面 16.04.1 LTS