[libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
Author: EarnestlyCreated Mar 17, 2023Updated Feb 16, 2026
Labelsbugmissing-log4.22
- 4.22-24-ga5da4d54
For awhile now I've been witnessing a great deal of logging with the messages:
[libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.I have not yet tried to bisect the problem but I did eventually discover this problem only occurs when I use split h or split v.
So to trigger this problem all I need to do is use my keybind to trigger split h or split v and immediately I will get six lines of this log message:
2023-03-17T20:42:00.70455 17/03/23 20:42:00 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
2023-03-17T20:42:00.78653 17/03/23 20:42:00 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
2023-03-17T20:42:01.32601 17/03/23 20:42:01 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
2023-03-17T20:42:01.32739 17/03/23 20:42:01 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
2023-03-17T20:42:01.41734 17/03/23 20:42:01 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.
2023-03-17T20:42:02.84599 17/03/23 20:42:02 - [libi3] ERROR: Surface 0x55ab4795f468 is not initialized, skipping drawing.While the split mode is active (i.e. the indicator on the window is visible) this message will print profusely whenever switching workspaces or interacting with the WM.
Is there anything I could do to try and nail down the reason why this might be happening?
Source: i3/i3