Where is the Error Log File (v.1.13.7) on Linux?

The place to post your WML questions and answers.

Moderators: Forum Moderators, Developers

Forum rules
  • Please use [code] BBCode tags in your posts for embedding WML snippets.
  • To keep your code readable so that others can easily help you, make sure to indent it following our conventions.
Post Reply
User avatar
chol
Posts: 38
Joined: September 9th, 2015, 11:19 am

Where is the Error Log File (v.1.13.7) on Linux?

Post by chol »

Where is the Error Log File (v.1.13.7) on Linux?
I've looked in /home/user/.local/share/wesnoth/1.13/
I've installed dbg symbols package
I've set my log-levels to max in >Main Menu>Settings>..

Where is the stderr file? Where to find, what else to do? Some hints?
Could somebody help me please?

Tad_Carlucci
Developer
Posts: 499
Joined: April 24th, 2016, 4:18 pm

Re: Where is the Error Log File (v.1.13.7) on Linux?

Post by Tad_Carlucci »

Launch wesnoth from a shell. stdout and stderr are on your console. Launched from a GUI menu/icon and stdout/stderr is discarded
I forked real life and now I'm getting merge conflicts.

User avatar
Pentarctagon
Forum Administrator
Posts: 4176
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Where is the Error Log File (v.1.13.7) on Linux?

Post by Pentarctagon »

More details here.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code

User avatar
tr0ll
Posts: 524
Joined: June 11th, 2006, 8:13 pm
Location: canada

Re: Where is the Error Log File (v.1.13.7) on Linux?

Post by tr0ll »

I wanted to launch Wesnoth from the GUI and still keep stderr and stdout logs. I have GNU/Linux Devuan 1.0 (Debian 8.0 sans systemd) with XFCE.
The first step was copying the global desktop entry to my profile (assuming Wesnoth is installed):

Code: Select all

cp /usr/local/share/applications/wesnoth.desktop ~/.local/share/applications/
Then edit my local desktop entry and modify the line

Code: Select all

Exec=wesnoth
After some frustration with "Error in command line: too many positional options have been specified on the command line" or wesnoth picking the wrong data directory, i hit upon this:

Code: Select all

Exec=sh -c "wesnoth >> ~/wesnoth.log 2>&1"
You can debug the development of your desktop entry by opening a terminal window and doing

Code: Select all

tail -f ~/.xsession-errors

Post Reply