Bug 474285

Summary:	Kate crashes on SQL reconnect
Product:	[Applications] kate	Reporter:	Vassilis Virvilis <vasvir>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	christoph, waqar.17a
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	22.12.3
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Vassilis Virvilis 2023-09-08 06:16:54 UTC

Application: kate (22.12.3)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.4.0-3-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.7 [KCrashBackend]

-- Information about the crash:
Sometimes when I hit the reconnect button to renew my database connection the plugin crashes and it takes Kate with it.

It does not happen everytime. I will test one or two things I have in my mind but for the bug to manifest the connection must have been expired. This rate limits my testing at one test per day.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f13b49b08ea in QSqlQuery::clear() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
#5  0x00007f13b49c2c88 in QSqlQueryModel::clear() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
#6  0x00007f13b4c9fd01 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so
#7  0x00007f13b4ca1a67 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so
#8  0x00007f13ccafba32 in QtPrivate::QSlotObjectBase::call (a=0x7ffed8521150, r=0x55926df63be0, this=0x55926e00a250) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate<false> (sender=0x55926df638e0, signal_index=5, argv=0x7ffed8521150) at kernel/qobject.cpp:3925
#10 0x00007f13b4c94075 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so
#11 0x00007f13b4c9c226 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so
#12 0x00007f13b4c960f4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesqlplugin.so
#13 0x00007f13ccafba32 in QtPrivate::QSlotObjectBase::call (a=0x7ffed85212c0, r=0x55926df63be0, this=0x55926dffb4e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate<false> (sender=0x55926dffb200, signal_index=4, argv=0x7ffed85212c0) at kernel/qobject.cpp:3925
#15 0x00007f13cd95c4d2 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f13cd95f12f in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007f13cda5661a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007f13cda56767 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f13cdb4f28a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f13cd9a4e18 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007f13cd962d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007f13cd96b1cd in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007f13ccac30d8 in QCoreApplication::notifyInternal2 (receiver=0x55926e002a50, event=0x7ffed8521850) at kernel/qcoreapplication.cpp:1064
#24 0x00007f13cd9694be in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x00007f13cd9bd96d in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x00007f13cd9c0cbf in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007f13cd962d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x00007f13ccac30d8 in QCoreApplication::notifyInternal2 (receiver=0x55926e186cc0, event=0x7ffed8521b00) at kernel/qcoreapplication.cpp:1064
#29 0x00007f13cd13ea6b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#30 0x00007f13cd112d5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#31 0x00007f13c6cfb8ba in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#32 0x00007f13ca9155b4 in g_main_dispatch (context=context@entry=0x7f13c0000ec0) at ../../../glib/gmain.c:3476
#33 0x00007f13ca918607 in g_main_context_dispatch_unlocked (context=0x7f13c0000ec0) at ../../../glib/gmain.c:4284
#34 g_main_context_iterate_unlocked (context=context@entry=0x7f13c0000ec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4349
#35 0x00007f13ca918bfc in g_main_context_iteration (context=0x7f13c0000ec0, may_block=1) at ../../../glib/gmain.c:4414
#36 0x00007f13ccb1c8d6 in QEventDispatcherGlib::processEvents (this=0x55926c3977c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#37 0x00007f13ccac1b7b in QEventLoop::exec (this=this@entry=0x7ffed8521e30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#38 0x00007f13ccaca020 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#39 0x000055926c269e33 in ?? ()
#40 0x00007f13cc2456ca in __libc_start_call_main (main=main@entry=0x55926c268fa0, argc=argc@entry=4, argv=argv@entry=0x7ffed8522398) at ../sysdeps/nptl/libc_start_call_main.h:58
#41 0x00007f13cc245785 in __libc_start_main_impl (main=0x55926c268fa0, argc=4, argv=0x7ffed8522398, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffed8522388) at ../csu/libc-start.c:360
#42 0x000055926c26ba91 in ?? ()
[Inferior 1 (process 2651955) detached]

Reported using DrKonqi

Comment 1 Christoph Cullmann 2024-10-20 18:30:46 UTC

Could you try this with the current 24.08 version?

Comment 2 Vassilis Virvilis 2024-10-20 18:44:53 UTC

Hi

I am currently in 23.0.8 and the bug is much more difficult to trigger. It was actually crashed 2-3 days after months of running a kate session.

I will update when debian unstable updates and report back here.

Given the chance I would like to give my compliments to whoever thought / implemented the SQL plugin. It is really a huge productivity booster for me since you can have your SQLs as notes in markdown files. Totally a great idea. Really hats of.

What takes some of the glow and makes it a bit more painful to use is the copy paste bug - but that's another bug https://bugs.kde.org/show_bug.cgi?id=461419

Comment 3 Christoph Cullmann 2024-10-20 19:22:08 UTC

Beside minimal fixes nothing happens with the plugin atm. Would be happy to get contributions:

https://kate-editor.org/join-us/

Comment 4 Bug Janitor Service 2024-11-04 03:46:20 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

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

Comment 5 Bug Janitor Service 2024-11-19 03:46:34 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.

Comment 6 Vassilis Virvilis 2024-11-19 08:15:28 UTC

I agree,

As I said the bug it is much more difficult to reproduce. It takes weeks if not months to actually crash Kate.

Comment 7 Waqar Ahmed 2024-11-19 08:19:20 UTC

ok, you can reopen it but please update the latest version with which you were able to reproduce the bug.

Also, would be great if you can share reproducible steps. I know its difficult, but it can help a lot. I just hope this is not a Qt bug

Comment 8 Vassilis Virvilis 2024-11-19 08:27:24 UTC

I am afraid I wasn't expressed clearly enough.

I said that I agree to close the bug because it does not crash every 2-3 days like it was when I reported at first.

Nowadays, It is very difficult to reproduce.

I had one crash after months of running Kate. It was SQL related but maybe not this bug, I can't tell since I didn't keep that backtrace.

So I think it is ok to close the bug until I find a way to semi-reliably reproduce it or at least get a newish backtrace if it happens again.

Leave it closed.

Thanks

Comment 9 Vassilis Virvilis 2025-09-11 10:01:06 UTC

It crashed again on reconnect - almost after a year.

I was surprised and failed to capture a meaningful backtrace. I had missing dbgsym packages because I am in a different system now.

I did the automatic report thing - not sure where it ends up.

I have now installed the missing packages  dbgsym.

If it happens again I will be ready.