Addendum to previous comment: After upgrading to Ubuntu 12.04, I also noticed I would get occasional reports that an internal error occured realated to Nautilus. It never really affected anything (apparently, apport is known to be a bit overzealous at times). I don't think it should be linked to the battery status problem but maybe it will give some hint. I pulled up the latest apport error log that was submitted:
ERROR: apport (pid 6191) Mon Jul 8 09:48:27 2013: called for pid 2150, signal 6 ERROR: apport (pid 6191) Mon Jul 8 09:48:27 2013: executable: /usr/bin/nautilus (command line "nautilus -n") ERROR: apport (pid 6191) Mon Jul 8 09:48:28 2013: gdbus call error: Error connecting: Could not connect: Connection refused ERROR: apport (pid 6191) Mon Jul 8 09:48:28 2013: debug: session gdbus call: ERROR: apport (pid 6191) Mon Jul 8 09:48:35 2013: wrote report /var/crash/_usr_bin_nautilus.1000.crash I also had a nautilus crash apport reported today that I didn't submit. I've attached the report from /var/crash/_usr_bin_lsb_release.1000.crash: ** Attachment added: "crash reporte related to nauilus" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1194563/+attachment/3738952/+files/nautiluscrash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194563 Title: No low battery notifications and no updated battery status (ACPI Errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1194563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
