From Fedora Project Wiki

(add table, rephrase some parts)
mNo edit summary
Line 5: Line 5:
Purpose of this page is to list those packages and collect detailed information about reasons that cause it and possibly suggest/refer improvements if possible.
Purpose of this page is to list those packages and collect detailed information about reasons that cause it and possibly suggest/refer improvements if possible.


While reading this it should remembered that contimuing to work while files change on disk is a complex process and not always possible depending on the nature of software. Items on the list shouldn't thus be seen as bad designs.
While reading this it should remembered that contimuing to work while files change on disk is may not always possible depending on the nature of software. Thus items on the list shouldn't be seen as bad designs.





Revision as of 12:06, 7 April 2013

It's known that some Fedora packages can't be updated to if the particular packaged software is running at the same time. If these packages are updated, this will cause hangup or crash in running process when files change on disk.

This can lead to indirect security issues if all updates are suspended for long period of time while trying to avoid harmful interrupts and some critical updates don't get installed soon enough.

Purpose of this page is to list those packages and collect detailed information about reasons that cause it and possibly suggest/refer improvements if possible.

While reading this it should remembered that contimuing to work while files change on disk is may not always possible depending on the nature of software. Thus items on the list shouldn't be seen as bad designs.




package symptoms cause notes
firefox crash due to files being removed from the disk without firefox noticing. Potentially due to the nature of xul engine
kde
NetworkManager looses its network interfaces
thunderbird same as firefox