blender
/
blender
130
398
Fork 574
Code Issues 6.2k Pull Requests 750 Projects 19 Wiki Activity

Resizing window causes crash on Wayland (libdecor) #107797

New Issue
Open
opened 2023-05-09 20:24:04 +02:00 by Daniel Schroeder · 22 comments
Daniel Schroeder commented 2023-05-09 20:24:04 +02:00
Copy Link

System Information
Operating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.6, DRM 3.47, 5.19.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.2.5

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: (unknown)

Short description of error
Rapidly resizing the Blender window causes the application to crash. If I resize the window very slowly (like, 10 or 20 pixels per second), it resizes successfully and smoothly. If I do a single, quick drag of the window edge to resize it by about 100 pixels, the window takes about a second to respond but does resize successfully. If I drag an edge or corner quickly over larger distances and for longer, the window crashes with this message in the terminal:

GHOST/Wayland: Error sending request: Broken pipe
The Wayland connection broke. Did the Wayland compositor die?
Error: Not freed memory blocks: 56580, total unfreed memory 17.653542 MB
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
[... etc. ...]

Exact steps for others to reproduce the error

  • Install Blender on Ubuntu 22.04.2 LTS from the official snap (https://snapcraft.io/blender)
  • Open Blender while running in a default Wayland login
  • Un-maximize the window, click and drag on a corner to resize the window, and move the mouse rapidly over large distances
**System Information** Operating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.35 64 Bits Graphics card: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.6, DRM 3.47, 5.19.0-41-generic) AMD 4.6 (Core Profile) Mesa 22.2.5 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: (unknown) **Short description of error** Rapidly resizing the Blender window causes the application to crash. If I resize the window *very* slowly (like, 10 or 20 pixels per second), it resizes successfully and smoothly. If I do a single, quick drag of the window edge to resize it by about 100 pixels, the window takes about a second to respond but does resize successfully. If I drag an edge or corner quickly over larger distances and for longer, the window crashes with this message in the terminal: GHOST/Wayland: Error sending request: Broken pipe The Wayland connection broke. Did the Wayland compositor die? Error: Not freed memory blocks: 56580, total unfreed memory 17.653542 MB Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom. [... etc. ...] **Exact steps for others to reproduce the error** - Install Blender on Ubuntu 22.04.2 LTS from the official snap (https://snapcraft.io/blender) - Open Blender while running in a default Wayland login - Un-maximize the window, click and drag on a corner to resize the window, and move the mouse rapidly over large distances
Daniel Schroeder added the
Priority
Normal
Type
Report
Status
Needs Triage
 labels 2023-05-09 20:24:05 +02:00
Iliya Katushenock added the
Interest
User Interface
Interest
Wayland
 labels 2023-05-09 20:24:46 +02:00
Daniel Schroeder commented 2023-05-09 20:40:20 +02:00
Author
Copy Link

Confirmed the same behavior on the current stable and alpha daily builds:

  • version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: 6ee8aa4997ee
  • version: 3.6.0 Alpha, branch: main, commit date: 2023-05-09 15:20, hash: 521e79b86912
Confirmed the same behavior on the current stable and alpha daily builds: - version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-25 13:50, hash: `6ee8aa4997ee` - version: 3.6.0 Alpha, branch: main, commit date: 2023-05-09 15:20, hash: `521e79b86912`
👍 1
Daniel Schroeder commented 2023-05-09 21:46:34 +02:00
Author
Copy Link

One more quick update: the crash does not occur if I request an Xorg session on the Ubuntu login screen. Additionally, several other applications experience very laggy window resizing under Wayland but not Xorg (e.g., VLC, GIMP), but none of them crash in response to window resize.

One more quick update: the crash does *not* occur if I request an Xorg session on the Ubuntu login screen. Additionally, several other applications experience very laggy window resizing under Wayland but not Xorg (e.g., VLC, GIMP), but none of them crash in response to window resize.
dgkf commented 2023-05-09 23:43:50 +02:00
Copy Link

Just chiming in with my own test of this. I haven't been able to crash a session even with some very fast window resizing. It resizes quite fast actually. I would say faster than most apps so I don't think I observe this same behavior of having a sluggish resize response time.

I'm on:

Ubuntu 23.04
Linux 6.2.0-20-generic x86_64
Wayland
AMD RX 570 GPU
Tested on official snap install and main (e151425c5c1 from 2023-05-08)

Just chiming in with my own test of this. I haven't been able to crash a session even with some very fast window resizing. It resizes quite fast actually. I would say faster than most apps so I don't think I observe this same behavior of having a sluggish resize response time. I'm on: > Ubuntu 23.04 > Linux 6.2.0-20-generic x86_64 > Wayland > AMD RX 570 GPU > Tested on official snap install and `main` (`e151425c5c1` from 2023-05-08)
YimingWu commented 2023-05-10 07:06:40 +02:00
Member
Copy Link

It's weird that I experience very laggy window resizing under X but not on wayland.

It's weird that I experience very laggy window resizing under X but not on wayland.
Philipp Oeser commented 2023-05-17 11:46:32 +02:00
Member
Copy Link

Cannot repro here

**System Information**
Operating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits
Graphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7
version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3`

@ideasman42 : are you able to repro?

Cannot repro here ``` **System Information** Operating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits Graphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7 version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` ``` @ideasman42 : are you able to repro?
Campbell Barton commented 2023-05-18 02:08:39 +02:00
Owner
Copy Link

I can't redo the bug either. Things to look into:

  • Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations).

  • Test on GNOME with libdecor disabled (possible since: a9358f5274), included in the latest 4.0 alpha daily build.

    • Uninstall libdecor.
    • Run DISPLAY="" ./blender

    This will run Blender without libdecor so you can check if this causes the error.

I can't redo the bug either. Things to look into: - Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations). - Test on GNOME with libdecor disabled (possible since: a9358f5274b60c61a5a2a57389372d01ade9be5a), included in the latest 4.0 alpha daily build. - Uninstall `libdecor`. - Run `DISPLAY="" ./blender` This will run Blender without libdecor so you can check if this causes the error.
Philipp Oeser commented 2023-07-19 13:39:05 +02:00
Member
Copy Link

I can't redo the bug either. Things to look into:

  • Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations).

  • Test on GNOME with libdecor disabled (possible since: a9358f5274), included in the latest 4.0 alpha daily build.

    • Uninstall libdecor.
    • Run DISPLAY="" ./blender

    This will run Blender without libdecor so you can check if this causes the error.

@dan5sch : do you have a chance to test the above?

> I can't redo the bug either. Things to look into: > > - Test on a different compositor (KDE/SWAY for example) most other compositors support server-side decorations. This issue could be related to libdecor (which handles decorations). > - Test on GNOME with libdecor disabled (possible since: a9358f5274b60c61a5a2a57389372d01ade9be5a), included in the latest 4.0 alpha daily build. > > - Uninstall `libdecor`. > - Run `DISPLAY="" ./blender` > > This will run Blender without libdecor so you can check if this causes the error. > @dan5sch : do you have a chance to test the above?
Philipp Oeser added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-07-19 13:39:14 +02:00
Daniel Schroeder commented 2023-07-21 00:06:23 +02:00
Author
Copy Link

@lichtwerk I haven't. I use this machine for my work, so I'm wary of mucking with the installation of the desktop environment itself.

@lichtwerk I haven't. I use this machine for my work, so I'm wary of mucking with the installation of the desktop environment itself.
Campbell Barton commented 2023-07-21 01:21:20 +02:00
Owner
Copy Link

@dan5sch: Running with DISPLAY="" ./blender doesn't require system modifications, could you please test this?

@dan5sch: Running with `DISPLAY="" ./blender` doesn't require system modifications, could you please test this?
Campbell Barton changed title from Resizing window causes crash to Resizing window causes crash on Wayland 2023-07-21 01:22:03 +02:00
Daniel Schroeder commented 2023-07-21 02:20:11 +02:00
Author
Copy Link

@ideasman42 running Blender with DISPLAY="" in a Wayland Gnome session still crashed when I resized the window quickly. (To be clear, this was without uninstalling libdecor or any of the other steps in your original comment.)

@ideasman42 running Blender with `DISPLAY=""` in a Wayland Gnome session still crashed when I resized the window quickly. (To be clear, this was without uninstalling `libdecor` or any of the other steps in your original comment.)
Campbell Barton commented 2023-07-21 07:00:21 +02:00
Owner
Copy Link

@dan5sch: hang on, you would have to make sure libdecor isn't available for this to work as expected.

@dan5sch: hang on, you would have to make sure libdecor isn't available for this to work as expected.
Daniel Schroeder commented 2023-07-21 18:49:28 +02:00
Author
Copy Link

@ideasman42 OK, found a way to test this. TL;DR: DISPLAY="" blender does NOT crash on rapid resize when loading of libdecor is prevented.

Method:
Using the approach in this post, I was able to LD_PRELOAD a modified dlopen() that prevents loading libdecor. To my pleasant surprise, this just worked.

Results (again in Wayland Gnome):

  • blender: crash on rapid window resize. xwininfo does NOT say Blender is an X window.
  • LD_PRELOAD=libmydlopen.so blender: Window decorations resemble those of "native" Gnome 3 applications. NO crash on rapid window resize. xwininfo says that Blender is an X window.
  • DISPLAY="" LD_PRELOAD=libmydlopen.so blender: NO window decorations at all. NO crash on rapid window resize after using ALT-F8 to enable resize with the mouse. xwininfo says that Blender is NOT an X window.
