[kwin] [Bug 464062] Absolute freeze after hibernation and standby
https://bugs.kde.org/show_bug.cgi?id=464062 tob...@g3ro.eu changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464062] Absolute freeze after hibernation and standby
https://bugs.kde.org/show_bug.cgi?id=464062 --- Comment #4 from tob...@g3ro.eu --- Created attachment 155241 --> https://bugs.kde.org/attachment.cgi?id=155241=edit gdb log directly after wakeup and re-login GDB log as requested, but it detached after some seconds and the "real" freeze happened one minute after that, so I don't know how useful it is. Sadly it is kind of impossible for me to know when the freeze will happen exactly, so all I could try is to restart this command until the freeze happens and hope that I catch the right moment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464062] Absolute freeze after hibernation and standby
https://bugs.kde.org/show_bug.cgi?id=464062 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- Please use: sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging on" -ex "set print thread-events off" -ex "thread apply all backtrace" -ex "quit" by telling it to continue, it won't get to the next step without an external trigger. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464062] Absolute freeze after hibernation and standby
https://bugs.kde.org/show_bug.cgi?id=464062 tob...@g3ro.eu changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from tob...@g3ro.eu --- (In reply to Nate Graham from comment #1) > You'll need to gdb kwin_wayland. Can you do that? Thanks! As I said: "I tried to debug with GDB (both Kwin and plasmashell), but the logs show nothing (empty)." This included kwin_wayland of course. The command I used is: sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file kwin_wayland.gdb" -ex "set logging on" -ex "set print thread-events off" -ex "continue" -ex "thread apply all backtrace" -ex "quit" It shows nothing, the log is empty. I tried that multiple times now and it does not show any errors on initialization, so GDB is working correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464062] Absolute freeze after hibernation and standby
https://bugs.kde.org/show_bug.cgi?id=464062 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version|unspecified |5.26.5 Component|general |wayland-generic Product|kde |kwin Resolution|--- |WAITINGFORINFO Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- You'll need to gdb kwin_wayland. Can you do that? Thanks! -- You are receiving this mail because: You are watching all bug changes.
