Bug 358132

Summary: Crash while using X2GO
Product: [Applications] kmix Reporter: oliver
Component: generalAssignee: Christian Esken <esken>
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 oliver 2016-01-17 15:58:10 UTC
Application: kmix (4.6RC1)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:
- What I was doing when the application crashed:

Logging in remotely with x2go, the application crashed. It was probably x2go.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbefc1d2900 (LWP 27596))]

Thread 2 (Thread 0x7fbedbb08700 (LWP 27598)):
#0  0x00007fbef3aca2fd in poll () from /lib64/libc.so.6
#1  0x00007fbef0ea9182 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007fbef0eaac77 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007fbedeab8da9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5
#4  0x00007fbef53633de in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#5  0x00007fbef1625555 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fbef3ad5b9d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fbefc1d2900 (LWP 27596)):
[KCrash Handler]
#5  0x00007fbedeac955c in QXcbScreen::mapFromNative(QPoint const&) const () from /lib64/libQt5XcbQpa.so.5
#6  0x00007fbedead19ba in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) () from /lib64/libQt5XcbQpa.so.5
#7  0x00007fbedeabaafd in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib64/libQt5XcbQpa.so.5
#8  0x00007fbedeabb433 in QXcbConnection::processXcbEvents() () from /lib64/libQt5XcbQpa.so.5
#9  0x00007fbef5574161 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007fbef66e341c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007fbef66e88e6 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007fbef554473b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007fbef5546b36 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#14 0x00007fbef559aaa3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#15 0x00007fbef488fa8a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x00007fbef488fe20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#17 0x00007fbef488fecc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007fbef559aeaf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007fbef5541eca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007fbef5549fac in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#21 0x00007fbefbdd3962 in kdemain () from /lib64/libkdeinit5_kmix.so
#22 0x00007fbef39f3700 in __libc_start_main () from /lib64/libc.so.6
#23 0x0000000000400ac9 in _start ()

Possible duplicates by query: bug 355585.

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-11-01 13:45:17 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-16 11:38:11 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 oliver 2018-11-16 11:57:17 UTC
(In reply to Andrew Crouthamel from comment #1)
> 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!

I have not seen this bug happen in a long time.