Bug 457037 - Can't click Next in "What do you know about the crash" dialog
Summary: Can't click Next in "What do you know about the crash" dialog
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-23 05:37 UTC by Dan Dascalescu
Modified: 2025-09-20 09:35 UTC (History)
4 users (show)

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


Attachments
Screencast (304.58 KB, image/gif)
2022-07-23 05:37 UTC, Dan Dascalescu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Dascalescu 2022-07-23 05:37:58 UTC
Created attachment 150843 [details]
Screencast

STEPS TO REPRODUCE
1. Crash Krusader
2. Go to the What Do You Know About the Crash" page of the dialog
3. Check Yes in "Do you remember..."
4. Click "Next"

OBSERVED RESULT
Nothing

EXPECTED RESULT
Report the bug

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.4.0-120-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8665U CPU @ 1.90GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
System Version: ThinkPad X1 Carbon 7th

ADDITIONAL INFORMATION
 This did work in the past. No idea what happened now.
Comment 1 Patrick Silva 2022-07-23 12:18:12 UTC
is qml-module-org-kde-syntaxhighlighting package installed on your system?
Possibly duplicate of bug 453224
Comment 2 Carlos De Maine 2025-09-20 09:35:59 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!