Why was this marked invalid? According to comment #45, it's the desktop
manager's responsibility to truncate .xsession-errors. If so, it's a kdm
bug, since I still see the same problem under KDE.
** Changed in: kdebase (Ubuntu)
Status: Invalid = New
** Summary changed:
- .xsession_errors
I have this bug with the freeRDP issue:
http://sourceforge.net/tracker/index.php?func=detailaid=3315749group_id=278330atid=1181674
Patched /etc/X11/Xsession to log errors to /dev/null.
** Bug watch added: SourceForge.net Tracker #3315749
http://sourceforge.net/support/tracker.php?aid=3315749
I have this on a fresh install of 11.04, in about 5 days without
rebooting, logging-out/in or suspending my .xsession-errors fills up to
about 140 GB. I use this system for work so this is really annoying,
rebooting or logging out/in is a hassle because I have to re-setup my
environment (I can't
I'm a bit late, but anyway, happy 5th birthday bug report!
(Last 2 recent messages show that this bug is still a major security
issue...)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
I just came across this bug report after finally tracking down my own
disk space issues to .xsession-errors.old. The file had grown to over
13 GB!
Obviously, most users are not affected by this bug, so it seems to be
triggered by excessive error reporting somewhere else. In my case, the
most
scm, as this bug has a much broader scope, I created bug 771661 for the
allow symlinks part of this. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/60448
Title:
Attached is a patch to gdm-session-worker to at least allow .xsession-
errors to be a symbolic link, so it can be manually moved elsewhere.
** Patch added: don't overwrite symlinks as symlinks, instead overwrite their
destination
Happy 4th birthday bug report!
--
.xsession_errors file grows out of control saturates disk space
https://bugs.launchpad.net/bugs/60448
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
Ive got ubuntu lucid and gnome, I don't log off, I'm running simple
lampp server. This morning I woke up to find that I had 2GB space left
because I had a massive 650GB log file in my hard drive. I deleted the
file manually, but should I just disable logging until this is fixed?
--
Is there someone from the Ubuntu Security Team /Ubuntu Review Team
listening to this report?
This bug, as I've experienced it at first (I'm the initial reporter) and
as it is experienced by other reporters here, can clearly crash down a
system, so it's not just some ordinary risk less bug. I've
/etc/X11/Xsession patch to disable error logging
** Patch added: log xsession errors in /dev/null
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/60448/+attachment/1508356/+files/Xsession.patch
--
.xsession_errors file grows out of control saturates disk space
this is still an annoying problem in lucid with gnome while running
buggy/verbose software. the file needs to be truncated in realtime and should
be disabled or put on a ramdisk for ssd users imho. this potentially breaks the
users' hardware in the long run without anything being really broken
Stumbled upon this thread b/o system filling up to 100% slowly without clear
reason.
I second the last report by jason, similar issue, the .xsession-errors was
huge, removed it.
Amazing this issue still exists (or reoccurs)
yet slowly but surely the filesytem fills up with a MB per 1-3
err:wave:wodPlayer_WriteMaxFrags Error in writing wavehdr. Reason:
Input/output error
It seems that this error is filling it up at a rate over 20 MB/sec while
I type this. Thanks for the command, manu, very helpful.
I just tried disabling the file per those instructions making a link to
I can't find any text editor that can open a 1 GB text file so I have
no idea what's causing it to expand that much, clearly the only way to
solve the expanding .xsession_errors is to cap it at a certain file
size. Having an option to disable it entirely would be nice too.
The file grows to 10
#47
Jason, try:
tail --lines=20 ~/.xsession-errors
If you don't experience any other problems with X windows, just disable
it, see comment #41
--
.xsession_errors file grows out of control saturates disk space
https://bugs.launchpad.net/bugs/60448
You received this bug notification because
It appears that the .xsession-errors file creates anew after each
reboot, moving the previous content to .xsession-errors.old and an
enormous size file can be eliminated by rebooting twice, but what is
causing the file to grow needs to be determined and fixed otherwise the
problem recurs. I think
It's gdm/kdm/other DM open this log file and keep it open; so they'd
need to watch it and truncate it regularly.
** Package changed: xorg (Ubuntu) = gdm (Ubuntu)
** Changed in: gdm (Ubuntu)
Importance: High = Low
** Changed in: gdm (Ubuntu)
Status: In Progress = Triaged
** Changed
18 matches
Mail list logo
