Bug 488738

Summary:	kalarm fail
Product:	[Applications] kalarm	Reporter:	Felipe fedinandec <freijoasfedinando>
Component:	general	Assignee:	David Jarvie <djarvie>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	danfrantes
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	attachment-1441645-0.html

Description Felipe fedinandec 2024-06-19 14:33:13 UTC

Application: kalarm (3.5.4.2 (KDE Gear 22.12.3))

Qt Version: 5.15.10
Frameworks Version: 5.115.0
Operating System: Linux 6.8.11-amd64 x86_64
Windowing System: X11
Distribution: Kali GNU/Linux Rolling
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
at opening kalarm from bash, it abruptly close ant it then showed the kde bug reporting bugzilla

The crash can be reproduced sometimes.

-- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault

[KCrash Handler]
#4  0x00007faede77c12f in ?? () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#5  0x00007faede7432f4 in KDirWatch::contains(QString const&) const () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#6  0x00007faedf588d64 in KSambaShare::~KSambaShare() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#7  0x00007faedf588dbd in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#8  0x00007faedd25aa16 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007faedd25ab4a in exit () from /lib/x86_64-linux-gnu/libc.so.6
#10 0x00007faedd927abc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007faedd927f83 in QCommandLineParser::process(QStringList const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000055a1e2147910 in ?? ()
#13 0x00007faeddb062b2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007faedf4d726b in KDBusService::activateRequested(QStringList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5DBusAddons.so.5
#15 0x00007faedf4d7802 in ?? () from /lib/x86_64-linux-gnu/libKF5DBusAddons.so.5
#16 0x00007faedf4e1e34 in ?? () from /lib/x86_64-linux-gnu/libKF5DBusAddons.so.5
#17 0x00007faede6888ab in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#18 0x00007faede68c320 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#19 0x00007faede68cdc9 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#20 0x00007faede68f04c in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#21 0x00007faeddaf9940 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007faede962f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007faeddacc748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007faeddacfe51 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007faeddb28697 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007faedbb0de3f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007faedbb0fec7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007faedbb104e0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007faeddb27d4a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x00007faeddacb0fb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007faeddad38a4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x000055a1e20959eb in ?? ()
#33 0x00007faedd242c8a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#34 0x00007faedd242d45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#35 0x000055a1e2096361 in ?? ()
[Inferior 1 (process 1911) detached]

Reported using DrKonqi

Comment 1 David Jarvie 2024-06-19 18:18:12 UTC

Unfortunately the crash trace does not contain any references to KAlarm code, so it is not possible to determine the cause without more information. It looks as if it crashes while in the initial stages of Qt/KDE application startup.

I notice that there is a reference to Samba in the trace, which I haven't seen before in a crash. Are you using Samba? If so, and if it is practical for you to temporarily disable it, does KAlarm still crash in this way without Samba being enabled?

Comment 2 Felipe fedinandec 2024-06-19 21:47:17 UTC

Created attachment 170654 [details]
attachment-1441645-0.html

For now it is working well again, if the issue happens again, i Will
disable samba as mentioned, Regards

El mié., 19 de junio de 2024 1:18 p. m., David Jarvie <
bugzilla_noreply@kde.org> escribió:

> https://bugs.kde.org/show_bug.cgi?id=488738
>
> --- Comment #1 from David Jarvie <djarvie@kde.org> ---
> Unfortunately the crash trace does not contain any references to KAlarm
> code,
> so it is not possible to determine the cause without more information. It
> looks
> as if it crashes while in the initial stages of Qt/KDE application startup.
>
> I notice that there is a reference to Samba in the trace, which I haven't
> seen
> before in a crash. Are you using Samba? If so, and if it is practical for
> you
> to temporarily disable it, does KAlarm still crash in this way without
> Samba
> being enabled?
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 3 daniel 2024-06-20 16:02:28 UTC

Hello,
did you try to reproduce this bug on rolling release distro,like arch or KDE neon?

Sometimes Kali does this weird things.

Greetings 
Daniel

Comment 4 David Jarvie 2024-07-08 18:14:46 UTC

The crash seemed to happen so early in program initialisation that it's doubtful that KAlarm was really the culprit, and since you say that it's working again, I'm closing this bug report. If it happens again, please reopen it.