https://bugs.kde.org/show_bug.cgi?id=416647
--- Comment #8 from Joan <joan.herr...@urv.cat> --- I am attaching 3 text files; the total output from console is splitted between the second and third files; in the first file there is the part of console output which I guess might be more relevant, after kbibtex execution started. Let me explain how the last seven output lines appeared: kbibtex.parts: watchableFilename is Empty kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" kbibtex.parts: watchableFilename is Empty qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14661, resource id: 55074827, major code: 40 (TranslateCoords), minor code: 0 kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" Each time I try to "Save", I get (almost immediately) these four lines on output: kbibtex.parts: watchableFilename is Empty kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" kbibtex.parts: watchableFilename is Empty and after a few seconds the floppy icon vanishes, meaning that the modified file should have been rewritten in the remote directory (but it is not, even though its time stamp is updated). The last 3 lines, qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14661, resource id: 55074827, major code: 40 (TranslateCoords), minor code: 0 kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" appear instead during the "Save as" alternative, i.e, when (successfully) saving the modified file into the remote directory with a different name. I guess the "XCB error" is unrelated to the current issue, it seems has something to do with a small window shown during the "Save as" process. Thus I would say that the relevant difference in ouptut between a failed and a successful remote save operation is, kbibtex.parts: watchableFilename is Empty showing twice per failed try. Let me also explain the results from an additional little test: this time I modified the remote file, while keeping kbibtex open (I know, a sensible user should never do this), not 'directly' (using a konsole on the server) but locally (using Kate); this is the summary (scheme) of the file update history: #1 original remote file opened locally both in kbibtex and kate #2 version modified internally in kbibtex, but cannot be updated into remote directory #3, #4, #5 subsequently modified versions in Kate, successfully updated each time in the remote directory At this point, the original (#1) file only 'lives' as a temporary file (somewhere). If now I try a "Save" in bibtex, #1 reappears again in the remote directory (it overwrites the newer version #5, previosly saved by Kate). -- You are receiving this mail because: You are watching all bug changes.
