You are not logged in.

#1 2018-05-05 07:25:18

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Problem with launching a programms after updating linux

Good day, all.
I met problem with launching half  programs after updating linux (last stable version for me  linux-4.16.2-2-x86_64):
example of stack trace for terminator:

(terminator:2512): dbind-WARNING **: 14:55:59.839: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

with firefox-developer-edition:

firefox-developer-deition:
ExceptionHandler::GenerateDump cloned child 2651
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I downgrade to linux-4.16.2-2-x86_64 and all works ok, but what i should do to handle this problem with latest version of linux?

Offline

#2 2018-05-05 08:10:02

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 25,728
Website

Re: Problem with launching a programms after updating linux

Not an Arch discussion, moving to NC...


Arch + dwm   •   Mercurial repos  •   Github

Registered Linux User #482438

Offline

#3 2018-05-05 10:23:13

Skunky
Member
Registered: 2018-01-25
Posts: 41

Re: Problem with launching a programms after updating linux

Hello lgar_tigar, can you try reinstalling one of the programs not working after update?

Offline

#4 2018-05-05 10:29:39

loqs
Member
Registered: 2014-03-06
Posts: 5,826

Re: Problem with launching a programms after updating linux

Please post the kernel messages from the journal for a boot under the affected version also a backtrace from a coredump of one of the programs.

Offline

#5 2018-05-05 12:31:47

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

Skunky wrote:

Hello lgar_tigar, can you try reinstalling one of the programs not working after update?

Sure, it was 1st step when i got this issue. It didn't help.

Offline

#6 2018-05-05 12:40:52

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 5,258

Re: Problem with launching a programms after updating linux

Please post complete outputs, what you posted so far are random excerpts that are almost certain to have no relation to what you are experiencing (especially the first one is quite likely to be normal even in a working setup)

https://bbs.archlinux.org/viewtopic.php?id=57855

Post a journal excerpt look for coredumps etc

Last edited by V1del (2018-05-05 12:43:34)

Offline

#7 2018-05-06 14:19:24

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

Try to provide all logs that can find =x

I updates linux to 4.16.6-1-ARCH GNU/Linux

during launching terminator:
just dmsg part:

[  947.735520] ata1.00: exception Emask 0x0 SAct 0x10000 SErr 0x50000 action 0x0
[  947.735533] ata1.00: irq_stat 0x40000008
[  947.735542] ata1: SError: { PHYRdyChg CommWake }
[  947.735550] ata1.00: failed command: READ FPDMA QUEUED
[  947.735569] ata1.00: cmd 60/08:80:a0:0b:24/00:00:1d:00:00/40 tag 16 ncq dma 4096 in
                        res 41/40:08:a0:0b:24/00:00:1d:00:00/6d Emask 0x409 (media error) <F>
[  947.735577] ata1.00: status: { DRDY ERR }
[  947.735583] ata1.00: error: { UNC }
[  947.735598] ata1: hard resetting link
[  948.050086] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  948.127333] ata1.00: configured for UDMA/100
[  948.127525] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  948.127534] sd 0:0:0:0: [sda] tag#16 Sense Key : Medium Error [current] 
[  948.127541] sd 0:0:0:0: [sda] tag#16 Add. Sense: Unrecovered read error - auto reallocate failed
[  948.127549] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 1d 24 0b a0 00 00 08 00
[  948.127554] print_req_error: I/O error, dev sda, sector 488901536
[  948.127623] ata1: EH complete
[  952.168776] ata1.00: exception Emask 0x0 SAct 0x40 SErr 0x50000 action 0x0
[  952.168798] ata1.00: irq_stat 0x40000008
[  952.168807] ata1: SError: { PHYRdyChg CommWake }
[  952.168816] ata1.00: failed command: READ FPDMA QUEUED
[  952.168834] ata1.00: cmd 60/08:30:a0:0b:24/00:00:1d:00:00/40 tag 6 ncq dma 4096 in
                        res 41/40:08:a0:0b:24/00:00:1d:00:00/6d Emask 0x409 (media error) <F>
[  952.168843] ata1.00: status: { DRDY ERR }
[  952.168849] ata1.00: error: { UNC }
[  952.168863] ata1: hard resetting link
 

seems like problem with reading of failed HDD bloks but how it relate to launch some of programm (moreower i reinstall them).

console terminator launch output:

 (terminator:1333): dbind-WARNING **: 14:14:18.741: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Ошибка шины (стек памяти сброшен на диск)

coredumpctl relate to terminator:

Sun 2018-05-06 14:16:13 +03    1433  1002   100   7 present   /usr/lib/at-spi-bus-launcher

[nolik@R2D2 GetItFreeService]$ coredumpctl info 1433
           PID: 1433 (at-spi-bus-laun)
           UID: 1002 (nolik)
           GID: 100 (users)
        Signal: 7 (BUS)
     Timestamp: Sun 2018-05-06 14:16:08 +03 (2min 9s ago)
  Command Line: /usr/lib/at-spi-bus-launcher
    Executable: /usr/lib/at-spi-bus-launcher
 Control Group: /user.slice/user-1002.slice/user@1002.service/at-spi-dbus-bus.service
          Unit: user@1002.service
     User Unit: at-spi-dbus-bus.service
         Slice: user-1002.slice
     Owner UID: 1002 (nolik)
       Boot ID: 43399cbd171e4e0f806265ff2b524453
    Machine ID: 7722fbcff55c4d2ca3853b63790eac1f
      Hostname: R2D2
       Storage: /var/lib/systemd/coredump/core.at-spi-bus-laun.1002.43399cbd171e4e0f806265ff2b524453.1433.1525605368000000.lz4
       Message: Process 1433 (at-spi-bus-laun) of user 1002 dumped core.
                
                Stack trace of thread 1433:
                #0  0x00007f118bc3742a n/a (libdconfsettings.so)
                #1  0x00007f118bc3865e n/a (libdconfsettings.so)
                #2  0x00007f118bc37944 n/a (libdconfsettings.so)
                #3  0x00007f118bc38a19 n/a (libdconfsettings.so)
                #4  0x00007f118e262418 n/a (libgobject-2.0.so.0)
                #5  0x00007f118e264180 g_object_new_valist (libgobject-2.0.so.0)
                #6  0x00007f118e26450a g_object_new (libgobject-2.0.so.0)
                #7  0x00005579e81c4de0 n/a (at-spi-bus-launcher)
                #8  0x00007f118e8629a7 __libc_start_main (libc.so.6)
                #9  0x00005579e81c4e9a n/a (at-spi-bus-launcher)
 

Offline

#8 2018-05-06 14:30:14

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

with firefox-developer-edition:
console output:

 [nolik@R2D2 GetItFreeService]$ firefox-developer-edition 
ExceptionHandler::GenerateDump cloned child 1806ExceptionHandler::WaitForContinueSignal waiting for continue signal...

ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Ошибка шины (стек памяти сброшен на диск)
[nolik@R2D2 GetItFreeService]$ Failed to open curl lib from binary, use libcurl.so instead

!Sic in both examples we got Ошибка шины (стек памяти сброшен на диск) => it's mean: Bus error (the memory stack is flushed to disk)

coredumpctl

