Contenu | Rechercher | Menus

Annonce

Ubuntu-fr vend de superbes t-shirts et de belles clés USB 32Go
Rendez-vous sur la boutique En Vente Libre

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 18/09/2019, à 15:40

Zwank

[RÉSOLU] Plantage Discover

Bonjour,

Très satisfait de ma récente installation de KDE Neon, sauf un petit souci avec discover qui plante dès que je veux ouvrir la liste des applications.
J'ai essayé le rapport de déboguage, en faisant tout ce qu'il me disait de faire.
Pour terminer il n'y avait pas assez d'informations.
J'ai pu enregister le rapport suivant :

Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee9490ee00 (LWP 1362))]

Thread 10 (Thread 0x7fee157fa700 (LWP 1416)):
#0  0x00007fee899f34a6 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fee899f4485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fee899f4721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fee89a1c195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fee8c2d66db in start_thread (arg=0x7fee157fa700) at pthread_create.c:463
#6  0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fee28e8b700 (LWP 1404)):
#0  0x00007fee8c2dc9f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x564482d1ffd0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x564482d1ff80, cond=0x564482d1ffa8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x564482d1ffa8, mutex=0x564482d1ff80) at pthread_cond_wait.c:655
#3  0x00007fee8fc52dbb in QWaitConditionPrivate::wait (deadline=..., this=0x564482d1ff80) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=<optimized out>, mutex=0x5644826b21f0, deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x00007fee8fc530c9 in QWaitCondition::wait (this=0x5644826b21f8, mutex=0x5644826b21f0, time=<optimized out>) at thread/qwaitcondition_unix.cpp:208
#6  0x00007fee932e96f8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fee932e9b2a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x5644826b2170) at thread/qthread_unix.cpp:361
#9  0x00007fee8c2d66db in start_thread (arg=0x7fee28e8b700) at pthread_create.c:463
#10 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fee2968c700 (LWP 1398)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007fee8fc4e354 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=<optimized out>, op=0, addr=<optimized out>) at thread/qfutex_p.h:92
#2  QtLinuxFutex::futexWait<QBasicAtomicInteger<unsigned int> > (expectedValue=<optimized out>, futex=...) at thread/qfutex_p.h:107
#3  futexSemaphoreTryAcquire_loop<false> (timeout=-1, nn=8589934593, curValue=<optimized out>, u=...) at thread/qsemaphore.cpp:219
#4  futexSemaphoreTryAcquire<false> (timeout=-1, n=n@entry=1, u=...) at thread/qsemaphore.cpp:262
#5  QSemaphore::acquire (this=this@entry=0x7fee2968ac50, n=n@entry=1) at thread/qsemaphore.cpp:326
#6  0x00007fee8fe54b10 in QMetaObject::activate (sender=0x564482e6f060, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3760
#7  0x00007fee906c0ca2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#8  0x00007fee906c1bfc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#9  0x00007fee8fe54875 in QMetaObject::activate (sender=0x7fee18004440, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3795
#10 0x00007fee906bfd62 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#11 0x00007fee9061102f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#12 0x00007fee9061284c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#13 0x00007fee8fe54875 in QMetaObject::activate (sender=0x7fee18068860, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3795
#14 0x00007fee90688382 in QSslSocket::preSharedKeyAuthenticationRequired(QSslPreSharedKeyAuthenticator*) () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#15 0x00007fee906aeefc in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#16 0x00007fee3ae06156 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#17 0x00007fee3ae042eb in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#18 0x00007fee3ae0e24e in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#19 0x00007fee3ae0d147 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#20 0x00007fee3adf94c4 in SSL_do_handshake () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#21 0x00007fee906af405 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#22 0x00007fee906af9d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#23 0x00007fee90689304 in QSslSocket::startClientEncryption() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#24 0x00007fee90689dc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#25 0x00007fee90691389 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#26 0x00007fee8fe54875 in QMetaObject::activate (sender=0x7fee18037b00, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3795
#27 0x00007fee9065a309 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#28 0x00007fee9065d1a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#29 0x00007fee9066d2dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#30 0x00007fee927e365c in QApplicationPrivate::notify_helper (this=this@entry=0x564480602680, receiver=receiver@entry=0x7fee180688e0, e=e@entry=0x7fee2968ba40) at kernel/qapplication.cpp:3736
#31 0x00007fee927eab90 in QApplication::notify (this=0x7ffcb6900250, receiver=0x7fee180688e0, e=0x7fee2968ba40) at kernel/qapplication.cpp:3483
#32 0x00007fee8fe24d18 in QCoreApplication::notifyInternal2 (receiver=0x7fee180688e0, event=0x7fee2968ba40) at kernel/qcoreapplication.cpp:1060
#33 0x00007fee8fe24eee in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7fee2968ba40) at kernel/qcoreapplication.cpp:1450
#34 0x00007fee8fe82a18 in socketNotifierSourceDispatch (source=0x7fee18001600) at kernel/qeventdispatcher_glib.cpp:106
#35 0x00007fee899f4417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007fee899f4650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007fee8fe81dcb in QEventDispatcherGlib::processEvents (this=0x7fee18000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#39 0x00007fee8fe2303a in QEventLoop::exec (this=this@entry=0x7fee2968bc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#40 0x00007fee8fc4a4ca in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#41 0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x564482e6f570) at thread/qthread_unix.cpp:361
#42 0x00007fee8c2d66db in start_thread (arg=0x7fee2968c700) at pthread_create.c:463
#43 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fee3adc0700 (LWP 1369)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007fee8fc4bf75 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=<optimized out>) at thread/qfutex_p.h:92
#2  QtLinuxFutex::futexWait<QBasicAtomicPointer<QMutexData> > (expectedValue=<optimized out>, futex=...) at thread/qfutex_p.h:107
#3  lockInternal_helper<false> (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142
#4  QBasicMutex::lockInternal (this=0x7fee9091c4e0) at thread/qmutex_linux.cpp:159
#5  0x00007fee906af1f0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#6  0x00007fee906af9d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#7  0x00007fee90689304 in QSslSocket::startClientEncryption() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#8  0x00007fee90689dc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#9  0x00007fee90691389 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#10 0x00007fee8fe54875 in QMetaObject::activate (sender=0x7fee2c0653c0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3795
#11 0x00007fee9065a309 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#12 0x00007fee9065d1a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#13 0x00007fee9066d2dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#14 0x00007fee927e365c in QApplicationPrivate::notify_helper (this=this@entry=0x564480602680, receiver=receiver@entry=0x7fee2c0c2da0, e=e@entry=0x7fee3adbfa40) at kernel/qapplication.cpp:3736
#15 0x00007fee927eab90 in QApplication::notify (this=0x7ffcb6900250, receiver=0x7fee2c0c2da0, e=0x7fee3adbfa40) at kernel/qapplication.cpp:3483
#16 0x00007fee8fe24d18 in QCoreApplication::notifyInternal2 (receiver=0x7fee2c0c2da0, event=0x7fee3adbfa40) at kernel/qcoreapplication.cpp:1060
#17 0x00007fee8fe24eee in QCoreApplication::sendEvent (receiver=<optimized out>, event=event@entry=0x7fee3adbfa40) at kernel/qcoreapplication.cpp:1450
#18 0x00007fee8fe82a18 in socketNotifierSourceDispatch (source=0x7fee2c001600) at kernel/qeventdispatcher_glib.cpp:106
#19 0x00007fee899f4417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fee899f4650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fee8fe81daf in QEventDispatcherGlib::processEvents (this=0x7fee2c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007fee8fe2303a in QEventLoop::exec (this=this@entry=0x7fee3adbfc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#24 0x00007fee8fc4a4ca in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#25 0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x564482fc80e0) at thread/qthread_unix.cpp:361
#26 0x00007fee8c2d66db in start_thread (arg=0x7fee3adc0700) at pthread_create.c:463
#27 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fee3c3b7700 (LWP 1368)):
#0  0x00007fee8f54ca66 in __libc_recv (fd=7, buf=0x7fee3400c9b8, len=8192, flags=0) at ../sysdeps/unix/sysv/linux/recv.c:28
#1  0x00007fee9065594c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#2  0x00007fee906460b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#3  0x00007fee90646904 in QNetworkInterface::allInterfaces() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#4  0x00007fee3b762766 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer/libqgenericbearer.so
#5  0x00007fee8fe35fb5 in QMetaMethod::invoke (this=this@entry=0x7fee3c3b62d0, object=object@entry=0x564480f03600, connectionType=Qt::DirectConnection, connectionType@entry=Qt::AutoConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2295
#6  0x00007fee8fe37f28 in QMetaObject::invokeMethod (obj=0x564480f03600, member=0x7fee906cee64 "requestUpdate", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1509
#7  0x00007fee906334fb in QNetworkConfigurationManagerPrivate::pollEngines() () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#8  0x00007fee906c3455 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#9  0x00007fee8fe54875 in QMetaObject::activate (sender=sender@entry=0x7fee3400c710, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fee3c3b68a0) at kernel/qobject.cpp:3795
#10 0x00007fee8fe54f47 in QMetaObject::activate (sender=sender@entry=0x7fee3400c710, m=m@entry=0x7fee902d1da0 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fee3c3b68a0) at kernel/qobject.cpp:3648
#11 0x00007fee8fe61757 in QTimer::timeout (this=this@entry=0x7fee3400c710, _t1=...) at .moc/moc_qtimer.cpp:204
#12 0x00007fee8fe61ab8 in QTimer::timerEvent (this=0x7fee3400c710, e=<optimized out>) at kernel/qtimer.cpp:255
#13 0x00007fee8fe5539b in QObject::event (this=0x7fee3400c710, e=<optimized out>) at kernel/qobject.cpp:1282
#14 0x00007fee8fe24d01 in doNotify (event=0x7fee3c3b6a10, receiver=0x7fee3400c710) at kernel/qcoreapplication.cpp:1150
#15 QCoreApplication::notify (event=<optimized out>, receiver=<optimized out>, this=<optimized out>) at kernel/qcoreapplication.cpp:1136
#16 QCoreApplication::notifyInternal2 (receiver=0x7fee3400c710, event=0x7fee3c3b6a10) at kernel/qcoreapplication.cpp:1060
#17 0x00007fee8fe81219 in QTimerInfoList::activateTimers (this=0x7fee340016d0) at kernel/qtimerinfo_unix.cpp:643
#18 0x00007fee8fe819e1 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182
#19 0x00007fee899f4417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fee899f4650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fee8fe81dcb in QEventDispatcherGlib::processEvents (this=0x7fee34000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x00007fee8fe2303a in QEventLoop::exec (this=this@entry=0x7fee3c3b6c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#24 0x00007fee8fc4a4ca in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#25 0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x5644812fc2e0) at thread/qthread_unix.cpp:361
#26 0x00007fee8c2d66db in start_thread (arg=0x7fee3c3b7700) at pthread_create.c:463
#27 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fee66c38700 (LWP 1367)):
#0  0x00007fee8c2dc9f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x564480968158) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x564480968108, cond=0x564480968130) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x564480968130, mutex=0x564480968108) at pthread_cond_wait.c:655
#3  0x00007fee674d20aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x00007fee674d1dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x00007fee8c2d66db in start_thread (arg=0x7fee66c38700) at pthread_create.c:463
#6  0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fee76545700 (LWP 1366)):
#0  _dl_update_slotinfo (req_modid=2) at ../elf/dl-tls.c:645
#1  0x00007fee9474487c in update_get_addr (ti=0x7fee902d3670) at ../elf/dl-tls.c:799
#2  0x00007fee9474aa28 in __tls_get_addr () at ../sysdeps/x86_64/tls_get_addr.S:55
#3  0x00007fee8fc4ac26 in get_thread_data () at thread/qthread_unix.cpp:184
#4  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:239
#5  0x00007fee8fe81caa in postEventSourcePrepare (s=0x7fee680047a0, timeout=0x7fee76544a74) at kernel/qeventdispatcher_glib.cpp:252
#6  0x00007fee899f3b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007fee899f44fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007fee8fe81dcb in QEventDispatcherGlib::processEvents (this=0x7fee68000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#10 0x00007fee8fe2303a in QEventLoop::exec (this=this@entry=0x7fee76544c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#11 0x00007fee8fc4a4ca in QThread::exec (this=this@entry=0x5644806c37c0) at thread/qthread.cpp:531
#12 0x00007fee90c35115 in QQmlThreadPrivate::run (this=0x5644806c37c0) at qml/ftw/qqmlthread.cpp:148
#13 0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x5644806c37c0) at thread/qthread_unix.cpp:361
#14 0x00007fee8c2d66db in start_thread (arg=0x7fee76545700) at pthread_create.c:463
#15 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fee77756700 (LWP 1365)):
#0  0x00007fee8f53a0b4 in __GI___libc_read (fd=7, buf=0x7fee77755a20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007fee89a392d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fee899f40b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fee899f4570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fee899f46dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fee8fe81dcb in QEventDispatcherGlib::processEvents (this=0x7fee70000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007fee8fe2303a in QEventLoop::exec (this=this@entry=0x7fee77755c30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x00007fee8fc4a4ca in QThread::exec (this=<optimized out>) at thread/qthread.cpp:531
#8  0x00007fee90fd3015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x7fee9124ad80) at thread/qthread_unix.cpp:361
#10 0x00007fee8c2d66db in start_thread (arg=0x7fee77756700) at pthread_create.c:463
#11 0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fee7f5f5700 (LWP 1364)):
#0  0x00007fee8f53ebf9 in __GI___poll (fds=0x7fee7f5f4b68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fee89129747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fee8912b36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fee821d5578 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007fee8fc4bc72 in QThreadPrivate::start (arg=0x5644806406f0) at thread/qthread_unix.cpp:361
#5  0x00007fee8c2d66db in start_thread (arg=0x7fee7f5f5700) at pthread_create.c:463
#6  0x00007fee8f54b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fee9490ee00 (LWP 1362)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007fee90a60215 in QV4::Object::get (receiver=0x7ffcb68fca38, hasProperty=0x0, name=0x7ffcb68fca40, this=0x7ffcb68fca38) at jsruntime/qv4object_p.h:308
#8  QV4::Lookup::getterProtoTwoClasses (l=<optimized out>, engine=<optimized out>, object=...) at jsruntime/qv4lookup.cpp:301
#9  0x00007fee657ab8ce in ?? ()
#10 0x0000000000000000 in ?? ()

Si cela inspire une âme généreuse et surtout compétente, je lui dis un grand MERCI.

Dernière modification par Zwank (Le 19/09/2019, à 14:11)

Hors ligne

#2 Le 19/09/2019, à 10:04

Zwank

Re : [RÉSOLU] Plantage Discover

Je viens d'essayer cela en suivant un fil en rapport avec segmantation fault :

zwank@zwank-System-Product-Name:~$ dpkg -l | grep discover
ii  avahi-utils                                   0.7-3.1ubuntu1.2                         amd64        Avahi browsing, publishing and discovery utilities
ii  discover                                      2.1.2-8                                  amd64        hardware identification system
ii  discover-data                                 2.2013.01.11                             all          Data lists for Discover hardware detection system
ii  libdiscover2                                  2.1.2-8                                  amd64        hardware identification library
ii  muon-updater                                  4:5.12.8-0ubuntu0.1                      all          Transitional package (muon-updater -> plasma-discover)
ii  plasma-discover                               5.16.5-0xneon+18.04+bionic+build54       amd64        Discover software management suite
ii  plasma-discover-backend-flatpak               5.16.5-0xneon+18.04+bionic+build54       amd64        Discover software management suite - Flatpak backend
ii  plasma-discover-backend-snap                  5.16.5-0xneon+18.04+bionic+build54       amd64        Discover software management suite - Snap backend
ii  plasma-discover-common                        5.16.5-0xneon+18.04+bionic+build54       all          Discover software manager suite (common data files)
ii  plasma-discover-dbgsym                        5.16.5-0xneon+18.04+bionic+build54       amd64        debug symbols for plasma-discover
zwank@zwank-System-Product-Name:~$ sudo apt-get update
[sudo] Mot de passe de zwank : 
Atteint :1 http://fr.archive.ubuntu.com/ubuntu bionic InRelease
Atteint :2 http://fr.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                           
Atteint :3 http://security.ubuntu.com/ubuntu bionic-security InRelease                                                            
Atteint :4 http://fr.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                         
Réception de :5 http://archive.neon.kde.org/user bionic InRelease [153 kB]                      
153 ko réceptionnés en 1s (240 ko/s)                          
Lecture des listes de paquets... Fait

