Results 1 to 6 of 6

Thread: Warning: Critical DoS Bug in 13.04

  1. #1
    Join Date
    Nov 2007
    Beans
    93

    Warning: Critical DoS Bug in 13.04

    I know a "critical bug" is a strong statement, but I think this one qualifies. by default, X creates the .xsession file. most of the time, it is fine---except that it can completely overflow the partition. this happens due to gstreamer in my 13.04 ubuntu (it was ok in 12.10). in particular, after about 100GB of messages in .xsession like this,

    GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: assertion `timeout == 0 || bus->priv->poll != NULL' failed

    the system then comes to a halt when it runs out of space on the partition. lsof tells me that gstreamer plugs into all sorts of other processes, which means that even deleting the .xsession file does not fix the problem. basically, it seems to require a reboot.

    I would think this would be critical bug.

    I tried to change in /etc/X11/Xsession

    exec >> /dev/null 2>&1 ## iaw-change to remove huge Xsession.log file from $ERRFILE

    but this did not work. I tried a couple of other fixes, but none worked. if anyone has a solution, please let me know. right now, I am afraid to start any music.

    /iaw
    Last edited by iaw4; May 2nd, 2013 at 01:07 AM.

  2. #2
    Join Date
    Aug 2008
    Location
    Washington DC
    Beans
    2,186
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Warning: Critical DoS Bug in 13.04

    its only a DoS in the way that driving over a nail on the way to work is a DoS..

    This is more like a routine case of excessive logging..

    you might try symlinking the log file to /dev/null..
    Last edited by iponeverything; May 2nd, 2013 at 02:13 AM.

  3. #3
    Join Date
    Nov 2007
    Beans
    93

    Re: Warning: Critical DoS Bug in 13.04

    not a solution. .xsession-errors is always deleted and recreated.

    I think everything that can force a system to shut down all processes and reboot (without voluntary user choice) is a critical DoS. in Xsession, there is even a

    "truncate ERRFILE if it is too big to avoid disk usage DoS"

    unfortunately, this is only on reboot. it works for minor fillup over length periods of time that can be cured between reboots. it is not capable of dealing with rapid fillups, e.g., through the gstreamer spam.

  4. #4
    Join Date
    Nov 2007
    Beans
    93

    Re: Warning: Critical DoS Bug in 13.04

    another question---how do I restart the X server? ctrl-alt-backspace does not work for me. (maybe it's the apple keyboard.) I also don't know how to get to virtual consoles any more---ctrl-alt-F1 also does not work.

    Xsession does not seem to be executed. I put an "echo 'IAW'" at the top and looked in all the log files in /var/log/*.log --- it never shows up there. no wonder that my attempts to tinker with it to suppress creation of .xsession-errors does not work. where is .xsession-errors actually controlled under 13.04?

    right now, I am rebooting for test. yikes.



    /iaw
    Last edited by iaw4; May 2nd, 2013 at 05:31 PM.

  5. #5
    Join Date
    Nov 2007
    Beans
    93

    Re: Warning: Critical DoS Bug in 13.04

    here is how to force a system reboot: open rythmbox. go to radio. click on "Absolute Radio (Modern)" or some other station. at this point, watch .xsession-errors grow huge and crash your system.

  6. #6
    Join Date
    Apr 2013
    Beans
    18

    Re: Warning: Critical DoS Bug in 13.04

    I have the some problem, plus I use btrfs, which means that when I run out of space I can't even delete files... How do we fix this ? Has this bug been reported ?

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •