Bug 471563

Summary: Discover crashes right after login.
Product: [Applications] Discover Reporter: mdrosenfeldt
Component: discoverAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aleixpol, fella, nate, needhelp0
Priority: NOR    
Version First Reported In: 5.27.6   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: drkonqi generated file containing description of the issue (unable to upload the report. Error: missing tokens)

Description mdrosenfeldt 2023-06-29 11:59:42 UTC
Created attachment 159971 [details]
drkonqi generated file containing description of the issue (unable to upload the report. Error: missing tokens)

SUMMARY
The application crashes when being the first app started right after system and user startup. Discover then starts normally
When filling the report through drKonqi (see attachment), report 469422 seems the most similar to what occurred to me.

STEPS TO REPRODUCE
1. Start the OS, login into the user account
2. Launch Discover form the kickoff launcher. 
3. Icon on the taskbar appears.
4. Crash occured

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Operating System: openSUSE Tumbleweed 20230624
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.9-1-default (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Processors: 4 × Intel® Core™ i3-6006U CPU @ 2.00GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Comment 1 Nate Graham 2023-09-14 19:19:54 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 2 Bug Janitor Service 2023-09-29 03:46:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-10-14 03:46:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!