Opened 3 years ago
Closed 3 years ago
#16646 closed enhancement (fixed)
libX11-1.8.1 (Xorg library)
| Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
|---|---|---|---|
| Priority: | normal | Milestone: | 11.2 |
| Component: | BOOK | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
New point version.
Change History (9)
comment:1 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 3 years ago
follow-up: 4 comment:3 by , 3 years ago
I don't believe that's correct, because it is enabled by default. I see that Arch has disable-thread-safety-constructor "as temporary solution until Xfce gets fixed".
comment:4 by , 3 years ago
Replying to martyj19:
I don't believe that's correct, because it is enabled by default. I see that Arch has disable-thread-safety-constructor "as temporary solution until Xfce gets fixed".
What needs to be fixed in Xfce?
comment:5 by , 3 years ago
The original report from Arch trouble ticket 75004 has
After reboot startxfce4 resulted in black screen with only mouse arrow.
The issue was confirmed due to 1.8.1 by downgrading to 1.8.
comment:6 by , 3 years ago
There are a couple more links:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/158
I can't find any mention in xfce because I don't know which package.
comment:7 by , 3 years ago
From https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 the locking in xfsettingsd is wrong (comments from ofourdan and ajax), that is part of xfce4-settings.
Updating libX11 is easier :)
This might also affect other desktops which are not in BLFS.
comment:8 by , 3 years ago
From the best I could tell, this has not been reported to the xfce developers. I did not see anything at https://gitlab.xfce.org/xfce/xfce4-settings/-/issues
comment:9 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed at updates e97b581b22 and 57886172be.
The only change is "configure.ac: Fix --enable-thread-safety-constructor". It does not affect us because we don't use this option.