LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 03-19-2006, 05:41 PM   #1
helliax
LQ Newbie
 
Registered: Nov 2005
Distribution: Slackware 10.2
Posts: 9

Rep: Reputation: 0
"Warning: add_groups: Invalid Argument"


I started getting this message after I added myself to some groups using KDE 3.5.1's User Manager. I've got Slackware -current. I boot up into the console, and then I login using my login name (not root), the line appears right after "Password: ". However, I don't get this message if I login as root.

I've looked at the files KDE User Manager modifies, and thhey're all the ones you'd expect, the /etc/groups, shadow, etc. I also added myself to some more user groups, and then tried to find any files modified under / in the past 2 minutes, but noen of them had any "add_groups" command in the contents.

So I was wondering, has anyoen else had this problem? There seems to be only one real result when searchign on google or this forum, and that one post never got answered.
 
Old 03-19-2006, 08:27 PM   #2
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 162Reputation: 162
If the user that you're logging in as is a member of many groups and if you take that user out of most of their groups the error goes away - then yes I've had that happen.

It wasn't triggered here by joining groups. It happened after I upgraded a PC from Slackware 10.2 to Slackware current several weeks ago. I took the user out of all but 3 groups (because of the word group in the error) and the error went away. Since it was a test box, I just noted that the error happened, but haven't had a chance to go back and find the cause.

I realise that doesn't help - unless taking the user out of groups makes it go away on your setup as well.
 
Old 03-20-2006, 01:43 AM   #3
helliax
LQ Newbie
 
Registered: Nov 2005
Distribution: Slackware 10.2
Posts: 9

Original Poster
Rep: Reputation: 0
You're right, removing myself from the non-essential groups worked, and the message dissapaeared. However, when I readdded myself, so I can listen to audio, etc, the message reappeared.
 
Old 03-20-2006, 06:52 AM   #4
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 162Reputation: 162
One of the packages I upgraded at the time I noticed the problem was coreutils. In the TODO file under /usr/doc/coreutils-5.94 is the following:
Code:
Implement Ulrich Drepper's suggestion to use getgrouplist rather
  than getugroups.  This affects only `id', but makes a big difference
  on systems with many users and/or groups, and makes id usable once
  again on systems where access restrictions make getugroups fail.
  But first we'll need a run-test (either in an autoconf macro or at
  run time) to avoid the segfault bug in libc-2.3.2's getgrouplist.
  In that case, we'd revert to using a new (to-be-written) getgrouplist
  module that does most of what `id' already does.
I wondered if this was related to the problem so I tried to look up man getugroups but got nothing. However man getgrouplist does provide an entry and the man page does list a bug:
Code:
       The glibc 2.3.2 implementation of this function is broken: it overwrites memory when the actual number
       of groups is larger than *ngroups.
Perhaps the problem is related to this - but that's just a guess...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Getting a "KDSETKEYCODE: Invalid argument" error. sk545 Ubuntu 1 11-12-2005 05:42 AM
Cedega from Fat32 (Invalid path "." given for "--use-dos-cwd") bdox Linux - Software 0 03-30-2005 11:24 AM
Cedega and Fat32 (Invalid path "." given for "--use-dos-cwd") bdox Linux - Games 0 03-26-2005 02:48 AM
"FBIOPAN_DISPLAY invalid argument" perry Mandriva 0 05-30-2004 11:23 AM
Quagga "Can't bind socket: Invalid argument" JJX Linux - Networking 0 04-29-2004 10:21 AM


All times are GMT -5. The time now is 11:35 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration