Thanks again. Seems to be fine here, but it's tricky to debug with missing source, the first error about address 0x0 must come from "next" not working due to that. Shouldn't really matter, though.
So I'm running a little out of ideas now. It can come from a D-Bus issue, likely in conjunction with 64bits arch. Yet another try, again on the backend side: sudo killall system-tools-backends sudo gdb /usr/sbin/system-tools-backends break dispatcher.c:547 print dbus_message_get_args (message, NULL, DBUS_TYPE_UINT32, &message_uid, DBUS_TYPE_INVALID) print message_uid continue [reproduce problem] print dbus_message_get_args (message, NULL, DBUS_TYPE_UINT32, &message_uid, DBUS_TYPE_INVALID) print message_uid Another question: you say the second time you try without closing users- admin, it works. But the gdb trace from above shows that the very same issue occurs. Can you confirm the name is actually changed, or is it simply that no error is reported? After that, if I don't find the issue I'll try to test this myself on a 64 bits CPU. -- Changing the long name in users-admin to the same name results in an error https://bugs.launchpad.net/bugs/533870 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
