(Or at the least use a try/except here and give a nicer message before dying?)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1590447 Title: Error reporting of asio exceptions from AsioDMConnection could be better Status in Unity System Compositor: Triaged Status in unity-system-compositor package in Ubuntu: Triaged Bug description: At least in this one case. Josh Arenson and I were debugging a problem with a greeter / lightdm / unity-system-compositor. It turned out to be because lightdm was passing unity-system-compositor "--from-dm-fd=0" which resulted in an asio exception when it tried to use fd 0. But the exception looked like: """ ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION) Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> > std::exception::what: assign: Operation not permitted """ It took us a surprising amount of effort to track down where this was actually failing (which was the usc::AsioDMConnection::AsioDMConnection constructor in src/asio_dm_connection.cpp). I don't have a suggested fix, just a request to make similar failure- hunts easier. Or at the least, this specific error case more obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1590447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
