Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • xfwm4 xfwm4
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
  • Issues 362
    • Issues 362
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 41
    • Merge requests 41
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • XfceXfce
  • xfwm4xfwm4
  • Issues
  • #405
Closed
Open
Issue created Jul 10, 2020 by Stéphane Gourichon@stephane.gourichon

xfwm4 killed with SIGTRAP from glib in clientSendConfigureNotify client.c:699 calling XSendEvent().

Summary

xfwm4 killed with SIGTRAP from glib in clientSendConfigureNotify client.c:699 calling XSendEvent().

Context

  • Xubuntu 20.04, up-to-date, no heavy configuration tweaking or special software installed, no PPA (initially). Machine seems sane, no mysterious crashes.

Path followed

  • xfwm4 crashes (and is automatically restarted) about once a week. (By the way, after xfwm4 restart, all windows get moved to the right and bottom by the thickness of left and top decorations in the style used.)
  • I logged in on /dev/tty1 and there started gdb which ran fxwm4 --replace.
  • Installed Ubuntu PPA for dbgsym packages and xfwm4-dbgsym.
  • This time, crash happened after machine (a laptop) woke from suspend-to-ram. Other crash conditions exist.
  • X session was reachable but could not focus any window, so I guessed xfwm4 was frozen.
  • Indeed on /dev/tty1 gdb was available. Captured stack trace and core dump.
  • Stack trace is attached: gdb_xfwm4_02_bt.txt
  • Core dump available, just ask.
Assignee
Assign to
Time tracking