If I'm a dumb user, I have no idea what "HAL" is, or what "libchipcard" is, or how to "start" or "stop" them.
If libchipcard is getting started in the wrong order, then that is something that needs fixing in the packaging. If HAL is a dependency of libchipcard and is not found running (eg. HAL crashed, or was restarted during an upgrade asi in this case) then libchipcard needs to deal with that situation and cope with it, not generate errors. ...libchipcard should *check* if HAL running, before attempting to call it. If something fails and nothing has changed, trying to perform the same operation 10 seconds later is _also_ likely to fail. At no point should libchipcard ever be generating errors though its own inaction or lack of error/sanity checking before or after performing RPC. Lack of such error+sanity checking is probably also an indication of potential security issues. (Back to being a dump user---if I hit the power switch, the machine should "just work"...) -- assertion failed in file dbus-errors.c line 278. https://bugs.launchpad.net/bugs/429853 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
