[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #8 from Peter Hutterer --- Can you reproduce it with upstream libinput? Just build it and run libinput debug-events from the build dir (sudo ./builddir/libinput-debug-events). Run evemu-record after starting debug-events - is the device listed as grabbed? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106674] button scrolling for absolute devices
https://bugs.freedesktop.org/show_bug.cgi?id=106674 --- Comment #30 from Peter Hutterer --- fwiw, I had a few high-priority things come in, so this will take me a while. Feel free to get started on it though. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #6 from Peter Hutterer --- Either way, bugs shouldn't be closed until they're on git master anyway. Patch is pushed now, thanks for testing. commit 07eefba84b1fe46b3e8702ee0db806ddfb80df73 Author: Peter Hutterer <> Date: Mon Jun 4 08:16:48 2018 +1000 udev: the IBM X41 Tablet must not disable the keyboard in tablet mode https://wayland.freedesktop.org/libinput/doc/latest/reporting_bugs.html#fixed_bugs -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 Peter Hutterer changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99174] Chromium/Chrome scroll incorrectly when running in a Wayland session with Xwayland
https://bugs.freedesktop.org/show_bug.cgi?id=99174 --- Comment #2 from Nate Graham --- Thanks! -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98272] Europa Universalis IV, Hearts of Iron IV, and Stellaris fail to display anything on XWayland
https://bugs.freedesktop.org/show_bug.cgi?id=98272 Jason Ekstrand changed: What|Removed |Added Summary|Europa Universalis IV, |Europa Universalis IV, |Hearts of Iron IV, and |Hearts of Iron IV, and |Stellaris fail to display |Stellaris fail to display |anything on Radeon Polaris |anything on XWayland --- Comment #16 from Jason Ekstrand --- I was looking at something almost completely unrelated and I think I came across the root cause of this bug. Currently, XWayland does not advertise support for any multisampled visuals. You can reproduce this trivially with "glxgears -samples 4". Hidden in comment 13 is this nugget: (In reply to pandiculationfinch from comment #13) > 300c302 > < 192 GLX Visuals > --- > > 480 GLX Visuals I think the root cause here is that XWayland loads swrast for indirect GLX instead of figuring out which actual DRI driver to load. Since swrast does not support multisampling, we get no multisampled visuals. I don't really know the internals of XWayland enough to know how to fix that problem but there it is. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766
--- Comment #13 from James Jones ---
> Sure, but the overhead of importing a semaphore into a Vulkan context,
> exporting that as an opaque FD, importing that into GL and then using it,
> seems higher than just importing a fence? Those extensions are also only
> synced for big GL: there's a question at the end concluding that there's no
> use for EGL/ES, since you can already import dma-fence FDs into EGLSync
> objects.
I'm not sure where this import/export/import path comes from? And no, these
are not BigGL only. Can you point to the question you think implies this?
Look at the extension's dependencies section, and the notes in the "functions
added" sections describing which apply to OpenGL Vs OpenGL ES only. They're
explicitly designed for both GLES and GL.
> The compositor can't just take the client's wl_vk_semaphore object and
> instruct all operations using the buffer to signal the semaphore: there may
> be
> more than one (e.g. scanout + media encode), and the compositor doesn't
> necessarily know when queuing those operations that they will be the last
> operations queued on that buffer either. I assume that API of delayed fence
> ->
> syncobj signal chaining would still be prohibitively expensive for you though?
I think this is being over-thought. For the out-fence, you've specified an
event that provides an FD to the client. Instead, you'd probably have a
potentially "empty" wayland sync object thing (Let's please not try to make the
naming slant the debate) pre-associated with the surface at attach time, and
you could send an event when it was safe for the client to wait for it when
releasing as-is (implying it was non-empty when attached), or optionally
include an update to the object that associates a new FD with it (For the case
where it was previously empty, or just needs some new primitive to back it for
whatever reason).
> It sounds like the protocol would need to encode a preference: 'I can take
> dma-fences but it's going to reduce your framerate' vs. 'I can take syncobjs
> but I'm just going to export them straight to fences'. And I have no idea
> which side should 'win' if the compositor prefers one synchronisation model
> and the client prefers another.
I hadn't imagined the client/server would claim support for less-than-ideal
primitives. Similar to DRM-based buffers, you support sync-fd or you don't,
both as a compositor and a client. Presumably this would only really be useful
with hardware-accelerated clients, and just like wl_drm stuff, you just keep
the client API binding (EGL, Vulkan WSI, etc.) and compositor in sync. Apps
that don't reach down to do low-level buffer pushing themselves would be
oblivious, and the handful that hand-code this would support what they support.
If sync fd gets embedded in enough hand-coded apps, it becomes a de-facto
standard for some market. This hasn't actually been a problem with DRM buffers
thus far. I'm just suggesting emulation of roughly that model for
synchronization as well.
> Also, without either a totally omniscient planner ('here's how to recognise
> your scene graph and I guarantee this will work'), or the brute-force model
> we
> use with atomic KMS where we just throw potential configurations at the wall
> in a test-only mode until it finally sticks, we can't really hoist things
> into
> overlays. There's also the need for atomic modesetting, hotplug
> notifications,
> and so forth.
I'm really trying to avoid debating the merits of a Vulkan compositor (It was
just an example), but Vulkan direct-to-display has atomic modesetting (you can
atomically present multiple swapchains, share images between swapchains), and
display hotplug notification.
It would not be hard to write an extension that let's direct-to-display
swapchain images be shareable or client-allocated. It's only hard to share
swapchain images in the general swapchain case, not for specific swapchain
backends/VkSurface types. I may write this at some point anyway for other
reasons, but I've been waiting for an urgent use case to justify it.
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766
--- Comment #12 from Daniel Stone ---
(In reply to James Jones from comment #9, and also comment #11)
> Yes, the overhead is in the ioctls needed to instantiate a sync object into
> a usermode driver or another command queue in our kernel driver. It's
> relatively expensive on NV hardware when not using a global GPU virtual
> address space.
>
> There's an API to import general Vulkan sync primitives (Including dma
> fences/sync FDs, but also persistent-style Vulkan semaphores) directly to GL
> via the GL/Vulkan interop extensions which I believe Mesa supports.
Sure, but the overhead of importing a semaphore into a Vulkan context,
exporting that as an opaque FD, importing that into GL and then using it, seems
higher than just importing a fence? Those extensions are also only synced for
big GL: there's a question at the end concluding that there's no use for
EGL/ES, since you can already import dma-fence FDs into EGLSync objects.
In a pure-Vulkan world, I can see the use for the equivalent of in-fences (from
the compositor's PoV, what would be the signal semaphore of vkQueuePresentKHR's
operation) to associate with wl_surface_attach using sync objects; it seems
pretty obvious that the client would create it early (unsignaled), queue one
signaling operation, and then the compositor would queue at least one wait
operation.
But for the equivalent of out-fences (semaphore parameter to
vkAcquireNextImageKHR, associated with wl_buffer_release), not so much? The
compositor may queue at least one operation which would be the semaphore for
the image inside vkAcquireNextImage. This might be an EGLSync/dma-fence
signaling after the last EGL/GLES operation sourcing from the buffer, or a
dma-fence from KMS, or a VkSemaphore from Vulkan composition. It looks like
we'd need new API for the kernel, which would signal a syncobj when a
particular collection of dma-fences had all signaled.
The compositor can't just take the client's wl_vk_semaphore object and instruct
all operations using the buffer to signal the semaphore: there may be more than
one (e.g. scanout + media encode), and the compositor doesn't necessarily know
when queuing those operations that they will be the last operations queued on
that buffer either. I assume that API of delayed fence -> syncobj signal
chaining would still be prohibitively expensive for you though?
> -Explicitly name the type of the FD being registered. If dma-fence/sync FD
> is the only type available in rev1, that's fine, but it's an easily
> extensible API.
It sounds like the protocol would need to encode a preference: 'I can take
dma-fences but it's going to reduce your framerate' vs. 'I can take syncobjs
but I'm just going to export them straight to fences'. And I have no idea which
side should 'win' if the compositor prefers one synchronisation model and the
client prefers another.
> KMS may need sync FDs, but not all compositing happens in KMS. There's also
> the hypothetical-at-this-point Vulkan-only compositor implementation that
> doesn't use KMS.
To be honest, it's not really clear to me at the moment what a Vulkan
composition model would look like, so it's hard to say. For example, as far as
I can tell there's no way to directly present VkImages with VK_KHR_display,
only the result of the compositor's own Vulkan rendering, which means we can't
usefully use overlay planes in a compositor yet.
Also, without either a totally omniscient planner ('here's how to recognise
your scene graph and I guarantee this will work'), or the brute-force model we
use with atomic KMS where we just throw potential configurations at the wall in
a test-only mode until it finally sticks, we can't really hoist things into
overlays. There's also the need for atomic modesetting, hotplug notifications,
and so forth.
Maybe standing up a demo of how a VK_KHR_display-based compositor could look
would be enlightening.
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766 --- Comment #11 from James Jones --- Not proposing baking in any particular backend assumptions or debating whether Khronos or Linux assumptions are better, but rather I was indirectly suggesting a few modifications to make the overall extension less dependent on any particular type, and allow persistence -Register fences as a new wayland object type prior to actual attachment, similar to how wl_surface abstracts DRM/shm/etc. This makes persistence easy when the underlying objects support it, and since apparently wayland object creation is cheap, shouldn't add appreciable overhead where persistence doesn't matter or doesn't work. -Explicitly name the type of the FD being registered. If dma-fence/sync FD is the only type available in rev1, that's fine, but it's an easily extensible API. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766 --- Comment #10 from Jason Ekstrand --- (In reply to James Jones from comment #9) > Yes, the overhead is in the ioctls needed to instantiate a sync object into > a usermode driver or another command queue in our kernel driver. It's > relatively expensive on NV hardware when not using a global GPU virtual > address space. I agree that there are some ways in which the sync file ioctls could be more efficient. Our driver does N-1 sync file merge operations ioctls on each submit which isn't great especially if the compositor has dozens of clients each handing it sync files. If we had a multi-merge ioctl, maybe a bunch of this overhead would go away. > There's an API to import general Vulkan sync primitives (Including dma > fences/sync FDs, but also persistent-style Vulkan semaphores) directly to GL > via the GL/Vulkan interop extensions which I believe Mesa supports. Some mesa drivers support it but not all. In general, we seem to be getting back to the same discussion as EGLStreams about whether we build Wayland on top of Khronos APIs or Linux APIs. Even if both Vulkan and GL support said extension, what about KMS? What about some video encode API? The advantage of sync_file is that it's supported everywhere and allows multiple components from multiple vendors to synchronize between each other. Fun fact: at one point in time, there was a KMS-only (no 3D API involved) Weston back-end for the raspberry pi. > KMS may need sync FDs, but not all compositing happens in KMS. There's also > the hypothetical-at-this-point Vulkan-only compositor implementation that > doesn't use KMS. Having Weston/Mesa/Mutter/etc. support only KMS and even > only sync FDs/dma-fences is the current design norm, but baking that > assumption in the protocol is another thing. We have to bake some set of assumptions in. We can bake in Linux/Android assumptions around sync_file or we can bake in Khronos API assumptions around GL, Vulkan, EGL, etc. The question isn't if we bake in assumptions, it's which assumptions we bake in. When we already have fairly well standardized APIs for modesetting and cross-component synchronization, why is the answer to keep wrapping them in more and more layers of Khronos APIs until EGL rules the world? By the way, I'm not arguing that you don't have a real problem which really needs solving. I'm well aware of the problem and it badly needs solving! I just question the solution of adding more EGL (or Vulkan WSI). -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766 --- Comment #9 from James Jones --- Yes, the overhead is in the ioctls needed to instantiate a sync object into a usermode driver or another command queue in our kernel driver. It's relatively expensive on NV hardware when not using a global GPU virtual address space. There's an API to import general Vulkan sync primitives (Including dma fences/sync FDs, but also persistent-style Vulkan semaphores) directly to GL via the GL/Vulkan interop extensions which I believe Mesa supports. KMS may need sync FDs, but not all compositing happens in KMS. There's also the hypothetical-at-this-point Vulkan-only compositor implementation that doesn't use KMS. Having Weston/Mesa/Mutter/etc. support only KMS and even only sync FDs/dma-fences is the current design norm, but baking that assumption in the protocol is another thing. The core wayland protocols aimed for platform independence, and this seems like something that's likely to become a relatively central concept in Wayland frame delivery in the future. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766 --- Comment #8 from Daniel Stone --- (In reply to James Jones from comment #7) > The protocol: > > https://lists.freedesktop.org/archives/wayland-devel/2017-September/035080. > html > > Doesn't seem to support the persistent object model that would be more > performant if using something like Vulkan semaphores to perform the > synchronization, and requires dma-fence. Isn't preferable to write this in > a way that doesn't require a specific type of primitive and doesn't require > transmitting/setting up a fence FD on every frame? We could rewrite it to use a persistent syncobj I suppose, but I don't understand the performance argument in all honesty. Is it just the overhead of importing and exporting dma-fences on your driver? Ultimately we need a dma-fence to work with KMS anyway, so Weston at least would probably just turn straight around and export the syncobj to a fence if the client was being displayed in a plane on the display controller. Unless I've missed something (please point me to it if so?) we also don't have an extension for EGL to ingest syncobjs, so we'd need export for that anyway. If the performance argument is just about creating Wayland objects, I'm intensely relaxed about that. Creating objects does not require a roundtrip, and we already have a lot of throwaway objects, e.g. in the dmabuf extension where we create a new object just to take the buffer parameters and discard it as soon as the buffer is created. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98766] We need fences support in Wayland compositors
https://bugs.freedesktop.org/show_bug.cgi?id=98766 --- Comment #7 from James Jones --- The protocol: https://lists.freedesktop.org/archives/wayland-devel/2017-September/035080.html Doesn't seem to support the persistent object model that would be more performant if using something like Vulkan semaphores to perform the synchronization, and requires dma-fence. Isn't preferable to write this in a way that doesn't require a specific type of primitive and doesn't require transmitting/setting up a fence FD on every frame? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106736] With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop
https://bugs.freedesktop.org/show_bug.cgi?id=106736 --- Comment #16 from Eero Tamminen --- (In reply to Pekka Paalanen from comment #15) > Oh right, like Michel Dänzer said in IRC, the repaint-window should probably > be dynamically adjusted based on performance. That would be a nice research > project. Do you think that could be the solution, Eero? It definitely seems something worth trying. (In reply to Pekka Paalanen from comment #14) [...] > Variable refresh rate is an aid to let keep vsync on. > > I only recently saw a discussion about how variable refresh rate should be > exposed in KMS UABI. Therefore I believe there is no UABI for it yet, which > means that nothing on DRM KMS can make use of it yet. Oh, I had no idea one needs Windows for that. :-/ While games are not really my thing [1], I would image gamers to want 144Hz monitor with "FreeSync" and configure the game so that he gets somewhere between e.g. 72-144Hz update frequency with variable Vsync rate. However, something like that should be done with fullscreen / compositor bypass. [1] I'm more into emulators (one of the maintainers for one), those also need Vsync differing from 60Hz (in my case 50 or 71). Because those frequencies are fixed during emulator run, changing whole display refresh rate would be one option there, but "FreeSync" would be nice there too. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 93237] Spontaneous keyboard layout switching after upgrade to XWayland 1.18.0
https://bugs.freedesktop.org/show_bug.cgi?id=93237 --- Comment #7 from Simon Volpert --- (In reply to Daniel Stone from comment #6) > Simon, is Jonas's comment helpful for you at all? To be honest, not very much. Firstly, the described process is too complicated for me to reproduce. Secondly, the general context of the bug i was experiencing was different; I was using a typical set of programs (Firefox, weston-terminal, LibreOffice) under the Weston compositor, so no weird window manager nesting for me. Thirdly, i have since given up on Wayland, for now, and switched back to X.Org, in an attempt to work around its problems and get some useful stuff done. Sorry! -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106734] Fullscreen GL applications aren't visible with Xwayland, or there's a panel on top (under Weston)
https://bugs.freedesktop.org/show_bug.cgi?id=106734 Eero Tamminen changed: What|Removed |Added Severity|normal |major Priority|medium |high --- Comment #3 from Eero Tamminen --- (In reply to Olivier Fourdan from comment #2) > Reproduced under weston, yet the same works fine GNOME on Wayland → moving > to weston. Increasing importance. Fullscreen (XWayland) windows not being visible is at least high major issue. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #17 from Daniel Stone --- (In reply to Pekka Paalanen from comment #15) > I think the proposal is to make it undefined. That's my suggestion. (In reply to Pekka Paalanen from comment #16) > Ahumm... wl_cursor_image_get_buffer() always returns the same wl_buffer. Not > sure there is a way in the API to get separate wl_buffers, and multiple > wl_surfaces for the same image is very possible by having multiple wl_seats. Ouch. We should definitely fix that. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #16 from Pekka Paalanen --- Ahumm... wl_cursor_image_get_buffer() always returns the same wl_buffer. Not sure there is a way in the API to get separate wl_buffers, and multiple wl_surfaces for the same image is very possible by having multiple wl_seats. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #15 from Pekka Paalanen --- I think the proposal is to make it undefined. You mean one release per attach+commit in mutter, right? So Weston and Mutter implement the opposite behaviours. This means that if a client ever depended on either behaviour, it would malfunction on the other. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #14 from Jonas Ådahl --- FWIW, mutter has implemented the one-release-per-attach semantics, which I've read as the correct way. Is it now meant to be illegal to have a single buffer attached at multiple surfaces? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #5 from Sergey Koziakov --- Oh, right, I wasn't the one who openned issue. Anyways, changes persist trough reboot and work perfectly. Thanks again!. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #4 from Sergey Koziakov --- (In reply to Peter Hutterer from comment #3) > It's a git patch, you're better off doing "git am < patchfile" and git will > take care of it. Otherwise patch -p1 should work too but I'd rather you use > git directly. Installing afterwards is correct but not necessary, you could > just copy the hwdb file over the system one. Yep, I tried again using git patch, and it produced no errors. > The udevadm test messages are fine. What was the bottom of the udevadm test > output though? Did it list the LIBINPUT_MODEL_TABLET_MODE_NO_SUSPEND > property for the keyboard device? It does! For some reason, I tried again using git patch and it works perfectly. Regular keyboard also works (if I stick a finger between lid and case and press some keys when event has triggered they work), but it's not like lid is pressing any buttons or moving a trackpoint, so it's not a problem. I'm going to reboot and see if everything persists, and then close the bug. Thank you! -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #13 from Pekka Paalanen --- That's actually a good point that even wl_shm clients can simply create multiple wl_buffers for the same memory. Yeah, I'm fine with just documenting the current limitation and not solving the issue by complicating protocol. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #7 from Mario --- The way to reproduce the bug using, for example, an external bluetooth device like mine: - stop, in my case, any libinput-gesture instance; - disconnect the device; - launch 'libinput-debug-events' without options; - connect the device. Here on trackpad usage: from the libinput-debug-events output I can see the device to be removed/reattached and the correct events reported; the mouse pointer is completely stuck. If I stop libinput-debug-events, everything starts to work Can you reproduce it? libinput-debug-events output: -event3 DEVICE_ADDED Power Button seat0 default group1 cap:k -event4 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event1 DEVICE_ADDED Power Button seat0 default group3 cap:k -event0 DEVICE_ADDED Lid Switchseat0 default group4 cap:S event0 SWITCH_TOGGLE +0.01s switch lid state 1 -event2 DEVICE_ADDED Sleep Button seat0 default group5 cap:k -event6 DEVICE_ADDED Yubico Yubikey NEO OTP+U2F+CCID seat0 default group6 cap:k -event7 DEVICE_ADDED ELAN Touchscreen seat0 default group7 cap:t size 305x170mm calib -event22 DEVICE_ADDED Integrated_Webcam_HD: Integrate seat0 default group8 cap:k -event12 DEVICE_ADDED DLL0704:01 06CB:76AE Touchpad seat0 default group9 cap:pg size 101x57mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on -event21 DEVICE_ADDED Webcam C170: Webcam C170 seat0 default group10 cap:k -event23 DEVICE_ADDED Trackpad di MkMiniseat0 default group11 cap:pg size 132x112mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger -event8 DEVICE_ADDED Apple Inc. Apple Keyboard seat0 default group12 cap:k -event9 DEVICE_ADDED Apple Inc. Apple Keyboard seat0 default group12 cap:k -event15 DEVICE_ADDED HDA Intel PCH Headphone Mic seat0 default group13 cap: -event16 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=3 seat0 default group13 cap: -event17 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=7 seat0 default group13 cap: -event18 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=8 seat0 default group13 cap: -event19 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=9 seat0 default group13 cap: -event20 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=10 seat0 default group13 cap: -event10 DEVICE_ADDED Intel HID events seat0 default group14 cap:k -event13 DEVICE_ADDED Dell WMI hotkeys seat0 default group15 cap:k -event5 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group16 cap:k -event23 DEVICE_REMOVED Trackpad di MkMiniseat0 default group11 cap:pg size 132x112mm -event23 DEVICE_ADDED Trackpad di MkMiniseat0 default group17 cap:pg size 132x112mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger event23 POINTER_MOTION +23.96s0.13/ 0.00 event23 POINTER_MOTION +23.98s0.20/ 0.00 event23 POINTER_MOTION +24.07s0.00/ 0.17 event23 POINTER_MOTION +24.10s -0.36/ 0.18 event23 POINTER_MOTION +24.13s -0.48/ 0.00 event23 POINTER_MOTION +24.14s -0.52/ -0.54 event23 POINTER_MOTION +24.15s -0.58/ -0.60 event23 POINTER_MOTION +24.16s
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #6 from Peter Hutterer --- tbh, no idea where this comes from. libinput itself doesn't grab the device, libinput debug-events has an option to grab it but it's off by default. libinput-gestures doesn't appear to be using that option though. And I can certainly run two libinput debug-events instances here without issues. I can't find anything in the libinput-gestures git history that used a grab, so *shrugh* I don't know, sorry. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #3 from Peter Hutterer --- It's a git patch, you're better off doing "git am < patchfile" and git will take care of it. Otherwise patch -p1 should work too but I'd rather you use git directly. Installing afterwards is correct but not necessary, you could just copy the hwdb file over the system one. Whether the lid keys are mapped to anything doesn't really matter to libinput at least, but depending what they're mapped to X may filter them. What does evemu-record say about the buttons on the lid? The udevadm test messages are fine. What was the bottom of the udevadm test output though? Did it list the LIBINPUT_MODEL_TABLET_MODE_NO_SUSPEND property for the keyboard device? What does libinput debug-events --verbose say when you run it now? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #5 from Mario --- Ok, it looks that the problem is the use of libinput-gestures (that uses libinput-debug-events to gather events). Let's see what I discovered step-by-step: $ evemu-record /dev/input/event23 error: this device is grabbed and I cannot record events see the evemu-record man page for more information $ fuser -v /dev/input/event23 USERPID ACCESS COMMAND /dev/input/event23: mario 1353 F libinput-debug- mario 1389 F gnome-shell $ ps aux | grep libinput mario 1337 0.1 0.0 41556 11856 ?Ss 11:35 0:00 /usr/bin/python3 /home/mario/.bin/libinput-gestures mario 1353 0.2 0.0 35736 4252 ?S11:35 0:00 libinput-debug-events $ systemctl --user stop libinput-gestures.service (external trackpad started to work! the internal one of the XPS 13 worked in any case with any version of libinput) $ systemctl --user start libinput-gestures.service (now libinput-gestures gather gestures from both the trackpads) It looks something changed in libinput and this create badly conflict with the (weird) method used by libinput-gestures to gather event notifications. Note the I use libinput-gestures option 'device all' in order to catch events from multiple devices: including the device attached after service launch. I think this is the schedule in my system: - libinput-gestures launch libinput-debug-events; - the external bluetooth device is later connected. Is it normal that libinput doesn't make the external device to work if an instance of libinput-debug-events is running? As proof of this: if after the previous steps (so with everything working) I switch off the bluetooth trackpad, wait some seconds and reconnect it: the problem is there again. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #2 from Sergey Koziakov --- I forgot to add that after all that, lid keys still don't work when transformed. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106799] IBM x41 tablet must not disable the keyboard in tablet mode
https://bugs.freedesktop.org/show_bug.cgi?id=106799 --- Comment #1 from Sergey Koziakov --- Hello! Thank you very much. I am not sure if I'm doing everything correctly, so here is what I am doing: 1. I have applied patch (with 'patch < patchname.patch`) to the source code (patch was in repository root, but said it can't find a file, so I provided it a path to the file) and built and installed libinput according to official build instructions. I realize now that it's silly, but at first I couldn't found libinput's hwdb file. 2. I updated hwdb file on-disk and ran 'udevadm trigger' for event devices 4 and 5 (keyboard and additional buttons which include tablet switch event). 3. I then ran 'udevadm test' for those devices. There are few lines that bothered me in the output, here are they: PROGRAM 'libinput-device-group /sys/devices/platform/i8042/serio0/input/input10/event4' /usr/lib/udev/rules.d/80-libinput-device-groups.rules:7 starting 'libinput-device-group /sys/devices/platform/i8042/serio0/input/input10/event4' 'libinput-device-group /sys/devices/platform/i8042/serio0/input/input10/event4'(out) '11/1/1:isa0060/serio0' Process 'libinput-device-group /sys/devices/platform/i8042/serio0/input/input10/event4' succeeded. IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:32 2 character(s) replaced IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:36 IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:40 IMPORT builtin 'hwdb' returned non-zero and PROGRAM 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input6/event5' /usr/lib/udev/rules.d/80-libinput-device-groups.rules:7 starting 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input6/event5' 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input6/event5'(out) '19/1014/5054:thinkpad_acpi' Process 'libinput-device-group /sys/devices/platform/thinkpad_acpi/input/input6/event5' succeeded. 2 character(s) replaced IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:36 IMPORT builtin 'hwdb' returned non-zero IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/90-libinput-model-quirks.rules:40 IMPORT builtin 'hwdb' returned non-zero I'm not sure if it is ok, so I decided I should attach this. 4. Those lid buttons don't have keycodes at first, so I used 'setkeycodes' to give them keycodes. I tried using udev/hwdb rule in past, but it didn't work at all. Am I doing something wrong? Did I forgot some step or something? Thanks again. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75390] Weston's gl-renderer affected by GL_MAX_TEXTURE_SIZE
https://bugs.freedesktop.org/show_bug.cgi?id=75390 Daniel Stone changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #3 from Daniel Stone --- Right, it would be an error for clients to resize themselves larger than GL's declared limits and expect it to work. There's nothing we can do in the compositor or protocol to steer them away from this. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 77769] Add touch support to weston's Wayland backend
https://bugs.freedesktop.org/show_bug.cgi?id=77769 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Daniel Stone --- This landed ages ago. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 78585] multiple monitor fullscreen images incorrect position/scale
https://bugs.freedesktop.org/show_bug.cgi?id=78585
Daniel Stone changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #16 from Daniel Stone ---
I'm closing this on the grounds that it's probably been fixed with the new
('new') xdg_shell protocol which is used in place of wl_shell, and that we
haven't had new information in four years.
--
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 81316] cursor sometimes remains on screen after weston-launch quits
https://bugs.freedesktop.org/show_bug.cgi?id=81316 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Daniel Stone --- We now clear out the cursor more aggressively. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83055] weston freezes temporarly
https://bugs.freedesktop.org/show_bug.cgi?id=83055 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Daniel Stone --- Based on what's written, I strongly suspect that qml-compositor is missing some display flushes (e.g. for frame/release events); we've never previously seen the Wayland backend hanging elsewhere. Please reopen if you can still reproduce and debug. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83680] weston-simple-egl fullscreen does not work when output seat specified in weston.ini
https://bugs.freedesktop.org/show_bug.cgi?id=83680 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Daniel Stone --- Presumably this was fixed a while ago, because this is one of my go-to tests for KMS. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 80119] dead/unreachable code at line 643 & 648 of simple-egl.c
https://bugs.freedesktop.org/show_bug.cgi?id=80119 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Daniel Stone --- Not sure what the actual bug is here. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83954] Touch does not work in secondary display after calibration in multihead setup
https://bugs.freedesktop.org/show_bug.cgi?id=83954 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Daniel Stone --- Fixed with the new touch calibrator. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 84960] Weston crashes after "unexpectedly large timestamp jump"
https://bugs.freedesktop.org/show_bug.cgi?id=84960 --- Comment #1 from Daniel Stone --- If you can still reproduce this, can you please try running under Valgrind? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #4 from Peter Hutterer --- very weird. evemu-record shows events? Please attach an event sequence here from that device. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 89674] Touch is not working with transformed output
https://bugs.freedesktop.org/show_bug.cgi?id=89674 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Daniel Stone --- As far as I know, this is now properly supported by the new touchscreen calibrator included with Weston 5.0.0. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 89386] weston-launch ends in tight poll/recvmsg loop when straced and weston terminates
https://bugs.freedesktop.org/show_bug.cgi?id=89386 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 90434] weston's toytoolkit hangs on some versions of Mesa, on some hardware platforms
https://bugs.freedesktop.org/show_bug.cgi?id=90434 Daniel Stone changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Daniel Stone --- I would certainly prefer to fix this by removing non-image Cairo backends, cf. #83878. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 90673] Weston's desktop-shell keybindings don't respect keyboard layout (variant)
https://bugs.freedesktop.org/show_bug.cgi?id=90673 --- Comment #1 from Daniel Stone --- Right, they are bound to keycodes rather than keysyms. Fixing that would certainly be nice, but involve quite a large increase in complexity in shortcut processing. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83881] Generic dmabuf protocol
https://bugs.freedesktop.org/show_bug.cgi?id=83881 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #14 from Daniel Stone --- Let's just close it. Mesa and GStreamer (at least) are using it and the sky doesn't seem to have quite fallen in yet. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 91884] Building Weston (1.8.92) for Raspberry Pi with EGL enabled fails due to missing `libdrm` dependency
https://bugs.freedesktop.org/show_bug.cgi?id=91884 Daniel Stone changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #8 from Daniel Stone --- libdrm is small enough, and our configuration options already bewildering enough, that I don't think this is much of an issue. Beyond that, the recommended Raspberry Pi driver is now VC4 which will use libdrm, and even NVIDIA are providing KMS which requires libdrm. So at this point I don't think there's much use in avoiding it. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 85475] Copy and paste not working properly + crash
https://bugs.freedesktop.org/show_bug.cgi?id=85475 --- Comment #7 from Daniel Stone --- (In reply to Artem Chudinov from comment #6) > Created attachment 118444 [details] [review] > Hacky patch > > This patch helps me, though I don't even know what is XCB_ALLOC_COLOR_PLANES > (I am not familiar with the code). I suppose my patch breaks something, but > I couldn't find what. XCB_ALLOC_COLOR_PLANES is referring to a request. An event numbered 87 must be an extension event: if you run xdpyinfo -queryExtensions, you can find out which extension this would belong to. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 92261] SIGSEGV in weston_surface_destroy
https://bugs.freedesktop.org/show_bug.cgi?id=92261 --- Comment #1 from Daniel Stone --- Are you able to run this under Valgrind, if it's still reproducible? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 92384] Bogus use of wl_surface scaling leads to compositor crash
https://bugs.freedesktop.org/show_bug.cgi?id=92384 --- Comment #2 from Daniel Stone --- Hm, I wonder if the problem here is that the client gets killed by a protocol error; then by the time the xdg_toplevel ping has timed out, the resource is no longer there so we dereference garbage. Can you still reproduce this, and if so, could you please get a Valgrind trace? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 92837] desktop number advertisement and desktop movement
https://bugs.freedesktop.org/show_bug.cgi?id=92837 Daniel Stone changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Daniel Stone --- Closing per Pekka's comment, though it would be possible to build a more complete desktop environment using libweston. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 66830] weston/wayland: Invalid read/write with rdp-backend.so
https://bugs.freedesktop.org/show_bug.cgi?id=66830 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #12 from Daniel Stone --- Assuming this was fixed by the patch. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 97201] Weston crash when touch on exiting application run at fullscreen
https://bugs.freedesktop.org/show_bug.cgi?id=97201 --- Comment #1 from Daniel Stone --- I've not been able to reproduce this myself. Are you able to run weston under Valgrind and provide a trace? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 100946] Not able to remove/hide the titlebar using weston.ini
https://bugs.freedesktop.org/show_bug.cgi?id=100946 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #1 from Daniel Stone --- Right, we do not support a way to do this; clients need to know themselves that they should not draw title bars. You would have to address this in whatever client you are using; each toolkit often has their way to avoid drawing decorations. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 94851] Multiple GPU rendering
https://bugs.freedesktop.org/show_bug.cgi?id=94851 --- Comment #1 from Daniel Stone --- Yeah, whilst Mutter does it, it's not something we've had the developer time to deal with. I don't know that it's on anyone's radar, nor when we could expect to see it. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106442] process /usr/bin/Xwayland consume 100% CPU resources and GUI stop respond
https://bugs.freedesktop.org/show_bug.cgi?id=106442 --- Comment #23 from Olivier Fourdan --- Rawhide (f29) has the fix, see https://bugzilla.redhat.com/show_bug.cgi?id=1579067 -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 103437] Syscall param sendmsg(msg.msg_iov[0]) points to uninitialised byte(s)
https://bugs.freedesktop.org/show_bug.cgi?id=103437 --- Comment #2 from Daniel Stone --- Seb, if this still happens, could you please attach the output of running with 'WAYLAND_DEBUG=client'? That will at least give us a clue which Wayland requests have been made before this happens. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 103894] Synaptic Package Manager and other apps that want to display as root will not run on wayland by default
https://bugs.freedesktop.org/show_bug.cgi?id=103894 Daniel Stone changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Daniel Stone --- Yes, we'd want to encourage Synaptic to fix their architecture. If you look at, e.g. GNOME Software, that uses PackageKit as a privileged backend and runs the UI unprivileged. I'm pretty sure the same is true of the KDE equivalent. As Pekka says, this is quite a dangerous thing to be doing. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 104050] scrolllock, the only key that can switch keyboard back light can't be activated
https://bugs.freedesktop.org/show_bug.cgi?id=104050 Daniel Stone changed: What|Removed |Added Component|wayland |libinput CC||dan...@fooishbar.org --- Comment #10 from Daniel Stone --- Peter, handballing to you in case you have any bright (groan) ideas. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106736] With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop
https://bugs.freedesktop.org/show_bug.cgi?id=106736 --- Comment #15 from Pekka Paalanen --- Oh right, like Michel Dänzer said in IRC, the repaint-window should probably be dynamically adjusted based on performance. That would be a nice research project. Do you think that could be the solution, Eero? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 49021] Ideas: A wayland settings protocol to tell clients about themes, fonts, etc.
https://bugs.freedesktop.org/show_bug.cgi?id=49021 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Daniel Stone --- Resolved to be handled out of band, rather than forcing it through the window system. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 Daniel Stone changed: What|Removed |Added Component|wayland |weston -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 101806] plasma 5: system settings crashes when I leave desktop effects kcm
https://bugs.freedesktop.org/show_bug.cgi?id=101806 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #5 from Daniel Stone --- Sorry, but please bounce this bug back to KDE. What is happening is that there is an asynchronous thread calling eglSwapBuffers(), using the wl_egl_window + wl_surface objects passed to EGL. KDE/Qt destroy the wl_surface too early and eglSwapBuffers tries to access now-freed memory. It must destroy the EGLSurface (and stop rendering to it!) before it destroys the wl_surface. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106736] With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop
https://bugs.freedesktop.org/show_bug.cgi?id=106736 --- Comment #14 from Pekka Paalanen --- (In reply to Eero Tamminen from comment #13) > (In reply to Pekka Paalanen from comment #11) ... > * If compositor on some platform skips screen updates, that gives unfair > performance advantage (number) on that platform ... > [1] such as compositing, which is 100% memory bandwidth bound and for which > one can actually calculate the expected performance. I understand all the above (including the ones I cut out in the quote) as just more reasons to run benchmarks with vsync on. If one does not actually display every frame, like you said, the compositor overhead will be a random factor since it will be processing some frames but not all. Another way is to increase the benchmark complexity until it just starts missing vblanks. But then again the compositor's design will play a part: a compositor could in its repaint check whether a client buffer is ready, and if it is not, postpone it to the next refresh. This is actually something I would like in Weston, so that applications could not delay screen updates arbitrarily and make e.g. pointer cursor motion choppy. So really, maybe benchmarks should be using fences and reading their completion timestamps to figure out how long it took to execute a GPU task. Since most GPUs still don't really pre-empt, that should be quite robust against compositor overheads. > > Games need to be designed to have vsync on. > > Problem is that games have variable frame rate and people like to crank > settings as high as possible. They also have higher than 60 FPS monitor. > > Solutions for avoiding getting only half the FPS with Vsync are either using > FreeSync/Gsync and monitor capable of that, or disabling Vsync. > > Btw. How well Xwayland & Wayland compositors work with FreeSync (and Gsync)? > > (FreeSync has been part of DP & HDMI specs quite a while now.) Variable refresh rate is an aid to let keep vsync on. I only recently saw a discussion about how variable refresh rate should be exposed in KMS UABI. Therefore I believe there is no UABI for it yet, which means that nothing on DRM KMS can make use of it yet. > > However, Weston will never tear on presenting to screen, and Weston will > > never sample from a client buffer that has not finished drawing (implicit > > fencing). > > Windows (at last with Intel drivers) lets rendering tear if application is > both fullscreen and has disabled Vsync. I think this is reasonable, as > compositor shouldn't then be involved. Disabling Vsync kind of means that > application and/or user doesn't care about tearing. I think that could be possible to implement, provided two things: - the compositor has a working composite bypass path and the fullscreen window hits it - the compositor actually knows the applications has "disabled vsync" (currently there is no way to know reliably) However, disabling vsync by setting eglSwapInterval=0 is not a reliable indication that the application actually wants to tear: Wayland applications can do it to be sure that eglSwapBuffers does not block unnecessarily while they still want vsync and handle frame syncing manually. Do you have ideas how to fix the issues you reported? I'm not sure what to do. An application posts a GPU task that is so long that it forces the compositor to miss the vblank, decimating the compositor's framerate. We could protect the compositor's framerate from being decimated by a) not using client buffers that are not finished drawing (with explicit fences), and b) have the compositor GPU task pre-empt any applications GPU tasks. We'd need both to ensure the compositor can update in time, but it won't change the fact that the compositor will only update once for each vblank. However, solution a) probably has the drawback that if the application is unthrottled and hammering the compositor with new frames, the compositor might never have a finished client buffer when it repaints because the client has replaced it with a new one already. So the compositor would have to hold on to some buffer to ensure it gets finished and can be shown. Then again, I question the sensibility of optimizing a system for unnatural benchmarks in the first place. I really want to push the world away from the "maximize fps at all costs" mentality that means that games waste power by drawing frames that will never be shown. VR would probably be a very good setting to improve the display pipeline: it demands vsync, high framerate (because the actual displays are high framerate), and low latency. I think would be much better to optimize for that instead of traditional benchmarks that don't care if a frame gets shown. With VR there is simply no room to waste power by drawing frames you never see. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org
[Wayland-bugs] [Bug 106442] process /usr/bin/Xwayland consume 100% CPU resources and GUI stop respond
https://bugs.freedesktop.org/show_bug.cgi?id=106442 --- Comment #22 from Daniel Stone --- Two patches which fix this issue very slightly differently are not yet in a release, but are in master: https://cgit.freedesktop.org/xorg/xserver/commit/?id=3da999a0390407d512bf784e4faf01482bfff9ea https://cgit.freedesktop.org/xorg/xserver/commit/?id=4d5950ce14676f970d9de97380929a93948b98f2 -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 97932] wl_shell: Does not emit configure event
https://bugs.freedesktop.org/show_bug.cgi?id=97932 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Daniel Stone --- Sure thing. Let's close this then; Nicolas, please reopen if it's still happening for you. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98887] Random, one second blank external screen upon window activation or keypress
https://bugs.freedesktop.org/show_bug.cgi?id=98887 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #6 from Daniel Stone --- If this is still happening for you, could you please file a KMS bug report, following the instructions here? https://01.org/linuxgraphics/documentation/how-report-bugs -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99635] It is impossible to screenshot a user selected window.
https://bugs.freedesktop.org/show_bug.cgi?id=99635 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Daniel Stone --- GNOME now implements PipeWire doing exactly this, in part driven by the Flatpak-portal usecase I mentioned above. It's not fully complete, but discussing it with them would be the best way to go about getting it fully functional. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 84644] Can't play FPS games with Xwayland EG CS:GO Etc
https://bugs.freedesktop.org/show_bug.cgi?id=84644 Bug 84644 depends on bug 84014, which changed state. Bug 84014 Summary: Pointer locking protocol https://bugs.freedesktop.org/show_bug.cgi?id=84014 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 84014] Pointer locking protocol
https://bugs.freedesktop.org/show_bug.cgi?id=84014 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Daniel Stone --- At this point we can probably close it ... :) -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 96871] Only native resolution available with Wayland (mirroring impossible)
https://bugs.freedesktop.org/show_bug.cgi?id=96871 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #1 from Daniel Stone --- Can you please file this bug at https://gitlab.gnome.org/GNOME/mutter ? That would be a feature request for them. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 97932] wl_shell: Does not emit configure event
https://bugs.freedesktop.org/show_bug.cgi?id=97932 --- Comment #3 from Quentin "Sardem FF7" Glidic --- Considering the symptoms and the date, this was probably fixed in commit 72f68c53eaad0829f9d14f62bb72a0db237983f4. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75303] Protocol: wl_buffer.release is racy
https://bugs.freedesktop.org/show_bug.cgi?id=75303 --- Comment #12 from Daniel Stone --- At this point, I think it would be more simple to document it as a limitation that attaching the same wl_buffer to two wl_surfaces has inherent race conditions and is thus a bad idea, and move on with our lives. EGL clients can't ever access the buffer. dmabuf clients can just create a new buffer referring to the same storage and do refcounting client side; ditto SHM clients. So do we have a good usecase for multi-attach with a hard limit of one buffer object? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106442] process /usr/bin/Xwayland consume 100% CPU resources and GUI stop respond
https://bugs.freedesktop.org/show_bug.cgi?id=106442 --- Comment #21 from mikhail.v.gavri...@gmail.com --- (In reply to Daniel Stone from comment #20) > That sounds much more like a Mesa/amdgpu-kernel issue to me. Could you > please open a separate issue to track that? In the meantime, I'll mark this > as fixed as a patch for the original issue has been merged. Please wait... In which xorg-x11-server version was applied patch from comment #c11? I am curious because xorg-x11-server 1.20 which shipped in Fedora 29 (Rawhide) not contain this patch. And I need every time after mesa upgrade in distribution rebuild xorg-x11-server packages with this patch. I would like to not spend more for this time. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 75382] Implement wl_probe, or something similar
https://bugs.freedesktop.org/show_bug.cgi?id=75382 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #13 from Daniel Stone --- This did eventually land in wayland-protocols. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #3 from Mario --- Created attachment 140002 --> https://bugs.freedesktop.org/attachment.cgi?id=140002=edit 'libinput debug-events --verbose' output with interaction with the MTP -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106786] Magic Trackpad stopped to work with libinput 1.10.7
https://bugs.freedesktop.org/show_bug.cgi?id=106786 --- Comment #2 from Mario --- (In reply to Peter Hutterer from comment #1) > What does libinput debug-events --verbose say when you interact with the > device? Nothing. See the new attachment. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 89702] Centered/Splash shell surfaces
https://bugs.freedesktop.org/show_bug.cgi?id=89702 --- Comment #2 from Daniel Stone --- Yeah, a splash-screen window class would be the way to do this, but honestly we mostly just don't have splash screens in the first place these days. There is no other way to anchor yourself to the centre of the screen. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 48991] ICCCM: "no kb focus please" mechanism
https://bugs.freedesktop.org/show_bug.cgi?id=48991 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Daniel Stone --- I believe this is now implicit in surface types. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83431] Integrate a better protocol document generator
https://bugs.freedesktop.org/show_bug.cgi?id=83431 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Daniel Stone --- We do at least have cross-references, though they aren't great. The website in general probably needs some help. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83429] Wayland documentation meta-bug
https://bugs.freedesktop.org/show_bug.cgi?id=83429 Bug 83429 depends on bug 83431, which changed state. Bug 83431 Summary: Integrate a better protocol document generator https://bugs.freedesktop.org/show_bug.cgi?id=83431 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 48997] EWMH: Protocol for specifying title bar rectangle
https://bugs.freedesktop.org/show_bug.cgi?id=48997 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Daniel Stone --- We don't have a close-button rectangle, but it's seemingly not actually been necessary. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 81071] Generating keyboard events
https://bugs.freedesktop.org/show_bug.cgi?id=81071 --- Comment #4 from Daniel Stone --- That being said, we'd vastly prefer a compositor mechanism than allowing arbitrary clients to snoop on and inject events, since the latter is a security issue. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 48994] EWMH: move to workspace, keep on top, on all workspaces, minimize etc
https://bugs.freedesktop.org/show_bug.cgi?id=48994 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Daniel Stone --- Calling this fixed with xdg_shell (and we did have a 'show window menu'). -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 73076] Corruption in weston using drm or wayland backends
https://bugs.freedesktop.org/show_bug.cgi?id=73076 Daniel Stone changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW |RESOLVED --- Comment #6 from Daniel Stone --- I believe this would be an error in the GBM implementation, but either way this should be fixed now since others have managed to run it fine on similar hardware. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 48992] EWMH: configure should provide dx_left, dx_right, dy_top, dy_bottom...
https://bugs.freedesktop.org/show_bug.cgi?id=48992 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Daniel Stone --- Calling this fixed with xdg_shell. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99619] weston-terminal crashes on gnome
https://bugs.freedesktop.org/show_bug.cgi?id=99619 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Daniel Stone --- This works for me and has for quite a while. If you can still reproduce it, can you please provide a backtrace from coredumpctl? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 96841] Recover from eglSwapBuffers() errors in gl_renderer_repaint_output()
https://bugs.freedesktop.org/show_bug.cgi?id=96841 Daniel Stone changed: What|Removed |Added CC||mic...@daenzer.net --- Comment #2 from Daniel Stone --- *** Bug 99546 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99546] Screen freezes after DRM_IOCTL_MODE_PAGE_FLIP failure for client buffer
https://bugs.freedesktop.org/show_bug.cgi?id=99546 Daniel Stone changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #3 from Daniel Stone --- Marking as a duplicate of #96841, which notes the same fundamental issue and talks about how to recover from it. *** This bug has been marked as a duplicate of bug 96841 *** -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 96841] Recover from eglSwapBuffers() errors in gl_renderer_repaint_output()
https://bugs.freedesktop.org/show_bug.cgi?id=96841 --- Comment #1 from Daniel Stone --- The backend repaint has the same issue: if, e.g., an atomic commit fails, then we just go into stasis for that output until you do something drastic like VT switching. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 98373] vaapi-recorder fails on RGB to YUV conversion on ivb
https://bugs.freedesktop.org/show_bug.cgi?id=98373 --- Comment #1 from Daniel Stone --- Does any RGB -> YUV VA-API pipeline work on your hardware? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99174] Chromium/Chrome scroll incorrectly when running in a Wayland session with Xwayland
https://bugs.freedesktop.org/show_bug.cgi?id=99174 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #1 from Daniel Stone --- This is being tracked in Chromium, and it's certainly their issue: https://bugs.chromium.org/p/chromium/issues/detail?id=712737 -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106573] When kwin_wayland tries to start XWayland, XWayland hangs with endless inet6-related errors
https://bugs.freedesktop.org/show_bug.cgi?id=106573 --- Comment #14 from Daniel Stone --- It's worth noting that adding -nolisten options from the compositor doesn't work, because if that option isn't available (e.g. '-nolisten tcp6' when you've built without IPv6 support), failure to not listen will be a hard error. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106546] crashed when no one was at home
https://bugs.freedesktop.org/show_bug.cgi?id=106546 --- Comment #12 from Daniel Stone --- Hmm. Do you have an external monitor connected, and if so, how is it connected? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 103282] XWayland refresh rate locked to 60 Hz
https://bugs.freedesktop.org/show_bug.cgi?id=103282 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Daniel Stone --- Resolving as fixed with the Xwayland Present implementation in 1.20; the Mutter 60Hz issue is a bug in Mutter which is being tracked there. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106573] When kwin_wayland tries to start XWayland, XWayland hangs with endless inet6-related errors
https://bugs.freedesktop.org/show_bug.cgi?id=106573 --- Comment #13 from Olivier Fourdan --- (In reply to Pekka Paalanen from comment #12) > (In reply to Olivier Fourdan from comment #11) > > Xorg/Xwayland will acquire the lock as it always do in the "normal" case, I > > do not see this as a bug in kwin. > > So the error about unix listening socket failing is just a red herring and > it creates another socket that works? Assuming I guess correctly what the > messages pointed to in comment #7 mean. That's what “-displayfd” does, it “tries” to open the socket and if it fails, tries the next one. So if you have an Xserver already running on :0, you will get those messages once. If you have 2 xservers on :0 and :1, you'll get those messages twice, so on and so forth... Example: $ Xwayland -displayfd 2 & _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running ✔ ~/src/wayland/xserver [master ↑·10|…141⚑ 33] 1 ← This is Xwayland writing to stderr (fd 2) the display number it found, I have already an Xserver running on :0, so it found one available on :1 $ Xwayland -displayfd 2 & _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running 2 ← ditto, it found :2 available after trying :0 and :1, hence twice the messages $ Xwayland -displayfd 2 & _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running 3 ← ditto, it found :3 available after trying :0, :1 and :2 which were already used... -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 106442] process /usr/bin/Xwayland consume 100% CPU resources and GUI stop respond
https://bugs.freedesktop.org/show_bug.cgi?id=106442 Daniel Stone changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #20 from Daniel Stone --- (In reply to Olivier Fourdan from comment #17) > (In reply to mikhail.v.gavrilov from comment #14) > > Today this problem happened on patched system. > > But case was different: > > 1. launch Firefox > > 2. switch firefox in fullscrenn mode by F11 > > -- here GUI hung and gnome-shell process begin consume 100% > > I got backtrace from gnome-shell process and after it Xwayland begins > > consume 100% > > > > All backtraces attached below. > > I reckon this is a different issue. That sounds much more like a Mesa/amdgpu-kernel issue to me. Could you please open a separate issue to track that? In the meantime, I'll mark this as fixed as a patch for the original issue has been merged. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 84644] Can't play FPS games with Xwayland EG CS:GO Etc
https://bugs.freedesktop.org/show_bug.cgi?id=84644 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Daniel Stone --- (In reply to BNolet from comment #10) > The main issue is that the pointer is not semi-locked to the center of the > screen. The way most FPS games work is that the mouse gets brought back to > the center of a screen based on a certain refresh rate determined by the > game. > > Not too familiar with any of the protocols or exact coding but I believe > there's some sort of call that the game actually performs to the mouse that > will determine how many times in a second that mouse position is read and > then returned to the center. Right, doing this is in fact supported in Xwayland, as long as your compositor provides the appropriate extensions. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 100152] QGIS : erroneous mouse comportement
https://bugs.freedesktop.org/show_bug.cgi?id=100152 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Daniel Stone --- Closing as this bug should be fixed; please reopen if it is still happening for you. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99490] xhost +local: should work
https://bugs.freedesktop.org/show_bug.cgi?id=99490 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Daniel Stone --- Closing this bug as it should work fine; please reopen if you are still having issues. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 99853] Clipboard of legacy Xorg apps and Wayland compositor sometimes desyncs
https://bugs.freedesktop.org/show_bug.cgi?id=99853 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |MOVED -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 93237] Spontaneous keyboard layout switching after upgrade to XWayland 1.18.0
https://bugs.freedesktop.org/show_bug.cgi?id=93237 --- Comment #6 from Daniel Stone --- Simon, is Jonas's comment helpful for you at all? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
