lxsession risks filling disk with improper log handling

[Dennis Knorr]

My PC run for 2-3 days, and this evening, when i came back from work, the computer was full, since the .cache/lxsession/Lubuntu/run.log was 600gb.
the applications which were running are firefox and ktorrent.
Obviously, i cannot upload the file and i will not keep it...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lxsession 0.4.9.2+git20140410-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Oct 1 20:06:19 2014
SourcePackage: lxsession
UpgradeStatus: No upgrade log present (probably fresh install)

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

hi again. :) please monitor that location for additional writes. if
you see more in the run.log, please post the results here or parse it
for something useful! have you had any `lxsession` crashes recently?
there appears to be at least one other similar problem
(http://homeduino.blogspot.com/2014/05/lubuntu-installing-vnc-server.html)
which resulted from a bad `lxsession` call. this may be your problem.
see if `ps` can give you the flags `lxsession` is running with. not
sure if it spawns again, but that may be a good place to start.

On Wed, Oct 1, 2014 at 11:10 AM, Dennis Knorr
<email address hidden> wrote:
> Public bug reported:
>
> My PC run for 2-3 days, and this evening, when i came back from work, the computer was full, since the .cache/lxsession/Lubuntu/run.log was 600gb.
> the applications which were running are firefox and ktorrent.
> Obviously, i cannot upload the file and i will not keep it...
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: lxsession 0.4.9.2+git20140410-0ubuntu1.1
> ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
> Uname: Linux 3.13.0-34-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.4
> Architecture: amd64
> CurrentDesktop: LXDE
> Date: Wed Oct 1 20:06:19 2014
> SourcePackage: lxsession
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: lxsession (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 apport-bug trusty
>
> --
> You received this bug notification because you are a member of Lubuntu
> Packages Team, which is subscribed to lxsession in Ubuntu.
> https://bugs.launchpad.net/bugs/1376380
>
> Title:
> lxsession run.log fills up disk
>
> Status in “lxsession” package in Ubuntu:
> New
>
> Bug description:
> My PC run for 2-3 days, and this evening, when i came back from work, the computer was full, since the .cache/lxsession/Lubuntu/run.log was 600gb.
> the applications which were running are firefox and ktorrent.
> Obviously, i cannot upload the file and i will not keep it...
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: lxsession 0.4.9.2+git20140410-0ubuntu1.1
> ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
> Uname: Linux 3.13.0-34-generic x86_64
> ApportVersion: 2.14.1-0ubuntu3.4
> Architecture: amd64
> CurrentDesktop: LXDE
> Date: Wed Oct 1 20:06:19 2014
> SourcePackage: lxsession
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1376380/+subscriptions

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[dj (dwight7)]

i had exactly the same problem. just came into work and run.log was 76GB. My Home partion was completely full ( glad i made it a partition ). i restarted lightdm and it cleared it out. uptime shows 1 day 22 hours. at this point run.log does not seem to be growing without bound, but there are errors in the log file.

[dj (dwight7)]

the log file looks almost like a trace file. should the logging be turned from debug to info or warning? And there are a lot of communications errors.

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

there's a similar bug on the upstream tracker: https://sourceforge.net/p/lxde/bugs/634/. it seems to me that the issue can happen for several reasons, none of which have to do with lxsession itself. however, i think that how lxsession handles logs makes no sense.

[Lyn Perrine (walterorlin)]

Yes there is no way to patch every game which might make a call to lxsession or similar appliaction with developers that might not have much care for lxde.

[Dennis Knorr (dennis-knorr)]

That may be, but then the session log must be under rotation.

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

Agree. This is still an issue with lxsession: improper handling of logging.

[ambossarm (ambossarm)]

Just had a full home disk. Problem was mplayer writing "seek failed" into run.log for the last day. I had a broken video file, that I deleted when it did not start. Seems that one or two mplayer kept running in the background. Had to kill it with -9.

[Christopher Redden (christopher-redden)]

I am getting this on Lubuntu 16.04. Is there a way to disable run.log? Every few weeks I have to delete it.

[Javier Marino (marino-javier)]

hi everyone

Any fix fot this behaviour? i getting a lot using KODI, fill all my disk with the file run.log

Thanks

[Donald (78luphr0rnk2nuqimstywepozxn9kl19tqh0tx66b5dki1xxsh5mkz9gl21a5rlwfnr8jn6ln0m3jxne2k9x1ohg85w3jabxlrqbgszpjpwcmvkbcvq9spp6z3w5j1m33k06tlsf-c04cs2xj0-a811i2i3ytqlsztthjth0svbccw8inm65tmkqp9sarr553jq53in4xm1m8wn3o4rlwaer06ogwvqwv9mrqoku2x334n7di44o65qze67n1wneepmidnuwnde1rqcbpgdf70gtqq2)]

Same here.

root@raspberrypi:/home/pi/.cache/lxsession/LXDE-pi# tail -f run.log

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown desktop item

** (pcmanfm:672): WARNING **: 14:23:20.696: got unmount for unknown desktop item

In my case the funny thing is that although the root FS seems ext4 I keep getting

    write(2, "\n** (pcmanfm:672): WARNING **: 2"..., 82) = -1 EFBIG ...

when looking at the strace output of the pcmanfm process. Any new on how to avoid this?

[Elvis de Freitas Souza (edigitalb)]

It filled all my disk, when I checked it was about 50gb!

I used the following hack to fix the problem for now, removed the write permission for all users

chmod a= ~/.cache/lxsession/Lubuntu/run.log

ls -lha ~/.cache/lxsession/Lubuntu/run.log
---------- 1 typer typer 17K nov 23 21:47 /home/typer/.cache/lxsession/Lubuntu/run.log