sudo e wifi falham simultaneamente

1

Acabei de instalar o Ubuntu 16.04 LTS na minha Asus (memória de 7,7 GiB, processador Intel 5Y10 CPU a 0,80 Ghzx4, gráficos Intel HD 5300 (broadwell Gt2), 64 bits, 117,5 GB).

Após 5 a 15 minutos de uso, o Wi-Fi é desligado, mas também a capacidade de usar qualquer comando sudo no terminal. Depois de uma reinicialização, normalmente funciona novamente, mas às vezes duas reinicializações são necessárias antes que eu possa aproveitar o Ubuntu por 5-15 min novamente.

Primeiro, pensei que era apenas um problema de Wi-Fi, mas parece estar mais relacionado a uma perda de privilégios administrativos?

Foi solucionada por 2 dias e até mesmo reinstalada uma vez.

Alguma idéia?

Saída de tail -n20 /var/log/syslog

Sep 17 22:07:09 ramhak-UX305FA kernel: [ 1784.092876] asus_wmi: Unknown key cf pressed
Sep 17 22:07:09 ramhak-UX305FA kernel: [ 1784.580230] proc_thermal 0000:00:04.0: Unsupported event [0x84]
Sep 17 22:07:35 ramhak-UX305FA AptDaemon: INFO: Quitting due to inactivity
Sep 17 22:07:35 ramhak-UX305FA AptDaemon: INFO: Quitting was requested
Sep 17 22:07:35 ramhak-UX305FA org.freedesktop.PackageKit[823]: 22:07:35 AptDaemon [INFO]: Quitting due to inactivity
Sep 17 22:07:35 ramhak-UX305FA org.freedesktop.PackageKit[823]: 22:07:35 AptDaemon [INFO]: Quitting was requested
Sep 17 22:17:01 ramhak-UX305FA CRON[3318]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (gvfsd:1230): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Timeout was reached
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: message repeated 5 times: [ ** (gvfsd:1230): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Timeout was reached]
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2816): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2814): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2818): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2829): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2831): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (gvfsd:1230): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Timeout was reached
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (process:2837): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: ** (gvfsd:1230): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Timeout was reached
Sep 17 22:19:14 ramhak-UX305FA org.gtk.vfs.Daemon[1153]: message repeated 4 times: [ ** (gvfsd:1230): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Timeout was reached]
Sep 17 22:27:12 ramhak-UX305FA kernel: [ 2987.465543] proc_thermal 0000:00:04.0: Unsupported event [0x84]
Sep 17 22:37:32 ramhak-UX305FA org.gnome.evolution.dataserver.Sources5[1153]: ** (evolution-source-registry:1409): WARNING **: secret_service_search_sync: must specify at least one attribute to match
    
por ram 17.09.2017 / 22:04

1 resposta

1

Resolvido.

Analisamos cuidadosamente o /var/log/syslog (graças ao mikewhatever) e descobrimos que o kernel pode não ser o mais adequado ( --end trace--- error).

Mudou de uma versão 4.10 para uma versão 4.4 e está funcionando perfeitamente agora, isso resolveu todos os problemas mencionados acima.

    
por ram 18.09.2017 / 08:28