[Solved] ~/*.xsession-errors

Sector11 · 2021-02-25 16:55:28

Why are things like this:

2021-02-25 12:21:12 (11.2 MB/s) - written to stdout [7836]

--2021-02-25 12:22:40--  https://mail.google.com/mail/feed/atom
--2021-02-25 12:22:40--  https://mail.google.com/mail/feed/atom
Resolving mail.google.com (mail.google.com)... Resolving mail.google.com (mail.google.com)... {snip}
Connecting to mail.google.com (mail.google.com)|{snip}
Connecting to mail.google.com (mail.google.com)|{snip}... connected.
connected.
HTTP request sent, awaiting response... HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/xml]
Saving to: ‘STDOUT’

     0K                                                        9.77M=0s

2021-02-25 12:22:40 (9.77 MB/s) - written to stdout [340]

being written to ~/*.xsession-errors continiuously.

Now the current ending I understand but would like to fix the problem:

2021-02-25 13:55:41 (3.81 MB/s) - written to stdout [8503]


###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost


(thunar:977): Gtk-WARNING **: 13:56:40.802: no trigger event for menu popup

(thunar:977): Gtk-CRITICAL **: 13:56:40.802: gtk_menu_popup_at_rect: assertion 'GDK_IS_WINDOW (rect_window)' failed

(thunar:977): Gdk-CRITICAL **: 13:56:40.802: gdk_event_free: assertion 'event != NULL' failed

Any help appreciated.

unklar · 2021-02-25 18:36:17

^Hello, my friend.

If the issue is that this .xsession-errors keeps getting extremely large because a bunch of meaningless stuff is written in it, to the point that overnight the hard disk is full, then I can suggest you two solutions: big_smile

1. the Humane
by logrotate, weekly or daily and keep max. two versions.

sudo touch /etc/logrotate.d/xsession

with this content

$HOME/.xsession-errors {
  rotate 2
  weekly
  compress
  missingok
  notifempty
}

(of course, according to your path) wink

2. the Rapiate (currently use in siduction)
a script for the orkus yikes

#!/bin/sh
if [ ! -h /home/unklar/.xsession-errors ]; then
	rm /home/unklar/.xsession-errors
	ln -s /dev/null /home/unklar/.xsession-errors
fi

make executable
(of course, according to your path)
into the autostart of your OS smile

If that's not what you mean, forget it. lol

ohnonot · 2021-02-25 20:27:54

Your first output looks like fairly standard wget output; my guess is that one of your conkys downloads & parses a web page and did not add the --quiet option to wget.

The 2nd output is unfortunately totally normal. Unless you're a GTK developer you can (try to) ignore it.

Sector11 · 2021-02-26 00:52:04

ohnonot wrote:

Your first output looks like fairly standard wget output; my guess is that one of your conkys downloads & parses a web page and did not add the --quiet option to wget.

The bash script gets the "number of new emails" from gmail. wget so the output is needed.

#!/bin/bash

wget -O - --user myemail@gmail.com --password mypassword --auth-no-challenge https://mail.google.com/mail/feed/atom | sed 's/^.*<fullcount>//' | sed 's/<\/fullcount>.*$//' > $HOME/conky_gmail/mails_number

mails=$(sed -n 1p $HOME/conky_gmail/mails_number)
sound=$(ls $HOME/conky_gmail/mail_sounds/ | shuf -n 1)
if [[ $mails > 0 ]]; then
	aplay $HOME/conky_gmail/mail_sounds/$sound
fi

The 2nd output is unfortunately totally normal. Unless you're a GTK developer you can (try to) ignore it.

or get rid of ~/.xsessions-errors all together.

See next post ...

Sector11 · 2021-02-26 01:04:24

unklar wrote:

^Hello, my friend.
If the issue is that this .xsession-errors keeps getting extremely large because a bunch of meaningless stuff is written in it, to the point that overnight the hard disk is full, then I can suggest you two solutions:
1. the Humane
{snip}
2. the Rapiate (currently use in siduction)
{snip}
If that's not what you mean, forget it.

With all my years of using Linux I have never has a problem with this file until recently.

so you got me looking with that siduction solution... I dug further and found this.

TL:DR:

Disable writes on .xsession-errors file
If you want to forget about this log because in normal operation you are not interested in its debugging information, you can redirect to /dev/null everything that is written to it and thus always keep a size of 0 bytes. For this you can edit the /etc/X11/Xsession configuration file of the X Window system and locate the following line:
ERRFILE=$HOME/.xsession-errors
Replace it with:
ERRFILE=/dev/null

Done!

Sector11 · 2021-02-26 01:05:07

Thanks Guys

damo · 2021-02-26 07:35:11

I run a shutdown script which truncates the errors file to the last 100 lines (there is a one-liner in Scripts&Tips somewhere). The errors ARE actually useful sometimes!

unklar · 2021-02-26 12:50:08

Sector11 wrote:

...
so you got me looking with that siduction solution... I dug further and found this.
TL:DR:
...

Well dug, I did not know. big_smile

#1 2021-02-25 16:55:28

[Solved] ~/*.xsession-errors

#2 2021-02-25 18:36:17

Re: [Solved] ~/*.xsession-errors

#3 2021-02-25 20:27:54

Re: [Solved] ~/*.xsession-errors

#4 2021-02-26 00:52:04

Re: [Solved] ~/*.xsession-errors

#5 2021-02-26 01:04:24

Re: [Solved] ~/*.xsession-errors

#6 2021-02-26 01:05:07

Re: [Solved] ~/*.xsession-errors

#7 2021-02-26 07:35:11

Re: [Solved] ~/*.xsession-errors

#8 2021-02-26 12:50:08

Re: [Solved] ~/*.xsession-errors

Board footer