Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W
weston
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 273
    • Issues 273
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 120
    • Merge Requests 120
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #162

Closed
Open
Opened Nov 09, 2018 by Emil Velikov@evelikovReporter

Spawning Weston (+Xwayland) within tmux kills the X connection

This may be related to of #161.

Effectively starting Xwayland enabled weston in tmux kills the X connection and the following can be observed in dmesg:

weston[5588]: segfault at 7f3af2433d50 ip 00007f3af2433d50 sp 00007ffdc8fa9268 error 14 in libXdmcp.so.6.0.0

Note that the X session is still alive, although the connection itself is hosed. For example: $ pgrep Xserver | wc -l -> 1 while $ DISPLAY=:0 app fails

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/weston#162