I am currently running wicd 1.6.2 on Slackware 12.2 using a slightly modified version of wicd.SlackBuild from Slackware -current. Only modification I made was txz to tgz. I know that I had to add myself to the netdev group to get wicd to work as it did before. Although, now when I log in I get this error.
I've had this warning error message before but it was removed when I removed the user from the appropriate group. Just to verify I deleted my user from the netdev group and then re-logged in and the warning message went away. Adding my user back to that group made the warning come back. Any ideas how to to get rid of this warning message?

I did a quick google search and came upon this old forum post.
http://www.linuxquestions.org/questi...gument-426383/
It just reaffirmed what I had already verified.

probably because netdev is not listed on your /etc/group since you are still running 12.2

I checked before I added my user to the group. It is listed in /etc/group.

I've seen this before, but I simply cannot remember what was causing it and how I made it go away :/
Does "shadowconfig on" as root throw any errors at you?

Here is what I get when I run "shadowconfig on".
So no errors when the command is issued. Unfortunately, only removing the user from the group prevents the error from happening.

Poke me on IRC via private msg, and if we can figure out the solution, we'll post it here. I've got a few ideas, but it will be easier to try them on IRC :-)

Someone else ran across this and sent their /etc/group file to me, and while I don't have a solution (yet?), I think I know what's causing it. Count up the groups to which you're adding the relevant user, and I suspect that it will be >16. It seems that 2^4 is the largest number of groups to which any specific user can be added to by login. :/

That's good to know for future reference. Unfortunately, I've already wiped my system clean and installed Slackware 13.0. So, I can't test this out. It seems plausible as my previous user belonged to a lot of groups.

Now I just need to figure out why plasma sometimes eats up a lot of cpu cycles and freezes the panel.

I'll confirm the problem and conjecture. Recently I tried to create a new group called mediausers, which would provide appropriate permissions for handling media files on my new HTPC. I received the same error message all the time. When I removed my normal user from the new group then the error message stopped. My normal account is a member of 16 groups.

A while back when testing Currrent I experienced the same problem with adding root to additional groups. Yup, root is a member of 16 groups.

The error seems harmless but like many error messages, is irritating.

What a silly idea!

Any possibility to patch the source code?

Yes, I will confirm this issue too. My root account has same message after logging (in my case, user root is a member of 18 groups )

Sorry, for my bad english

Small update:
1. It seems that this warning is harmless - I put root in eighteen groups, then logged in on the console, got the warning, but root is correctly placed in all eighteen groups.
2. In shadow's source directory, ./libmisc/newgrps.c has a loop starting with "i = 16" -- if you change that to "32" instead and rebuild, the warning goes away. Note that I am NOT recommending that change, especially since the warning seems harmless, because I don't know what other ramifications it might have.

Checking around the web seems to reveal that NFS is the culprit for the 16 group limit. However, there might be a patch available. This stuff is over my head and makes my eyes water.

Hi! I was also getting this warning at login. As advised from this thread, I shaved off a couple of groups from my user account, and that brought down the total number of groups I want attached to my account to 14. The warning disappeared at the subsequent logins. But I was wondering if the warning actually is harmless, and that all listed groups that need to be added to a user account is executed, or if only the first 16 list groups are added?

As mentioned a couple of posts above you. As far as we know it is harmless.