17 May
2012
17 May
'12
1:05 a.m.
I've noticed many errors in my .xsession-error.log. The main culprit is:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3600134
The opcode is usually 19 or 20. The errors are mainly caused from gtk
applications written in gtkdialog with many other entries being from
tdeinit.
[tdeinit] Got EXT_EXEC 'kfmclient' from launcher.
[tdeinit] PID 4739 terminated.
At the moment i am softlinking .xsession-errors to /dev/null in my
environment. An ugly fix.
The log fills quite fast. Is this just bad coding of gtk apps?
Kind Regards,
Jay
17 May
17 May
1:45 a.m.
New subject: [trinity-devel] xsession error log
I've noticed many errors in my
.xsession-error.log. The main culprit is:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3600134
The opcode is usually 19 or 20. The errors are mainly caused
from gtk applications written in gtkdialog with many other
entries being from tdeinit.
[tdeinit] Got EXT_EXEC 'kfmclient' from launcher.
[tdeinit] PID 4739 terminated.
At the moment i am softlinking .xsession-errors to
/dev/null in my environment. An ugly fix.
The log fills quite fast. Is this just bad coding of gtk
apps?
Those errors have been around for years:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=297
I have seen al lkinds of things generate the errors, not just GTK apps. I'm be curious
to hear from some GNOME or Xfce users how rampant the errors appear in those
environments.
Please add any clues you find to the bug report.
Darrell
1:49 a.m.
New subject: [trinity-devel] xsession error log
At the moment i am softlinking .xsession-errors to
/dev/null in my
environment. An ugly fix.
Try changing it to /tmp/xsession-errors. it works quite well and if you
have a tmpfs setup it won't hurt your hard drive. I find it extremely
aggravating that .xsession-errors is written full of useless crap-ol-ah
noon
New subject: [trinity-devel] xsession error log
I really should have checked the bug reports first. Sorry.
Try changing it to /tmp/xsession-errors.
Thanks, will try that. We do indeed use a
tmpfs.
Jay
On Thu, May 17, 2012 at 1:49 AM, Calvin Morrison <mutantturkey(a)gmail.com>wrote;wrote:
> At the moment i am softlinking .xsession-errors to /dev/null in my
>> environment. An ugly fix.
>
> Try changing it to /tmp/xsession-errors. it works quite well and if you
> have a tmpfs setup it won't hurt your hard drive. I find it extremely
> aggravating that .xsession-errors is written full of useless crap-ol-ah
>
------------------------------**------------------------------**---------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@**
>
lists.pearsoncomputing.net<trinity-devel-unsubscribe(a)lists.pearsoncomputing.net > For additional commands, e-mail:
trinity-devel-help(a)lists.**
> pearsoncomputing.net <trinity-devel-help(a)lists.pearsoncomputing.net > Read list messages on the web archive:
http://trinity-devel.**
> pearsoncomputing.net/ <http://trinity-devel.pearsoncomputing.net/ > Please remember not to top-post:
http://trinity.**
>
pearsoncomputing.net/mailing_**lists/#top-posting<http://trinity.pearson…
4603
days inactive
4603
days old
3 comments
3 participants
participants (3)
-
Calvin Morrison -
Darrell Anderson -
Jay