xcb_xf86dri_auth_connection(3)
π NAME π
xcb_xf86dri_auth_connection β okay so bestie, this page lives in the XCB Requests manual (that's section 3 of your man pages, iykyk), and the actual one-line description up top isβ¦ literally just a dash. Nothing. Empty. The upstream girlies left it blank, and we're not gonna invent lore that isn't there. π
β¨ SYNOPSIS β¨
First things first, you gotta pull in the header:
#include <xcb/xf86dri.h>
πΈ Request function πΈ
xcb_xf86dri_auth_connection_cookie_t
xcb_xf86dri_auth_connection(xcb_connection_t *conn,
uint32_t screen, uint32_t magic);
π¦ Reply datastructure π¦
typedef struct xcb_xf86dri_auth_connection_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t authenticated;
} xcb_xf86dri_auth_connection_reply_t;
π Reply function π
xcb_xf86dri_auth_connection_reply_t
*xcb_xf86dri_auth_connection_reply(xcb_connection_t *conn,
xcb_xf86dri_auth_connection_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your lil hotline to the server, periodt.screenβTODO: NOT YET DOCUMENTED.Yeah bestie, that's what it says. Nobody wrote it up yet. π«magicβ alsoTODO: NOT YET DOCUMENTED.The docs are giving mystery on purpose, I guess. π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_XF86DRI_AUTH_CONNECTION. This field also shows up in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. It's the little name tag at the party. πsequenceβ the sequence number of the last request processed by the X11 server. Tracking numbers but make it X11. β¨lengthβ the length of the reply, counted in words (and a word is 4 bytes, no cap).authenticatedβTODO: NOT YET DOCUMENTED.That's it. That's the whole description. π
π§ DESCRIPTION π§
β¦and there's literally nothing here. The DESCRIPTION section is empty, bestie. Not me reading a whole blank section like it was gonna tell me the tea. π
π RETURN VALUE π
It hands you back an xcb_xf86dri_auth_connection_cookie_t. Your cookie!! πͺ
Errors? You don't deal with those here β they have to be handled when you call the reply function xcb_xf86dri_auth_connection_reply.
If you'd rather handle errors in the event loop instead, usexcb_xf86dri_auth_connection_unchecked. Go readxcb-requests(3)for the full details, bestie, it's all in there. π«Ά
π ERRORS π
This request does never generate any errors. Not one. Zero. The drama-free icon we all aspire to be. π₯
πΈ SEE ALSO πΈ
Absolutely nothing listed. Crickets. The SEE ALSO is empty, bestie β this page is out here with no friends in the cross-reference department. π¦
π AUTHOR π
Generated from xf86dri.xml. Got corrections or improvements? Contact xcb@lists.freedesktop.org β they're taking notes, fr fr. π
And that's the whole vibe check, bestie β this page is from X Version 11, libxcb 1.17.0, the one and only xcb_xf86dri_auth_connection(3). Now go auth that connection, main character. Slay. π
β¨
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms