I think I've done a bad job of describing this :^( My duplicate bug #1285033 resulted from the first boot after installation, subsequent boots seem to be OK.
The partitioning scheme or installation method seems to make little difference as I've now encountered this using manual partitioning, entire disc install, and upgrading via live DVD on a bare-metal 80GB drive using this hardware: Intel Atom CPU 230 @ 1.60GHz Intel 82945G/GZ Integrated Graphics Controller (rev 02) Intel N10/ICH 7 Family High Definition Audio Controller (rev 01) Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) 2GB DDR2 RAM The one constant is that auto-login must NOT be chosen during installation. Installations where auto-login is chosen do not seem to be effected. But the behavior is not 100% reproducible so multiple test installs may be required to reproduce this bug. So if I were to redefine what I'm seeing I'd say, "Sometimes after performing an Ubuntu GNOME installation without choosing to auto-login gdm may take a long time to appear on the initial boot which may lead a user to think the boot process is frozen but gdm will eventually appear and then apport may auto-generate this bug". I realize that "sometimes" and "may" stink in a definition but it's true in this case. The behavior is just not consistent. @ two clix, Does that definition make sense to you? Or was your experience something altogether different? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284017 Title: gnome-shell crashed with SIGABRT in g_thread_abort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1284017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
