01:42 Sharply8872: Hi, I'm having issues with the disable-while-typing feature on my lenovo laptop. The model is an IdeaPad Gaming 3. I came across these threads https://askubuntu.com/questions/1386598/cant-disable-touchpad-while-typing https://forum.manjaro.org/t/disable-touchpad-while-typing-not-working-on-kde-lenovo-thinkbook-16p-g2-libinput/129010 which suggest adding a quirk to classify the device as internal. Is this the correct way to go?
01:43 Sharply8872: here is the output of list-devices: https://bpa.st/3Y6QU
08:28 wlb: weston Merge request !1612 opened by () xdg_surface: avoid weston crash while xdg_surface ack_configure https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1612
13:20 any1: Ping on wayland!368
13:20 any1: !368
13:21 any1: guess I'm doing it wrong
15:06 DemiMarie: Ping on https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/409. It fixes a regression in 1.23 that allows clients to cause the compositor to loop and consume CPU.
15:07 DemiMarie: The actual code change is tiny, but some struct definitions had to be moved around so that a regression test could be added.
16:08 Ermine: Is this the right place to discuss libxkbcommon?
16:13 soreau: I don't know of any place more fitting
16:25 DemiMarie: What is the layout of YUV formats when used with wl_shm?
16:27 Ermine: Ok. So I get a bunch of warnings when building libxkbcommon library docs: https://tpaste.us/paj4 . Should I ignore them?
16:34 DemiMarie: Actually, I filed an issue for that already. I'll make a PR.
16:38 DemiMarie: From an application compatibility perspective, is it okay to require stride and offset for shm buffers to be a multiple of 4, or will that break too many applications?
17:08 kennylevinsen: DemiMarie: it should be a multiple of the block size. I guess a client could post a C8 buffer, although it’s quite unlikely
17:10 bl4ckb0ne: Ermine: looks like harmless doc issue
17:11 psykose: has there been a doc/doxygen/md2man/asciidoc/docbook/whatever build in history where it doesn't print 5,231,252 warnings while running during a build
17:11 bl4ckb0ne: doc is hard y'all
17:20 daniels: DemiMarie: find the most lax allowed behaviour between the widely-used compositors, and that’s the most acceptable restriction
17:20 daniels: Ermine: I’m sure Ran would welcome a PR
17:21 daniels: any1: you’re not doing it wrong, but having the Qt patch submitted to them and accepted would be very good
17:22 any1: daniels: I meant getting the bot to link the MR
17:25 emersion: ah, for that I'd need to set up my bot
17:27 any1: ahh, I thought there was a bot in here already.
17:27 any1: Ugh, submitting patches to Qt is a nuisance. I have to set up 2 accounts? wtf..
17:29 any1: Well, I suppose I only have to set up the account once...
17:30 any1: Imagine a world where you could submit patches via email everywhere
17:31 emersion: maybe we should document the requirements for merging core Wayland protocol changes
17:32 emersion: in practice it's same as wp but I don't think it's written down anywhere?
17:32 daniels: probably just w-p but also ‘don’t do this if you can avoid it’
17:32 emersion: right
18:14 any1: submitting to Qt is not a frictionless experience. No I have to read a legal document and agree to it
18:18 any1: s/No/Now
18:58 DemiMarie: daniels: the problem is that some compositors (Weston) are so lax that I am confident there is a security problem.
18:59 DemiMarie: I was able to cause hilarious results by submitting an XRGB8888 or ARGB8888 (forgot which) buffer with width = stride.
19:01 DemiMarie: kennylevinsen: Can the pixel width and height be in fractional pixels per block?
19:16 kennylevinsen: DemiMarie: the stride has to be an integer number of blocks, and the height is an integer number of strides
19:17 DemiMarie: kennylevinsen: do you mean total image size in bytes?
19:17 DemiMarie: The height can be less than stride and often will be.
19:19 kennylevinsen: I didn’t mean that its value was a multiple of the stride, but that it is the value that the stride is multiplied by to form the image size. All integer.
19:20 kennylevinsen: But for simple formats you have 1 pixel per block, and each pixel is then between one and 8 bytes (c8 is 1, rgb332 is 2, rgb888 is 3, argb8888 is 4, f16 is 8)
19:21 kennylevinsen: Ah sorry you asked about stride and offset alignment. I misread while distracted.
19:24 kennylevinsen: But yeah, with 1, 2 or 3 byte per pixel formats, it’s definitely not guaranteed that the stride or offset is a multiple of 4 pixels
19:28 DemiMarie: kennylevinsen: are those formats incompatible with Pixman?
19:29 DemiMarie: Also, if a block is 2x2 pixels, is an image with an odd width or height allowed.
19:30 any1: pixman can handle stride
19:33 any1: there are some formats that are incompatible with pixman on little endian systems
19:34 any1: err, big endian
19:37 dottedmag:wonders if big-endian will ever end up in the same bin as non-8-bit-byte machines
19:40 kennylevinsen: DemiMarie: good question, not sure. For reference, the main example I can think of for blocks_per_pixel != 1 is YUV formats, which are 2x1
19:44 DemiMarie: kennylevinsen: There are 2x2 YUV formats as well
19:52 kennylevinsen: not sure how pixman would handle formats that are more than 1 px tall. We don't have those wired up in wlroots at least, but things like R8, RGB332, RGB565 and RGB888 work fine (and all have their uses)
20:01 wlb: wayland Merge request !425 opened by () Document that wl_shm.format is not authoritative https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/425
20:10 daniels: DemiMarie: please find it and let me know
20:11 daniels: you can get incorrect rendering for sure, but play stupid games and win stupid prizes; for that you can just misrender with ‘correct’ parameters
20:11 daniels: I don’t believe there’s any security-sensitive issues, but would be very happy to be proven wrong
20:12 DemiMarie: daniels: the "hilarious" results include things like rendering two entire copies of the window, and once I got a segfault under Valgrind
20:12 kennylevinsen: did you file bugs for these? :/
20:12 DemiMarie: I need to
21:16 daniels: rendering two entire copies of the window is expected if you get stride wrong; a segfault is a security issue
21:17 daniels: again, if you want to misrender as a client, then you don’t need to play tricks with stride; you just need to put garbage in there to begin with