.goutputstream files polluting $HOME
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GLib |
Fix Released
|
Low
|
|||
Light Display Manager |
Fix Released
|
Medium
|
Unassigned | ||
X.Org X server |
New
|
Undecided
|
Unassigned | ||
glib2.0 (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Precise |
Won't Fix
|
Low
|
Unassigned | ||
lightdm (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
Precise |
Invalid
|
Low
|
Unassigned |
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
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
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)
Related branches
- Robert Ancell: Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 101 lines (+33/-22)1 file modifiedapisrc/xauthority.c (+33/-22)
palimmo (palimmo) wrote : | #1 |
- Dependencies.txt Edit (5.0 KiB, text/plain; charset="utf-8")
- usr_lib_nautilus.txt Edit (303 bytes, text/plain; charset="utf-8")
Fabio Marconi (fabiomarconi) wrote : | #2 |
Fabio Marconi (fabiomarconi) wrote : | #3 |
oops, i mean bug 795760
---
Ubuntu Bug Squad volunteer triager
http://
palimmo (palimmo) wrote : | #4 |
I don't think so.. Several persons have the same problem.
http://
And.. what do you mean with "sounding like your hard disk is going bad"? Could you explain in the other bug page?
thanks!
Launchpad Janitor (janitor) wrote : | #5 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in ubuntu: | |
status: | New → Confirmed |
Lucazade (lucazade) wrote : | #6 |
same here, not a hw problem
Ubuntu Foundations Team Bug Bot (crichton) wrote : | #7 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/
To change the source package that this bug is filed about visit https:/
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]
tags: | added: bot-comment |
affects: | ubuntu → nautilus (Ubuntu) |
Daniel Cordeiro (dcordeiro) wrote : | #8 |
What to do when the right package for the bug cannot be easily determined?
I don't known which package causes the bug (I don't think it is nautilus). A comment in the Ubuntu forum [http://
palimmo (palimmo) wrote : | #9 |
gtk-recordmydesktop isn't installed on my machine.
bobhuber (bobhuber-tampabay) wrote : | #10 |
gtk-recordmydesktop isn't installed on my machine either. I also am not sure which package is causing this .
Herbert Thielen (thielen) wrote : | #11 |
Seems to have something to do with X11 authorization, maybe lightdm?
$ ls -l .goutputstream-
-rw------- 1 itsme itsme 4201 Apr 27 12:21 .goutputstream-
$ file .goutputstream-
.goutputstream-
Herbert Thielen (thielen) wrote : | #12 |
Seems not to be caused by lightdm - the files are not created every time during login.
Blümchen Blau (bluemchen-blau) wrote : | #13 |
I suspect Dropbox to be the source of the problem. As recordmydesktop is not installed on my Computer and I do not use fileroller every day, but the files date back to - as far as I can remember - the day I installed the Dropbox-
Pakage is: nautilus-dropbox 0.7.1-2 from repos.
BB
Franz Schnetzinger (schnetf) wrote : | #14 |
I have the same problem:
.goutputstream-
I neither have Dropbox, fileroller, nor gtk-recordmydesktop installed.
I noticed the bug today when syncing files via Ubuntu One. When I edit (Gedit) and sync it to my other PC it appears as .goutputstream-
Daniel Cordeiro (dcordeiro) wrote : | #15 |
Hum, I just saw that all my .goutputstream-* files have exactly 51 bytes.
They all are binary files and:
$ file .goutputstream-
.goutputstream-
$ strings .goutputstream-
<my localhostname>
MIT-MAGIC-COOKIE-1
cheribibi (sergebricole) wrote : | #16 |
Same problem: many files .goutputstream -XXXXXX squat my /home.
(Precise Pangolin 64 bit)
The problem disappear (in my case) removing all package UbuntuOne from Synaptic.
Daniel Cordeiro (dcordeiro) wrote : | #17 |
I uninstalled all Ubuntu One packages yesterday and today I have one .goutputstream file on my $HOME. :(
JustinChuTw (justin-chu) wrote : | #18 |
I also have this problem. I begin to notice .goutputstream-* files appearing in /home after upgrading to Ubuntu 12.04 LTS Precise Pangolin 32 bit (fresh install). Deleting all of the .goutputstream-* files from /home do not seem to affect my system but they keep reappearing. I do not have gtk-recordmydes
cheribibi (sergebricole) wrote : | #19 |
Hey guys,
I confirm: before 3 days of intensive computer use without UbuntuOne, i have now just ONE file .goutputstream- xxxxxx in /home. ( With UbuntuOne installed, in 2-3 days of use, i have easily 10 goutputstream files).
At this point, I think the strategy "Remove Ub.One, Wait and Say" can be to consider.
?
cheribibi (sergebricole) wrote : | #20 |
Edit: sorry for my bad English... Correction of my precedent message: evidently, you have to replace "Before" with "After"
IMBJR (imbjr) wrote : | #21 |
This also affects Thunar not just Nautilus.
Krino Hoogestraat (krino) wrote : | #22 |
Same with me: Affects Thunar (Final Release – Xubuntu 12.04 LTS Precise Pangolin).
Scott Moore (scottbomb) wrote : | #23 |
I second IMBJR (imbjr). I use Xubuntu 12.04. I never saw these in 11.10. My home directory is also polluted with many of these .goutputstream-
Scott Moore (scottbomb) wrote : | #24 |
They are data files of some kind. Not viewable in a text editor.
JustinChuTw (justin-chu) wrote : | #25 |
After removing/
Hope someone who is familiar with Ubuntu ... and its variants ... will look into this problem as it is quite frustrating to see these apparently useless files appearing everyday.
Karolis (reklamukibiras) wrote : | #26 |
nautilus/
i don't have dropbox, file roller, ubuntu one, nautilus (thunar for me).
`ls -al | grep goutput` gives me this:
-rw------- 1 mdm mdm 51 May 9 16:34 .goutputstream-
-rw------- 1 mdm mdm 51 May 10 20:39 .goutputstream-
-rw------- 1 mdm mdm 51 May 10 02:45 .goutputstream-
-rw------- 1 mdm mdm 51 May 7 00:22 .goutputstream-
-rw------- 1 mdm mdm 51 May 6 19:44 .goutputstream-
-rw------- 1 mdm mdm 51 May 10 04:28 .goutputstream-
-rw------- 1 mdm mdm 51 May 11 14:52 .goutputstream-
-rw------- 1 mdm mdm 51 May 9 15:57 .goutputstream-
-rw------- 1 mdm mdm 51 May 8 14:25 .goutputstream-
which seems a lot like my computers startup times.. (or was it shutdowns?, i'll check it sometime..)
if i run `strings` on any file i get:
<hostname>
MIT-MAGIC-COOKIE-1
sg]|
all the three lines are the same for all files. I would notice the "DW" on the end of each file name. does it have something to do with "doubleword"?
before finding this bug report i was blaming gstreamer for making these files, now i'm in doubt. i've had it all the time 12.04, beta 12.04 and 11.10, running xubuntu, can't remember about ubuntu
Karolis (reklamukibiras) wrote : | #27 |
ok so i checked it with a stopwatch and it seems that upon confirmation of shutdown the file is being created
Karolis (reklamukibiras) wrote : | #28 |
really sorry for tripleposting, but on the fly bug research lead me to this:
the bug is related to "X Window authorization" or "xauth"
according to wikipedia a cookie based access:
"These cookies are created by a separate program and stored in the file .Xauthority in the user's home directory, by default."
if i run `strings .Xauthority` i get almost the same as in .goutputstream*DW:
<3 identical lines (check two posts up)>
<2 lines that repeats the first two>
question remains - how do these .Xauthority get's partially duplicated into bunch of .goutputstream* on every shutdown?
affects: | nautilus (Ubuntu) → xauth (Ubuntu) |
description: | updated |
JustinChuTw (justin-chu) wrote : | #29 |
Please refer to this post in Ubuntu Forums [ http://
I followed the advise given in Post #5 of the above by logging out before re-starting or shutting down my computer and .goutputstream-* files stop appearing when I start my computer this morning.
Sebastien Bacher (seb128) wrote : | #30 |
reassigning to nautilus, it's not likely an xauth issue, rathr a GNOME one (though not likely nautilus itself)
Changed in xauth (Ubuntu): | |
importance: | Undecided → Low |
affects: | xauth (Ubuntu) → nautilus (Ubuntu) |
Changed in nautilus (Ubuntu Precise): | |
status: | New → Confirmed |
importance: | Undecided → Low |
milestone: | none → precise-updates |
Mark Rowland (mrowland) wrote : | #31 |
Google shows instances of this bug going back to at least 2009. I had 19 of these files covering the first 13 days of May, starting when I installed Pangolin and ending when I installed Mint 12/Cinnamon to overcome an intractable printer problem. In my case all 19 files were zero bytes.
Daniel Cordeiro (dcordeiro) wrote : | #32 |
I have been using Ubuntu for several years (and on several machines) and never had this problem before.
dginsd (davidgardenhire) wrote : | #33 |
I have the same issue as everyone else, nothing much else to add. I don't recall these being generated in prior Ubuntu versions.
Just a thought since others have suggested removing Ubuntu one solves the problem and others that logging out before shutdown does. It would seem something needs to be changed with how shutdown stops U1. Just a thought.
mazurkin (mazurkin) wrote : | #34 |
I see no any .goutputstream files any more. I did nothing just installed all pending updates.
Dennis Baurichter (d-baurichter) wrote : | #35 |
Summary of previous comments:
- blank files (#25, #31) or partial copies of .Xauthority (#11, #15, #26 / #28, mine too)
- in Ubuntu and Xubuntu (files shown by Nautilus, Thunar and ls; no file manager problem)
- created on direct shutdown (but not logout -> shutdown)
Workaround: put 'sh -c "rm ~/.goutputstrea
My Software:
- Ubuntu 12.04 amd64 (up-to-date)
- file-roller installed but usually not running (also not running on shutdown: see below)
- No gtk-recordmydes
I tried to find out which software is creating these files. I used (e.g.) inotifywait (package inotify-tools) and lsof, but it didn't work out. Probably the .goutputstream-* files are open only very short (too short for my script to catch it although run with niceness -19).
Then I simply logged all processes running with my UID (1000) in an endless loop (i.e. until the script was terminated because of shutdown). I'll attach the script and its shortened output (removed duplicate blocks with no changes in process list and many blocks at the beginning).
The output also contains a line stating "FILE CREATED!!!" when the ~/.goutputstream-* file is created. Just before / after this gnome-session quits and lightdm is started by UID 1000 (not root as usual). I don't know, why it is started, but it is also the next process which quits.
lightdm also uses the ~/.Xauthority file. See
strings `which lightdm` | grep -iE 'output|xauth'
and the source code of lightdm:
grep -ri xauthority /path/to/
lightdm is used by Ubuntu and Xubuntu, but not Kubuntu. This fits to the previous comments.
Maybe also related: GIO (part of glib)
http://
Get own processes using this:
ps -o comm= -U 1000 -u 1000 | while read cmd; do file=$(which "$cmd") || file=$(locate -b "$cmd*"); strings -af $file | grep -E ': g.*output.*stream'; done > search.out
I assume it's a problem with lightdm, but I can't fix it. I hope my information helps.
Dennis Baurichter (d-baurichter) wrote : | #36 |
Sebastien Bacher (seb128) wrote : | #37 |
Thank you for the debug work those informations seem useful indeed ... is that specific to one of the lightdm greeters?
> Just before / after this gnome-session quits and lightdm is started by UID 1000 (not root as usual). I don't know, why it is started, but it is also the next process which quits.
do you mean that it happens at logout?
Dennis Baurichter (d-baurichter) wrote : | #38 |
> is that specific to one of the lightdm greeters?
I don't know if it's specific to unity-greeter. Maybe an Xfce / LXDE user can try the script I attached. There are also some Xubuntu users which commented on this bug.
For those who want to try my script: You should start it only just before requesting shutdown or restart. It produces a lot of output into the logfile (more time -> more output).
> do you mean that it happens at logout?
It happened on shutdown. It seems that makes a difference here (between logout and shutdown I mean; see comment #29).
I did this:
- rm ~/.goutputstream-*
- start ps-log.sh: sudo -b nice -n -19 sh ./ps-log.sh
- start gnome-session-quit --power-off and click on "Shutdown" (This should be the same as top-right button in Unity -> Shutdown -> Shutdown.)
After restarting my computer I looked into ps-log.out:
...
COMMAND
gnome-session
...
FILE CREATED!!! <-- This is the point where my script first sees an ~/.goutputstream-* file.
COMMAND
lightdm
...
Karolis (reklamukibiras) wrote : | #39 |
very nice Dennis ;)
definitely not specific to unity-greeter. xfce4-session on xubuntu12.04 produces this from Dennis script:
http://
really don't have the time now to dig into this but i'll check back with it later in more detail
Dennis Baurichter (d-baurichter) wrote : | #40 |
- Shortened version of Karolis's log Edit (3.9 KiB, text/plain)
Thank you Karolis! I downloaded your file and merged the duplicate blocks (search + replace). It's 330 lines now, instead of 3900.
Here are the diffs:
$ diff PART1 PART2
2c2
< sh
---
> lightdm # LightDM start
$ diff PART2 PART3 # "FILE CREATED!!!" is between these two (empty diff)
$ diff PART3 PART4
2d1
< lightdm # LightDM end
$ diff PART4 PART5
5d4
< xfconfd
11d9
< xfsettingsd
14d11
< gvfsd
$ diff PART5 PART6
7d6
< xfwm4
# ... and so on (only processes quitting or becoming "<defunct>" and then quitting)
When I ran my script lightdm appeared right after "FILE CREATED!!!", but it probably spawned a bit earlier, i.e. right before .goutputstream-* is created. It was also the first process to quit after the creation of .goutputstream-*.
Now, in a Xfce session, we have lightdm spawning right before .goutputstream-* is created and quitting afterwards again.
It's not a proof, but an indication.
And I have no clue why it is started (by user 1000!) at all ...
Anybody else?
Karolis (reklamukibiras) wrote : | #41 |
- ps-summary Edit (763 bytes, text/plain)
It was a bit unclear for me so I made extreemely short compare of processes that are same in both files. The bug we're in so strange that i'm starting to doubt it's lightdm issue. But highly suspected. It was one of these.
First collumn is Dennis, second mine. Notice, how lightdm was not present on Dennis machine when file created, then it comes up and dissapears.
How do you know it runs with userid 1000? How to check it on my computer? User cannot run lightdm unless --test-mode flag is on, or is there another way? Why should it testmode itself on shutdown?
bryncoles (brunomatti) wrote : | #42 |
Also been hit with this. Using Xubuntu:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Dennis Baurichter (d-baurichter) wrote : | #43 |
> Notice, how lightdm was not present on Dennis machine when file created, then it comes up and dissapears.
Maybe lightdm was actually running. This would be possible:
- ps logs running processes (started by my script)
- lightdm starts and creates .goutputstream*
- next run of ps
But it could also be possible, that lightdm was started later. I will repeat this test and comment later again.
> How do you know it runs with userid 1000? How to check it on my computer?
In my script:
> ps -o comm -U 1000 -u 1000 >> ps-log.out
man ps
> -U userlist Select by real user ID (RUID) or name.
> -u userlist Select by effective user ID (EUID) or name.
So this command only logs processes running with real or effective UID 1000. That is the UID of the user created at installation.
Karolis (reklamukibiras) wrote : | #44 |
oh yes! checked the code and then again lost my memory :). very cool time is exam session - feels like i felt from a tree
Dennis Baurichter (d-baurichter) wrote : | #45 |
- lightdm-logging.tar.gz Edit (853 bytes, application/x-tar)
> oh yes! checked the code and then again lost my memory :).
No problem. Happens :)
In short: I'm pretty sure now, that lightdm is creating these files.
In long:
I modified my ps-log.sh a bit, ran it several times and saw, that lightdm sometimes appeared in the log right before the file was created and sometimes right after it. This implies, that lightdm creates the file very fast after starting.
Also tried starting lightdm. Didn't work (maybe would have, if I had tried with --test-mode from a tty):
$ lightdm
Only root can run Light Display Manager. To run as a regular user for testing run with the --test-mode flag.
$ lightdm --test-mode
Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable.
Logged whole command line of lightdm as started on shutdown:
lightdm --session-child 12 19
--session-child is not documented in the man page.
Tried this command in a running session, but no .goutputstream-* file was created (neither in current working directory, nor in ~):
$ lightdm --session-child 12 19
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Error reading from daemon: Bad file descriptor
Failed to start PAM: System error
Then I tried logging with inotifywait and lsof (again, but modified script). This is a part of the log file:
lightdm 1348 a 9w REG 8,6 46 304928 /home/a/
-> It's really lightdm.
2 scripts + logfiles attached.
Sebastien Bacher (seb128) wrote : | #46 |
Robert, do you have any idea why lightdm would run as user and create those files when doing a shutdown?
affects: | nautilus (Ubuntu) → lightdm (Ubuntu) |
Changed in lightdm (Ubuntu Precise): | |
assignee: | nobody → Robert Ancell (robert-ancell) |
Karolis (reklamukibiras) wrote : | #47 |
what is your lightdm version? mine 1.2.1
if i do `ps -ef | grep lightdm` while writing this post i get:
root 1108 1 0 May23 ? 00:00:00 lightdm
root 15862 1108 4 May23 tty7 00:04:14 /usr/bin/X :0 -auth /var/run/
root 15916 1108 0 May23 ? 00:00:00 lightdm --session-child 12 25
there's already `--sesion-child` running as root. i couldn't find documentation anything else that running `lightdm --session-child` myself:
Usage: lightdm --session-child INPUTFD OUTPUTFD
it exits with value 1 "if (argc != 4)"
looking at source code of lightdm 1.2.1 those two integers stands for "from_deamon_
running `lightdm --test-mode` on pts gives me the same Xephyr requirement, but running it on tty says:
"Failed to get D-Bus connection"
if i build ps tree `ps -ejH`:
PID PGID SID TTY TIME CMD
1108 1108 1108 ? 00:00:00 lightdm
1163 1163 1163 tty7 00:06:39 Xorg
1931 1108 1108 ? 00:00:00 lightdm
1962 1962 1962 ? 00:00:00 sh
1991 1991 1991 ? 00:00:00 ssh-agent
2008 1962 1962 ? 00:00:00 xscreensaver
2010 1962 1962 ? 00:00:00 xfce4-session
which bring me back to questioning xauth. Xorg to be more specific. Don't know why my gut says it's not lightdm..
Also - why last four processes goes under lightdm tree? from logic by process name ok, but from parent pgid logic..?
(i'm writing this post offline. second day)
so i thought let's try good old `kill -9` and what i discovered - killing lightdm doesn't do anything besides hanging the pc, but killing Xorg (in pts hangs, in tty restarts gui interface in pts) and both ways killing Xorg creates the file!
Dennis Baurichter (d-baurichter) wrote : | #48 |
- ps-ejH.part Edit (1.5 KiB, text/plain)
> what is your lightdm version? mine 1.2.1
Mine too, but that's no surprise. All users of (X|K|L)Ubuntu 12.04 should have LightDM 1.2.1 (unless manually changed). See http://
> ps -ef | grep lightdm
Mine is similar:
root 980 1 0 13:33 ? 00:00:00 lightdm
root 1018 980 1 13:33 tty7 00:01:23 /usr/bin/X :0 -auth /var/run/
root 1345 980 0 13:33 ? 00:00:00 lightdm --session-child 12 19
root 9934 9743 0 14:46 pts/2 00:00:00 grep --color=auto lightdm
> lightdm --session-child INPUTFD OUTPUTFD
> ... "from_deamon_
> ... "Failed to get D-Bus connection"
When using a tty there is usually no connection to D-Bus in the environment. There is an session bus set up at login for interprocess communication of desktop applications as well as an systemwide bus started by init / Upstart. (https:/
These INPUTFD and OUTPUTFD (fd = file descriptor) arguments could be the fds to use for communication with D-Bus.
> ps -ejH
See attachment. (Launchpad seems to merge all spaces and tabs into one space in comments.)
- LightDM starts Xorg
- LightDM starts another lightdm child (the `--session-child` one)
- this child starts the desktop session; here: invokes gnome-session
- all processes (more or less) necessary for the desktop session are started, including (see manpages for more information):
- shells (/bin/sh -> /bin/dash, /bin/bash), used to start further processes and in terminal windows (like gnome-terminal)
- ssh-agent for ssh-key management
- screensaver process
- many more
> parent pgid
You mean "parent pid" = "parent process id"? Wrong interpretation. See `man ps`: "PGID" = "process group ID"
> kill -9
9 SIGKILL terminates the process immediately (poor process: no chance for cleanup or other actions).
The process doesn't really receive this signal to react, but instead the kernel just kills / deletes / terminates the process.
15 SIGTERM tells the process to terminate. ("Hey you: Stop yourself or I will stop you (using SIGKILL)!" ;) ) -> chance for cleanup
SIGKILL is usually only used if SIGTERM doesn't work.
> killing lightdm doesn't do anything besides hanging the pc
When you kill lightdm (using SIGKILL), it has no chance for any reaction (including creating a .goutputstream-* file).
> killing Xorg creates the file!
Probably this happens:
Xorg gone without cleanup -> LightDM wants to quit -> LightDM creates .goutputstream-* file.
I tried sending SIGTERMs (all commands entered in a tty; before each 'kill' logged in into the session on tty7 using LightDM):
sudo kill <LightDM with '--session-child'> # login screen shown
sudo kill <LightDM without parameters, i.e. the one started by init (PPID = 1)> # no login screen or other GUI on tty7
restarting by pressing Ctrl+Alt+Del
sudo kill <X / Xorg> # login screen shown
I repeated this procedure a second time. None of them created a .goutputstream-* file.
Also note: Sometimes there was no .goutputstream-* file created when I shutdown / restarted from a running session. I saw...
Sebastien Bacher (seb128) wrote : | #49 |
there is little chance the issue is an xorg one since .goutputstream is coming from the GNOME stack and xorg doesn't those libs
Karolis (reklamukibiras) wrote : | #50 |
i have to bow to your knowledge. don't really have anything to add appart this - what if Xorg has some troubles terminating and this returns a value to lightdm causing lightdm to create a file? Or Xorg wants to create a file through it's parent process - lightdm? (is that even possible?)
i don't think i'm gonna be useful here on. too quick for me to go this far
malbo (pique-sel) wrote : | #51 |
I have the same issue with Ubuntu 12.04.
I made Comparison between Ubuntu 11.10 and Ubuntu 12.04 against "Shut down". Both install (11.10 and 12.04) are in the same PC and both use Lightdm.
1) with Ubuntu 11.10 :
- PC restart : "Shut down" > "Restart"
- At login screen, I press Ctrl+Alt+F1 and check .Xauthority file :
ls -l .Xauthority
-rw------- 1 malbo malbo 0 2012-05-25 11:39 .Xauthority
- I press Ctrl + Alt + F7 to return to login screen and log in. Since my graphic session, I check .Xauthority :
ls -l .Xauthority
-rw------- 1 malbo malbo 67 2012-05-25 11:41 .Xauthority
2) with Ubuntu 12.04
- PC restart : "Shut down" > "Restart"
- At login screen, I press Ctrl+Alt+F1 and check .Xauthority file :
ls -l .Xauthority
-rw------- 1 malbo malbo 51 mai 25 11:57 .Xauthority
- I press Ctrl + Alt + F7 to return to login screen and log in. Since my graphic session, I check .Xauthority :
ls -l .Xauthority
-rw------- 1 malbo malbo 51 mai 25 12:00 .Xauthority
My Comment :
Ubuntu 11.10 works good with "Shut down" : .Xauthority file is 0 bytes just before the opening session (it goes to 67 bytes after the login).
Ubuntu 12.04 is wrong with "Shut down" : .Xauthority file is not zero byte just before the login (it is 51 bytes and I checked
it is in the state of the opening of the previous session)
I think this anomaly is related to the creation of .goutputstream files
Simon Reed (xubuntu-o) wrote : | #52 |
I am running Xubuntu 11.10 and lightdm 1.0.6-0ubuntu1.6 and no Unity-greeter.
I have 4 of these files:
-rw------- 1 simon simon 0 2012-05-19 08:38 .goutputstream-
-rw------- 1 simon simon 0 2012-05-26 22:25 .goutputstream-
-rw------- 1 simon simon 0 2012-06-03 17:56 .goutputstream-
-rw------- 1 simon simon 0 2012-06-06 09:06 .goutputstream-
The last 3 certainly coincide with when I last rebooted my PC.
maxim (off220) wrote : | #53 |
I've found several files ~2 Gb size. Ubuntu 12.04 x86-64, gnome-shell, gdm.
Karolis (reklamukibiras) wrote : | #54 |
maxim>> could you give some more detail about what's in it? or creation datestamp?
Jimmy (jimmy-axenhus) wrote : | #55 |
I also got this. Standard installation of Ubuntu 12.04. The file is indeed only created on shutdown. I logged in and out but the file wasn't there. Once I shut down my cumputer and started it again it was there. The timestamp matches exactly the shutdown time. (I waited a few minutes before starting it again.)
$ ls -al | grep goutputstream
-rw------- 1 me me 110 jun 13 19:49 .goutputstream-
$ file .goutputstream-
.goutputstream-
N1ck 7h0m4d4k15 (nicktux) wrote : | #56 |
The fact is that problem exits..
Recently (about 5 days) i installed Ubuntu 12.04 64bit.. and here is my output
$ ls -la | grep goutputstream
-rw------- 1 me me 0 Jun 13 01:42 .goutputstream-
-rw------- 1 me me 0 Jun 13 17:29 .goutputstream-
-rw------- 1 me me 0 Jun 13 12:14 .goutputstream-
-rw------- 1 me me 0 Jun 12 18:08 .goutputstream-
-rw------- 1 me me 0 Jun 11 13:53 .goutputstream-
-rw------- 1 me me 0 Jun 13 18:37 .goutputstream-
But my files are comletely empty..
$ file ..goutputstream
.goutputstream-
They are all the same.. :empty.
Ann Brzezinski (aebrzezinski) wrote : | #57 |
I have some of these dating back to January 2012, which is about when I installed 11.10 on this computer. There are far more being created since I updated to 12.04 (mid-May). All are empty:
-rw------- 1 ann ann 0 Jun 18 06:06 .goutputstream-
-rw------- 1 ann ann 0 Jun 17 16:03 .goutputstream-
-rw------- 1 ann ann 0 Jun 17 12:19 .goutputstream-
-rw------- 1 ann ann 0 Jun 15 17:45 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 21:07 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 20:11 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 13:20 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 12:10 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 08:47 .goutputstream-
-rw------- 1 ann ann 0 Jun 14 07:12 .goutputstream-
-rw------- 1 ann ann 0 Jun 13 10:23 .goutputstream-
-rw------- 1 ann ann 0 Jun 12 15:00 .goutputstream-
-rw------- 1 ann ann 0 Jun 12 12:18 .goutputstream-
-rw------- 1 ann ann 0 Jun 11 07:27 .goutputstream-
-rw------- 1 ann ann 0 Jun 10 15:47 .goutputstream-
-rw------- 1 ann ann 0 Jun 10 15:10 .goutputstream-
-rw------- 1 ann ann 0 Jun 9 19:53 .goutputstream-
-rw------- 1 ann ann 0 Jun 9 14:40 .goutputstream-
-rw------- 1 ann ann 0 Jun 9 14:03 .goutputstream-
-rw------- 1 ann ann 0 Jun 9 13:31 .goutputstream-
-rw------- 1 ann ann 0 Jun 9 12:36 .goutputstream-
-rw------- 1 ann ann 0 Jun 8 18:22 .goutputstream-
-rw------- 1 ann ann 0 Jun 8 08:57 .goutputstream-
-rw------- 1 ann ann 0 Jun 7 17:13 .goutputstream-
-rw------- 1 ann ann 0 Jun 6 18:29 .goutputstream-
-rw------- 1 ann ann 0 Jun 6 06:10 .goutputstream-
-rw------- 1 ann ann 0 Jun 4 08:45 .goutputstream-
-rw------- 1 ann ann 0 Jun 3 21:29 .goutputstream-
-rw------- 1 ann ann 0 Jun 3 18:15 .goutputstream-
-rw------- 1 ann ann 0 May 31 07:21 .goutputstream-
-rw------- 1 ann ann 0 May 29 22:58 .goutputstream-
-rw------- 1 ann ann 0 May 27 13:08 .goutputstream-
-rw------- 1 ann ann 0 May 26 18:00 .goutputstream-
-rw------- 1 ann ann 0 May 26 05:30 .goutputstream-
-rw------- 1 ann ann 0 May 23 17:24 .goutputstream-
-rw------- 1 ann ann 0 May 15 07:49 .goutputstream-
-rw------- 1 ann ann 0 May 13 07:20 .goutputstream-
-rw------- 1 ann ann 0 Apr 12 18:23 .goutputstream-
-rw------- 1 ann ann 0 Mar 10 05:26 .goutputstream-
-rw------- 1 ann ann 0 Feb 18 17:05 .goutputstream-
-rw------- 1 ann ann 0 Feb 8 19:48 .goutputstream-
-rw------- 1 ann ann 0 Feb 6 18:36 .goutputstream-
-rw------- 1 ann ann 0 Feb 2 16:50 .goutputstream-
-rw------- 1 ann ann 0 Jan 30 09:22 .goutputstream-
-rw------- 1 ann ann 0 Jan 28 04:42 .goutputstream-
-rw------- 1 ann ann 0 Jan 27 11:56 .goutputstream-
I just noticed these things this morning so I can't accurately associate them with a particular activity, but I did think it should be noted that some were created while running 11.10.
Michael (mnichau) wrote : | #58 |
I have 1 dated from January, and the rest (all empty) from the moment I installed Precise:
$ ls -trl .goutputstream-*
-rw------- 1 michael michael 0 Jan 29 04:28 .goutputstream-
-rw------- 1 michael michael 0 Jun 3 20:58 .goutputstream-
-rw------- 1 michael michael 0 Jun 3 22:42 .goutputstream-
-rw------- 1 michael michael 0 Jun 4 14:40 .goutputstream-
-rw------- 1 michael michael 0 Jun 4 16:51 .goutputstream-
-rw------- 1 michael michael 0 Jun 7 01:46 .goutputstream-
-rw------- 1 michael michael 0 Jun 7 08:50 .goutputstream-
-rw------- 1 michael michael 0 Jun 7 18:07 .goutputstream-
-rw------- 1 michael michael 0 Jun 8 19:16 .goutputstream-
-rw------- 1 michael michael 0 Jun 10 19:10 .goutputstream-
-rw------- 1 michael michael 0 Jun 12 15:36 .goutputstream-
-rw------- 1 michael michael 0 Jun 13 16:08 .goutputstream-
-rw------- 1 michael michael 0 Jun 15 18:43 .goutputstream-
-rw------- 1 michael michael 0 Jun 16 13:58 .goutputstream-
-rw------- 1 michael michael 0 Jun 18 02:11 .goutputstream-
-rw------- 1 michael michael 0 Jun 21 02:20 .goutputstream-
-rw------- 1 michael michael 0 Jun 22 02:21 .goutputstream-
-rw------- 1 michael michael 0 Jun 23 04:46 .goutputstream-
-rw------- 1 michael michael 0 Jun 24 14:36 .goutputstream-
-rw------- 1 michael michael 0 Jun 25 14:48 .goutputstream-
-rw------- 1 michael michael 0 Jun 25 19:04 .goutputstream-
-rw------- 1 michael michael 0 Jun 27 08:47 .goutputstream-
-rw------- 1 michael michael 0 Jun 27 17:14 .goutputstream-
-rw------- 1 michael michael 0 Jun 28 01:26 .goutputstream-
-rw------- 1 michael michael 0 Jun 28 08:48 .goutputstream-
-rw------- 1 michael michael 0 Jun 29 20:14 .goutputstream-
-rw------- 1 michael michael 0 Jun 30 04:36 .goutputstream-
bioShark (bioshark) wrote : | #59 |
I also had a bunch of this files dating back from May.
After reading this bug report, I realized they are not vital files, so I deleted them:
rm ~/.goutputstream-*
I am even putting this command in a script and adding it to the start-up process, so that I don't get bothered about this files in the near future.
I will check this thread for future development though. You guys are amazing in debugging this issue.
Sam_ (and-sam) wrote : | #60 |
Reproducable.
Open Nautilus two pane view.
Copy a large (>1gb) file from left to right pane, it has the same title so you've been asked to replace, yes, start to copy.
The right pane displays an ephemeral .goutputstream file which disappears when the operation is finished.
N1ck 7h0m4d4k15 (nicktux) wrote : | #61 |
Yes sam_ you have right. I just replaced a large file 1.8GB .
To see .goutputstream file unhide with Ctrl+H . It stands there. It has the same size as the original file and its size ADDED to the total.
I replaced a movie file on Usb stick . Now the used space on usb-stick is 3.6GB's and both files , Original movie file and .goutputsteam file can be produced by movie player.
Affter a while (almost 2 minutes) .goutputstream file disappears and total used size returns to 1.8GB.
All this time usb-stick seems busy (light flashing) even if the replace progress finished. The light flashing stops when the .goutputstream file disappears.
Jimmy (jimmy-axenhus) wrote : | #62 |
Sam_ and NikTh: I believe that's not an issue, as the file is cleaned up for you. The issue the rest of us have is that the file is never removed, but left there. This happens only on shutdown.
Roger Warburton (r-j-warby) wrote : | #63 |
My files are still being generated by this bug,the only clue I have noticed is when I delete other files they reappear as if they haven't been deleted
N1ck 7h0m4d4k15 (nicktux) wrote : | #64 |
Jimmy yes , i just reproduced Sam's consider about this. Maybe developers understand something from this , i don't know.
The truth is that when i searched my home for this specific file i didn't see it. The file was cleaned up and i counted that an empty file (the same) will be created in my home folder . I marked up the numbers but i didn't see it.
Other .goutputsteam files are there as well. Of course i don't know how they created . For now i use a workaround like
$rm .goutputstream-*
in a script added to my startup applications.
I will continue to follow this bug , just from curiosity on how these files created.
Thanks
Sam_ (and-sam) wrote : | #65 |
Jimmy, the example was supposed to bring in another player which makes the mysterious file occur.
In ~/ the file only occured on shutdown. Since I almost never shutdown except a new kernel or else asked me to I haven't seen the file in a while.
True is that this file never got my attention on any Ubuntu until 12.04, but perhaps it was there all along and only ephemeral in /tmp or somewhere else since the manual says "it's a base class for writing output".
Seems it does some kind of file operation monitoring.
http://
Another reproducable test case shows that .goutputstream* is created in the target directory when a copy operation was terminated.
Nautilus two pane view, use context menu to copy a large (>1gb) file from left to right pane, it has the same title so you've been asked to replace, yes, start to copy and then terminate the copy operation by click on the cross of the dialog window.
It creates a .goutputstream* file.
In 2009 it was considered as bug in glib (gio), unfortunately no bug number available.
https:/
security vulnerability: | no → yes |
security vulnerability: | yes → no |
visibility: | public → private |
visibility: | private → public |
Stefan Tauner (stefanct) wrote : | #68 |
mine are either 104 or 0 bytes, but that's just because there are two keys/cookies in them:
xauth -f ~/.goutputstrea
<hostname>/unix:11 MIT-MAGIC-COOKIE-1 <key1>
<hostname>/unix:10 MIT-MAGIC-COOKIE-1 <key2>
(no idea why there are two though...)
apart from that i am using mate-desktop but also with lightdm. i am commenting only due to the size/cookie count mismatch, although i dont think it matters, sorry if it is just spam (like 50% of the messages above :)
fmarcia (franck-marcia) wrote : | #69 |
On my 12.04 install, grep found "goutputstream" in:
/usr/lib/
/usr/lib/
/usr/lib/
/usr/lib/
/usr/lib/
/usr/lib/
Maybe something to do with color profiles?
askuhn (askuhn) wrote : | #70 |
- colord SIGSEGV Edit (90.0 KiB, image/png)
Would this dialog I see several times per week agree with what fmarcia said about color profiles being related?
"Sorry, Ubuntu 12.04 has experienced an internal error..
Julien Spautz (julien-spautz) wrote : | #71 |
just noticed an xml file called .goutputstream-
Content looks like this:
<application-state>
<context id="">
<application id="gedit.desktop" open-window-
<application id="deluge.desktop" open-window-
...
<application id="deja-
<application id="yelp.desktop" open-window-
</context>
</application-
Kevin Youren (kyouren) wrote : | #72 |
I found that the program "evince" which is used for PDF reading/viewing writes to the home drive
See /etc/apparmor.
# evince creates a temporary stream file like '.goutputstream
# directory a file is saved. This allows that behavior.
owner /**/.goutputstr
Of course, several other programs could use the same technique to save status info, neglects to clean them up.
Bob Jamieson (rbjamie-k) wrote : | #73 |
Just did some simple testing on this, and shutting down completely starts these things getting deposited in /home while logging off DOESN"T. That's about as far as I can go, am certainly not as advanced as some here, but it definitely looks like the Ubuntu OS (I'm running 12.04, BTW) is the culprit.
Whatever software IS the culprit, it's extremely bothersome and annoying, so I hope the launchpad folks, or somebody, soon gets to the bottom of this!
Changed in glib: | |
importance: | Unknown → Low |
status: | Unknown → New |
jjb3nl (jjb3nl) wrote : | #74 |
On my machine (Ubuntu 12.04 x64) all the files are 0 bytes.
Andre Mangan (kyphi) wrote : | #75 |
Using LinuxMint Maya (13) Cinnamon.
Using Lightdm will produce a "goutputstream" file from second reboot on without fail. Switching the display manager to MDM (Mint Display Manager) does not produce any "goutputstream" files on reboot ever.
The finger points to Lightdm.
caersith persoana (caersith) wrote : | #76 |
Other than the home directory. It also shows up on the shared folder. I run Ubuntu 12.04 x64 on a windows 7 host with virtual box.
The interesting part is the one on the shared folder, it has 'SVG' file type with a picture in it. I wonder if I've mistakenly overwritten the damn file with inkspace.
Sebastien Bacher (seb128) wrote : | #77 |
> The finger points to Lightdm.
the bugzilla linked at the top of the page rather point to glib
Paddy Landau (paddy-landau) wrote : | #78 |
I have found that I get an empty .goutputstream file if Dropbox had run at some time during the session (even if closed before restarting). The file is created at the time of shutdown.
Pюtя Dчыэc (pidybi) wrote : | #79 |
I have the some and can't make
rm .goutputstream-* -v
every day :(
Neil (kingfisher) wrote : | #80 |
They are created in my home directory when I use remmina to connect to the desktop of a another pc on my lan
Dennis Baurichter (d-baurichter) wrote : | #81 |
pidybi:
> I have the some and can't make
>
> rm .goutputstream-* -v
>
> every day :(
Just put this command into autorun (in system menu top left on screen):
sh -c "rm ~/.goutputstream-*"
OrangeCrate (bluesan) wrote : | #82 |
After a kernel update today, to 3.2.0-30, I now have a string of .goutputstream files in my home directory. I'm using Xubuntu 12.04.
Exeleration-G (exeleration-g) wrote : | #83 |
I'm probably having this issue because of running mplayer as a cronjob every day.
Chascon (chascone) wrote : | #84 |
"I'd say this is a bug in glib (gio) where it needs to remove the target
if cancelled at the "wrong" place.¨
https:/
Changed in glib2.0 (Ubuntu): | |
importance: | Undecided → Low |
Changed in glib2.0 (Ubuntu Precise): | |
importance: | Undecided → Low |
Launchpad Janitor (janitor) wrote : | #85 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in glib2.0 (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in glib2.0 (Ubuntu): | |
status: | New → Confirmed |
Collin O'Reilly (collin-o) wrote : | #87 |
Hi all - I have the same issue with Precise 64 bit and the many .goutputstream files, dating back to the day I setup my workstation with Precise (clean install), and the lightdm discussion here rang a bell.
I have done some tweaking to lightdm, and I wonder if this is causging the problem...??? Happens on ALL my Precise machines, all of which are 64 bit, all of which I've done the exact same lightdm tweaks.
First, my lightdm.conf file...
[SeatDefaults]
user-session=
greeter-
greeter-
allow-guest=false
Then I have done the following to set a custom wall paper for lightdm (since hiding users in lightdm results in the default lightdm wallpaper at the login screen). I chose a wallpaper I wanted to use and just named it lightdm.jpg
sudo xhost +SI:localuser:
sudo su lightdm -s /bin/bash
gsettings set com.canonical.
Now, I am not as technically minded as all you fine people, but I can surf and find solutions for things I want to accomplish, although granted, I do not unstand many of them as well as I should, but life and Linux is a learning process... always some new challenge to figure out, which is what makes Linux so enjoyable...
Anyway, hope my info helps, or at least makes a lightbulb go off for someone else...!!!
Hibou57 (Yannick Duchêne) (yannick-duchene) wrote : | #88 |
I also sometime had some in my Desktop folder.
Karolis (reklamukibiras) wrote : | #89 |
ok, i've wrote a lot before while i was using presice (though i find it not so useful), but now i'm testing quantal and here the sum of what i've found - i have to excuse, because i didn't have enough time to dig in to it:
it seems that goutputstream* files are not generated on every single shutdown operation. however, it is being generated. i haven't inspected the time of creation or the process of creation, sorry about that, but in precise i have always had constantly same 52 bytes size goutputstream* files containing the same bytes in all of them. the difference were in the file name and that's it. however, in quantal i see 0 bytes long goutputstream fiels. yet again i repeat - there is no syncronization of file creation time to shutdown time, but it happens.
i promise to check it back again during the next 30 days if the bug is still around, good luck guys;]
Daniel Cordeiro (dcordeiro) wrote : | #90 |
Hi, I just want to add that this bug is still around in Ubuntu 12.10 (Quantal Quetzal).
tags: | added: quantal |
Anthony (craigslistamc) wrote : | #91 |
Still on 12.04 and i have to say i'm disappointed that rob ancell is on the case...
Alan (alanjas) wrote : | #92 |
Still on 13.04 (Raring - development branch)
tags: | added: raring |
KSSG (kssg) wrote : | #93 |
I am affected by this after I upgraded to 12.10. Not a major issue but would like to know what it is.
William Engisch (engisch) wrote : | #94 |
I have this bug with my Dell M1330 laptop that is running Xubuntu 12.04 64bit with Thunar as my file manager. It appears that it has nothing to do with file manager. I remember when I fresh installed, I had some problems with lightdm causing slow booting that I fixed with a patch: http://
Craig Magina (craig.magina) wrote : | #95 |
I see this bug on my Kubuntu 12.10 amd64 installation. I also saw it on my Kubuntu 12.04 amd64 installation. Both times I was using Lightdm and Ubuntu One.
JustinChuTw (justin-chu) wrote : | #96 |
I also want to confirm that this bug is still around in Ubuntu 12.10 Quantal Quetzal.
Until such time that a REAL fix is found, my workaround to prevent these .goutputstream-* files from overwhelming my /home is to "Log Out" before re-starting or shutting down my computer.
Paddy Landau (paddy-landau) wrote : | #97 |
I searched my computer and found that these files are also present in /var/lib/lightdm, created by user lightdm.
Look at bug #728700. The submitter of that bug thinks that this is caused by failed copies, but I have been unable to duplicate this.
Paddy Landau (paddy-landau) wrote : | #98 |
Further comments in bug #728700 led me to searching Google.
It appears that LightDM may be a red herring for this problem.
It seems to be (as far as I can tell — I may be wrong) that this is caused by glib when cancelling a file being copied, as per comment #60 and others.
Steve Sauls (steve.sauls) wrote : | #99 |
I have the same issue and I have a brand new Lenovo laptop with a fresh install of 12.10 on it. I just deleted all of my .goutputstream-* files and I am going to watch it to see if I can determine when they are created. So this is not a hardware problem or 3rd party software issues. It is happening with a clean install on a new laptop.
actionparsnip (andrew-woodhead666) wrote : | #100 |
Happens in Raring too. I have a command in /etc/rc.local to run:
rm /home/andy/
each boot
N1ck 7h0m4d4k15 (nicktux) wrote : Re: [Bug 984785] Re: .goutputstream files polluting $HOME | #101 |
On 12/01/2012 07:39 PM, actionparsnip wrote:
> Happens in Raring too. I have a command in /etc/rc.local to run:
>
> rm /home/andy/
>
> each boot
>
@actionparsnip , I have the same command at my start-up applications (no
rc.local needed as no root privileges needed to remove these files)
Changed in glib: | |
status: | New → Fix Released |
Sebastien Bacher (seb128) wrote : | #102 |
upstream commited a fix to git if somebody wants to try the change:
http://
Changed in lightdm (Ubuntu Precise): | |
assignee: | Robert Ancell (robert-ancell) → nobody |
Changed in lightdm (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in lightdm (Ubuntu Precise): | |
status: | Confirmed → Invalid |
Changed in glib2.0 (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in glib2.0 (Ubuntu Precise): | |
status: | Confirmed → Triaged |
akuma-kun (akuma-kun) wrote : | #103 |
These .goutputstream-xxx files get created everytime Ubuntu 12.04 shuts down or starts up.
I tried to fresh install several Ubuntu 12.04 flavors on several laptops and desktops to check this behavior, and it happens with ALL distros based on Ubuntu (Kubuntu, Xubuntu, UbuntuStudio, Mint, etc.).
I noticed that every time there is a file write activity, a temporary .goutputstream-xxx is created in the folder where this file write activity accours.
Say i copy a file from ~/Downloads to ~/Documents, in the ~/Documents folder there is a temporary .goutputstream-xxx file created which gets automatically deleted when the copy action finishes.
In the $HOME folder seems that these temporary .goutputstream-xxx files are not cleaned up when the Ubuntu system starts up or shuts down.
I normally run a start up script that automatically deletes these .goutputstream-xxx files in my $HOME, but it would be better if the bug that causes this is fixed.
This only happens in *buntu 12.04 not earlier.
I haven't tried 12.10.
Federico Gazaba (federico-gazaba-6) wrote : | #104 |
Have the same issue. All the files have 0 bytes but also contains "1" text inside. Date of creation seems to be same as shutdown. Affects me in two computers.
Nicolas M. (nicolas-m-le-zer0) wrote : | #105 |
As reported before, all the “.goutputstream
Now, let's focus on the other part of the problem. On every session close, LightDM needs to clean ~/.Xauthority. According to #28, there can be lines in .Xauthority that shouldn't be erased, though the last line seems to stand for the current session and should be deleted when the session is closed. I don't know well how it works, but some process (most likely XAuth) is called to remove the last cookie of .Xauthority. It works fine when you only close your session, but when you shutdown from an open session, it looks like LightDM doesn't take time to close it properly before shutting the whole system down. o_O
That results in a “.goutputstream
cousteau (cousteaulecommandant) wrote : | #106 |
Shouldn't temporary files be created in /tmp rather than $HOME?
Paddy Landau (paddy-landau) wrote : | #107 |
@cousteaulecomm
That depends on whether the contents are potentially private. As this is related to .Xauthority, according to nicolas-m-le-zer0, these files should go to the user's home folder.
rpr nospam (rpr-nospam) wrote : | #108 |
@paddy-landau: Every application that writes to /tmp can change permissions of the files in order to limit access only to the owner of the files. Log on to Ubuntu as a guest and you'll find the complete user's home directory in the /tmp/guest-* directory.
@nicolas-m-le-zer0: You probable meant to say that comment #102 mentioned a bug fix.
Paddy Landau (paddy-landau) wrote : | #109 |
@rpr-nospam — thanks for the clarification. I am aware of the permissions ability, but it is further improved if the user uses encryption on his home folder. Anyway, that is probably suitable for a separate discussion.
Regarding comment #105 by @nicolas-m-le-zer0, I have been automatically removing .Xauthority (via a logout script) when logging out since I read that comment. Unfortunately, it did not solve the problem. The .goutputstream* files were still being created and left in the home folder. I have reverted to deleting the .goutputstream* files in the logout script.
Markus Klyver (markusklyver) wrote : | #110 |
Hmm...
root@XXX:~# ls -al|fgrep '.goutput'
-rw------- 1 markus markus 0 mar 7 23:54 .goutputstream-
-rw------- 1 markus markus 0 feb 20 22:55 .goutputstream-
-rw------- 1 markus markus 0 mar 11 00:21 .goutputstream-
-rw------- 1 markus markus 0 feb 20 15:00 .goutputstream-
-rw------- 1 markus markus 0 feb 22 00:02 .goutputstream-
-rw------- 1 markus markus 0 mar 10 20:15 .goutputstream-
-rw------- 1 markus markus 0 feb 23 00:43 .goutputstream-
-rw------- 1 markus markus 0 feb 25 00:00 .goutputstream-
-rw------- 1 markus markus 0 feb 20 20:34 .goutputstream-
-rw------- 1 markus markus 0 feb 20 18:05 .goutputstream-
-rw------- 1 markus markus 0 feb 20 18:26 .goutputstream-
root@XXX:~# file .goutputstream-*
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
.goutputstream-
Why empty files?
benditoelqueviene (quasar1970) wrote : | #111 |
Same problem in Aspire 5920G with Precise 32-bit with 3.2.0-39-
Dabo Ross (daboross) wrote : | #112 |
I get these a lot with ubuntu 12.10, though they aren't really a problem as I have a script run with crontab to delete them on boot
`@reboot rm ~/.goutputstream-*`
in `crontab -e`.
It has something to do with file management, I think.
just speculating, but because everyone who has these have them with some process that edits files, like Ubuntu one/dropbox, or when booting up/shutting down. What if the process that creates goutputstream for changing files hasn't fully loaded or is shut down in the middle of an operation? (just speculating).
Russian redneck (otaku-8) wrote : | #113 |
IMHO making all "Shutdown" buttons in various *DEs work like "Logout then shutdown" can workaround or even fix many bugs including this one, especially for linux newbies. But it's a task of *DEs developers, not only Ubuntu/Unity ones.
Excuse me if i'm spamming.
Karolis (reklamukibiras) wrote : | #114 |
For a while I thought this bug has been solved, but here I am looking at my $HOME forlder again. And what I see:
-rw------- 1 root root 103 Apr 20 10:39 .Xauthority
-rw-rw-r-- 1 user user 52 Apr 10 00:57 .Xauthority.2259UW
Now what is that second one? Reminds me of good old '.goutputstream
localhost-pc
MIT-MAGIC-COOKIE-1
One eye on strangeness, though i can't recall my actions on that timestamp
geezanansa (geezanansa-ubuntu) wrote : | #115 |
Since installing 12.10 have noticed that a warning box indicates a process is not shutting down as quickly as it should be ref signon-ui at shutdown time. This could be related to the use of Ubuntu One sign in with relation to the Backup app. If Backup is closed from desktop session an Ubuntu One sign in box appears.
After noticing the hidden goutputstream files and doing a websearch then looking here it appears there is no definite cause to this happening. Reading comment #33 did motivate me to note my own observations but do not have programming experience to help identify what is the actual cause of the goutputstream files in home folder. Ref https:/
t0m5k1 (tom-tomsbox) wrote : | #116 |
ok I seem to have made some head way on this & I think this file is definitely created by a bug within xauth:
┌─(t0m5k1@
└─>(%:~)
└─>> la | grep '.goutputstream-*' && strings .goutputstream-*
-rw------- 1 t0m5k1 users 44 Sep 13 2012 .goutputstream-
-rw------- 1 t0m5k1 users 44 Sep 25 2012 .goutputstream-
-rw------- 1 t0m5k1 users 0 Apr 14 2012 .goutputstream-
-rw------- 1 t0m5k1 users 44 Sep 13 2012 .goutputstream-
-rw------- 1 t0m5k1 users 44 Dec 13 00:01 .goutputstream-
-rw------- 1 t0m5k1 users 44 Feb 28 15:55 .goutputstream-
-rw------- 1 t0m5k1 users 44 Mar 9 01:15 .goutputstream-
-rw------- 1 t0m5k1 users 44 Aug 29 2012 .goutputstream-
-rw------- 1 t0m5k1 users 44 Feb 19 23:55 .goutputstream-
-rw------- 1 t0m5k1 users 44 Mar 3 00:30 .goutputstream-
-rw------- 1 t0m5k1 users 44 Apr 20 15:05 .goutputstream-
-rw------- 1 t0m5k1 users 44 Dec 15 11:08 .goutputstream-
-rw------- 1 t0m5k1 users 44 Dec 15 11:20 .goutputstream-
-rw------- 1 t0m5k1 users 44 Nov 4 2012 .goutputstream-
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MTVG
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
MIT-MAGIC-COOKIE-1
┌─(t0m5k1@
└─>(%:~)
└─>> man xauth
<snip>
generate displayname protocolname [trusted|untrusted]
This command is similar to add. The main difference is that instead of requiring the user to supply the key data, it connects to the server specified in displayname and uses the
is treated as an abbreviation for MIT-MAGIC-COOKIE-1.
<snip>
EXAMPLE
The most common use for xauth is to extract the entry for the current display, copy it to another machine, and merge it into the user's authority file on the remote machine:
% xauth extract - $DISPLAY | ssh otherhost xauth merge -
The following command contacts the server :0 to create an authorization using the MIT-MAGIC-COOKIE-1 protocol. Clients that connect with this authorization will be untrusted.
% xauth generate :0 .
<snip>
BUGS
Users that have unsecure networks should take care to use encrypted file transfer mechanisms to copy authorization entries between machines. Similarly, the MIT-MAGIC-COOKIE-1 protocol is
not very useful in unsecure environments. Sites that are interested in additional security may need to use encrypted authorization mechanisms such as Kerberos.
moko138 (tfjb321) wrote : | #117 |
Hello,
I also have.goutputstream files polluting $HOME.
But I don't use amd64 nor lightdm.
I use Lucid ubuntu 10.04-4 with gdm
Intel(R) Pentium(R) M processor 1400MHz
Let's tell me which other informations could be useful.
Thanks
moko138 (tfjb321) wrote : | #118 |
I have to add this : I mostly have .goutputstream files also in my FAT32 personal data partition. Their content is
sometimes an intentionally pasted text (Ctrl C, Ctrl V),
sometimes a small part of a bigger txt file, but with no use of (Ctrl C, Ctrl V).
moko138 (tfjb321) wrote : | #119 |
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-
- Gedit, "open file", and you can see, in the dialog box, your new .goutputstream-
- 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-
moko138 (tfjb321) wrote : | #120 |
I made a small mistake in my #119 comment :
if I paste at the very beginning of the Occidental (ISO-8859-15) file, I do NOT get an empty file : my .goutputstream-
And one more time, I got this with a 32 bits Pentium M processor, GDM and Ubuntu 10.04 4.
Changed in lightdm: | |
status: | New → Triaged |
importance: | Undecided → Medium |
PS Jenkins bot (ps-jenkins) wrote : | #121 |
Fix committed into lp:lightdm at revision 1675, scheduled for release in lightdm, milestone Unknown
Changed in lightdm: | |
status: | Triaged → Fix Committed |
Changed in lightdm: | |
milestone: | none → 1.7.1 |
status: | Fix Committed → Fix Released |
Andrea (sammybuca) wrote : | #122 |
Hi, I have same bug. A new .goutputstream-xxx is created at every shutdown of PC.
I use gnome-panel on ubuntu 12.04 64 bit. Any suggestions?
Andrea (sammybuca) wrote : | #123 |
I have fixed the problem, simply unistalling dropbox..... I hope this can help someone else..
Forest (foresto) wrote : | #124 |
See also: #1175023
Forest (foresto) wrote : | #125 |
(Oops: I guess launchpad doesn't recognize that format for bug links. Here's a direct link.)
https:/
Mike (mrmikee) wrote : | #126 |
Same trouble here.
Win7(Host) running VirtualBox 4.2.16
Linux Mint 14 Nadia Kernel 3.5.0-17-
Guest applications Geany(1.22), Pluma(1.4.0), and Gedit (2.30.4) cannot save to existing file.
Must create new file for each save on the Vbox shared folder. Other local(guest) folders work fine.
Did not start until Virtualbox updated to 4.2.16 no problems with setup before that.
Attempting to save an existing file with modifications results in files with names like (.goutputstream
Two solutions I have found so far are:
1.) save-as a new file name each time I make a change. (terrible)
2.) open a terminal session in that folder and use nano or vi to edit text file. (no problems)
So it seems that the drive "mount" for the shared folder is ok as nano can edit files, but the "gui apps" have an issue.
Qianqian Fang (fangq) wrote : | #127 |
I am not able to log on my computer (12.04), and I noticed that everytime lightdm failed to log me in, there is a .goutputsteam-xxxx file and a sedxxxx file created under my home directory.
my computer runs nis/autofs with a home directory mapped on a file server.
I believe the bug I've seen is related to Bug #1004515, but not sure how it is related to this bug. just post here in case someone can make sense of it.
fangq@wazu:~$ ls -alt | more
total 15992
drwxr-x--- 138 fangq fangq 16384 Sep 3 13:30 .
-rw------- 1 fangq fangq 0 Sep 3 13:30 .goutputstream-
-rw-r--r-- 1 fangq fangq 35 Sep 3 13:30 .pam_environment
-rw-r--r-- 1 fangq fangq 0 Sep 3 13:30 sedP678ir
-rw------- 1 fangq fangq 0 Sep 3 13:12 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 13:12 sedHOLePA
-rw------- 1 fangq fangq 0 Sep 3 13:10 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 13:10 sedwABtEH
-rw------- 1 fangq fangq 0 Sep 3 12:58 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:58 sedmB4jfg
-rw------- 1 fangq fangq 0 Sep 3 12:54 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:54 sedCaKDJQ
-rw------- 1 fangq fangq 0 Sep 3 12:54 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:54 sedBNUaTe
-rw------- 1 fangq fangq 0 Sep 3 12:53 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:53 sed0tAN1Q
-rw------- 1 fangq fangq 0 Sep 3 12:51 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:51 sedp2WKJN
-rw------- 1 fangq fangq 0 Sep 3 12:51 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:51 sedqj5rwG
-rw------- 1 fangq fangq 0 Sep 3 12:49 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:49 sed0V3DkN
-rw------- 1 fangq fangq 0 Sep 3 12:49 .goutputstream-
-rw-r--r-- 1 fangq fangq 0 Sep 3 12:49 sedGnzVh8
-rw------- 1 fangq fangq 0 Sep 3 12:48 .bash_history
Id2ndR (id2ndr) wrote : | #128 |
It seams like it's fixed in saucy. I encountered the trouble in precise and it seams it was related to X/lightdm because of "MIT-MAGIC-COOKIE" it contains. It often occurs at the time I shut down the computer (the friday afternoon after five days being up or suspended).
Brian Murray (brian-murray) wrote : | #129 |
The commit mentioned by seb128 in comment #102 has been committed to glib2.0 in Saucy, so that bug task will be marked as Fix Released. However, it should probably also be fixed in Ubuntu 12.04 (Precise).
Changed in glib2.0 (Ubuntu): | |
status: | Fix Committed → Fix Released |
Brian Murray (brian-murray) wrote : | #130 |
If there is anybody interested in seeing this fixed in Precise and willing to perform SRU verification as detailed at http://
Paddy Landau (paddy-landau) wrote : | #131 |
@brian-murray: For 12.04, unless this bug causes failures for people, I wonder if the fix is worth the potential risk in an LTS, especially as the next LTS, 14.04, is only 6-7 months away.
However, if you do release the code for testing, I shall be happy to test it.
Jochen Fahrner (jofa) wrote : | #132 |
I found those files not only in my $HOME, but also in my NFS mounted NAS.
houstonbofh (leesharp) wrote : | #133 |
I know that 14.04 is out. However, it has regressions for many people and so 12.04 is still in wide use. The fact that this is still a bug on a new system after 2 years is truly sad.
Novastorm (novastorm87) wrote : | #134 |
Happy to test an update Brian, I would like to see this bug closed on Precise.
Sam_Ashley (a-you) wrote : | #135 |
I was until recently using ubuntu studio quantal 64 bit (now using trusty) and I happened to run across this in the apparmor profile for evince:
# evince creates a temporary stream file like '.goutputstream
# directory a file is saved. This allows that behavior.
owner /**/.goutputstr
This discovery has I think been reported here before, but in case it's useful to say, I thought to check my backup drive and discovered that indeed those goutputstream files were still piling up in ubuntu studio quantal. For example I have a backup done on 2014-06-18 and there are 3 of those files in my home directory; another backup dated 2014-04-08 has 14.
Sam_Ashley (a-you) wrote : | #136 |
If it's of interest:
At the moment there are 4 of those .goutputstream-
tags: | added: i386 |
Ken Sharp (kennybobs) wrote : | #138 |
If people stopped spamming bug reports I could find out what the cause is. At this point, with all the meaningless waffle and crap I just can't be bothered.
Steve Langasek (vorlon) wrote : | #139 |
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release
Changed in glib2.0 (Ubuntu Precise): | |
status: | Triaged → Won't Fix |
I think that is connected to bug 983059 ,sounding like your hard disk is going bad. wiki.ubuntu. com/BugSquad
---
Ubuntu Bug Squad volunteer triager
http://