Bug 372814 - Kate crashed after closing it (happend only once)
Summary: Kate crashed after closing it (happend only once)
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2016-11-22 22:52 UTC by Gregor Mi
Modified: 2018-10-28 03:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2016-11-22 22:52:22 UTC
Application: kate (16.08.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Open kate, use the git context menu (don't know if this is related to the crash), close kate. This crash appears.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f859703c780 (LWP 15946))]

Thread 2 (Thread 0x7f85887a7700 (LWP 15947)):
#0  0x00007f859170bccd in read () at /lib64/libc.so.6
#1  0x00007f858c304b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f858c2c3999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f858c2c3df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f858c2c3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f85923169cc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f85800008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#6  0x00007f85922c62db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f85887a6e20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x00007f859210bfca in QThread::exec() (this=this@entry=0x7f8592993d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507
#8  0x00007f859272ca25 in QDBusConnectionManager::run() (this=0x7f8592993d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#9  0x00007f85921107f9 in QThreadPrivate::start(void*) (arg=0x7f8592993d00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368
#10 0x00007f858e1370a4 in start_thread () at /lib64/libpthread.so.0
#11 0x00007f859171802d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f859703c780 (LWP 15946)):
[KCrash Handler]
#6  0x0000000003816b50 in  ()
#7  0x00007f857e8b315e in  () at /usr/lib64/libKF5Notifications.so.5
#8  0x00007f857e8b31f9 in  () at /usr/lib64/libKF5Notifications.so.5
#9  0x00007f85922eee35 in QObjectPrivate::deleteChildren() (this=this@entry=0x3049500) at kernel/qobject.cpp:1970
#10 0x00007f85922f83ae in QObject::~QObject() (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:1041
#11 0x00007f857e897029 in  () at /usr/lib64/libKF5Notifications.so.5
#12 0x00007f859166ab39 in __run_exit_handlers () at /lib64/libc.so.6
#13 0x00007f859166ab85 in  () at /lib64/libc.so.6
#14 0x00007f8591654b2c in __libc_start_main () at /lib64/libc.so.6
#15 0x0000000000448ef7 in _start ()

Reported using DrKonqi
Comment 1 Christoph Cullmann 2017-07-25 08:53:04 UTC
Sorry, can't reproduce. If you get some way to do so, please reopen .=)
Comment 2 Andrew Crouthamel 2018-09-28 02:37:48 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 set the bug status 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 Andrew Crouthamel 2018-10-28 03:31:20 UTC
Dear Bug Submitter,

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!