@maresh no, there are no hardcoded dependencies beyond the basic boot setup, as long as the fis partitioning is the same and initramfs is used as explained above there should be no issues.
your description sounds like a race between kernel and hardware (timing issue) ... my theory would be that the kernel gets confused because HW is still initializing which makes some essential underlying service like udev fail (which in ubuntu is very closely bound to the kernel we use since we are always using the latest upstream here) ... which in turn might cause a service the applets need to fail (hal/dbus etc) ... can you compare (and probably attach) the kernels dmesg output from a boot with the function in place and one without the function in place ? @alan one easy way is to just put the keyword "text" on the kernel commandline so you get a textboot and can start gdm manually with the initscript (or just call startx and attach gdb from a different tty to the process you want to debug)... given that the whole issue looks rather like an infrastructural problem here rather than something with the applets themselves i cant tell you where to attach gdb to though, we should work our way through the stack layer by layer to see what part of the backend is exactly failing ... i would still be curious how you get a MAC address in your setup, we didnt see one and didnt get an IP durung our tests, the output of ifconfig after boot, but before a network cable is plugged in on your system would be intresting... -- notification area applets crash on login https://bugs.launchpad.net/bugs/392716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