Rien de passionnant à mon niveau...

???

Hors ligne

#3 Le 19/09/2019, à 12:41

abecidofugy

Re : [RÉSOLU] Plantage Discover

Salut,

Je te conseille de poser la question sur le sous-forum KDE neon de KDE.org : il y a les développeurs là-bas pour ton problème un peu pointu.

Sinon, essaie ça en attendant :
- ferme Discover
Tu fais :

pkcon refresh
pkcon update

Regarde dans Discover si ça a changé quelque chose.


Kubuntu et KDE neon 18.04 LTS en VM dans host Windows 10 (24 Go de ram) / Kubuntu en double-boot avec Win10 / Ubuntu 16.04 serveur sur machines dédiées.
Agence de communication en Alsace · web · print
Sur Riot : @patricius:matrix.org

Hors ligne

#4 Le 19/09/2019, à 13:20

Zwank

Re : [RÉSOLU] Plantage Discover

Sinon, essaie ça en attendant :
- ferme Discover
Tu fais :

pkcon refresh
pkcon update

Regarde dans Discover si ça a changé quelque chose.

zwank@zwank-System-Product-Name:~$ pkcon refresh
Actualisation du cache        [=========================]         
Chargement du cache           [=========================]         
Téléchargement des paquets  [=========================]         
Exécution                    [=========================]         
Terminé                      [=========================]         
 Activé                              http://fr.archive.ubuntu.com/ubuntu bionic InRelease
