[kwin] [Bug 457757] kwin_wayland crashed

2022-10-01 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=457757

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |WORKSFORME

--- Comment #10 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-09-16 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #9 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-09-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #8 from Nate Graham  ---
Whatever you did to get the backtrace of the plasmashell crash, do it again,
but for the kwin_wayland crash. `coredumpctl` can show them to you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-09-01 Thread dauntless
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #7 from dauntless 
<[email protected]> ---
And how do I get that? I just pasted a backtrace following the instructions in
the link into the pastebin in Comment 3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-09-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=457757

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|REPORTED|NEEDSINFO

--- Comment #6 from Nate Graham  ---
That log shows us a plasmashell crash. It's expected that plasmashell crashes
when kwin crashes; we need a log of the kwin_wayland crash.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-09-01 Thread dauntless
https://bugs.kde.org/show_bug.cgi?id=457757

dauntless <[email protected]> changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #5 from dauntless 
<[email protected]> ---
Log files posted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-08-30 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #4 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-08-16 Thread dauntless
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #3 from dauntless 
<[email protected]> ---
Got another crash shortly after login, here's the coredumpctl output:
https://pastebin.com/TPJSukRu

I would paste it in the comment here for searchability but the log is over the
~65k character limit.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-08-11 Thread dauntless
https://bugs.kde.org/show_bug.cgi?id=457757

--- Comment #2 from dauntless 
<[email protected]> ---
Ah, I see. I just tried now and I get "No coredumps found.", so I guess I'll
have to wait until it crashes again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 457757] kwin_wayland crashed

2022-08-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=457757

Nate Graham  changed:

   What|Removed |Added

Summary|Plasmashell crash after |kwin_wayland crashed
   |login   |
 Resolution|--- |BACKTRACE
   Assignee|[email protected] |[email protected]
 Status|REPORTED|NEEDSINFO
Version|master  |5.24.4
   Target Milestone|1.0 |---
  Component|generic-crash   |wayland-generic
 CC||[email protected]
Product|plasmashell |kwin

--- Comment #1 from Nate Graham  ---
> The Wayland connection broke. Did the Wayland compositor die

The crash log only tells us that KWin crashed; sadly it's a known and
unavoidable issue that when kwin_wayland crashes, all apps crash too (see
https://bugreports.qt.io/browse/QTBUG-85631). The app crash logs are not
useful; all they do is tell us that KWin crashed. But we need to know why KWin
crashed. For that, we need a backtrace of the KWin crash itself. You may be
able to retrieve it with `coredumpctl`. See
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 are watching all bug changes.