Created attachment 119834 [details] krfb-20190503-083309.kcrash Hi, krfb 19.4.0 crash report SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 5.0.10-1 (manjaro arm) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Application: Partage de bureau (krfb), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xffff9949e010 (LWP 820))] Thread 7 (Thread 0xffff8583b560 (LWP 920)): #0 0x0000ffff9cd4a7f0 in pthread_cond_wait@@GLIBC_2.17 () from /usr/lib/libpthread.so.0 #1 0x0000ffff8b4d3e5c in ?? () from /usr/lib/dri/swrast_dri.so #2 0x0000ffff8b4d3d6c in ?? () from /usr/lib/dri/swrast_dri.so #3 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #4 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 6 (Thread 0xffff8603c560 (LWP 919)): #0 0x0000ffff9cd4a7f0 in pthread_cond_wait@@GLIBC_2.17 () from /usr/lib/libpthread.so.0 #1 0x0000ffff8b4d3e5c in ?? () from /usr/lib/dri/swrast_dri.so #2 0x0000ffff8b4d3d6c in ?? () from /usr/lib/dri/swrast_dri.so #3 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #4 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 5 (Thread 0xffff8683d560 (LWP 918)): #0 0x0000ffff9cd4a7f0 in pthread_cond_wait@@GLIBC_2.17 () from /usr/lib/libpthread.so.0 #1 0x0000ffff8b4d3e5c in ?? () from /usr/lib/dri/swrast_dri.so #2 0x0000ffff8b4d3d6c in ?? () from /usr/lib/dri/swrast_dri.so #3 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #4 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 4 (Thread 0xffff8703e560 (LWP 917)): #0 0x0000ffff9cd4a7f0 in pthread_cond_wait@@GLIBC_2.17 () from /usr/lib/libpthread.so.0 #1 0x0000ffff8b4d3e5c in ?? () from /usr/lib/dri/swrast_dri.so #2 0x0000ffff8b4d3d6c in ?? () from /usr/lib/dri/swrast_dri.so #3 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #4 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 3 (Thread 0xffff93064560 (LWP 874)): #0 0x0000ffff9d373340 in read () from /usr/lib/libc.so.6 #1 0x0000ffff9bb4aa78 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x0000ffff9baf7ec0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x0000ffff9baf8428 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x0000ffff9baf8624 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x0000ffff9d8ec694 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #6 0x0000ffff9d883948 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #7 0x0000ffff9d688f54 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x0000ffff9d1c35ec in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x0000ffff9d68ac28 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #11 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 2 (Thread 0xffff98d05560 (LWP 857)): #0 0x0000ffff9d377780 in poll () from /usr/lib/libc.so.6 #1 0x0000ffff9d2812f0 in ?? () from /usr/lib/libxcb.so.1 #2 0x0000ffff9d283284 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x0000ffff99057908 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x0000ffff9d68ac28 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x0000ffff9cd4456c in start_thread () from /usr/lib/libpthread.so.0 #6 0x0000ffff9d38101c in thread_start () from /usr/lib/libc.so.6 Thread 1 (Thread 0xffff9949e010 (LWP 820)): [KCrash Handler] #6 0x0000ffff9c9664dc in ?? () from /usr/lib/libgnutls.so.30 #7 0x0000ffff9c93bc4c in ?? () from /usr/lib/libgnutls.so.30 #8 0x0000ffff9c928e9c in ?? () from /usr/lib/libgnutls.so.30 #9 0x0000ffff9c929194 in gnutls_certificate_set_x509_key_file2 () from /usr/lib/libgnutls.so.30 #10 0x0000ffff9ee87224 in rfbssl_init_global () from /usr/lib/libvncserver.so.1 #11 0x0000ffff9ee87320 in rfbssl_init () from /usr/lib/libvncserver.so.1 #12 0x0000ffff9ee9dc70 in webSocketsCheck () from /usr/lib/libvncserver.so.1 #13 0x0000ffff9ee6cdf4 in ?? () from /usr/lib/libvncserver.so.1 #14 0x0000ffff9ee76830 in ?? () from /usr/lib/libvncserver.so.1 #15 0x0000ffff9ee7698c in rfbProcessNewConnection () from /usr/lib/libvncserver.so.1 #16 0x0000ffff9d8b92ac in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x0000ffff9d8c729c in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #18 0x0000ffff9d8c77b0 in QSocketNotifier::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #19 0x0000ffff9e3867cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #20 0x0000ffff9e38f370 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x0000ffff9d885378 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #22 0x0000ffff9d8ed708 in ?? () from /usr/lib/libQt5Core.so.5 #23 0x0000ffff9baf8210 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0x0000ffff9baf8550 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0x0000ffff9baf8624 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0x0000ffff9d8ec674 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #27 0x0000ffff9d883948 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #28 0x0000ffff9d88d814 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #29 0x0000aaaad03acac0 in ?? () #30 0x0000ffff9d2cf2a4 in __libc_start_main () from /usr/lib/libc.so.6 #31 0x0000aaaad03acec4 in _start () Backtrace stopped: previous frame identical to this frame (corrupt stack?) [Inferior 1 (process 820) detached]
Manjaro arm? On what device, I'm curious? Looking at stack trace, seems similar to ones mentioned in 406660, 406834. Crash is deep inside libvncserver / gnutls, looks like manjaro builds libvncserver with gnutls and not with openssl, and it fails somewhere internally.
Created attachment 119861 [details] attachment-6906-0.html Hi, Thank you for your message. The device is an odroid c2. Ok, I'll report this bugg to manjaro. Le lun. 6 mai 2019 à 01:22, Alexey Min <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=407206 > > Alexey Min <alexey.min@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |alexey.min@gmail.com > > --- Comment #1 from Alexey Min <alexey.min@gmail.com> --- > Manjaro arm? On what device, I'm curious? > > Looking at stack trace, seems similar to ones mentioned in 406660, 406834. > Crash is deep inside libvncserver / gnutls, looks like manjaro builds > libvncserver with gnutls and not with openssl, and it fails somewhere > internally. > > -- > You are receiving this mail because: > You reported the bug.
You may also want report to gnutls. According to their changelogs they often fix crashes like that. And to make backtrace even more useful, get debug information. As I understand, if manjaro is a fork of Arch - follow this manual: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces . This is not so easy on arch, though... seems they don't have debuginfo packages ready.
Hi, I reported the bugs to gnutls and libvncserver.
*** Bug 407502 has been marked as a duplicate of this bug. ***
*** Bug 406660 has been marked as a duplicate of this bug. ***
Could you please add the links for the upstream tickets? The information added there by developers might be useful to decide if this is an krfb issue.
Created attachment 120257 [details] attachment-4777-0.html Hi, please find below the post let on the libvncserver github page ( I sent the same to gnutls, but no reply) https://github.com/LibVNC/libvncserver/issues/303 sorry, I maybe wrong... Le mar. 21 mai 2019 à 21:47, Christoph Feck <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=407206 > > --- Comment #7 from Christoph Feck <cfeck@kde.org> --- > Could you please add the links for the upstream tickets? The information > added > there by developers might be useful to decide if this is an krfb issue. > > -- > You are receiving this mail because: > You reported the bug.
Your issue 303 indeed looks like duplicate of libvncservers 219, stack trace is the same. After reading https://github.com/LibVNC/libvncserver/issues/219 it looks like the issue is not specific to krfb, x11vnc is also having it with combination of libvncserver + gnutls.
Thanks for the update; changing status.
Created attachment 120262 [details] attachment-12289-0.html you're welcome Le mer. 22 mai 2019 à 23:48, Christoph Feck <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=407206 > > Christoph Feck <cfeck@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |UPSTREAM > Status|REPORTED |RESOLVED > > --- Comment #10 from Christoph Feck <cfeck@kde.org> --- > Thanks for the update; changing status. > > -- > You are receiving this mail because: > You reported the bug.