Bug 354418

Summary: Desktop sharing app crashed
Product: [Applications] krfb Reporter: Aled Hughes <kde>
Component: generalAssignee: George Goldberg <grundleborg>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Aled Hughes 2015-10-26 19:27:41 UTC
Application: krfb (4.14.7)
KDE Platform Version: 4.14.11
Qt Version: 4.8.6
Operating System: Linux 4.1.10-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:
I had used desktop sharing from a remote site using TightVNC. That was a few days ago, and when I came back to this PC I found this crash report. I don't recall anything actually going wrong during the remote session.

-- Backtrace:
Application: Desktop Sharing (krfb), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  __strstr_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:40
#7  0x00000037f3c4f110 in _gnutls_url_is_known (url=0x0) at gnutls_x509.c:1962
#8  0x00000037f3c4f189 in read_key_file (flags=0, pass=0x0, type=GNUTLS_X509_FMT_PEM, keyfile=0x0, res=0x2407a00) at gnutls_x509.c:847
#9  gnutls_certificate_set_x509_key_file2 (res=0x2407a00, certfile=0x0, keyfile=0x0, type=GNUTLS_X509_FMT_PEM, pass=0x0, flags=0) at gnutls_x509.c:1350
#10 0x00000037dfe17112 in rfbssl_init_global () from /lib64/libvncserver.so.0
#11 0x00000037dfe171cc in rfbssl_init () from /lib64/libvncserver.so.0
#12 0x00000037dfe1650a in webSocketsCheck () from /lib64/libvncserver.so.0
#13 0x00000037dfe0cef9 in rfbNewTCPOrUDPClient () from /lib64/libvncserver.so.0
#14 0x00000037dfe150c3 in rfbProcessNewConnection () from /lib64/libvncserver.so.0
#15 0x0000003468d9e0c0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4
#16 0x0000003468def48e in QSocketNotifier::activated(int) () from /lib64/libQtCore.so.4
#17 0x0000003468da87fb in QSocketNotifier::event(QEvent*) () from /lib64/libQtCore.so.4
#18 0x00000039a65c43ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#19 0x00000039a65cb206 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#20 0x00000039a7c5554a in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5
#21 0x0000003468d89f1d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4
#22 0x0000003468dbaac2 in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtCore.so.4
#23 0x0000003458a49a8a in g_main_dispatch (context=0x2296f40) at gmain.c:3122
#24 g_main_context_dispatch (context=context@entry=0x2296f40) at gmain.c:3737
#25 0x0000003458a49e20 in g_main_context_iterate (context=context@entry=0x2296f40, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#26 0x0000003458a49ecc in g_main_context_iteration (context=0x2296f40, may_block=1) at gmain.c:3869
#27 0x0000003468dba4ee in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#28 0x00000039a666a626 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
#29 0x0000003468d88791 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#30 0x0000003468d88b05 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#31 0x0000003468d8e6a9 in QCoreApplication::exec() () from /lib64/libQtCore.so.4
#32 0x000000000040e1f9 in main ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-31 04:14:22 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-15 10:56:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-30 04:08:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!