Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
wayland
wayland
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 28
    • Merge Requests 28
  • 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
  • waylandwayland
  • Issues
  • #12

Closed
Open
Created May 25, 2018 by Bugzilla Migration User@bugzilla-migration

Make send overflow disconnect instead of abort

Submitted by Pekka Paalanen @pq

Assigned to Pekka Paalanen @pq

Link to original bug (#7947)

Description

Request sending functions do not return a code, so they have no way of failing gracefully. If the send buffer is full, libwayland-client attemps an automatic flush. If the flush fails, there is no place to store the request, so it aborts which crashes the whole program.

It would be more friendly to the program to just kill the Wayland connection instead. The program will notice the failure once it returns to its main loop, giving it a chance to save its work or even try reconnecting.

While at it, check that the server-side event sending functions do the same instead of aborting.

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