Bug 455026 - kwin crashes when closing the session with compositing enabled on an optimus freebsd system
Summary: kwin crashes when closing the session with compositing enabled on an optimus ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (other bugs)
Version First Reported In: 5.24.5
Platform: FreeBSD Ports FreeBSD
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-08 13:08 UTC by lamcilaktheo
Modified: 2022-07-08 04:36 UTC (History)
1 user (show)

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


Attachments
log (19.06 KB, text/plain)
2022-06-08 22:07 UTC, lamcilaktheo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lamcilaktheo 2022-06-08 13:08:42 UTC
STEPS TO REPRODUCE
1. install the nvidia hybrid drivers and kde plasma then enable compositing
2. close the session

OBSERVED RESULT
kwin crashes and disables the compositor

EXPECTED RESULT
the session should close without issues keeping the compositor

SOFTWARE/OS VERSIONS
FreeBSD 13.1
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
CPU : intel i7 8750h
GPU : NVIDIA GTX 1060
RAM : 16 gb ddr4

this is an optimus laptop (acer predator helios 300 PH315-51) so I use the nvidia-hybrid-graphics freebsd drivers which by default use the mesa intel UHD graphics 630

when it comes to debug log, I did try to obtain one but I'm getting this issue

seledreams-pc% gdb -pid $(pidof kwin_x11) -batch -ex "set logging file kwin_x11.gdb" -ex "set logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit"

Excess command line arguments ignored. (1913 ...)
1922: No such file or directory.
ptrace: Device busy.
The program is not being run.

so i'm not that sure about how I could send a more detailed log, I also did try the "send crash report" button after the kwin crash but then nothing happens
Comment 1 Nate Graham 2022-06-08 18:59:32 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!
Comment 2 lamcilaktheo 2022-06-08 19:02:03 UTC
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Can you please attach one? Thanks!

Hi,

I did check this page however the link provided in the freebsd section of this page is dead
Comment 3 Nate Graham 2022-06-08 19:28:22 UTC
Then I guess you'll need to find the FreeBSD-specific instructions yourself. And when you do, please edit the page to fix the link! It is a wiki, after all. :)
Comment 4 lamcilaktheo 2022-06-08 22:07:04 UTC
Created attachment 149561 [details]
log
Comment 5 lamcilaktheo 2022-06-08 22:09:02 UTC
While I'm still looking to get gdb working with kwin, I tried starting kwin from command line and get a log going

some things i noticed is that when it crashes it creates tons of zombie kwin_x11 processes that i can see in ksysguard, I also notice that when I start a session it always tends to start *two* kwin_x11 processes, and I don't get the crash when I make sure to kill one of the two kwin_x11 processes
Comment 6 Bug Janitor Service 2022-06-23 04:35:35 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 7 Bug Janitor Service 2022-07-08 04:36:50 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!