https://bugs.kde.org/show_bug.cgi?id=427382

Méven Car <meve...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |meve...@gmail.com

--- Comment #4 from Méven Car <meve...@gmail.com> ---
(In reply to Peter L. Steger from comment #3)
> unfortunately I can not find kdelib5-dbg on my system:
> 
> sudo apt search kdelibs5-dbg  kde5libs-dbg  kdelib5-dbg  kde5lib-dbg  
> Sortierung... Fertig
> Volltextsuche... Fertig
> 
> I have the User-version not the Developer version installed. Which packages
> or ppa's do I have to install in order to get access to the debugging
> packages?

I believe the debug symbols are in the normal repository, the are postfixed by
-dbgsym for neon or ubuntu.

You probably want to install kwin-wayland-dbgsym , kwin-common-dbgsym or 
plasma-desktop-dbgsym

> 
> No crash-Dialog appears. Only one of the screens turns to black/white and
> the kwin-menu bars are not responding anymore.
> 
> The output of gdb does not give me further information either:
> 
> gdb kwin
> GNU gdb (Ubuntu 9.1-0ubuntu1) 9.1
> Copyright (C) 2020 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-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> 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"...
> Reading symbols from kwin...
> (No debugging symbols found in kwin)
> (gdb) thread apply all backtrace
> (gdb) 

Here you don't nothing. To use gdb you'd want next to launch the program using
"r" command (for run).
But in wayland you can't debug kwin_wayland from within the session or you lose
ALL keyboard input and will be forced a hard reboot.
> 
> For the restart of kwin I use the following (hotkey with script)
> 
> killall plasmashell
> plasmashell &
> 
> After this the system is responsible again, No (other) application is
> affected.

The process here does not affect kwin, plasmashell is an independent program,
handling the session UI, taskbar...
For wayland kwin program is kwin_wayland.
So it seems to me your bug relates to plasmashell.

You might want to reproduce your crash running beforehand :
sudo gdb -pid `pidof plasmashell` # to attach gdb to the running plasmashell
process
# then in the gdb console type "c" (for continue) and hit enter, this might
take a few seconds...

The next time plasmashell crashes you will get a back trace in the console.

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

Reply via email to