[Bug 984785] Re: .goutputstream files polluting $HOME

[moko138]

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
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/984785

Title:
  .goutputstream files polluting $HOME

Status in The "G" Library - GLib:
  Fix Released
Status in Light Display Manager:
  New
Status in X.Org X server:
  New
Status in “glib2.0” package in Ubuntu:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “glib2.0” source package in Precise:
  Triaged
Status in “lightdm” source package in Precise:
  Invalid

Bug description:
  .goutputstream files polluting $HOME.
  Which software or operation is creating these and why?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xauth 1:1.0.6-1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia & ati
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 18 13:29:31 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin"
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xauth
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/984785/+subscriptions