Bug 472415 - KRunner crashed when I typed =
Summary: KRunner crashed when I typed =
Status: RESOLVED DUPLICATE of bug 470219
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.5
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-07-20 02:35 UTC by efoley92
Modified: 2023-07-20 16:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (73.35 KB, text/plain)
2023-07-20 02:35 UTC, efoley92 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description efoley92 2023-07-20 02:35:06 UTC 
Application: krunner (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-10-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I was going to use KRunner to calculate the square root of 21 but when I hit the equal key KRunner crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#4  0x00007efd57c55a60 in MathStructure::type() const () from /lib/x86_64-linux-gnu/libqalculate.so.22
#5  0x00007efd57c58b72 in MathStructure::MathStructure(MathStructure const&) () from /lib/x86_64-linux-gnu/libqalculate.so.22
#6  0x00007efd57bd6bf8 in CalculateThread::run() () from /lib/x86_64-linux-gnu/libqalculate.so.22
#7  0x00007efd57c6596f in Thread::doRun(void*) () from /lib/x86_64-linux-gnu/libqalculate.so.22
[...]
#11 0x00007efdafb0984e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi
Comment 1 efoley92 2023-07-20 02:35:08 UTC 
Created attachment 160403 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Fushan Wen 2023-07-20 16:30:19 UTC 

*** This bug has been marked as a duplicate of bug 470219 ***