[Bug 123984] Re: m-a username checking broken

2008-06-06 Thread Evan Dandrea
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on t

[Bug 123984] Re: m-a username checking broken

2008-03-18 Thread Evan Dandrea
I'm bumping this back to incomplete as the code in ubiquity for the migration-assistant page has been greatly simplified and no longer creates multiple users, thus removing the need for and in turn removing the code itself for the block in question. Are you able to reproduce this using any of the

[Bug 123984] Re: m-a username checking broken

2007-09-03 Thread Evan Dandrea
** Changed in: ubiquity (Ubuntu) Importance: Undecided => Medium -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lis

[Bug 123984] Re: m-a username checking broken

2007-09-03 Thread Nanley Chery
Messed up again -- 112811 is a duplicate of 77966. -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com htt

[Bug 123984] Re: m-a username checking broken

2007-09-03 Thread Nanley Chery
You're right, it's supposed to be a dupe of 48355 instead. This bug is about the Migration Assistant failing, I accidentally marked 112811 as a duplicate because it had all the symptoms of of this bug. I'll be more careful next time. -- m-a username checking broken https://bugs.launchpad.net/bugs

[Bug 123984] Re: m-a username checking broken

2007-09-03 Thread David Balažic
Bug 112811 is about not properly detecting a too small install partition. Are you sure it is a duplicate ? As I see it, this bug is about user creation ? -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member of Ubuntu B

[Bug 123984] Re: m-a username checking broken

2007-09-01 Thread Nanley Chery
This same bug occurred on a Feisty install: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/112811 This should be fixed in gutsy and sent to feisty as well. -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member

[Bug 123984] Re: m-a username checking broken

2007-09-01 Thread Nanley Chery
I should add that I was using Tribe 5. -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.u

[Bug 123984] Re: m-a username checking broken

2007-09-01 Thread Nanley Chery
I had the same problem: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/135656 *marking mine as a duplicate* -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubun

[Bug 123984] Re: m-a username checking broken

2007-07-25 Thread Evan Dandrea
It looks like a bug in the ubiquity end of migration-assistant. The code in gtkui.py uses '-' as a key for a null username to prevent a partially filled out user details form from appearing wherever a username is not filled in. I know that doesn't make much sense, I'll have to look over that sect

[Bug 123984] Re: m-a username checking broken

2007-07-19 Thread Colin Watson
Wow, it's trying to create a user called "-". Is m-a's username checking broken? ** Summary changed: - Gutsy Gibbon: Test of tribe 2. Installation. + m-a username checking broken -- m-a username checking broken https://bugs.launchpad.net/bugs/123984 You received this bug notification because yo