@ideasman42 OK, found a way to test this. TL;DR: `DISPLAY="" blender` does NOT crash on rapid resize when loading of `libdecor` is prevented. Method: Using the approach in [this post](https://stackoverflow.com/a/47611414), I was able to `LD_PRELOAD` a modified `dlopen()` that prevents loading `libdecor`. To my pleasant surprise, this just worked. Results (again in Wayland Gnome): - `blender`: crash on rapid window resize. `xwininfo` does NOT say Blender is an X window. - `LD_PRELOAD=libmydlopen.so blender`: Window decorations resemble those of "native" Gnome 3 applications. NO crash on rapid window resize. `xwininfo` says that Blender is an X window. - `DISPLAY="" LD_PRELOAD=libmydlopen.so blender`: NO window decorations at all. NO crash on rapid window resize after using `ALT-F8` to enable resize with the mouse. `xwininfo` says that Blender is NOT an X window.
Philipp Oeser commented 2023-08-15 12:17:01 +02:00
Member
Copy Link

OK, thx getting back.

@ideasman42 : what would be the way forward here then?

OK, thx getting back. @ideasman42 : what would be the way forward here then?
Philipp Oeser changed title from Resizing window causes crash on Wayland to Resizing window causes crash on Wayland (libdecor) 2023-08-15 12:17:17 +02:00
Campbell Barton commented 2023-08-18 07:48:41 +02:00
Owner
Copy Link

@lichtwerk I can't redo this bug reliably although I did manage to get a crash once.
I'm not all that satisfied with libdecor, there are currently 3 open issues relating to libdecor where I'm not sure how we might proceed, although this crash is the worst.

For reference the 2 other bugs: #109194, #108308.

So longer term it may be best to use client side decorations, although if this crash can be reproduced reliably by a developer it should be investigated of course.

@lichtwerk I can't redo this bug reliably although I did manage to get a crash once. I'm not all that satisfied with libdecor, there are currently 3 open issues relating to libdecor where I'm not sure how we might proceed, although this crash is the worst. For reference the 2 other bugs: #109194, #108308. --- So longer term it may be best to use client side decorations, although if this crash can be reproduced reliably by a developer it should be investigated of course.
Campbell Barton commented 2023-08-23 07:50:40 +02:00
Owner
Copy Link

Attempting to redo this crash and I wasn't able to - gnome-shell 44.3.

Unless a developer can redo the issue it doesn't seem likely it can be resolved.

Attempting to redo this crash and I wasn't able to - gnome-shell 44.3. Unless a developer can redo the issue it doesn't seem likely it can be resolved.
Campbell Barton commented 2023-10-06 08:37:02 +02:00
Owner
Copy Link

@dan5sch could you check if this is resolved by recent builds? (it's possible e1dac0b122 fixes the bug).

@dan5sch could you check if this is resolved by recent builds? (it's possible e1dac0b1225eb498524811d12fb1561eef3407b5 fixes the bug).
Campbell Barton added
Status
Needs Information from User
 and removed
Status
Needs Info from Developers
 labels 2023-10-06 08:37:33 +02:00
Daniel Schroeder commented 2023-10-07 21:10:57 +02:00
Author
Copy Link

@ideasman42 tested today's alpha build f3f494fd63 which is now past the commit e1dac0b122 you mentioned. Results:

  • Crashing: it is now much harder to crash Blender by dragging a window corner and resizing. Crashes only occur after several seconds of dragging and rapidly moving the mouse large distances; and only some attempts trigger a crash.
  • Lag: while dragging a window corner rapidly, the window updates its displayed size at only single-digit framerates (or not at all for over a second before a crash). But so do several other applications on this system under Wayland (despite good system specs, and those applications resizing quickly under Xorg).

Notably, a new bug has appeared: if I begin dragging a corner of the window, move the mouse rapidly, and release the left mouse button while the mouse is still moving rapidly, the dimensions of the displayed window contents and the displayed window decoration / drop shadow appear to disagree with one another by one frame of mouse movement. Examples:

Screenshot from 2023-10-07 13-44-47.png
Screenshot from 2023-10-07 13-44-35.png

In this state:

  • the bottom right corner of the drop shadow displays a resize cursor on hover and responds to resize click-drag inputs; as soon as I begin resizing, the window contents snap to the dimensions of the drop shadow
  • if I interact with the window contents region with the mouse, the region redraws (e.g., rotating the viewport camera) without changing its dimensions to match the drop shadow
  • moving the window by dragging the title bar does not remove the glitched state
  • alt-tabbing away from the Blender window and then back removes the glitched state
@ideasman42 tested today's alpha build f3f494fd63aa which is now past the commit e1dac0b122 you mentioned. Results: - Crashing: it is now *much* harder to crash Blender by dragging a window corner and resizing. Crashes only occur after several seconds of dragging and rapidly moving the mouse large distances; and only some attempts trigger a crash. - Lag: while dragging a window corner rapidly, the window updates its displayed size at only single-digit framerates (or not at all for over a second before a crash). But so do several other applications on this system under Wayland (despite good system specs, and those applications resizing quickly under Xorg). Notably, a *new* bug has appeared: if I begin dragging a corner of the window, move the mouse rapidly, and release the left mouse button while the mouse is still moving rapidly, the dimensions of the displayed window contents and the displayed window decoration / drop shadow appear to disagree with one another by one frame of mouse movement. Examples: ![Screenshot from 2023-10-07 13-44-47.png](/attachments/6d9e9a8d-cf18-4c61-966a-637b24b8a2b2) ![Screenshot from 2023-10-07 13-44-35.png](/attachments/4fa3b9b9-288f-4b3a-921e-0f547ae1e950) In this state: - the bottom right corner of the *drop shadow* displays a resize cursor on hover and responds to resize click-drag inputs; as soon as I begin resizing, the window contents snap to the dimensions of the drop shadow - if I interact with the window *contents* region with the mouse, the region redraws (e.g., rotating the viewport camera) *without* changing its dimensions to match the drop shadow - moving the window by dragging the title bar does *not* remove the glitched state - alt-tabbing away from the Blender window and then back removes the glitched state
Screenshot from 2023-10-07 13-44-35.png
510 KiB
Screenshot from 2023-10-07 13-44-47.png
516 KiB
Campbell Barton commented 2023-10-09 11:45:16 +02:00
Owner
Copy Link

@dan5sch thanks for checking: could you please note which versions of gnome-shell & libdecor your using?
I'm on: GNOME Shell 44.5, libdecor 0.2.0.

It may be that this issue only happens on older versions of both.
Note that I was concerned about e1dac0b122 causing the issue you described with the border getting out of sync with the window but I wasn't able to trigger this problem, so it's unfortunate this happens for some configurations.

@dan5sch thanks for checking: could you please note which versions of gnome-shell & libdecor your using? I'm on: GNOME Shell 44.5, libdecor 0.2.0. It may be that this issue only happens on older versions of both. Note that I was concerned about e1dac0b122 causing the issue you described with the border getting out of sync with the window but I wasn't able to trigger this problem, so it's unfortunate this happens for some configurations.
Daniel Schroeder commented 2023-10-10 19:18:00 +02:00
Author
Copy Link

@ideasman42 GNOME Shell 42.9, libdecor 0.1.0

These are the versions provided by Ubuntu 22.04.3 LTS.

@ideasman42 GNOME Shell 42.9, libdecor 0.1.0 These are the versions provided by Ubuntu 22.04.3 LTS.
Philipp Oeser added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2023-10-24 09:48:19 +02:00
Campbell Barton commented 2023-12-17 08:34:43 +01:00
Owner
Copy Link

@dan5sch could you please check if this is resolved in recent builds, it's possible 1455315111 resolves the problem.

@dan5sch could you please check if this is resolved in recent builds, it's possible 1455315111ae769d101413fe600662484ff46d62 resolves the problem.
Campbell Barton added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-12-17 08:35:02 +01:00
Daniel Schroeder commented 2023-12-18 05:12:54 +01:00
Author
Copy Link

@ideasman42 tested the latest alpha build 29b5919ad1 which is past 1455315111. Same GNOME Shell / libdecor versions as last test (from system repos).

Blender continues to crash after about two seconds of rapidly resizing the window. The non-crash failure mode described in my previous reply (with the screenshots) no longer occurs.

New since my original bug report is that the program displays a stack trace upon crashing. Pasting it in case it's useful.

GHOST/Wayland: Error sending request: Broken pipe
./blender() [0xf5f210]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x595a) [0x7fa8bfe3d95a]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_array_flags+0x46d) [0x7fa8bfe412bd]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_flags+0xef) [0x7fa8bfe41c7f]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7283) [0x7fa8d52c8283]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7bfd) [0x7fa8d52c8bfd]
/usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7de6) [0x7fa8d52c8de6]
/lib/x86_64-linux-gnu/libdecor-0.so.0(libdecor_frame_commit+0x8d) [0x7fa8bfe28a5d]
./blender() [0x289a919]
./blender() [0x289ace3]
/lib/x86_64-linux-gnu/libdecor-0.so.0(+0x37ec) [0x7fa8bfe277ec]
/lib/x86_64-linux-gnu/libffi.so.8(+0x7e2e) [0x7fa8bfe08e2e]
/lib/x86_64-linux-gnu/libffi.so.8(+0x4493) [0x7fa8bfe05493]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x6ad0) [0x7fa8bfe3ead0]
/lib/x86_64-linux-gnu/libwayland-client.so.0(+0x7243) [0x7fa8bfe3f243]
/lib/x86_64-linux-gnu/libwayland-client.so.0(wl_display_dispatch_queue_pending+0x7c) [0x7fa8bfe3f43c]
./blender() [0x2891b4e]
./blender() [0xfd5e1d]
./blender() [0xfa4218]
./blender() [0x72662d]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fa8c3429d90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fa8c3429e40]
./blender() [0x8c076e]
The Wayland connection broke. Did the Wayland compositor die?
@ideasman42 tested the latest alpha build 29b5919ad11a which is past 1455315111. Same GNOME Shell / libdecor versions as last test (from system repos). Blender continues to crash after about two seconds of rapidly resizing the window. The non-crash failure mode described in my previous reply (with the screenshots) no longer occurs. New since my original bug report is that the program displays a stack trace upon crashing. Pasting it in case it's useful. ``` GHOST/Wayland: Error sending request: Broken pipe ./blender() [0xf5f210] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x595a) [0x7fa8bfe3d95a] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_array_flags+0x46d) [0x7fa8bfe412bd] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_proxy_marshal_flags+0xef) [0x7fa8bfe41c7f] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7283) [0x7fa8d52c8283] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7bfd) [0x7fa8d52c8bfd] /usr/lib/x86_64-linux-gnu/libdecor/plugins-1/libdecor-cairo.so(+0x7de6) [0x7fa8d52c8de6] /lib/x86_64-linux-gnu/libdecor-0.so.0(libdecor_frame_commit+0x8d) [0x7fa8bfe28a5d] ./blender() [0x289a919] ./blender() [0x289ace3] /lib/x86_64-linux-gnu/libdecor-0.so.0(+0x37ec) [0x7fa8bfe277ec] /lib/x86_64-linux-gnu/libffi.so.8(+0x7e2e) [0x7fa8bfe08e2e] /lib/x86_64-linux-gnu/libffi.so.8(+0x4493) [0x7fa8bfe05493] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x6ad0) [0x7fa8bfe3ead0] /lib/x86_64-linux-gnu/libwayland-client.so.0(+0x7243) [0x7fa8bfe3f243] /lib/x86_64-linux-gnu/libwayland-client.so.0(wl_display_dispatch_queue_pending+0x7c) [0x7fa8bfe3f43c] ./blender() [0x2891b4e] ./blender() [0xfd5e1d] ./blender() [0xfa4218] ./blender() [0x72662d] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fa8c3429d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fa8c3429e40] ./blender() [0x8c076e] The Wayland connection broke. Did the Wayland compositor die? ```
Campbell Barton commented 2023-12-19 15:27:16 +01:00
Owner
Copy Link

