I discovered how to reproduce the bug with Gedit and Firefox : - Create a text file, and save it with this encoding type : "Occidental (ISO-8859-15)" - Type several lines in it. Save it again. - Go to a web page with a certain encoding, UTF8 compatible, but not compatible with "Occidental (ISO-8859-15)". - Copy a few lines including, for instance, go-to-note, or (french) "puce" (you know, that sort of symbol you can put, instead of a number or a letter, at the beginning of a line or of a paragraph, when listing items). (Sorry for my rusty english and the lack of precision). -5) Then go back to your text file : paste the formerly copied lines from the web page, but NOT at the beginning. - Have a look at the clock on your pc, memorize the time. Try to save your file : you get normally an error message, pointing the different encoding types. (You could save the copied text if you created for it a new UTF8 encoded file. It is not necessary for this experience.)
Here you are ! the new .goutputstream-XYZ123 file already exists, not empty. - Gedit, "open file", and you can see, in the dialog box, your new .goutputstream-XYZ123 file, dated when you tried unsuccessfully to save your txt file. - If you open it, you'll find only the first "Occidental (ISO-8859-15)" lines of your file, but not the end : the saving stopped when encountering different encoding. In order to get a 0 ko .goutputstream-XYZ123 file, just do the same process, but, at the 5th step, paste at the very beginning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
