Entre para seguir isso  
Seguidores 0
omizocles

Logoff inesperado automatico, fechando os aplicativos no ubuntu

9 posts neste tópico

Olá, hora estou utilizando o ubuntu 11.10 normalmente, mas quando menos se espera o sistema faz logoff automaticamente, principalmente quando, mas comumente, duplicando abas no chrome, não sei o que ocasiona isso, mas é muito irritante, já perdi uma trabalho pois, simplemente do nada, ele fez logoff fechando tudo. Será que tem algum atalho pra fazer logoff conflitando ou algo ativo na inicialização relacionado a atualização, onde posso desativar isso. Obrigado!

--------

Pesquisando verifiquei que existe um atalho que se eu precionar uma vez fecha a linha de comando "Ctrl+D" mas descobri que se for precionado duas vezes ele acaba fazendo logoff no sistema. Talvez me tenha ocorrido isso, mas as vezes eu só movo o mouse depois de deixa a noite ligado e faz logoff do nada. Alguma outra coisa pode esta ocasionado isso. O que seria, a tela de atualização do ubuntu automatica estava aberta no momento ocorrido. Obrigado.

Editado por omizocles
Obs.:

Compartilhar este post


Link para o post
Compartilhar em outros sites

Terá que analisar os logs do sistemas. Pegue a hora em que isso aconteceu, abra o syslog. log (está no /var/log) e extraia as linhas que tenham alguma informação sobre esse logoff inesperado.

Compartilhar este post


Link para o post
Compartilhar em outros sites
Terá que analisar os logs do sistemas. Pegue a hora em que isso aconteceu, abra o syslog. log (está no /var/log) e extraia as linhas que tenham alguma informação sobre esse logoff inesperado.

Este arquivo registra todos os eventos que ocorrem no linux? Boa. Vou verificar o arquivo quando ocorrer, a situação ta chata, to até digitando mais devagar com medo de fechar algo importante que estou fazendo... esperar o bendito problema acontecer de novo e dou resposta... flws.

Editado por omizocles

Compartilhar este post


Link para o post
Compartilhar em outros sites
Este arquivo registra todos os eventos que ocorrem no linux? Boa. Vou verificar o arquivo quando ocorrer, a situação ta chata, to até digitando mais devagar com medo de fechar algo importante que estou fazendo... esperar o bendito problema acontecer de novo e dou resposta... flws.

Depois de um tempo sem este problema, voltou a acontecer hoje, fez logoff do nada e fechou tudo que tava aberto no ubuntu, acessei o arquivo syslog mas não identifiquei nada, vou colar aqui:

May  6 10:11:33 nbtl kernel: [ 1415.322380] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:33 nbtl kernel: [ 1415.322389] ata3.00: irq_stat 0x40000001
May 6 10:11:33 nbtl kernel: [ 1415.322395] ata3.00: failed command: READ DMA EXT
May 6 10:11:33 nbtl kernel: [ 1415.322408] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:33 nbtl kernel: [ 1415.322410] res 51/40:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:33 nbtl kernel: [ 1415.322417] ata3.00: status: { DRDY ERR }
May 6 10:11:33 nbtl kernel: [ 1415.322421] ata3.00: error: { UNC }
May 6 10:11:33 nbtl kernel: [ 1415.323689] ata3.00: configured for UDMA/100
May 6 10:11:33 nbtl kernel: [ 1415.323707] sd 2:0:0:0: [sda] Unhandled sense code
May 6 10:11:33 nbtl kernel: [ 1415.323711] sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 6 10:11:33 nbtl kernel: [ 1415.323717] sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
May 6 10:11:33 nbtl kernel: [ 1415.323723] Descriptor sense data with sense descriptors (in hex):
May 6 10:11:33 nbtl kernel: [ 1415.323727] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 6 10:11:33 nbtl kernel: [ 1415.323741] 16 81 7a d0
May 6 10:11:33 nbtl kernel: [ 1415.323747] sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
May 6 10:11:33 nbtl kernel: [ 1415.323754] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 16 81 7a d0 00 00 08 00
May 6 10:11:33 nbtl kernel: [ 1415.323768] end_request: I/O error, dev sda, sector 377584336
May 6 10:11:33 nbtl kernel: [ 1415.323798] ata3: é complete
May 6 10:11:37 nbtl kernel: [ 1419.368651] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:37 nbtl kernel: [ 1419.368659] ata3.00: irq_stat 0x40000001
May 6 10:11:37 nbtl kernel: [ 1419.368666] ata3.00: failed command: READ DMA EXT
May 6 10:11:37 nbtl kernel: [ 1419.368678] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:37 nbtl kernel: [ 1419.368680] res 51/40:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:37 nbtl kernel: [ 1419.368687] ata3.00: status: { DRDY ERR }
May 6 10:11:37 nbtl kernel: [ 1419.368691] ata3.00: error: { UNC }
May 6 10:11:37 nbtl kernel: [ 1419.370124] ata3.00: configured for UDMA/100
May 6 10:11:37 nbtl kernel: [ 1419.370141] ata3: é complete
May 6 10:11:41 nbtl kernel: [ 1423.407866] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:41 nbtl kernel: [ 1423.407874] ata3.00: irq_stat 0x40000001
May 6 10:11:41 nbtl kernel: [ 1423.407882] ata3.00: failed command: READ DMA EXT
May 6 10:11:41 nbtl kernel: [ 1423.407894] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:41 nbtl kernel: [ 1423.407897] res 51/01:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x1 (device error)
May 6 10:11:41 nbtl kernel: [ 1423.407903] ata3.00: status: { DRDY ERR }
May 6 10:11:41 nbtl kernel: [ 1423.409232] ata3.00: configured for UDMA/100
May 6 10:11:41 nbtl kernel: [ 1423.409249] ata3: é complete
May 6 10:11:45 nbtl kernel: [ 1427.428029] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:45 nbtl kernel: [ 1427.428038] ata3.00: irq_stat 0x40000001
May 6 10:11:45 nbtl kernel: [ 1427.428045] ata3.00: failed command: READ DMA EXT
May 6 10:11:45 nbtl kernel: [ 1427.428057] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:45 nbtl kernel: [ 1427.428060] res 51/40:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:45 nbtl kernel: [ 1427.428066] ata3.00: status: { DRDY ERR }
May 6 10:11:45 nbtl kernel: [ 1427.428071] ata3.00: error: { UNC }
May 6 10:11:45 nbtl kernel: [ 1427.429330] ata3.00: configured for UDMA/100
May 6 10:11:45 nbtl kernel: [ 1427.429349] ata3: é complete
May 6 10:11:51 nbtl kernel: [ 1433.288324] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:51 nbtl kernel: [ 1433.288333] ata3.00: irq_stat 0x40000001
May 6 10:11:51 nbtl kernel: [ 1433.288340] ata3.00: failed command: READ DMA EXT
May 6 10:11:51 nbtl kernel: [ 1433.288352] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:51 nbtl kernel: [ 1433.288355] res 51/40:00:d1:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:51 nbtl kernel: [ 1433.288361] ata3.00: status: { DRDY ERR }
May 6 10:11:51 nbtl kernel: [ 1433.288366] ata3.00: error: { UNC }
May 6 10:11:51 nbtl kernel: [ 1433.289627] ata3.00: configured for UDMA/100
May 6 10:11:51 nbtl kernel: [ 1433.289645] ata3: é complete
May 6 10:11:55 nbtl kernel: [ 1437.186160] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:55 nbtl kernel: [ 1437.186169] ata3.00: irq_stat 0x40000001
May 6 10:11:55 nbtl kernel: [ 1437.186176] ata3.00: failed command: READ DMA EXT
May 6 10:11:55 nbtl kernel: [ 1437.186188] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:55 nbtl kernel: [ 1437.186191] res 51/40:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:55 nbtl kernel: [ 1437.186198] ata3.00: status: { DRDY ERR }
May 6 10:11:55 nbtl kernel: [ 1437.186202] ata3.00: error: { UNC }
May 6 10:11:55 nbtl kernel: [ 1437.187480] ata3.00: configured for UDMA/100
May 6 10:11:55 nbtl kernel: [ 1437.187499] ata3: é complete
May 6 10:11:59 nbtl kernel: [ 1441.215358] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
May 6 10:11:59 nbtl kernel: [ 1441.215367] ata3.00: irq_stat 0x40000001
May 6 10:11:59 nbtl kernel: [ 1441.215374] ata3.00: failed command: READ DMA EXT
May 6 10:11:59 nbtl kernel: [ 1441.215386] ata3.00: cmd 25/00:08:d0:7a:81/00:00:16:00:00/e0 tag 0 dma 4096 in
May 6 10:11:59 nbtl kernel: [ 1441.215389] res 51/40:00:d0:7a:81/00:00:16:00:00/e0 Emask 0x9 (media error)
May 6 10:11:59 nbtl kernel: [ 1441.215395] ata3.00: status: { DRDY ERR }
May 6 10:11:59 nbtl kernel: [ 1441.215400] ata3.00: error: { UNC }
May 6 10:11:59 nbtl kernel: [ 1441.216671] ata3.00: configured for UDMA/100
May 6 10:11:59 nbtl kernel: [ 1441.216693] sd 2:0:0:0: [sda] Unhandled sense code
May 6 10:11:59 nbtl kernel: [ 1441.216698] sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 6 10:11:59 nbtl kernel: [ 1441.216706] sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
May 6 10:11:59 nbtl kernel: [ 1441.216715] Descriptor sense data with sense descriptors (in hex):
May 6 10:11:59 nbtl kernel: [ 1441.216719] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
May 6 10:11:59 nbtl kernel: [ 1441.216738] 16 81 7a d0
May 6 10:11:59 nbtl kernel: [ 1441.216747] sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
May 6 10:11:59 nbtl kernel: [ 1441.216756] sd 2:0:0:0: [sda] CDB: Read(10): 28 00 16 81 7a d0 00 00 08 00
May 6 10:11:59 nbtl kernel: [ 1441.216775] end_request: I/O error, dev sda, sector 377584336
May 6 10:11:59 nbtl kernel: [ 1441.216806] ata3: é complete
May 6 10:12:42 nbtl anacron[1008]: Job `cron.daily' terminated (exit status: 1) (mailing output)
May 6 10:12:42 nbtl anacron[1008]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
May 6 10:12:42 nbtl anacron[1008]: Normal exit (1 job run)
May 6 10:17:01 nbtl CRON[4223]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 6 10:23:12 nbtl gnome-session[1993]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :0.#012
May 6 10:23:12 nbtl acpid: client 1144[0:0] has disconnected
May 6 10:23:12 nbtl acpid: client connected from 4434[0:0]
May 6 10:23:12 nbtl acpid: 1 client rule loaded
May 6 10:23:14 nbtl dbus[747]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper)
May 6 10:23:14 nbtl dbus[747]: [system] Successfully activated service 'net.reactivated.Fprint'
May 6 13:23:15 nbtl rtkit-daemon[1689]: Successfully made thread 4526 of process 4526 (n/a) owned by '104' high priority at nice level -11.
May 6 13:23:15 nbtl rtkit-daemon[1689]: Supervising 1 threads of 1 processes of 1 users.
May 6 13:23:15 nbtl rtkit-daemon[1689]: Successfully made thread 4527 of process 4526 (n/a) owned by '104' RT at priority 5.
May 6 13:23:15 nbtl rtkit-daemon[1689]: Supervising 2 threads of 1 processes of 1 users.
May 6 13:23:15 nbtl rtkit-daemon[1689]: Successfully made thread 4528 of process 4526 (n/a) owned by '104' RT at priority 5.
May 6 13:23:15 nbtl rtkit-daemon[1689]: Supervising 3 threads of 1 processes of 1 users.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Successfully made thread 4634 of process 4634 (n/a) owned by '1000' high priority at nice level -11.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Supervising 4 threads of 2 processes of 2 users.
May 6 10:23:28 nbtl pulseaudio[4634]: [pulseaudio] pid.c: Stale PID file, overwriting.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Successfully made thread 4639 of process 4634 (n/a) owned by '1000' RT at priority 5.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Supervising 5 threads of 2 processes of 2 users.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Successfully made thread 4643 of process 4643 (n/a) owned by '1000' high priority at nice level -11.
May 6 13:23:28 nbtl rtkit-daemon[1689]: Supervising 6 threads of 3 processes of 2 users.
May 6 10:23:28 nbtl pulseaudio[4643]: [pulseaudio] pid.c: Daemon already running.
May 6 10:32:19 nbtl ntfs-3g[5808]: Version 2011.4.12AR.4 external FUSE 28.

O Log acima é da ultimos minutos antes do logoff.

Estava aberto o Google Chrome, Player Audacious, Janelas do Nautilus, qBittorrent, fechou tudo e voltou a tela de logoff, e no momento estava só lendo algo na net... nem havia tocado no teclado. Dei um tapa no note, (_(, não tenho ideia do que esta gerando isso. Sorte também de não esta fazendo nada importante.

Compartilhar este post


Link para o post
Compartilhar em outros sites

Me passa teu lspci e, além disso, procure nos logs do

/var/log/Xorg.xxxxx

alguma coincidência com esse erro:

10:23:12 nbtl gnome-session[1993]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :0.#012

Compartilhar este post


Link para o post
Compartilhar em outros sites
Me passa teu lspci e, além disso, procure nos logs do

/var/log/Xorg.xxxxx

alguma coincidência com esse erro:

10:23:12 nbtl gnome-session[1993]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :0.#012

lspci

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
09:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
09:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
09:09.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
09:09.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)

Não encontrei nada parecido nos arquivos de log citados com os erro acima, IO error 11 x server.

Desculpe a demora...

Compartilhar este post


Link para o post
Compartilhar em outros sites

Olá, pesquisando achei este tópico, onde, parece ser um bug quando se esta utilizando o gnome-shell no ubuntu 11.10.

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/887794

Será que este tópico ajuda.

Parece que ainda não tem uma solução, mas ainda estou na expectativa, hoje novamente fez logoff, acho que vou acabar voltando ao unit ou gnome classic, só para testar se isso ira ocorre também.

Compartilhar este post


Link para o post
Compartilhar em outros sites

Para análise, vou precisar do teu syslog ( do mesmo horário do problema) para análise.

Compartilhar este post


Link para o post
Compartilhar em outros sites
Para análise, vou precisar do teu syslog ( do mesmo horário do problema) para análise.

Testando ocorreu o mesmo problema quando não usava o gnome-shell, 3 vezes hoje :naonao:, assim que ocorrer, postarei novamente, to preocupado, pois estava utilizando este para trabalho e ocorrer um problema desses...

Compartilhar este post


Link para o post
Compartilhar em outros sites

Crie uma conta ou entre para comentar

Você precisar ser um membro para fazer um comentário

Criar uma conta

Crie uma nova conta em nossa comunidade. É fácil!


Crie uma nova conta

Entrar

Já tem uma conta? Faça o login.


Entrar agora
Entre para seguir isso  
Seguidores 0