| Summary: | Use of TOR with Wayland results in unstable desktop environment. | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | panorain <pj.world> |
| Component: | xwayland | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | fanzhuyifan, pj.world |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
backtrace of kwin_wayland
My second attempt at providing kwin_wayland gdb backtrace. |
||
|
Description
panorain
2025-03-03 13:37:36 UTC
I did not remove: *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** I apologize, can you please remove this from the initial report? When your system freezes, could you use ctrl+alt+f3/f2 to switch to a VT (You may need to do ctrl + alt + SysRq, and R first), and check 1. Is any process using 100% of cpu? 2. Attach a gdb instance to kwin, and attach the outputs of `thread apply all backtrace full`? Thanks! (In reply to fanzhuyifan from comment #2) > When your system freezes, could you use ctrl+alt+f3/f2 to switch to a VT No, frozen solid, no VT available that way. > (You may need to do ctrl + alt + SysRq, and R first), and check I can try, I think not possible. > > 1. Is any process using 100% of cpu? Not prior to crash and how can this be shown after crash (top/htop etc)? > 2. Attach a gdb instance to kwin, and attach the outputs of `thread apply > all backtrace full`? > Ok, trying to do this suggestion ^. > Thanks! Here am new to this, I apologize but am trying thanks for response. Was able to SSH into remote host (affilcted machine) from a client machine. Then used 'tmux' on host and 'tmux a' on client (seems to work). Been reading > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_with_GDB Can you suggest a specific area to follow perhaps? :-> top | grep kwin 5163 panorain -2 0 3020188 350068 269816 S 1.982 2.143 10:13.40 kwin_wa+ :~> gdb kwin 5163 GNU gdb (GDB; openSUSE Tumbleweed) 15.2 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... kwin: No such file or directory. Attaching to process 5163 ptrace: Operation not permitted. /home/panorain/5163: No such file or directory. (gdb) I created a directory below: :~> pwd /home/panorain drwxr-xr-x. 1 panorain panorain 0 Mar 3 18:12 5163 passed '$ gdb kwin 5163' again and this now below: "/home/panorain/5163" is not a core dump: file format not recognized Seems some incorrect with steps I am doing? By chance can you offer advice to proceed better? I apologize for lack of knowledge here with this. -Greatest Hopes sshing into the frozen host is great! You would probably need to do `sudo -E gdb kwin_wayland -p <pid of process>`. Then press Ctrl-C, then run `set logging file ~/backtrace.txt` `set logging enabled on` and then `thread apply all backtrace full` Created attachment 179409 [details]
backtrace of kwin_wayland
After resume from suspend seems more likely of kwin_wayland freezing machine.
(In reply to panorain from comment #5) > Created attachment 179409 [details] > backtrace of kwin_wayland > > After resume from suspend seems more likely of kwin_wayland freezing machine. The backtrace seems to be from kwin_wayland_wrapper. Could you get a backtrace from kwin_wayland? Thanks Created attachment 179800 [details]
My second attempt at providing kwin_wayland gdb backtrace.
Please do let me know if this is in fact the correct kwin_wayland gdb backtrace information or not. Regards
🐛🧹 ⚠️ 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! (In reply to panorain from comment #7) > Created attachment 179800 [details] > My second attempt at providing kwin_wayland gdb backtrace. > > Please do let me know if this is in fact the correct kwin_wayland gdb > backtrace information or not. Regards Sorry for not getting back to this until now -- unfortunately the attached backtrace does not contain any kde code. Would you be able to try again using the instructions here? https://bugs.kde.org/show_bug.cgi?id=501005#c4 Thanks! (In reply to fanzhuyifan from comment #9) > (In reply to panorain from comment #7) > > Created attachment 179800 [details] > > My second attempt at providing kwin_wayland gdb backtrace. > > > > Please do let me know if this is in fact the correct kwin_wayland gdb > > backtrace information or not. Regards > > Sorry for not getting back to this until now -- unfortunately the attached > backtrace does not contain any kde code. Would you be able to try again > using the instructions here? https://bugs.kde.org/show_bug.cgi?id=501005#c4 > > Thanks! Hi, did I provide the wrong pid? -Greatest Hopes (In reply to panorain from comment #10) > (In reply to fanzhuyifan from comment #9) > > (In reply to panorain from comment #7) > > > Created attachment 179800 [details] > > > My second attempt at providing kwin_wayland gdb backtrace. > > > > > > Please do let me know if this is in fact the correct kwin_wayland gdb > > > backtrace information or not. Regards > > > > Sorry for not getting back to this until now -- unfortunately the attached > > backtrace does not contain any kde code. Would you be able to try again > > using the instructions here? https://bugs.kde.org/show_bug.cgi?id=501005#c4 > > > > Thanks! > > Hi, did I provide the wrong pid? > > -Greatest Hopes The backtrack contains > Thread 5 (Thread 0x7f7c44bfa6c0 (LWP 23594) "gdb worker"): Did you accidentally attach gdb to another gdb instance? 🐛🧹 ⚠️ 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! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |