Summary: | Typing = after certain phrases crashes krunner | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | afedotov861 |
Component: | calculator | Assignee: | Alexander Lohnau <alexander.lohnau> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.24.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | calculator runner gibberish |
Description
afedotov861
2022-05-21 06:51:09 UTC
Please attach a stacktrace and say which distro you yre running. If you don't have a DrKonqui notification, you can run "krunner --replace" on the terminal and see if there is any crash. Unfortunately, I am using Arch Linux, which makes it hard for me to generate a useful trace as it does not sanely distribute debug symbols. I did run krunner --replace inside a terminal, here is what i got: https://pastebin.com/VgYbywmb The crash happened on Line 8 and below, I just decided to include everything it wrote out for completeness. Meanwhile I will try to figure out how they want me to use debuginfod... Oh, and DrKonqui never showed when I crashed krunner after opening it from keyboard shortcut, and it only sometimes showed from krunner launched in a terminal by krunner --replace Thanks for the info! Does disabling the calculator runner fix the issue? There is another bug report about the calculator runner crashing, but I was not able to reproduce it with KDE Neon packages, qalculate master or the qaclculate version the bugreporter uses. Yes, disabling the calculator component of krunner does fix this issue. I figure it's trying to calculate on something invalid when = is typed. As in, parsing things it shouldn't be parsing. I'll soon attach a picture of something that supports my theory, although this time it doesn't crash but instead spits out gibberish. Created attachment 149055 [details]
calculator runner gibberish
Here, I've attached it
Interesting, on the qalc CLI I get
>> GNUPGHOME=
> error: "U" is not a valid variable/function/unit.
> error: "OME" is not a valid variable/function/unit.
> giganewton × (0 × poise) × gigahenry = 0 g²/(F·s)
Could you please file a separate bug report for the gibberish results?
|