[PR #264] [MERGED] Small fixes for docker-compose up command's error and warning #4028

Closed
opened 2026-03-23 21:35:58 +00:00 by mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/AppFlowy-IO/AppFlowy/pull/264
Author: @texhno
Created: 1/20/2022
Status: Merged
Merged: 8/3/2022
Merged by: @appflowy

Base: mainHead: main


📝 Commits (2)

  • 7a197df fix: Fixes docker-compose up error and warning
  • 32ee068 chore: resolve docker-compose.yml conflicts

📊 Changes

1 file changed (+13 additions, -2 deletions)

View changed files

📝 frontend/scripts/docker-buildfiles/docker-compose.yml (+13 -2)

📄 Description

When I run docker-compose up command I'm getting the following error:

app_1  | (app_flowy:1): dbind-WARNING **: 20:06:32.776: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
app_1  | libGL error: MESA-LOADER: failed to retrieve device information
app_1  | [xcb] Unknown sequence number while processing queue
app_1  | [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
app_1  | [xcb] Aborting, sorry about that.
app_1  | app_flowy: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
appflowy_app_1 exited with code 139

I searched on the Internet and found some solutions, feel free to use them if you consider them useful.

Lines below are fixing the libGL error: MESA-LOADER: failed to retrieve device information and following [xcb] messages

devices:
      - "/dev/dri:/dev/dri"  # fixes MESA-LOADER error

Line - NO_AT_BRIDGE=1 is fixing the (app_flowy:1): dbind-WARNING **: 20:06:32.776: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/AppFlowy-IO/AppFlowy/pull/264 **Author:** [@texhno](https://github.com/texhno) **Created:** 1/20/2022 **Status:** ✅ Merged **Merged:** 8/3/2022 **Merged by:** [@appflowy](https://github.com/appflowy) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`7a197df`](https://github.com/AppFlowy-IO/AppFlowy/commit/7a197df57ce05ff953acd59e67f3b8ffe10f434c) fix: Fixes docker-compose up error and warning - [`32ee068`](https://github.com/AppFlowy-IO/AppFlowy/commit/32ee068c73a6b07ee6c5a1df0b74fc4910cbf439) chore: resolve docker-compose.yml conflicts ### 📊 Changes **1 file changed** (+13 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `frontend/scripts/docker-buildfiles/docker-compose.yml` (+13 -2) </details> ### 📄 Description When I run `docker-compose up` command I'm getting the following error: ``` app_1 | (app_flowy:1): dbind-WARNING **: 20:06:32.776: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. app_1 | libGL error: MESA-LOADER: failed to retrieve device information app_1 | [xcb] Unknown sequence number while processing queue app_1 | [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called app_1 | [xcb] Aborting, sorry about that. app_1 | app_flowy: xcb_io.c:269: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. appflowy_app_1 exited with code 139 ``` I searched on the Internet and found some solutions, feel free to use them if you consider them useful. Lines below are fixing the `libGL error: MESA-LOADER: failed to retrieve device information` and following `[xcb]` messages ``` devices: - "/dev/dri:/dev/dri" # fixes MESA-LOADER error ``` Line `- NO_AT_BRIDGE=1` is fixing the `(app_flowy:1): dbind-WARNING **: 20:06:32.776: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
mirror 2026-03-23 21:35:58 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#4028
No description provided.