Why does useradd cause a GLib-CRITICAL error?

[Jason Hsu]

The script I'm using fails at the useradd command with the following message:
(gksudo:2942): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL' 
failed

The useradd command is:
self.do_run_in_chroot(useradd -s %s -c \'%s\' -G sudo -m %s % (/bin/bash, 
setup.real_name, setup.username))

More details are at 
http://forums.linuxmint.com/viewtopic.php?f=189p=565740sid=5c6825a8521aa1383c649b74a7f70dc2#p565740
 .

Exactly what is necessary to make sure that the useradd command works properly?

-- 
Jason Hsu jhsu802...@jasonhsu.com


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120412011149.4b2421d9f31a9b2820063...@jasonhsu.com

Re: Why does useradd cause a GLib-CRITICAL error?

[Camaleón]

On Thu, 12 Apr 2012 01:11:49 -0500, Jason Hsu wrote:

 The script I'm using fails at the useradd command with the following
 message: (gksudo:2942): GLib-CRITICAL **: g_str_has_prefix: assertion
 `str != NULL' failed
 
 The useradd command is:
 self.do_run_in_chroot(useradd -s %s -c \'%s\' -G sudo -m %s %(/bin/bash, 
 setup.real_name, setup.username))
 
 More details are at
 http://forums.linuxmint.com/viewtopic.php?f=189p=565740sid=5c6825a8521aa1383c649b74a7f70dc2#p565740
 .
 
 Exactly what is necessary to make sure that the useradd command works
 properly?

So it's gksudo who complains? :-?

I don't know what can be the problem. How you considered asking also at 
debian-devel mailing list?

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jm6ti3$gu4$7...@dough.gmane.org