PNS_12HelperThreadEEE5StartES2_ (libxul.so)
                #5  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #6  0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1750:
                #0  0x00007f1c97a84f09 syscall (libc.so.6)
                #1  0x00007f1c88bc065b epoll_wait (libxul.so)
                #2  0x00007f1c88bc2753 epoll_dispatch (libxul.so)
                #3  0x00007f1c88bc4f92 event_base_loop (libxul.so)
                #4  0x00007f1c88baca7e _ZN4base19MessagePumpLibevent3RunEPNS_11MessagePump8DelegateE (libxul.so)
                #5  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #6  0x00007f1c88bbaf2a _ZN4base6Thread10ThreadMainEv (libxul.so)
                #7  0x00007f1c88bac5ba _ZL10ThreadFuncPv (libxul.so)
                #8  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #9  0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1751:
                #0  0x00007f1c984fd3bb pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d76e _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS>
                #2  0x00007f1c88799fb7 _ZN11TimerThread3RunEv (libxul.so)
                #3  0x00007f1c88797c41 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1802:
                #0  0x00007f1c97a84f09 syscall (libc.so.6)
                #1  0x000055cf02b71bf9 _ZL9pages_mapPvm.constprop.110 (firefox)
                #2  0x000055cf02b74688 _ZL11chunk_allocmmbPb (firefox)
                #3  0x000055cf02b77c5e _ZN7arena_t8AllocRunEmbb (firefox)
                #4  0x000055cf02b795ed _ZN7arena_t16GetNonFullBinRunEP11arena_bin_t (firefox)
                #5  0x000055cf02b7a263 _ZN7arena_t6MallocEmb (firefox)
                #6  0x000055cf02b7a38e calloc (firefox)
                #7  0x00007f1c710ba364 n/a (libtasn1.so.6)
                #8  0x00007f1c710b7652 n/a (libtasn1.so.6)
                #9  0x00007f1c710b6bf4 asn1_der_decoding2 (libtasn1.so.6)
                #10 0x00007f1c710b6c48 asn1_der_decoding (libtasn1.so.6)
                #11 0x00007f1c712dd149 n/a (libnssckbi.so)
                #12 0x00007f1c712cd195 n/a (libnssckbi.so)
                #13 0x00007f1c712cdef1 n/a (libnssckbi.so)
                #14 0x00007f1c712ccb8d n/a (libnssckbi.so)
                #15 0x00007f1c712cfc16 n/a (libnssckbi.so)
                #16 0x00007f1c712d2568 n/a (libnssckbi.so)
                #17 0x00007f1c712d334a n/a (libnssckbi.so)
                #18 0x00007f1c712d3997 n/a (libnssckbi.so)
                #19 0x00007f1c712d3c89 n/a (libnssckbi.so)
                #20 0x00007f1c712db8b8 n/a (libnssckbi.so)
                #21 0x00007f1c712db9b6 n/a (libnssckbi.so)
                #22 0x00007f1c712dbb5a n/a (libnssckbi.so)
                #23 0x00007f1c712dc56c n/a (libnssckbi.so)
                #24 0x00007f1c712d7756 n/a (libnssckbi.so)
                #25 0x00007f1c987a3b82 pk11_FindObjectByTemplate (/usr/lib/firefox-developer-edition/libnss3.so)
                #26 0x00007f1c987b18ce PK11_InitSlot (/usr/lib/firefox-developer-edition/libnss3.so)
                #27 0x00007f1c98799965 secmod_LoadPKCS11Module (/usr/lib/firefox-developer-edition/libnss3.so)
                #28 0x00007f1c987a67a6 SECMOD_LoadModule (/usr/lib/firefox-developer-edition/libnss3.so)
                #29 0x00007f1c987a699a SECMOD_LoadUserModule (/usr/lib/firefox-developer-edition/libnss3.so)
                #30 0x00007f1c886f96ab _ZN7mozilla3psm17LoadLoadableRootsERK9nsTStringIcES4_ (libxul.so)
                #31 0x00007f1c8b5561b0 _ZN21LoadLoadableRootsTask17LoadLoadableRootsEv (libxul.so)
                #32 0x00007f1c8b5565bc _ZN21LoadLoadableRootsTask3RunEv (libxul.so)
                #33 0x00007f1c88797c41 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #34 0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #35 0x00007f1c88bd9f7a _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #36 0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #37 0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #38 0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #39 0x00007f1c984f70bc start_thread (libpthread.so.0)
                #40 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1795:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d548 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox)
                #2  0x00007f1c889f4383 _ZN7mozilla3net13CacheIOThread10ThreadFuncEv (libxul.so)
                #3  0x00007f1c889f440f _ZN7mozilla3net13CacheIOThread10ThreadFuncEPv (libxul.so)
                #4  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #5  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #6  0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1753:
                #0  0x00007f1c97a7fcd9 __poll (libc.so.6)
                #1  0x00007f1c988e7b02 _pr_poll_with_poll (/usr/lib/firefox-developer-edition/libnspr4.so)
                #2  0x00007f1c888488b6 _ZN7mozilla3net24nsSocketTransportService4PollEPNS_16BaseTimeDurationINS_27TimeDurationValueC>
                #3  0x00007f1c888524d5 _ZN7mozilla3net24nsSocketTransportService15DoPollIterationEPNS_16BaseTimeDurationINS_27TimeDu>
                #4  0x00007f1c888528ac _ZN7mozilla3net24nsSocketTransportService3RunEv (libxul.so)
                #5  0x00007f1c88797c41 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #6  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #7  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #8  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #9  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #10 0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #11 0x00007f1c984f70bc start_thread (libpthread.so.0)
                #12 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1796:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d548 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox)
                #2  0x00007f1c8879064b _ZN7mozilla16ThreadEventQueueINS_10EventQueueEE8GetEventEbPNS_13EventPriorityE (libxul.so)
                #3  0x00007f1c88797bc9 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1793:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d548 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox)
                #2  0x00007f1c8879064b _ZN7mozilla16ThreadEventQueueINS_10EventQueueEE8GetEventEbPNS_13EventPriorityE (libxul.so)
                #3  0x00007f1c88797bc9 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1794:
                #0  0x00007f1c984fd3bb pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d76e _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS>
                #2  0x00007f1c8879e52a _ZN12nsThreadPool3RunEv (libxul.so)
                #3  0x00007f1c88797c41 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1788:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d548 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox)
                #2  0x00007f1c8879064b _ZN7mozilla16ThreadEventQueueINS_10EventQueueEE8GetEventEbPNS_13EventPriorityE (libxul.so)
                #3  0x00007f1c88797bc9 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1797:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x000055cf02b7d548 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (firefox)
                #2  0x00007f1c8879064b _ZN7mozilla16ThreadEventQueueINS_10EventQueueEE8GetEventEbPNS_13EventPriorityE (libxul.so)
                #3  0x00007f1c88797bc9 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #4  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #5  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #6  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #7  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #8  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #9  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #10 0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1752:
                #0  0x00007f1c97a7fcd9 __poll (libc.so.6)
                #1  0x00007f1c88b3637f _ZN20nsNotifyAddrListener3RunEv (libxul.so)
                #2  0x00007f1c88797c41 _ZN8nsThread16ProcessNextEventEbPb.part.257 (libxul.so)
                #3  0x00007f1c8879e958 _Z19NS_ProcessNextEventP9nsIThreadb (libxul.so)
                #4  0x00007f1c88bd9fba _ZN7mozilla3ipc28MessagePumpForNonMainThreads3RunEPN4base11MessagePump8DelegateE (libxul.so)
                #5  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #6  0x00007f1c88795b37 _ZN8nsThread10ThreadFuncEPv (libxul.so)
                #7  0x00007f1c988ecfc3 _pt_root (/usr/lib/firefox-developer-edition/libnspr4.so)
                #8  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #9  0x00007f1c97a8a2ff __clone (libc.so.6)
                
                Stack trace of thread 1785:
                #0  0x00007f1c984fd07c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                #1  0x00007f1c88bba1d0 _ZN4base13WaitableEvent9TimedWaitERKNS_9TimeDeltaE (libxul.so)
                #2  0x00007f1c88bba204 _ZN4base13WaitableEvent4WaitEv (libxul.so)
                #3  0x00007f1c88bad628 _ZN4base18MessagePumpDefault3RunEPNS_11MessagePump8DelegateE (libxul.so)
                #4  0x00007f1c88baf150 _ZN11MessageLoop3RunEv (libxul.so)
                #5  0x00007f1c88bbaf2a _ZN4base6Thread10ThreadMainEv (libxul.so)
                #6  0x00007f1c88bac5ba _ZL10ThreadFuncPv (libxul.so)
                #7  0x00007f1c984f70bc start_thread (libpthread.so.0)
                #8  0x00007f1c97a8a2ff __clone (libc.so.6)

Offline

#9 2018-05-06 14:54:53

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 5,258

Re: Problem with launching a programms after updating linux

If your harddisk is starting to fail this will have all sorts of wide reaching correlations. Back up what you can immediately. Run a SMART test and post the -a results after the mentioned time elapses.

But I don't have much hope of that coming out positive

Offline

#10 2018-05-06 15:01:19

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

V1del wrote:

If your harddisk is starting to fail this will have all sorts of wide reaching correlations. Back up what you can immediately. Run a SMART test and post the -a results after the mentioned time elapses.

But I don't have much hope of that coming out positive

But how it relate to the fact that  all works ok if i will downgrade my linux version to 4.16.2-2-ARCH?

Last edited by Igar_tigar (2018-05-06 15:01:40)

Offline

#11 2018-05-06 15:39:48

loqs
Member
Registered: 2014-03-06
Posts: 5,826

Re: Problem with launching a programms after updating linux

Can you determine which kernel the issue started with between 4.16.2-2 and 4.16.6-1?  You can obtain kernel versions you do not have cached from the ALA.
Running a SMART test / checking the SMART status of devices will rule out a possibility.

Offline

#12 2018-05-06 15:47:34

seth
Member
Registered: 2012-09-03
Posts: 8,201

Re: Problem with launching a programms after updating linux

