xsession.errors next question

[Derek Broughton]

Nils Kassube wrote:

> Ray Parrish wrote:
>> Nils Kassube wrote:
>> > Ray Parrish wrote:
>> >> Well, no one's answering, so I guess I stumped the group. On this
>> >> question and all of the other ones I asked about error messages in
>> >> the xsession file.
>> >>
>> >> I really haven't found this group to be much of a help yet with any
>> >> errors I encounter. I do learn a little bit from the answers to
>> >> other people, but when I ask one, no-one seems to know the answer.
>> >
>> > I think the reason is that nobody cares about what is in
>> > the .xsession-errors file. After all nearly every KDE application
>> > spits out tons of warnings which all land in this file. IMHO the file
>> > name is a bit misleading, i.e. it should rather be
>> > .xsession-warnings.
>>
>> Errors, warning messages... what's the difference? Something's not
>> working right, and I'd like to know what it is and fix it if possible.
> 
> My definition of the difference is this. A warning is given if something
> unexpected but non-fatal happens during the operation of a program and
> the operation continues. An error would be an explanation for something
> fatal where the program can't continue. Here is an example for a warning
> from my .xsession-errors file:

In fact, I'd say it shouldn't be .xsession-warnings, either.  It's just 
.xsession-log.  The file contains far more than errors and warnings - it 
contains a huge amount of debugging information that sloppy programmers 
didn't bother to turn off.  So, if your program works, but feeds huge amounts 
of output to .xsession-errors, file a bug report...

> | kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated
> | action.
> 
> In both cases I wouldn't expect to find someone on this list who knows how
> to eliminate the problem.

I pretty much expect _that_ one to get fixed when it needs to be fixed...  
It's often not a good idea to even try to update code that uses deprecated 
calls until you have to.

>> Some of the questions I asked seemed to be security related to me, like
>> the one about an ssh connection already being open... why is an ssh
>> connection opening when I'm not using it for anything?
> 
> Yes, that's a really interesting question but I can't help you there.

The answer of course is that you _are_ using it for something, but that's a 
different thread (I hope).