@dan5sch since the issue is a broken pipe in libdecor's code, it looks as if the connection is being lost outside of Blender, I'm not sure if this is something we can fix.

@dan5sch since the issue is a broken pipe in libdecor's code, it looks as if the connection is being lost outside of Blender, I'm not sure if this is something we can fix.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
fix-121021
blender-v4.1-release
blender-v3.3-release
blender-v3.6-release
universal-scene-description
blender-v3.6-temp_wmoss_animrig_public
temp-sculpt-dyntopo
gpencil-next
anim/animation-id-113594
blender-v4.0-release
blender-projects-basics
bridge-curves
sculpt-blender
asset-browser-frontend-split
asset-shelf
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-v2.93-release
realtime-clock
sculpt-dev
bevelv2
xr-dev
v4.1.1
v3.6.11
v3.3.18
v4.1.0
v3.3.17
v3.6.10
v3.6.9
v3.3.16
v3.6.8
v3.6.7
v3.3.14
v4.0.2
v4.0.1
v4.0.0
v3.6.5
v3.3.12
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset Browser

  
Interest
Asset Browser Project Overview

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Collada

  
Interest
Compatibility
This issue affects/is about backward or forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
Interest
EEVEE & Viewport

  
Interest
Freestyle

  
Interest
Geometry Nodes

  
Interest
Grease Pencil

  
Interest
ID Management

  
Interest
Images & Movies

  
Interest
Import Export

  
Interest
Line Art

  
Interest
Masking

  
Interest
Metal

  
Interest
Modeling

  
Interest
Modifiers

  
Interest
Motion Tracking

  
Interest
Nodes & Physics

  
Interest
OpenGL

  
Interest
Overlay

  
Interest
Overrides

  
Interest
Performance

  
Interest
Physics

  
Interest
Pipeline, Assets & IO

  
Interest
Platforms, Builds & Tests

  
Interest
Python API

  
Interest
Render & Cycles

  
Interest
Render Pipeline

  
Interest
Sculpt, Paint & Texture

  
Interest
Text Editor

  
Interest
Translations

  
Interest
Triaging

  
Interest
Undo

  
Interest
USD

  
Interest
User Interface

  
Interest
UV Editing

  
Interest
VFX & Video

  
Interest
Video Sequencer

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
Legacy
Blender 2.8 Project

  
Legacy
Milestone 1: Basic, Local Asset Browser

  
Legacy
OpenGL Error

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
Module
EEVEE & Viewport

  
Module
Grease Pencil

  
Module
Modeling

  
Module
Nodes & Physics

  
Module
Pipeline, Assets & IO

  
Module
Platforms, Builds & Tests

  
Module
Python API

  
Module
Render & Cycles

  
Module
Sculpt, Paint & Texture

  
Module
Triaging

  
Module
User Interface

  
Module
VFX & Video

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Priority
High

  
Priority
Low

  
Priority
Normal

  
Priority
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Info from Developers

  
Status
Needs Information from User

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Patch

  
Type
Report

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
5 Participants
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: blender/blender#107797
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?