Your message dated Fri, 04 Sep 2015 07:55:13 +0100
with message-id <55e94051.8040...@zoho.com>
and subject line Re: [pkg-fgfs-crew] Bug#797936: libsimgearscene3.4.0: Fixed
has caused the Debian Bug report #797936,
regarding flightgear: Crash on startup: symbol lookup error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
797936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flightgear
Version: 3.4.0-1
Severity: important

Flightgear does not launch.

$ fgo

Avvio di /usr/games/fgfs con le opzioni seguenti:
        --atlas=socket,out,5,localhost,5501,udp
        --aircraft=Cub
        --airport=LIMC
        --fg-root=/usr/share/games/flightgear
        --fg-scenery=/home/lucio/flightgear/Scenery

--------------------------------------------------------------------------------

/usr/games/fgfs: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libSimGearScene.so.3.4.0: undefined symbol: 
_ZN5osgDB16ReadFileCallback11openArchiveERKSsNS_12ReaderWriter13ArchiveStatusEjPKNS_7OptionsE

$ fgrun
fgrun: symbol lookup error: /usr/lib/x86_64-linux-gnu/libSimGearScene.so.3.4.0: 
undefined symbol: 
_ZN5osgDB16ReadFileCallback11openArchiveERKSsNS_12ReaderWriter13ArchiveStatusEjPKNS_7OptionsE

$ fgfs
fgfs: symbol lookup error: /usr/lib/x86_64-linux-gnu/libSimGearScene.so.3.4.0: 
undefined symbol: 
_ZN5osgDB16ReadFileCallback11openArchiveERKSsNS_12ReaderWriter13ArchiveStatusEjPKNS_7OptionsE


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (998, 'unstable'), (994, 'testing'), (990, 'stable'), (500, 
'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flightgear depends on:
ii  flightgear-data-all       3.4.0+dfsg-1
ii  freeglut3                 2.8.1-2
ii  libc6                     2.19-19
ii  libdbus-1-3               1.8.20-1
ii  libflite1                 1.4-release-12
ii  libgcc1                   1:5.2.1-15
ii  libgl1-mesa-glx [libgl1]  10.6.5-1
ii  libglu1-mesa [libglu1]    9.0.0-2
ii  libgsm1                   1.0.13-4
ii  libhtsengine1             1.08-1
ii  libice6                   2:1.0.9-1+b1
ii  libopenal1                1:1.16.0-3
ii  libopenscenegraph100      3.2.1-6+b3
ii  libopenthreads20          3.2.1-7
ii  libplib1                  1.8.5-7
ii  libpng12-0                1.2.50-2+b2
ii  libsimgearcore3.4.0       3.4.0-2
ii  libsimgearscene3.4.0      3.4.0-2
ii  libsm6                    2:1.2.2-1+b1
ii  libspeex1                 1.2~rc1.2-1
ii  libspeexdsp1              1.2~rc1.2-1
ii  libsqlite3-0              3.8.11.1-1
ii  libstdc++6                5.2.1-15
ii  libudev1                  225-1
ii  libx11-6                  2:1.6.3-1
ii  libxext6                  2:1.3.3-1
ii  libxi6                    2:1.7.4-1+b2
ii  libxmu6                   2:1.1.2-1
ii  zlib1g                    1:1.2.8.dfsg-2+b1

flightgear recommends no packages.

flightgear suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 3.4.0-2+b1

We didn't do anything, but someone recompiled simgear+flightgear (hence the +b1 suffix), so it evidently was a gcc5 transition issue.
--- End Message ---

Reply via email to