Does anybody know what this means? I just upgraded 15.0 to its final state (modulo kernel since I have an out-of-tree driver I want to deal with separately) and part of that included an FF update. I have an existing FF session running that I don't want to close 60.8.0esr (64-bit) and whatever I do, including searching for this error message :( results in a window saying: XML Parsing Error: undefined entity Location: about:preferences Line Number 225, Column 39: <label class="header-name" flex="1">&paneSearchResults.title;</label> --------------------------------------^ including e.g. about:preferences Does anybody have any idea what's going on? TIA, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 08.12.19 um 21:03 schrieb Dave Howorth:
Does anybody know what this means?
I just upgraded 15.0 to its final state (modulo kernel since I have an out-of-tree driver I want to deal with separately) and part of that included an FF update. I have an existing FF session running that I don't want to close 60.8.0esr (64-bit) and whatever I do, including searching for this error message :( results in a window saying:
XML Parsing Error: undefined entity Location: about:preferences Line Number 225, Column 39: <label class="header-name" flex="1">&paneSearchResults.title;</label> --------------------------------------^
including e.g. about:preferences
Does anybody have any idea what's going on?
you said you got an FF update installed while it was running. So while the FF binary is still in memory it might do some lazy loading of things (my guess is translations here) which now do not match on disk and memory. Actually sounds quite "normal and expected" behaviour? Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 8 Dec 2019 21:12:08 +0100 Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 08.12.19 um 21:03 schrieb Dave Howorth:
Does anybody know what this means?
I just upgraded 15.0 to its final state (modulo kernel since I have an out-of-tree driver I want to deal with separately) and part of that included an FF update. I have an existing FF session running that I don't want to close 60.8.0esr (64-bit) and whatever I do, including searching for this error message :( results in a window saying:
XML Parsing Error: undefined entity Location: about:preferences Line Number 225, Column 39: <label class="header-name" flex="1">&paneSearchResults.title;</label> --------------------------------------^
including e.g. about:preferences
Does anybody have any idea what's going on?
you said you got an FF update installed while it was running. So while the FF binary is still in memory it might do some lazy loading of things (my guess is translations here) which now do not match on disk and memory. Actually sounds quite "normal and expected" behaviour?
Sorry, to me that is a bug in either the program or the environment. If FF 60.whatever is running then it should be able to keep running and whatever it needs should be kept until it terminates. Whether that is up to the program to keep whatever files it needs open or the environment not to delete components of running programs I have no idea. Sorry, I'm feeling pretty p*ss*d off after spending the entire afternoon 'chatting' with amazon about why their music store won't let me download stuff I've paid for (hence the FF upgrade) :( And yes, I have restarted FF and it works now, so it's just one more irritating bug that will never be looked at.
Wolfgang
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/12/2019 21.30, Dave Howorth wrote:
On Sun, 8 Dec 2019 21:12:08 +0100 Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 08.12.19 um 21:03 schrieb Dave Howorth:
Does anybody know what this means?
I just upgraded 15.0 to its final state (modulo kernel since I have an out-of-tree driver I want to deal with separately) and part of that included an FF update. I have an existing FF session running that I don't want to close 60.8.0esr (64-bit) and whatever I do, including searching for this error message :( results in a window saying:
XML Parsing Error: undefined entity Location: about:preferences Line Number 225, Column 39: <label class="header-name" flex="1">&paneSearchResults.title;</label> --------------------------------------^
including e.g. about:preferences
Does anybody have any idea what's going on?
you said you got an FF update installed while it was running. So while the FF binary is still in memory it might do some lazy loading of things (my guess is translations here) which now do not match on disk and memory. Actually sounds quite "normal and expected" behaviour?
Sorry, to me that is a bug in either the program or the environment. If FF 60.whatever is running then it should be able to keep running and whatever it needs should be kept until it terminates.
Well, no. When you update an application while running, you can not expect it to work stable and reliable. It make keep running, but it is just a "best effort" expectation. No warranties. You are expected to restart the application ASAP. Yes, in Linux an open file is not changed because the named file is deleted, the running apps still have access to the old file. But any new open accesses the new version. Same with programs and libraries. With a complex program such as Firefox you may be in a status where parts are still using the old version and parts the new, because there are many files. The result is unpredictable. Thus you should not run an update if you can not restart whatever it updates (even the entire system!). If you are in the middle of something in firefox, don't update it. Sorry, but that is how it is. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXe5H9QAKCRC1MxgcbY1H 1eAUAJ9F/QlyANhZr8Nvp7ofGSO9c9ri1QCfSBJ9X5KVkuJHCO4xXqozh6tqk2o= =4uLv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 9 Dec 2019 14:11:33 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/12/2019 21.30, Dave Howorth wrote:
On Sun, 8 Dec 2019 21:12:08 +0100 Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Am 08.12.19 um 21:03 schrieb Dave Howorth:
Does anybody know what this means?
I just upgraded 15.0 to its final state (modulo kernel since I have an out-of-tree driver I want to deal with separately) and part of that included an FF update. I have an existing FF session running that I don't want to close 60.8.0esr (64-bit) and whatever I do, including searching for this error message :( results in a window saying:
XML Parsing Error: undefined entity Location: about:preferences Line Number 225, Column 39: <label class="header-name" flex="1">&paneSearchResults.title;</label> --------------------------------------^
including e.g. about:preferences
Does anybody have any idea what's going on?
you said you got an FF update installed while it was running. So while the FF binary is still in memory it might do some lazy loading of things (my guess is translations here) which now do not match on disk and memory. Actually sounds quite "normal and expected" behaviour?
Sorry, to me that is a bug in either the program or the environment. If FF 60.whatever is running then it should be able to keep running and whatever it needs should be kept until it terminates.
Well, no.
When you update an application while running, you can not expect it to work stable and reliable. It make keep running, but it is just a "best effort" expectation. No warranties. You are expected to restart the application ASAP.
Yes, in Linux an open file is not changed because the named file is deleted, the running apps still have access to the old file. But any new open accesses the new version. Same with programs and libraries. With a complex program such as Firefox you may be in a status where parts are still using the old version and parts the new, because there are many files. The result is unpredictable.
Thus you should not run an update if you can not restart whatever it updates (even the entire system!). If you are in the middle of something in firefox, don't update it.
Sorry, but that is how it is.
It may be how it is, but it's not how it should be IMHO. Either the program should guarantee access to any files it may need by opening them when it starts, or the environment should provide an atomic environment to running programs, rather than switching it to the new snapshot. The old version is still there! It's btrfs!!!
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXe5H9QAKCRC1MxgcbY1H 1eAUAJ9F/QlyANhZr8Nvp7ofGSO9c9ri1QCfSBJ9X5KVkuJHCO4xXqozh6tqk2o= =4uLv -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/12/2019 17.49, Dave Howorth wrote:
On Mon, 9 Dec 2019 14:11:33 +0100 "Carlos E. R." <> wrote: On 08/12/2019 21.30, Dave Howorth wrote:
...
Well, no.
When you update an application while running, you can not expect it to work stable and reliable. It make keep running, but it is just a "best effort" expectation. No warranties. You are expected to restart the application ASAP.
Yes, in Linux an open file is not changed because the named file is deleted, the running apps still have access to the old file. But any new open accesses the new version. Same with programs and libraries. With a complex program such as Firefox you may be in a status where parts are still using the old version and parts the new, because there are many files. The result is unpredictable.
Thus you should not run an update if you can not restart whatever it updates (even the entire system!). If you are in the middle of something in firefox, don't update it.
Sorry, but that is how it is.
It may be how it is, but it's not how it should be IMHO.
Either the program should guarantee access to any files it may need by opening them when it starts, or the environment should provide an atomic environment to running programs, rather than switching it to the new snapshot. The old version is still there! It's btrfs!!!
It is not possible to be different. Wrong expectations. re btrfs, the program was not designed to run on btrfs, thanks deity. The kernel people would have to invent a new load and run function for that. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXe992QAKCRC1MxgcbY1H 1e17AJ0SrgeFnmBETYfBlDgaB1TmYbAAcgCfcjiFv/XP7Ov4hi6LKjCrgFXncRE= =xkWf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2019 10:49 AM, Dave Howorth wrote:
Sorry, but that is how it is. It may be how it is, but it's not how it should be IMHO.
Either the program should guarantee access to any files it may need by opening them when it starts, or the environment should provide an atomic environment to running programs, rather than switching it to the new snapshot. The old version is still there! It's btrfs!!!
We are victims of our own "success": [5 Big Fat Reasons Why Mutexes Suck Big Time](https://accu.org/var/uploads/journals/Overload149.pdf) (2nd Article) When we gave up deterministic code -- the writing was on the wall. Makes an actual debug of something like this impossible in some cases. -- David C. Rankin, J.D.,P.E.
participants (4)
-
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Wolfgang Rosenauer