Re: After display protocol error communication between wayland protocol and client is broken.

2019-01-01 Thread Pekka Paalanen
On Mon, 31 Dec 2018 20:08:24 +0530 Ikshwaku Chauhan wrote: > Hello Pekka, > > Thanks for your reply. > Here we are trying to identify the exact root cause for the protocol error. > we deliberately dumped the back trace by calling *abort in > display_protocol_error* function and attaching

Re: After display protocol error communication between wayland protocol and client is broken.

2018-12-31 Thread Ikshwaku Chauhan
Hello Pekka, Thanks for your reply. Here we are trying to identify the exact root cause for the protocol error. we deliberately dumped the back trace by calling *abort in display_protocol_error* function and attaching backtrace for your reference. Could you please have a look and provide your

Re: After display protocol error communication between wayland protocol and client is broken.

2018-12-30 Thread Pekka Paalanen
On Fri, 28 Dec 2018 15:46:23 +0530 Ikshwaku Chauhan wrote: > Hello Pekka, Hello Dima, > > Thanks for your prompt responce. > After analyzing the below wayland client logs we concluded that we are > getting the *Protocol Error: Invalid Object*, because we are trying to set > the property of a

Re: After display protocol error communication between wayland protocol and client is broken.

2018-12-28 Thread Ikshwaku Chauhan
Hello Pekka, Hello Dima, Thanks for your prompt responce. After analyzing the below wayland client logs we concluded that we are getting the *Protocol Error: Invalid Object*, because we are trying to set the property of a destroyed surface. [216074.552] ivi_controller@6.surface(80) [216074.635]

Re: After display protocol error communication between wayland protocol and client is broken.

2018-12-28 Thread Pekka Paalanen
On Thu, 27 Dec 2018 11:55:03 -0800 Dima Ryazanov wrote: > Hello, > > Yes, that's expected. From the documentation > : > "The error event is sent out when a fatal (non-recoverable) error has > occurred" > It

Re: After display protocol error communication between wayland protocol and client is broken.

2018-12-27 Thread Dima Ryazanov
Hello, Yes, that's expected. From the documentation : "The error event is sent out when a fatal (non-recoverable) error has occurred" It indicates a bug in the code, so there's no point in handling the error.

After display protocol error communication between wayland protocol and client is broken.

2018-12-27 Thread Ikshwaku Chauhan
Hello All, We are facing an issue where we are not receiving any surface/layer creation/distortion notifications from Layermanager. We debugged and found that, once we get "*display protocol error : Invalid Object XX" i.e, (wl_display@1.error(wl_display@1, 0, "invalid object XX"))* on wayland