Bug 497495

Summary:	Crash at start
Product:	[Applications] Skanlite	Reporter:	lupe <lupeficara>
Component:	general	Assignee:	Kåre Särs <kare.sars>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	john.kizer
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	attachment-1365135-0.html

Description lupe 2024-12-15 10:44:52 UTC

SUMMARY


STEPS TO REPRODUCE
1. launch skanlite
2. search for available scanners
3. crash

OBSERVED RESULT

it crashed 5 time at start, a short pop up appears but impossible to read in time

EXPECTED RESULT
would like it to work

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 

ADDITIONAL INFORMATION

the report directly from skanlite don´t work, the collected infos are insufficient to submit

Comment 1 John Kizer 2024-12-27 07:04:27 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 lupe 2024-12-27 10:31:44 UTC

Created attachment 176901 [details]
attachment-1365135-0.html

Hi unfortunately when I tried to automatically report the bug from the
program itself directly, after the crash, I got a prompt informing me that
"it has been impossible to collect a proper back trace" , and so I reported
it manually.

That said, I couldn't reproduce it anymore

Le vendredi 27 décembre 2024, John Kizer <bugzilla_noreply@kde.org> a
écrit :

> https://bugs.kde.org/show_bug.cgi?id=497495
>
> John Kizer <john.kizer@proton.me> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>              Status|REPORTED                    |NEEDSINFO
>                  CC|                            |john.kizer@proton.me
>          Resolution|---                         |BACKTRACE
>
> --- Comment #1 from John Kizer <john.kizer@proton.me> ---
> 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!
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 3 John Kizer 2024-12-28 07:02:18 UTC

Thanks for the update! If the crash reoccurs, and a backtrace is able to be generated, please attach that here so it can be investigated - but hopefully for your sake the crash doesn't come back!

Comment 4 Bug Janitor Service 2025-01-12 03:47:44 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

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

Comment 5 Bug Janitor Service 2025-01-27 03:47:07 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.