Bug#933162: unknown-horizons: unknown-horizons crashes when starting

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#933162: unknown-horizons: unknown-horizons crashes when starting

Jose Ortiz
Package: unknown-horizons
Version: 2019.1-1
Severity: normal

Dear Maintainer,

unknown-horizons crashes when I started from the command line with the following message

$ unknown-horizons --debug

> Python version: sys.version_info(major=3, minor=7, micro=3, releaselevel='final', serial=0)
> Platform: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0
> SYS.PATH: ['/usr/games', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.7/dist-packages']
> PATHSEP: ":" SEP: "/"
> LD_LIBRARY_PATH: <undefined>
> PATH: /home/lui/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> PYTHONPATH <undefined>
> Python version: sys.version_info(major=3, minor=7, micro=3, releaselevel='final', serial=0)
> Platform: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0
> Using fife version 0.4.2, at least 0.4.2 required
> Controller:LOG:Fifengine v0.4.2
> Controller:LOG:================== Engine initialize start =================
> Controller:LOG:Time manager created
> Controller:LOG:Creating VFS
> Controller:LOG:Adding root directory to VFS
> VFS:DEBUG:VFSDirectory created with root path ./
> VFS:LOG:new provider: OS Directory
> Controller:LOG:Adding zip provider to VFS
> VFS:LOG:new provider: ZIP
> Controller:LOG:Engine pre-init done
> Controller:LOG:Creating event manager
> Controller:LOG:Creating resource managers
> Controller:LOG:Creating render backend
> Controller:LOG:OpenGL Render backend created
> Controller:LOG:Initializing render backend
> Controller:WARN:Selected video driver is not supported for your Operating System!  Reverting to default driver.
> Controller:LOG:Querying device capabilities
> Controller:LOG:Creating main screen
> Video:LOG:RenderBackendOpenGLError initializing GLEW!Missing GL version
> Video:LOG:RenderBackendOpenGLVideomode 1366x768 at 0 bpp with 60 Hz
> Segmentation fault


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages unknown-horizons depends on:
ii  python3         3.7.3-1
ii  python3-enet    0.0~vcs.2017.05.26.git-2.1+b1
ii  python3-fife    0.4.2-1
ii  python3-future  0.16.0-1
ii  python3-yaml    3.13-2
ii  ttf-unifont     1:11.0.03-1

unknown-horizons recommends no packages.

unknown-horizons suggests no packages.

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#933162: unknown-horizons: unknown-horizons crashes when starting

Bernhard Übelacker-3
Hello Jose Ortiz,
without deeper knowledge of unknown-horizons I tried to reproduce
this issue, but it did not show up for me.

It might be possible to install the package systemd-coredump.

Then in the journal should a backtrace be printed when you
repeat the checkconfig, which you could forward to this bug.

Additionally the backtrace would contain more function names when
the matching debug symbols are installed like described in [1].
This page might give some more pointer how to retrieve more
information from that issue.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols