Just throwing a suggestion out there. If i rememebr right, in tribe 4, there was a bug that was milestoned too late to make the final release, that had to do with an audit of the cupsd daemon. It wouldnt allow printing because of a conflict with apparmor. Looking at this line from dmesg
[ 48.634720] audit(1193246854.105:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=5227 profile="/usr/sbin/cupsd" [ 54.857942] Failure registering capabilities with primary security module. It seems to be doing the same. It's something so far, that i noticed everyone had in common who posted their dmesg on the forums Not everyone had the audit line. But, everyone experiencing the problem, from the collected data had the failure registering capabilities with primary security module. I installed Gutsy, fresh clean install, on my two HP laptop computers, both AMD64. I then installed it on my desktop, clean, with the i386 kernel. The desktop boots fine, the two laptops dont. The laptops have a message in their dmesg: [code][ 53.940709] Failure registering capabilities with primary security module.[/code] The desktop does not reference anything of that nature. After gathering this information, i don't know what my next step should be. Kind of hit a road block. -- [Gutsy] GNOME takes too much time to load during system boot https://bugs.launchpad.net/bugs/151544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
