On Wed, May 16, 2018 at 10:51:17AM +0100, Stuart Henderson wrote: > > > > More reports of the same thing are useless/counter-productive. We're > > reaching the point of diminishing returns where it takes longer to answer > > emails/classify failures into "already known/new"... > > ... which is a recipe for issues to fall between the cracks, because people > > WON'T report new issues, or they will be dismissed as the same as something > > that's already known... > > Yes, I agree. I think we should at least add the known-needed ones > like getpw (even if we don't want them long-term). We have no hope to > analyse the code and figure out a complete list of what's actually > needed as is usual with pledge..
I've added getpw and mcast in 60.0.1. > > BTW, if you're supposed to start dbus BEFORE firefox, that's cool, but then > > the firefox code should be tweaked to display "please start dbus" instead > > of the "helpful" error message "firefox crashed in a pledge violation > > (proc)". > > Simplest method is a wrapper script I think. Or telling people (via the README) to make sure its running. I hate wrapper scripts, and i'm *NOT* going to 'tweak the firefox code to display please start dbus'. If this isnt enough, someone caring enough should file bugs upstream, be it at glib or firefox.
