[opensuse] networkmanager + nfs + resume
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name. On Leap422 with KDE, how do I get NetworkManager to start early enough or everything to wait until NetworkManager has an active connection? Surely this isn't such an unusual problem? -- Per Jessen, Zürich (7.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
On Leap422 with KDE, how do I get NetworkManager to start early enough or everything to wait until NetworkManager has an active connection? Surely this isn't such an unusual problem?
-- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled. I see data for each access point in /etc/Networkmanager/system-connections/. I'll try rebooting and see what happens. -- Per Jessen, Zürich (8.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation. -- Per Jessen, Zürich (8.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op dinsdag 21 februari 2017 11:25:40 CET schreef Per Jessen:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
This is after hibernation? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 11:25:40 CET schreef Per Jessen:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
This is after hibernation?
Right now, it was just a reboot. -- Per Jessen, Zürich (9.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users". Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager? -- Per Jessen, Zürich (10.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 22 febbraio 2017 09:37:47, Per Jessen ha scritto:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I have exactly the same after migrating to 42.2. Although the networkmanager driven connection is the local ethernet one, ownership all user, I get presented with the popup, in all user accounts at login. Very annoying but you can safely ignore it. Nothing happens. This must be an issue with PAM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data mercoledì 22 febbraio 2017 09:37:47, Per Jessen ha scritto:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I have exactly the same after migrating to 42.2. Although the networkmanager driven connection is the local ethernet one, ownership all user, I get presented with the popup, in all user accounts at login. Very annoying but you can safely ignore it. Nothing happens. This must be an issue with PAM
Do you use any shared/networked files over nfs, cifs etc ? -- Per Jessen, Zürich (10.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data mercoledì 22 febbraio 2017 09:37:47, Per Jessen ha scritto:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I have exactly the same after migrating to 42.2. Although the networkmanager driven connection is the local ethernet one, ownership all user, I get presented with the popup, in all user accounts at login. Very annoying but you can safely ignore it. Nothing happens. This must be an issue with PAM
I just tried ignoring it, my wifi connection did not come up until I typed in the password. -- Per Jessen, Zürich (10.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 22 februari 2017 11:14:54 schreef Per Jessen:
I just tried ignoring it, my wifi connection did not come up until I typed in the password.
When you enable the two options I wrote about before for your WiFi connection, the connection will be set up at boot time without asking for a password. The password is present in a file in /etc/NetworkManager/system-connections/ -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Freek de Kruijf wrote:
Op woensdag 22 februari 2017 11:14:54 schreef Per Jessen:
I just tried ignoring it, my wifi connection did not come up until I typed in the password.
When you enable the two options I wrote about before for your WiFi connection, the connection will be set up at boot time without asking for a password.
I have those two options enabled, I still get a pop-up asking for root password.
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully). Maybe it's stored in the kwallet? It looks like maybe kwallet isn't open at the time NetworkManager needs it. -- Per Jessen, Zürich (12.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Freek de Kruijf wrote:
Op woensdag 22 februari 2017 11:14:54 schreef Per Jessen:
I just tried ignoring it, my wifi connection did not come up until I typed in the password.
When you enable the two options I wrote about before for your WiFi connection, the connection will be set up at boot time without asking for a password.
I have those two options enabled, I still get a pop-up asking for root password.
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Maybe it's stored in the kwallet? It looks like maybe kwallet isn't open at the time NetworkManager needs it.
With the modification to dispatcher.d/nfs, on a boot-up, I now get the pop-up asking for root pasword "System policy prevents modification of network settings for all users". Once I have entered it, kwallet pops up asking for its password. My nfs and cifs shares are mounted, but owncloud still starts too early. -- Per Jessen, Zürich (12.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-22 a las 12:32 +0100, Per Jessen escribió:
Freek de Kruijf wrote:
Op woensdag 22 februari 2017 11:14:54 schreef Per Jessen:
I just tried ignoring it, my wifi connection did not come up until I typed in the password.
When you enable the two options I wrote about before for your WiFi connection, the connection will be set up at boot time without asking for a password.
I have those two options enabled, I still get a pop-up asking for root password.
I don't use permanent NFS connections on this laptop, which uses network manager. I don't get a password prompt at boot or resume.
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Mine are. The files are readable only by root, but are plain text. I could symlink the file to be stored in my encripted partition.
Maybe it's stored in the kwallet? It looks like maybe kwallet isn't open at the time NetworkManager needs it.
That could be your problem. I'm using XFCE, thus no kwallet. In order for the network to be up on boot or restore automatically, the password must be accessible on boot. The user can not be prompted for it - same as it happens wit if-up or whatever is the current name; wicked? - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlithjcACgkQja8UbcUWM1wK9QD/eNEVRKPmRnvVQ2FJX+N3Mn3U FgWYgCDe982aGzsYIe8A/22o87Fu/a7Id5BRDcV9AUCfIqphSOKcHlvAZfNx1fY1 =fFx8 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Mine are. The files are readable only by root, but are plain text. I could symlink the file to be stored in my encripted partition.
The idea of having the root password stored in clear text is mind-boggling, even if only root can read it.
Maybe it's stored in the kwallet? It looks like maybe kwallet isn't open at the time NetworkManager needs it.
That could be your problem. I'm using XFCE, thus no kwallet.
In order for the network to be up on boot or restore automatically, the password must be accessible on boot. The user can not be prompted for it - same as it happens wit if-up or whatever is the current name; wicked?
With wicked it all works, perfectly. The only reason I'm playing with NetworkManager is because wicked doesn't work on this laptop. Something to do with rfkill. -- Per Jessen, Zürich (14.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 15:02, Per Jessen wrote:
Carlos E. R. wrote:
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Mine are. The files are readable only by root, but are plain text. I could symlink the file to be stored in my encripted partition.
The idea of having the root password stored in clear text is mind-boggling, even if only root can read it.
I never said the root's password. What is stored is the WiFi password. For several networks, actually. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2017-02-22 15:02, Per Jessen wrote:
Carlos E. R. wrote:
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Mine are. The files are readable only by root, but are plain text. I could symlink the file to be stored in my encripted partition.
The idea of having the root password stored in clear text is mind-boggling, even if only root can read it.
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good. -- Per Jessen, Zürich (11.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Per, [...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required. And if so, you could perhaps avoid the question by setting up kwallet5 correctly.
-- Per Jessen, Zürich (11.3°C)
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 18:40, Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required.
If the connection is defined so that all users can use it, then it needs root's password. Otherwise, the connection is not available till the user logs in. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 22/02/17 19:34, Carlos E. R. wrote:
On 2017-02-22 18:40, Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required.
If the connection is defined so that all users can use it, then it needs root's password. Otherwise, the connection is not available till the user logs in.
EVERY boot? How stupid. That means you can't use the computer unless you know the root password. (That, or the whole point of that option is a waste of time!) Plus, what happens if the user needs the network to be up before they can log in (nfs homes, etc etc). Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-23 12:39, Wols Lists wrote:
On 22/02/17 19:34, Carlos E. R. wrote:
On 2017-02-22 18:40, Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required.
If the connection is defined so that all users can use it, then it needs root's password. Otherwise, the connection is not available till the user logs in.
EVERY boot? How stupid. That means you can't use the computer unless you know the root password.
No. Every time you want to modify the Network manager settings for that connection.
(That, or the whole point of that option is a waste of time!)
Plus, what happens if the user needs the network to be up before they can log in (nfs homes, etc etc).
Works for me. IMHO, Per has hit a bug related to KDE. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 23/02/17 11:44, Carlos E. R. wrote:
(That, or the whole point of that option is a waste of time!)
Plus, what happens if the user needs the network to be up before they can log in (nfs homes, etc etc).
Works for me. IMHO, Per has hit a bug related to KDE.
So I guess I've hit the same bug, seeing as I (obviously) run KDE too. And unfortunately, tumbleweed is NOT an option - I'm running leap because that's what I've put on my mum's computer, and she runs VirtualBox which is explicitly NOT supported on Tumbleweed :-( Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for?
Hmm, I thought it was - I'll have to double check now.
Normally *your* password is required.
Okay - that sounds weird, I'm already logged in, why does it need _my_ password? I'll check again.
And if so, you could perhaps avoid the question by setting up kwallet5 correctly.
kwallet seems to work for everything else. -- Per Jessen, Zürich (8.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required.
The pop-up window text reads: system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action: Password for root: _________________ -- Per Jessen, Zürich (8.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 21:36, Per Jessen wrote:
Michael Hirmke wrote:
are you sure, the root password is the one it asks for? Normally *your* password is required.
The pop-up window text reads:
system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action:
Password for root: _________________
Yes, that is what I expected. But why does it want to change anything? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2017-02-22 21:36, Per Jessen wrote:
Michael Hirmke wrote:
are you sure, the root password is the one it asks for? Normally *your* password is required.
The pop-up window text reads:
system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action:
Password for root: _________________
Yes, that is what I expected. But why does it want to change anything?
Dunno, it started after I enabled that option "enable for all users" (not sure about the exact text). I later tried to disable it again, but it won't let me. I untick the box, but the Ok button remains greyed out. -- Per Jessen, Zürich (8.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 22:44, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-22 21:36, Per Jessen wrote:
Michael Hirmke wrote:
are you sure, the root password is the one it asks for? Normally *your* password is required.
The pop-up window text reads:
system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action:
Password for root: _________________
Yes, that is what I expected. But why does it want to change anything?
Dunno, it started after I enabled that option "enable for all users" (not sure about the exact text). I later tried to disable it again, but it won't let me. I untick the box, but the Ok button remains greyed out.
The thing is, it has to be enabled for all users if you want the connection to be working during boot. Otherwise, it will wait till the user logs in. I think you should try with another desktop. XFCE or LXDE. For testing. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
On 2017-02-22 22:44, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-22 21:36, Per Jessen wrote:
Michael Hirmke wrote:
are you sure, the root password is the one it asks for? Normally *your* password is required.
The pop-up window text reads:
system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action:
Password for root: _________________
Yes, that is what I expected. But why does it want to change anything?
Dunno, it started after I enabled that option "enable for all users" (not sure about the exact text). I later tried to disable it again, but it won't let me. I untick the box, but the Ok button remains greyed out.
The thing is, it has to be enabled for all users if you want the connection to be working during boot. Otherwise, it will wait till the user logs in.
Aha, thanks for that explanation, I ws wondering what it meant. Well, ticking that box did not make it work during boot. When I boot up and then log in, I see the network manager icon connecting (the cirle is rotating). After 5-10 seconds the pop-up window asks for root password.
I think you should try with another desktop. XFCE or LXDE. For testing.
Maybe - I don't know how much time I want to waste on this. I would rather spend it on getting wicked to work, unfortunately noone has picked up the bugreport so far. -- Per Jessen, Zürich (6.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-23 a las 08:43 +0100, Per Jessen escribió:
Carlos E. R. wrote:
Password for root: _________________
Yes, that is what I expected. But why does it want to change anything?
Dunno, it started after I enabled that option "enable for all users" (not sure about the exact text). I later tried to disable it again, but it won't let me. I untick the box, but the Ok button remains greyed out.
The thing is, it has to be enabled for all users if you want the connection to be working during boot. Otherwise, it will wait till the user logs in.
Aha, thanks for that explanation, I ws wondering what it meant. Well, ticking that box did not make it work during boot. When I boot up and then log in, I see the network manager icon connecting (the cirle is rotating). After 5-10 seconds the pop-up window asks for root password.
Looks buggy to me.
I think you should try with another desktop. XFCE or LXDE. For testing.
Maybe - I don't know how much time I want to waste on this. I would rather spend it on getting wicked to work, unfortunately noone has picked up the bugreport so far.
I can only say that I do not get any password request on restore from hibernation or boot, and that I'm using XFCE. I do not know when the network starts, because where I am this laptop doesn't connect to anything. I may check the logs, though. 2017-02-22 01:51:29+01:00 - Booting the system now ================================================================================ Linux minas-tirith 4.4.46-11-default #1 SMP Sat Feb 4 06:07:41 UTC 2017 (f555e41) x86_64 x86_64 x86_64 GNU/Linux <5.6> 2017-02-22 01:51:33 minas-tirith rsyslogd - - - [origin software="rsyslogd" swVersion="8.4.0" x-pid="2104" x-info="http://www.rsyslog.com"] start ... <3.6> 2017-02-22 01:51:41 minas-tirith systemd 1 - - Started Network Manager Script Dispatcher Service. <0.6> 2017-02-22 01:51:42 minas-tirith kernel - - - [ 42.665047] wlan0: authenticate with 64:68:0c:74:e7:07 <3.6> 2017-02-22 01:51:49 minas-tirith avahi-daemon 2047 - - Registering new address record for 192.168.1.129 on wlan0.IPv4. <3.6> 2017-02-22 01:51:50 minas-tirith systemd 1 - - Reached target Network. Judging from the timestamps, my network is indeed started up during boot startup, before login. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliuyFoACgkQja8UbcUWM1waVgD+LtzSHsmd7vSxVl0LfYtB+gMm OuzgKB1Ia5ZMsTvCz0QA/A3I5MD+YwGRMDzKXnNnuTog0DdUb55U5mWdm8BPf23u =83dL -----END PGP SIGNATURE-----
On 23/02/17 07:43, Per Jessen wrote:
The thing is, it has to be enabled for all users if you want the
connection to be working during boot. Otherwise, it will wait till the user logs in.
Aha, thanks for that explanation, I ws wondering what it meant. Well, ticking that box did not make it work during boot. When I boot up and then log in, I see the network manager icon connecting (the cirle is rotating). After 5-10 seconds the pop-up window asks for root password.
And then it asks you for the network password, because (on my setup) it appears to have refused to save it ... :-) Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-23 a las 11:41 -0000, Wols Lists escribió:
On 23/02/17 07:43, Per Jessen wrote:
The thing is, it has to be enabled for all users if you want the
connection to be working during boot. Otherwise, it will wait till the user logs in.
Aha, thanks for that explanation, I ws wondering what it meant. Well, ticking that box did not make it work during boot. When I boot up and then log in, I see the network manager icon connecting (the cirle is rotating). After 5-10 seconds the pop-up window asks for root password.
And then it asks you for the network password, because (on my setup) it appears to have refused to save it ... :-)
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliuzLEACgkQja8UbcUWM1zz+AD/TWkZ64u6qdZzpzVu89eWew1j qbbDu3MdSdzlgE/XChYA/21DUzJoRVaPczRdgelVPvImCvfKXKg1Gl7zpUbz+i4l =VsnZ -----END PGP SIGNATURE-----
Le 23/02/2017 à 12:51, Carlos E. R. a écrit :
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead.
In one of my install it keeps asking first the root pass, then the kwallet one I didn't had time to investigate more :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-23 a las 12:55 +0100, jdd escribió:
Le 23/02/2017 à 12:51, Carlos E. R. a écrit :
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead.
In one of my install it keeps asking first the root pass, then the kwallet one
I didn't had time to investigate more :-(
It makes sense to ditch KDE >:-) - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliu06EACgkQja8UbcUWM1wj4wD/W98C/EiL7LIUkySHsvA3nGDZ Bg92aZju8VUDcn41a+AA/R8oppmanbekzdttHry84NZKRiKzeQikX3BLBacfaSIz =vzzm -----END PGP SIGNATURE-----
On 23.02.2017 12:55, jdd wrote:
Le 23/02/2017 à 12:51, Carlos E. R. a écrit :
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead.
In one of my install it keeps asking first the root pass, then the kwallet one
I didn't had time to investigate more :-(
The problem is here, that NetworkManager reads the system connection (connection made avalible to all users), and it does not contain the Wifi password. So it wants to add the password to the file, and here it asks for the root PW. Then kwallet says: don't save it, i will provide it! The solution: Edit the connection and go to the Wifi Password. The field contains 2 symbols: a eye to view the password in cleartext, and a floppy disc or a speech bubble. Click there and select to save it unencrypted for all users (symbol: 2 floppy discs). That did the trick for me.
Le 25/02/2017 à 18:44, Florian Gleixner a écrit :
On 23.02.2017 12:55, jdd wrote:
Le 23/02/2017 à 12:51, Carlos E. R. a écrit :
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead.
In one of my install it keeps asking first the root pass, then the kwallet one
I didn't had time to investigate more :-(
The problem is here, that NetworkManager reads the system connection (connection made avalible to all users), and it does not contain the Wifi password. So it wants to add the password to the file, and here it asks for the root PW. Then kwallet says: don't save it, i will provide it!
The solution:
Edit the connection and go to the Wifi Password. The field contains 2 symbols: a eye to view the password in cleartext, and a floppy disc or a speech bubble. Click there and select to save it unencrypted for all users (symbol: 2 floppy discs).
That did the trick for me.
thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-25 18:44, Florian Gleixner wrote:
On 23.02.2017 12:55, jdd wrote:
Le 23/02/2017 à 12:51, Carlos E. R. a écrit :
Maybe it wants to open the kwallet of root's. As you probably have never logged in as root in kde, it asks for root's password instead.
In one of my install it keeps asking first the root pass, then the kwallet one
I didn't had time to investigate more :-(
The problem is here, that NetworkManager reads the system connection (connection made avalible to all users), and it does not contain the Wifi password. So it wants to add the password to the file, and here it asks for the root PW. Then kwallet says: don't save it, i will provide it!
Makes sense. This is a bug. You should report it in Bugzilla.
The solution:
Edit the connection and go to the Wifi Password. The field contains 2 symbols: a eye to view the password in cleartext, and a floppy disc or a speech bubble. Click there and select to save it unencrypted for all users (symbol: 2 floppy discs).
That did the trick for me.
Or edit the file directly. Look into /etc/NetworkManager/system-connections/ for the correct file, should be obvious to find. ssid=Minhiriath2 key-mgmt=wpa-psk psk=..... -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 22/02/17 17:40, Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required. And if so, you could perhaps avoid the question by setting up kwallet5 correctly.
Or is it the kwallet password? I've forced that to a null password - I'd rather just not have kwallet but oftentimes I think security people are mad ... Every now and then (rather more often than I like) when I hit security stuff, I think that for all the use it is, the computer might as well be encased in concrete, in a locked room, with all connectivity disabled, for all the use it is seeing as security is preventing it doing any actual work. What's the point of a secure computer, if it's so secure the user can't actually use it? What's the point of having a laptop, if I can't configure it to actually get at all my files on the server? Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-23 12:36, Wols Lists wrote:
On 22/02/17 17:40, Michael Hirmke wrote:
Hi Per,
[...]
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
are you sure, the root password is the one it asks for? Normally *your* password is required. And if so, you could perhaps avoid the question by setting up kwallet5 correctly.
Or is it the kwallet password?
He gets this text: +++-------------------- system policy prevents modification of network settings for all users. An application is attempting to perform an action that requires privileges. Authentication is required to perform this action: Password for root: _________________ --------------------++- -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 2017-02-22 17:25, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-22 15:02, Per Jessen wrote:
Carlos E. R. wrote:
The password is present in a file in /etc/NetworkManager/system-connections/
Looking at the file, I see no password stored there (thankfully).
Mine are. The files are readable only by root, but are plain text. I could symlink the file to be stored in my encripted partition.
The idea of having the root password stored in clear text is mind-boggling, even if only root can read it.
I never said the root's password.
That's right, you didn't, but that is the topic here. The wifi access password has not been mentioned. The pop-up window asking for the root password started appearing after I enabled "All users may connect". There was never any problem with the wifi access other than it slow to connect. I'll disable "All users may connect", it didn't do any good.
Some people got the prompt for the WiFi password previously because kwallet was not accessible, I think. It has to ask for the root password to do changes, but I don't see why it wants to do any change. I suggest you try XFCE, set it up there. There is no wallet. Verify that those files contain the WiFi password in plain text. If it works with no prompt on boot, then change back to KDE. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
In data mercoledì 22 febbraio 2017 11:14:54, Per Jessen ha scritto:
stakanov wrote:
In data mercoledì 22 febbraio 2017 09:37:47, Per Jessen ha scritto:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen: > Because of bug#1012299, I have switched to using NetworkManager > on a new > laptop - but it doesn't really work very well. When KDE is > restarting apps that were open with resources on network drives, > they fail with "file not found" because the network drives > (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly > because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I have exactly the same after migrating to 42.2. Although the networkmanager driven connection is the local ethernet one, ownership all user, I get presented with the popup, in all user accounts at login. Very annoying but you can safely ignore it. Nothing happens. This must be an issue with PAM
I just tried ignoring it, my wifi connection did not come up until I typed in the password. Right, with wifi it is different. Only ethernet does not need a password. Do you have "secure file permissions"?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov wrote:
In data mercoledì 22 febbraio 2017 11:14:54, Per Jessen ha scritto:
stakanov wrote:
In data mercoledì 22 febbraio 2017 09:37:47, Per Jessen ha scritto:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote: > Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen: >> Because of bug#1012299, I have switched to using >> NetworkManager on a new >> laptop - but it doesn't really work very well. When KDE is >> restarting apps that were open with resources on network >> drives, they fail with "file not found" because the network >> drives (nfs,cifs) aren't mounted. Also, owncloud doesn't >> start properly because it cannot resolve the server name. > > Did you enable the option to start the network when it is > available and for all users? It will enter some data in > /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I have exactly the same after migrating to 42.2. Although the networkmanager driven connection is the local ethernet one, ownership all user, I get presented with the popup, in all user accounts at login. Very annoying but you can safely ignore it. Nothing happens. This must be an issue with PAM
I just tried ignoring it, my wifi connection did not come up until I typed in the password.
Right, with wifi it is different. Only ethernet does not need a password. Do you have "secure file permissions"?
Whatever is the default in Leap422. -- Per Jessen, Zürich (14.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 22 febbraio 2017 15:05:14, Per Jessen ha scritto:
stakanov wrote:
typed in the password.
Right, with wifi it is different. Only ethernet does not need a password. Do you have "secure file permissions"?
Whatever is the default in Leap422. The default is permission normal local and should allow network without rootpassword. Permission secure local should instead ask for root password when trying to change a network setting that you do own. At least this was the default for 42.1. Maybe the default was tightened or plasma does now what it should have done before? Actually a thing like the latter happened recently in TW with plasma asking what to do when clicking on a desktop item. As it turns out it was the normal behavior (gotten broken some time before).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 15:55, stakanov wrote:
In data mercoledì 22 febbraio 2017 15:05:14, Per Jessen ha scritto:
stakanov wrote:
typed in the password.
Right, with wifi it is different. Only ethernet does not need a password. Do you have "secure file permissions"?
Whatever is the default in Leap422. The default is permission normal local and should allow network without rootpassword. Permission secure local should instead ask for root password when trying to change a network setting that you do own. At least this was the default for 42.1. Maybe the default was tightened or plasma does now what it should have done before? Actually a thing like the latter happened recently in TW with plasma asking what to do when clicking on a desktop item. As it turns out it was the normal behavior (gotten broken some time before).
But he is not changing the settings. He is just booting the computer or resuming from suspend/hibernate. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
In data mercoledì 22 febbraio 2017 16:11:06, Carlos E. R. ha scritto:
On 2017-02-22 15:55, stakanov wrote:
In data mercoledì 22 febbraio 2017 15:05:14, Per Jessen ha scritto:
stakanov wrote:
typed in the password.
Right, with wifi it is different. Only ethernet does not need a password. Do you have "secure file permissions"?
Whatever is the default in Leap422.
The default is permission normal local and should allow network without rootpassword. Permission secure local should instead ask for root password when trying to change a network setting that you do own. At least this was the default for 42.1. Maybe the default was tightened or plasma does now what it should have done before? Actually a thing like the latter happened recently in TW with plasma asking what to do when clicking on a desktop item. As it turns out it was the normal behavior (gotten broken some time before).
But he is not changing the settings. He is just booting the computer or resuming from suspend/hibernate. Yes, I know. I had all working in 42.1 now I have the same popup in 42.2. I suppose they did change a PAM related rule. But I find PAM such a blackbox (did not really find an understandable article on how to set PAM up, how to understand the rules etc).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-22 17:07, stakanov wrote:
In data mercoledì 22 febbraio 2017 16:11:06, Carlos E. R. ha scritto:
But he is not changing the settings. He is just booting the computer or resuming from suspend/hibernate. Yes, I know. I had all working in 42.1 now I have the same popup in 42.2. I suppose they did change a PAM related rule. But I find PAM such a blackbox (did not really find an understandable article on how to set PAM up, how to understand the rules etc).
Are you using KDE? Because I don't get the prompt, and I use XFCE. Yes, PAM is a dark box. Maybe there is something in the Admin Book. (doc.opensuse.org) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Op woensdag 22 februari 2017 09:37:47 CET schreef Per Jessen:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I am using Tumbleweed with NetworkManager and only my Ethernet connection. But I do not get any popup for authentication when starting the system or starting a desktop. I do not use nfs or cifs. Could this popup for authentication have anything to do with the use of one of these? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
In data mercoledì 22 febbraio 2017 10:18:55, Freek de Kruijf ha scritto:
Op woensdag 22 februari 2017 09:37:47 CET schreef Per Jessen:
authentication have anything to do with the use of one of these? I am not using any of them both. And I am using only ethernet. Although all this, I am presented also with the popup. So personally I doubt it has to do with it.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Freek de Kruijf wrote:
Op woensdag 22 februari 2017 09:37:47 CET schreef Per Jessen:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
I am using Tumbleweed with NetworkManager and only my Ethernet connection.
Ah, maybe that's a hint - I'm using wifi. It takes longer to negotiate with the access point.
But I do not get any popup for authentication when starting the system or starting a desktop. I do not use nfs or cifs. Could this popup for authentication have anything to do with the use of one of these?
The pop up is new after I enabled that setting yesterday. It also seems quite clear what it's about "System policy prevents modification of network settings for all users". The main issue is, as I see it - NetworkManager is quite slow in starting the network (wifi), hence network shares are delayed and applications that were active with networked resources complain they cannot be accessed. Most of those can just be restarted, but owncloud needs a manual restart. It's really quite annoying. -- Per Jessen, Zürich (10.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-22 a las 11:01 +0100, Per Jessen escribió:
The pop up is new after I enabled that setting yesterday. It also seems quite clear what it's about "System policy prevents modification of network settings for all users".
I get prompted for root's password when I try to modify network settings on the applet, for the WiFi connection or ethernet connection. This makes sense when you make the connection global, not user owned.
The main issue is, as I see it - NetworkManager is quite slow in starting the network (wifi), hence network shares are delayed and applications that were active with networked resources complain they cannot be accessed. Most of those can just be restarted, but owncloud needs a manual restart. It's really quite annoying.
If you get a password prompt it will certainly be too slow. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlith7QACgkQja8UbcUWM1wpMgD9FxAjuJoQRnUbvXK/xikbXAoP D/QZD3nQM5bst8w9UQEA/iBJfW7PjWovL3kTSgDz/SfFc3maRxjR/C/8Eb6IuGg/ =WyqV -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2017-02-22 a las 11:01 +0100, Per Jessen escribió:
The pop up is new after I enabled that setting yesterday. It also seems quite clear what it's about "System policy prevents modification of network settings for all users".
I get prompted for root's password when I try to modify network settings on the applet, for the WiFi connection or ethernet connection. This makes sense when you make the connection global, not user owned.
The main issue is, as I see it - NetworkManager is quite slow in starting the network (wifi), hence network shares are delayed and applications that were active with networked resources complain they cannot be accessed. Most of those can just be restarted, but owncloud needs a manual restart. It's really quite annoying.
If you get a password prompt it will certainly be too slow.
Yes, but it is still slow even without it. I'm not impressed by NetworkManager. I thought it was meant to make things easier .... -- Per Jessen, Zürich (14.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Per, [...]
Yes, but it is still slow even without it. I'm not impressed by NetworkManager. I thought it was meant to make things easier ....
it depends :) The version in Leap 42.2 seems to be still work in progress, but the progress made in the next versions (for example in Tumbleweed) is really remarkable.
-- Per Jessen, Zürich (14.0°C)
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Per, [...]
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
do you have set "Automatically connect to this network when it is available"?
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
Meanwhile I use it without any problem. You have to "systemctl enable nfs", even if it doesn't seem to be necessary. That was my main problem when starting with this combination. And you have to have /etc/NetworkManager/dispatcher.d/nfs, which handles ups and downs for your nfs shares according to the state of your network. You could then copy this script naming it "samba" and do whatever you like using the same logics. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Michael Hirmke wrote:
Hi Per,
[...]
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
do you have set "Automatically connect to this network when it is available"?
Yep. That part works fine.
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
Meanwhile I use it without any problem.
You have to "systemctl enable nfs", even if it doesn't seem to be necessary.
Okay, I don't have that. You're right, it doesn't seem necessary, the mounts work anyway. I'll enable it.
That was my main problem when starting with this combination. And you have to have /etc/NetworkManager/dispatcher.d/nfs, which handles ups and downs for your nfs shares according to the state of your network.
Yes, that one is present.
You could then copy this script naming it "samba" and do whatever you like using the same logics.
Okay. A lot of jumping through hoops, I wish wicked just worked. -- Per Jessen, Zürich (11.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Michael Hirmke wrote:
Hi Per,
[...]
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
do you have set "Automatically connect to this network when it is available"?
Yep. That part works fine.
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
Meanwhile I use it without any problem.
You have to "systemctl enable nfs", even if it doesn't seem to be necessary.
Okay, I don't have that. You're right, it doesn't seem necessary, the mounts work anyway. I'll enable it.
We have progress - my nfs shares were mounted now. owncloud still doesn't wait. How do I make application wait for a network connection? I'm going to amend dispatcher.d/nfs to also mount cifs shares. -- Per Jessen, Zürich (11.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Per, [...]
Okay, I don't have that. You're right, it doesn't seem necessary, the mounts work anyway. I'll enable it.
We have progress - my nfs shares were mounted now. owncloud still doesn't wait. How do I make application wait for a network connection?
just the same way you now use for nfs. Create a script in /etc/NetworkManage/dispatcher.d, named "owncloud" for example. It can look similar to this snippet: ------------------------< snip snip snip >----------------------------- #!/bin/bash INTERFACE="$1" ACTION="$2" case "$ACTION" in pre-up) ;; vpn-pre-up) ;; up) for svc in owncloud blahsvc blubbsvc do _status=$( /usr/bin/sysctl is-enabled ${svc}.service ) case "$_status" in masked*|linked*) ;; *) # it is important to use "&" at least in the down cases # - the script only has a small amount of time to run, before it # gets killed to avoid blocking NetworkManager /usr/bin/sysctl restart ${svc}.service >/dev/null 2>&1 & ;; esac done ;; vpn-up) ;; pre-down) for svc in blubbsvc blahsvc owncloud do # it is important to use "&" at least in the down cases # - the script only has a small amount of time to run, before it # gets killed to avoid blocking NetworkManager /usr/bin/sysctl stop ${svc}.service >/dev/null 2>&1 & ;; esac done ;; vpn-pre-down) ;; down) ;; vpn-down) ;; esac ------------------------< snip snip snip >----------------------------- For the down cases you have to create new directories named "pre-down.d" and "vpn-pre-down.d" below /etc/NetworkManager/dispatcher.d and link the script into these directories. Be aware, though, that not all of these cases are handled correctly with NetworkManager 1.0.12, which is part of Leap 42.2. The newer versions as in Tumbleweed are dealing much better with the various conditions.
-- Per Jessen, Zürich (11.9°C)
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/02/17 08:37, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
Freek de Kruijf wrote:
Op dinsdag 21 februari 2017 09:50:42 CET schreef Per Jessen:
Because of bug#1012299, I have switched to using NetworkManager on a new laptop - but it doesn't really work very well. When KDE is restarting apps that were open with resources on network drives, they fail with "file not found" because the network drives (nfs,cifs) aren't mounted. Also, owncloud doesn't start properly because it cannot resolve the server name.
Did you enable the option to start the network when it is available and for all users? It will enter some data in /etc/Networkmanager/system-connections/
I didn't have "all users may use this network" enabled.
I've enabled it now, but it didn't improve the situation.
Having enabled "all users may use this network", I now get a pop up window on every restart or resume: "Authentication required", "System policy prevents modification of network settings for all users".
Not many bresponses to this topic - is it really so unusual to use shared drives (nfs,cifs) on system that use NetworkManager?
You're not getting what I did? A broken desktop that kept stopping responding so I could only use whatever apps I already had un-minimised and open? I think it's something that hasn't been thought through, seems badly tested, and has a whole host of "unfortunate" interactions. I had a thread on exactly this maybe a month ago, and every fix to the current problem merely brought a new one. My current bugbear is I need to use the Big Red Switch to turn my laptop off - when I try to shut it down, the network goes down before the network drives do, so systemd hangs forever trying to unmount them :-( Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Wols Lists wrote:
I had a thread on exactly this maybe a month ago, and every fix to the current problem merely brought a new one. My current bugbear is I need to use the Big Red Switch to turn my laptop off - when I try to shut it down, the network goes down before the network drives do, so systemd hangs forever trying to unmount them :-(
That one I seem to have managed to avoid (sofar). -- Per Jessen, Zürich (14.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Carlos E. R. -
Florian Gleixner -
Freek de Kruijf -
jdd -
mh＠mike.franken.de -
Per Jessen -
stakanov -
Wols Lists