https://bugs.kde.org/show_bug.cgi?id=494650
--- Comment #9 from Mark <mark.coet...@gmail.com> --- (In reply to Mark from comment #8) > (In reply to TraceyC from comment #7) > > Thinking about what you had described so far, you had said these scripts are > > in a subdirectory some levels below your home directory. Are all of the > > directories in between readable by your user? (As in, no root owned > > directories above the directory where the scripts are)? > > > > In regards to getting a good backtrace - if you have a Wayland session you > > won't have a process named "kwin", it will be "kwin_wayland". You can see > > the name of the kwin process in your current login session with > > > > pgrep -fla kwin > > > > if that doesn't work, try > > ps -ef |grep kwin) > > > > and then the number after your username is the pid > > Once you have that pid, use it to retrieve a backtrace with GDB > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > > How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB > > > > At this point I think gdb will be more useful than coredumpctl > > Okay, my apologies for the long delay; I am officially an ID10T > > I have subsequently reinstalled my system -- plasma 6.5.1(In reply to > TraceyC from comment #7) > > Thinking about what you had described so far, you had said these scripts are > > in a subdirectory some levels below your home directory. Are all of the > > directories in between readable by your user? (As in, no root owned > > directories above the directory where the scripts are)? > > > > In regards to getting a good backtrace - if you have a Wayland session you > > won't have a process named "kwin", it will be "kwin_wayland". You can see > > the name of the kwin process in your current login session with > > > > pgrep -fla kwin > > > > if that doesn't work, try > > ps -ef |grep kwin) > > > > and then the number after your username is the pid > > Once you have that pid, use it to retrieve a backtrace with GDB > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > > How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB > > > > At this point I think gdb will be more useful than coredumpctl > > Okay, I am officially an ID10T -- my apologies for the long delay, and for > wasting your time. > > In the interim, I reinstalled my system (Plasma 6.1.5 on Manjaro) and, this > morning, updated to Plasma 6.2.4 (on X11). > > I then caused my system to crash again, as before, before looking closer at > my 'Link to Application-, only to discover that I never specified that the > script should run in the terminal (Konsole). > > Upon specifying that the script should run in the terminal, it worked as > expected. > > Maybe it still qualifies as a bug since, if there's no direction that the > script should run in the terminal, my system crashes. > > Many thanks, and kind regards. > > Mark I just ran: echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope gdb -pid $(pidof kwin_x11) -batch -ex "set logging file kwin_x11.gdb" -ex "set logging enabled on" -ex "continue" -ex "thread apply all backtrace" -ex "quit" I then tried left clicking on a .sh file to open it, and selected 'execute', upon which my system froze again. I did this twice, and was rewarded with two files in my home directory, the content of which is the following: [Thread 0x7494d6ffe6c0 (LWP 2460) exited] [Thread 0x7494d67fd6c0 (LWP 2459) exited] [New Thread 0x7494d6ffe6c0 (LWP 2559)] [New Thread 0x7494d67fd6c0 (LWP 2560)] [Inferior 1 (process 1206) detached] [Thread 0x7494d67fd6c0 (LWP 2560) exited] [Thread 0x7494d6ffe6c0 (LWP 2559) exited] [New Thread 0x7494d67fd6c0 (LWP 2684)] [New Thread 0x7494d6ffe6c0 (LWP 2685)] [Thread 0x7494f766d6c0 (LWP 1313) exited] [Thread 0x74950e2ecf80 (LWP 1206) exited] [Thread 0x7494e2d796c0 (LWP 1330) exited] [Thread 0x74950bd5b6c0 (LWP 1231) exited] and [Inferior 1 (process 1212) detached] I ran ps -ef |grep kwin, and (gdb) kwin 11092, but kwin, Kwin, KWin, and KWIN were rejected as being 'undefined'.. I hope this helps.. Regards Mark -- You are receiving this mail because: You are watching all bug changes.
