Bug 139942

Summary:	kdm.log fills up root partition
Product:	[Unmaintained] kdm	Reporter:	Josh Metzler <joshdeb>
Component:	general	Assignee:	kdm bugs tracker <kdm-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	davian818
Priority:	HI
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Josh Metzler 2007-01-12 03:41:52 UTC

Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I am forwarding this bug from a Debian user:

Package: kdm
Version: 4:3.5.5a.dfsg.1-1
Severity: grave

Hello,

I recently discovered that my root partition was full. The reason was
not really clear, since there were over 3gb free. I found that kdm.log
files are full of crap: billions of duplicated lines, apparently comming
from X server but stored there. Example:

(**) RADEON(0): RADEONSaveScreen(2)
(**) RADEON(0): RADEONSaveScreen(2)
(many thousands of that)
Freeing resource id=40207B4A which isn't there.
Freeing resource id=40207B4A which isn't there.
(many millions of that)

If I look at the time stamp, I see that RADEONSaveScreen lines are added
even now, while I am logged into X trough kdm already.

Seriously, upstream should think about adding a simple filter for
duplicates, like syslog does. Or not log the messages at all, or collect
them in chunks and not store more than eg. one MB. Or both.

Eduard.

Comment 1 Oswald Buddenhagen 2007-02-10 17:36:47 UTC

important, but still only a missing feature.

Comment 2 Urmas 2011-01-02 11:55:17 UTC

I had severe data loss because of garbage-filled kdm.log file grown up to several GBs. If you do not use standard logging features, please ensure you keep your logs in sensible manner!

Comment 3 Urmas 2011-08-10 03:25:08 UTC

Also, why it is WISHLIST? The bug causes FUCKING DATA LOSS!

Comment 4 Nate Graham 2018-04-16 20:24:37 UTC

KDM is unmaintained and not used in KDE Plasma 5.

SDDM is the login manager used in KDE Plasma 5. If you still have this same issue with SDDM, please file an issue on the SDDM bugtracker (after doing a search for existing issues first!): https://github.com/sddm/sddm/issues/