Bug 361462

Summary: KLauncher crash in xcb_disconnect()
Product: [Frameworks and Libraries] frameworks-kinit Reporter: RJ <ogldelphi>
Component: generalAssignee: Martin Flöser <mgraesslin>
Status: RESOLVED WORKSFORME    
Severity: crash CC: faure, kdelibs-bugs-null, ogldelphi
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description RJ 2016-04-06 16:09:42 UTC 
Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#5  0xb693bf96 in free () from /lib/libc.so.6
#6  0xb751f557 in xcb_disconnect (c=0x976e388) at xcb_conn.c:356
#7  0xb3bc5137 in KLauncher::close (this=0x9713a00) at /usr/src/debug/kinit-5.20.0/src/klauncher/klauncher.cpp:192
#8  0xb3bc51c2 in KLauncher::destruct (this=0x9713a00) at /usr/src/debug/kinit-5.20.0/src/klauncher/klauncher.cpp:204
#9  0xb3bca154 in KLauncher::slotKDEInitData (this=0x9713a00) at /usr/src/debug/kinit-5.20.0/src/klauncher/klauncher.cpp:281
#10 0xb3bd154b in KLauncher::qt_static_metacall (_o=0x9713a00, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfb43008) at /usr/src/debug/kinit-5.20.0/build/src/klauncher/moc_klauncher.cpp:132
#11 0xb6d0ab01 in QMetaObject::activate (sender=0x9713fb8, signalOffset=3, local_signal_index=0, argv=0xbfb43008) at kernel/qobject.cpp:3713
#12 0xb6d0affd in QMetaObject::activate (sender=0x9713fb8, m=0xb6f45474 <QSocketNotifier::staticMetaObject>, local_signal_index=0, argv=0xbfb43008) at kernel/qobject.cpp:3578
#13 0xb6d89635 in QSocketNotifier::activated (this=0x9713fb8, _t1=8) at .moc/moc_qsocketnotifier.cpp:134
#14 0xb6d169d9 in QSocketNotifier::event (this=0x9713fb8, e=0xbfb43174) at kernel/qsocketnotifier.cpp:260
#15 0xb6cdc07c in QCoreApplicationPrivate::notify_helper (this=0x96c49a0, receiver=0x9713fb8, event=0xbfb43174) at kernel/qcoreapplication.cpp:1093
#16 0xb6cdc0dc in QCoreApplication::notify (this=0xbfb43460, receiver=0x9713fb8, event=0xbfb43174) at kernel/qcoreapplication.cpp:1038
#17 0xb700b6fa in QGuiApplication::notify (this=0xbfb43460, object=0x9713fb8, event=0xbfb43174) at kernel/qguiapplication.cpp:1538
#18 0xb6cdc1ef in QCoreApplication::notifyInternal (this=0xbfb43460, receiver=0x9713fb8, event=0xbfb43174) at kernel/qcoreapplication.cpp:965
#19 0xb6d2ea70 in QCoreApplication::sendEvent (event=0xbfb43174, receiver=<optimized out>) at kernel/qcoreapplication.h:224
#20 QEventDispatcherUNIX::activateSocketNotifiers (this=0x970aaf8) at kernel/qeventdispatcher_unix.cpp:565
#21 0xb6d2ecc6 in QEventDispatcherUNIXPrivate::doSelect (this=0x970abe8, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:264
#22 0xb6d2f065 in QEventDispatcherUNIX::processEvents (this=0x970aaf8, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#23 0xb2c8f7ff in QUnixEventDispatcherQPA::processEvents (this=0x970aaf8, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:62
#24 0xb6cd94c3 in QEventLoop::processEvents (this=0xbfb433cc, flags=...) at kernel/qeventloop.cpp:128
#25 0xb6cd98fa in QEventLoop::exec (this=0xbfb433cc, flags=...) at kernel/qeventloop.cpp:204
#26 0xb6ce1aaa in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#27 0xb70066d1 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1529
#28 0xb3bcf2d7 in kdemain (argc=2, argv=0x96b88c0) at /usr/src/debug/kinit-5.20.0/src/klauncher/klauncher_main.cpp:219
#29 0x0804f74e in launch (argc=argc@entry=2, _name=_name@entry=0x8052427 "klauncher", args=<optimized out>, args@entry=0xbfb4378c "--fd=8", cwd=0x0, envc=0, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8052473 "0") at /usr/src/debug/kinit-5.20.0/src/kdeinit/kinit.cpp:744
#30 0x080507f5 in start_klauncher () at /usr/src/debug/kinit-5.20.0/src/kdeinit/kinit.cpp:1032
#31 0x0804c8d5 in main (argc=2, argv=0xbfb43a04) at /usr/src/debug/kinit-5.20.0/src/kdeinit/kinit.cpp:1791

Reproducible: Didn't try
Comment 1 Martin Flöser 2016-04-11 05:43:58 UTC 
Could you please provide some information on what you did to get this crash?
Comment 2 RJ 2016-11-04 17:07:06 UTC 
(In reply to Martin Gräßlin from comment #1)
> Could you please provide some information on what you did to get this crash?

Sorry, I don't know.
Comment 3 Justin Zobel 2020-12-17 05:23:59 UTC 
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 4 Bug Janitor Service 2021-01-01 04:35:29 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 5 Bug Janitor Service 2021-01-16 04:34:40 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!