Similar problem for me, on plain old Desktop Jaunty. I get these constantly as of a week ago. Main difference seems to be that mine is error 4 instead of error 6. There is no crash data in /var/crash , and the premature transition to "invalid" presuming that was the case is disappointing. The good bugs never leave behind log files where you want them to be.
In my case, I can trace exactly when the problem popped up. I installed the "ATI/AMD proprietary FGLRX graphics driver" and then switched on HDMI audio going to that card, to get sound coming out of the monitor via that connection. That all works fine, but these log entries started showing up heavily every since, continuing to today. Attached is the log segment where things started going wrong. The first crashes looked like this: Sep 14 11:24:00 grace -- MARK -- Sep 14 11:44:00 grace -- MARK -- Sep 14 12:00:01 grace kernel: [889997.051939] hal-acl-tool[31763]: segfault at 80 ip 00007f1f610f7c90 sp 00007fff26321438 error 4 in libc-2.9.so[7f1f61077000+168000] Sep 14 12:00:01 grace kernel: [889997.056091] hal-acl-tool[31766]: segfault at 80 ip 00007f6d4ba74c90 sp 00007fff1b86b9a8 error 4 in libc-2.9.so[7f6d4b9f4000+168000] Sep 14 12:00:01 grace kernel: [889997.060190] hal-acl-tool[31767]: segfault at 80 ip 00007f8413d8ec90 sp 00007fffea193908 error 4 in libc-2.9.so[7f8413d0e000+168000] Sep 14 12:05:01 grace kernel: [890297.057395] hal-acl-tool[31854]: segfault at 80 ip 00007fadf885fc90 sp 00007fff6150f1c8 error 4 in libc-2.9.so[7fadf87df000+168000] Sep 14 12:05:01 grace kernel: [890297.062342] hal-acl-tool[31861]: segfault at 80 ip 00007f0275816c90 sp 00007fff39e31528 error 4 in libc-2.9.so[7f0275796000+168000] So after months of never seeing anything interesting in the logs, just a MARK every 20 minutes most of the time, now I get these segfaults spaced exactly 5 minutes apart most of the time, always in a pair each time. And if you look at the detailed logs, they started showing up slightly before the fglrx driver started doing its thing. I'd be happy to try and accumulate a better stack trace or debug log of what's happening here to help track this down, but I'm not sure how to stop whatever hal-acl-tool is doing automatically and try running it manually instead. ** Attachment added: "Log of situation leading up to and shortly after bug appeared" https://bugs.launchpad.net/ubuntu/+source/hal/+bug/318916/+attachment/1599925/+files/361223-segfault.log -- hal acl tool has frequent segmentation faults https://bugs.launchpad.net/bugs/318916 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
