Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
On 05/04/2017 01:01 μμ, Marco Martin wrote: yeah, "the xcb windowing system" playing around a bit with our crashes in wayland but here it is, wayland painting for Latte... but of course we cant yet position our docks and get infos for the active window so this is the reason for the ping of the thread in order to open the discussion concerning external docks for plasma in wayland world... https://cloud.githubusercontent.com/assets/2216474/24711791/a6082e10-1a29-11e7-94d5-9f5cc920b478.png
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
On Wednesday 05 April 2017, Michail Vourlakos wrote: > > to see if it's due to xwayland, you can try to do > > export QT_QPA_PLATFORM=wayland > > > > then launch it from the same terminal and see what happens > > I forgot the link with the screenshot: > > https://drive.google.com/file/d/0B98NarVO5dq1LThERmNRUEV3c2M/view?usp=shari > ng yeah, "the xcb windowing system" -- Marco Martin
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
to see if it's due to xwayland, you can try to do export QT_QPA_PLATFORM=wayland then launch it from the same terminal and see what happens Hello Marco! in x session, if I use your guidelines an error message occurs that such display can not be found in wayland session, if I use your guidelines Latte is starting but before creating the dock windows is crashing... I suppose this is because we havent enabled yet the wayland surfaces creation yet in wayland session, if I just run the app it runs ok... the following screenshot shows the about windows of dolphin and latte in a wayland session... the first one is using wayland and the second xcb... I suppose this means that we use xwayland https://drive.google.com/file/d/0B98NarVO5dq1LThERmNRUEV3c2M/view?usp=sharing
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
to see if it's due to xwayland, you can try to do export QT_QPA_PLATFORM=wayland then launch it from the same terminal and see what happens I forgot the link with the screenshot: https://drive.google.com/file/d/0B98NarVO5dq1LThERmNRUEV3c2M/view?usp=sharing
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
to see if it's due to xwayland, you can try to do export QT_QPA_PLATFORM=wayland then launch it from the same terminal and see what happens Hello Marco! in x session, if I use your guidelines an error message occurs that such display can not be found in wayland session, if I use your guidelines Latte is starting but before creating the dock windows is crashing... I suppose this is because we havent enabled yet the wayland surfaces creation yet in wayland session, if I just run the app it runs ok... the following screenshot shows the about windows of dolphin and latte in a wayland session... the first one is using wayland and the second xcb... I suppose this means that we use xwayland
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
On Wednesday 05 April 2017, Michail Vourlakos wrote: > ping... > > Hello everyone... > > Merging Now Dock with Candil Dock we managed to release > Latte Dock the last weekend and we are more than happy to use only > kde and plasma technologies!! :) In the next phase of Latte development we > are > trying to make a plan for supporting wayland... Yesterday I managed to open > a > wayland session in openSUSE Tumbleweed for plasma 5.9 > (it just run with the official packages with no adjustments) and tried to > run > Latte just for fun in it, so it opened and it looked fantastic! :) I > suppose it uses > the xwayland to achieve this... you can see a screenchot for it at: to see if it's due to xwayland, you can try to do export QT_QPA_PLATFORM=wayland then launch it from the same terminal and see what happens -- Marco Martin
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
ping... Hello everyone... Merging Now Dock with Candil Dock we managed to release Latte Dock the last weekend and we are more than happy to use only kde and plasma technologies!! :) In the next phase of Latte development we are trying to make a plan for supporting wayland... Yesterday I managed to open a wayland session in openSUSE Tumbleweed for plasma 5.9 (it just run with the official packages with no adjustments) and tried to run Latte just for fun in it, so it opened and it looked fantastic! :) I suppose it uses the xwayland to achieve this... you can see a screenchot for it at: https://cloud.githubusercontent.com/assets/2216474/24677245/c9f422de-198e-11e7-802a-8e489484556c.png we havent added yet any wayland specific code and we were expecting crashes etc. but this didnt happen... many kudos for everyone working around wayland porting etc!!! Being in that point we would like please an update concerning the use of kwayland from external apps like Latte... What is the situation in plasma 5.9, is there a way to access these privileged apis? if not, are there any plans when such support may be possible? thank you very much once more !!! regards, michail 2016-12-21 21:16 GMT+02:00 Martin Gräßlin > send from wrong address...(or kmail is broken) > > Am 2016-12-21 20:15, schrieb Martin Gräßlin: > >> Hi, >> >> currently every window gets access. This will change soon. The >> implementation for authorization is already on the whiteboard left to >> me :-) >> >> Basically the required interface will be restricted. The >> identification will be based on process ids with a root (!) owned >> global configuration file. >> >> At runtime any access without authorization will simply abort the >> application. It will raise a Wayland protocol error which will result >> in application termination. >> >> There might be a protocol added to ask the user for authorization. But >> that will be runtime, that is every time the user restarts the >> application it will be asked again. But that's a secondary step. The >> first will be to just shut down any access to these privileged >> interface. >> >> Most likely this will be introduced with Plasma 5.10 or 5.11. >> >> Cheers >> Martin >> >>> >>>
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
Am 2016-12-21 22:58, schrieb Michail Vourlakos: Στις 21 Δεκ 2016 23:17, ο χρήστης "Martin Gräßlin" έγραψε: Am 21. Dezember 2016 21:19:02 MEZ, schrieb Michail Vourlakos : On 21/12/2016 09:16 μμ, Martin Gräßlin wrote: send from wrong address...(or kmail is broken) Am 2016-12-21 20:15, schrieb Martin Gräßlin: Hi, currently every window gets access. This will change soon. The implementation for authorization is already on the whiteboard left to me :-) nice to hear... :) Basically the required interface will be restricted. The identification will be based on process ids with a root (!) owned global configuration file. If I read it correctly, then the user could edit this file in order to allow a dock executable to gain access, right? this is sufficient for me... So, a kcm could be added in order to edit this file and make this easier for the user, right? No, as that will be a system wide setting and root owned there will certainly not be a kcm for it. So this doesnt fall in the category of all the other kcm's that require root password to apply their settings such as the time/date one and the sddm one... We don't offer kcms for everything. This will fall into the category of no KCM should be provided. This is about the security of the system. It's distro or admin job. So the user that owns the root password should be able to edit that file, am I wrong? If I ever see introductions by 3rd party providers on how to edit the files so that the fancy tool works, I'll change the implementation ASAP. This is about security of the system! Normal users shall not know how to do that. Now that I am thinking it, even an installation from a package distro installation could also alter it, no? Yes, that's the idea how we want to do it for Plasma. The package installation will take care of it. Cheers Martin
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
Στις 21 Δεκ 2016 23:17, ο χρήστης "Martin Gräßlin" έγραψε: Am 21. Dezember 2016 21:19:02 MEZ, schrieb Michail Vourlakos < mvourla...@gmail.com>: > > >On 21/12/2016 09:16 μμ, Martin Gräßlin wrote: >> send from wrong address...(or kmail is broken) >> >> Am 2016-12-21 20:15, schrieb Martin Gräßlin: >>> Hi, >>> >>> currently every window gets access. This will change soon. The >>> implementation for authorization is already on the whiteboard left >to >>> me :-) >nice to hear... :) > >>> >>> Basically the required interface will be restricted. The >>> identification will be based on process ids with a root (!) owned >>> global configuration file. >>> >If I read it correctly, then the user could edit this file in order to >allow a dock >executable to gain access, right? this is sufficient for me... > >So, a kcm could be added in order to edit this file and make this >easier >for the user, right? No, as that will be a system wide setting and root owned there will certainly not be a kcm for it. So this doesnt fall in the category of all the other kcm's that require root password to apply their settings such as the time/date one and the sddm one... This is about the security of the system. It's distro or admin job. So the user that owns the root password should be able to edit that file, am I wrong? Now that I am thinking it, even an installation from a package distro installation could also alter it, no?
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
Am 21. Dezember 2016 21:19:02 MEZ, schrieb Michail Vourlakos : > > >On 21/12/2016 09:16 μμ, Martin Gräßlin wrote: >> send from wrong address...(or kmail is broken) >> >> Am 2016-12-21 20:15, schrieb Martin Gräßlin: >>> Hi, >>> >>> currently every window gets access. This will change soon. The >>> implementation for authorization is already on the whiteboard left >to >>> me :-) >nice to hear... :) > >>> >>> Basically the required interface will be restricted. The >>> identification will be based on process ids with a root (!) owned >>> global configuration file. >>> >If I read it correctly, then the user could edit this file in order to >allow a dock >executable to gain access, right? this is sufficient for me... > >So, a kcm could be added in order to edit this file and make this >easier >for the user, right? No, as that will be a system wide setting and root owned there will certainly not be a kcm for it. This is about the security of the system. It's distro or admin job. 3rd party installed software won't have access to this system. > >>> At runtime any access without authorization will simply abort the >>> application. It will raise a Wayland protocol error which will >result >>> in application termination. >sounds logical! > >>> . >>> >>> Most likely this will be introduced with Plasma 5.10 or 5.11. >no matter on the time, Martin :) I just wanted a light in the end of >the >tunnel!! :) >we are very glad to have you in the kde team... > >thank you a lot your time and your immediate response.. > > >regards, >michail
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
On 21/12/2016 09:16 μμ, Martin Gräßlin wrote: send from wrong address...(or kmail is broken) Am 2016-12-21 20:15, schrieb Martin Gräßlin: Hi, currently every window gets access. This will change soon. The implementation for authorization is already on the whiteboard left to me :-) nice to hear... :) Basically the required interface will be restricted. The identification will be based on process ids with a root (!) owned global configuration file. If I read it correctly, then the user could edit this file in order to allow a dock executable to gain access, right? this is sufficient for me... So, a kcm could be added in order to edit this file and make this easier for the user, right? At runtime any access without authorization will simply abort the application. It will raise a Wayland protocol error which will result in application termination. sounds logical! . Most likely this will be introduced with Plasma 5.10 or 5.11. no matter on the time, Martin :) I just wanted a light in the end of the tunnel!! :) we are very glad to have you in the kde team... thank you a lot your time and your immediate response.. regards, michail
Re: [KWin Question] - KWin authorize external docks to manipulate tasks and windows
send from wrong address...(or kmail is broken) Am 2016-12-21 20:15, schrieb Martin Gräßlin: Hi, currently every window gets access. This will change soon. The implementation for authorization is already on the whiteboard left to me :-) Basically the required interface will be restricted. The identification will be based on process ids with a root (!) owned global configuration file. At runtime any access without authorization will simply abort the application. It will raise a Wayland protocol error which will result in application termination. There might be a protocol added to ask the user for authorization. But that will be runtime, that is every time the user restarts the application it will be asked again. But that's a secondary step. The first will be to just shut down any access to these privileged interface. Most likely this will be introduced with Plasma 5.10 or 5.11. Cheers Martin Am 2016-12-21 18:47, schrieb Michail Vourlakos: Hello everyone, as it appears, in the following versions of Now Dock the dock will try to live outside plasmashell as a standalone separate executable. It will still use all plasma technologies from frameworks etc. but there is an issue with that design decision change as the plasma developers informed me. In wayland world only the plasmashell executable gains access through kwayland to manipulate tasks, get information about the windows and even move its own window. I would like to ask you what are the policies and guidelines in order for another executable to gain such access. This is the case of course for all docks living outside plasmashell. thanks a lot for your time. regards, michail
[KWin Question] - KWin authorize external docks to manipulate tasks and windows
Hello everyone, as it appears, in the following versions of Now Dock the dock will try to live outside plasmashell as a standalone separate executable. It will still use all plasma technologies from frameworks etc. but there is an issue with that design decision change as the plasma developers informed me. In wayland world only the plasmashell executable gains access through kwayland to manipulate tasks, get information about the windows and even move its own window. I would like to ask you what are the policies and guidelines in order for another executable to gain such access. This is the case of course for all docks living outside plasmashell. thanks a lot for your time. regards, michail