zwank@zwank-System-Product-Name:~$ pkcon update
Obtention des mises à jour   [=========================]         
Terminé                      [=========================]         
Chargement du cache           [=========================]         
Test des changements          [=========================]         
Terminé                      [=========================]         
Mise à jour des paquets      [=========================]         
Attente de l'authentification [=========================]          daemon
Chargement du cache           [=========================]         
Téléchargement des paquets  [=========================]         
Exécution                    [=========================]         
Installation des paquets      [=========================]         
Terminé                      [=========================] 

Et discover plante encore.
Et donc : Forum KDE.org
wink
Merci

Hors ligne

#5 Le 19/09/2019, à 14:11

Zwank

Re : [RÉSOLU] Plantage Discover

Réponse rapide sur le forum KDE :
" BUG -> https://bugs.kde.org/show_bug.cgi?id=411286 "
Je me suis inscrit sur the forum of the bugs (anglophone),
essayé de leur balancer mon bug, ou de lire les fils (en anglais).
No comment hmm
Au final, je résouds le problème à ma sauce très basique.
Je vire discover, qui ne me satisfaisait qu'à peine, et j'installe gnome-software.
Et on n'en parle plus... I hope so.

Hors ligne

#6 Le 19/09/2019, à 17:18

jajaX

Re : [RÉSOLU] Plantage Discover

salut,

j'ai eu aussi un plantage hier je crois. suis repassé en lgne de commande....


@+
jajaX
Asus X93SM-YZ065V sous KDE Neon
ASUS N53SN et HP dv7 2230f sous Kubuntu 18.04 Bionic Beaver (64 bits) / ACER Aspire 5612 WLMI sous Kubuntu 18.04 Bionic Beaver (32 bits)

Hors ligne

#7 Le 20/09/2019, à 05:48

abecidofugy

Re : [RÉSOLU] Plantage Discover

@Zwank : le désinstaller était un peu too much, non ? Cet outil ne cesse de s'améliorer, mais la ligne de commande, y'a que ça de vrai en effet ^^


Kubuntu et KDE neon 18.04 LTS en VM dans host Windows 10 (24 Go de ram) / Kubuntu en double-boot avec Win10 / Ubuntu 16.04 serveur sur machines dédiées.
Agence de communication en Alsace · web · print
Sur Riot : @patricius:matrix.org

Hors ligne

#8 Le 24/09/2019, à 14:54

LeCelt

Re : [RÉSOLU] Plantage Discover

Idem plantage dès que je le lance, j'ai fais les mises à jour en ligne de commande et depuis il fonctionne.

@+


Intel Core i7*4770 - RAM 16 Go - Carte graphique Nvidia GeForce GTX 670
Manjaro 18.04

Hors ligne

#9 Le 25/09/2019, à 17:12

Zwank

Re : [RÉSOLU] Plantage Discover

@abecidofugy : Tu me donnes des remords. Je viens de virer gnome-software qui ne me notifiait pas les mises à jour.
Je les faisais donc en ligne de commande comme tu me l'avais appris.;-)
J'ai réinstallé discover.
Il est nickel.

À bientôt

Hors ligne