Bug 462783 - Unknown Error Code 150 when launching Kate from app menu
Summary: Unknown Error Code 150 when launching Kate from app menu
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.08.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-08 14:34 UTC by Eric R
Modified: 2022-12-31 23:33 UTC (History)
2 users (show)

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


Attachments
Error dialog at Kate launch (21.09 KB, image/png)
2022-12-08 14:34 UTC, Eric R
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric R 2022-12-08 14:34:56 UTC
Created attachment 154428 [details]
Error dialog at Kate launch

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When I launch Kate from the Application Launcher, Kate shows me a dialog stating "Unknown error code 150 Bad parameters"

STEPS TO REPRODUCE
1. Launch Kate from Application Launcher
2. 
3. 

OBSERVED RESULT
Dialog box stating "Unknown error code 150 Bad parameters". See attachment.
After dismissing dialog, Kate seems to function normally.

EXPECTED RESULT
Kate launches without an error dialog

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.7
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz
Memory: 7.6 GiB of RAM
Graphics Processor: NVA8
Manufacturer: LENOVO
Product Name: 43142MU
System Version: ThinkPad T510

ADDITIONAL INFORMATION
Comment 1 Christoph Cullmann 2022-12-31 18:08:32 UTC
No idea what that should be, please try 22.12
Comment 2 Eric R 2022-12-31 23:33:54 UTC
(In reply to Christoph Cullmann from comment #1)
> No idea what that should be, please try 22.12

Ok, yup, works for me in 22.12, too! Thanks anyhow!