Re: [PATCH libinput] Note that libinput_unref() really destroys everything

2015-09-03 Thread Peter Hutterer
On Fri, Sep 04, 2015 at 08:29:07AM +0200, Andreas Pokorny wrote: > Hi, > To some degree this does not sound like a bug. At least for resources that > are not presented to the user as being ref counted. But I would have > expected that libinput_path_add_device would increase the ref count of the > l

Re: [PATCH libinput] Note that libinput_unref() really destroys everything

2015-09-03 Thread Andreas Pokorny
Hi, To some degree this does not sound like a bug. At least for resources that are not presented to the user as being ref counted. But I would have expected that libinput_path_add_device would increase the ref count of the libinput_context and similar for seats. So as long as the device is not unre

Re: [PATCH libinput] Note that libinput_unref() really destroys everything

2015-09-03 Thread Jonas Ã…dahl
On Fri, Sep 04, 2015 at 02:17:06PM +1000, Peter Hutterer wrote: > This is both a bug and required behavior. A caller may hold refcounted > references to devices, seats, or device groups but when libinput_unref() > cleans up, all these become invalid. > > It is required behavior, because the last c

[PATCH libinput] Note that libinput_unref() really destroys everything

2015-09-03 Thread Peter Hutterer
This is both a bug and required behavior. A caller may hold refcounted references to devices, seats, or device groups but when libinput_unref() cleans up, all these become invalid. It is required behavior, because the last call to libinput_unref() also calls libinput_suspend() and thus stops any e