Assertion after package update

[Andrew Farris]

Bill Nottingham wrote:
> Andrew Farris (lordmorgul at gmail.com) said: 
>> This assertion was generated after some updates finished, and I think
>> its something PackageKit did, although at the moment I don't know if
>> its PackageKit's fault or actually the Firefox/Xulrunner package's
>> fault.  Both firefox and xulrunner updated during that operation.
>> Before I get this to bugzilla has anyone else seen it?
> 
> If FF/Xulrunner is updated, it generally needs restarted. We don't
> have metadata/a mechanism to automatically do this yet.

Thanks Bill, I know it would usually need restarted, as most apps do, but was 
wondering why it caused an assertion (not typical) when I wasn't doing anything. 
  It could have been an extension making some action, I don't know.  I'd also 
like to hear if anyone had this occur who was not using/running Firefox at the 
time of update.

I won't bugzilla this unless someone else saw it, with my large extension set 
there is no way of knowing at the moment whose fault it was.

-- 
Andrew Farris <lordmorgul at gmail.com> www.lordmorgul.net
  gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB  5BD5 5F89 8E1B 8300 BF29
  revoked key 0xC99B1DF3 no longer used
No one now has, and no one will ever again get, the big picture. - Daniel Geer
----                                                                       ----