I can confirm this bug.
I have a .xsession-errors from a backup.
The file is 22821 lines. Over half of this is from kcheckgmail.
(tdn@bart) (07-05-17 23:25) (P:0 L:1) [0] [ 23:25:59 up 1 day, 22:27, 2 users, load average: 0.70, 1.09, 1.03] ~/bart-backup-2007-05-03/tdn $ ls -lh .xsession-errors -rw------- 1 tdn tdn 1,3M 2007-05-03 15:05 .xsession-errors (tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:05 up 1 day, 22:27, 2 users, load average: 0.64, 1.07, 1.02] ~/bart-backup-2007-05-03/tdn $ wc -l .xsession-errors 22821 .xsession-errors (tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:08 up 1 day, 22:27, 2 users, load average: 0.64, 1.07, 1.02] ~/bart-backup-2007-05-03/tdn $ grep kcheck .xsession-errors|wc -l 16041 (tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:21 up 1 day, 22:27, 2 users, load average: 0.50, 1.02, 1.01] ~/bart-backup-2007-05-03/tdn $
I can confirm this bug.
I have a .xsession-errors from a backup.
The file is 22821 lines. Over half of this is from kcheckgmail.
(tdn@bart) (07-05-17 23:25) (P:0 L:1) [0] [ 23:25:59 up 1 day, 22:27, 2 users, load average: 0.70, 1.09, 1.03] backup- 2007-05- 03/tdn $ ls -lh .xsession-errors backup- 2007-05- 03/tdn $ wc -l .xsession-errors backup- 2007-05- 03/tdn $ grep kcheck .xsession-errors|wc -l backup- 2007-05- 03/tdn $
~/bart-
-rw------- 1 tdn tdn 1,3M 2007-05-03 15:05 .xsession-errors
(tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:05 up 1 day, 22:27, 2 users, load average: 0.64, 1.07, 1.02]
~/bart-
22821 .xsession-errors
(tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:08 up 1 day, 22:27, 2 users, load average: 0.64, 1.07, 1.02]
~/bart-
16041
(tdn@bart) (07-05-17 23:26) (P:0 L:1) [0] [ 23:26:21 up 1 day, 22:27, 2 users, load average: 0.50, 1.02, 1.01]
~/bart-