[gelöst erstmal]In /home immer 0 byte - Dateien?

Allgemeine Gespräche hinsichtlich Sabayon Linux

Moderator: Moderators

[gelöst erstmal]In /home immer 0 byte - Dateien?

Postby pitt » Mon Jun 24, 2013 7:44

Hallo,

im home-Verzeichniss sind immer Dateien (versteckte daher nicht sofort gesichtet) mit 0 Byte Namens .goutputstream-IMLEZW. Die letzten Buchstaben ändern sich. Das ständige löschen nervt da ein wenig. Ist das Problem bekannt und kann wer helfen?


Letzte Version Sabayon mit KDE SC 4.10.4, intel und nvidia GK-Treiber

Gruß
Last edited by pitt on Sun Sep 22, 2013 20:13, edited 1 time in total.
pitt
Baby Hen
 
Posts: 18
Joined: Sun Jun 09, 2013 10:40

Re: In /home immer 0 byte - Dateien?

Postby pitt » Sat Jun 29, 2013 9:07

Halo,

danke für die vielen Antworten bin begeistert. :mrgreen:

Nach langem suchen hier nun meine Ergebnisse, es ist wohl ein alter BUG von Lightdm siehe:
Code: Select all
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 ~/.goutputstream-*"' (without the single quotes) into autorun

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-recordmydesktop, Dropbox or UbuntuOne.

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/source/of/lightdm-1.2.1/src/

lightdm is used by Ubuntu and Xubuntu, but not Kubuntu. This fits to the previous comments.

Maybe also related: GIO (part of glib)
http://developer.gnome.org/gio/2.30/GOutputStream.html

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.


oder auch: Bug

wer hat den da eine alte Lightdm in Sabayon untergejubelt? Oder ist der Bug noch nicht beseitigt? :?:

Edit:Script zum löschen der Dateien im Autostartordner eingebunden, damit sind die DAteien beim Neustart erst mal gelöscht.

Gruß
pitt
Baby Hen
 
Posts: 18
Joined: Sun Jun 09, 2013 10:40


Return to German

Who is online

Users browsing this forum: No registered users and 1 guest

cron