OK, thanks for going though that painful process! Do you have an user
called "jnih" on your system? From the debugging I could perform, it
seems that the first argument we're passing to strcmp() is wrong, and
leads to crash while we're iterating on user "jnih". If it doesn't
exist, it's likely that the trace is corrupt.
Anyway, I'm glad to tell you that the part of the code that triggered
the problem has changed in the new release, and that it will likely no
longer crash since it now checks that the username is not NULL before
using it. That doesn't mean everything will be fine, but it will be
easier to get more informations on the real problem. And since the code
has changed, it may as well have been fixed.
Do you think you could try a LiveCD of Lucid? Since after examining the
code I don't really see what can have happened, it would be nice to
check that still occurs before we spend more time on it. Next steps will
be more complex if we have to find the culprit.
I remove the Core dump since I've saved it on my disk, leaving it public
may harm your privacy.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-system-tools (Ubuntu)
Status: New => Triaged
** Attachment removed: "CoreDump.gz"
http://launchpadlibrarian.net/38342121/CoreDump.gz
--
users-admin crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/512112
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
