Comment 2 for bug 1505660

Something is MAJORLY wrong with something... I can't even login anymore (into KDE).
Like another user somewhere else said, normal users might just have to give up on their PC in this case :/.

Fortunately, I'm an advanced user and could log in remotely from another PC and find out
that two partitions had been filled up entirely:

1) Firstly, the partition containing /home/carlo/.cache/upstart :

-rw-r----- 1 carlo carlo 38G Mar 24 01:05 /home/carlo/.cache/upstart/startkde.log

that's 38 GB of repeated spam, and then, because this partition (.cache) ran full,

2) also my home directory partition was filled:

-rw------- 1 carlo carlo 1.5G Mar 24 00:29 .xsession-errors

with the repeated spam of 20739073 times:

init: Failed to write to log file /home/carlo/.cache/upstart/startkde.log

Really? 20739073 times? Of course it only stopped because then the
partition was full (which only had 1.5GB free).

The spam in /home/carlo/.cache/upstart/startkde.log exists of
an infinitely number of times the repeat of:

cannot connect alsa-jack.jackP.3627.0:out_000 to system:playback_1
AL lib: (EE) ALCplaybackAlsa_mixerProc: start failed: Input/output error
Server is not running

Which isn't that weird since I have to start the JACK server by hand.
Now I'm sure that whatever is flooding with this log message is in
error, but imho also upstart shouldn't create log files of 38 GB at
100 MB/s because anything is flooding it with repeated lines of
messages...