Bug 362141 - Can not fully create or edit Connection
Summary: Can not fully create or edit Connection
Status: RESOLVED FIXED
Alias: None
Product: frameworks-networkmanager-qt
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
: 362310 362423 362443 362847 363255 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-23 13:50 UTC by Valdas
Modified: 2016-05-19 06:59 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of message (52.92 KB, image/png)
2016-04-23 13:51 UTC, Valdas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valdas 2016-04-23 13:50:48 UTC
If I change something in Connection settings (f.e. MTU, gateway) through NetworkManager applet and close dialog then error message popups and I lost all my changes.

Excerpt from error message: connection.gateway-ping-timeout: can not set property: value...

I attaching screenshot of message;

Snippet from .xsession-errors:

QXcbConnection: XCB error: 2 (BadValue), sequence: 12829, resource id: 106954756, major code: 142 (Unknown), minor code: 3
Currrent active notifications: QHash()
Guessing partOf as: 0
 New Notification:  "Nepavyko atnaujinti ryšio Namu-laidinis" "connection.gateway-ping-timeout: can not set property: value \"41457456\" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint'" -1 & Part of: 0
D-Bus call: "org.kde.Spectacle" : "/" : "StartAgent" : ()

I encounter this when installed Kubuntu 16.04 (freshly). This happens even in LiveCD session.

Reproducible: Always

Steps to Reproduce:
1. right click on Connection icon and choose "Configure connections...";
2. create or edit existing connection;
3. change something, f.e. fill inn fixed IP, DNS, gateway, or change MTU;
4. close dialog -> error message;
5. reopen last edited Connection -> all changes reverted to default
Comment 1 Valdas 2016-04-23 13:51:44 UTC
Created attachment 98536 [details]
Screenshot of message
Comment 2 Jan Grulich 2016-04-23 17:51:45 UTC
This is caused by latest NetworkManager and should be fixed in upcoming frameworks release, see:

Git commit 93faf9ec94826c5d753aa090313472800ee41b86 by Jan Grulich.
Committed on 04/04/2016 at 08:20.
Pushed by grulich into branch 'master'.

ConnectionSettings: Initialize gateway ping timeout

NM 1.2.0 is really strict about what we send when adding or updating connection

M  +3    -0    src/settings/connectionsettings.cpp
Comment 3 Jan Grulich 2016-04-26 16:06:02 UTC
*** Bug 362310 has been marked as a duplicate of this bug. ***
Comment 4 Jan Grulich 2016-04-29 06:14:36 UTC
*** Bug 362443 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2016-05-02 02:24:57 UTC
*** Bug 362423 has been marked as a duplicate of this bug. ***
Comment 6 Jan Grulich 2016-05-09 09:07:29 UTC
*** Bug 362847 has been marked as a duplicate of this bug. ***
Comment 7 Ovidiu-Florin BOGDAN 2016-05-09 09:23:34 UTC
What is the frameworks version we should expect this fix to be in?
Comment 8 Jan Grulich 2016-05-09 11:29:24 UTC
It should be already in KDE Frameworks 5.21 and if not then definitely in 5.22 which is going to be released this week.
Comment 9 Jan Grulich 2016-05-19 06:59:39 UTC
*** Bug 363255 has been marked as a duplicate of this bug. ***