Bug 488250 - Plasma crashed on opening FreeBSD 14.1
Summary: Plasma crashed on opening FreeBSD 14.1
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.27.11
Platform: FreeBSD Ports FreeBSD
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-06-09 09:52 UTC by Marc Perkins
Modified: 2024-07-12 03:47 UTC (History)
2 users (show)

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


Attachments
attachment-200772-0.html (2.12 KB, text/html)
2024-06-12 17:55 UTC, Marc Perkins
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Perkins 2024-06-09 09:52:39 UTC
Application: plasmashell (5.27.11)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: FreeBSD 14.1-RELEASE amd64
Windowing System: X11
Distribution (Platform): FreeBSD Ports
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
On boot KDE reported that Plasma had crashed.  I had done nothing different that prior boots, and this is a relatively fresh install of FreeBSD 14.1.  All I did was log in from sddm.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

(lldb) process attach --pid 78452
(lldb) settings set term-width 200
(lldb) thread info
(lldb) bt all

The reporter indicates this bug may be a duplicate of or related to bug 487662.

Reported using DrKonqi
Comment 1 Nate Graham 2024-06-10 17:47:51 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?
Comment 2 Marc Perkins 2024-06-12 17:55:22 UTC
Created attachment 170429 [details]
attachment-200772-0.html

Hei Nate,

Go ahead and delete this one.  I never got confirmation from KDE's bug
submitter that the bug went through, and ended up wiping the FreeBSD
install shortly afterwards due to too many issues.

Sorry for not being able to provide more information.

--Marc

On Mon, Jun 10, 2024 at 8:47 PM Nate Graham <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=488250
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |nate@kde.org
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |BACKTRACE
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> 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
> ?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Nate Graham 2024-06-12 18:25:23 UTC
Ok, sorry it wasn't a great experience. :/
Comment 4 Bug Janitor Service 2024-06-27 03:47:55 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 5 Bug Janitor Service 2024-07-12 03:47:19 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!