Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

2018-10-09 Thread Fabio Fantoni
Il 09/10/2018 01:12, Michael Biebl ha scritto:
> This is now waiting for an ack by the release team, see #910628
>
Good, very big thanks.



Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

2018-10-08 Thread Michael Biebl
Hi Fabio

On Thu, 15 Mar 2018 12:22:40 +0100 Fabio Fantoni
 wrote:
> Package: network-manager
> Version: 1.6.2-3
> Severity: important
> Tags: stretch
> 
> Trying Cinnamon next version (with switch to libnm) on Stretch was find that 
> it crash for this "small" upstream fix missed:
> libnm/client: proxy *_enabled and metered properties to the right object - 
> https://github.com/NetworkManager/NetworkManager/commit/c81005b84650b8e6d709ce6afda96fb55987cdb8
> Actually I'm not know other Stretch application using libnm that have/risk 
> this issue
> Other details here: https://github.com/linuxmint/Cinnamon/pull/6993
> This is for example already applied to Fedora 26 without issue FWIK: 
> https://src.fedoraproject.org/cgit/rpms/NetworkManager.git/commit/?h=f26=58e92b645a0d0b8f0b1e04116d76752e8d780bbd
> I reported this because is a important bug using libnm and can be fixed with 
> a small patch, in case there was any possibility of a new build 
> (1.6.2-3+deb9u1).
> Thanks for any reply and sorry for my bad english.

This is now waiting for an ack by the release team, see #910628

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

2018-06-26 Thread Eli Schwartz
Please note also that this commit was cherry-picked upstream for the
network-manager 1.6 and 1.8 maintenance branches.

See
https://github.com/NetworkManager/NetworkManager/commit/b2af5f7ab676675a496adfa08541ecca43a9d9f8

It would be nice to have this fixed, for reasons similar to 896818

It's a maintenance branch fix which results in software working as it
was always intended to, instead of crashing (which it was not intended
to do).

It makes users' custom scripts no longer crash and burn, and it makes
developers of software that runs on stretch, more comfortable about
considering improvements to their software which rely on libnm not being
broken.

Even if it is unlikely that newer versions of Cinnamon itself will be
backported to stretch, Linux Mint Debian Edition which is a respin of
stretch, will have those packages, Cinnamon developers will likely want
to make personal builds for testing purposes, etc. so having this not
crash can only be a good thing...

And it means upstream software can get developed faster, which in the
long run means that newer versions of Debian are more likely to see
useful improvements faster, and other distros with newer versions of
networkmanager that don't crash because of this bug, will be able to see
those improvements immediately.

-- 
Eli Schwartz
Bug Wrangler and Trusted User



Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

2018-03-15 Thread Fabio Fantoni
Package: network-manager
Version: 1.6.2-3
Severity: important
Tags: stretch

Trying Cinnamon next version (with switch to libnm) on Stretch was find that it 
crash for this "small" upstream fix missed:
libnm/client: proxy *_enabled and metered properties to the right object - 
https://github.com/NetworkManager/NetworkManager/commit/c81005b84650b8e6d709ce6afda96fb55987cdb8
Actually I'm not know other Stretch application using libnm that have/risk this 
issue
Other details here: https://github.com/linuxmint/Cinnamon/pull/6993
This is for example already applied to Fedora 26 without issue FWIK: 
https://src.fedoraproject.org/cgit/rpms/NetworkManager.git/commit/?h=f26=58e92b645a0d0b8f0b1e04116d76752e8d780bbd
I reported this because is a important bug using libnm and can be fixed with a 
small patch, in case there was any possibility of a new build (1.6.2-3+deb9u1).
Thanks for any reply and sorry for my bad english.