openSUSE 13.2 64bit KDE
User 1000 has NetworkManager running and connected via wireless. User 1001 has no icon for NetworkManager and cannot access the Internet.
Any advice will be appreciated.
Configure Desktop → Startup and Shutdown
Click the services manager (I don’t remember the exact name) in the left column.
Make sure that the Network service is checked (I don’t remember the exact name for that either). If it was not checked, then after checking, click “start” or “run” (or whatever) – or logout and login again.
Then right click on the system tray and go to tray settings. Make sure that the network applet is checked there, too.
The above is all for the user having problems. But you can check this also in the account of the user that is working, just to see what the settings are.
If all else fails, have the user logout from KDE, and login to Icewm. Then remove or rename “.kde4”. Then login again to KDE to have a new default setup. It might be that the user has been updating the setting since way back many version ago, and perhaps there some incompatibility that has crept in.
Thank you VERY much nrickert. Deleting .kde4 did the trick. It had been copied over from another machine.
Just curious (I do not use NetworjManager), how is this supposed to work when two users (or even the same user twice) are loged in at the same time? Is it just what one of them did last that counts?
The rough idea is that a connection belongs to one user. You can also have a shared connection. For a shared connection, it requires the root password to change anything. An ethernet connection is, by default, shared.
I don’t know what happens if there are two users at the same time trying to connect to the same WiFi network. I expect that the second user cannot connect, but gets to freeload on the connection setup by the first user. And if the first user logs out, then the second user loses network access until he/she connects. It’s better to make it a shared connection and avoid the problem, though doing this requires root.
I assume that the shjared connection case is in fact the same as ifup/wicked. Therefore no NM needed (I haven’t installed it e…g.) and that is not the case I ask this for.
I may have to much fantasy, but I see before my eyes two people each struggling to switch to the network of their choice. After all Unix/Linux is multi-user.
You can set a connection to be shared with all users. That’s a NetworkManager option. It does require the root password.
I may have to much fantasy, but I see before my eyes two people each struggling to switch to the network of their choice. After all Unix/Linux is multi-user.
What we normally think of as a multi-user system is better using “ifup” (or “wicked”). I’m not sure whether Unbuntu (for example) offers either of those possibilities.
But you should also consider the case of a laptop that a husband/wife share and take with them while travelling. It’s probably best to use NetworkManager for that because it is easier to configure WiFi. Probably only one will be logged in at a time.
This is my exact situation. I don’t like NetworkManager. At home I use Wicked on all the boxes, especially since my scripts for backups to a server and inter-network transfers are written for fixed addresses.
I do understand the two ways of using:
- the Computer room or Desktop way of working that always connects to the same network;
- the laptop/walk-around system, used by only one person at the time concected to what is available at that moment and place;
And I recognise that somehing like NM had to designed to care for the second case (which fact is: how do I create an interface for the end-user to do in a controled and secure way those things that require root and the knowledge of a system manager).
But my dirty mind brings me to ask how that functions in a, may be unusual, real multi-user case. After all, the same situation exists in the mounting of file systems, where the end-user connects file systems during his session. For this “desktop mounting” we had several solutions that created sometimes hilarious situations until we arrived at nowaday’s solution which recognises a session “in the seat” as the only one allowed to do this.
In short, is there also something as the “session in the seat” in NM? Or can we create “hilarious situations” witth NM also?
BTW, this is just a bit of mind exercise, not to be taken to serious.
I’ve got 2 “real world” situations here.
My parents PC has 2 wired network cards configured by NM. One is used by the household and is connected to the “main” network. The other may be used by visiting family (user: guest) and is connected to the “guest” network.
My memory is that if I was to switch user, from a household member to the guest user, both networks become active and the guest user is able to access the “main” network.
I’m unable to confirm this right now as I’ve just discovered that the ability to switch user is broken on their KDE5 desktop (and as switching user tends only to confuse my parents as well as the possible 2 connections, am not in a particular hurry to fix).
With this setup btw. Root is needed to create any type of connection. I can’t remember what but I made some changes to one of the polkit privs files.
I’ll try to look at the laptop (1 wireless card and 2 SSIDs) when it becomes free later this afternoon.
Hmm, I’d not set up a guest account on our new (TW) laptop but have just created one to try. I then switched user from myself to the new guest account.
What the KDE Network Manager app shows this first login is quite bizarre. According to that, not only am I connected to both our “abandon-all-hope” (“main” network) and “fools-rush-in” (“guest” network), I’m also connected to the network at the house that is close to our property!.
That of course is impossible but my own “abandon-all-hope” /“main” network connection has remained active. I guess that would change if say I connected to “fools-rush-in” from the guest account,
I have double checked to ensure the “abandon-all-hope” connections is for the household named users only and a new account hasn’t somehow added the new user “guest”.
I know this is drifting further away but IMO KDE Network Manager on TW is pretty much “screwed beyond redemption” when you try to have 2 users logged in (in my case via switch/new user).
I failed to get it to allow me to set up “fools-rush-in” after swiching to guest from user:jon
I logged out as both users, then logged in as user guest. I was then able to create a single) guest user account for “fools-rush-in” (guest network).
I then switch user to me, user jon. Network manager tellls me I’m connected to both in the big house near me (ie’ 2 x SKYsomething) and neither of my own (a-a-h and f-r-i) are on the connected list.
I guess the conclusion in it only can work/make sense where only one user can be logged in at a time???