Bug 480755 - Kate crashed when setting recent items setting to 0
Summary: Kate crashed when setting recent items setting to 0
Status: RESOLVED DUPLICATE of bug 476312
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 23.04.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-02-03 00:10 UTC by ericswpark
Modified: 2024-02-03 16:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ericswpark 2024-02-03 00:10:25 UTC
Application: kate (23.04.2)

Qt Version: 5.15.9
Frameworks Version: 5.107.0
Operating System: Linux 6.1.52-valve9-1-neptune-61 x86_64
Windowing System: X11
Distribution: SteamOS
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
I set the recent items (how many recent items are shown) to 0, and then Kate immediately crashed when I clicked on "OK" to apply and save the setting.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x00007fcdfe928674 in ?? () from /usr/lib/libKF5ConfigWidgets.so.5
#5  0x00007fcdfe92a35f in KRecentFilesAction::setMaxItems(int) () from /usr/lib/libKF5ConfigWidgets.so.5
#6  0x00007fce00dafecf in ?? () from /usr/lib/libkateprivate.so.23.04.2
#7  0x00007fcdff8d01a3 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007fce0056bbb7 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5
#9  0x00007fce0057160b in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5
#10 0x00007fce006f3b4b in ?? () from /usr/lib/libQt5Widgets.so.5
#11 0x00007fce006f3c6d in ?? () from /usr/lib/libQt5Widgets.so.5
#12 0x00007fce005af1e1 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007fce0057893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#14 0x00007fce0057ddef in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#15 0x00007fcdff89ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#16 0x00007fce0057c12a in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /usr/lib/libQt5Widgets.so.5
#17 0x00007fce005cd9d4 in ?? () from /usr/lib/libQt5Widgets.so.5
#18 0x00007fce005cec27 in ?? () from /usr/lib/libQt5Widgets.so.5
#19 0x00007fce0057893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#20 0x00007fcdff89ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#21 0x00007fcdffd4121c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5
#22 0x00007fcdffd2a955 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#23 0x00007fcdf732f710 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#24 0x00007fcdfd110981 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007fcdfd16db39 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007fcdfd10e032 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007fcdff8e9f0c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#28 0x00007fcdff899824 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#29 0x00007fcdff89acc3 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#30 0x000055593a66b60e in ?? ()
#31 0x00007fcdff039850 in ?? () from /usr/lib/libc.so.6
#32 0x00007fcdff03990a in __libc_start_main () from /usr/lib/libc.so.6
#33 0x000055593a66dab5 in ?? ()
[Inferior 1 (process 43286) detached]

Reported using DrKonqi
Comment 1 Christoph Cullmann 2024-02-03 16:57:33 UTC
*** This bug has been marked as a duplicate of bug 476312 ***