It might be an unrelated problem, or a kernel bug or the newer kernel triggers some bad sectors.

In any case: YOU WANT TO BE SURE YOUR HDD IS OK and the stackpile of SIGBUS' plus the IO errors should scare the shit out of you.

Once you settled it's NOT the HDD, it's time to check on whether this might relate to drive power management, swap handling, a single bad block (does dmesg always point the same problematic sector?), ...

Offline

#13 2018-05-06 17:17:37

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

loqs wrote:

Can you determine which kernel the issue started with between 4.16.2-2 and 4.16.6-1?  You can obtain kernel versions you do not have cached from the ALA.
Running a SMART test / checking the SMART status of devices will rule out a possibility.

issue started from linux-4.16.3-1-x86_64.pkg.

later i will provide SMART test results (but idea that system depend on some HDD block on new version little bit confuse me).

Offline

#14 2018-05-06 18:44:16

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

Smart results (Too much info for me sad )

 smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.16.2-2-ARCH] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..75GSX
Device Model:     TOSHIBA MK5075GSX
Serial Number:    81MRD284B
LU WWN Device Id: 5 000039 37b289f9b
Firmware Version: GT001M
User Capacity:    500107862016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun May  6 18:43:22 2018 +03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 112)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 163) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2013
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       8938
  5 Reallocated_Sector_Ct   0x0033   061   061   050    Pre-fail  Always       -       15400
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   049   049   000    Old_age   Always       -       20771
 10 Spin_Retry_Count        0x0033   253   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       8802
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       277
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       441
193 Load_Cycle_Count        0x0032   075   075   000    Old_age   Always       -       255166
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       37 (Min/Max 13/65)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1028
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       976
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       8256
222 Loaded_Hours            0x0032   061   061   000    Old_age   Always       -       15728
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       311
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 20799 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 20799 occurred at disk power-on lifetime: 20771 hours (865 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 5a a0 0b 24 6d  Error: WP at LBA = 0x0d240ba0 = 220466080

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 60 78 81 45 40 00      01:55:26.546  WRITE FPDMA QUEUED
  60 10 58 a0 0b 24 40 00      01:55:23.756  READ FPDMA QUEUED
  60 88 50 08 44 22 40 00      01:55:23.756  READ FPDMA QUEUED
  60 20 48 98 40 22 40 00      01:55:23.741  READ FPDMA QUEUED
  60 e0 40 50 8c 08 40 00      01:55:23.734  READ FPDMA QUEUED

Error 20798 occurred at disk power-on lifetime: 20769 hours (865 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 ca a0 0b 24 6d  Error: UNC at LBA = 0x0d240ba0 = 220466080

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 e0 58 0d 44 40 00      00:00:48.071  READ FPDMA QUEUED
  60 18 d8 68 0a 29 40 00      00:00:48.071  READ FPDMA QUEUED
  61 40 d0 98 08 84 40 00      00:00:48.071  WRITE FPDMA QUEUED
  60 10 c8 a0 0b 24 40 00      00:00:46.581  READ FPDMA QUEUED
  60 08 c0 98 0b c1 40 00      00:00:46.562  READ FPDMA QUEUED

Error 20797 occurred at disk power-on lifetime: 20769 hours (865 days + 9 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 92 18 1f 24 6d  Error: WP at LBA = 0x0d241f18 = 220471064

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 98 00 b8 57 40 00      06:59:09.700  WRITE FPDMA QUEUED
  60 08 90 18 1f 24 40 00      06:59:09.556  READ FPDMA QUEUED
  60 08 88 60 0c c1 40 00      06:59:09.540  READ FPDMA QUEUED
  61 78 80 38 2a 84 40 00      06:59:09.538  WRITE FPDMA QUEUED
  61 00 78 00 b2 57 40 00      06:59:08.632  WRITE FPDMA QUEUED

Error 20796 occurred at disk power-on lifetime: 20768 hours (865 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 12 a0 0b 24 6d  Error: WP at LBA = 0x0d240ba0 = 220466080

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 38 18 98 08 84 40 00      06:52:05.822  WRITE FPDMA QUEUED
  60 10 10 a0 0b 24 40 00      06:52:05.318  READ FPDMA QUEUED
  60 20 08 00 48 93 40 00      06:52:05.318  READ FPDMA QUEUED
  60 08 00 98 0b c1 40 00      06:52:05.299  READ FPDMA QUEUED
  60 30 f0 90 0e c8 40 00      06:52:05.298  READ FPDMA QUEUED

Error 20795 occurred at disk power-on lifetime: 20768 hours (865 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 5a a0 0b 24 6d  Error: WP at LBA = 0x0d240ba0 = 220466080

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 60 b0 43 f3 40 00      06:39:53.717  WRITE FPDMA QUEUED
  60 08 58 a0 0b 24 40 00      06:39:53.717  READ FPDMA QUEUED
  60 00 50 30 f8 88 40 00      06:39:53.717  READ FPDMA QUEUED
  61 f8 48 80 83 84 40 00      06:39:53.717  WRITE FPDMA QUEUED
  61 08 40 00 0a 55 40 00      06:39:53.717  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       00%     20770         488296080
# 2  Short offline       Completed without error       00%         1         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Offline

#15 2018-05-06 18:48:41

loqs
Member
Registered: 2014-03-06
Posts: 5,826

Re: Problem with launching a programms after updating linux

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       00%     20770         488296080

The drive appears to have issues independent of any kernel issue.
Edit:
From 4.16.3 Release Notes

commit 80dc97f7e1e1b90ab62dc120ec9d09d69c8e03e8
Author: Bart Van Assche <bart.vanassche@wdc.com>
Date:   Thu Apr 5 10:32:59 2018 -0700

    Revert "scsi: core: return BLK_STS_OK for DID_OK in __scsi_error_from_host_byte()"
    
    commit cbe095e2b584623b882ebaf6c18e0b9077baa3f7 upstream.
    
    The description of commit e39a97353e53 is wrong: it mentions that commit
    2a842acab109 introduced a bug in __scsi_error_from_host_byte() although that
    commit did not change the behavior of that function.  Additionally, commit
    e39a97353e53 introduced a bug: it causes commands that fail with
    hostbyte=DID_OK and driverbyte=DRIVER_SENSE to be completed with
    BLK_STS_OK. Hence revert that commit.
    
    Fixes: e39a97353e53 ("scsi: core: return BLK_STS_OK for DID_OK in __scsi_error_from_host_byte()")
    Reported-by: Damien Le Moal <damien.lemoal@wdc.com>
    Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>
    Cc: Hannes Reinecke <hare@suse.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Damien Le Moal <damien.lemoal@wdc.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Lee Duncan <lduncan@suse.com>
    Cc: stable@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Hannes Reinecke <hare@suse.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Could explain why you were not seeing errors before 4.16.3

Last edited by loqs (2018-05-06 19:00:04)

Offline

#16 2018-05-06 18:51:30

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

loqs wrote:
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       00%     20770         488296080

The drive appears to have issues independent of any kernel issue.

suppose, yes, but now all works fine ¯\_(ツ)_/¯ despite of drive issue.

Offline

#17 2018-05-06 18:53:38

seth
Member
Registered: 2012-09-03
Posts: 8,201

Re: Problem with launching a programms after updating linux

  5 Reallocated_Sector_Ct   0x0033   061   061   050    Pre-fail  Always       -       15400
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1028
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       976
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       00%     20770         488296080

Before anything else, save all valuable data from that disk.
The get a life-disk system w/ maintainance focus (eg. grml) and run https://wiki.archlinux.org/index.php/Badblocks (you can go w/ the non-destructive test) to see whether this is an isolated error or the disk is toast.
Then you'll have to make up your mind about the further fate of the disk, but I would cease to "trust" it (though it might still be good as temporary media tank attached to your TV or so)

Offline

#18 2018-05-07 14:46:47

ua4000
Member
Registered: 2015-10-14
Posts: 110

Re: Problem with launching a programms after updating linux

220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       8256

Never seen before, had to google:
"Distance of the disk has shifted relative to the spindle. Incorrect disk spin can be cause by mechanical shock or high temperature."

Offline

#19 2018-06-12 18:37:15

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

issue, don't relate to hard disk. I suppose it's relate to dbus.

all time this dbus issue start after update with linux version >4.16.2-2.

although got a dbus error on Geany.

Offline

#20 2018-06-12 19:16:20

seth
Member
Registered: 2012-09-03
Posts: 8,201

Re: Problem with launching a programms after updating linux

DBUS is not related to the kernel, does not cause IO errors in dmesg and that disc is not reported as healthy by any stretch.
You're free to believe whatever you want, but the most likely explanation is that the inodes that hold some dbus binary or library are affected by the disc damage.

Offline

#21 2018-06-12 20:07:49

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

seth wrote:

DBUS is not related to the kernel, does not cause IO errors in dmesg and that disc is not reported as healthy by any stretch.
You're free to believe whatever you want, but the most likely explanation is that the inodes that hold some dbus binary or library are affected by the disc damage.

sure, i agree that my disc has a crashed blocks. But how it's explain that when i reverting to any linux package 4.16.2-2 or early, i didn't get any errors (related to Dbus) and problems with launch some of programs?

Offline

#22 2018-06-12 22:16:30

seth
Member
Registered: 2012-09-03
Posts: 8,201

Re: Problem with launching a programms after updating linux

Comment #15 suggested that there's been a bug in 4.16 that stashed I/O failures. With those failures being reported again w/ 4.16.3, you face coredumps rather than silent failures in the HW.

How does the LTS kernel behave?
What about some 4.15 kernel?

Offline

#23 2018-06-14 19:14:04

Igar_tigar
Member
Registered: 2018-02-18
Posts: 16

Re: Problem with launching a programms after updating linux

seth wrote:

Comment #15 suggested that there's been a bug in 4.16 that stashed I/O failures. With those failures being reported again w/ 4.16.3, you face coredumps rather than silent failures in the HW.

How does the LTS kernel behave?
What about some 4.15 kernel?

Possible u right.

I met same issue when installed linux-lts and 4.15-1.

Offline

Board footer

Powered by FluxBB