xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2023-01-30T08:21:02Zhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1433"Are you sure you want to proceed?" message on login.2023-01-30T08:21:02Zhongyi-zhao"Are you sure you want to proceed?" message on login.I'm using Ubuntu 22.10, Gnome desktop and `Xorg`. Each time when I try to log in to desktop, I meet the "Are you sure you want to proceed?" message as described [here](https://askubuntu.com/questions/587868/are-you-sure-you-want-to-proce...I'm using Ubuntu 22.10, Gnome desktop and `Xorg`. Each time when I try to log in to desktop, I meet the "Are you sure you want to proceed?" message as described [here](https://askubuntu.com/questions/587868/are-you-sure-you-want-to-proceed-message-on-login). I've tried all sorts of ways to get out of this window, but it doesn't work, and I'm wondering what's going on here, is it related to some Settings in `Xorg`?
See [here](https://gitlab.gnome.org/GNOME/gdm/-/issues/833) for the related discussion.
Regards,
Zhaohttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1432FatalError add FatalError to output makes it simpler to find in core dumps2023-01-26T22:47:18ZJonnyFatalError add FatalError to output makes it simpler to find in core dumps
FatalError() is called from 366 different places, without any consistent prefix such as "FatalError"
A consistent prefix would allow users to use strings to search a core file for the cause of the error. It's a common issue that users ...
FatalError() is called from 366 different places, without any consistent prefix such as "FatalError"
A consistent prefix would allow users to use strings to search a core file for the cause of the error. It's a common issue that users don't have debug symbols, but do have a core file.
os/log.c contains the implementation of FatalError on line 983
The other way would be to add the "FatalError:" prefix there in the buffer, so visible in the core file. That would be the same as the way assert() macro messages are visible in core files then.https://gitlab.freedesktop.org/xorg/util/xcb-util-m4/-/issues/2Please make a release2023-01-27T12:46:13ZwerdahiasPlease make a releaseRelated to #1. Please consider making a release containing the three macro files. This would allow for easier packaging.Related to #1. Please consider making a release containing the three macro files. This would allow for easier packaging.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1430Follow-up from "Xwayland: Implement linux_dmabuf v4 feedback support"2023-02-16T10:26:44ZMichel DänzerFollow-up from "Xwayland: Implement linux_dmabuf v4 feedback support"The following discussion from !818 should be addressed:
- [ ] @ofourdan started a [discussion](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/818#note_1726275): (+2 comments)
> If that assertion fails, that would qua...The following discussion from !818 should be addressed:
- [ ] @ofourdan started a [discussion](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/818#note_1726275): (+2 comments)
> If that assertion fails, that would qualify as a bug in the compositors rather than Xwayland, wouldn't it?
>
> If so, I'd rather have this function handle the case nicely rather than aborting Xwayland entirely.
>
> Besides, I think `assert()` should not be used to validate data from the compositor, as this can be disabled with `NDEBUG` at compile time.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1429modesetting driver hangs on starting gui with 32-bit 6.1.2 kernel2023-02-03T10:52:33ZJohn Frankishmodesetting driver hangs on starting gui with 32-bit 6.1.2 kernelxorg-server-21.1.3 with mesa-21.3.4 and a 5.15.10 32-bit kernel works as expected with intel hd4400 graphics and the modesetting driver.
If the above is used with a 6.1.2 32-bit kernel the gui does not start and hangs with the backlight...xorg-server-21.1.3 with mesa-21.3.4 and a 5.15.10 32-bit kernel works as expected with intel hd4400 graphics and the modesetting driver.
If the above is used with a 6.1.2 32-bit kernel the gui does not start and hangs with the backlight on. The console will not switch, so the only way out is a hard reset. This does not happen with a 6.1.2 64-bit kernel, nor does it happen with the 6.1.2 32-bit kernel and the xf86-video-intel driver.
Updating to xorg-server-21.1.6 and mesa-22.3.3 does not help.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1428RFE: XGE generic event channels2023-02-02T17:39:01ZAdam Jacksonajax@nwnk.netRFE: XGE generic event channelsThe Present extension makes the notable improvement that events are selected and delivered relative to an `EVENTID` type - "event channel" might be a better name. This allows for multiple subsystems within a process to receive a copy of ...The Present extension makes the notable improvement that events are selected and delivered relative to an `EVENTID` type - "event channel" might be a better name. This allows for multiple subsystems within a process to receive a copy of any given event, without affecting other subsystems or needing to rely on a client-side convention for event queue interest. (Well. Kinda. It bakes that convention into libxcb as "special events". Whatever.)
Unfortunately it stops there, and it doesn't really belong there. Event channels ought to be an XGE extension concept, and they should be able to encapsulate arbitrary core or extension events. This could massively improve life on the client side. A few examples off the top of my head:
- Multiple readers could listen for `ConfigureNotify` on the root window, or corresponding RANDR events, and all would get notified
- llvmpipe would be able to use the `send_event=True` version of `ShmPutImage` to increase parallelism
- libX11 could potentially internally redirect event selection to its own private channel, which might finally solve the "who owns the event queue" problem when mixing xcb and xlib in one processhttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1427Multiple touchscreen support using identical hardware2023-01-16T04:27:34ZZoltán BöszörményiMultiple touchscreen support using identical hardwareI am in the POS industry and have come across hardware with two touchscreens.
When those touchscreen hardware attached to the same machine are different, it's easy to use `MatchProduct` in two `InputClass` sections.
But when they are i...I am in the POS industry and have come across hardware with two touchscreens.
When those touchscreen hardware attached to the same machine are different, it's easy to use `MatchProduct` in two `InputClass` sections.
But when they are identical, there seems to be no way to distinguish between them. Product name is identical, USB ID is identical. Obviously the device path is different but `/dev/input/eventX` is not stable, as other devices may be plugged in that would make the event device numbers change.
`BusID` only exists for `Device` sections but there is no equivalent `MatchBusID` for `InputClass`.
Is there a way to match a device exactly today in this situation, or should I implement `MatchBusID`?
@ofourdanhttps://gitlab.freedesktop.org/xorg/app/xrandr/-/issues/68Unable to set supported resolution manually2023-01-11T15:11:50ZLorenz StangierUnable to set supported resolution manuallyI am trying to get my external monitor (LG 27UL550-W) to work on 4k@60Hz with my Laptop (Lenovo ThinkPad E480 running Linux) using a USB-C dock via an HDMI Cable.
4k@60Hz works when using the same hardware (Cable, Monitor & Dock) with ...I am trying to get my external monitor (LG 27UL550-W) to work on 4k@60Hz with my Laptop (Lenovo ThinkPad E480 running Linux) using a USB-C dock via an HDMI Cable.
4k@60Hz works when using the same hardware (Cable, Monitor & Dock) with my friends MacBook Air M1.
I tried setting the resolution manually, as described here: https://wiki.archlinux.org/title/Xrandr#Adding_undetected_resolutions, which resulted in the following commands:
xrandr --newmode "3480x2160_60.00" 645.25 3480 3768 4144 4808 2160 2163 2173 2237 -hsync +vsync
xrandr --verbose --addmode DP-1 "3480x2160_60.00"
xrandr --verbose --output DP-1 --mode "3480x2160_60.00"
This gave the error:
crtc 2: 3480x2160_60.00 59.99 +0+0 "DP-1"
xrandr: Configure crtc 2 failed
crtc 0: disable
crtc 1: disable
crtc 2: disable
crtc 3: disable
crtc 4: disable
crtc 5: disable
crtc 6: disable
crtc 7: disable
screen 0: revert
crtc 0: revert
crtc 1: revert
crtc 2: revert
crtc 3: revert
crtc 4: revert
crtc 5: revert
crtc 6: revert
crtc 7: revert
As the laptop is, according to the manual, supposed to support 4k@60Hz via USB-C and the hardware does support it (as tested) I really don't know what else could be the issue. Thankful for any idea.https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/179LibX11 1.8.2+ regression on bepo layout in wine2023-03-06T12:34:35ZaerisLibX11 1.8.2+ regression on bepo layout in wineHello here!
Since libX11 1.8.2, I got a regression very strange I'm currently not able to understand.
Until [ArchLinux 1.8.1-3](https://github.com/archlinux/svntogit-packages/commit/5b89deb289ea002839fe4e4fe8988627ba961684), bepo layou...Hello here!
Since libX11 1.8.2, I got a regression very strange I'm currently not able to understand.
Until [ArchLinux 1.8.1-3](https://github.com/archlinux/svntogit-packages/commit/5b89deb289ea002839fe4e4fe8988627ba961684), bepo layout was poorly managed by Wine (some keycode seems rendering to wrong key) but was usable with some tweaks, but since 1.8.2 some keycodes are just no more usable at all in some weird contexts.
At this time, I notice at least `É` on 1.8.1 detected as `=` on 1.8.2+ and `È` working on 1.8.1 but random behavior on 1.8.2+ (using key on chat text input works and display the right character but the same key on keyboard mapping settings not recognized at all when pressed)
Downgrading libx11 to 1.8.1-3 restore previous correct/usable behavior.
Regression tested in 1.8.2-1, 1.8.2-2 and 1.8.3-5 on ArchLinux and very easy to reproduce at least on my setup.
You can see the corresponding issue on Wine side [here](https://bugs.winehq.org/show_bug.cgi?id=53991).https://gitlab.freedesktop.org/xorg/lib/libxt/-/issues/15Should XtCallbackReleaseCacheRefList free its argument?2023-01-02T21:53:42ZAlan CoopersmithShould XtCallbackReleaseCacheRefList free its argument?In the libXt spec, starting at https://gitlab.freedesktop.org/xorg/lib/libxt/-/blob/master/specs/CH09.xml#L2919 `XtCallbackReleaseCacheRefList()` is defined as a way to "explicitly decrement reference counts", but the current implementat...In the libXt spec, starting at https://gitlab.freedesktop.org/xorg/lib/libxt/-/blob/master/specs/CH09.xml#L2919 `XtCallbackReleaseCacheRefList()` is defined as a way to "explicitly decrement reference counts", but the current implementation also tries to free the list it's given:
https://gitlab.freedesktop.org/xorg/lib/libxt/-/blob/1aaf5d502027104ddd566090787780319f510278/src/Convert.c#L1106-1114
For nearly two decades now, we've been carrying around a change in the Solaris libXt that removes the free statement:
https://github.com/oracle/solaris-userland/blob/f82e11f/components/x11/lib/libXt/patches/05-15143893.patch
Unfortunately, the original author left the company long ago, but in our internal bug database, it appears this came up when submitting VSW5 results for certification to The Open Group, and getting a segfault in the `XtCallbackReleaseCacheRefList()` test because it had allocated the list on the stack, not with `malloc()`. It appears we were told then this was a bug in our implementation and that the function should not be freeing the list. (It's unclear why this change never got reported/fixed in the X.Org upstream code if this is the case, as the free has been there since the function was created: <https://gitlab.freedesktop.org/alanc/xc-historical/-/commit/540552e8f832f45392de7a2ef8e31433daeee295>)
After the VSW test suite was open sourced as XTS, the test was changed to workaround this issue:
https://gitlab.freedesktop.org/xorg/test/xts/-/commit/c3a401f84ce701e310efb9de6ab5c031451e01f3
I'm not clear on which view was correct - was the test wrong or is the current libXt code wrong?https://gitlab.freedesktop.org/xorg/xserver/-/issues/1423Indirect rendering causes segfaults, has broken refresh.2022-12-29T23:39:39ZuvosIndirect rendering causes segfaults, has broken refresh.On xorg-server 21.1.6 running on Arch Linux on amdgpu using the modesetting ddx (and also using the amdgpu ddx) xorg will hang, exit with a segfault, or fail to draw frames if any indirect glx clients are active.
to repoduce:
1. run xo...On xorg-server 21.1.6 running on Arch Linux on amdgpu using the modesetting ddx (and also using the amdgpu ddx) xorg will hang, exit with a segfault, or fail to draw frames if any indirect glx clients are active.
to repoduce:
1. run xorg with the +iglx option
2. export LIBGL_ALWAYS_INDIRECT=1
3. run a glx client
1. glxgears will run, but will fail to refesh more than the 1s maximum timer between refreshes
2. linuxcnc axis will reliably cause a segfault (see apitrace)
3. several other clients will simply cause xorg to hang
intdirect glx worked at least as of xorg 1.20
[axis.trace](/uploads/1075447ca66a044cdfed361b7835c27b/axis.trace)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1422Xwayland screen resolution issues2023-01-04T10:28:59ZBruno do NascimentoXwayland screen resolution issuesI don't know if I'm in the right place, however I'm having a problem with Xwayland....
It doesn't detect my native resolution (1360x768)
So I can't use that resolution in games
The only resolution that is detected is 1366x768
Can anyone ...I don't know if I'm in the right place, however I'm having a problem with Xwayland....
It doesn't detect my native resolution (1360x768)
So I can't use that resolution in games
The only resolution that is detected is 1366x768
Can anyone help me with this?
```
➜ ~ xrandr
Screen 0: minimum 16 x 16, current 1360 x 768, maximum 32767 x 32767
XWAYLAND0 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1366x768 59.80*+
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.52
720x480 59.71
640x400 59.95
320x200 58.96
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.55
640x350 59.77
➜ ~
```https://gitlab.freedesktop.org/xorg/xserver/-/issues/1421how to monitor the running status of Xserver?2022-12-29T03:19:39Zhao fanghow to monitor the running status of Xserver?We previously used xrandr to detect the startup of xserver, but maybe someone knows whether there is some kind of graphical software that can easily monitor the running status of Xserver?We previously used xrandr to detect the startup of xserver, but maybe someone knows whether there is some kind of graphical software that can easily monitor the running status of Xserver?https://gitlab.freedesktop.org/xorg/app/xfwp/-/issues/1swab() on overlapping data undefined2022-12-29T18:11:03ZThomas Klausnerswab() on overlapping data undefinedDue to a recent bugfix in swab() I noticed that POSIX says about swab():
```
If copying takes place between objects that overlap, the behavior is undefined.
```
see https://pubs.opengroup.org/onlinepubs/9699919799/functions/swab.html
xfw...Due to a recent bugfix in swab() I noticed that POSIX says about swab():
```
If copying takes place between objects that overlap, the behavior is undefined.
```
see https://pubs.opengroup.org/onlinepubs/9699919799/functions/swab.html
xfwp uses swab() on overlapping src/dst:
https://gitlab.freedesktop.org/xorg/app/xfwp/-/blob/master/io.c#L1043https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/60Cursor is now affected by redshift gamma ramps2023-10-24T02:13:08ZTasos SahanidisCursor is now affected by redshift gamma ramps## Brief summary of the problem:
After updating the kernel, under X11, the cursor is now noticeably affected by gamma ramps as applied by [redshift](https://github.com/jonls/redshift). This behaviour was introduced by [drm/amd/display: ...## Brief summary of the problem:
After updating the kernel, under X11, the cursor is now noticeably affected by gamma ramps as applied by [redshift](https://github.com/jonls/redshift). This behaviour was introduced by [drm/amd/display: don't enable DRM CRTC degamma property for DCE (0e444a4de6b3)](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0e444a4de6b38c4593a07e4cfb5bf54c40cc79b6).
At first I thought this occurred because hardware cursors were no longer being used, but comparing drm_info with and without the commit reverted, assuming I'm understanding it correctly, it seems that they are now used with that commit.
It's really difficult to tell by looking at a screen if it was applied before, but maybe after this change, the gamma ramps are now somehow applied multiple times, intensifying the effect.
When the cursor is moved to the display attached to the card driven by nouveau, it always remains unaffected.
## Hardware description:
- GPU:
```
*-display
description: VGA compatible controller
product: Bonaire XTX [Radeon R7 260X/360] [1002:6658]
vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
physical id: 0
bus info: pci@0000:08:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:33 memory:d0000000-dfffffff memory:ef000000-ef7fffff ioport:c800(size=256) memory:feac0000-feafffff memory:c0000-dffff
*-display
description: VGA compatible controller
product: G86 [GeForce 8400 GS] [10DE:422]
vendor: NVIDIA Corporation [10DE]
physical id: 0
bus info: pci@0000:07:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:30 memory:fd000000-fdffffff memory:b0000000-bfffffff memory:fa000000-fbffffff ioport:bc00(size=128) memory:fe9e0000-fe9fffff
```
## System information:
- Distro name and Version: Ubuntu 20.04.5 LTS
- Kernel version: torvalds/linux.git (b6bb9676f2165d518b35ba3bea5f1fcfc0d969bf)
- Custom kernel: custom config
- Mesa: 22.3.1 - kisak-mesa
## How to reproduce the issue:
Run a recent kernel (after the commit that introduced this behaviour) and enable redshift. For example, to force a visible change `redshift -t 4000K:4600K`.
## Attached files:
### Screenshots/video files
![cursors](/uploads/0ba670523a466063d6fea6994338f02c/cursors.jpg)
### Log files
- drm_info with the commit reverted: [drm_info_reverted.txt](/uploads/f1f649eef6c8b26150193b55f05612b1/drm_info_reverted.txt)
- drm_info without revert: [drm_info_not_reverted.txt](/uploads/be111283641b84e5955f7ea5caeb2fbe/drm_info_not_reverted.txt)https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/172nls: add compose seq's for Cyrillic letters from KOI8-C into the main table2023-12-09T19:58:33ZKelly Roadkillnls: add compose seq's for Cyrillic letters from KOI8-C into the main tableKOI8-C is a [pre-Unicode codepage](https://ru.wikipedia.org/wiki/%D0%9A%D0%9E%D0%98-8#%D0%9A%D0%BE%D0%B4%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0_KOI8-C_(%D0%A6%D0%B5%D0%BD%D1%82%D1%80%D0%B0%D0%BB%D1%8C%D0%BD%D0%B0%D1%8F_%D0%90%D0%B7%D0%B8%D1...KOI8-C is a [pre-Unicode codepage](https://ru.wikipedia.org/wiki/%D0%9A%D0%9E%D0%98-8#%D0%9A%D0%BE%D0%B4%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0_KOI8-C_(%D0%A6%D0%B5%D0%BD%D1%82%D1%80%D0%B0%D0%BB%D1%8C%D0%BD%D0%B0%D1%8F_%D0%90%D0%B7%D0%B8%D1%8F)) for Caucasus and Central Asia Cyrillic-based alphabets (Tatar, Buryat, Kalmyk, etc.) It was rarely used even before Unicode. Yet, it has its own compose table for letters like Җ, Қ, Ү, that are outside of basic Russian alphabet (which was fitting, since it is challenge to find a physical keyboard engraved with them). The table sits in [`nls/koi8-c/Compose.pre`](https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/master/nls/koi8-c/Compose.pre).
Unfortunately, it was never converted and included into any of modern Unicode compose tables. As a result, to be able to type a few letters in Tatar, for example, the user has to install the whole input language into the system.
My proposal is to add those sequences either to en_us.UTF-8, or to the affected Cyrillic layouts - the latter option is justified by the fact that all proposed sequences are based on Cyrillic letters (those which are common across all Cyrillic layouts).
I have converted the sequences to Unicode, fixed and extended the table to match the scope of Latin and Greek tables. Current version: [dotXCompose4libX11](/uploads/f2ff22aec9b42c3c984d756ed1d69073/dotXCompose4libX11) - I'll keep updating it here, as well as [in the repo](https://github.com/roadkell/xcompose).
I was initially working on an exhaustive table for as many Cyrillic letters as possible to be typable from any Cyrillic layout, but to make it acceptable for merging I'm planning to consult with fellow linguists & translators and make an "essentials" table, that is concise enough for either en_US, or affected Cyrillic layouts. Meanwhile, I would like to discuss the patterns in use, the scope to aim for, and everything that is needed to be accounted for to make this table (or a part of it) acceptable for libX11. Thanks.https://gitlab.freedesktop.org/xorg/xserver/-/issues/1418DPMS Off seems to trigger duplicated PresentCompleteNotify2022-12-16T21:12:20ZyshuiDPMS Off seems to trigger duplicated PresentCompleteNotifyI have a program that calls PresentNotifyMsc every frame to receive CompleteNotify for that frame. If the screen turns off while the program is running, the program sometimes receives duplicated CompleteNotify.
Here is an example trace:...I have a program that calls PresentNotifyMsc every frame to receive CompleteNotify for that frame. If the screen turns off while the program is running, the program sometimes receives duplicated CompleteNotify.
Here is an example trace:
```
1671051426.525 000:<:1148: 40: Present-Request(147,2): NotifyMSC window=0x000000a0 serial=0 target_msc=10110327 divisor=0 remainder=0
1671051426.541 000:>:1148: Event Generic(35) Present(147) CompleteNotify(1) kind=NotifyMSC(0x01) mode=Copy(0x00) event=0x03c00264 window=0x000000a0 serial=0 ust=198368549434 msc=10110327
1671051426.541 000:<:1149: 40: Present-Request(147,2): NotifyMSC window=0x000000a0 serial=0 target_msc=10110328 divisor=0 remainder=0
1671051426.775 000:>:1149: Event Generic(35) Present(147) CompleteNotify(1) kind=NotifyMSC(0x01) mode=Copy(0x00) event=0x03c00264 window=0x000000a0 serial=0 ust=198368549434 msc=10110327
```
Note that CompleteNotify with msc=10110327 was received twice. Curiously, the second one was arriving very late (230ms after the NotifyMsc request), the frame rate was 60fps.
This is not conformant w.r.t. the spec, which says
> If 'target-msc' is greater than the current msc for 'window', the event will be delivered at (or after) the 'target-msc' field.https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/59Output source runs at 1FPS when laptop lid is closed - issue is back2023-11-26T20:28:44ZMarcin SzewczykOutput source runs at 1FPS when laptop lid is closed - issue is backWith recent nvidia drivers version 525.60 the issue is back, same as [here](https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37). The fix was working for few months and with new nvidia drivers is back. Downgrading nv...With recent nvidia drivers version 525.60 the issue is back, same as [here](https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37). The fix was working for few months and with new nvidia drivers is back. Downgrading nvidia drivers to 520.56 solves the problem.
My specs:
```
System:
Host: vampirhon Kernel: 6.0.12-arch1-1 arch: x86_64 bits: 64 Desktop: GNOME
v: 43.2 Distro: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA401IV_GA401IV
v: 1.0 serial: <superuser required>
Mobo: ASUSTeK model: GA401IV v: 1.0 serial: <superuser required>
UEFI: American Megatrends v: GA401IV.219 date: 12/30/2020
Graphics:
Device-1: NVIDIA TU106M [GeForce RTX 2060 Max-Q] driver: nvidia v: 525.60.11
Device-2: AMD Renoir driver: amdgpu v: kernel
driver: snd-usb-audio,uvcvideo
Display: x11 server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5 driver: X:
loaded: amdgpu,nvidia unloaded: modesetting dri: radeonsi
gpu: amdgpu,nvidia,nvidia-nvswitch resolution: 1: 1920x1080 2: 1920x1080
3: 1920x1080~120Hz
API: OpenGL Message: Unable to show GL data. Required tool glxinfo
missing.
```
xorg packages:
- xorg-fonts-encodings 1.0.6-1
- xorg-server 21.1.4-1
- xorg-server-common 21.1.4-1
- xorg-setxkbmap 1.3.3-1
- xorg-xev 1.2.5-1
- xorg-xhost 1.0.9-1
- xorg-xinput 1.6.3-3
- xorg-xkbcomp 1.4.6-1
- xorg-xprop 1.2.6-1
- xorg-xrandr 1.5.2-1
- xorg-xrdb 1.2.1-1
- xorg-xset 1.2.5-1
- xorg-xwayland 22.1.5-1
- xorgproto 2022.2-1https://gitlab.freedesktop.org/xorg/xserver/-/issues/1416Didn't work xrdp after reboot2022-12-12T22:18:31ZSanchous1295Didn't work xrdp after rebootXRDP was configured on the server and everything worked fine until the server was rebooted
After reboot, it gives an error when entering the login password
`Connecting to sesman ip 127.0.0.1 port 3350`
`sesman connect ok`
`Sending l...XRDP was configured on the server and everything worked fine until the server was rebooted
After reboot, it gives an error when entering the login password
`Connecting to sesman ip 127.0.0.1 port 3350`
`sesman connect ok`
`Sending login info to session manager, please wait`
`login successful for display 10`
`started connecting`
`connection problem, giving up`
`some problem`
X server isn't starting successfully:-
`[20221207-12:08:42] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[20221207-12:08:52] [WARN ] Timed out waiting for X server on display 10 to startup`
But i didn`t have .xorgxrdp.10.log file
`/usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log`
[start_the_X_server.txt](/uploads/3f5fb264393c6b8114351fb0b20504e1/start_the_X_server.txt)
`$ sudo cat ~/.xorgxrdp.log
cat: /home/poker/.xorgxrdp.log: No such file or directory`
`$ ls /home/poker
Desktop Documents Downloads Music Pictures Public Sert Templates thinclient_drives Videos`https://gitlab.freedesktop.org/xorg/xserver/-/issues/1415Intel Gemini Lake (Goldmont Plus) and DSI - Random black screen2022-12-11T14:57:44ZLucas MorenoIntel Gemini Lake (Goldmont Plus) and DSI - Random black screenI've Lenovo D330 with Intel Gemini Lake and DSI.<br>
It has random black screen at startup and rotate (like xrandr -o or sensors, it's an x86 tablet).
Is not a kernel issue and using Wayland rotate without random black screen. <br>
I'm...I've Lenovo D330 with Intel Gemini Lake and DSI.<br>
It has random black screen at startup and rotate (like xrandr -o or sensors, it's an x86 tablet).
Is not a kernel issue and using Wayland rotate without random black screen. <br>
I'm using 5.4 last kernel, newer kernels like 5.10 etc cause total black screen at startup but sound and brightness works.