Bug 433524 - Absturz test
Summary: Absturz test
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Norbert Zawodsky
Keywords: drkonqi
Depends on:
Reported: 2021-02-24 08:19 UTC by Norbert Zawodsky
Modified: 2021-02-24 12:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Zawodsky 2021-02-24 08:19:28 UTC
Application: GrapeCashkde ()

Qt Version: 5.9.7
Frameworks Version: 5.55.0
Operating System: Linux 4.12.14-lp151.28.91-default x86_64
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
- What I was doing when the application crashed:
just started the application. then it crashed immediately.

-- Backtrace:
Application: GrapeCashkde (GrapeCashkde), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f14e1312506 in GcpL6Mgr::sendMessage(QByteArray const*) () at /home/norbert/prog/Grape/build/cash/server/api/libGrapeCashSrvComm.so
#7  0x00007f14e13112b1 in GcProcessor::getGcUserList(QList<GcUser>*) () at /home/norbert/prog/Grape/build/cash/server/api/libGrapeCashSrvComm.so
#8  0x0000000000415105 in GckMainWindow::doInit() ()
#9  0x00007f14de21fc05 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#10 0x00007f14de22c843 in  () at /usr/lib64/libQt5Core.so.5
#11 0x00007f14de22072b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#12 0x00007f14df2303dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#13 0x00007f14df237ca4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#14 0x00007f14de1f0fa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#15 0x00007f14de2494be in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#16 0x00007f14de249c81 in  () at /usr/lib64/libQt5Core.so.5
#17 0x00007f14d94b8e87 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f14d94b9230 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x00007f14d94b92bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#20 0x00007f14de24a01f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#21 0x00007f14de1eefda in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#22 0x00007f14de1f8084 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#23 0x0000000000413542 in main ()
[Inferior 1 (process 14018) detached]

Reported using DrKonqi
Comment 1 Alois Wohlschlager 2021-02-24 10:53:42 UTC
Sorry, I cannot find the application you have observed to crash. Where did you download it from?
Comment 2 Norbert Zawodsky 2021-02-24 11:59:11 UTC
Hi Alois,
This is my own application (I'm the programmer). I didn't use this program for some months now and tried again this morning. It crashed and to my surprise, drkonqi popped up. I thought, I'd give it a try to move on with drkonqi. It wasn't clear to me that drkonqi will automatically file a bug. I thought, it would only "inform" the developer in some way. Now I know better.

So this bugreport could simply be deleted. How could I do that? Just set the status to RESOLVED ?
Comment 3 Alois Wohlschlager 2021-02-24 12:02:56 UTC
Ok, so this is not a bug with any KDE app. I have set it to RESOLVED NOT A BUG. If you think that drkonqi was too eager to file a bug report for a crash of an unofficial application, this should probably be reported as a bug against drkonqi.