aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAge
* ipc: add LIBINPUT_CONFIG_ACCEL_PROFILE_CUSTOM entryv1.8Libravatar Simon Ser10 days
| | | | | | | | | | This was introduced in the last libinput release. Fixes the following error: ../sway/ipc-json.c:928:17: error: enumeration value 'LIBINPUT_CONFIG_ACCEL_PROFILE_CUSTOM' not handled in switch [-Werror=switch] 928 | switch (libinput_device_config_accel_get_profile(device)) { | ^~~~~~
* build: bump version to 1.8.11.8.1Libravatar Simon Ser2023-02-12
|
* Clarify documentation for window_rectLibravatar Łukasz Adamczak2023-02-12
| | | | (cherry picked from commit 8e4b6595786edf307623b9f1fcf3c7e5c8fa3833)
* Correct window_rect.y with hide_edge_bordersLibravatar Łukasz Adamczak2023-02-12
| | | | | | | | | | | | | With `hide_edge_borders both` (or at least `vertical`), `window_rect.y` will equal `border_thickness` for SOME windows, but it will be 0 for windows adjacent to top screen edge. Therefore setting it to `border_thickness` is not sufficient. This commit changes it to the actual y offset of content into the container. (cherry picked from commit fadfbe8dbae4b3a840cc05fcfe67d74f5050a878)
* Apply new adaptive sync value from wlr-output-managementLibravatar Alexander Courtis2023-02-10
| | | | | | | | | | | | | | | fixes #7394 Test cases: * zwlr_output_configuration_head_v1_set_adaptive_sync 0->0, no change * 0->1, enabled * 1->0, disabled * 1->1, no change Similar tests with an incapable display resulted in `"Adaptive sync failed, ignoring"` messages as expected. (cherry picked from commit 2c0f68b7c6c6e0f5ab79b22fc4334b6813a0f3fd)
* focus_on_window_activation: raise if floatingLibravatar Tobias Bengfort2023-02-10
| | | | (cherry picked from commit a7b9f6fedc8e625b9c950f43cad36cfc8fc6734c)
* Fix pointer events for ext-session-lock surfacesLibravatar Simon Ser2023-02-10
| | | | | | | We were never sending any pointer event to ext-session-lock surfaces. (cherry picked from commit 6a3e265326fab11b8f68374c9f30410f647ae866)
* Send wl_surface.enter for ext-session-lock surfacesLibravatar Simon Ser2023-02-10
| | | | (cherry picked from commit 284966fd57fb0efe1bcc6fc3ac23ae77e5a0d884)
* input/tablet: handle focusing NULL surfaceLibravatar Kirill Primak2023-02-10
| | | | | | | Additionally, rename the function responsible for switching focus to match its behavior better. (cherry picked from commit 53c9a4a6438824abfb3d539bf55aec92074977e0)
* warp_to_constraint_cursor_hint: Handle NULL viewLibravatar Alexander Orzechowski2023-02-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This might be the wrong fix, but the crash is happening because the ->data field on an xwayland surface is NULL. A NULL data field is normal for unmanaged surfaces, however it seems clients can do weird things: They can create a cursor lock on a regular xwayland surface then make it unmanaged by calling override_redirect. In this case, the xwayland server should destroy the cursor lock, which is does, but does so in the wrong order making it try to dereference a NULL pointer after sway has acknowledged its new unmanaged status. ``` (gdb) bt full 0 0x000055fd91934861 in warp_to_constraint_cursor_hint (cursor=0x55fd93486c00) at ../sway/input/cursor.c:1243 sy = 605 lx = 6.9527431433545762e-310 sx = 1272 view = 0x0 con = 0x7ffd1cdfe400 ly = -6.949595189996421e+59 constraint = 0x55fd93e7faa0 1 0x000055fd91934976 in handle_constraint_destroy (listener=0x55fd93f0fd58, data=0x55fd93e7faa0) at ../sway/input/cursor.c:1266 sway_constraint = 0x55fd93f0fd30 constraint = 0x55fd93e7faa0 cursor = 0x55fd93486c00 2 0x00007fda8275bf6e in wl_signal_emit_mutable () at /usr/lib/libwayland-server.so.0 3 0x00007fda82e57016 in pointer_constraint_destroy (constraint=0x55fd93e7faa0) at ../subprojects/wlroots/types/wlr_pointer_constraints_v1.c:49 4 0x00007fda82e570dc in pointer_constraint_destroy_resource (resource=0x55fd933cf8f0) at ../subprojects/wlroots/types/wlr_pointer_constraints_v1.c:66 constraint = 0x55fd93e7faa0 5 0x00007fda8275d8ba in () at /usr/lib/libwayland-server.so.0 6 0x00007fda8275f6a9 in wl_resource_destroy () at /usr/lib/libwayland-server.so.0 7 0x00007fda82e56fb3 in resource_destroy (client=0x55fd93ea52e0, resource=0x55fd933cf8f0) at ../subprojects/wlroots/types/wlr_pointer_constraints_v1.c:39 8 0x00007fda81d8f4f6 in () at /usr/lib/libffi.so.8 9 0x00007fda81d8bf5e in () at /usr/lib/libffi.so.8 10 0x00007fda81d8eb73 in ffi_call () at /usr/lib/libffi.so.8 11 0x00007fda8275aada in () at /usr/lib/libwayland-server.so.0 12 0x00007fda8275f01c in () at /usr/lib/libwayland-server.so.0 13 0x00007fda8275d9e2 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0 14 0x00007fda8275e197 in wl_display_run () at /usr/lib/libwayland-server.so.0 15 0x000055fd919264d3 in server_run (server=0x55fd919a3a80 <server>) at ../sway/server.c:320 16 0x000055fd91925457 in main (argc=1, argv=0x7ffd1cdfed98) at ../sway/main.c:411 verbose = false debug = false validate = false allow_unsupported_gpu = false config_path = 0x0 c = -1 ``` (cherry picked from commit 88c17ece3b2617762c3f5f1c1fa79fe8f4df0082)
* Use correct length for strncmp comparisonLibravatar Carl Smedstad2023-02-10
| | | | (cherry picked from commit 714559812e222f988e18a52ffecd8dcaf9604ad5)
* man: fix typo in output disable docsLibravatar Simon Ser2023-02-10
| | | | (cherry picked from commit 0c23b0ec339ae6b294539ce47addc9c4b523a438)
* Allow setting the font size to 0Libravatar Kate2023-02-01
|
* build: bump version to 1.81.8Libravatar Simon Ser2022-12-25
|
* swaynag: fix NULL font descriptionLibravatar Simon Ser2022-12-22
| | | | | | | | The font description was only set if provided on the CLI. It was left NULL for the defaults and when reading from the config file. Closes: https://github.com/swaywm/sway/issues/7186 (cherry picked from commit fd0af78e43f4dd67a404f475c676b25ae38a4b82)
* build: bump version to 1.8-rc41.8-rc4Libravatar Simon Ser2022-12-19
|
* seat: Set keyboard if seat keyboard is NULLLibravatar Kenny Levinsen2022-12-19
| | | | | | | | | | | | | | | | | sway sends wl_keyboard.enter on seat focus change and when a keyboard active on a seat is configured. If all keyboards are removed and a keyboard is added back without changing the focused client, no new notify event would be sent despite having keyboard focus. This could lead to key events without notify, which is a protocol violation. As a quick fix, when configuring a keyboard on a seat where no keyboard is currently active, activate the keyboard so that a focused surface will receive a notify event. Regressed by: e1b268af98edeb09e570e8855ef64f0719cbafe2 Closes: https://github.com/swaywm/sway/issues/7330 (cherry picked from commit 1ade0ce753dc5f588584f444ce80d27c3b1e4300)
* commands/move: Warp cursor after moving workspace to another outputLibravatar Ankit Pandey2022-12-19
| | | | | | | | | This makes sway's behavior consistent with i3 when `mouse_warping` is set to any value besides `none`. Fixes #7027. (cherry picked from commit e3c63bf58d0744dfb436f0f38442ce3735e40f47)
* build: bump version to 1.8-rc31.8-rc3Libravatar Simon Ser2022-12-12
|
* criteria: be lenient on window_role and instance tooLibravatar Ronan Pigott2022-12-12
|
* seat: Avoid sending redundant keymaps on reloadLibravatar Kenny Levinsen2022-12-12
| | | | | | | | | | | | | | | | | | | When we reload the config, we reset every input device and re-apply configuration from the config file. This means that the keyboard keymap is updated at least once during config reload, more if the config file contains keyboard configuration. When they keyboard keymap changes and is updated through wlr_seat, the keymap ends up sent to every keyboard bound in every client, seemingly multiple times. On an x230 of mine with a keyboard layout set in the config file, I see 42 keymap events sent to foot on config reload. Reduce events from keyboard configurations by skipping all but the currently active keyboard for the seat, and by clearing the active keyboard during input manager device reset. After this change, I only see a single just-in-time keymap event. Fixes: https://github.com/swaywm/sway/issues/6654
* build: bump version to 1.8-rc21.8-rc2Libravatar Simon Ser2022-12-03
|
* build: fix have_xwayland when xcb-icccm is not foundLibravatar Simon Ser2022-12-03
| | | | | | xcb-icccm is required to build Xwayland support. Backported from commit d41f11e6bd8cef80f02dda4c66d4a31611aed753.
* Fix build on Debian StableLibravatar nerdopolis2022-11-29
| | | | (cherry picked from commit dca0bb5749bc16f91ab964fc1b06ebb9a453368f)
* build: bump version to 1.8-rc11.8-rc1Libravatar Simon Ser2022-11-26
|
* build: drop unused wayland-egl dependencyLibravatar Simon Ser2022-11-26
| | | | (cherry picked from commit 37e4a3d6370dc6ba2b0877d588845c06781e880e)
* swaybar: Make hotspots block bar release bindingsLibravatar Joan Bruguera2022-11-26
| | | | | | | | | | | | | | | | | | | | | | | The previous commit prioritized hotspots before bar bindings for press events, which matches i3's behaviour. However, since hotspots don't need to do any processing on release events, those were not handled, and simply fell through to `bindsym --release` bar bindings (if any). This is counter-intuitive, and doesn't match i3's behaviour. Instead in case a hotspot handles the press event, it should also handle the release event, doing nothing, but blocking the event from triggering a --release bar binding. E.g., in Sway, without this commit, this config. shows a text on tray clicks: bar { # ... bindsym --release button1 exec swaynag -m I_got_the_release_event. } But the same configuration in i3 (with i3-nagbar) doesn't show the text. Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com> (cherry picked from commit 94b69acf0d7b26ee5af2172300cb18473508da76)
* swaybar: Prioritize hotspot events to bar bindingsLibravatar Joan Bruguera2022-11-26
| | | | | | | | | | | | | | | | | | This is consistent with i3bar's behaviour, and for example, allows binding a command to button1, while still being able to click on tray icons or other zones on the bar's status line which may have their own bindings. E.g., in Sway, without this commit, this config. makes tray icons unclickable: bar { # ... bindsym button1 exec swaynag -m You_clicked_the_tray._Want_some_help? } But the same configuration in i3 (with i3-nagbar) keeps tray items clickable. Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com> (cherry picked from commit 53f9dbd424dc173a85c9f4cd30802259d38b1ef4)
* launcher: export X startup ids and use them for workspace matchingLibravatar Ronan Pigott2022-11-26
| | | | (cherry picked from commit 28fda4c0d38907fab94dc7d82c9dcf0754748b4e)
* launcher: export xdga tokens and use them for workspace matchingLibravatar Ronan Pigott2022-11-26
| | | | (cherry picked from commit 30ad4dc4a5a41ce7c7aa85096a6e18f374172983)
* launcher: fudge the interface a bitLibravatar Ronan Pigott2022-11-26
| | | | | | We want to create a context before knowing the pid it will match with. (cherry picked from commit bdeb9f95651f6c99cc2f4cfb59020ddee202cf36)
* launcher: initialize launcher_ctxs once on startupLibravatar Ronan Pigott2022-11-26
| | | | (cherry picked from commit 66568508c06267445489d655c91c94a34d6d9ffe)
* view: associate launch contexts with viewsLibravatar Ronan Pigott2022-11-26
| | | | | | | | | Views now maintain a reference to a launch context which, as a last resort, is populated at map time with a context associated with its pid. This opens the possibility of populating it before map via another source, e.g. xdga-tokens or configuration. (cherry picked from commit 864b3a9a18f236f92f1898bb44ab977ceaebfd68)
* launcher: rename pid_workspace to launcher_ctxLibravatar Ronan Pigott2022-11-26
| | | | | | Soon we will match views with more than just a pid. (cherry picked from commit d75c9f9722389d441fd24bd490c5cf12c4bef39a)
* launcher: use xdga tokensLibravatar Ronan Pigott2022-11-26
| | | | | | | This reuses wlroots token tracking for workspace matching. It doesn't export any xdga tokens for clients yet. (cherry picked from commit bd66f4943da1c96edc3ba49573e27b42b688c543)
* launcher: track workspaces by nodeLibravatar Ronan Pigott2022-11-26
| | | | | | | | | | | | This removes the need to rename the pid_workspaces when a workspace is renamed. It also opens the possibility of tracking other node types. Tracking containers would allow application to be placed correctly in the container tree even if the user has moved their focus elsewhere since it was launched. (cherry picked from commit 3b49f2782e8faf68766269b9c7390b16e25ae824)
* node: prettify node type namesLibravatar Ronan Pigott2022-11-26
| | | | (cherry picked from commit 1c4b94ae3ca94b972410c80a61404a347af1ee68)
* root: move the workspace matching code to its own fileLibravatar Ronan Pigott2022-11-26
| | | | | | | | | This removes the pid_workspace bits from tree/root before it gets too interesting. No functional change. (cherry picked from commit eb5021ef990fb29ff86544aea58d687ad62c757a)
* build: drop intermediate libraries for protocolsLibravatar Simon Ser2022-11-26
| | | | (cherry picked from commit af8a5a8918ef42336194fb1077b008a736de7af9)
* build: drop "server" from target name for protocol codeLibravatar Simon Ser2022-11-26
| | | | (cherry picked from commit e5475d9310941ce88ed016ce1515b36e3a440252)
* build: unify server & client protocol generationLibravatar Simon Ser2022-11-26
| | | | | | | No need to make a difference here, let's just generate header files for both. (cherry picked from commit 5be5a038da8a3789a19945719f2a27233291445d)
* build: drop wayland-scanner fallbackLibravatar Simon Ser2022-11-26
| | | | (cherry picked from commit 366f6ef3d31688631dc453028e108f98a1d7ab57)
* Use shm_open instead of mkstempLibravatar Manuel Stoeckl2022-11-26
| | | | | | | shm_open is more reliable because it does not require a writeable filesystem folder, unlike mkstemp. (cherry picked from commit e2bc8866f46701e9c825ad7fa5baac02b2e4898f)
* output: set damage ring bounds to pixel valuesLibravatar Kirill Primak2022-11-26
| | | | | Fixes: https://github.com/swaywm/sway/issues/7254 (cherry picked from commit 85005b52fe5b832e4ea914fa28048b0c5c803769)
* workspace_create: Don't allow NULL nameLibravatar Alexander Orzechowski2022-11-26
| | | | (cherry picked from commit 34933bb84350fe805d82276ea02d5732546e9993)
* ci: checkout wlroots 0.16.0Libravatar Simon Ser2022-11-11
|
* container_get_siblings: handle NULL workspaceLibravatar Baltazár Radics2022-11-11
|
* lock: fix crash on output destroyLibravatar Simon Ser2022-11-11
| | | | Closes: https://github.com/swaywm/sway/issues/7120
* Use wlr_damage_ringLibravatar Kirill Primak2022-11-11
| | | wlr_output_damage is to be replaced with wlr_damage_ring, so use that.
* Use wl_signal_emit_mutable()Libravatar Simon Ser2022-11-10
| | | | | This function fixes segfaults when emitting a signal potentially removes arbitrary listeners.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-28 15:08:47 +0000