summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2021-08-31compositor: Do not allow vt-switching by defaultMarius Vlad1-1/+1
Users are still able to customize that behaviour by modifying configuration file. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Id21b9cf5b486b8f124bfc128c139f8b706c16b45
2021-06-30Add gitreview file for Lucky Lamprey branchlamprey_12.0.0lamprey_11.93.0lamprey/12.0.0lamprey/11.93.012.0.011.93.0Jan-Simon Möller1-1/+1
Update the .gitreview file. Bug-AGL: SPEC-4006 Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org> Change-Id: I87030a715f3b89113d60d7b7ee6853233a079a9e
2021-04-20main: Split of main() from wet_main()marlin_12.90.0marlin/12.90.0lamprey_11.92.0lamprey_11.91.0lamprey/11.92.0lamprey/11.91.012.90.011.92.011.91.0sandbox/mvlad/pre-ciMarius Vlad3-1743/+1792
This is follow-up to catch up with weston's way of loading the compositor instance. This is necessary because the test itself is capable of loading a specific compositor instance (and with, specific arguments). No functional changes whatsoever. Bug-AGL: SPEC-3889, SPEC-3880 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Iedb979156a73def4567927969ab9190c481ffbce
2021-04-20main: Copy cmd line args and print themMarius Vlad1-2/+28
This makes it really easy to spot on what arguments have been passed to the compositor. When a test client will run the compositor this will be helpful to verify that we pass the correct arguments. Fixes a small typo along the way. Bug-AGL: SPEC-3880 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia4198ce6bff465f479cf9a0a87c17998c5548868
2021-04-20main: Teach agl-compositor to load additional modulesMarius Vlad1-0/+52
Passing modules arguments to the compositor instance would be useful when using the testing framework/harness because that way the test itself can start-up. The idea here is that we would need to load-up a testing plug-in (either one from weston) or one written specifically for this. Bug-AGL: SPEC-3888 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia5e688901fe11b1ab10feb3f5e2631a0f31707be
2021-04-20main: Add support for loading the headless-backendMarius Vlad1-0/+54
For making use of the testing framework/harness we should be able to load up the headless backend. This patch adds support for loading it. Bug-AGL: SPEC-3887 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I569ad3e562cd0a90094c6238ca02ed00e4106b10
2021-04-20meson.build: Do an release update before libweston9 integrationMarius Vlad1-2/+2
We haven't had an release for quite some time now so, do it now before the libweston9 integration. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I8202f88565a94e10cc5dc60fe2ec30cc1e8ee478
2021-04-19layout: Remove weston_output_damage dependecyMarius Vlad2-6/+4
Doing a damage_below for the view should be sufficient to trigger a repaint. This way we don't actually need it. Bug-AGL: SPEC-3641 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I90f4c4c13571f441b35f933f2b93aaff7efd3481
2021-04-08layout: Fix split role sending invalid dimensionsMarius Vlad1-6/+2
As we send from the beginning/start the size for the client, we'll be missing a checking when using split type of surfaces, which will result in invalid width/height passed to clients on configure events. Avoid using it entirely and assume for split roles to use half of the output by default. Bug-AGL: SPEC-3881 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia9728c9401cdd1ae918229853ddf7393e14f6cb1
2021-03-11desktop: Tell clients to use current geometry area from startMarius Vlad1-0/+52
After the shell UI is started we can tell clients the available geometry area, and with it, they can avoid resizing to the surface size. Bug-AGL: SPEC-3839 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Id30617dadc665d1ca202a505d98e70eed592e856
2021-03-11desktop: Send remove event only if output and app_id is setMarius Vlad1-2/+3
This will guard against clients do not have an application id, or they weren't activated at all. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Iee58c0f54efdecce82ff07e0916ebef15f7f64d8
2021-02-17Notify about application destructionWalter Lozano2-2/+10
Currently agl-compositor notifies about application ids which can be activated/deactivated, as well as the application state. However, when an application is destroyed this information is not communicated to desktop making it out of sync with the actual list of available applications. To overcome this limitation extend the protocol and the logic to notify about application destruction on surface remove. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: Ib766cf3f3fbd10f55b85212480dc4717ab1bec22
2021-02-04Allow unregistered applications in rbaAnusha Gugale3-4/+17
- To allow unregistered applications, set allow_unregistred_app=true in .ini file under core section of /etc/xdg/weston/weston.ini . Bug-AGL: SPEC-3738 Signed-off-by: Anusha Gugale <external.agogale@jp.adit-jv.com> Change-Id: Ic56564ea97900df0091d92a2dd4ed1bc7cb0559f
2021-01-26Use parameterized constructor of RBAArbitratorkoi_10.93.0koi/10.93.010.93.0Anusha Gugale1-2/+1
- To hide unnecessary internal interfaces from user, reconstructed public files of librba. At this time, default constructor has been removed. Bug-AGL: SPEC-3738 Signed-off-by: Anusha Gugale <external.agogale@jp.adit-jv.com> Change-Id: I957796861081c79df9018cac92bd06927952924d
2021-01-13doc/arch_diagram: Update architecture diagram with a small legendMarius Vlad2-83/+186
Trivial change to display which are API calls, which are Wayland ones. Bug-AGL: SPEC-3386 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I265e19baaa7437af4221a71378706661395b4445
2021-01-12Added rba policy implementationkoi_10.92.0koi/10.92.010.92.0Anusha Gugale5-2/+230
- Added rba-policy option in meson file - Created new rba adapter file to call rba interfaces from librba - All the application from Homescreen will be allowed to display through rba policy as its added in RBAModel.json Bug-AGL: SPEC-3738 Signed-off-by: Anusha Gugale <external.agogale@jp.adit-jv.com> Change-Id: Iffd4ac16d9abe768476d025556cbe98a31553288
2021-01-07meson.build: Fix building with cross SDKMarius Vlad1-2/+7
For some time now, yocto/OE no longer builds all weston back-ends, which means the X11 is no longer supported on AGL platform. The agl-compositor can be built, assuming all dependencies have been satisfied, without the need of having an AGL or yocto/OE environment, but so far, I've never tried using SDK directly. This patch should allow building the compositor, by only using the AGL SDK, and instead of using the local pkg-config, only use what is available in the SDK sysroot. This takes care of assuming that X11 back-end is available, when in reality, in the AGL SDK platform that is not the case. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia2a182b9c3015f14f82043a04e83e917cd99bf6f
2021-01-06main: Add activate_by_default ini optionMarius Vlad3-0/+8
Displaying the application surface as soon as started required activating the surface by default. With this patch, we give the possibility to do it conditionally, as it helps CI with cases where we don't really want other applications change the active surface. With applications that start by default, this interferes with the ability to take a screenshot with just the background. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I6e826a6715b9a348181df80ed53ffaa6b65b7d2b
2020-11-19layout: Do not attempt to activate surfaces that doesn't have a valid app_idkoi_10.91.0koi/10.91.010.91.0Marius Vlad1-0/+6
Observed when trying to activate (a previous one, as a result of deactivation) a surface that didn't had an application id set. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I3c39ae7dfb237e53f4b2bad64e7bc5ef91a76f0c
2020-11-19shell: Throttle the log messageMarius Vlad1-1/+5
As libweston doesn't currently have a rate limiting the log message function, use a static variable to limit the amount of log message we might be seeing if application do not set-up an app_id. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I4fb3a5b7421a154d8da483b2ac577df7a60e09cc
2020-11-19build/: Allow to build the compositor w/o walthamMarius Vlad2-2/+15
Provides empty implementations to avoid sprinking ifdefs everywhere. The transmitter plug-in does not expose a pkgconfig file we instead resort to test again waltham protocol (which is used by the transmitter) and the the remoting plug-in. Fixes a minor deps check in the meson file. Bug-AGL: SPEC-3691 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Id25d21d2ef0c6e55575c2e7685cda73e401db015
2020-11-18shell: Perform wl_list_init() after wl_list_remove()Walter Lozano1-0/+1
In order to follow the best practices perform wl_list_init() after wl_list_remove() on shell_ready. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: Ia5ea915a5ad55e8251e3bc86c87ddfc140bbe592
2020-11-17desktop: Allow to remove surface from pending listWalter Lozano1-3/+2
In some special corner cases a surface can be removed while it is still in the pending list. An example of this case is when a surface is added and removed before the system is ready. Under this circumstances the surface still has role == ROLE_NONE and is in the pending list. The fact of not removing the surface from the pending_list ends in a segfault when the system is ready. In order to fix the issue, remove the restriction to only remove surfaces with role != ROLE_NONE. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: Ia71b6c3ca214849448c935cc09039581d0e209a8
2020-11-17desktop: Do not attempt to advertise the clients if there are noneMarius Vlad1-1/+2
Clients not binding to agl_shell_desktop will cause spurious signal emits when they commit the changes. Make sure we only attempt to advertise if the are clients. Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I5c790b105b7c7f7d759e8a8fc2c64713df22d561
2020-11-17desktop: Delay surface creation until committedWalter Lozano3-14/+27
Some frameworks like GTK-3 delay the set_app_id until title and parent are set, which makes ivi_check_pending_desktop_surface unable to set the proper role on surface_added. A consequence of this behaviour is that is not possible to use set_app_property to configure an application as popup. Instead, delay the creation of the surface until committed to give the chance to have a valid app_id configured. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: I3f672fb365f48659711c866c45a21df6058a5a02
2020-11-05shell: Destroy weston_transmitter_surface as wellMarius Vlad3-0/+20
Instruct waltham-transmitter-plugin that it can destroy its own surface representation when the weston_surface is also destroyed. Bug-AGL: SPEC-3601, SPEC-3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ie0e5409b21c043b8c98bebb4d77808227ee38aca
2020-11-05shell: Keep a reference to weston_transmitter_surfaceMarius Vlad2-1/+11
When 'pushing' the surface store a reference of the weston_transmitter_surface so we can later inform the plug-in when the weston_surface is destroyed, so that it can also destroy the transmittter_surface from its side. Bug-AGL: SPEC-3601, SPEC-3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I7fd1df2130e53e8c226c7a751c598765608ae6b3
2020-11-05desktop: Insert a black surface only when the output is a remote typeMarius Vlad1-2/+2
And the output is not a waltham version. Bug-AGL: SPEC-3601, SPEC-3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I9ce3354fe59ad5f4de691823627e3603fc4cb226
2020-11-05desktop: Group tests for checking against last remote surfaceMarius Vlad1-5/+3
Synthetic change, to group them together. Makes reading the code a bit more clearer. Bug-AGL: SPEC-3601 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Id1f5ad9a408591a010678a53eff0f3cad2d269d9
2020-11-05shell: Push the surface to the remote sideMarius Vlad1-0/+62
The receiver expects that the sender/transmitter will inform it when it can create a surface and it can start the gstreamer pipeline. The transmitter plug-in exposes a way to call that using 'push_surface' callback. So, whenever we detect that the remote surface is to be assigned to a waltham-type of output, we would need to call into this 'push_surface' callback. This acts as notification mechanism for the remote side. Bug-AGL: 3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia5db0d8f2356708eaee3fbaabed2b3ba3ac97eb6
2020-11-05main: Create a remoting output if the waltham plug-in has been loadedMarius Vlad1-0/+55
The waltham-transmitter will no longer create an output on its own so we'll re-use the remoting plug-in for streaming out the buffers to the remoting side. Bug-AGL: 3601 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I6f85c3dfc54e81e8fa05f518b77fae24334fafc1
2020-11-05ivi-compositor: Add the ability to distinguish between differentMarius Vlad2-0/+10
types of remoting outputs This is required to further differentiate between remoting outputs as for waltham we would need to use the transmitter_api to forward a surface to the remoting output. Bug-AGL: 3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I7c59fd448226afab0492fe674e8770d3b9a995aa
2020-11-05main: Add support loading waltham transmitter plug-inMarius Vlad3-1/+62
This is the same as the remoting plug-in, given that we'll be using the remoting plug-in to create the remoting output. The difference would be that instead of the 'remoting-output' section we'll use 'transmitter-output', with all other section specific being the same. For instance, using agl-shell-app-id we can instruct the application to be assigned to that 'transmitter-output'. Bug-AGL: SPEC-3611 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ic16b6b9672802f4f83be121385c0798b9dbe08e9
2020-11-05layout: Check app_id for remote type of surfacesMarius Vlad1-0/+3
We don't have any checks against for not having an app_id being set. Bug-AGL: SPEC-3601 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Iff7f633bced60b1177f53246880952a06cb716f0
2020-11-05shell: Avoid creating and inserting black surfaceMarius Vlad1-2/+5
Creating and inserting the black surface will require to have an valid weston output. That might not be always the case so guard against no output being set. Bug-AGL: SPEC-3601 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: If7034bf0259fee164ba0f4b6a6ac3ef7d6bf30d6
2020-10-29main: Use the output handler to destroy to black viewMarius Vlad2-6/+6
Use the specific output destroyer handler, instead of destroying it in the handler itself. This way we can still clean-up and avoid any leaks, and still not trip ourselves causing a use-after-free, when the output is destroyed by libweston. Bug-AGL: SPEC-3630, SPEC-3672 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Reported-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: I11916245b85d2541286ee438284601b466dc20c2
2020-10-15shell: Advertise app when app_id is availableWalter Lozano4-2/+35
When using GTK-3 to create apps, the framework issues set_parent_id which forces a surface to be added even before the app_id is set. This causes the compositor to fail to advertise the app. This patch tries to overcome this issue by checking on surface commit if the surface was previously advertised, and do it if it was not. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: I4e5fec82c1008c30d8ae7d213d85a82e39c404c3
2020-10-15shell: Avoid advertising applications without app_id setWalter Lozano1-0/+11
When using GTK-3 to create apps, the framework issues set_parent_id which forces a surface to be added even before the app_id is set. This causes the compositor to try to advertise an invalid app_id. This patch avoids advertising an app which has no app_id set. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: Iadcea106e6464b41171a2aa92aa0eed3a8e2ff2d
2020-10-08main: Create black surface after listening socketWalter Lozano1-2/+2
If agl-compositor is started without XDG_RUNTIME_DIR defined, an error arises and the system tries to exit cleanly. However, in this process a segfault is produced and the terminal is left misconfigured. The cause of this segfault is related to the destruction of the black surface, which is not handled properly in this corner case. In order to avoid this issue and as an initial fix, create the surface after the listening socket, which causes that the check for the var XDG_RUNTIME_DIR to be done before the surface creation. Bug-AGL: SPEC-3623 Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: I04760828f9ce5b5a6d4a31aeccdefe779a1c15a3
2020-09-30main: Use a configuration option for hidding out the cursorMarius Vlad1-3/+2
Bug-AGL: SPEC-3580 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I3504fc2c6dda3c10a67a23e68126201acd4ba455
2020-09-30main: Enable screenshoter interface when debug option is passedMarius Vlad1-1/+2
Bug-AGL: SPEC-3580 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I9adf8c707991301f5cf214b492ce3c6ee45997e2
2020-09-30input: Add basic seat handlingMarius Vlad5-1/+267
This allows for basic input handling, to better customize how we handle out seat capabilities to the client. One useful outcome of this is the fact that we re-advertise to the client that in some situations there might not be a pointer available. That should let the client know as to avoid creating a pointer surface. Bug-AGL: SPEC-3591 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I4624a956264e9fa12a86da005944e9b426dde10a
2020-09-30client/screenshooter: Client for taking screenshotsMarius Vlad7-0/+971
The client allows to take screenshots of all outputs, a specific output (making use of xdg_output_manager interface) or just listing outputs. Bug-AGL: SPEC-3580 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Idd60d4892adf4c2ea493477421b6e5623e0ca1f0
2020-09-30screenshooter: Add agl-screenshooter protocolMarius Vlad5-0/+229
Just like weston, we add a private protocol. Underneath we make use of the weston renderer to get a hold of the pixels and transfer them to a user-supplied buffer. This only brings up the server side implementation of the protocol. Bug-AGL: SPEC-3580 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I02a07ad5eb492ef2ecad74efb34d1453ebcbedc0
2020-09-28layout: Set active output NULL when displaying backgroundWalter Lozano1-0/+1
Currently agl-compositor keeps track of the active app and uses this information to to also keep track of the previous one. This is useful to allow to show the previous activated app when deactivating the current one. However, when deactivating all the apps, for instance the background, this information is not saved, which causes that when activating and deactivating and new app, instead of the background a different app shows. This patch sets output->previous_active = NULL when displaying the background to overcome this issue. Signed-off-by: Walter Lozano <walter.lozano@collabora.com> Change-Id: I29c3f8972d6055d2387e0fdcbb28574d3d2e38a7
2020-09-10layout: Activate by default xdg surface that do not have an app_id setjellyfish_9.99.4jellyfish/9.99.49.99.4Marius Vlad2-5/+34
The following is necessary in case the app_id is set-up at a later point in time, and it is intended as a work-around for WAM/chromium68 clients that specify the app_id after the initial surface commit. Note that activation will not work, in case the application will never set-up an app_id because we can't identify which app_id to switch to. The activation phase is needed to inform the client of the window dimensions, and it is mandated by the XDG-shell protocol. Bug-AGL: SPEC-3544 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I49a7270dcb68e525fc9d85db2cd189a50c02502f
2020-09-10layout: If no valid output found, abort early with a protocol violationMarius Vlad1-0/+9
Spotted by code inspection, but haven't seen in the wild. Bug-AGL: SPEC-3544 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ie1f0191e7c987c1688c820e1cabbc581b3679232
2020-07-29layout: Add missing hooks for other surface rolesjellyfish_9.99.3jellyfish/9.99.39.99.3Marius Vlad1-0/+28
We are missing the activate_by_default hooks for split, pop-up and and fullscreen roles. Part of that is due to the fact that these roles are handled a bit differently that the remote and desktop roles. Note, these hooks are different than the commit ones -- which are 'installed' a bit earlier. This means that there was still a possiblity one might've used that hook to retrieve the surface role for instance, and act accordingly. Also, note that we allow for pop-up/dialogs be activated by using the deliberate 'activate' request, which allows one to customize the policy to deny certain pop-up/dialogs to be activated by default, but allow do so explictly when using the 'activate' request. Bug-AGL: SPEC-3494 Reported-by: Scott Murray <scott.murray@konsulko.com> Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I634bbb5915e65880c1d47363cf6dae529feac9d2
2020-07-29layout: Advertise state change for other types of surface rolesMarius Vlad3-2/+26
Given that now other surfaces roles will be active by default, we need to let other application aware of that fact by advertising state change. Print some debug message while at it, to make it more consistent with the desktop role. Bug-AGL: SPEC-3494 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: Ia9d959a0912e330303fa3d959ce600237edf35b4
2020-07-29shell: Assume consistency with the desktop rolesMarius Vlad1-0/+4
While looking into activation by default of other surfaces, noticed that we're missing consistency on how we handle other types of surface roles. This patch, activate all other surfaces by default when starting up, even if they are started before or after the client shell. Expecting and assuming the same behaviour is important into trying to establish some common work-flow for applications. Bug-AGL: SPEC-3494 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I90e764c6c3a7ed543934ee6f68fa716d90ff151e